Oracle Standby FIX using RMAN Incremental Backup from Primary DB

 

When you don’t have an option other than doing incremental backup from Primary DB (when ARCH logs are gone from all places) below is the high-level DB steps to fix the Standby GAP

On Standby:

Get the current DB SCN number

SYS@myoradb> select to_char (current_scn) from v$database;
TO_CHAR(CURRENT_SCN)
---------------------------------
11411445224862      à  SCN to take Backup from
  

1. [Standby] Stop the managed standby apply process:
2. Shut down standby
3. start RMAN incremental backup from source (primary OR standby)
   RMAN> Backup as compressed backupset incremental from scn 11411445224862 database format '/u01/app/oracle/RMAN_INC/ForStandby_%U' tag 'FORSTANDBY';
4. backup control file from source
   backup current controlfile for standby format '/u01/app/oracle/RMAN_INC/TRGDB_ForStandbyCTRL.bck';
5. SCP backup pieces to Standby Server
   oracle@SRCHOST testdb > nohup scp TRGHOST:/u01/app/oracle/RMAN_INC/ForStandby_6091 . > Nohup_6091.log &
6. [on standby] shut down DB and copy standby control file to location specified in standby
• Backup existing control file and replace with primary control file
7. mount standby DB from only 1 NODE
   RMAN> alter database mount;

       8 . Catalog all backup files with RMAN and start recover
             RMAN> catalog start with '/u01/app/oracle/TESTDB_standby_';
             RMAN> recover database;

             SYS@myoradb> select thread#, low_sequence#, high_sequence# from v$archive_gap;

 

 For Standby GAP fix using DB service :
https://chandu208.blogspot.com/2023/06/refresh-19c-physical-standby-database.html

PL/SQL package DBNAME.DBMS_RCVCAT version 19.06.00.00. in RCVCAT database is not current

 
 
 
When trying to connect to catalog database from rman I am getting below error
 
 
HOSTNAME:dbname:/home/oracle $ rman target /
 
Recovery Manager: Release 19.0.0.0.0 - Production on Tue Jun 14 11:50:16 2022
Version 19.9.0.0.0
 
Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.
 
connected to target database: DBNAME (DBID=3401445687)
 
 
RMAN> connect catalog user/pass@catalogdb
 
connected to recovery catalog database
PL/SQL package DBNAME_EXA_RMAN.DBMS_RCVCAT version 19.06.00.00. in RCVCAT database is not current
PL/SQL package DBNAME_EXA_RMAN.DBMS_RCVMAN version 19.06.00.00 in RCVCAT database is not current
 
 

Reason :

 There is a version mismatch between the RMAN-executable and the RMAN-catalog SCHEMA

Solution :
 
HOSTNAME:dbname:/home/oracle $ rman target /
 
Recovery Manager: Release 19.0.0.0.0 - Production on Tue Jun 14 11:50:16 2022
Version 19.9.0.0.0
 
Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.
 
connected to target database: DBNAME (DBID=3401445687)
 
 
RMAN> connect catalog user/pass@catalogdb
 
connected to recovery catalog database
PL/SQL package DBNAME_EXA_RMAN.DBMS_RCVCAT version 19.06.00.00. in RCVCAT database is not current
PL/SQL package DBNAME_EXA_RMAN.DBMS_RCVMAN version 19.06.00.00 in RCVCAT database is not current
 
RMAN>
 
RMAN> upgrade catalog;
 
recovery catalog owner is DBNAME_EXA_RMAN
enter UPGRADE CATALOG command again to confirm catalog upgrade
 
-- give same command again
 
RMAN> upgrade catalog;
 
recovery catalog upgraded to version 19.09.00.00.00
DBMS_RCVMAN package upgraded to version 19.09.00.00
DBMS_RCVCAT package upgraded to version 19.09.00.00.
 
RMAN> exit
 
 
Refer:
 
Pl/Sql Package Rman.Dbms_rcvcat Version xxxxx In Rcvcat Database Is Not Current (Doc ID 1365435.1)

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

When trying to delete Database archivelog where goldengate in running using rman i see below Warning  message.

RMAN> Delete archivelog all completed before  'SYSDATE-3';

released channel: ORA_DISK_1

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=2907 device type=DISK

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

