您正在查看 "Oracle Err" 分类下的文章
2009-08-24 11:09
--alert.log出现很多如下警告日志:
Errors in file /u01/app/oracle/admin/ESUITE/bdump/esuite_rvwr_23296.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 18055168 bytes disk space from 85899345920 limit
--查看dba_outstanding_alerts视图(oracle10g新增的):
SQL> col REASON format a40
col OBJECT_TYPE format a20
col CREATION_TIME format a35
col TIME_SUGGESTED format a35
col SUGGESTED_ACTION format a75
SQL> select obj |
2009-08-17 15:53
oracle10g 里 expdp 时遇到以下错误:
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [PROCACT_SCHEMA:"U_EXPDP"]
ORA-04063: view "SYS.KU$_CLUSTER_VIEW" has errors
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 6313
----- PL/SQL Call Stack -----
object |
2009-08-13 10:04
SQL> startup;
ORACLE instance started.
Total System Global Area 2147483648 bytes
Fixed Size 1220460 bytes
Variable Size 452984980 bytes
Database Buffers 1677721600 bytes
Redo Buffers |
2009-07-28 11:59
如果之前装过, 但OMS服务器换了(比如换机器了或者重装了等等)那么参照以下步骤重新配置Agent即可:
1) Stop Agent
$ $AGENT_HOME/bin/emctl stop agent
2) 更改emd.properties
$ vi $AGENT_HOME/sysman/config/emd.properties
...
REPOSITORY_URL=https://dataguard2:1159/em/upload
...
agentTZRegion=PRC
...
其中REPOSITORY_URL如果忘记了就是参考OMS所在机器上的AGENT(默认的OMS服务器也安装了AGENT: $AGENT_HOME/bin/emctl status agent), 然后找到Rep |
2009-07-09 16:28
平台: Oracle10.2.0.4
dataguard主库redo大小发生变更后, 如果此时备库的standby redo大小未跟着更改, 则会发生ORA-16086错误.
Thu Jul 9 15:18:43 2009
Errors in file /u01/app/oracle/admin/YITIAN/bdump/yitian_lgwr_3550.trc:
ORA-16086: standby database does not contain available standby log files
Thu Jul 9 15:18:43 2009
LGWR: Failed to archive log 7 thread 1 sequence 4206 (16086)
Thu Jul 9 15:18:47 2009
Thread 1 a |
2009-07-08 11:58
注意, 如果是64bit备库的建立时源于32bit主库(反过来也一样), 在启动备库或开启sql apply的时候会遇到"ORA-06553: PLS-801: internal error [56319]"错误, 这就要求在开启sql apply前先重新编译64bit的plsql模块, 按照如下步骤操作:
|
2009-04-22 15:20
其中全库复制那个库已经开启了实时异地捕获, 而用户复制这个库开启时却提示如下错误:
SQL> exec DBMS_CAPTURE_ADM.SET_PARAMETER(capture_name => 'CAP_WENDING', parameter => 'downstream_real_time_mine', value => 'y');
BEGIN DBMS_CAPTURE_ADM.SET_PARAMETER(capture_name => 'CAP_WENDING', parameter => 'downstream_real_time_mine', value => 'y'); END;
*
ERROR at line 1:
ORA-23605: invalid value "y" for STREAMS |
2009-04-15 13:26
如果源库原先配置过Dataguard, 尽管后来删除了Dataguard环境.
再基于源库配置异地捕获方式的Streams复制时, 设置源库日志传送方式总是提示ORA-16052: DB_UNIQUE_NAME attribute is required, 加了该属性后, alert.log和v$archive_dest里又会提示"ORA-16047 目标设置和备用之间的 DGID 不匹配"错误, 即使把参数 log_archive_config 设置为空也不行.
其实是还要显示设置 log_archive_config 参数为"NODG_CONFIG"才行:
SQL> ALTER SYSTEM SET log_archive_config='NODG_CONFIG';
|
2009-04-13 17:19
今天给Streams管理用户授权时遇到如下错误:
SQL> exec DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE(grantee => 'strmrep',grant_privileges => true);
BEGIN DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE(grantee => 'strmrep',grant_privileges => true); END;
*
ERROR at line 1:
ORA-04063: package body "SYS.DBMS_LOGREP_UTIL" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_LOGREP_UTIL"
ORA-06512: at "SYS.DB |
2009-02-27 16:26
源库全库复制（rman恢复的方式）, 做完流初始化, 启动捕获进程有误。
alert.log提示:
Thu Jan 8 14:50:38 2009
Errors in file /u01/app/oracle/admin/esuite/bdump/esuite_c001_9636.trc:
ORA-23605: invalid value "" for STREAMS parameter FILE_NAME
ORA-06512: at "SYS.DBMS_CAPTURE_ADM_INTERNAL", line 842
ORA-06512: at "SYS.DBMS_CAPTURE_PROCESS", line 397
ORA-06512: at line 1
Metalink里说这是个bug 5278539, 后来发现是rman备份脚本里有删 |
|
| 
