Create a clone database form rman catalog !

Dear Friend ,
I have a rman catalog database . I am using this rman catalog for against a database name 'testdb' . Everyday I take rman full backup of the testdb using the catalog database .
Now I create a another database which will be the clone of the testdb . I want to create it using that rman catalog database . Can I create a new database using the catalog database ?
If yes, then plz help me to give some directions .....

Check here:
[http://www.shutdownabort.com/quickguides/clone_rman.php]
[Duplicating a Database with Recovery Manager|http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmdupdb.htm#441628]
Oracle documentation Link added.

Similar Messages

Is it possible to create a Clone database with the same name of source db ?

Is it possible to create a Clone database with the same name of source db using RMAN ...
DB version is 11.2.0.2
Is it possible to clone a 11.2.0.2 database to 11.2.0.3 home location directly on a new server . If it starts in a upgrade mode , it is ok ....

user11919409 wrote:
Is it possible to create a Clone database with the same name of source db using RMAN ...
yes
>
DB version is 11.2.0.2
Is it possible to clone a 11.2.0.2 database to 11.2.0.3 home location directly on a new server . If it starts in a upgrade mode , it is ok ....yes
Handle:     user11919409
Status Level:     Newbie (10)
Registered:     Dec 7, 2009
Total Posts:     102
Total Questions:     28 (22 unresolved)
why do you waste time here when you rarely get any answers to your questions?

Registering Clone database in Recovery catalog

Can we able to register the clone database in recovery catalog database without changing dbid?
I don't want to use dbid utility.
Is that any parameter?
Regards,
Latha

Well you can register it without changing any parameters in oracle 10.2
That does not mean you should do it.
I would have answered as follows:
It is not a good idea to register a clone database in the same recovery catalog as the original database as the recovery catalog uses the dbid to identify the database and having two databases with the same dbid essentially corrupts the recovery catalog.
If you change the dbid then it is perfectly okay to store the cloned database in the same recovery catalog.

Unable to create a duplicat database through rman

Hi,
Oracle Version:10.2.0.1
Operating System:Linux
Here i am having databae KKK and i need to duplicate that databae to vtldb.I take the backup of the KKK database as
rman target /
RMAN>Backup databsase;after that i copied all the bakup sets to my vtldb database in the location '/u01/app/oracle/oradata/vtldb/'.Then i created a new auxiliary channel as
create auciliary channel as device type disk format '/u01/pp/oracle/oradata/vtldb/%U';Then connecting to my auxiliary databae and getting the following error.
[oracle@vtlsys3-143 ~]$ rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Mar 11 13:30:12 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: KKK (DBID=2526957931)
RMAN> connect aucxiliary sys@vtldb_rmandup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "auxiliary, catalog, clone, rcvcat, target"
RMAN-01008: the bad identifier was: aucxiliary
RMAN-01007: at line 1 column 9 file: standard input
RMAN> connect auxiliary sys@vtldb_rmandup
auxiliary database Password:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-04006: error from auxiliary database: ORA-01031: insufficient privilegesI create the passowrd file for VTLDB aslo .
Can any one please help me how to solve my problem.
Thanks & Regars,
Poorna Prasad.

Hi Anil,
Thanks for your replays.Now i was able to connect to the database.But i am facing another problem.
RMAN> list backup;
RMAN> backup database;
Starting backup at 11-MAR-10
using channel ORA_DISK_1
using channel ORA_DISK_2
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=/u01/app/oracle/oradata/kkk/system01.dbf
channel ORA_DISK_1: starting piece 1 at 11-MAR-10
channel ORA_DISK_2: starting full datafile backupset
channel ORA_DISK_2: specifying datafile(s) in backupset
input datafile fno=00003 name=/u01/app/oracle/oradata/kkk/sysaux01.dbf
input datafile fno=00002 name=/u01/app/oracle/oradata/kkk/undotbs01.dbf
channel ORA_DISK_2: starting piece 1 at 11-MAR-10
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 03/11/2010 16:36:11
ORA-19504: failed to create file "/u02/rman_bkp/kkk/ora_rbk713378170_s"
ORA-27038: created file already exists
Additional information: 1
channel ORA_DISK_2 disabled, job failed on it will be run on another channel
channel ORA_DISK_1: finished piece 1 at 11-MAR-10
piece handle=/u02/rman_bkp/kkk/ora_rbk713378170_s tag=TAG20100311T163610 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=/u01/app/oracle/oradata/kkk/sysaux01.dbf
input datafile fno=00002 name=/u01/app/oracle/oradata/kkk/undotbs01.dbf
channel ORA_DISK_1: starting piece 1 at 11-MAR-10
channel ORA_DISK_1: finished piece 1 at 11-MAR-10
piece handle=/u02/rman_bkp/kkk/ora_rbk713378186_s tag=TAG20100311T163610 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=/u01/app/oracle/oradata/kkk/users01.dbf
channel ORA_DISK_1: starting piece 1 at 11-MAR-10
channel ORA_DISK_1: finished piece 1 at 11-MAR-10
piece handle=/u02/rman_bkp/kkk/ora_rbk713378201_s tag=TAG20100311T163610 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 11-MAR-10
Starting Control File Autobackup at 11-MAR-10
piece handle=/u02/rman_bkp/rman_ctlbkp/ora_cfc-2526957931-20100311-03 comment=NONE
Finished Control File Autobackup at 11-MAR-10
RMAN> connect auxiliary sys@vtldb
auxiliary database Password:
connected to auxiliary database: VTLDB (not mounted)
RMAN> duplicate target database to vtldb
2> ;
Starting Duplicate Db at 11-MAR-10
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=159 devtype=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: sid=157 devtype=DISK
contents of Memory Script:
   set until scn 557331;
   set newname for datafile 1 to
"/u01/app/oracle/oradata/vtldb/system01.dbf";
   set newname for datafile 2 to
"/u01/app/oracle/oradata/vtldb/undotbs01.dbf";
   set newname for datafile 3 to
"/u01/app/oracle/oradata/vtldb/sysaux01.dbf";
   set newname for datafile 4 to
"/u01/app/oracle/oradata/vtldb/users01.dbf";
   restore
   check readonly
   clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 11-MAR-10
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/11/2010 17:07:11
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restoreRegards,
Poorna Prasad.

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

Can't register a database in RMAN catalog (PL/SQL package not current)

Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
$ rman catalog rman/rman target sys@MPOWER
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
connected to target database: MPOWER (DBID=**********)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===============
RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
RMAN-00571: =================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
I cannot register the target database into the RMAN catalog.
I highly appretiate if you give me an advice on this.
Regards

user13064912 wrote:
Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
$ rman catalog rman/rman target sys@MPOWER
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
connected to target database: MPOWER (DBID=**********)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===============
RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
RMAN-00571: =================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
I cannot register the target database into the RMAN catalog.
I highly appretiate if you give me an advice on this.
RegardsCould you try to run the rman at the target database server (MPOWER), instead of rman catalog server ant try to register your database?
Your rman client is higher than your target server. That could be the problem.
Best Regards,
Gokhan
If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks

Unregistering of a database from RMAN Catalog

Hello,
We had set up RMAN backup though RMAN Catalog for one of our database.
We later decided not to take the backups of this particular database. One of the DBA did something but what we can see now is that -
1. Target database is not registered in the catalog so no information can be gathered rman prompt after connecting to catalog through target database
2. But the recovery catalog "rc_backup_datafile" is showing as if it has old backups
We know that the tapes don't have the backup of this database.
Question - How to remove information from recovery catalog for a database in such a situation where although the database is not registered in the catalog but somehow the information related to old backups still persists in the catalog tables.
Thanks!

Thanks Tycho, for my purpose DBMS_RCVCAT.UNREGISTERDATABASE worked fine.
I have another question though -
We have compressed backup for one of the database/
If I look at backupset by executing "list backupset xxxxxxx;" command it shows the correct compressed value (in GB) of the backup set.
BUT when I look at the rc_backup_datafile table of the rman catalog for the size of of the backupset, it shows the uncompresses size of the backupset. I am using following query -
select BS_KEY,SUM(blocks*block_size)/1024/1024/1024 GB from rc_backup_datafile where DB_NAME='CCSTG04' and BS_KEY=1 group by BS_KEY;
Question - How to check the compressed size of the backupset from the Catalog tables/views?
Thanks for your help on this!
Thanks!
,

To calculate the size of backup for a particular database in RMAN catalog

Hi ALL,
Could you please guide me how I can calculate the size of backup data for a particular database in Recovery Catalog, if I am using Tapes as my backup media for recovery catalog.
Regards
Harpreet Singh

Hi,
I am not Up to the mark of your question ..
If you see the V$log you can get it.. Size of the redo logs can be determined either by examining the file system size or by reading the BYTES column on the V$LOG view. Then Check the number of redo Logs avaialble checked whether they are mirrored or etc., Combining the two figures we have a total redo log data at peak in one day. This is the amount of data that any backup facility or storage of Archive Redo Logs would have to take into account. This figure should be mitigated against the fact that manual switching of redo logs means that not all archived redo logs will be the full size.
- Pavan Kumar N

Clone database using RMAN on Oracle 10g

contents of Memory Script:
shutdown clone;
startup clone nomount ;
executing Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/26/2009 15:55:39
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested canc
el of current operation
how to solve this error?
Kushal

Hi,
but i am not able to configure using enterprise manager. it is always giving error.You could check the OEM forum or raise an SR at metalink.
Hard to tell what is going on without the details.
Regards,
Tycho

Clone database using RMAN

We are using Oracle 10g R2 on Linux.
We have a development database which is in non-archival mode. Can we clone this database without shutting it down using RMAN.

<off-topic>
Paul M. here below what I've seen from the "Overview" tab:
=================================================================================
@PaulM. replied (in response to Moazzam)
We have a development database which is in non-archival mode. Can we clone this database without shutting it down using RMAN. …
5 minutes ago
=================================================================================
I know you, that was impossible that you said this or asked such a question, but my heart missed a beat. I've had to open the discussion or "preview" your response to be sure about what you said.
We all have to take care about what we are quoting here.
</off-topic>
Nicolas.

DBhanging in open stage after creating physical standby database

alter database open read only hanging after creating the standby database using rman.

hi,
when i starts the database in restricted mode it is asking resetlogs;
when i openthe database using the
alter database open resetlogs;
it is showing following errors
alter database open RESETLOGS
Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
ORA-00367: checksum error in log file header
ORA-00338: log 1 of thread 1 is more recent than control file
ORA-00312: online log 1 thread 1: '/dev/stage/oradev/db/apps_st/data/group_1.314.731945051'
RESETLOGS after complete recovery through change 28393568059
Resetting resetlogs activation ID 3821641494 (0xe3c99f16)
Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
ORA-00367: checksum error in log file header
ORA-00322: log 1 of thread 1 is not current copy
ORA-00312: online log 1 thread 1: '/dev/stage/oradev/db/apps_st/data/group_1.314.731945051'
Thu Feb 24 20:05:42 2011
Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
ORA-00316: log 1 of thread 1, type 0 in header is not log file
ORA-00312: online log 1 thread 1: '/dev/stage/oradev/db/apps_st/data/group_1.314.731945051'
Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
ORA-00322: log 2 of thread 1 is not current copy
ORA-00312: online log 2 thread 1: '/dev/stage/oradev/db/apps_st/data/group_2.313.731945057'
Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
ORA-00322: log 3 of thread 2 is not current copy
ORA-00312: online log 3 thread 2: '/dev/stage/oradev/db/apps_st/data/group_3.316.731945065'
Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
ORA-00322: log 4 of thread 2 is not current copy
ORA-00312: online log 4 thread 2: '/dev/stage/oradev/db/apps_st/data/group_4.315.731945069'
Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
ORA-00367: checksum error in log file header
ORA-00322: log 2 of thread 1 is not current copy
ORA-00312: online log 2 thread 1: '/dev/stage/oradev/db/apps_st/data/group_2.313.731945057'
Thu Feb 24 20:05:58 2011
Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
ORA-00367: checksum error in log file header
ORA-00322: log 3 of thread 2 is not current copy
ORA-00312: online log 3 thread 2: '/dev/stage/oradev/db/apps_st/data/group_3.316.731945065'
Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
ORA-00367: checksum error in log file header
ORA-00322: log 4 of thread 2 is not current copy
ORA-00312: online log 4 thread 2: '/dev/stage/oradev/db/apps_st/data/group_4.315.731945069'
thanks in advance

Creating a Standby Database with the Same Directory Structure

Hello gurus,
I am self-learning the feature Oracle Data Guard, so I am testing it on Oracle 10g R2.
At Oracle documentation there is a section F.4.: Creating a Standby Database with the Same Directory Structure*, that explains how to create a standby database with RMAN but there is something that I don´t understand:
In the standby server, I created a database with the SID equal to production database* with the objetive to have the same directory structure, but when I try to startup nomount the standby database with pfile appear this expected error:
ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
So my question is: Is possible have the Same Directory Structure on both: Production and StandBy server?
Thanks in advanced.

Uwe and mseberg: thanks for your quick answers
I have a doubt: How can you have the same directory structure if you have differents SIDs?, for example if you follow the OFA suggestions you would must have:
On Production server: */u01/app/oracle/oradata/PRIMARY/system.dbf*
On StandBy server: */u01/app/oracle/oradata/STANDBY/system.dbf*
Or you created the directory structure manually on StandBy server? For example replacing the string STANDBY* to PRIMARY* before create the database using dbca.
Do you understand my doubt? Excuse me for my english.
Thanks.

Standby Database with RMAN on ASM

Hi,
I am using redhat Linux AS 4 and my database is 10.2.0.1. This database used ASM for storage of data files, control files, online redo logs. Flash recovery area is also configured in the ASM.
I want to create a physical standby database on a different machine by using RMAN. Can someone kindly point me to some easy to follow document? I have scoured the oracle docs, but am more confused than ever.
regards

Step By Step Guide To Create Physical Standby Database Using RMAN [ID 469493.1]
Note: the examples in this document use regular filesystems but the process is the same regardless, ie, in db_file_name_convert use your diskgroup rather than a filesystem (db_file_name_convert=+DG_SOURCE,+DG_TARGET)
another note to complement the first one:
Step By Step Guide On Creating Physical Standby Using RMAN Duplicate In ASM Filesystem For ASM Primary [ID 837102.1]
Edited by: rui_catcuddler on Sep 2, 2010 6:51 AM

10g: Clone database with DBCA silent option

Hello community,
I have tried now for several times to make a clone of my existing database with DBCA and "-silent" option. I could improve my progress in cloning but now I always stick in the following error:
But first, what I have done so far:
1. Created a clone template of my Database with command:
dbca -silent -createCloneTemplate -sourceSID DBORIGIN -templateName myTest.dbc -datafileJarLocation /tmp/oratest
2. Create the clone-database by using the template from (1.) with command:
dbca -silent -createDatabase -templateName myTest.dbc -cloneTemplate -gdbname DBCLONE -sid DBCLONE -datafileJarLocation /tmp/oratest -datafileDestination /oradata -responseFile NO_VALUE -characterset AL32UTF8
Then the progress of execution is shown, it ends with a link to a log file. In this log file I can see the following contents:
==============================
Copying database files
DBCA_PROGRESS : 1%
DBCA_PROGRESS : 3%
DBCA_PROGRESS : 11%
DBCA_PROGRESS : 18%
DBCA_PROGRESS : 26%
DBCA_PROGRESS : 33%
DBCA_PROGRESS : 37%
Creating and starting Oracle instance
ORA-01503: CREATE CONTROLFILE failed
ORA-00200: control file could not be created
ORA-00202: control file: '/oradata/DBCLONE/<OMF_CONTROL_0>'
ORA-27040: file create error, unable to create file
DBCA_PROGRESS : 38%
ORA-00210: cannot open the specified control file
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 4168
ORA-06512: at line 1
ORA-01507: database not mounted
DBCA_PROGRESS : 40%
DBCA_PROGRESS : 41%
ORA-01503: CREATE CONTROLFILE failed
ORA-00200: control file could not be created
ORA-00202: control file: '/oradata/DBCLONE/<OMF_CONTROL_0>'
ORA-27040: file create error, unable to create file
ORA-01507: database not mounted
DBCA_PROGRESS : 46%
DBCA_PROGRESS : 47%
ORA-01219: database not open: queries allowed on fixed tables/views only
ORA-01507: database not mounted
DBCA_PROGRESS : 52%
ORA-01219: database not open: queries allowed on fixed tables/views only
ORA-01507: database not mounted
DBCA_PROGRESS : 53%
DBCA_PROGRESS : 58%
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_DATAPUMP_UTL.REPLACE_DEFAULT_DIR' must be declared
and so on
=====================================================
I have no idea where the "<OMF_CONTROL_0>" comes from. It is nowhere included in my myTest.dbc-file. In my eyes, it looks like that DBCA tries to create the file exactly with this filename - and this fails on Solaris, sure...
Here is, what I have in my template file "myTest.dbc" regarding the control files:
=======================
<ControlfileAttributes id="Controlfile">
<maxDatafiles>100</maxDatafiles>
<maxLogfiles>16</maxLogfiles>
<maxLogMembers>3</maxLogMembers>
<maxLogHistory>1</maxLogHistory>
<maxInstances>8</maxInstances>
<image name="o1_mf_2k1zmdmp_.ctl" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
<image name="o1_mf_2k1zmdvo_.ctl" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
</ControlfileAttributes>
====================================
To be honest, it is the first time that i try to use the DBCA with all these "special" options, especially the silent mode.
Does anyone have an idea what is going wrong in my case described here? What do I or could I change to come to a success clone?
Maybe, you can tell me where I can find some kind of "how to" for creating a clone using the silent-option.
Thanks a lot in advance for helping a newbie! ;-)
Regards
FireFighter

Hello,
finally I was successful in installing the clone of my DB. :-)
You remember that I had problems with the control files and these looked very strange:
control_files=("/oradata/DBCLONE/<OMF_CONTROL_0>","/oradata/DBCLONE/<OMF_CONTROL_1>")
The hint to check the permission in "/oradata" was a good one. The permissions were right all the time, but Oracle's DBCA was not able to create the sub-directory "DBCLONE". When I created it manually before installing the clone, the installation worked fine!
I'm still wondering about this because all other subdirectories were created automatically during running "dbca" (e.g. all subdirectories "DBCLONE" needed below the $ORACLE_BASE/admin/-directory like adump,bdump and so on...).
And i'm wondering about the names of the control files:
I expected that these strange OMF-names would be replaced by a "normal" file name. But "dbca" was able to create the files exactly with the names "<OMF_CONTROL_0>" and "<OMF_CONTROL_0>"...
As I had understood so far from OMF-concept, isn't the idea that Oracle takes care of file-naming instead of myself? I mean it can't be that I have to enter the template for DBCA and manually enter the control files names...
I'm still close to the thought that it be a bug that isn't documented until now. Maybe, when I have some time left I will open a service request at metalink.
If you are interested in this I will keep you informed on this topic. The other way round I stay interested in your opions and hints for using "dbca" to make and install a DB-clone.
Thanks again for you effort to help me as a rookie in Oracle. :-)
Regards
FireFighter

