Oracle® Real User Experience Insight Administrator's Guide 12c Release 2 (12.1.0.3) for Linux x86-64 Part Number E37267-01 |
|
|
PDF · Mobi · ePub |
This chapter describes a number of settings necessary to perform database maintenance and facilitate backups.
In the event of a database crash, objects may become corrupted. Typically, this reveals itself with ORA-00376 and similar errors reported in the Event Log. It is recommended that you carefully review the information in the Knowledge Base article at the following location:
https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1303180.1
In particular, ensure that the indicated tablespaces are set to force logging. You can use the following command to view the status of the database tables:
cop stats %period
where period
indicates the required year (2012), month (201203), or day (20120326). The command output appears as follows:
STRUCTURE PRESENTATION DATA ROWS DATA SIZE hash data dims lvls pres view data desc data desc cube name------ ---- ---- ---- ---- ---- ------ ------ ------- ------- ----------fTq7vQ 19 11 22 133 156 0 2 0.1 MB 0.1 MB wg_keypage_mo_201203u7q+3g 9 4 8 13 7 - 470 0.6 MB 0.1 MB wg_kpi_mo_201203PMocAw 22 9 17 159 174 - 16960 19.0 MB 4.0 MB wg_page_mo_201203K/p4ww 12 12 29 123 104 0 0 0.1 MB 0.1 MB wg_service_mo_2012031S2Ggg 10 19 29 79 90 - 247 2.0 MB 0.1 MB wg_slowurl_mo_201203lZRuxg 29 5 10 279 61 0 0 0.1 MB 0.1 MB wg_trasta_mo_201203yuY0aQ 29 11 20 153 204 - 343 2.0 MB 0.1 MB wg_visit_mo_201203
Note that if the Data column contains a zero value, or there a large number of zeros or dashes, this would indicate corrupted database tables. In this case, you should use the script described in the following Knowledge Base article to restore the database:
https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=556733.1
In addition, it is recommended that you issue the following commands to force an update of the RUEI configuration and template tables:
makedatabase @ modr -fn all
When performing maintenance on the database, it is recommended that you manually stop RUEI processing for the time that the database is down to prevent the reporting of error messages to show. Do the following:
Use SSH to logon to the Reporter system as the RUEI_USER
user.
Issue the following command to stop processing:
project -stop wg
Ensure that the following processes are no longer running before bringing down the database: qjob
, logr
, and rsynclogdird
. If necessary, use the kill
command to stop them.
After completion of database maintenance, restart processing by issuing the following command:
project -start wg
As of version 12.1.0.3, the USERS
and UXCONF
tablespaces within new installations are set to force
logging
mode. Previously, the default mode was nologging
. The upgrade procedure does not change your database's current setting. However, be aware that changing the tablespace mode to force
logging
can considerably increase disk I/O.
By default, the database does not support online backups. In order to do so, the database's noarchivelog
mode needs to be changed, and a number of operations changed from nologging
mode to force
logging
mode. Do the following:
Logon to the database system as the oracle
user:
Stop all processing by issuing the following commands:
source /etc/ruei.conf su - $RUEI_USER project -stop wg killall logmsgd killall qjobd killall rsynclogdird
Ensure that the $RUEI_DB_INST
setting specifies the RUEI database.
Change the database to archivelog
mode by issuing the following commands:
. oraenv sqlplus / as sysdba shutdown immediate startup mount alter database archivelog; alter database open;
Issue the following commands to set the required operations to force
logging
mode:
alter tablespace USERS force logging; alter tablespace UXCONF force logging;
Configure and schedule the online backup.
See the Oracle Backup and Recovery User's Guide for further information. It is available at the following location:
http://www.oracle.com/pls/db112/portal.portal_db?selected=14
By default, redo logging of the RUEI database is disabled. If this is enabled for the complete database, very large redo log archives can be created. Therefore, if you want to use redo logging as part of your backup strategy, you need to make a number of configuration changes. Do the following:
Logon to the database system as the oracle
user.
Issue the following commands to set the required logging options in the RUEI database table spaces:
sqlplus / as sysdba SQL> alter tablespace USERS force logging; SQL> alter tablespace UXCONF force logging; SQL> alter tablespace UXSTAT no force logging; SQL> alter tablespace UXTEMP no force logging;
Note that the UXSTAT
and UXTEMP
tablespaces are not set to force
logging
because they are not relevant to the backup and restore process because they only contain intermediate data.
By default, the degree of parallelism used for core-related queries in the database is 1. This is controlled by the db_core_dop
setting. Increasing the number available can improve database performance. However, this setting should never be set to a number higher than the amount of cores available from the database server. This setting utilizes the DOP features of the Oracle database. It has no functional impact other than potentially making data processing run faster.
Use the following command to obtain the setting's current value:
execsql config_get_value processor db_core_dop
Use the following command to modify the setting's value:
execsql config_set_value processor db_core_dop dop
where dop
specifies the degree of parallelism used for queries in processing.
Additional statistics and facts database tables are automatically created to facilitate RUEI integration with Oracle Enterprise Manager. These tables can significantly increase the level of database I/O activity and storage requirements. The creation of these tables is controlled by the appliance_fact_enabled
and appliance_statistics_enabled
setting:
Use the following commands to obtain the settings' current values:
execsql config_get_value appliance fact_enabled execsql config_get_value appliance_statistics_enabled
Use the following commands to modify the settings' value:
execsql config_set_value appliance fact_enabled value execsql config_set_value appliance statistics_enabled value
where value
specifies whether the setting should be enabled (1) or disabled (0).
Be aware that disabling either of the above settings will prevent the correct operation of an Oracle Enterprise Manager deployment with a RUEI integration.