刚刚安装了ORACLE 10g R2后，启动数据库时发现告警日志有如下错误：
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
Errors 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 not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "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 will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Fri Apr 24 13:48:04 2015
Starting background process CJQ0
CJQ0 started with pid=17, OS id=24786
[oracle@getlnx01 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 27 21:02:33 EDT 2011
Machine: x86_64
Instance name: epps
Redo thread mounted by this instance: 1
Oracle process number: 14
Unix process pid: 24778, image: oracle@getlnx01.esquel.com (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 not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
ORA-06512: at line 15
在eygle大神的Oracle10gR2的ORA-06512 OLAP错误博客里面解到，数据库启动过程中，执行了一个和OLAP有关的Trigger，出现这个错误。可以通过禁用这两个触发器解决这个问题。
禁用了这两个触发器后，重新启动数据库检查发现这个错误消失了。问题解决。