ORA-04045,Standby停止Apple log处理一例
2008-06-11 17:51
633 查看
今天检查数据库,发现standby已经停止apply 了.查看日志发现如下错误:
LOGSTDBY status: ORA-04045: errors during recompilation/revalidation of MES.BARCODE_INFO_TR1
LOGSTDBY Apply process P005 pid=29 OS id=2232 stopped
Wed Jun 11 08:48:47 2008
LOGSTDBY status: ORA-04045: errors during recompilation/revalidation of MES.BARCODE_INFO_TR1
LOGSTDBY Apply process P004 pid=28 OS id=1580 stopped
Wed Jun 11 08:48:47 2008
LOGSTDBY status: ORA-04045: errors during recompilation/revalidation of MES.BARCODE_INFO_TR1
LOGSTDBY Apply process P007 pid=31 OS id=1248 stopped
Wed Jun 11 08:48:47 2008
LOGSTDBY status: ORA-04045: errors during recompilation/revalidation of MES.BARCODE_INFO_TR1
LOGSTDBY Apply process P008 pid=32 OS id=2668 stopped
Wed Jun 11 08:48:47 2008
Errors in file d:"mes"dump"bdump"mess_lsp0_2648.trc:
ORA-12801: error signaled in parallel query server P005
ORA-04045: errors during recompilation/revalidation of MES.BARCODE_INFO_TR1
LOGSTDBY Analyzer process P003 pid=27 OS id=2028 stopped
LOGSTDBY Apply process P006 pid=30 OS id=2480 stopped
Wed Jun 11 08:48:47 2008
LOGSTDBY status: ORA-16222: automatic Logical Standby retry of last action
LOGSTDBY status: ORA-16111: log mining and apply setting up
Wed Jun 11 08:48:47 2008
检查Trigger MES.BARCODE_INFO_TR1的状态,为不可用.发现这个trigger用到了一个DB_LINK.检查此DB_LINK,发现不可用.突然想到可能是standby的TNSNAMES和主库不同,修改成相同后,编译这个trigger,成功.
重新Apply,检查LOG,发现开始Apply.
LOGSTDBY status: ORA-04045: errors during recompilation/revalidation of MES.BARCODE_INFO_TR1
LOGSTDBY Apply process P005 pid=29 OS id=2232 stopped
Wed Jun 11 08:48:47 2008
LOGSTDBY status: ORA-04045: errors during recompilation/revalidation of MES.BARCODE_INFO_TR1
LOGSTDBY Apply process P004 pid=28 OS id=1580 stopped
Wed Jun 11 08:48:47 2008
LOGSTDBY status: ORA-04045: errors during recompilation/revalidation of MES.BARCODE_INFO_TR1
LOGSTDBY Apply process P007 pid=31 OS id=1248 stopped
Wed Jun 11 08:48:47 2008
LOGSTDBY status: ORA-04045: errors during recompilation/revalidation of MES.BARCODE_INFO_TR1
LOGSTDBY Apply process P008 pid=32 OS id=2668 stopped
Wed Jun 11 08:48:47 2008
Errors in file d:"mes"dump"bdump"mess_lsp0_2648.trc:
ORA-12801: error signaled in parallel query server P005
ORA-04045: errors during recompilation/revalidation of MES.BARCODE_INFO_TR1
LOGSTDBY Analyzer process P003 pid=27 OS id=2028 stopped
LOGSTDBY Apply process P006 pid=30 OS id=2480 stopped
Wed Jun 11 08:48:47 2008
LOGSTDBY status: ORA-16222: automatic Logical Standby retry of last action
LOGSTDBY status: ORA-16111: log mining and apply setting up
Wed Jun 11 08:48:47 2008
检查Trigger MES.BARCODE_INFO_TR1的状态,为不可用.发现这个trigger用到了一个DB_LINK.检查此DB_LINK,发现不可用.突然想到可能是standby的TNSNAMES和主库不同,修改成相同后,编译这个trigger,成功.
重新Apply,检查LOG,发现开始Apply.
相关文章推荐
- Poster: ORA-01458: invalid length inside variable character string. 处理一例
- ORA-00054 故障处理一例
- Drop user cascade failed ORA-00604 ORA-02429 处理一例
- ORA-00054 故障处理一例
- ORA-00054 故障处理一例
- ORA-27102:out of memeory 故障处理一例
- 远程通过监听连接报ORA-01034故障处理一例
- ora.LISTENER.lsnr INTERMEDIATE 处理一例
- ORA-00054 故障处理一例
- 处理因sqlnet.ora引起的ASM资源为UNKNOWN一例
- impdp导入数据报错"ORA-39029"处理一例
- ORA-00201处理一例
- ORA-28547 故障处理一例
- STANDBY_FILE_MANAGEMENT参数导致的ORA-01274错误处理
- 逻辑 STANDBY ORA-00368日志应用失败处理一例
- ORA-01031: insufficient privileges处理一例 推荐
- primary同步数据到逻辑standby时报违反唯一约束(ora-00001)导致逻辑standby同步停止
- ORA-1547一例处理
- ORA-30009 故障处理一例
- ORA-12528处理一例---补充