Home » RDBMS Server » Backup & Recovery » Duplicate RMAN issue (Oracle, 9.2.0.1, Windows)
Duplicate RMAN issue [message #361241] Tue, 25 November 2008 08:43 Go to next message
shekharnegi12
Messages: 52
Registered: October 2008
Member
Hello Everyone,

I have a question related to RMAN duplicate function. Here's the problem: In order to perform the duplicate command I first created a different database using database configuration assistant that created the service and the listener for me along with the init file. I made the control file and redo log files in the same file system format as my target database.

I then connected to the target database (one from which I'm going to get the data) using the sys account
RMAN> connect Target sys/password@databasesid
connected to target database: databasesid (DBID=#########)
it got connect the target database

I then connect to the target catalog using rman account

RMAN> connect catalog rman/password@databasesid
connected to recovery catalog database

Then I connected to the auxiliary database(database where I want to copy the data to)
RMAN>connect auxiliary sys/password@auxiliaydatabase
connected to auxiliary database: auxiliaydatabase (DBID=######)

Once connections are made I gave the following command to start duplication
RMAN> DUPLICATE TARGET DATABASE TO auxiliarydatabase;

and I got the following error:
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10039: error encountered while polling for RPC completion on channel clone_default
RMAN-10006: error running SQL statement: select act from x$ksusex where sid=:1 and serial=:2
RMAN-10002: ORACLE error: ORA-12571: TNS: packet writer failure
RMAN-03002: failure of Duplicate Db command at 06/30/2005 06:24:28
RMAN-06136: ORACLE error from auxiliary database: ORA-12571: TNS: packet writer failure

Can anyone help?

Thanks,
SN
Re: Duplicate RMAN issue [message #361255 is a reply to message #361241] Tue, 25 November 2008 09:42 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10672
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
Check the alert sid log for the auxillary instance and post the relevant contents.
Re: Duplicate RMAN issue [message #361256 is a reply to message #361255] Tue, 25 November 2008 09:53 Go to previous messageGo to next message
shekharnegi12
Messages: 52
Registered: October 2008
Member
I have copied the part that is relevant to the duplicate process from the alert sid log file:


starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Mon Nov 24 16:39:44 2008
alter database mount exclusive
Mon Nov 24 16:39:48 2008
Successful mount of redo thread 1, with mount id #######.
Mon Nov 24 16:39:48 2008
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Mon Nov 24 16:39:48 2008
alter database open
Mon Nov 24 16:39:48 2008
LGWR: Primary database is in CLUSTER CONSISTENT mode
Thread 1 opened at log sequence 4
Current log# 3 seq# 4 mem# 0: E:\ORACLE\ORADATA\databasesid\REDO03A.LOG
Current log# 3 seq# 4 mem# 1: C:\ORACLE\ORADATA\databasesid\REDO03B.LOG
Successful open of redo thread 1.
Mon Nov 24 16:39:49 2008
SMON: enabling cache recovery
Mon Nov 24 16:39:49 2008
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Mon Nov 24 16:39:49 2008
SMON: enabling tx recovery
Mon Nov 24 16:39:49 2008
Database Characterset is WE8MSWIN1252
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Mon Nov 24 16:42:46 2008
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 5

All dispatchers and shared servers shutdown
Mon Nov 24 16:42:51 2008
ALTER DATABASE CLOSE NORMAL
Mon Nov 24 16:42:51 2008
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Nov 24 16:42:51 2008
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 4
Successful close of redo thread 1.
Mon Nov 24 16:42:52 2008
Completed: ALTER DATABASE CLOSE NORMAL
Mon Nov 24 16:42:52 2008
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Mon Nov 24 16:42:55 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.1.0.
System parameters with non-default values:
processes = 150
timed_statistics = TRUE
shared_pool_size = 150994944
large_pool_size = 92274688
java_pool_size = 25165824
control_files = C:\oracle\oradata\databasesid\CONTROL01.CTL, C:\oracle\oradata\databasesid\CONTROL02.CTL, C:\oracle\oradata\databasesid\CONTROL03.CTL
db_block_size = 8192
db_cache_size = 444596224
compatible = 9.2.0.0.0
db_file_multiblock_read_count= 16
fast_start_mttr_target = 300
undo_management = AUTO
undo_tablespace = UNDOTBS1
undo_retention = 10800
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = databasesid
dispatchers = (PROTOCOL=TCP) (SERVICE=databasesidXDB)
job_queue_processes = 10
hash_join_enabled = TRUE
background_dump_dest = C:\oracle\admin\databasesid\bdump
user_dump_dest = C:\oracle\admin\databasesid\udump
core_dump_dest = C:\oracle\admin\databasesid\cdump
sort_area_size = 524288
db_name = databasesid
open_cursors = 300
star_transformation_enabled= FALSE
query_rewrite_enabled = FALSE
pga_aggregate_target = 197132288
aq_tm_processes = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
CJQ0 started with pid=8
QMN0 started with pid=9
Mon Nov 24 16:42:58 2008
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...

Thanks,
SN
Re: Duplicate RMAN issue [message #361289 is a reply to message #361256] Tue, 25 November 2008 12:56 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10672
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
You sure this is from your aux instance?
Re: Duplicate RMAN issue [message #361290 is a reply to message #361289] Tue, 25 November 2008 12:59 Go to previous messageGo to next message
shekharnegi12
Messages: 52
Registered: October 2008
Member
Positive. I got it from Oracle_base\admin\auxiliarydatabase\bdump
and in there alert_auxiliarydatabase.log
Re: Duplicate RMAN issue [message #361508 is a reply to message #361290] Wed, 26 November 2008 12:28 Go to previous message
Mahesh Rajendran
Messages: 10672
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
Not sure what you missed.
I would start again from basics.
First, try to establish an sql session to aux instance with proper tns entries and try
sqlplus "sys/password@auxiliaydatabase as sysdba"

Previous Topic: delete obsolete true but archive logs didnt delete
Next Topic: Duplicate RMAN problem
Goto Forum:
  


Current Time: Sat Dec 10 14:49:21 CST 2016

Total time taken to generate the page: 0.09280 seconds