We’re excited to announce support for tablespace monitoring and database parameter management in Cloud Infrastructure (OCI) Database Management service for on-premises databases. The feature allows you to have a better understanding about the database storage footprint and key database configuration parameters.
A common task for a database administrator is to monitor and manage tablespaces. This task can include monitoring space for all the data files in a tablespace, setting thresholds as an early warning mechanism for space issues, and taking corrective action to automatically address the ‘tablespace full’ problem across different types of tablespaces.
The tablespace monitoring feature supports basic monitoring to report the space used and allocated for all the data files within the system and user tablespaces. You can search by tablespace name, get a summary of the overall space allocated and used for the entire database, and get a breakdown by individual tablespaces and data files. You can also view the status of the tablespaces and data files to identify key attributes, such as defaultCellMemory, defaultIndexCompression, and defaultTableCompression. These attributes are useful for a better understanding of the storage configuration.
Figure 1: Tablespace monitoring in managed database details page
When you create preconfigured databases provided by Oracle, the initialization parameters are optimized for normal use in the environment that you specify. You can view and modify the parameter settings for your database using the database parameters page under Resources in the managed database details page.
The following property pages show on the Database Parameters page:
Current: This page displays all the initialization parameter values that are currently in memory for the database instance. You can use this page to make dynamic changes to parameters in the currently running instance. Only parameters marked ‘dynamic’ can change. To persist the changes across database restarts, you can optionally apply changes to the server parameter file (spfile).
Server parameter file: This property page shows the parameter values in the database spfile, whose location is displayed at the top of the table. Changes to parameter settings in this file are persistent across instance startup and shutdown. If the parameter is marked dynamic, you can apply changes to the currently running instance. If you don’t exercise this option, your changes don’t take effect until the database is shut down and restarted.
You can also track any deviations in database parameter settings between the current instance and the server parameter file configuration with the option to reset to the default configuration equivalent to factory default.
Figure 2: Database parameters in managed database details page
Having a standardization strategy for your database deployments is important. Using the tablespace monitoring and database parameter configuration features, you can achieve easy automation, increased security, and reduced human error.