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错误博客里面解到...
问题描述 同事反应Oracle数据库在使用数据泵导出时,导出报UDE-31623、ORA-31623、ORA-06512,大致如下: 告警日志信息大致如下: 处理过程 (1)第一步, 我以为是streams pool size不足或者是sga分配不足导致的,查询后发现sga分配了64G,同时 streams pool size = 256M;故内存分配不足的问题呗排除了; (2)第二步,...
If you have installed Oracle Configuration Manager in a home that contains a database, you must run a script to instrument the database for configuration collection. Whether you are inConnectedorDisconnectedmode, youmustrun this script. It will create the database account, ORACLE_OCM. This accou...
Oracle Receivables - Version 11.5.9 to 11.5.10.3 [Release 11.5.9 to 11.5.10]: Remit-To Address Form Error: ORA-06550, PLS-00905: OBJECT APPS.ARP_STAX_165 IS INVALID,
ORA-27041:无法打开文件Linux-x86_64 Error: 2: No such file or directory Additional information: 3 ORA-06512:在line 9 是我们环境的临时表空间损坏了,oracle数据库的临时表空间是用来存放用户的临时数据,临时数据在需要时被覆盖,关闭数据库后自动删除,其中不能存放永久临时性数据。
ORA-06512: at line 15 在eygle大神的Oracle10gR2的ORA-06512 OLAP错误博客里面解到,数据库启动过程中,执行了一个和OLAP有关的Trigger,出现这个错误。可以通过禁用这两个触发器解决这个问题。 禁用了这两个触发器后,重新启动数据库检查发现这个错误消失了。问题解决。
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 ...
Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner. Alert log states the following error at startup of the database: ...
报错信息如下: UDE-31623: operation generatedOracleerror 31623ORA-31623: a job is not attached to this session via the specified handleORA-06512: at "SYS.DBMS_DATAPUMP", line 3263ORA-06512: at "SYS.DBMS_DATAPUMP", line 4488ORA-06512: at line 1 ...
奇怪的一点,主库业务用户也是没有这个系统表查询权限的,但是执行sql可以正常执行,这也有可能触发了oracle bug。