RMAN Cloning issues [message #527621] |
Wed, 19 October 2011 06:19 |
sekharsomu
Messages: 72 Registered: December 2008
|
Member |
|
|
The error i am getting is
RMAN> duplicate target database to esstest
2> ;
Starting Duplicate Db at 19-OCT-11
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/19/2011 16:09:51
RMAN-06403: could not obtain a fully authorized session
RMAN-04006: error from auxiliary database: ORA-01034: ORACLE not available
what i have done to resolve?
Quote:Recreated my listner and tnsnames
have checked the tnsping
add a parameter remote_login_passwordfile=exclusive to auxilary's pfile
Spent nearly 5 hrs on books and net tried adding inbound parameter to listner either that didnt help
none of them helped
This all what a done:
i have tried to clone between 2 system(Same Configuration)
This are the steps i have done:
@aux:
1.create a oracle home @auxilary<esstest>
2.create similar database structure in esstest
3.create a same backup location structure in esstest
4.moved a pfile from source<essprod> @ ora_home/dbs and made
necessary changes and add parameters db_file_name_convert,
log_file_name_convert
5.add parameter remote_login_passwordfile=exclusive and create
password file in dbs directory
6.create a new environmental file with new sid esstest
7. created a new listner and started it
@Source
1.ran the env file for essprod
2.startup successful
3.configured tnsnames.ora
4.tried to tnsping result:Successful
@AUX:
1.Started database in nomount
@source:
1.rman target=/ auxilary =sys/oracle@AUXDB
2.Succesful
ISSUE:
When try the following command in rman
RMAN>duplicate target database to esstest
errors are as follows:
RMAN> duplicate target database to esstest
2> ;
Starting Duplicate Db at 19-OCT-11
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/19/2011 16:09:51
RMAN-06403: could not obtain a fully authorized session
RMAN-04006: error from auxiliary database: ORA-01034: ORACLE not available
various configs at Aux:
pfile <initesstest.ora>
essprod.__db_cache_size=239075328
essprod.__java_pool_size=4194304
essprod.__large_pool_size=4194304
essprod.__shared_pool_size=62914560
essprod.__streams_pool_size=0
*.background_dump_dest='/prod/esstest/admin/bdump'
*.compatible='10.2.0'
*.control_files='/prod/esstest/oradata/contro01.dbf'
*.core_dump_dest='/prod/esstest/admin/cdump'
*.db_block_size=2048
*.db_name='esstest'
*.log_archive_dest='/backup/archive'
*.sga_target=300M
*.undo_management='auto'
*.undo_tablespace='undotbs'
*.user_dump_dest='/prod/esstest/admin/udump'
db_file_name_convert='/prod/essqa/ordata','/prod/esstest/oradata'
log_file_name_convert='/prod/essqa/ordata','/prod/esstest/oradata'
remote_login_passwordfile=exclusive
Lisneter@Aux:
# listener.ora Network Configuration File: /a01/oracle/product/10.2.0//network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = esstest)
(ORACLE_HOME = /a01/oracle/product/10.2.0/)
)
)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = som2.fzl.com)(PORT = 1521))
)
)
cross verified all mypath everthing exist
@Source
tnsnames.ora
AUXDB =
(DESCRIPTION =
(ADDRESS = (HOST = som2.fzl.com)(PORT = 1521)(PROTOCOL = tcp))
(CONNECT_DATA =
(SID = esstest)
)
)
How do i resolve this error
[Updated on: Wed, 19 October 2011 06:26] Report message to a moderator
|
|
|
Re: RMAN Cloning issues [message #527622 is a reply to message #527621] |
Wed, 19 October 2011 06:42 |
|
Mahesh Rajendran
Messages: 10708 Registered: March 2002 Location: oracleDocoVille
|
Senior Member Account Moderator |
|
|
Quote:When try the following command in rman
RMAN>duplicate target database to esstest
Where are you executing this from? which node?
How exactly are you connecting? please post the session.
To keep it simple,
I would try these, executing RMAN from the node you are duplicating to. Something like this.
export ORACLE_SID=yourAuxSIX
rman > connect target "connect to your target@othernode".
rman > connect Aux
[Updated on: Wed, 19 October 2011 06:50] Report message to a moderator
|
|
|
|
|
|
|
Re: RMAN Cloning issues [message #527642 is a reply to message #527629] |
Wed, 19 October 2011 08:51 |
sekharsomu
Messages: 72 Registered: December 2008
|
Member |
|
|
Thanks for your sugesstion it did work
this is what i have done
1.created an password file @source<essprod>
2.created a tnsnames.ora entry @auxiliary
and then ...
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Oct 19 19:08:18 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect target sys/oracle@sourc
connected to target database: ESSPROD (DBID=135535548)
RMAN> connect auxiliary /
connected to auxiliary database: ESSTEST (not mounted)
RMAN> duplicate target database to esstest;
Starting Duplicate Db at 19-OCT-11
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=36 devtype=DISK
contents of Memory Script:
{
set until scn 235144;
set newname for datafile 1 to
"/prod/esstest/oradata/system01.dbf";
set newname for datafile 2 to
"/prod/esstest/oradata/undotbs01.dbf";
set newname for datafile 3 to
"/prod/esstest/oradata/sysaux01.dbf";
set newname for datafile 4 to
"/prod/esstest/oradata/users01.dbf";
set newname for datafile 5 to
"/prod/esstest/oradata/users02.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
executing command: SET NEWNAME
Starting restore at 19-OCT-11
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /prod/esstest/oradata/system01.dbf
restoring datafile 00002 to /prod/esstest/oradata/undotbs01.dbf
restoring datafile 00003 to /prod/esstest/oradata/sysaux01.dbf
restoring datafile 00004 to /prod/esstest/oradata/users01.dbf
restoring datafile 00005 to /prod/esstest/oradata/users02.dbf
channel ORA_AUX_DISK_1: reading from backup piece /backup/rman/ESSPROD_135535548 _14_20111019
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/backup/rman/ESSPROD_135535548_14_20111019 tag=TAG20111019T190028
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:26
Finished restore at 19-OCT-11
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "ESSTEST" RESETLOGS ARCHIVE LOG
MAXLOGFILES 16
MAXLOGMEMBERS 2
MAXDATAFILES 30
MAXINSTANCES 1
MAXLOGHISTORY 292
LOGFILE
GROUP 1 ( '/prod/esstest/oradata/redolog01.log' ) SIZE 50 M REUSE,
GROUP 2 ( '/prod/esstest/oradata/redolog02.log' ) SIZE 50 M REUSE
DATAFILE
'/prod/esstest/oradata/system01.dbf'
CHARACTER SET UTF8
contents of Memory Script:
{
switch clone datafile all;
}
executing Memory Script
released channel: ORA_AUX_DISK_1
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=764968247 filename=/prod/esstest/oradata/undot bs01.dbf
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=764968247 filename=/prod/esstest/oradata/sysau x01.dbf
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=764968247 filename=/prod/esstest/oradata/users 01.dbf
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=764968247 filename=/prod/esstest/oradata/users 02.dbf
contents of Memory Script:
{
set until scn 235144;
recover
clone database
delete archivelog
;
}
executing Memory Script
executing command: SET until clause
Starting recover at 19-OCT-11
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=36 devtype=DISK
starting media recovery
channel ORA_AUX_DISK_1: starting archive log restore to default destination
channel ORA_AUX_DISK_1: restoring archive log
archive log thread=1 sequence=17
channel ORA_AUX_DISK_1: reading from backup piece /backup/rman/ESSPROD_135535548 _16_20111019
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/backup/rman/ESSPROD_135535548_16_20111019 tag=TAG20111019T190136
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
archive log filename=/backup/archive/1_17_764880501.dbf thread=1 sequence=17
channel clone_default: deleting archive log(s)
archive log filename=/backup/archive/1_17_764880501.dbf recid=1 stamp=764968247
media recovery complete, elapsed time: 00:00:01
Finished recover at 19-OCT-11
contents of Memory Script:
{
shutdown clone;
startup clone nomount ;
}
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 314572800 bytes
Fixed Size 1219160 bytes
Variable Size 96470440 bytes
Database Buffers 213909504 bytes
Redo Buffers 2973696 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "ESSTEST" RESETLOGS ARCHIVE LOG
MAXLOGFILES 16
MAXLOGMEMBERS 2
MAXDATAFILES 30
MAXINSTANCES 1
MAXLOGHISTORY 292
LOGFILE
GROUP 1 ( '/prod/esstest/oradata/redolog01.log' ) SIZE 50 M REUSE,
GROUP 2 ( '/prod/esstest/oradata/redolog02.log' ) SIZE 50 M REUSE
DATAFILE
'/prod/esstest/oradata/system01.dbf'
CHARACTER SET UTF8
contents of Memory Script:
{
set newname for tempfile 1 to
"/prod/esstest/oradata/tempx01.dbf";
switch clone tempfile all;
catalog clone datafilecopy "/prod/esstest/oradata/undotbs01.dbf";
catalog clone datafilecopy "/prod/esstest/oradata/sysaux01.dbf";
catalog clone datafilecopy "/prod/esstest/oradata/users01.dbf";
catalog clone datafilecopy "/prod/esstest/oradata/users02.dbf";
switch clone datafile all;
}
executing Memory Script
executing command: SET NEWNAME
renamed temporary file 1 to /prod/esstest/oradata/tempx01.dbf in control file
cataloged datafile copy
datafile copy filename=/prod/esstest/oradata/undotbs01.dbf recid=1 stamp=7649682 55
cataloged datafile copy
datafile copy filename=/prod/esstest/oradata/sysaux01.dbf recid=2 stamp=76496825 5
cataloged datafile copy
datafile copy filename=/prod/esstest/oradata/users01.dbf recid=3 stamp=764968256
cataloged datafile copy
datafile copy filename=/prod/esstest/oradata/users02.dbf recid=4 stamp=764968256
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=764968255 filename=/prod/esstest/oradata/undot bs01.dbf
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=764968255 filename=/prod/esstest/oradata/sysau x01.dbf
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=764968256 filename=/prod/esstest/oradata/users 01.dbf
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=764968256 filename=/prod/esstest/oradata/users 02.dbf
contents of Memory Script:
{
Alter clone database open resetlogs;
}
executing Memory Script
database opened
Finished Duplicate Db at 19-OCT-11
But as per my knowledge the pervious approach i followed is the one i have done many times why did it fail? Is there any suggestion u can make instead of doing it from auxiliary end
as i follow a similar approach in creating a stand by i just want to know a solution to th problem below:
RMAN> duplicate target database to esstest
2> ;
Starting Duplicate Db at 19-OCT-11
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/19/2011 16:09:51
RMAN-06403: could not obtain a fully authorized session
RMAN-04006: error from auxiliary database: ORA-01034: ORACLE not available
[Updated on: Wed, 19 October 2011 08:56] Report message to a moderator
|
|
|
Re: RMAN Cloning issues [message #527643 is a reply to message #527641] |
Wed, 19 October 2011 08:58 |
sekharsomu
Messages: 72 Registered: December 2008
|
Member |
|
|
John Watson wrote on Wed, 19 October 2011 08:49You say you started the esstest instance, but RMAN says you didn't. Are you sure it is in fact started?
Yep i did start my instance in nomount state i have cross verfied it
|
|
|
Re: RMAN Cloning issues [message #527647 is a reply to message #527643] |
Wed, 19 October 2011 09:20 |
John Watson
Messages: 8964 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
Yes, it is started now. But it wasn't. Your screen shot is absolutely clear on this:
connected to auxiliary database (not started)
That's why your first try to duplicate failed. No problem, you have it sorted now.
|
|
|
|
|
|
Re: RMAN Cloning issues [message #527670 is a reply to message #527664] |
Wed, 19 October 2011 12:58 |
sekharsomu
Messages: 72 Registered: December 2008
|
Member |
|
|
As you said i tried connecting from source and it did fail:
[oracle@som1 prod]$ sqlplus sys/oracle@auxdb
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Oct 19 23:25:14 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
As far as env there just my bash profile setting:
export ORACLE_HOME=/a01/oracle/product/10.2.0
export PATH=$ORACLE_HOME/bin:$PATH
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export ORACLE_SID=esstest
Now how can i solve this issue?
[Updated on: Wed, 19 October 2011 13:01] Report message to a moderator
|
|
|
|
|
Re: RMAN Cloning issues [message #527675 is a reply to message #527672] |
Wed, 19 October 2011 13:15 |
sekharsomu
Messages: 72 Registered: December 2008
|
Member |
|
|
no i just gave u sample from my auxiliary. to show what are contents of my env file
the essprod.env which i ran in source contain SID = essprod So no luck there
[oracle@som1 prod]$ cat essprod.env
export ORACLE_HOME=/a01/oracle/product/10.2.0
export PATH=$ORACLE_HOME/bin:$PATH
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export ORACLE_SID=essprod
[oracle@som1 prod]$ sqlplus sys/oracle@auxdb
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Oct 19 23:44:51 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
|
|
|
Re: RMAN Cloning issues [message #527676 is a reply to message #527671] |
Wed, 19 October 2011 13:17 |
sekharsomu
Messages: 72 Registered: December 2008
|
Member |
|
|
BlackSwan wrote on Wed, 19 October 2011 13:06>sqlplus sys/password@aux
flawed test above.
"SYS" requires "as sysdba"
so do as below
sqlplus scott/tiger@aux
@REMOTE does not depend upon local environmental variables,
with possible exception being TNS_ADMIN
But how can i create user such a scott in auxiliary databasewithout cloning the database there <auxiliary>
yeah i do understand that this is a flawed test but is there some solution to resolve my problem mentioned in the beginning of the thread
[Updated on: Wed, 19 October 2011 13:21] Report message to a moderator
|
|
|
|
|
Re: RMAN Cloning issues [message #527685 is a reply to message #527678] |
Wed, 19 October 2011 14:05 |
John Watson
Messages: 8964 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
First, please don't post those JPG files: many people can't download them. Use copy/paste to copy the information as characters.
Second, creating your password file. To say "that didnt work" does not give us much information! You must post the detail. But I can tell you te problem: your syntax is incomplete, you need to include "entries=5" or something similar.
Third, the simplest test to see what instances (if any) are running is this:
ps -ef|grep smon
|
|
|
Re: RMAN Cloning issues [message #527729 is a reply to message #527621] |
Wed, 19 October 2011 23:00 |
sekharsomu
Messages: 72 Registered: December 2008
|
Member |
|
|
hey guys finally it worked!
@Source
i tried connecting to auxiliary from source
sqlplus sys/oracle@auxdb as sysdba
sqlplus>startup nomount
Now when i connected from RMAN it showed esstest(nomount)
and the cloning was done.
but i still didn't figure out why was rman unable recognize the state of the database if i made a startup nomount in the Auxiliary directly
[Updated on: Wed, 19 October 2011 23:02] Report message to a moderator
|
|
|