archived log file name=+RECO/TESTDB/ARCHIVELOG/2017_10_07/thread_1_seq_3435.12440.956737243 thread=1 sequence=3435

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

archived log file name=+RECO/TESTDB/ARCHIVELOG/2017_10_07/thread_1_seq_3436.12438.956746549 thread=1 sequence=3436

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

archived log file name=+RECO/TESTDB/ARCHIVELOG/2017_10_07/thread_1_seq_3437.12437.956746819 thread=1 sequence=3437

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

archived log file name=+RECO/TESTDB/ARCHIVELOG/2017_10_07/thread_1_seq_3438.12436.956746869 thread=1 sequence=3438

SQL> select capture_name, status, captured_scn, applied_scn, capture_type,STATUS_CHANGE_TIME from dba_capture;

CAPTURE_NAME                                                                                                                     STATUS   CAPTURED_SCN    APPLIED_SCN   CAPTURE_TY   STATUS_CHAN

------------------------------------------------------------------------------------------------------------------- -------- ------------ 

 ----------- ---------- -----------

OGG$CAP_ETESTDB                                                                                                                   ENABLED    3.3555E+11  3.3555E+11 LOCAL      27-JUN-2017

OGG$CAP_ETESTDBQ2                                                                                                                 ENABLED    3.5047E+11  3.5047E+11 LOCAL      13-NOV-2017

I see one of the OLD Extract process(ETESTDB) is registered and blocking archivelog deletion using RMAN which is not used any more so I need to delete that to resolve the issue

SQL> exec DBMS_CAPTURE_ADM.STOP_CAPTURE('OGG$CAP_ETESTDB');

  

^CBEGIN DBMS_CAPTURE_ADM.STOP_CAPTURE('OGG$CAP_ETESTDB'); END;

*

ERROR at line 1:

ORA-01013: user requested cancel of current operation

ORA-06512: at "SYS.DBMS_LOGREP_UTIL", line 1310

ORA-06512: at "SYS.DBMS_CAPTURE_ADM", line 90

ORA-06512: at line 1

Hanging here ..............so killed

GGSCI (ORACLEDEV01) 2> dblogin useridalias gguser_dev

ERROR: Unable to connect to database using user GGUSER. Please check privileges.

Unable to initialize database connection because of error ORA-00257: Archiver error. Connect AS SYSDBA only until resolved..

GGSCI (ORACLEDEV01) 3> dblogin useridalias gguser_dev

Successfully logged into database.

GGSCI (ORACLEDEV01 as GGUSER@TESTDB) 4> unregister extract ETESTDB database

2017-11-14 11:14:21  INFO    OGG-01750  Successfully unregistered EXTRACT ETESTDB from database.

GGSCI (ORACLEDEV01 as GGUSER@TESTDB) 5> exit

oracledev01:TESTDB:/home/oracle $ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Tue Nov 14 11:14:33 2017

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics

and Real Application Testing options

SQL> select capture_name, status, captured_scn, applied_scn, capture_type,STATUS_CHANGE_TIME from dba_capture;

CAPTURE_NAME

--------------------------------------------------------------------------------

STATUS   CAPTURED_SCN APPLIED_SCN CAPTURE_TY STATUS_CHAN

-------- ------------ ----------- ---------- -----------

OGG$CAP_ETESTDBQ2

ENABLED    3.5062E+11  3.5062E+11 LOCAL      13-NOV-2017

Refer Oracle Doc:

RMAN-08137: WARNING: Archived Log Not Deleted, Needed For Standby Or Upstream Capture Proces (Doc ID 1993799.1)

RMAN waiting for snapshot control file enqueue

oracledev.domain.com:DEMODB:/home/oracle $ . dbaenv

ORACLE_SID = [DEMODB] ? demodb

The Oracle base remains unchanged with value /opt/oracle

oracledev.domain.com:demodb:/home/oracle $ rman target /

Recovery Manager: Release 12.1.0.2.0 - Production on Tue Feb 28 08:54:29 2017

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

connected to target database: DEMODB (DBID=77281235)

