If the system is running the Oracle Database, you can use the Oracle Solaris System Web Interface to view a high-level overview of Oracle Database performance and problems on that system. The information provided enables an Oracle Solaris administrator to diagnose whether the source of a problem is in the operating system, network, or storage, or whether a database administrator is required to further diagnose the problem.
Use the Oracle Database sheet to examine data such as the following:
Number of times per second that the database performs block changes, data retrievals, or user commits.
Amount of time the database spends waiting due to system events, user application code, and system configuration.
See V$SYSTEM_EVENT and V$SYSSTAT in “Instance Tuning Using Performance Views” in the database performance tuning guide. For example, see Oracle Database Performance Tuning Guide 18c. In particular, see “Table of Wait Events and Potential Causes.”
Memory consumption of running database processes.
The Oracle Database sheet also includes system performance visualizations that are not specific to Oracle Database but are included for convenience. For example, you could correlate a drop in database work or an increase in database wait times with an increase in disk reads and writes from other sources or with a CPU going offline.
The following figure shows an example of an Oracle Database sheet. The Oracle Database instance in this example is mypdb.
Figure 11 Sample Oracle Database Sheet
To use the Oracle Database sheet, install the service/oracle-rdbms-stats package. The service/oracle-rdbms-stats package delivers the Oracle Database sheet, Instant Client, the application/stats/oracle-database-stats SMF service, the statcfg utility, and the statcfg(1) and rdbms-stat(1) man pages.
The statcfg utility enables the administrator to configure an Oracle Database sheet to report statistics for a specific Oracle Database instance. Until you run the statcfg utility, the oracle-database-stats SMF service is disabled, and you will not see an Oracle Database sheet.
To run the statcfg utility, you must have the solaris.smf.modify authorization. The following example shows how to add this authorization for user admin:
# usermod -A +solaris.smf.modify admin
Invoke the statcfg utility as follows. See the statcfg(1) man page for more information.
# /usr/bin/statcfg oracle-rdbms -u user -g group -s sid -c connectstring
The Oracle Solaris user and group that this oracle-database-stats service instance will run as.
The name of the Oracle Database instance that this oracle-database-stats:sid service instance will monitor.
The alias for access credentials for the sid database instance. See “Oracle Wallet” below for more information.
Perform the following configuration for user:
Ensure that user has the following authorizations assigned:
The following example shows how to add these authorizations for user:
# usermod -A +solaris.sstore.update.res,solaris.sstore.write user
Ensure that user has the SYSDBA connect privilege for the sid database instance.
The shell startup script for user must specify ORACLE_HOME, or specify ORACLE_HOME in the service as shown in the following example:
# svccfg -s application/stats/oracle-database-stats:sid \ setenv ORACLE_HOME /u0/app/oracle/product/12.2.0/dbhome_2
The sqlnet.ora parameter file must specify the Oracle Wallet location for user.
The tnsnames.ora file must specify the Oracle Wallet db_connect_string alias for the sid database instance.
By default, both sqlnet.ora and tnsnames.ora are located in the $ORACLE_HOME/network/admin directory.
Follow the instructions in “Managing the Secure External Password Store for Password Credentials” in the database security guide to configure the user’s Oracle Wallet. For example, see Oracle Database Security Guide 18c.
Check whether the oracle-database-stats:sid service is online.
If the service is in maintenance or is otherwise not online, check the service log as shown in the following example:
$ svcs -xL oracle-database-stats:sid
If any of the Oracle RDBMS connections fail to communicate with their respective databases, the service will enter the degraded state.
To check the settings of the service instance, use the svcprop command to show the values of the following properties:
For more information about service commands, see Managing System Services in Oracle Solaris 11.4.