Show pageOld revisionsBacklinksODT exportBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ====Configuration of the Destination==== After the backup files have been copied, then we have to perform duplication as follows: Ensure that the database is dropped and started in NOMOUNT state <sxh> SQL> shutdown abort; ORACLE instance shut down. SQL> startup mount exclusive restrict ORACLE instance started. Total System Global Area 1.0689E+10 bytes Fixed Size 2237776 bytes Variable Size 6241127088 bytes Database Buffers 4429185024 bytes Redo Buffers 16924672 bytes Database mounted. SQL> drop database; </sxh> After that the SPFILE/PFILE should be modified so it will reflect the replica server and the database started in NOMOUNT mode: <sxh> SQL> startup pfile='/home/oracle/textpfile' nomount; ORACLE instance started. Total System Global Area 4275781632 bytes Fixed Size 2235208 bytes Variable Size 2298479800 bytes Database Buffers 1962934272 bytes Redo Buffers 12132352 bytes </sxh> From the recovery Manager, duplicate the database using the backups which were copied: <sxh> Recovery Manager: Release 11.2.0.3.0 - Production on Fri May 27 16:10:49 2016 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to auxiliary database: FINEXPRO (not mounted) Reenabling controlfile options for auxiliary database Executing: alter database add supplemental log data RMAN> RUN { ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE DISK; duplicate database to destinSRV backup location "/home/oracle" NOFILENAMECHECK ; } / contents of Memory Script: { Alter clone database open resetlogs; } executing Memory Script database opened Finished Duplicate Db at 27-MAY-16 released channel: c1 </sxh> oracle_12_goldengate_conf_initial_load_p2.txt Last modified: 2019/10/18 20:04by 127.0.0.1