RMAN> connect catalog demodb_rman/*******@rcv

connected to recovery catalog database

RMAN> show all for db_unique_name all;

waiting for snapshot control file enqueue

waiting for snapshot control file enqueue

waiting for snapshot control file enqueue

^C

user interrupt received

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of show command at 02/28/2017 09:13:52

RMAN-03014: implicit resync of recovery catalog failed

RMAN-03099: job cancelled at user request

RMAN> exit

Check ANY RMAN jobs running/hanging in the Database:

SQL> SELECT SID, SERIAL#,SOFAR,TOTALWORK, ROUND(SOFAR/TOTALWORK*100,2)  "%_COMPLETE",OPNAME,to_char(START_TIME, 'dd-mm-yy hh24:mi:ss') START_TIME FROM V$SESSION_LONGOPS WHERE OPNAME LIKE 'RMAN%'  AND OPNAME NOT LIKE '%aggregate%'   AND TOTALWORK != 0 AND SOFAR <> TOTALWORK;

no rows selected

SQL> select sid, CLIENT_INFO ch, seq#, event, state from v$session where program like '%rman%';

      SID CH                                                                     SEQ# EVENT                                                            STATE

---------- ---------------------------------------------------------------- ---------- ---------------------------------------------------------------- -------------------

       172 rman channel=dev_0                                                    61014 imm op                                                           WAITING

       433 rman channel=dev_1                                                    46223 SQL*Net message from client                                      WAITING

       446                                                                       16546 SQL*Net message from client                                      WAITING

       471                                                                       28962 SQL*Net message from client                                      WAITING

       509 rman channel=dev_2                                                    17665 SQL*Net message from client                                      WAITING

       536 rman channel=dev_3                                                    16948 SQL*Net message from client                                      WAITING

       563 rman channel=dev_4                                                     8144 SQL*Net message from client                                      WAITING

       588 rman channel=dev_5                                                    54329 SQL*Net message from client                                      WAITING

       615 rman channel=dev_6                                                    50208 SQL*Net message from client                                      WAITING

       641 rman channel=dev_7                                                    54811 SQL*Net message from client                                      WAITING

10 rows selected.

Need to kill all above SID's .......................

SQL> select SESSION_KEY,SESSION_RECID,START_TIME,END_TIME,STATUS from V$RMAN_BACKUP_JOB_DETAILS where STATUS='RUNNING';

SESSION_KEY   SESSION_RECID   START_TIM   END_TIME  STATUS

--------------- ------------- --------- ---------     -----------------------

        313           313    19-FEB-17   28-FEB-17    RUNNING

                               

SQL> col TIME_TAKEN_DISPLAY for a33

SQL> select session_key, command_id, status, time_taken_display from v$rman_backup_job_details where STATUS='RUNNING';

SESSION_KEY COMMAND_ID                        STATUS                  TIME_TAKEN_DISPLAY

----------- --------------------------------- ----------------------- ---------------------------------

        313 2017-02-19T18:00:16               RUNNING                 ###:19:04

SQL> select sid from v$rman_status where COMMAND_ID='2017-02-19T18:00:16';

       SID

----------

       446

       446

       446

SQL> select SID,serial#,username,osuser,status,machine,program  from v$session where sid=446 ;

       SID    SERIAL# USERNAME                       OSUSER                         STATUS   MACHINE                        PROGRAM

---------- ---------- ------------------------------ ------------------------------ -------- ------------------------------ ---------------------------------------

       446      35822 SYS                            oracle                         INACTIVE oracledev.domain.com          rman@oracledev.domain.com (TNS V1-V3)

                  

SQL> alter system kill session '446,35822' immediate;

System altered.

SQL> select session_key, command_id, status, time_taken_display from v$rman_backup_job_details where STATUS='RUNNING';

no rows selected

RMAN-04004: error from recovery catalog database: ORA-28040: No matching authentication protocol

My oracle database: 9i  on HP-UX

My Catalog database: 12c on RHEL 6

Today while taking RMAN backup from backup tool we are getting below error

[Major] From: ob2rman@myoradec01.domain.com"prod"  Time: 10/15/16 17:03:34

                The database reported error while performing requested operation.

RMAN-00571: ===========================================================

 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

 RMAN-00571: ===========================================================

 RMAN-04004: error from recovery catalog database: ORA-28040: No matching authentication protocol

I wanted to try connecting from the server to the catalog database

Myoradev01:prod:/opt/oracle/product/9.2.0.8.64/network/admin $ rman target /

Recovery Manager: Release 9.2.0.8.0 - 64bit Production

Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.

connected to target database: PROD (DBID=176732808)

RMAN> connect catalog prod_user/xxxx@rcvc

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-04004: error from recovery catalog database: ORA-28040: No matching authentication protocol

RMAN>

According to oracle 

 “Connections to a 12c database server can only be made from a 10.2 and later client.”

But if you make changes to sqlnet.ora on the catalog it will work, to do so go to catalog database and modify $ORACLE_HOME/network/admin/sqlnet.ora file as below

audbs1:rm:/opt/oracle/product/12.1.0.2.64/network/admin $ vi sqlnet.ora

AUTOMATIC_IPC=ON

SQLNET.INBOUND_CONNECT_TIMEOUT=0

SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8  à ADDED this Line

 Try to connect to catalog database again from 9i database

Myoradev01:prod:/opt/oracle/product/9.2.0.8.64/network/admin $ rman target /

Recovery Manager: Release 9.2.0.8.0 - 64bit Production

Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.

connected to target database: PROD (DBID=176732808)

RMAN> connect catalog prod_user/xxxx@rcvc

connected to recovery catalog database

Now I can able to connect and my Issue is resolved.

Refer:

RMAN Catalog (12c) Connection Failed For 9.2.0.6.0 Database (Doc ID 1922190.1)

RMAN-06613: Connect identifier for DB_UNIQUE_NAME not configured

Primary database: PRIMDB

Standby db unique name: PRIMDB_SB4

OS: RHEL6

Oracle database: 12.1.0.2

Catalog database:

Primary:

oradev8:primdb:/home/oracle $ rman target /

Recovery Manager: Release 12.1.0.2.0 - Production on Wed Nov 2 11:08:31 2016

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

connected to target database: PRIMDB (DBID=1183475863)

RMAN> connect catalog primdb_rman/primdbpr2010@rcv

connected to recovery catalog database

RMAN> configure db_unique_name 'PRIMDB_SB4' connect identifier 'PRIMDB_SB4';

new RMAN configuration parameters:

CONFIGURE DB_UNIQUE_NAME 'PRIMDB_SB4' CONNECT IDENTIFIER  'PRIMDB_SB4';

new RMAN configuration parameters are successfully stored

starting full resync of recovery catalog

full resync complete

RMAN> show all;

RMAN configuration parameters for database with db_unique_name PRIMDB are:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2555 DAYS;

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

CONFIGURE CONTROLFILE AUTOBACKUP ON;

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default

CONFIGURE DB_UNIQUE_NAME 'PRIMDB_SB4' CONNECT IDENTIFIER  'PRIMDB_SB4';

CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/product/12.1.0.2.64/dbs/snapcf_primdb.f'; # default

Standby:

orastandby8:primdb:/home/oracle $ rman target /

Recovery Manager: Release 12.1.0.2.0 - Production on Wed Nov 2 11:07:26 2016

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

connected to target database: PRIMDB (DBID=1183475863)

RMAN> connect catalog primdb_rman/primdbpr2010@rcv

connected to recovery catalog database

RMAN> resync catalog;

starting partial resync of recovery catalog

partial resync complete

RMAN> show all for db_unique_name all;

RMAN configuration parameters for database with db_unique_name PRIMDB are:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2555 DAYS;

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

CONFIGURE CONTROLFILE AUTOBACKUP ON;

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default

CONFIGURE DB_UNIQUE_NAME 'PRIMDB_SB4' CONNECT IDENTIFIER  'PRIMDB_SB4';

CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/product/12.1.0.2.64/dbs/snapcf_primdb.f'; # default

RMAN configuration parameters for database with db_unique_name PRIMDB_SB4 are:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2555 DAYS;

CONFIGURE BACKUP OPTIMIZATION ON;

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

CONFIGURE CONTROLFILE AUTOBACKUP ON;

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default

CONFIGURE DB_UNIQUE_NAME 'PRIMDB_SB4' CONNECT IDENTIFIER  'PRIMDB_SB4';

CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/product/12.1.0.2.64/dbs/snapcf_primdb.f'; # default

UNREGISTER db unique name:

If you want to remove DB_UNIQUE_NAME from show all, Connect to target and catalog and use below command

RMAN> unregister DB_UNIQUE_NAME 'db_unique_name';

database db_unique_name is "xxxx", db_name is "xxxx" and DBID is 771234705

Want to unregister the database with target db_unique_name (enter YES or NO)? yes

database with db_unique_name xxxxxx unregistered from the recovery catalog

Reference:

RMAN-06613: Connect identifier for DB_UNIQUE_NAME not configured (Doc ID 1598653.1)

Recovery Writer (RVWR) is stuck until more space is available in the recovery area.

Today I got an alert for My OMS is down and when I checked the oem url I see OMS down message.

[oracle@OMS_SERVER bin]$ ./emctl status oms

Oracle Enterprise Manager Cloud Control 13c Release 2

Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.

WebTier is Up

Oracle Management Server is Down

JVMD Engine is Down

BI Publisher Server is Up

Checked OMS repository database(EMREPO) and i see database and listener is up and running fine but found below error in alert log…………

*************************************************************

Unable to allocate flashback log of 6377 blocks from

current recovery area of size 32212254720 bytes.

Recovery Writer (RVWR) is stuck until more space

is available in the recovery area.

recovery area is full, presence of a guaranteed

restore point and no reusable flashback logs.

Mon Nov 07 10:51:46 2016

*************************************************************

SQL> select space_limit/1024/1024/1024 maxGB,space_used/1024/1024/1024 usedGB from v$recovery_file_dest;

     MAXGB     USEDGB

---------- ----------

        30 29.9878693

SQL> SELECT FILE_TYPE "Type",PERCENT_SPACE_USED "% Used",PERCENT_SPACE_RECLAIMABLE "% Reclaim",

NUMBER_OF_FILES "# Files" FROM V$FLASH_RECOVERY_AREA_USAGE;

Type                                                                      % Used  % Reclaim    # Files

--------------------------------------------------------------------- ---------- ---------- ----------

CONTROL FILE                                                                   0          0          0

REDO LOG                                                                       0          0          0

ARCHIVED LOG                                                                   0          0          0

BACKUP PIECE                                                                 .06        .06          1

IMAGE COPY                                                                     0          0          0

FLASHBACK LOG                                                               99.9          0        154

FOREIGN ARCHIVED LOG                                                           0          0          0

AUXILIARY DATAFILE COPY                                                        0          0          0

8 rows selected.

SQL> show parameter db_recovery

NAME                                       TYPE                                                                                               VALUE

------------------------------------ -----------------------------------------------------------------------------   ------

db_recovery_file_dest                string                                                                                           /opt/oem/u20

db_recovery_file_dest_size           big integer                                                                                      30G

SQL> SELECT NAME, SCN, TIME, DATABASE_INCARNATION#, GUARANTEE_FLASHBACK_DATABASE, STORAGE_SIZE FROM V$RESTORE_POINT;

 NAME                                     SCN TIME                                         DATABASE_INCARNATION# GUARANTEE STORAGE_SIZE

--------------------------------- ---------- -------------------------------------------- --------------------- --------- ------------

EMREPO_BEFORE_UPGRADE13C          3.1001E+11 27-OCT-16 11.04.22.000000000 AM                                  2 YES         3.2181E+10

Now, I remember it is because of the Grantee Restore point which I have created during my recent OMS upgrade and now I can drop this since it’s been so many days and everything looks good.

SQL> DROP RESTORE POINT EMREPO_BEFORE_UPGRADE13C;

Restore point dropped.

SQL>

SQL> SELECT NAME, SCN, TIME, DATABASE_INCARNATION#, GUARANTEE_FLASHBACK_DATABASE, STORAGE_SIZE FROM V$RESTORE_POINT;

no rows selected

SQL> select space_limit/1024/1024/1024 maxGB,space_used/1024/1024/1024 usedGB from v$recovery_file_dest;

     MAXGB     USEDGB

---------- ----------

        30 .651931763

                               

[oracle@OMS_SERVER bin]$ ./emctl start oms

Oracle Enterprise Manager Cloud Control 13c Release 2

Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.

Starting Oracle Management Server...

WebTier Successfully Started

Oracle Management Server Already Started

Oracle Management Server is Up

JVMD Engine is Up

Starting BI Publisher Server ...

BI Publisher Server Already Started

BI Publisher Server is Up

Now I see my OEM url is working fine…………….