After the Oracle 10g R2 was installed, the alert log was found to have the following error when starting the database:
Database Characterset is UTF8
Replication_dependency_tracking turned off (no async multimaster replication found)
Warning:aq_tm_processes is set to 0. System operation might be adversely affected.
Fri APR 24 13:48:03 2015
in FILE/U01/APP/ORACLE/ADMIN/EPPS/UDUMP/EPPS_ORA_24778.TRC:
Ora-00604:error occurred at recursive SQL level 1
Ora-12663:services required by client no available on the server
Ora-36961:oracle OLAP is not available.
"SYS. Olapihistoryretention ", line 1
Ora-06512:at Line 15
Completed:alter DATABASE OPEN
Fri APR 24 13:48:03 2015
Db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
User-specified limit on the amount of space that would be used by this
for recovery-related files, and does not reflect the amount of
in the underlying filesystem or ASM DiskGroup.
Fri APR 24 13:48:04 2015
Process CJQ0
CJQ0 started with pid=17, OS id=24786
[[email protected] bdump]$ more/u01/app/oracle/admin/epps/udump/epps_ora_24778.trc
/u01/app/oracle/ ADMIN/EPPS/UDUMP/EPPS_ORA_24778.TRC
Oracle Database 10g Release 10.2.0.1.0-64bit Production
Oracle_home =/u01/ App/oracle/product/10.2.0/db_1
System name: Linux
Node name: getlnx01.esquel.com
release: 2.6.32-200.13.1.el5uek
version: #1 SMP Wed Jul 21:02:33 EDT-
machine: & nbsp; x86_64
Instance name:epps
Redo thread mounted by this instance:1
Oracle process number :
Unix process pid:24778, Image: [email protected] (TNS v1-v3)
SERVICE NAME: (sys$users) 2015-04-24 13:48:03.863
SESSION ID: (160.3) 2015-04-24 13:48:03.863
Error in executing triggers on database startup
2015-04-24 13:48:03.863
Ksedmp:internal or fatal error
Ora-00604:error occurred at recursive SQL level 1
Ora-12663:services required by client no available on the server
Ora-36961:oracle OLAP is not available.
Ora-06512:at "SYS. Olapihistoryretention ", line 1
Ora-06512:at Line 15
In the eygle of the oracle10gr2 of the great god ORA-06512 OLAP Error blog inside, the database startup process, the implementation of an OLAP-related trigger, this error occurs. You can resolve this issue by disabling both triggers.
When both triggers are disabled, restarting the database check finds that the error has disappeared. Problem solving.
Resources:
Http://www.eygle.com/archives/2007/08/10gr2_olap_trigger.html
ORACLE OLAP Error Ora-06512:at "SYS. Olapihistoryretention "