De dataguard configuratie in dit artikel komt er als volgt uit te zien.
| ODA prim DB | ODA stby DB | |||
| node | aj007 | aj008 | aj001 | aj002 |
| database |
CRGS |
CRGSSB |
||
Het aanmaken van een active dataguard database op ODA wordt vanuit een backupgedaan. Hoe en wat van backup is in een ander artikel beschreven en wordt hier niet uitgelegd. Het backupreport is nodig om een input .json file te maken voor de restore. De backup is aangemaakt op de aj007, de eerste node van de ODA waar de primary database is aangemaakt.
[root@aj007 ~]# odacli describe-backupreport -i 0e6965c9-27ef-4c39-8a82-adb83d37e6fe
{
"id" : "0e6965c9-27ef-4c39-8a82-adb83d37e6fe",
"dbResId" : "40bf62e5-2af9-44c8-8994-8d098056fefc",
"tag" : "backup4DG",
"dbId" : "2431416426",
"dbName" : "CRGS",
"dbUniqueName" : "CRGS",
"backupType" : "Regular-L0",
"keepDays" : null,
"backupLocation" : "/backup_files_aj005/CRGS/orabackups/aj007-c/database/2431416426/CRGS/db",
"cfBackupHandle" : "/backup_files_aj005/CRGS/orabackups/aj007-c/database/2431416426/CRGS/db/c-2431416426-20230331-31",
"spfBackupHandle" : "/backup_files_aj005/CRGS/orabackups/aj007-c/database/2431416426/CRGS/db/c-2431416426-20230331-31",
"pitrTimeStamp" : "March 31, 2023 11:34:22 AM CEST",
"pitrSCN" : "4023538",
"resetLogsTimeStamp" : "March 28, 2023 14:09:50 PM CEST",
"resetLogsSCN" : "2617625",
"oraHomeVersion" : "19.16.0.0.220719",
"sqlPatches" : "34133642",
"backupLogLoc" : "/backup_files_aj005/CRGS/orabackups/aj007-c/database/2431416426/CRGS/rmanlog/2023-03-31/rman_backup_backup4DG_2023-03-31_11-33-16.0414.log",
"tdeWalletLoc" : null,
"dbConfigLoc" : "/backup_files_aj005/CRGS/orabackups/aj007-c/database/2431416426/CRGS/dbconfig/2023-03-31/DBCONFIG_backup4DG_2023-03-31_11-34-43.0358.tar.gz",
"name" : "Backup_Report_CRGS",
"createTime" : "March 31, 2023 11:33:13 AM CEST",
"state" : {
"status" : "CONFIGURED"
},
"updatedTime" : "March 31, 2023 11:33:13 AM CEST",
"backupReportLogDetail" : "/backup_files_aj005/CRGS/orabackups/aj007-c/database/2431416426/CRGS/rmandetaillogreport/2023-03-31/rman_list_backup_detail_backup4DG_2023-03-31_11-34-32.0984.log",
"dbInfo" : {
"dbClass" : "OLTP",
"dbType" : "RAC",
"dbShape" : "odb1",
"dbEdition" : "EE",
"dbStorage" : "ASM",
"dbRedundancy" : null,
"pdbName" : "PDB1",
"isCdb" : true
},
"dbDataSize" : "5174M",
"dbRedoSize" : "16410M",
"rmanBackupPieces" : "/backup_files_aj005/CRGS/orabackups/aj007-c/database/2431416426/CRGS/backuppieces/2023-03-31/backupPieces_backup4DG_40bf62e5-2af9-44c8-8994-8d098056fefc_20230331113442.json",
"compressionAlgo" : "BASIC",
"cpuPool" : null,
"numberOfCores" : null
}
[root@aj007 ~]#De 1ste node van de ODA waar de standby database aangemaakt wordt is deaj001. In het backupreport op de aj007 zagen we dat de backup files aangemaakt worden op aj007:/backup_files_aj005/CRGS en deze directory is via NFS geshared als aj001:/backup_files/CRGS. Dit zal uiteindelijk in PRD anders worden ingericht. Het idee is om een NFS share aan te maken naar een '3e locatie' ( dus niet op één van de ODA's in dit artikel) , waarbij deze dan met dezelfde naam op beide ODA's ge-mount worden.
Het aanmaken van een data guard database op een ODA gebeurt m.b.v. een restore (irestore eigenlijk), waarbij van een backupreport en .json file gemaakt wordt om als input voor de irestore tedienen. Hiervoor wordt gebruik gemaakt van het odacli describe-backreport commando, uitgevoerd als user root. met behulp van odacli describe-backreport --help kan achterhaald worden welke parameter nodig zijn. In dit geval is er gebruik gemaakt van de volgende parameters:
-i voor het ID van het backupreport .De output van dit commando schrijf je weg naar een .json file. Deze file moet terechtkomen op de node van waaruit de standby database aangemaakt wordt. In dit voorbeeld wordt de file in 2 stappen naar een shared folder verplaatst, omdat er iets niet in orde is met rechten en er geen tijd gestoken is om dit op te lossen. Kan dus sneller.
[root@aj007 ~]# odacli describe-backupreport -i 0e6965c9-27ef-4c39-8a82-adb83d37e6fe -j > /backup_files_aj005/CRGS/burep_CRGS.json
-bash: /backup_files_aj005/CRGS/burep_CRGS.json: Permission denied
[root@aj007 ~]# odacli describe-backupreport -i 0e6965c9-27ef-4c39-8a82-adb83d37e6fe -j > /tmp/burep_CRGS.json
[root@aj007 ~]# su - oracle
Last login: Fri Mar 31 12:40:19 CEST 2023
[oracle@aj007 ~]$ cp /tmp/burep_CRGS.json /backup_files_aj005/CRGS
[oracle@aj007 ~]$Aangezien we momenteel nog geen NFS share hebben die op alle 4 de database nodes in de 2 ODA's naar dezelfde locatie verwijzen moeten we de .json file aanpassen, zodat de paden naar de juiste locatie verwijzen. In dt voorbeeld moet backup_files_aj005 vervangen worden door backup_files. Er is gekozen om dit niet in dezelfde file te doen maar een nieuwe file /backup_files/CRGS/burep_CRGSSB.json aan te maken. Deze file wordt later gebruikt voor de irestore-database.
[root@aj001 ~]# sed 's/backup_files_aj005/backup_files/g' /backup_files/CRGS/burep_CRGS.json > /backup_files/CRGS/burep_CRGSSB.json
[root@aj001 ~]# cat /backup_files/CRGS/burep_CRGSSB.json
{
"id" : "0e6965c9-27ef-4c39-8a82-adb83d37e6fe",
"dbResId" : "40bf62e5-2af9-44c8-8994-8d098056fefc",
"tag" : "backup4DG",
"dbId" : "2431416426",
"dbName" : "CRGS",
"dbUniqueName" : "CRGS",
"backupType" : "Regular-L0",
"keepDays" : null,
"backupLocation" : "/backup_files/CRGS/orabackups/aj007-c/database/2431416426/CRGS/db",
"cfBackupHandle" : "/backup_files/CRGS/orabackups/aj007-c/database/2431416426/CRGS/db/c-2431416426-20230331-31",
"spfBackupHandle" : "/backup_files/CRGS/orabackups/aj007-c/database/2431416426/CRGS/db/c-2431416426-20230331-31",
"pitrTimeStamp" : "March 31, 2023 11:34:22 AM CEST",
"pitrSCN" : "4023538",
"resetLogsTimeStamp" : "March 28, 2023 14:09:50 PM CEST",
"resetLogsSCN" : "2617625",
"oraHomeVersion" : "19.16.0.0.220719",
"sqlPatches" : "34133642",
"backupLogLoc" : "/backup_files/CRGS/orabackups/aj007-c/database/2431416426/CRGS/rmanlog/2023-03-31/rman_backup_backup4DG_2023-03-31_11-33-16.0414.log",
"tdeWalletLoc" : null,
"dbConfigLoc" : "/backup_files/CRGS/orabackups/aj007-c/database/2431416426/CRGS/dbconfig/2023-03-31/DBCONFIG_backup4DG_2023-03-31_11-34-43.0358.tar.gz",
"name" : "Backup_Report_CRGS",
"createTime" : "March 31, 2023 11:33:13 AM CEST",
"state" : {
"status" : "CONFIGURED"
},
"updatedTime" : "March 31, 2023 11:33:13 AM CEST",
"backupReportLogDetail" : "/backup_files/CRGS/orabackups/aj007-c/database/2431416426/CRGS/rmandetaillogreport/2023-03-31/rman_list_backup_detail_backup4DG_2023-03-31_11-34-32.0984.log",
"dbInfo" : {
"dbClass" : "OLTP",
"dbType" : "RAC",
"dbShape" : "odb1",
"dbEdition" : "EE",
"dbStorage" : "ASM",
"dbRedundancy" : null,
"pdbName" : "PDB1",
"isCdb" : true
},
"dbDataSize" : "5174M",
"dbRedoSize" : "16410M",
"rmanBackupPieces" : "/backup_files/CRGS/orabackups/aj007-c/database/2431416426/CRGS/backuppieces/2023-03-31/backupPieces_backup4DG_40bf62e5-2af9-44c8-8994-8d098056fefc_20230331113442.json",
"compressionAlgo" : "BASIC",
"cpuPool" : null,
"numberOfCores" : null
}
[root@aj001 ~]#Op een node in de ODA waar de standby database komt voer je odacli irestore-database uit met de volgende parameters:
-dh het ID van de database home.-r de locatie van de .json imput file.-u de dbuniquename van de stabdny database.-ro de role STANDBY.Het is niet mogelijk om de db_name van de standby database aan te passen, dit geeft een foutmelding. Het gevolg is dat de db_name van de standby database hetzelfde is als de primary standby, het verschil is de db_unique_name.
[root@aj001 ~]# odacli irestore-database -dh 4490898f-5432-4778-bd09-c3965d0ea683 -r /backup_files/CRGS/burep_CRGSSB.json -n CRGSSB -u CRGSSB -ro STANDBY
For restoring as standby database, dbname can only be the same as the primary database's dbname, as in the backup report
[root@aj001 ~]# odacli irestore-database -dh 4490898f-5432-4778-bd09-c3965d0ea683 -r /backup_files/CRGS/burep_CRGSSB.json -u CRGSSB -ro STANDBY
Enter SYS user password:
Retype SYS user password:
{
"jobId" : "7a260c94-e028-4410-901a-0bd80c3733c6",
"status" : "Created",
"message" : null,
"reports" : [ ],
"createTimestamp" : "March 31, 2023 13:42:57 PM CEST",
"resourceList" : [ ],
"description" : "Database service recovery with db name: CRGS",
"updatedTime" : "March 31, 2023 13:42:57 PM CEST",
"jobType" : ""
}
[root@aj001 ~]#Hou met odacli describe-job de voortgang in de gaten.
[root@aj001 ~]# odacli describe-job -i "7a260c94-e028-4410-901a-0bd80c3733c6"
Job details
----------------------------------------------------------------
ID: 7a260c94-e028-4410-901a-0bd80c3733c6
Description: Database service recovery with db name: CRGS
Status: Success
Created: March 31, 2023 1:42:57 PM CEST
Message:
Task Name Start Time End Time Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Check if cluster ware is running March 31, 2023 1:42:59 PM CEST March 31, 2023 1:42:59 PM CEST Success
Check if cluster ware is running March 31, 2023 1:42:59 PM CEST March 31, 2023 1:42:59 PM CEST Success
Creating DbStorage for DbRestore March 31, 2023 1:42:59 PM CEST March 31, 2023 1:43:01 PM CEST Success
Validating DiskSpace for DATA March 31, 2023 1:42:59 PM CEST March 31, 2023 1:43:00 PM CEST Success
Setting up ssh equivalance March 31, 2023 1:43:00 PM CEST March 31, 2023 1:43:01 PM CEST Success
Audit directory creation March 31, 2023 1:43:01 PM CEST March 31, 2023 1:43:01 PM CEST Success
Audit directory creation March 31, 2023 1:43:01 PM CEST March 31, 2023 1:43:01 PM CEST Success
Create pfile for Auxiliary Instance March 31, 2023 1:43:01 PM CEST March 31, 2023 1:43:01 PM CEST Success
Deleting FRA March 31, 2023 1:43:01 PM CEST March 31, 2023 1:43:02 PM CEST Success
Rman duplicate March 31, 2023 1:43:02 PM CEST March 31, 2023 1:46:52 PM CEST Success
Creating pfile from spfile March 31, 2023 1:46:52 PM CEST March 31, 2023 1:46:52 PM CEST Success
Set PFile Ownership March 31, 2023 1:46:52 PM CEST March 31, 2023 1:46:52 PM CEST Success
Customize Db Parameters March 31, 2023 1:46:52 PM CEST March 31, 2023 1:46:53 PM CEST Success
Shutdown And Start database March 31, 2023 1:46:53 PM CEST March 31, 2023 1:47:41 PM CEST Success
Create spfile for restore db March 31, 2023 1:47:41 PM CEST March 31, 2023 1:47:42 PM CEST Success
Set PFile Ownership March 31, 2023 1:47:42 PM CEST March 31, 2023 1:47:42 PM CEST Success
Shutdown And Mount database March 31, 2023 1:47:42 PM CEST March 31, 2023 1:48:29 PM CEST Success
Customize DB for Type RAC/RacOne March 31, 2023 1:48:29 PM CEST March 31, 2023 1:48:31 PM CEST Success
Enable cluster ware for rac/racone db March 31, 2023 1:48:31 PM CEST March 31, 2023 1:48:31 PM CEST Success
Register Database taskflow March 31, 2023 1:48:34 PM CEST March 31, 2023 1:52:00 PM CEST Success
Create SPFile in shared loc March 31, 2023 1:48:34 PM CEST March 31, 2023 1:48:42 PM CEST Success
Delete Local Spfile March 31, 2023 1:48:42 PM CEST March 31, 2023 1:48:42 PM CEST Success
Register DB with clusterware March 31, 2023 1:48:42 PM CEST March 31, 2023 1:49:49 PM CEST Success
Set SysPassword and Create PwFile March 31, 2023 1:49:49 PM CEST March 31, 2023 1:49:52 PM CEST Success
Enable block change tracking March 31, 2023 1:49:52 PM CEST March 31, 2023 1:49:56 PM CEST Success
Creating pfile March 31, 2023 1:49:56 PM CEST March 31, 2023 1:49:57 PM CEST Success
Updating db env March 31, 2023 1:49:57 PM CEST March 31, 2023 1:49:59 PM CEST Success
Enable DbSizing Template March 31, 2023 1:49:59 PM CEST March 31, 2023 1:51:01 PM CEST Success
Create tns entry March 31, 2023 1:51:01 PM CEST March 31, 2023 1:51:02 PM CEST Success
Create tns entry March 31, 2023 1:51:02 PM CEST March 31, 2023 1:51:02 PM CEST Success
Running datapatch March 31, 2023 1:51:02 PM CEST March 31, 2023 1:51:03 PM CEST Success
Set CPU pool March 31, 2023 1:51:03 PM CEST March 31, 2023 1:51:03 PM CEST Success
Reset Associated Networks for Databse March 31, 2023 1:52:00 PM CEST March 31, 2023 1:52:03 PM CEST Success
Reset Associated Networks March 31, 2023 1:52:03 PM CEST March 31, 2023 1:52:03 PM CEST Success
Set log_archive_dest for Database March 31, 2023 1:52:03 PM CEST March 31, 2023 1:52:05 PM CEST Success
[root@aj001 ~]#De irestore-database heeft een database aangemaakt met de naam (db_name) van de originele database CRGS en een db_unique_name CRGSSB. Dit is een verandering t.o.v. de huidige situatie, waarbij db_name en db_unique_name gelijk zijn.
[oracle@aj001 ~]$ . oraenv<<<CRGS1
ORACLE_SID = [oracle] ? The Oracle base has been set to /u01/app/odaorabase/oracle
[oracle@aj001 ~]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Fri Mar 31 15:12:21 2023
Version 19.16.0.0.0
Copyright (c) 1982, 2022, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.16.0.0.0
SQL> set lines 1000
SQL> select name, db_unique_name from v$database;
NAME DB_UNIQUE_NAME
--------- ------------------------------
CRGS CRGSSB
SQL>Na de irestore-database is het tijd om de dataguard configuratie te laten inrichten. Hiervoor is het nodig dat de user root over het netwerk meot kunnen inloggen vanaf aj007 de naar de aj001. Dit is/wordt mogelijk een issue, want is in feite niet toegestaan bij Avinty. Tijdelijk is dit moegelijk gemaakt met een passphrase.
Bij de vraag Enter RMAN backup encryption password: moet het sys password worden ingevuld.
[root@aj007 ~]# odacli configure-dataguard
Standby site address: aj001.wolk.care
BUI username for Standby site. If Multi-user Access is disabled on Standby site, enter 'oda-admin'; otherwise, enter the name of the user who has irestored the Standby database (default: oda-admin):
BUI password for Standby site:
Enter passphrase for key '/root/.ssh/id_rsa':
Database name for Data Guard configuration: CRGS
Primary database SYS password:
*******************************************************************************************
Data Guard default settings
Primary site network for Data Guard configuration: Public-network
Standby site network for Data Guard configuration: Public-network
Primary database listener port (TCP): 1521
Standby database listener port (TCP): 1521
Transport type: ASYNC
Protection mode: MAX_PERFORMANCE
Data Guard configuration name: CRGS_CRGSSB
Active Data Guard: disabled
Do you want to edit this Data Guard configuration? (Y/N, default:N):
Primary database is missing certain archivelogs for Data Guard configuration. We need to restore those from backup.
Enter RMAN backup encryption password:
Do you want to provide another RMAN backup encryption password? [y/n] (default 'n'):
Standby database's SYS password will be set to Primary database's after Data Guard configuration. Ignore warning and proceed with Data Guard configuration? (Y/N, default:N): Y
*******************************************************************************************
Configure Data Guard CRGS_CRGSSB started
*******************************************************************************************
Step 1: Validate Data Guard configuration request (Primary site)
Description: Validate DG Config Creation for db CRGS
Job ID: 2870965d-b765-431c-afca-398ea1f587ee
Started March 31, 2023 14:52:59 PM CEST
Validate create Data Guard configuration request
Finished March 31, 2023 14:53:04 PM CEST
*******************************************************************************************
Step 2: Validate Data Guard configuration request (Standby site)
Description: Validate DG Config Creation for db CRGS
Job ID: 84b3ac51-89e8-47cd-b158-71d9245cebf4
Started March 31, 2023 14:53:05 PM CEST
Validate create Data Guard configuration request
Finished March 31, 2023 14:53:08 PM CEST
*******************************************************************************************
Step 3: Restore missing archivelog (Primary site)
Description: Create Archivelog Restore for db:CRGS
Job ID: 3890e82a-28b8-40a5-aefd-0fe493fd5b68
Started March 31, 2023 14:53:10 PM CEST
Restore Archivelog validation
Restore Archivelog
Finished March 31, 2023 14:53:34 PM CEST
*******************************************************************************************
Step 4: Download password file from Primary database (Primary site)
Description: Download orapwd file from Primary database
Started March 31, 2023 14:53:34 PM CEST
Prepare orapwd file for Primary database CRGS
Finished March 31, 2023 14:53:37 PM CEST
*******************************************************************************************
Step 5: Upload password file to Standby database (Standby site)
Description: Upload orapwd file to Standby database
Started March 31, 2023 14:53:37 PM CEST
Write orapwd file to Standby database CRGS
Finished March 31, 2023 14:53:48 PM CEST
*******************************************************************************************
Step 6: Configure Primary database (Primary site)
Description: DG Config service for db CRGS - ConfigurePrimary
Job ID: 5b4095a9-8ff9-4f19-be68-1deb9b8cb56a
Started March 31, 2023 14:53:48 PM CEST
Configure host DNS on primary env
Configure Data Guard Tns on primary env
Enable Data Guard related Db parameters for primary env
Enable force logging and archivelog mode in primary env
Enable FlashBack
Configure network parameters for local listener on primary env
Restart listener on primary env
Create services for primary db
Finished March 31, 2023 14:54:14 PM CEST
*******************************************************************************************
Step 7: Configure Standby database (Standby site)
Description: DG Config service for db CRGS - ConfigureStandby
Job ID: dcb1286f-76ef-420a-9609-5ab5aa248770
Started March 31, 2023 14:54:15 PM CEST
Configure Data Guard Tns on standby env
Configure host DNS on standby env
Clear Data Guard related Db parameters for standby env
Enable Data Guard related Db parameters for standby env
Enable force logging and archivelog mode in standby env
Populate standby database metadata
Configure network parameters for local listener on standby env
Reset Db sizing and hidden parameters for ODA best practice
Restart Listener on standby env
Create services for standby db
Finished March 31, 2023 14:56:04 PM CEST
*******************************************************************************************
Step 8: Configure and enable Data Guard (Primary site)
Description: DG Config service for db CRGS - ConfigureDg
Job ID: 9cdfd535-adf3-467e-993e-2f946bdbcad6
Started March 31, 2023 14:56:05 PM CEST
Config and enable Data Guard
Post check Data Guard configuration
Finished March 31, 2023 14:57:33 PM CEST
*******************************************************************************************
Step 9: Enable Flashback (Standby site)
Description: DG Config service for db CRGS - EnableFlashback
Job ID: b5d21ca0-d46b-408b-8cde-19eea82ff81d
Started March 31, 2023 14:57:33 PM CEST
Enable FlashBack
Finished March 31, 2023 14:57:53 PM CEST
*******************************************************************************************
Step 10: Re-enable Data Guard (Primary site)
Description: DG Config service for db CRGS - ReenableDg
Job ID: fe598380-d697-4d9e-be4d-84712e461728
Started March 31, 2023 14:57:54 PM CEST
Re-enable Data Guard if inconsistent properties found
Post check Data Guard configuration
Finished March 31, 2023 14:57:58 PM CEST
*******************************************************************************************
Step 11: Create Data Guard status (Primary site)
Description: DG Status operation for db CRGS - NewDgconfig
Job ID: afb775d6-97ed-458d-8d2f-699864e9701e
Started March 31, 2023 14:57:58 PM CEST
Create Data Guard status
Finished March 31, 2023 14:58:05 PM CEST
*******************************************************************************************
Step 12: Create Data Guard status (Standby site)
Description: DG Status operation for db CRGS - NewDgconfig
Job ID: 34b3184f-a60b-48fc-9e38-3e98a2aa3ef1
Started March 31, 2023 14:58:06 PM CEST
Create Data Guard status
Finished March 31, 2023 14:58:12 PM CEST
*******************************************************************************************
Configure Data Guard CRGS_CRGSSB completed
*******************************************************************************************
[root@aj007 ~]#De status van de dataguard inrichting kan worden opgevraagd met odacli list-dataguardstatus. Op de database server waar de primary database draait (aj007) zie je dat de role van de database PRIMARY is.
[root@aj007 ~]# odacli list-dataguardstatus
Updated about 5 minute(s) ago
It can take up to several minutes to update Data Guard status. You can re-run the command to obtain the latest status.
ID Name Database Name Role Protection Mode Apply Lag Transport Lag Apply Rate Status
---------------------------------------- -------------------------------- -------------------- ---------- ------------------ --------------- --------------- --------------- ----------
8eef5cd6-dc30-46fb-ac53-537ed7a99429 CRGS_CRGSSB CRGS PRIMARY MAX_PERFORMANCE 0 seconds 0 seconds 3.00 KByte/s CONFIGURED
[root@aj007 ~]#Op de database server waar de standby database draait (aj001) zie je dat de role van de database STANDBY is.
[root@aj001 ~]# odacli list-dataguardstatus
Updated about 3 day(s) ago
It can take up to several minutes to update Data Guard status. You can re-run the command to obtain the latest status.
ID Name Database Name Role Protection Mode Apply Lag Transport Lag Apply Rate Status
---------------------------------------- -------------------------------- -------------------- ---------- ------------------ --------------- --------------- --------------- ----------
8eef5cd6-dc30-46fb-ac53-537ed7a99429 CRGS_CRGSSB CRGS STANDBY MAX_PERFORMANCE 0 seconds 0 seconds 9.00 KByte/s CONFIGURED
[root@aj001 ~]#Via dgmgrl is het mogelijk de stats van de dataguard configuratie te controleren.
[root@aj007 ~]# su - oracle
Last login: Fri Mar 31 15:03:49 CEST 2023
[oracle@aj007 ~]$ . oraenv<<<CRGS1
ORACLE_SID = [oracle] ? The Oracle base has been set to /u01/app/odaorabase/oracle
[oracle@aj007 ~]$ dgmgrl /
DGMGRL for Linux: Release 19.0.0.0.0 - Production on Fri Mar 31 15:05:58 2023
Version 19.16.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
Welcome to DGMGRL, type "help" for information.
Connected to "CRGS"
Connected as SYSDG.
DGMGRL> show configuration
Configuration - CRGS_CRGSSB
Protection Mode: MaxPerformance
Members:
CRGS - Primary database
CRGSSB - Physical standby database
Fast-Start Failover: Disabled
Configuration Status:
SUCCESS (status updated 12 seconds ago)
DGMGRL> show database CRGS
Database - CRGS
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
CRGS1
CRGS2
Database Status:
SUCCESS
DGMGRL> show database CRGSSB
Database - CRGSSB
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds (computed 0 seconds ago)
Apply Lag: 0 seconds (computed 0 seconds ago)
Average Apply Rate: 17.00 KByte/s
Real Time Query: OFF
Instance(s):
CRGS1 (apply instance)
CRGS2
Database Status:
SUCCESS
DGMGRL>Wat hierbij opvalt is dat de dataguard nog geen active dataguard is: Real Time Query: OFF. Dit moet aangepast worden op de node waar de standby database draait.
[oracle@aj001 ~]$ srvctl config database -db CRGSSB|grep "Start opt"
Start options: mount
[oracle@aj001 ~]$ srvctl modify database -db CRGSSB -startoption "read only"
[oracle@aj001 ~]$ srvctl config database -db CRGSSB|grep "Start opt"
Start options: read only
[oracle@aj001 ~]$ srvctl stop database -db CRGSSB
[oracle@aj001 ~]$ srvctl start database -db CRGSSB
[oracle@aj001 ~]$ srvctl status database -db CRGSSB
Instance CRGS1 is running on node aj001
Instance CRGS2 is running on node aj002
[oracle@aj001 ~]$ dgmgrl /
DGMGRL for Linux: Release 19.0.0.0.0 - Production on Fri Mar 31 15:19:41 2023
Version 19.16.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
Welcome to DGMGRL, type "help" for information.
Connected to "CRGSSB"
Connected as SYSDG.
DGMGRL> show database CRGSSB
Database - CRGSSB
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 19 minutes 22 seconds (computed 1 second ago)
Apply Lag: (unknown)
Average Apply Rate: (unknown)
Real Time Query: ON
Instance(s):
CRGS1 (apply instance)
CRGS2
Database Warning(s):
ORA-16854: apply lag could not be determined
ORA-16855: transport lag has exceeded specified threshold
Database Status:
WARNING
DGMGRL>Een switchover op de ODA manier wordt uitgevoerd m.b.v. het odacli switchover-dataguard commando. Hiervoor heb je het Id van de dataguard configuratie nodig wat achterhaald kan worden met odacli list-dataguardstatus.
[root@aj007 ~]# odacli list-dataguardstatus
Updated about 18 minute(s) ago
It can take up to several minutes to update Data Guard status. You can re-run the command to obtain the latest status.
ID Name Database Name Role Protection Mode Apply Lag Transport Lag Apply Rate Status
---------------------------------------- -------------------------------- -------------------- ---------- ------------------ --------------- --------------- --------------- ----------
8eef5cd6-dc30-46fb-ac53-537ed7a99429 CRGS_CRGSSB CRGS PRIMARY MAX_PERFORMANCE 0 seconds 0 seconds 26.00 KByte/s CONFIGURED
[root@aj007 ~]#Er zijn 2 parameters nodig voor het odacli switchover-dataguard commanndo.
-i voor het ID-u naam van de standby database wat de nieuwe primary moet worden.[root@aj007 ~]# odacli switchover-dataguard -i 8eef5cd6-dc30-46fb-ac53-537ed7a99429 -u CRGSSB
Password for target database:
{
"jobId" : "df634ce2-ecff-4ed1-b52e-f502336973ed",
"status" : "Created",
"message" : null,
"reports" : [ ],
"createTimestamp" : "March 31, 2023 15:23:51 PM CEST",
"resourceList" : [ ],
"description" : "Dataguard operation for CRGS_CRGSSB - SwitchoverDg",
"updatedTime" : "March 31, 2023 15:23:51 PM CEST",
"jobType" : null
}
[root@aj007 ~]#Met odacli describe-job is de voortgang te controleren.
[root@aj007 ~]# odacli describe-job -i "df634ce2-ecff-4ed1-b52e-f502336973ed"
Job details
----------------------------------------------------------------
ID: df634ce2-ecff-4ed1-b52e-f502336973ed
Description: Dataguard operation for CRGS_CRGSSB - SwitchoverDg
Status: Success
Created: March 31, 2023 3:23:51 PM CEST
Message:
Task Name Start Time End Time Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Precheck switchover DataGuard March 31, 2023 3:23:51 PM CEST March 31, 2023 3:23:54 PM CEST Success
Switchover DataGuard March 31, 2023 3:23:54 PM CEST March 31, 2023 3:25:21 PM CEST Success
Postcheck switchover DataGuard March 31, 2023 3:25:21 PM CEST March 31, 2023 3:25:22 PM CEST Success
Check if DataGuard config is updated March 31, 2023 3:25:42 PM CEST March 31, 2023 3:26:02 PM CEST Success
[root@aj007 ~]#Na de swtichover geeft odacli list-dataguardstatus aan dat de rol varanderd is naar STANDBY.
[root@aj007 ~]# odacli list-dataguardstatus
Updated about 4 minute(s) ago
It can take up to several minutes to update Data Guard status. You can re-run the command to obtain the latest status.
ID Name Database Name Role Protection Mode Apply Lag Transport Lag Apply Rate Status
---------------------------------------- -------------------------------- -------------------- ---------- ------------------ --------------- --------------- --------------- ----------
8eef5cd6-dc30-46fb-ac53-537ed7a99429 CRGS_CRGSSB CRGS STANDBY MAX_PERFORMANCE --- 0 seconds --- CONFIGURED
[root@aj007 ~]#Met dgmgrl / is ook te zien dat de database een switchover heeft gehad.
[root@aj007 ~]# su - oracle
Last login: Fri Mar 31 15:30:39 CEST 2023
[oracle@aj007 ~]$ . oraenv<<<CRGS1
ORACLE_SID = [oracle] ? The Oracle base has been set to /u01/app/odaorabase/oracle
[oracle@aj007 ~]$ dgmgrl /
DGMGRL for Linux: Release 19.0.0.0.0 - Production on Fri Mar 31 15:33:31 2023
Version 19.16.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
Welcome to DGMGRL, type "help" for information.
Connected to "CRGS"
Connected as SYSDG.
DGMGRL> show configuration
Configuration - CRGS_CRGSSB
Protection Mode: MaxPerformance
Members:
CRGSSB - Primary database
CRGS - Physical standby database
Fast-Start Failover: Disabled
Configuration Status:
SUCCESS (status updated 40 seconds ago)
DGMGRL>De nieuwe standby database CRGS is ook READ ONLY geopend.
DGMGRL> show database CRGS
Database - CRGS
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds (computed 0 seconds ago)
Apply Lag: 0 seconds (computed 0 seconds ago)
Average Apply Rate: 5.00 KByte/s
Real Time Query: ON
Instance(s):
CRGS1 (apply instance)
CRGS2
Database Status:
SUCCESS
DGMGRL>Een switchover naar de originele primary DB is bijna hetzelfde als een switchover. Alleen de waarde van parameter -u is anders, dit is de naam van de originele primary DB.
[root@aj001 ~]# odacli list-dataguardstatus
Updated about 32 minute(s) ago
It can take up to several minutes to update Data Guard status. You can re-run the command to obtain the latest status.
ID Name Database Name Role Protection Mode Apply Lag Transport Lag Apply Rate Status
---------------------------------------- -------------------------------- -------------------- ---------- ------------------ --------------- --------------- --------------- ----------
8eef5cd6-dc30-46fb-ac53-537ed7a99429 CRGS_CRGSSB CRGS STANDBY MAX_PERFORMANCE 0 seconds 0 seconds 2.00 KByte/s CONFIGURED
[root@aj001 ~]# odacli switchover-dataguard -i 8eef5cd6-dc30-46fb-ac53-537ed7a99429 -u CRGS
Password for target database:
{
"jobId" : "eb561ac9-5caa-491d-a21f-9b9a5b1345bb",
"status" : "Created",
"message" : null,
"reports" : [ ],
"createTimestamp" : "March 31, 2023 15:41:20 PM CEST",
"resourceList" : [ ],
"description" : "Dataguard operation for CRGS_CRGSSB - SwitchoverDg",
"updatedTime" : "March 31, 2023 15:41:20 PM CEST",
"jobType" : null
}
[root@aj001 ~]#controleer de voortgang met odacli describe-job.
[root@aj001 ~]# odacli describe-job -i "eb561ac9-5caa-491d-a21f-9b9a5b1345bb"
Job details
----------------------------------------------------------------
ID: eb561ac9-5caa-491d-a21f-9b9a5b1345bb
Description: Dataguard operation for CRGS_CRGSSB - SwitchoverDg
Status: Success
Created: March 31, 2023 3:41:20 PM CEST
Message:
Task Name Start Time End Time Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Precheck switchover DataGuard March 31, 2023 3:41:20 PM CEST March 31, 2023 3:41:22 PM CEST Success
Switchover DataGuard March 31, 2023 3:41:22 PM CEST March 31, 2023 3:42:50 PM CEST Success
Postcheck switchover DataGuard March 31, 2023 3:42:50 PM CEST March 31, 2023 3:43:50 PM CEST Success
Check if DataGuard config is updated March 31, 2023 3:44:00 PM CEST March 31, 2023 3:44:10 PM CEST Success
[root@aj001 ~]#Na een tijdje is te zien dat de rol weer PRIMARY geworden is.
[root@aj007 ~]# odacli list-dataguardstatus
Updated about 57 second(s) ago
It can take up to several minutes to update Data Guard status. You can re-run the command to obtain the latest status.
ID Name Database Name Role Protection Mode Apply Lag Transport Lag Apply Rate Status
---------------------------------------- -------------------------------- -------------------- ---------- ------------------ --------------- --------------- --------------- ----------
8eef5cd6-dc30-46fb-ac53-537ed7a99429 CRGS_CRGSSB CRGS PRIMARY MAX_PERFORMANCE 0 seconds 0 seconds 9.00 KByte/s CONFIGURED
[root@aj007 ~]#Dit kan je ook met dgmgrl / controleren.
DGMGRL> show configuration
Configuration - CRGS_CRGSSB
Protection Mode: MaxPerformance
Members:
CRGS - Primary database
CRGSSB - Physical standby database
Fast-Start Failover: Disabled
Configuration Status:
SUCCESS (status updated 23 second ago)
DGMGRL>Het verwijderen van een dataguard omgeving op een ODA doe je met het odacli deconfigure-dataguard commando, waarbij het ID van de dataguard configuratie als parameter wordt meegegeven.
[root@aj007 ~]# odacli deconfigure-dataguard -i e9ead619-0065-441d-be22-54113a9c10dd
Standby site address: aj001.wolk.care
BUI username for Standby site. If Multi-user Access is disabled on Standby site, enter 'oda-admin'; otherwise, enter the name of the user who has irestored the Standby database (default: oda-admin):
BUI password for Standby site:
root@aj001.wolk.care's password:
Standby database will be deleted after Data Guard configuration is removed. Ignore warning and proceed with Data Guard deconfiguration? (Y/N): Y
Deconfigure Dataguard Started
*******************************************************************************************
Step 1: Deconfigure Data Guard (Primary site)
Description: Deconfigure DG service
Job ID: cc49c740-40a5-4ef9-9a03-0441608dea13
Started March 29, 2023 11:14:18 AM CEST
Deconfigure Data Guard service
Cleanup broker resources
Finished March 29, 2023 11:15:44 AM CEST
*******************************************************************************************
Step 2: Delete Data Guard status (Primary site)
Description: DG Status operation for db - UpdateDgconfig
Job ID: 56667c30-9f46-47bb-b60c-6c455c527b77
Started March 29, 2023 11:15:44 AM CEST
Finished March 29, 2023 11:15:44 AM CEST
*******************************************************************************************
Step 3: Delete Data Guard status (Standby site)
Description: DG Status operation for db - UpdateDgconfig
Job ID: b4240b29-d33f-4f56-aff5-a6b5c799444e
Started March 29, 2023 11:15:45 AM CEST
Update Data Guard status
Finished March 29, 2023 11:15:45 AM CEST
*******************************************************************************************
Step 4: Delete Standby database (Standby site)
Description: Database service deletion with db name: CRGS with id : df461ad0-7e4b-496e-bd43-82b5b157653b
Job ID: 0a1c86ca-e36e-4094-8660-18f0f96c6721
Started March 29, 2023 11:15:48 AM CEST
Validate db df461ad0-7e4b-496e-bd43-82b5b157653b for deletion
Database Deletion By RHP
Unregister Db From Cluster
Kill Pmon Process
Database Files Deletion
Finished March 29, 2023 11:17:29 AM CEST
*******************************************************************************************
Data Guard configuration is removed
[root@aj007 ~]#Door bij de vraag Do you want to edit this Data Guard configuration? (Y/N, default:N): te kiezen voor Y krijg je de mogelijkheid om Active Data Guard direct te configureren.
Do you want to edit this Data Guard configuration? (Y/N, default:N): Y
*******************************************************************************************
Primary site network for Data Guard configuration [Public-network] (default: Public-network):
Standby site network for Data Guard configuration [Public-network] (default: Public-network):
Primary database listener port (TCP) (default: 1521):
Standby database listener port (TCP) (default: 1521):
Transport type [ASYNC, FASTSYNC, SYNC] (default: ASYNC): FASTSYNC
Protection mode [MAX_PROTECTION, MAX_PERFORMANCE, MAX_AVAILABILITY] (default: MAX_PERFORMANCE):
Data Guard configuration name (default: CA919P_CA919SB):
Primary database is missing certain archivelogs for Data Guard configuration. We need to restore those from backup.
Enter RMAN backup encryption password:
Do you want to provide another RMAN backup encryption password? [y/n] (default 'n'):
Enable Active Data Guard? (Y/N, default:N): Y
Standby database's SYS password will be set to Primary database's after Data Guard configuration. Ignore warning and proceed with Data Guard configuration? (Y/N, default:N): YDe ‘totale’ output van odacli configure-dataguard ziet er dan als volgt uit.
[root@ab037 ~]# odacli configure-dataguard
Standby site address: ab031
BUI username for Standby site. If Multi-user Access is disabled on Standby site, enter 'oda-admin'; otherwise, enter the name of the user who has irestored the Standby database (default: oda-admin):
BUI password for Standby site:
Database name for Data Guard configuration: CA919P
Primary database SYS password:
*******************************************************************************************
Data Guard default settings
Primary site network for Data Guard configuration: Public-network
Standby site network for Data Guard configuration: Public-network
Primary database listener port (TCP): 1521
Standby database listener port (TCP): 1521
Transport type: ASYNC
Protection mode: MAX_PERFORMANCE
Data Guard configuration name: CA919P_CA919SB
Active Data Guard: disabled
Do you want to edit this Data Guard configuration? (Y/N, default:N): Y
*******************************************************************************************
Primary site network for Data Guard configuration [Public-network] (default: Public-network):
Standby site network for Data Guard configuration [Public-network] (default: Public-network):
Primary database listener port (TCP) (default: 1521):
Standby database listener port (TCP) (default: 1521):
Transport type [ASYNC, FASTSYNC, SYNC] (default: ASYNC): FASTSYNC
Protection mode [MAX_PROTECTION, MAX_PERFORMANCE, MAX_AVAILABILITY] (default: MAX_PERFORMANCE):
Data Guard configuration name (default: CA919P_CA919SB):
Primary database is missing certain archivelogs for Data Guard configuration. We need to restore those from backup.
Enter RMAN backup encryption password:
Do you want to provide another RMAN backup encryption password? [y/n] (default 'n'):
Enable Active Data Guard? (Y/N, default:N): Y
Standby database's SYS password will be set to Primary database's after Data Guard configuration. Ignore warning and proceed with Data Guard configuration? (Y/N, default:N): Y
*******************************************************************************************
Configure Data Guard CA919P_CA919SB started
*******************************************************************************************
Step 1: Validate Data Guard configuration request (Primary site)
Description: Validate DG Config Creation for db CA919P
Job ID: c80f498a-9a02-4e86-9430-d0a28202bcb5
Started August 08, 2023 11:47:23 AM CEST
Validate create Data Guard configuration request
Finished August 08, 2023 11:47:28 AM CEST
*******************************************************************************************
Step 2: Validate Data Guard configuration request (Standby site)
Description: Validate DG Config Creation for db CA919P
Job ID: b46abddf-3410-4a57-a327-32de5ee64128
Started August 08, 2023 11:47:28 AM CEST
Validate create Data Guard configuration request
Finished August 08, 2023 11:47:33 AM CEST
*******************************************************************************************
Step 3: Download password file from Primary database (Primary site)
Description: Download orapwd file from Primary database
Started August 08, 2023 11:47:33 AM CEST
Prepare orapwd file for Primary database CA919P
Finished August 08, 2023 11:47:35 AM CEST
*******************************************************************************************
Step 4: Upload password file to Standby database (Standby site)
Description: Upload orapwd file to Standby database
Started August 08, 2023 11:47:35 AM CEST
Write orapwd file to Standby database CA919P
Finished August 08, 2023 11:47:39 AM CEST
*******************************************************************************************
Step 5: Configure Primary database (Primary site)
Description: DG Config service for db CA919P - ConfigurePrimary
Job ID: 324152fa-a83d-4c26-9f54-bf04c610f54f
Started August 08, 2023 11:47:39 AM CEST
Configure host DNS on primary env
Configure Data Guard Tns on primary env
Enable Data Guard related Db parameters for primary env
Enable force logging and archivelog mode in primary env
Enable FlashBack
Configure network parameters for local listener on primary env
Reload listener on primary env
Create services for primary db
Finished August 08, 2023 11:48:14 AM CEST
*******************************************************************************************
Step 6: Configure Standby database (Standby site)
Description: DG Config service for db CA919P - ConfigureStandby
Job ID: d33e6dbe-0cd7-4a73-a33a-458e74c447ba
Started August 08, 2023 11:48:14 AM CEST
Configure Data Guard Tns on standby env
Configure host DNS on standby env
Clear Data Guard related Db parameters for standby env
Enable Data Guard related Db parameters for standby env
Enable force logging and archivelog mode in standby env
Populate standby database metadata
Configure network parameters for local listener on standby env
Reset Db sizing and hidden parameters for ODA best practice
Reload Listener on standby env
Create services for standby db
Finished August 08, 2023 11:49:45 AM CEST
*******************************************************************************************
Step 7: Restore missing archivelog (Primary site)
Description: Create Archivelog Restore for db:CA919P
Job ID: 33bcec16-183e-4243-9eaf-736bfb5ac403
Started August 08, 2023 11:49:47 AM CEST
Restore Archivelog validation
Restore Archivelog
Finished August 08, 2023 11:50:16 AM CEST
*******************************************************************************************
Step 8: Configure and enable Data Guard (Primary site)
Description: DG Config service for db CA919P - ConfigureDg
Job ID: c47f9bb0-e412-428a-8d77-b9c15171c947
Started August 08, 2023 11:50:17 AM CEST
Config and enable Data Guard
Post check Data Guard configuration
Finished August 08, 2023 11:51:19 AM CEST
*******************************************************************************************
Step 9: Enable Flashback (Standby site)
Description: DG Config service for db CA919P - EnableFlashback
Job ID: a7246f00-d0b3-4fa7-a054-4cd8bc84ae6c
Started August 08, 2023 11:51:19 AM CEST
Enable FlashBack
Finished August 08, 2023 11:51:39 AM CEST
*******************************************************************************************
Step 10: Re-enable Data Guard (Primary site)
Description: DG Config service for db CA919P - ReenableDg
Job ID: 6ee0834c-549d-4933-bba0-6071563b209a
Started August 08, 2023 11:51:40 AM CEST
Re-enable Data Guard if inconsistent properties found
Post check Data Guard configuration
Finished August 08, 2023 11:51:44 AM CEST
*******************************************************************************************
Step 11: Enable Active Data Guard (Standby site)
Description: DG Config service for db CA919P - EnableActivedg
Job ID: af4ae49c-498a-4c33-bb87-beed8d69004f
Started August 08, 2023 11:51:45 AM CEST
Open standby db
Post check Data Guard configuration
Finished August 08, 2023 11:51:56 AM CEST
*******************************************************************************************
Step 12: Create Data Guard status (Primary site)
Description: DG Status operation for db CA919P - NewDgconfig
Job ID: 83976c08-d9c9-4f46-a331-92ade9ccf0fe
Started August 08, 2023 11:51:56 AM CEST
Create Data Guard status
Finished August 08, 2023 11:52:10 AM CEST
*******************************************************************************************
Step 13: Create Data Guard status (Standby site)
Description: DG Status operation for db CA919P - NewDgconfig
Job ID: f1b13171-1579-49ca-8e37-5f07b522abf3
Started August 08, 2023 11:52:10 AM CEST
Create Data Guard status
Finished August 08, 2023 11:52:17 AM CEST
*******************************************************************************************
Configure Data Guard CA919P_CA919SB completed
*******************************************************************************************
[root@ab037 ~]#Bij het opnieuw aanmaken van de DG configuratie op de ab037.ab038 en ab031/ab032 liep ik tegen een ‘onverklaarbare’ foutmelding aan.
[root@ab031 ~]# odacli describe-job -i eaa5206b-b2df-4119-af9d-3d18ec4afd16
Job details
----------------------------------------------------------------
ID: eaa5206b-b2df-4119-af9d-3d18ec4afd16
Description: Database service recovery with db name: CA919P
Status: Failure
Created: August 3, 2023 10:52:10 AM CEST
Message: DCS-10001:Internal error encountered: Failed to setup or check SSH state.
Task Name Node Name Start Time End Time Status
---------------------------------------- ------------------------- ----------------------------------- ----------------------------------- ----------
Restore Database ab031 August 3, 2023 10:52:18 AM CEST August 3, 2023 10:52:22 AM CEST Failure
Restore Database ab031 August 3, 2023 10:52:18 AM CEST August 3, 2023 10:52:22 AM CEST Failure
Check if cluster ware is running ab031 August 3, 2023 10:52:20 AM CEST August 3, 2023 10:52:20 AM CEST Success
Check if cluster ware is running ab032 August 3, 2023 10:52:20 AM CEST August 3, 2023 10:52:21 AM CEST Success
Creating DbStorage for DbRestore ab031 August 3, 2023 10:52:21 AM CEST August 3, 2023 10:52:22 AM CEST Failure
Validating DiskSpace for DATA ab031 August 3, 2023 10:52:21 AM CEST August 3, 2023 10:52:21 AM CEST Success
Setting up ssh equivalance ab031 August 3, 2023 10:52:21 AM CEST August 3, 2023 10:52:21 AM CEST Failure
task:TaskSequential_34347 ab031 August 3, 2023 10:52:21 AM CEST August 3, 2023 10:52:21 AM CEST Failure
Setting up SSH for user: oracle ab031 August 3, 2023 10:52:21 AM CEST August 3, 2023 10:52:21 AM CEST Failure
[root@ab031 ~]#Uiteindelijk bleek het steeds mis te gaan omdat de files in de .ssh directory van users root en oracle 'beschermd' zijn mbv chattr +i. Nadat dit terugedraaid is gaat het goed.
Na het verwijderen van een DG configuratie bleek dat er nog een directory bestond: /u04/app/oracle/redo . Dit veroorzaakte onderstaande foutmelding.
[root@ab031 tmp]# odacli irestore-database -dh 799e1ccd-7ff8-414e-b6c2-a254811bf0a2 -r /backup_files/ab037/burep_CA040P.json -u CA919SB -ro STANDBY -dr ACFS
Enter SYS user password:
Retype SYS user password:
DCS-10001:Internal error encountered: For input string: "acfsutil info fs: ACFS-03037: not an ACFS file system".
[root@ab031 tmp]#Na controle dat de directories leeg waren, zijn deze verwijderd. Hierna gaat de irestore wel goed.
Let verder op dat de pdb van de primary database de status ‘open’ heeft bij het maken van de backup. Indien dit niet het geval is zal de irestore mislukken.
[root@ab031 ~]# odacli describe-job -i ea22326f-3dbd-48be-ad34-0f2b2a5d3f04
Job details
----------------------------------------------------------------
ID: ea22326f-3dbd-48be-ad34-0f2b2a5d3f04
Description: Database service recovery with db name: CA919P
Status: Failure
Created: August 8, 2023 10:04:37 AM CEST
Message: DCS-10001:Internal error encountered: null.
Task Name Node Name Start Time End Time Status
---------------------------------------- ------------------------- ----------------------------------- ----------------------------------- ----------
Restore Database ab031 August 8, 2023 10:04:45 AM CEST August 8, 2023 10:07:35 AM CEST Failure
Restore Database ab031 August 8, 2023 10:04:45 AM CEST August 8, 2023 10:07:35 AM CEST Failure
Check if cluster ware is running ab031 August 8, 2023 10:04:47 AM CEST August 8, 2023 10:04:48 AM CEST Success
Check if cluster ware is running ab032 August 8, 2023 10:04:48 AM CEST August 8, 2023 10:04:48 AM CEST Success
Creating DbStorage for DbRestore ab031 August 8, 2023 10:04:48 AM CEST August 8, 2023 10:06:58 AM CEST Success
Validating DiskSpace for DATA ab031 August 8, 2023 10:04:48 AM CEST August 8, 2023 10:04:48 AM CEST Success
Setting up ssh equivalance ab031 August 8, 2023 10:04:48 AM CEST August 8, 2023 10:04:51 AM CEST Success
Creating volume datCA919P ab031 August 8, 2023 10:04:51 AM CEST August 8, 2023 10:05:15 AM CEST Success
Creating volume reco ab031 August 8, 2023 10:05:15 AM CEST August 8, 2023 10:05:38 AM CEST Success
Creating volume redo ab031 August 8, 2023 10:05:38 AM CEST August 8, 2023 10:06:00 AM CEST Success
Creating ACFS filesystem for DATA ab031 August 8, 2023 10:06:00 AM CEST August 8, 2023 10:06:18 AM CEST Success
Creating ACFS filesystem for RECO ab031 August 8, 2023 10:06:18 AM CEST August 8, 2023 10:06:39 AM CEST Success
Creating ACFS filesystem for REDO ab031 August 8, 2023 10:06:39 AM CEST August 8, 2023 10:06:58 AM CEST Success
Audit directory creation ab031 August 8, 2023 10:06:58 AM CEST August 8, 2023 10:06:58 AM CEST Success
Audit directory creation ab032 August 8, 2023 10:06:58 AM CEST August 8, 2023 10:06:58 AM CEST Success
Restore Database ab031 August 8, 2023 10:06:59 AM CEST August 8, 2023 10:07:35 AM CEST Failure
Create pfile for Auxiliary Instance ab031 August 8, 2023 10:06:59 AM CEST August 8, 2023 10:06:59 AM CEST Success
Modifying Storage Dir Ownership ab031 August 8, 2023 10:06:59 AM CEST August 8, 2023 10:06:59 AM CEST Success
Rman duplicate ab031 August 8, 2023 10:06:59 AM CEST August 8, 2023 10:07:24 AM CEST Failure