【翻译自mos文章】rman 备份时报:ORA-02396: exceeded maximum idle time
2014-07-17 12:44
288 查看
rman 备份时报:ORA-02396: exceeded maximum idle time
参考原文:
RMAN backup faling with ORA-02396: exceeded maximum idle time, please connect again (Doc ID 1446182.1)
适用于:
Oracle Server - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
症状:
rman 在备份db和归档日志时,报下列的错误:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 03/26/2012 00:19:36
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06004: ORACLE error from recovery catalog database: ORA-02396: exceeded maximum idle time, please connect again
ORACLE error from recovery catalog database: ORA-01012: not logged on
Process ID: 4060
Session ID: 24 Serial number: 23229
原因:
ORA-02396最有可能是 profile(with IDLE_TIME)导致的,该profile是指 Recovery Catalog 中的catalog owner
当执行rman备份的时候, rman 跟 Recovery Catalog 极少甚至不通信。
只有当rman备份完成后,相关的信息被从控制文件同步到 Recovery Catalog ,此时,rman 尝试更新 Recovery Catalog ,然后错误就产生了。
rman备份用的时间超过了 the catalog user's profile 中定义的idle_time,因此错误就出现了。
解决方案:
检查recovery catalog owner 是否在使用 IDLE_TIME 的profile。 如果使用了,禁用掉或者增大idle_time到更大的值
SQL> select * from dba_profiles where resource_name='IDLE_TIME';
SQL> select profile from dba_users where username='<USERNAME OF CATALOG OWNER>';
If the profile of the user matches the profile with a IDLE_TIME <> UNLIMITED, you should consider using a different profile for this user with IDLE_TIME=UNLIMITED.
SQL> alter user xx PROFILE < name of a profile> with IDLE_TIME=UNLIMITED >
参考原文:
RMAN backup faling with ORA-02396: exceeded maximum idle time, please connect again (Doc ID 1446182.1)
适用于:
Oracle Server - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
症状:
rman 在备份db和归档日志时,报下列的错误:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 03/26/2012 00:19:36
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06004: ORACLE error from recovery catalog database: ORA-02396: exceeded maximum idle time, please connect again
ORACLE error from recovery catalog database: ORA-01012: not logged on
Process ID: 4060
Session ID: 24 Serial number: 23229
原因:
ORA-02396最有可能是 profile(with IDLE_TIME)导致的,该profile是指 Recovery Catalog 中的catalog owner
当执行rman备份的时候, rman 跟 Recovery Catalog 极少甚至不通信。
只有当rman备份完成后,相关的信息被从控制文件同步到 Recovery Catalog ,此时,rman 尝试更新 Recovery Catalog ,然后错误就产生了。
rman备份用的时间超过了 the catalog user's profile 中定义的idle_time,因此错误就出现了。
解决方案:
检查recovery catalog owner 是否在使用 IDLE_TIME 的profile。 如果使用了,禁用掉或者增大idle_time到更大的值
SQL> select * from dba_profiles where resource_name='IDLE_TIME';
SQL> select profile from dba_users where username='<USERNAME OF CATALOG OWNER>';
If the profile of the user matches the profile with a IDLE_TIME <> UNLIMITED, you should consider using a different profile for this user with IDLE_TIME=UNLIMITED.
SQL> alter user xx PROFILE < name of a profile> with IDLE_TIME=UNLIMITED >
相关文章推荐
- 【翻译自mos文章】rman 备份时报:ORA-02396: exceeded maximum idle time
- ORA-02396: exceeded maximum idle time, please connect again的原因
- ORA-02396: exceeded maximum idle time, please connect again
- GoldenGate进程 abend,报错为OGG-00868 ORA-02396: Exceeded Maximum Idle Time, Please Connect Again
- ORA-02396: exceeded maximum idle time, please connect again
- GoldenGate过程 abend,报错OGG-00868 ORA-02396: Exceeded Maximum Idle Time, Please Connect Again
- ORA-02396: exceeded maximum idle time, please connect again的原因
- 【翻译自mos文章】在10g中,当发生ORA-00020时,sqlplus登陆会报“connected to an idle instance”
- 【翻译自mos文章】在10g中,当发生ORA-00020时,sqlplus登陆会报“connected to an idle instance”
- 【翻译自mos文章】为什么在备份过程中rman不使用unused block 压缩功能
- 【翻译自mos文章】/dev/shm应该设置多大Oracle 实例启动时才能不报ORA-00845
- 【翻译自mos文章】rman 标准版和企业版的兼容性
- 【翻译自mos文章】Block Recovery使用增量备份么?
- 【翻译自mos文章】在Oracle 12c中建立用户--避免ORA-65096 or ORA-65049错误
- 【翻译自mos文章】在11gR2/12c 的GI中,ORA_CRS_HOME 环境变量必须被unset
- 【翻译自mos文章】shutdown normal 挂起 在ora_j00X进程上
- 【翻译自mos文章】在11gR2 rac环境中,文件系统使用率紧张,而且lsof显示有非常多oraagent_oracle.l10 (deleted)
- 【翻译自mos文章】运行utlpwdmg.sql之后报ORA-28003, ORA-20001, ORA-20002, ORA-20003, ORA-20004 错误
- 翻译mos文章rman复原的先决条件
- 循环执行sql语句时报 ORA-01000 maximum open cursors exceeded 超出打开游标的最大数的原因和解决方案