oracle12c RAC source real-time synchronization with the end goal Dataguard, because of operational requirements need to increase the PDB at the source
1. The source added PDB
CREATE PLUGGABLE DATABASE kdlxpdb admin user kdlx identified by *
FILE_NAME_CONVERT =('+DATADG/SPDB/8E80F930196B6100E053E200A8C0AF9F/','+DATADG');
Under View trace logs directory alert_spdb2.log, PDB create success
2. The end goal
View trace directory under alert_spdbstb.log log and found that the synchronization failure
SQL> alter database recover managed standby database cancel; # cancel synchronization
Error: ORA-16136: Managed Standby Recovery not active, alert_spdbstb.log log is as follows:
Select the priority parameter modification db_file_name_convert
alter system set db_file_name_convert='+DATADG/SPDB/DATAFILE', '/data/spdbstb/datafile', '+DATADG/SPDB/8E80F930196B6100E053E200A8C0AF9F/DATAFILE', '/data/spdbstb/SEED/datafile', '+DATADG/SPDB/8E81C7A967C43CB7E053E300A8C06223/DATAFILE', '/data/spdbstb/SPDB1PDB/datafile', '+DATADG/SPDB/93BFEF75138BC79EE053E300A8C08BA1/DATAFILE', '/data/spdbstb/kdlxpdb/datafile' scope=spfile;
After modification the same again to cancel the synchronization error, and then shutdown immediate
After startup launched only found a synchronized file system data
SQL> select name from v$datafile;
By following the abolition synchronous actually normal, a little surprised
SQL> alter database recover managed standby database cancel;
SQL> alter database recover managed standby database using current logfile disconnect from session;
SQL> show pdbs;
SQL> alter pluggable database all open;
SQL> show pdbs;
SQL> alter database recover managed standby database cancel;
Then start off library library, open sync everything back to normal
See archive log directory / data / archivelog dual source node discovery log finally passed over, an interval of 3 hours
3. Specific questions can only be traced by looking at the log
From the point of view of data log files should be in complete synchronization is not canceled after the synchronous case again revised to sync.
Cancel sync error, and later somehow being good only use this article to explain http://www.kimgeek.com/article_detail_183.html
After the first treatment record, specific reasons and details still need to quietly and patted.
Note: to cancel and re-create the synchronization Dataguard PDB should be more fly some.