 RMAN Duplication failing with RMAN-06136 [message #180669] |
Tue, 04 July 2006 14:00  |
omoni
Messages: 2
Registered: July 2006
Location: London
|
Junior Member |
|
|
Hi All,
I have a production database on HP-UX 11.11. The database is 9.2.0.6. I also have a recovery catalog on Windows (Oracle 10.2)
I am trying to duplicate the prodcution to our DR Site using RMAN.
I have followed all the required steps in the RMAN Documentation. All the filesystems are the same on the DR site and I have created the AUX database using an spfile. I can connect to the AUX database from the production database via TNSNAMES and shut it down and startup nomount so I know the spfile works but I am having alot of issues during duplication.
We normally backup to TAPE using netbackup 5.1.
The first issue i was having was that the restore seemed to hang for a long time after restoring the last file. Netbackup will show that the restore is complete but RMAN will just hang and do nothing. After dialogue with Oracle they suggested using one AUX channel which seemed to get rid of that issue but now the duplication is failing with the error message below.
I dont understand it because it says not connected to Oracle but the AUX database is up and I can connect from this server.
The error meesage is below and after that is the script that I am using. Anything else that you need please ask.
Thanks
Error message
channel c1: restore complete
Finished restore at 04-JUL-06
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "finukprd" RESETLOGS ARCHIVELOG
MAXLOGFILES 6
MAXLOGMEMBERS 3
MAXDATAFILES 800
MAXINSTANCES 1
MAXLOGHISTORY 680
LOGFILE
GROUP 1 ( '/redo1/FINUKPRD/log01a.rdo', '/redo2/FINUKPRD/log01b.rdo' ) SIZE 536870912 REUSE,
GROUP 2 ( '/redo1/FINUKPRD/log02a.rdo', '/redo2/FINUKPRD/log02b.rdo' ) SIZE 536870912 REUSE,
GROUP 3 ( '/redo1/FINUKPRD/log03a.rdo', '/redo2/FINUKPRD/log03b.rdo' ) SIZE 536870912 REUSE
DATAFILE
'/u01/oradata/FINUKPRD/system01.dbf'
CHARACTER SET UTF8
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-10038: database session for channel clone_default terminated unexpectedly
RMAN-03002: failure of Duplicate Db command at 07/04/2006 04:57:15
RMAN-06136: ORACLE error from auxiliary database: ORA-03114: not connected to ORACLE
RMAN-06097: text of failing SQL statement: CREATE CONTROLFILE REUSE SET DATABASE "finukprd" RESETLOGS ARCHIVELOG
RMAN-06099: error occurred in source file: krmk.pc, line: 7607
Script
CONNECT TARGET /;
CONNECT CATALOG rman/xxxx@rmancat;
CONNECT AUXILIARY sys/xxxxx@finukprd_copy;
RUN
{
set until time "to_date('Jul 02 2006 18:32:00','Mon DD YYYY HH24:MI:SS')";
#parameter above used for point time recovery
ALLOCATE auxiliary CHANNEL c1 TYPE 'SBT_TAPE' parms="ENV=(NB_ORA_CLIENT=psprddb1-bkp,NB_ORA_SERV=spica-bkp,NB_O
RA_POLICY=psprddb1_oracle_FINUKPRD)";
DUPLICATE TARGET DATABASE TO finukprd
NOFILENAMECHECK;
release channel c1;
|
|
|
|
|
|
| Re: RMAN Duplication failing with RMAN-06136 [message #180779 is a reply to message #180682] |
Wed, 05 July 2006 04:16  |
omoni
Messages: 2
Registered: July 2006
Location: London
|
Junior Member |
|
|
Hi Mahesh,
Then why are you using FINUKPRD?
>> DUPLICATE TARGET DATABASE TO finukprd
FINUKPRD is the name of the SID. This is what you use for the clone not the tnsnames entry.
The db_name is finukprd for both production and clone.
Thanks
Subject: Re: RMAN Duplication failing with RMAN-06136 Author: Mahesh Rajendran Date: Tue, 04 July 2006 15:01
Could you explain your environment?
Quote:
CONNECT TARGET /;
CONNECT CATALOG rman/xxxx@rmancat;
CONNECT AUXILIARY sys/xxxxx@finukprd_copy;
With above i understand TARGETDB is your productionn database.
RMANCAT is your RMAN catalog.
finukrd_copy is your database_that_would_be_duplicated_from_TARGET.
Right?
Then why are you using FINUKPRD?
>> DUPLICATE TARGET DATABASE TO finukprd
To make things a little prettier, set your environment exclusively inside the shell script.
#Just a sample duplication script outlining the procedure.
#
#!/usr/bin/bash
export ORACLE_SID=your_auxillary_sid or database_that_would_be_duplicated_from_TARGET
rman msglog '/tmp/duplicate_prod_standby.log' <<EOF
connect target sys/sys@targetdatabase
connect catalog rman/rman@rmancat
connect auxiliary sys/sys_password_for_auxillary
run {
allocate channel ch1 type your_type;
allocate channel chn type your_type;
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE your_type;
set until time ........your TSPITR time frame ......
duplicate target database to database_that_would_be_duplicated_from_TARGET
...
...
...
}
exit;
EOF;
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
