Exacs:DG creation fails with error "RMAN-04022: target database mount id <ID> does not match channel's mount id <ID>"
(Doc ID 2958517.1)
Last updated on MAY 02, 2024
Applies to:
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and laterInformation in this document applies to any platform.
Symptoms
//In Exacs , DG creation from UI fails with below errors
dgdeployer" : [
"CDG-50102 : <DBNAME> Database not ready for DG Configuration\nERROR: Error in creation of standby database\nFile: dgdeployer, Line#: 206, Log: /var/opt/oracle/log/<DBNAME>/dgdeployer/dgdeployer_2023-06-24_18:26:29.64095953198.log"
#/var/opt/oracle/misc/platforminfo
EXABM
[root@<Node1> ~]# rpm -qa --last | egrep -i 'dbaastools_exa|dbcs'
dbcs-admin-update-23.1.1.0.1-230113.0444.x86_64 Thu 01 Jun 2023 03:27:09 PM BST
dbaastools_exa-1.0-23.2.1.0.0_230503.1101.x86_64 Thu 01 Jun 2023 03:21:47 PM BST
dbcs-agent-update-23.2.1.0.0-230503.1101.x86_64 Thu 01 Jun 2023 03:21:16 PM BST
dbcs-agent-2.8OL7-23.1.2.0.0_230305.1210.x86_64 Thu 01 Jun 2023 02:35:18 PM BST
//From dgdeployer_<TIMESTAMP>.log,Please check the below RMAN restore service failure that caused the DG configuration failure.
2023-06-24 19:23:54.017930 - WARN : non-zero status returned
Command: /u02/app/oracle/product/12.1.0/dbhome_6/bin/rman @/var/opt/oracle/dbaas_acfs/<DBNAME>/60118.rman LOG = /var/opt/oracle/log/<DBNAME>/rman_restore_recover_60118.log APPEND
Exit: 1
Excerpt:
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19>
2023-06-24 19:23:54.020044 - RMAN script:
2023-06-24 19:23:54.022017 - Output from cmd /bin/cat /var/opt/oracle/dbaas_acfs/<DBNAME>/60118.rman run on localhost is:
2023-06-24 19:23:54.033946 - CONNECT TARGET sys/********
run {
ALLOCATE CHANNEL C1 TYPE DISK CONNECT '/@<DBNAME>_lhr1_';
ALLOCATE CHANNEL C2 TYPE DISK CONNECT '/@<DBNAME>_lhr1_';
ALLOCATE CHANNEL C3 TYPE DISK CONNECT '/@<DBNAME>_lhr1_';
ALLOCATE CHANNEL C4 TYPE DISK CONNECT '/@<DBNAME>_lhr1_';
ALLOCATE CHANNEL C5 TYPE DISK CONNECT '/@<DBNAME>_lhr3_';
ALLOCATE CHANNEL C6 TYPE DISK CONNECT '/@<DBNAME>_lhr3_';
ALLOCATE CHANNEL C7 TYPE DISK CONNECT '/@<DBNAME>_lhr3_';
ALLOCATE CHANNEL C8 TYPE DISK CONNECT '/@<DBNAME>_lhr3_';
ALLOCATE CHANNEL C9 TYPE DISK CONNECT '/@<DBNAME>_lhr2_';
ALLOCATE CHANNEL C10 TYPE DISK CONNECT '/@<DBNAME>_lhr2_';
ALLOCATE CHANNEL C11 TYPE DISK CONNECT '/@<DBNAME>_lhr2_';
ALLOCATE CHANNEL C12 TYPE DISK CONNECT '/@<DBNAME>_lhr2_';
catalog start with '+DATAC1/<DBNAME>_lhr3ry/' noprompt;
catalog start with '+RECOC1/<DBNAME>_lhr3ry/' noprompt;
}
2023-06-24 19:23:54.035868 - cmd took 0.00638604164123535 seconds
2023-06-24 19:23:54.039739 - Output from cmd /bin/rm -f /var/opt/oracle/dbaas_acfs/<DBNAME>/60118.rman run on localhost is:
2023-06-24 19:23:54.059866 - cmd took 0.0143749713897705 seconds
2023-06-24 19:23:54.061974 -
CDG-50708 : Restore from service failed for DB <DBNAME>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>RMAN restore services were failed
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19>
File: odg, Line#: 5599, Log: /var/opt/oracle/log/<DBNAME>/dgrops/dgrops_duplicate_db_service_2023-06-24_18:27:03.64819160118.log
2023-06-24 19:23:54.064293 -
CDG-50104 : DataGuard Configuration failed for <DBNAME>
ERROR: Failed restore control file before recover
File: dgdb, Line#: 1872, Log: /var/opt/oracle/log/<DBNAME>/dgrops/dgrops_duplicate_db_service_2023-06-24_18:27:03.64819160118.log
2023-06-24 19:23:54.174850 - cmd took 3410.79414892197 seconds
2023-06-24 19:23:54.176746 - WARN : non-zero status returned
Command: /bin/su -- opc -c '/bin/sudo /var/opt/oracle/ocde/assistants/dg/lib/dgrops duplicate_db_service <DBNAME> rac /var/opt/oracle/dbaas_acfs/dgtmp_PRD21CDB/dgparams.json'
Exit: 1
Excerpt:
CDG-50104 : DataGuard Configuration failed for <DBNAME>
ERROR: Failed restore control file before recover
(...)
ERROR: Failed restore control file before recover
File: dgdb, Line#: 1872, Log: /var/opt/oracle/log/<DBNAME>/dgrops/dgrops_duplicate_db_service_2023-06-24_18:27:03.64819160118.log
2023-06-24 19:23:59.180074 - INFO: NO of retries = 1
//From rman_restore_recover_60118.log
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: using network backup set from service PRD21CDB_lhr3rx
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=+DATAC1/PRD21CDB_LHR3RY/CONTROLFILE/current.696.1140370075
Finished restore at 24-JUN-23
Recovery Manager complete.
Recovery Manager: Release 12.1.0.2.0 - Production on Sat Jun 24 19:23:52 2023
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
RMAN> CONNECT TARGET *
2> run {
3> ALLOCATE CHANNEL C1 TYPE DISK CONNECT *;
4> ALLOCATE CHANNEL C2 TYPE DISK CONNECT *;
5> ALLOCATE CHANNEL C3 TYPE DISK CONNECT *;
6> ALLOCATE CHANNEL C4 TYPE DISK CONNECT *;
7> ALLOCATE CHANNEL C5 TYPE DISK CONNECT *;
8> ALLOCATE CHANNEL C6 TYPE DISK CONNECT *;
9> ALLOCATE CHANNEL C7 TYPE DISK CONNECT *;
10> ALLOCATE CHANNEL C8 TYPE DISK CONNECT *;
11> ALLOCATE CHANNEL C9 TYPE DISK CONNECT *;
12> ALLOCATE CHANNEL C10 TYPE DISK CONNECT *;
13> ALLOCATE CHANNEL C11 TYPE DISK CONNECT *;
14> ALLOCATE CHANNEL C12 TYPE DISK CONNECT *;
15> catalog start with '+DATAC1/PRD21CDB_lhr3ry/' noprompt;
16> catalog start with '+RECOC1/PRD21CDB_lhr3ry/' noprompt;
17>
18> }
19>
connected to target database: <DBNAME> (DBID=2615283913, not open)
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-04022: target database mount id 2716549163 does not match channel's mount id 2707924912
RMAN-03002: failure of allocate command at 06/24/2023 19:23:53
RMAN-04022: target database mount id 2716549163 does not match channel's mount id 2707924912>>>>>>>>>>>>>>>>>>>>>
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |