Rman backup time: ORA-02396: exceededmaximumidletime

Rman backup time: ORA-02396: exceededmaximumidletime

Rman backup times: ORA-02396: exceeded maximum idle time

Reference Original:
RMAN backup faling with ORA-02396: exceeded maximum idle time, please connect again (Doc ID 1446182.1)

Applicable:
Oracle Server-Enterprise Edition-Version 11.2.0.1 and later
Information in this document applies to any platform.

Symptoms:
Rman reports the following errors when backing up db and archiving logs:
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

Cause:
ORA-02396 is most likely caused by profile (with IDLE_TIME), which is the Catalog owner in the Recovery catalog

When rman backup is performed, rman and Recovery Catalog seldom or even do not communicate.
Only when the rman backup is complete, the related information is synchronized from the control file to the Recovery Catalog. At this time, rman tries to update the Recovery Catalog and an error is generated.

The time used for rman backup exceeds the idle_time defined in the catalog user's profile, so an error occurs.

Solution:
Check whether the recovery catalog owner is using the IDLE_TIME profile. If it is used, disable or increase idle_time to a greater value.

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 shoshould 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>