{"id":52481,"date":"2022-09-28T13:48:15","date_gmt":"2022-09-28T13:48:15","guid":{"rendered":"https:\/\/dbtut.com\/?p=52481"},"modified":"2022-09-28T13:49:08","modified_gmt":"2022-09-28T13:49:08","slug":"creating-recovery-catalog","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/","title":{"rendered":"Creating Recovery Catalog"},"content":{"rendered":"<p>There&#8217;s a need to creating a Recovery Catalog so that the backups taken from Primay or Physical Standby database can be used among each other.<\/p>\n<p>Oracle best recommended also recommends that the server where the Recovery Catalog will be different from the servers in the Data Guard Environment.<\/p>\n<h4>Let&#8217;s Test<\/h4>\n<p>1. We connect to SQLPLUS on the server to be used for Recovery Catalog.<\/p>\n<pre class=\"lang:default decode:true \">[oracle@primary admin]$ sqlplus sys\/Passw0rd4@broker as sysdba\r\n\r\nSQL*Plus: Release 12.1.0.2.0 Production on Mon Feb 13 15:27:34 2017\r\n\r\nCopyright (c) 1982, 2014, Oracle.  All rights reserved.\r\n\r\n\r\nConnected to:\r\nOracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production\r\nWith the Partitioning, OLAP, Advanced Analytics and Real Application Testing options<\/pre>\n<p>2. We check if the connection is correct.<\/p>\n<pre class=\"lang:default decode:true \">[Primary] SQL&gt; show parameter name\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ncell_offloadgroup_name               string\r\ndb_file_name_convert                 string\r\ndb_name                              string      broker\r\ndb_unique_name                       string      broker\r\nglobal_names                         boolean     FALSE\r\ninstance_name                        string      broker\r\nlock_name_space                      string\r\nlog_file_name_convert                string\r\npdb_file_name_convert                string\r\nprocessor_group_name                 string\r\nservice_names                        string      broker\r\n<\/pre>\n<p>3. The current datafiles in the catalog server are queried.<\/p>\n<pre class=\"lang:default decode:true \">[Primary] SQL&gt; select file_name from dba_data_files;\r\n\r\nFILE_NAME\r\n--------------------------------------------------------------------------------\r\n\/u01\/app\/oracle\/oradata\/broker\/system01.dbf\r\n\/u01\/app\/oracle\/oradata\/broker\/sysaux01.dbf\r\n\/u01\/app\/oracle\/oradata\/broker\/example01.dbf\r\n\/u01\/app\/oracle\/oradata\/broker\/users01.dbf\r\n\/u01\/app\/oracle\/oradata\/broker\/undotbs01.dbf\r\n<\/pre>\n<p>4. We create a new tablespace to hold the Recovery Catalog information.<\/p>\n<pre class=\"lang:default decode:true \">[Primary] SQL&gt; create tablespace rcts datafile '\/u01\/app\/oracle\/oradata\/broker\/rcts01.dbf' size 30M autoextend on;\r\n\r\nTablespace created.\r\n<\/pre>\n<p>5. We create a Recovery Catalog user.<\/p>\n<pre class=\"lang:default decode:true \">[Primary] SQL&gt; create user rcowner identified by \"rcowner\" default tablespace rcts quota unlimited on rcts;\r\n\r\nUser created.\r\n<\/pre>\n<p>6. The RECOVERY_CATALOG_OWNER Role is assigned to the user.<\/p>\n<pre class=\"lang:default decode:true \">[Primary] SQL&gt; grant recovery_catalog_owner to rcowner;\r\n\r\nGrant succeeded.\r\n<\/pre>\n<p>7. We connect to the Catalog database with RMAN.<\/p>\n<pre class=\"lang:default decode:true \">[oracle@primary admin]$ rman\r\n\r\nRecovery Manager: Release 12.1.0.2.0 - Production on Mon Feb 13 15:33:58 2017\r\n\r\nCopyright (c) 1982, 2014, Oracle and\/or its affiliates.  All rights reserved.\r\n\r\nRMAN&gt; connect catalog rcowner\/rcowner@broker\r\n\r\nconnected to recovery catalog database\r\n<\/pre>\n<p>8. The catalog is created.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; create catalog;\r\n\r\nrecovery catalog created\r\n<\/pre>\n<p>9. We connect the primary database to be TARGET.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; connect target 'sys\/Passw0rd4@primary as sysdba'\r\n\r\nconnected to target database: PRIMARY (DBID=1772883609)\r\n<\/pre>\n<p>10. The primary database is REGISTERed to the catalog.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; register database;\r\n\r\ndatabase registered in recovery catalog\r\nstarting full resync of recovery catalog\r\nfull resync complete\r\n<\/pre>\n<p>With this operation, it copies the information in the Control File of the RMAN Primary database to the Recovery Catalog tables. Backup information is now in both Control File and Recovery Catalog.<\/p>\n<p>Thus, in case of a problem in Control File, I will be able to access Control File information from Recovery Catalog.<\/p>\n<p>At this stage I do not REGISTER the Physical Standby database. In the future, when using CONFIGURE DB_UNIQUE_NAME parameter, this database will be REGISTER automatically.<\/p>\n<p>11. All databases registered to Recovery Catalog are listed.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; list db_unique_name of database;\r\n\r\n\r\nList of Databases\r\nDB Key  DB Name  DB ID            Database Role    Db_unique_name\r\n------- ------- ----------------- ---------------  ------------------\r\n1       PRIMARY  1772883609       PRIMARY          PRIMARY     \r\n<\/pre>\n<p>12. Tablespaces of primary database are listed.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; report schema for db_unique_name 'primary';\r\n\r\nReport of database schema for database with db_unique_name PRIMARY\r\n\r\nList of Permanent Datafiles\r\n===========================\r\nFile Size(MB) Tablespace           RB segs Datafile Name\r\n---- -------- -------------------- ------- ------------------------\r\n1    820      SYSTEM               YES     \/u01\/app\/oracle\/oradata\/primary\/system01.dbf\r\n3    860      SYSAUX               NO      \/u01\/app\/oracle\/oradata\/primary\/sysaux01.dbf\r\n4    150      UNDOTBS1             YES     \/u01\/app\/oracle\/oradata\/primary\/undotbs01.dbf\r\n5    1243     EXAMPLE              NO      \/u01\/app\/oracle\/oradata\/primary\/example01.dbf\r\n6    5        USERS                NO      \/u01\/app\/oracle\/oradata\/primary\/users01.dbf\r\n\r\nList of Temporary Files\r\n=======================\r\nFile Size(MB) Tablespace           Maxsize(MB) Tempfile Name\r\n---- -------- -------------------- ----------- --------------------\r\n1    197      TEMP                 32767       \/u01\/app\/oracle\/oradata\/primary\/temp01.dbf\r\n<\/pre>\n<p>13. All archive logs in the primary database are listed.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; list archivelog all for db_unique_name 'primary';\r\n\r\nList of Archived Log Copies for database with db_unique_name\r\nBOSTON\r\n================================================================\r\n=====\r\nKey Thrd Seq S Low Time\r\n------- ---- ------- - ---------\r\n...\r\n\r\n358     1    6       A 13-FEB-17\r\n        Name: \/u01\/app\/oracle\/recovery_area\/PRIMARY\/archivelog\/2017_02_13\/o1_mf_1_6_db2v2vw6_.arc\r\n\r\n359     1    7       A 13-FEB-17\r\n        Name: \/u01\/app\/oracle\/recovery_area\/PRIMARY\/archivelog\/2017_02_13\/o1_mf_1_7_db2v3byy_.arc\r\n\r\n360     1    8       A 13-FEB-17\r\n        Name: \/u01\/app\/oracle\/recovery_area\/PRIMARY\/archivelog\/2017_02_13\/o1_mf_1_8_db2v3dmn_.arc\r\n\r\n361     1    9       A 13-FEB-17\r\n        Name: \/u01\/app\/oracle\/recovery_area\/PRIMARY\/archivelog\/2017_02_13\/o1_mf_1_9_db2v3wkl_.arc\r\n\r\n362     1    10      A 13-FEB-17\r\n        Name: \/u01\/app\/oracle\/recovery_area\/PRIMARY\/archivelog\/2017_02_13\/o1_mf_1_10_db2v41w4_.arc\r\n\r\n363     1    11      A 13-FEB-17\r\n        Name: \/u01\/app\/oracle\/recovery_area\/PRIMARY\/archivelog\/2017_02_13\/o1_mf_1_11_db2v4q0q_.arc\r\n\r\n364     1    12      A 13-FEB-17\r\n        Name: \/u01\/app\/oracle\/recovery_area\/PRIMARY\/archivelog\/2017_02_13\/o1_mf_1_12_db2v7xpg_.arc\r\n\r\n365     1    13      A 13-FEB-17\r\n        Name: \/u01\/app\/oracle\/recovery_area\/PRIMARY\/archivelog\/2017_02_13\/o1_mf_1_13_db34sy4t_.arc\r\n<\/pre>\n<p>14. All configurable RMAN parameters for the primary database are listed.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; show all for db_unique_name 'primary';\r\n\r\nRMAN configuration parameters for database with db_unique_name PRIMARY are:\r\nCONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default\r\nCONFIGURE BACKUP OPTIMIZATION OFF; # default\r\nCONFIGURE DEFAULT DEVICE TYPE TO DISK; # default\r\nCONFIGURE CONTROLFILE AUTOBACKUP OFF; # default\r\nCONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default\r\nCONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default\r\nCONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\r\nCONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\r\nCONFIGURE MAXSETSIZE TO UNLIMITED; # default\r\nCONFIGURE ENCRYPTION FOR DATABASE OFF; # default\r\nCONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default\r\nCONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default\r\nCONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default\r\nCONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default\r\nCONFIGURE SNAPSHOT CONTROLFILE NAME TO '\/u01\/app\/oracle\/product\/12.1.0\/db_1\/dbs\/snapcf_primary.f'; # default<\/pre>\n<p>15. We are editing the Backup Retention Policy.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; configure retention policy to recovery window of 7 days;\r\n\r\nnew RMAN configuration parameters:\r\nCONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;\r\nnew RMAN configuration parameters are successfully stored\r\nstarting full resync of recovery catalog\r\nfull resync complete\r\n<\/pre>\n<p>16. We determine when archive logs will be deleted.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; configure archivelog deletion policy to applied on all standby;\r\n\r\nnew RMAN configuration parameters:\r\nCONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;\r\nnew RMAN configuration parameters are successfully stored\r\nstarting full resync of recovery catalog\r\nfull resync complete\r\n<\/pre>\n<p>17. Which service to use is specified in TNSNAMES to connect to the primary database.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; configure db_unique_name 'primary' connect identifier 'primary';\r\n\r\nnew RMAN configuration parameters:\r\nCONFIGURE DB_UNIQUE_NAME 'primary' CONNECT IDENTIFIER  'primary';\r\nnew RMAN configuration parameters are successfully stored\r\nstarting full resync of recovery catalog\r\nfull resync complete\r\n<\/pre>\n<p>When RMAN will RESYNC the Databases in the Catalog, it must be connected to the databases remotely. For this reason, it is necessary to specify which service to connect to these databases.<\/p>\n<p>18. In order to connect to the Physical Standby database, which service will be used is specified in TNSNAMES.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; configure db_unique_name 'physical' connect identifier 'physical';\r\n\r\nnew RMAN configuration parameters:\r\nCONFIGURE DB_UNIQUE_NAME 'physical' CONNECT IDENTIFIER  'physical';\r\nnew RMAN configuration parameters are successfully stored\r\nstarting full resync of recovery catalog\r\nfull resync complete\r\n<\/pre>\n<p>19. We list the databases connected to the catalog.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; list db_unique_name of database;\r\n\r\n\r\nList of Databases\r\nDB Key  DB Name  DB ID            Database Role    Db_unique_name\r\n------- ------- ----------------- ---------------  ------------------\r\n1       PRIMARY  1772883609       PRIMARY          PRIMARY             \r\n1       PRIMARY  1772883609       STANDBY          PHYSICAL \r\n<\/pre>\n<p>Although there is no REGISTER operation for the Physical Standby Database, 2 databases appear in the catalog. The reason for this is that as we said before, only the REGISTER operation of the Primary database is mandatory.<\/p>\n<p>Standby Databases are automatically REGISTERed with Configure parameters.<\/p>\n<p>20. We list the Tablespaces of the Physical Standby Database.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; report schema for db_unique_name 'physical';\r\n\r\nReport of database schema for database with db_unique_name PHYSICAL\r\n\r\nList of Permanent Datafiles\r\n===========================\r\nFile Size(MB) Tablespace           RB segs Datafile Name\r\n---- -------- -------------------- ------- ------------------------\r\n1    820      SYSTEM               YES     \r\n3    860      SYSAUX               NO      \r\n4    150      UNDOTBS1             YES     \r\n5    1243     EXAMPLE              NO      \r\n6    5        USERS                NO  \r\n<\/pre>\n<p>21. Connects to the Physical Standby database as TARGET.<\/p>\n<pre class=\"lang:default decode:true \">[oracle@primary admin]$ rman target sys\/Passw0rd4@physical catalog rcowner\/rcowner@broker\r\n\r\nRecovery Manager: Release 12.1.0.2.0 - Production on Mon Feb 13 16:03:36 2017\r\n\r\nCopyright (c) 1982, 2014, Oracle and\/or its affiliates.  All rights reserved.\r\n\r\nconnected to target database: PRIMARY (DBID=1772883609)\r\nconnected to recovery catalog database\r\n<\/pre>\n<p>22. We list the current RMAN parameters for the Physical database.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; show all for db_unique_name 'physical';\r\n\r\nRMAN configuration parameters for database with db_unique_name PHYSICAL are:\r\nCONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;\r\nCONFIGURE BACKUP OPTIMIZATION OFF; # default\r\nCONFIGURE DEFAULT DEVICE TYPE TO DISK; # default\r\nCONFIGURE CONTROLFILE AUTOBACKUP OFF; # default\r\nCONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default\r\nCONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default\r\nCONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\r\nCONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\r\nCONFIGURE MAXSETSIZE TO UNLIMITED; # default\r\nCONFIGURE ENCRYPTION FOR DATABASE OFF; # default\r\nCONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default\r\nCONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default\r\nCONFIGURE DB_UNIQUE_NAME 'primary' CONNECT IDENTIFIER  'primary';\r\nCONFIGURE DB_UNIQUE_NAME 'physical' CONNECT IDENTIFIER  'physical';\r\nCONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default\r\nCONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;\r\nCONFIGURE SNAPSHOT CONTROLFILE NAME TO '\/u01\/app\/oracle\/product\/12.1.0\/db_1\/dbs\/snapcf_physical.f'; # default\r\n<\/pre>\n<p>23. We edit the Backup optimization parameter.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; configure backup optimization on;\r\n\r\nnew RMAN configuration parameters:\r\nCONFIGURE BACKUP OPTIMIZATION ON;\r\nnew RMAN configuration parameters are successfully stored\r\n\r\n\r\nSadece Catalog' a ba\u011flan\u0131l\u0131p bu parametre \u00e7al\u0131\u015ft\u0131r\u0131lmak istendi\u011finde a\u015fa\u011f\u0131daki hata al\u0131n\u0131r. \r\n\r\nRMAN-00571: ===========================================================\r\nRMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============\r\nRMAN-00571: ===========================================================\r\nRMAN-03002: failure of configure command at 02\/15\/2017 09:15:46\r\nRMAN-06171: not connected to target database\r\n<\/pre>\n<p>The way to resolve this error is to either connect to the database where the parameter will be edited as TARGET as specified, or to set the DBID. We set the DBID as follows.<\/p>\n<p>The DBID is learned.<\/p>\n<pre class=\"lang:default decode:true \">[Primary] SQL&gt; select DBID from v$database;\r\n\r\n      DBID\r\n----------\r\n1772883609\r\n<\/pre>\n<p>It connects to the catalog.<\/p>\n<pre class=\"lang:default decode:true \">[oracle@primary ~]$ rman\r\n\r\nRecovery Manager: Release 12.1.0.2.0 - Production on Wed Feb 15 09:18:48 2017\r\n\r\nCopyright (c) 1982, 2014, Oracle and\/or its affiliates.  All rights reserved.\r\n\r\nRMAN&gt; connect catalog rcowner\/rcowner@broker\r\n<\/pre>\n<p>The DBID is set.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; set dbid 1772883609;\r\n\r\nexecuting command: SET DBID\r\ndatabase name is \"PRIMARY\" and DBID is 1772883609<\/pre>\n<p>A parameter is set for testing purposes.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; configure controlfile autobackup on for db_unique_name 'primary';\r\n\r\nnew RMAN configuration parameters:\r\nCONFIGURE CONTROLFILE AUTOBACKUP ON;\r\nnew RMAN configuration parameters are successfully stored\r\n<\/pre>\n<p>The value of the parameter is displayed.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; show all for db_unique_name 'primary';\r\n\r\nRMAN configuration parameters for database with db_unique_name PRIMARY are:\r\nCONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;\r\nCONFIGURE BACKUP OPTIMIZATION OFF; # default\r\nCONFIGURE DEFAULT DEVICE TYPE TO DISK; # default\r\nCONFIGURE CONTROLFILE AUTOBACKUP ON;\r\nCONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default\r\nCONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\r\nCONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\r\nCONFIGURE MAXSETSIZE TO UNLIMITED; # default\r\nCONFIGURE ENCRYPTION FOR DATABASE OFF; # default\r\nCONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default\r\nCONFIGURE DB_UNIQUE_NAME 'primary' CONNECT IDENTIFIER  'primary';\r\nCONFIGURE DB_UNIQUE_NAME 'physical' CONNECT IDENTIFIER  'physical';\r\nCONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default\r\nCONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;\r\n<\/pre>\n<p>We query whether the parameter has changed in the other database in the Catalog.<\/p>\n<pre class=\"lang:default decode:true \">RMAN&gt; show all for db_unique_name 'physical';\r\n\r\nRMAN configuration parameters for database with db_unique_name PHYSICAL are:\r\nCONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;\r\nCONFIGURE BACKUP OPTIMIZATION ON;\r\nCONFIGURE DEFAULT DEVICE TYPE TO DISK; # default\r\nCONFIGURE CONTROLFILE AUTOBACKUP OFF; # default\r\nCONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default\r\nCONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\r\nCONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\r\nCONFIGURE MAXSETSIZE TO UNLIMITED; # default\r\nCONFIGURE ENCRYPTION FOR DATABASE OFF; # default\r\nCONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default\r\nCONFIGURE DB_UNIQUE_NAME 'primary' CONNECT IDENTIFIER  'primary';\r\nCONFIGURE DB_UNIQUE_NAME 'physical' CONNECT IDENTIFIER  'physical';\r\nCONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default\r\nCONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;\r\n<\/pre>\n<p>Although the DBIDs of the Primary and Physical Standby database are the same, I could not understand why only the Primary was changed.<\/p>\n<pre class=\"lang:default decode:true \">[Primary] SQL&gt; select dbid from v$database;\r\n\r\n      DBID\r\n----------\r\n1772883609\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Physical] SQL&gt; select dbid from v$database;\r\n\r\n      DBID\r\n----------\r\n1772883609\r\n<\/pre>\n<div class=\"pvc_clear\"><\/div>\n<p id=\"pvc_stats_52481\" class=\"pvc_stats all  \" data-element-id=\"52481\" style=\"\"><i class=\"pvc-stats-icon medium\" aria-hidden=\"true\"><svg aria-hidden=\"true\" focusable=\"false\" data-prefix=\"far\" data-icon=\"chart-bar\" role=\"img\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 512 512\" class=\"svg-inline--fa fa-chart-bar fa-w-16 fa-2x\"><path fill=\"currentColor\" d=\"M396.8 352h22.4c6.4 0 12.8-6.4 12.8-12.8V108.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v230.4c0 6.4 6.4 12.8 12.8 12.8zm-192 0h22.4c6.4 0 12.8-6.4 12.8-12.8V140.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v198.4c0 6.4 6.4 12.8 12.8 12.8zm96 0h22.4c6.4 0 12.8-6.4 12.8-12.8V204.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v134.4c0 6.4 6.4 12.8 12.8 12.8zM496 400H48V80c0-8.84-7.16-16-16-16H16C7.16 64 0 71.16 0 80v336c0 17.67 14.33 32 32 32h464c8.84 0 16-7.16 16-16v-16c0-8.84-7.16-16-16-16zm-387.2-48h22.4c6.4 0 12.8-6.4 12.8-12.8v-70.4c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v70.4c0 6.4 6.4 12.8 12.8 12.8z\" class=\"\"><\/path><\/svg><\/i> <img loading=\"lazy\" decoding=\"async\" width=\"16\" height=\"16\" alt=\"Loading\" src=\"https:\/\/dbtut.com\/wp-content\/plugins\/page-views-count\/ajax-loader-2x.gif\" border=0 \/><\/p>\n<div class=\"pvc_clear\"><\/div>\n","protected":false},"excerpt":{"rendered":"<p>There&#8217;s a need to creating a Recovery Catalog so that the backups taken from Primay or Physical Standby database can be used among each other. Oracle best recommended also recommends that the server where the Recovery Catalog will be different from the servers in the Data Guard Environment. Let&#8217;s Test 1. We connect to SQLPLUS &hellip;<\/p>\n<div class=\"pvc_clear\"><\/div>\n<p id=\"pvc_stats_52481\" class=\"pvc_stats all  \" data-element-id=\"52481\" style=\"\"><i class=\"pvc-stats-icon medium\" aria-hidden=\"true\"><svg aria-hidden=\"true\" focusable=\"false\" data-prefix=\"far\" data-icon=\"chart-bar\" role=\"img\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 512 512\" class=\"svg-inline--fa fa-chart-bar fa-w-16 fa-2x\"><path fill=\"currentColor\" d=\"M396.8 352h22.4c6.4 0 12.8-6.4 12.8-12.8V108.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v230.4c0 6.4 6.4 12.8 12.8 12.8zm-192 0h22.4c6.4 0 12.8-6.4 12.8-12.8V140.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v198.4c0 6.4 6.4 12.8 12.8 12.8zm96 0h22.4c6.4 0 12.8-6.4 12.8-12.8V204.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v134.4c0 6.4 6.4 12.8 12.8 12.8zM496 400H48V80c0-8.84-7.16-16-16-16H16C7.16 64 0 71.16 0 80v336c0 17.67 14.33 32 32 32h464c8.84 0 16-7.16 16-16v-16c0-8.84-7.16-16-16-16zm-387.2-48h22.4c6.4 0 12.8-6.4 12.8-12.8v-70.4c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v70.4c0 6.4 6.4 12.8 12.8 12.8z\" class=\"\"><\/path><\/svg><\/i> <img loading=\"lazy\" decoding=\"async\" width=\"16\" height=\"16\" alt=\"Loading\" src=\"https:\/\/dbtut.com\/wp-content\/plugins\/page-views-count\/ajax-loader-2x.gif\" border=0 \/><\/p>\n<div class=\"pvc_clear\"><\/div>\n","protected":false},"author":484,"featured_media":52482,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[4],"tags":[],"class_list":["post-52481","post","type-post","status-publish","format-standard","has-post-thumbnail","","category-oracle"],"aioseo_notices":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.9 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Creating Recovery Catalog - Database Tutorials<\/title>\n<meta name=\"description\" content=\"There&#039;s a need to creating a Recovery Catalog so that the backups taken from Primay or Physical Standby database can be used among each other\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Creating Recovery Catalog - Database Tutorials\" \/>\n<meta property=\"og:description\" content=\"There&#039;s a need to creating a Recovery Catalog so that the backups taken from Primay or Physical Standby database can be used among each other\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/\" \/>\n<meta property=\"og:site_name\" content=\"Database Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2022-09-28T13:48:15+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-09-28T13:49:08+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-28-164727.png\" \/>\n\t<meta property=\"og:image:width\" content=\"782\" \/>\n\t<meta property=\"og:image:height\" content=\"367\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Onur ARDAHANLI\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Onur ARDAHANLI\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/\"},\"author\":{\"name\":\"Onur ARDAHANLI\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\"},\"headline\":\"Creating Recovery Catalog\",\"datePublished\":\"2022-09-28T13:48:15+00:00\",\"dateModified\":\"2022-09-28T13:49:08+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/\"},\"wordCount\":512,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-28-164727.png\",\"articleSection\":[\"ORACLE\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/\",\"url\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/\",\"name\":\"Creating Recovery Catalog - Database Tutorials\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-28-164727.png\",\"datePublished\":\"2022-09-28T13:48:15+00:00\",\"dateModified\":\"2022-09-28T13:49:08+00:00\",\"description\":\"There's a need to creating a Recovery Catalog so that the backups taken from Primay or Physical Standby database can be used among each other\",\"breadcrumb\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#primaryimage\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-28-164727.png\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-28-164727.png\",\"width\":782,\"height\":367},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dbtut.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Creating Recovery Catalog\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/dbtut.com\/#website\",\"url\":\"https:\/\/dbtut.com\/\",\"name\":\"Database Tutorials\",\"description\":\"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux\",\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/dbtut.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/dbtut.com\/#organization\",\"name\":\"dbtut\",\"url\":\"https:\/\/dbtut.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"width\":223,\"height\":36,\"caption\":\"dbtut\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\",\"name\":\"Onur ARDAHANLI\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g\",\"caption\":\"Onur ARDAHANLI\"},\"url\":\"https:\/\/dbtut.com\/index.php\/author\/onurardahanli\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Creating Recovery Catalog - Database Tutorials","description":"There's a need to creating a Recovery Catalog so that the backups taken from Primay or Physical Standby database can be used among each other","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/","og_locale":"en_US","og_type":"article","og_title":"Creating Recovery Catalog - Database Tutorials","og_description":"There's a need to creating a Recovery Catalog so that the backups taken from Primay or Physical Standby database can be used among each other","og_url":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/","og_site_name":"Database Tutorials","article_published_time":"2022-09-28T13:48:15+00:00","article_modified_time":"2022-09-28T13:49:08+00:00","og_image":[{"width":782,"height":367,"url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-28-164727.png","type":"image\/png"}],"author":"Onur ARDAHANLI","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Onur ARDAHANLI","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#article","isPartOf":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/"},"author":{"name":"Onur ARDAHANLI","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6"},"headline":"Creating Recovery Catalog","datePublished":"2022-09-28T13:48:15+00:00","dateModified":"2022-09-28T13:49:08+00:00","mainEntityOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/"},"wordCount":512,"commentCount":0,"publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-28-164727.png","articleSection":["ORACLE"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/","url":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/","name":"Creating Recovery Catalog - Database Tutorials","isPartOf":{"@id":"https:\/\/dbtut.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#primaryimage"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-28-164727.png","datePublished":"2022-09-28T13:48:15+00:00","dateModified":"2022-09-28T13:49:08+00:00","description":"There's a need to creating a Recovery Catalog so that the backups taken from Primay or Physical Standby database can be used among each other","breadcrumb":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#primaryimage","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-28-164727.png","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/09\/Ekran-goruntusu-2022-09-28-164727.png","width":782,"height":367},{"@type":"BreadcrumbList","@id":"https:\/\/dbtut.com\/index.php\/2022\/09\/28\/creating-recovery-catalog\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dbtut.com\/"},{"@type":"ListItem","position":2,"name":"Creating Recovery Catalog"}]},{"@type":"WebSite","@id":"https:\/\/dbtut.com\/#website","url":"https:\/\/dbtut.com\/","name":"Database Tutorials","description":"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux","publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dbtut.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/dbtut.com\/#organization","name":"dbtut","url":"https:\/\/dbtut.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","width":223,"height":36,"caption":"dbtut"},"image":{"@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6","name":"Onur ARDAHANLI","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g","caption":"Onur ARDAHANLI"},"url":"https:\/\/dbtut.com\/index.php\/author\/onurardahanli\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/52481","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/users\/484"}],"replies":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/comments?post=52481"}],"version-history":[{"count":1,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/52481\/revisions"}],"predecessor-version":[{"id":52483,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/52481\/revisions\/52483"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media\/52482"}],"wp:attachment":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media?parent=52481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/categories?post=52481"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/tags?post=52481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}