Friday, September 15, 2017

catalog database resync failed after applying the PSU patch

Recovery Manager: Release 11.2.0.4.0 - Production on Thu Sep 14 11:14:59 2017

Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

connected to target database: DB_name (DBID=4129713203)
connected to recovery catalog database
PL/SQL package rman_user.DBMS_RCVCAT version 11.01.00.07 in RCVCAT database is too old

RMAN> upgrade catalog;

recovery catalog owner is rman_user
enter UPGRADE CATALOG command again to confirm catalog upgrade

RMAN> upgrade catalog;

recovery catalog upgraded to version 11.02.00.04
DBMS_RCVMAN package upgraded to version 11.02.00.04
DBMS_RCVCAT package upgraded to version 11.02.00.04

RMAN> show all;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 09/14/2017 11:16:30
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 09/14/2017 11:16:30
ORA-01403: no data found

RMAN> register database;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 09/14/2017 11:16:49
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 09/14/2017 11:16:49
ORA-01403: no data found


   Root cause for the issue:
just got the error after DB upgrade to 11204 and it throws the error.even when we unregistered the db ,it did not give any result.
just looked the database and found the PSU on $ORACLE_HOME applied while the database open.

Solution:
just  do the clean DB restart and it will resolve issue.

2 comments:

  1. This comment has been removed by the author.

    ReplyDelete
  2. i just faced this issue just now. fixed it after db restart.. :) weird issue.. thanks for help.. :)

    ReplyDelete