RMAN error while cloning hot database. [message #74387] |
Thu, 02 December 2004 06:54 |
Natraj
Messages: 53 Registered: March 2003
|
Member |
|
|
Hi,
i am creating a new database 9.2.0.4 on solaris by cloning a production database (hot)using RMAN.I am getting the following error.when i am executing the script.
connected to recovery catalog database
connected to target database: xxxxxx (DBID=yyyyyyyy)
connected to auxiliary database (not started)(my comments:i feel there is a problem here, i m starting the database in nomount stage but it is giving error database not started..)
executing command: SET until clause
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 12/01/2004 15:41:47
RMAN-06403: could not obtain a fully authorized session
RMAN-04006: error from auxiliary database: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory.the tnsnames and listener.ora are properly configured. i cannot shutdown the hot database.i have tried shutting down and restarting the target database(the database i am trying to clone.) but the error persists. I looked for solution in many sites.but didnt find the exact answer.kindly help
|
|
|
|
|
|
|
|
|
|
Re: RMAN error while cloning hot database. [message #74395 is a reply to message #74394] |
Thu, 02 December 2004 11:20 |
Natraj
Messages: 53 Registered: March 2003
|
Member |
|
|
i am executing the script from production mchine.this is correct as we have proper procedures.and i have refreshed databases in this manner.however this is the first time i created a new database previously i used to refresh already created dataabases. i have made the appropriate entry in tnsnames.ora of production and tnsping is working. also i updated the listener.ora file in the auxiliary database machine.to include the sid of auxiliary database.
|
|
|
|
|
|
Re: RMAN error while cloning hot database. [message #74399 is a reply to message #74396] |
Thu, 02 December 2004 11:59 |
Natraj
Messages: 53 Registered: March 2003
|
Member |
|
|
can i just mount the database without using RMAN.i guess probs r with env variables.password files etc. can i just run startup mount? the alertsid.log file of aux db is ok.i only do startup nomount or shu immediate.now i am getting uncomfortable with RMAN.!!
|
|
|
|
|
|
|
|
Re: RMAN error while cloning hot database. [message #74408 is a reply to message #74407] |
Mon, 06 December 2004 09:30 |
|
Mahesh Rajendran
Messages: 10708 Registered: March 2002 Location: oracleDocoVille
|
Senior Member Account Moderator |
|
|
assuming, something like this is your script.
assuming you have scripts that take care of fileName renaming, TIMESTAMP for TSPITR etc etc
wt
# # and --- are comments
#!define environmentvariables in your shell
export ORACLE_SID=AUX_SID --- sid of aux database to be clone
export ORACLE_BASE=xx
export ORACLE_HOME=xxx
export PATH:$PATH:$ORACLE_HOME/bin
export NLS_DATE_FORMAT='MON DD YYYY HH24:MI:SS'
rman msglog '/tmp/duplicate.log' <<EOF
connect target sys/sys@target --- database_or_primarydatabase
connect catalog rmanuser/pass@rmandb --- rman catalog database
connect auxiliary sys/password --- this is you auxillary database
--- if you using connnectstring , change to sys/pass@aux_connecstring.
run {
allocate channel ch1 type disk;
allocate channel ch2 type disk;
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
--- OTHER COMMANDS
--- Do your business
duplicate target database to AUX_SID
PFILE = initAUX_SID.ora
--- OTHER COMMANDS
--- Do your business
}
exit
EOF
here you have issues with duplicate command.
The issue is your Environment is NOT identifieing the AUX instance in NOMOUNT stage.
possiblieites?
1. your passswordfile is corrupt.
2. Your environment is not set right.
3. Your initsid.ora is NOT understood/identified.
4. since you use tnsentries, your listener is NOT configured properly.
now try replacing
duplicate target database to AUX_SID
with run commands as shown here ( strip the "run". ).
add only sql "alter database mount";
sql "alter database open";
http://www.orafaq.com/forum/t/27172/0/
[Updated on: Fri, 18 February 2005 23:32] Report message to a moderator
|
|
|
Re: RMAN error while cloning hot database. [message #74416 is a reply to message #74408] |
Tue, 07 December 2004 05:35 |
Natraj
Messages: 53 Registered: March 2003
|
Member |
|
|
Hi mahesh,
the problem wasw ith the listener, i had 2 entries of same sid in listener.ora, and it wa staking the latter entry with version 8.1.7 whereas my current entry of 9.2.0 was much above it.
Thanks for your help
|
|
|