Create a new Database in an other server using a copie of RMAN backup

Hi all,
I want to create an other instance for our production database. We have disk and tape in rman backup. My question is can i create a new database using our disk backup in an other server?
If some procedure or steps is there, email it to my adresse [email protected]
Hamid.
Thanks

By means of the use of Recovery Manager it is possible to duplicate a database out from a previously taken rman backup. The method will be outlined in the next few lines.
Let's assume a source database named SRCDB and the target database, named GEMINI. A unix like environment is assumed, but it can be implemented on windows as well, just beware of the particular Oracle implementation on a windows platform (orapwd file name, service creation, path format)
1. Create a password file for the Cloned (GEMINI) instance:
orapwd file=/u01/app/oracle/product/9.2.0.1.0/dbs/orapwGEMINI password=password entries=10
2. Configure tnsnames.ora and listner.ora
Properly identify the database at the tnsnames.ora and have the instance manually registered against the listener.ora files, both files located at the $ORACLE_HOME/network/admin directory.
2.a Manually register the database against the listener (listener.ora)
(SID_DESC =
(ORACLE_HOME = /u01/app/oracle/product/9.2.0.1.0)
(SID_NAME = GEMINI)
2.b Added the target GEMINI to the tnsnames.ora
GEMINI =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = myhost.mydomain.com)(PORT = 1521))
(CONNECT_DATA =
(ORACLE_SID = GEMINI)
2.c Reload the listener
lsnrctl reload
3. Create a new init.ora for the cloned database.
Next create an init.ora file for the cloned database. In case the same paths cannot be used on the target host, either because it is the same source host or because those paths are not reproducible on the target, then DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT may be required to be defined
DB_NAME=GEMINI
CONTROL_FILES=(/u02/oradata/GEMINI/control01.ctl,
/u02/oradata/GEMINI/control02.ctl,
/u02/oradata/GEMINI/control03.ctl)
# Convert file names to allow for different directory structure.
DB_FILE_NAME_CONVERT=(/u02/oradata/SRCDB/,/u02/oradata/GEMINI/)
LOG_FILE_NAME_CONVERT=(/u01/oradata/SRCDB/,/u01/oradata/GEMINI/)
# block_size and compatible parameters must match those of the source database
DB_BLOCK_SIZE=8192
COMPATIBLE=9.2.0.0.0
4. Connect to the cloned instance
ORACLE_SID=GEMINI; export ORACLE_SID
sqlplus /nolog
conn / as sysdba
5. Create an SPFILE based on the init.ora
CREATE SPFILE FROM PFILE='/u01/app/oracle/admin/GEMINI/pfile/init.ora';
6. Start the database in NOMOUNT mode:
STARTUP FORCE NOMOUNT;
7. Connect to the TARGET, CATALOG and AUXILIARY databases.
By means of the rman three connections are open, one for the Source Database (SOURCEDB), another for the Catalog database (RCAT), and one more for the cloned database (GEMINI)
ORACLE_SID=GEMINI; export ORACLE_SID
rman TARGET sys/password@SRCDB CATALOG rman/rman@RCAT AUXILIARY /
8. Complete or Incomplete clone (recover)
From the rman the database using one of the following commands:
8.a Clone the database by means of a complete recover.
DUPLICATE TARGET DATABASE TO GEMINI;
8.b Clone the database up to a defined point in time in the past by means of an incomplete recover
DUPLICATE TARGET DATABASE TO GEMINI UNTIL TIME 'SYSDATE-2';
9. Process finished.
Once the process is finished, the newly created GEMINI database is ready to be used as an independent new cloned database.
Ref. RMAN Clone a Database
~ Madrid

Create a clone database form rman catalog !

Similar Messages

Maybe you are looking for