RMAN incompatability
Hi
I am getting the error
RMAN-06429: TARGET database is not compatible with this version of RMAN
my rman database is 10g and target database is 9i.
Any idea how to resolve the problem without upgrade of the targer db to 10g
Hi
I am getting the error
AN-06429: TARGET database is not compatible with this
version of RMAN
y rman database is 10g and target database is 9i.
Any idea how to resolve the problem without upgrade
of the targer db to 10gWhat are you trying to achieve? If a backup of the 9i database that gets recorded in the 10g catalog then simply run rman from the 9i server (or a 9i client). If an upgrade or something else then a different approach might be warranted.
Niall Litchfield
http://www.orawin.info
Similar Messages
-
Hi All,
Working on DB v10.2.0.3.0 and 10.1.0.5 .0
OS:AIX 64 bits
We used to get the output when connecting from 10.2.0.3.0 to RMAN 10.2.0.3.0 as below:
SQL> select distinct object_type from rc_rman_status;
OBJECT_TYPE
ARCHIVELOG
DB FULL
But the same query doesn't work when connecting from 10.1.0.5 .0 to RMAN v10.2.0.3.0:
SQL> select distinct object_type from rc_rman_status;
OBJECT_TYPE
The above output is blank.
Also on doing some research,OBJECT_TYPE column doesn't exist in rc_rman_status for 10.1.0.5.0.
Oracle® Database Recovery Manager Reference
10g Release 1 (10.1)
Part Number B10770-02
RC_RMAN_STATUS
URL: http://download.oracle.com/docs/cd/B14117_01/server.101/b10770/rcviews28.htm#RCMRF381
So is there any other table or view apart from rc_rman_status where from we can extract this information - DB Full or Archivelog since Object_type column is not present in rc_rman_status in v10.1.0.5.
Thanks for your time!
Regards,Please configure RMAN settings and try to run full backup again.
RMAN> show all; --> will display current settings.
Arun wrote:
Hi,
I have registered the database and fired the full backup and getting the following message
channel ORA_DISK_1: starting piece 1 at 06-OCT-11
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 10/06/2011 01:41:22
ORA-19502: write error on file "/u01/app/oracle/product/dbname/dbs/df1c.dbname.t763781956.s6.p1", blockno 610433 (blocksize=8192)See, the backup pieces are going to $ORACLE_HOME/dbs directory.
Arun wrote:
ORA-27072: File I/O error
SVR4 Error: 25: Inappropriate ioctl for device
Additional information: 4
Additional information: 610433
Additional information: 841728
Do I need to reset the incarnation ? Please help me in this
Regards
ArunRegards,
Suresh.GV
Edited by: sureshgali on Oct 6, 2011 1:22 AM -
Centralized RMAN Catalog Database
Hello,
I have two 10g R2 databases on two separate servers.
I am trying to centralize my RMAN backup by creating a RMAN_DATABASE in 11G.
- I create RMAN_DATABASE
- I created RMAN user and tablespaces
- I edited my TNSNAMES.ORA so that I could connect to my two 10G R2 databases
When I run the command:
rman catalog=rman/password@rman_database target=sys/password@10g_db1I get the following error:
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.0 req
uired
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
When I google the error it indicates to change the binary files, but that doesn't work either, unless I don't understand what that entails.
Any suggestions?By saying that you have amended your tnsnames.ora to connect to the 10gR2 databases, I assume you are running the rman command on your 11gR1 server. This means that your RMAN client version is 11gR1, and your target database is 10gR2. This is not permitted, see the [compatibility matrix|http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/compat003.htm#i634479].
I suggest you try this on each of your 10gR2 servers:
1. Amend tnsnames.ora to include an entry for the 11gR1 rman_database
2. Ensure your oracle environment variables are set correctly, especially ORACLE_HOME and ORACLE_SID
3. rman target=sys/password catalog=rman/password@rman_database
This means you will be using the 10gR2 RMAN client on the 10gR2 target database which ensures no incompatibility problems. There is no issue with the fact your recovery catalog schema is at 11gR1, this is permitted to be greater than the RMAN client being used. -
RMAN backup finish with ORA-07445: exception encountered: core dump
Hi Group,
Repeatly we have problems with RMAN, showing this message, we need to know if this message is related to Oracle Database or is the backup software.
Thanks a lot
/pcpdci/oracle/product/920/admin/PCPDCI_bd/udump/pcpdci_ora_31187.trc
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
ORACLE_HOME = /pcpdci/oracle/product/920
System name: Linux
Node name: bd.copesa.cl
Release: 2.6.9-78.ELhugemem
Version: #1 SMP Wed Jul 9 15:57:33 EDT 2008
Machine: i686
Instance name: PCPDCI
Redo thread mounted by this instance: 1
Oracle process number: 948
Unix process pid: 31187, image: [email protected] (TNS V1-V3)
*** 2011-04-11 00:58:44.241
*** SESSION ID:(1519.515) 2011-04-11 00:58:44.240
SKGFQ OSD: Error in function sbtwrite2 on line 1031
SKGFQ OSD: Look for SBT Trace messages in file /pcpdci/oracle/product/920/admin/PCPDCI_bd/udump/sbtio.log
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x126, PC: [0xf6abe90b, __GI_strlen()+11]
Registers:
%eax: 0x00000126 %ebx: 0xf6b7dff4 %ecx: 0x00000002
%edx: 0x00000000 %edi: 0x00000000 %esi: 0x00000126
%esp: 0xfeff6154 %ebp: 0xfeff6794 %eip: 0xf6abe90b
%efl: 0x00010202
__GI_strlen()+0 (0xf6abe900) mov 0x4(%esp),%ecx
__GI_strlen()+4 (0xf6abe904) mov %ecx,%eax
__GI_strlen()+6 (0xf6abe906) and $3,%ecx
__GI_strlen()+9 (0xf6abe909) je 0xf6abe933
__GI_strlen()+11 (0xf6abe90b) cmpb %ch,(%eax) __GI_strlen()+13 (0xf6abe90d) jz 0xf6abe9aa
__GI_strlen()+19 (0xf6abe913) inc %eax
__GI_strlen()+20 (0xf6abe914) xor $3,%ecx
__GI_strlen()+23 (0xf6abe917) je 0xf6abe933
*** 2011-04-11 00:58:44.570
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [__GI_strlen()+11] [SIGSEGV] [Address not mapped to object] [0x126] [] []
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
ksedmp()+274 call ksedst() 1 ? 0 ? 0 ? 1 ? 33396562 ?
===========================================================
Tracing started for:
Application Client : TDPO Linux86
Version : 5.4.1.0
===========================================================
SBT-13207 07/12/2010 16:32:29 send2.cpp(412): sbtwrite2(): Exit - DSMSENDDATA() failed. dsmHandle = 1
===========================================================
Tracing started for:
Application Client : TDPO Linux86
Version : 5.4.1.0
===========================================================
SBT-14436 07/12/2010 16:52:58 send2.cpp(412): sbtwrite2(): Exit - DSMSENDDATA() failed. dsmHandle = 1
===========================================================
Tracing started for:
Application Client : TDPO Linux86
Version : 5.4.1.0
===========================================================
SBT-15110 07/12/2010 17:01:58 send2.cpp(412): sbtwrite2(): Exit - DSMSENDDATA() failed. dsmHandle = 1
===========================================================
Tracing started for:
Application Client : TDPO Linux86
Version : 5.4.1.0Reply from nagulan is correct. Our turned out to be an error with TSM. The disk pool had filled up and it was writing this to tape before allowing the backup to continue. The backup didn't handle the "pause" event well and failed out. We only get this with V9 RMAN, not V10 or V11 RMAN backups. This has to be addressed by the backup vendor for V9 as the Oracle RMAN software doesn't seem to handle it well. Maybe configuring a really large timeout for responses MAY fix this, depending on what the code returned from the backup software vendor is and why RMAN isn't happy with it.
In the end it is an issue between V9 RMAN and the backup software we run TSM. Maybe version incompatibility or maybe just V9 is not that robust. -
How can i do a RMAN backup of my database from the network ?
i'm using oracle 8i.1.7.3 with win server 2003
i want to know how can i do a RMAN backup of my database (sever machine A) from the network.
i'd like to save the backup in another machine (the same LAN, the same OS ).
to do that i've mapped a logical device in my comptur (z):
when i run rman command i got this error:
channel ORA_DISK_1: starting piece 1 at .......
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command ON ORA_DISK_1 channel at .......
00
ORA-19504: failed TO CREATE file "\\remote\save\"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 123) The filename, directory name, or volume label syntax is inco
rrect.Hi,
ORA-19504: failed TO CREATE file "\\remote\save\"make sure you have created this directory and change it's ownership (chown command)to oracle.
also make sure that oracle user has permission to write to this direcotry (chmod command)
hope this helps
cheers, walrus -
Issue in configuring Standby Database from Active database in 11g by RMAN
POSTED THE SAME IN DATA GUARD CATEGORY UNABLE TO DELETE
Hi All,
I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0)
Operating System:Linux 5
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Primary Database Entries:
Tnsentry:
SONYPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)(UR=A)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listner Entry:
SID_LIST_SONYPRD =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtproc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = SONYPRD)
(GLOBAL_DBNAME = SONYPRD)
Auxiliary Details:
Tns Entry:
SONYPRD =
(DESCRIPTION =
# (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listener Entry in auxiliary:
SID_LIST_SONYPRDSTBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = SONYPRDSTBY)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = SONYPRDSTBY)
TNSPING from Primary DB:
[oracle@oracle11g ~]$ tnsping sonyprdstby
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
OK (0 msec)
TNSPING from Auxuliary server
[oracle@oracle11gstby ~]$ tnsping sonyprd
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
OK (10 msec)
Script Used for duplicate:
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'sonyprd','sonyprdstby'
set db_unique_name='sonyprdstby'
set db_file_name_convert='/sonyprd/','/sonyprdstby/'
set log_file_name_convert='/sonyprd/','/sonyprdstby/'
set control_files='/u01/app/oracle/oradata/control01.ctl'
set log_archive_max_processes='5'
set fal_client='sonyprdstby'
set fal_server='sonyprd'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
Tried the script from both Primary and auxiliary but no luck
[oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SONYPRD (DBID=3131093559)
connected to auxiliary database: SONYPRD (not mounted)
Listener Status from primary:
[oracle@oracle11g ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 20-DEC-2012 17:42:17
Uptime 1 days 0 hr. 26 min. 41 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "sonyprd.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
Service "sonyprdXDB.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
The command completed successfully
Listener Status from Standby when database bring to Nomount state:
[oracle@oracle11gstby admin]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 21-DEC-2012 16:13:47
Uptime 0 days 1 hr. 58 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
Services Summary...
Service "sonyprdstby" has 1 instance(s).
Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
The command completed successfully
Please provide any work arounds to proceed further in creating the standby database.
Thanks,
Ram.
Edited by: 895188 on Dec 21, 2012 5:50 PM
Edited by: 895188 on Dec 21, 2012 6:09 PM
Edited by: 895188 on Dec 21, 2012 6:22 PMHello;
Script has to be run from auxiliary.
Great details, but what I don't see is how you connect in RMAN.
Example
Start RMAN
$ORACLE_HOME/bin/rman target=sys/@recover2 auxiliary=sys/@reclone
Recovery Manager: Release 11.2.0.2.0 - Production on Wed Feb 22 14:50:31 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RECOVER2 (DBID=3806912436)
connected to auxiliary database: RECLONE (not mounted)Nothing in your tnsnames or listener jumps out as wrong. I copied them into my text editor and compared against my working ones.
Generally for active duplication I start the future standby on a pfile NOMOUNT.
Auxiliary Instance Initialization Parameters Needed :
DB_NAME
CONTROL_FILES
DB_BLOCK_SIZE
( add extra parameters like DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT instead of using the SET command - clean up standby spfile right after duplication )
Then start RMAN and finally run a single line duplication command.
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
RMAN>duplicate target database for standby from active database NOFILENAMECHECK;Best Regards
mseberg -
Issue in creating the standby database from Active database using RMAN
Hi All,
I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0)
Operating System:Linux 5
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Primary Database Entries:
Tnsentry:
SONYPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)(UR=A)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listner Entry:
SID_LIST_SONYPRD =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtproc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = SONYPRD)
(GLOBAL_DBNAME = SONYPRD)
Auxiliary Details:
Tns Entry:
SONYPRD =
(DESCRIPTION =
# (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listener Entry in auxiliary:
SID_LIST_SONYPRDSTBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = SONYPRDSTBY)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = SONYPRDSTBY)
TNSPING from Primary DB:
[oracle@oracle11g ~]$ tnsping sonyprdstby
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
OK (0 msec)
TNSPING from Auxuliary server
[oracle@oracle11gstby ~]$ tnsping sonyprd
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
OK (10 msec)
Script Used for duplicate:
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'sonyprd','sonyprdstby'
set db_unique_name='sonyprdstby'
set db_file_name_convert='/sonyprd/','/sonyprdstby/'
set log_file_name_convert='/sonyprd/','/sonyprdstby/'
set control_files='/u01/app/oracle/oradata/control01.ctl'
set log_archive_max_processes='5'
set fal_client='sonyprdstby'
set fal_server='sonyprd'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
Tried the script from both Primary and auxiliary but no luck
[oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SONYPRD (DBID=3131093559)
connected to auxiliary database: SONYPRD (not mounted)
Listener Status from primary:
[oracle@oracle11g ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 20-DEC-2012 17:42:17
Uptime 1 days 0 hr. 26 min. 41 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "sonyprd.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
Service "sonyprdXDB.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
The command completed successfully
Listener Status from Standby when database bring to Nomount state:
[oracle@oracle11gstby admin]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 21-DEC-2012 16:13:47
Uptime 0 days 1 hr. 58 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
Services Summary...
Service "sonyprdstby" has 1 instance(s).
Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
The command completed successfully
Please provide any work arounds to proceed further in creating the standby database.
Thanks,
Ram.Pl do not post duplicates - Issue in configuring Standby Database from Active database in 11g by RMAN
-
Dear friends,
Is it passible that we take logical backup(i.e Export/Impot)
in Rman.
If yes then.
Why?
[email protected]Pixels.
For a 1" x 1" photo first crop the photo square. Then export with Kind = Current with JPEF Quality = Maximum and Size = Full size.
Then when you go to print the photo select a 1" x 1" print size. This will squeeze all available pixels in each dimension into the 1" dimension giving you the highest DPI resolution available from your image file.
More about DPI can be found here: All About Digital Photos - The Arithmetic of DPI and All About Digital Photos - The Myth of DPI
OT -
Can not recover table from rman backup
For testing I want to recover deleted table from rman backup.
I have make vm of oracle 11g. the following step i have applied but could not recover the table.
rman> backup database ;
On sqlplus create login as scott/tiger
create table scott.emp1(col1 varchar2(10));
insert into emp1(col1) value('Yasir ') ;
commit ;
select * from emp1 ;
it shows me one row successfully.
Now i have login the sys as sysdba
sqlplus> alter system switch logfile ;
after this i have drop the table .
Now to recover the table i have restored database on same vm.
rman>restore database ;
rman> recover database ;
rman> alter database open ;
on sqlplus i have issued
sqlplus> select * from scott.emp1 ;
table or view does not exist.
any help how to recover the deleted table from rman backupHi,
Check this test case
SQL> create table TEST2 as select * from emp;
Table created.
SQL> select count(*) from TEST2;
COUNT(*)
15
SQL> select TO_CHAR(SYSDATE,'DD-MON-YYYY HH24:MI:SS') from dual;
TO_CHAR(SYSDATE,'DD-
10-SEP-2013 10:57:05
SQL> alter system switch logfile;
System altered.
SQL> drop table TEST2 purge;
Table dropped.
SQL> shu immediate
[oracle@vnode MYSHELL]$ rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Tue Sep 10 10:58:39 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DDTEST (DBID=1667776968, not open)
RMAN> run{
set until time "to_date('2013 Sep 10 10:57','yyyy mon dd hh24:mi')";
restore database;
recover database;
alter database open resetlogs;
}2> 3> 4> 5> 6>
media recovery complete, elapsed time: 00:00:02
Finished recover at 10-SEP-13
database opened
RMAN> exit
SQL> set lin 200 pages 100
SQL> select count(*) from test2;
COUNT(*)
15
HTH -
RMAN duplicate target using set until telling me it can not find data files
I have RMAN scripts that I use freqently to clone a database from DB (production) to another (non-prod). These work just fine. I use the set until so that I can tell it at what point I want the new DB to be created from the backups of the source.
I had a request to go back a few weeks and the backup files (I do compressed backups to disk) were on tape. I had my backup person restore my backup directory for the source DB as it looked on a certain day (May 28). I have an 8 day retention policy and so the backup files that were restored showed files all the way back to 5/20 ( includes the point I want to use in my set until clause).
However, whenever I try to execute the rman clone, it tells me for each datafile:
RMAN-06023: no backup or copy of datafile 1 found to restore
Like I said, I am able to do this for a current backup that is on disk. I moved the backup files to the source db server and it works fine. However, from these files restored from tape it errors.
Here is the RMAN script:
spool log to c:\temp\clone_CSPROD_CSPRSUM1.log;
#connect to catalog <catalog info>
# target is the source and auxiliary is destination
#connect target <put in source info here>
#connect auxiliary /
run {
allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
##Archivelog number get from sql archive log list command
#set until sequence 831;
set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
duplicate target database to CSPRSUM1 nofilenamecheck
logfile
group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
Exit
Here is the output:
Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
Recovery Manager11.1.0.7.0
RMAN> #connect catalog <redacted info>>
2> # target is the source and auxiliary is destination
3> #connect target <redacted info>
4> #connect auxiliary /
5>
6> run {
7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
12> ##Archivelog number get from sql archive log list command
13> #set until sequence 831;
14> set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
15> duplicate target database to CSPRSUM1 nofilenamecheck
16> logfile
17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
20> }
starting full resync of recovery catalog
full resync complete
allocated channel: d1
channel d1: SID=534 device type=DISK
allocated channel: d2
channel d2: SID=533 device type=DISK
allocated channel: d3
channel d3: SID=532 device type=DISK
allocated channel: d4
channel d4: SID=531 device type=DISK
allocated channel: a1
channel a1: SID=530 device type=DISK
executing command: SET until clause
Starting Duplicate Db at 15-JUN-11
RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
contents of Memory Script:
set until scn 260398799;
set newname for datafile 1 to
"+data";
set newname for datafile 2 to
"+data";
set newname for datafile 3 to
"+data";
set newname for datafile 4 to
"+data";
set newname for datafile 5 to
"+data";
set newname for datafile 6 to
"+data";
set newname for datafile 7 to
"+data";
set newname for datafile 8 to
"+data";
set newname for datafile 9 to
"+data";
set newname for datafile 10 to
"+data";
set newname for datafile 11 to
"+data";
set newname for datafile 12 to
"+data";
set newname for datafile 13 to
"+data";
set newname for datafile 14 to
"+data";
set newname for datafile 15 to
"+data";
set newname for datafile 16 to
"+data";
set newname for datafile 17 to
"+data";
set newname for datafile 18 to
"+data";
set newname for datafile 19 to
"+data";
set newname for datafile 20 to
"+data";
set newname for datafile 21 to
"+data";
set newname for datafile 22 to
"+data";
set newname for datafile 23 to
"+data";
set newname for datafile 24 to
"+data";
set newname for datafile 25 to
"+data";
set newname for datafile 26 to
"+data";
set newname for datafile 27 to
"+data";
set newname for datafile 28 to
"+data";
set newname for datafile 29 to
"+data";
set newname for datafile 30 to
"+data";
set newname for datafile 31 to
"+data";
set newname for datafile 32 to
"+data";
set newname for datafile 33 to
"+data";
set newname for datafile 34 to
"+data";
set newname for datafile 35 to
"+data";
set newname for datafile 36 to
"+data";
set newname for datafile 37 to
"+data";
set newname for datafile 38 to
"+data";
set newname for datafile 39 to
"+data";
set newname for datafile 40 to
"+data";
set newname for datafile 41 to
"+data";
set newname for datafile 42 to
"+data";
set newname for datafile 43 to
"+data";
set newname for datafile 44 to
"+data";
set newname for datafile 45 to
"+data";
set newname for datafile 46 to
"+data";
set newname for datafile 47 to
"+data";
set newname for datafile 48 to
"+data";
set newname for datafile 49 to
"+data";
set newname for datafile 50 to
"+data";
set newname for datafile 51 to
"+data";
set newname for datafile 52 to
"+data";
set newname for datafile 53 to
"+data";
set newname for datafile 54 to
"+data";
set newname for datafile 55 to
"+data";
set newname for datafile 56 to
"+data";
set newname for datafile 57 to
"+data";
set newname for datafile 58 to
"+data";
set newname for datafile 59 to
"+data";
set newname for datafile 60 to
"+data";
set newname for datafile 61 to
"+data";
set newname for datafile 62 to
"+data";
set newname for datafile 63 to
"+data";
set newname for datafile 64 to
"+data";
set newname for datafile 65 to
"+data";
set newname for datafile 66 to
"+data";
set newname for datafile 67 to
"+data";
set newname for datafile 68 to
"+data";
set newname for datafile 69 to
"+data";
set newname for datafile 70 to
"+data";
set newname for datafile 71 to
"+data";
set newname for datafile 72 to
"+data";
set newname for datafile 73 to
"+data";
set newname for datafile 74 to
"+data";
set newname for datafile 75 to
"+data";
set newname for datafile 76 to
"+data";
set newname for datafile 77 to
"+data";
set newname for datafile 78 to
"+data";
set newname for datafile 79 to
"+data";
set newname for datafile 80 to
"+data";
set newname for datafile 81 to
"+data";
set newname for datafile 82 to
"+data";
set newname for datafile 83 to
"+data";
set newname for datafile 84 to
"+data";
set newname for datafile 85 to
"+data";
set newname for datafile 86 to
"+data";
set newname for datafile 87 to
"+data";
set newname for datafile 88 to
"+data";
set newname for datafile 89 to
"+data";
set newname for datafile 90 to
"+data";
set newname for datafile 91 to
"+data";
set newname for datafile 92 to
"+data";
set newname for datafile 93 to
"+data";
set newname for datafile 94 to
"+data";
set newname for datafile 95 to
"+data";
set newname for datafile 96 to
"+data";
set newname for datafile 97 to
"+data";
set newname for datafile 98 to
"+data";
set newname for datafile 99 to
"+data";
set newname for datafile 100 to
"+data";
set newname for datafile 101 to
"+data";
set newname for datafile 102 to
"+data";
set newname for datafile 103 to
"+data";
set newname for datafile 104 to
"+data";
set newname for datafile 105 to
"+data";
set newname for datafile 106 to
"+data";
set newname for datafile 107 to
"+data";
set newname for datafile 108 to
"+data";
set newname for datafile 109 to
"+data";
set newname for datafile 110 to
"+data";
set newname for datafile 111 to
"+data";
set newname for datafile 112 to
"+data";
set newname for datafile 113 to
"+data";
set newname for datafile 114 to
"+data";
set newname for datafile 115 to
"+data";
set newname for datafile 116 to
"+data";
set newname for datafile 117 to
"+data";
set newname for datafile 118 to
"+data";
set newname for datafile 119 to
"+data";
set newname for datafile 120 to
"+data";
set newname for datafile 121 to
"+data";
set newname for datafile 122 to
"+data";
restore
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
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 15-JUN-11
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: a1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/15/2011 11:21:42
RMAN-01005: not all datafiles have backups that can be recovered to scn 260398799
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 122 found to restore
RMAN-06023: no backup or copy of datafile 121 found to restore
RMAN-06023: no backup or copy of datafile 120 found to restore
RMAN-06023: no backup or copy of datafile 119 found to restore
RMAN-06023: no backup or copy of datafile 118 found to restore
RMAN-06023: no backup or copy of datafile 117 found to restore
RMAN-06023: no backup or copy of datafile 116 found to restore
RMAN-06023: no backup or copy of datafile 115 found to restore
RMAN-06023: no backup or copy of datafile 114 found to restore
RMAN-06023: no backup or copy of datafile 113 found to restore
RMAN-06023: no backup or copy of datafile 112 found to restore
RMAN-06023: no backup or copy of datafile 111 found to restore
RMAN-06023: no backup or copy of datafile 110 found to restore
RMAN-06023: no backup or copy of datafile 109 found to restore
RMAN-06023: no backup or copy of datafile 108 found to restore
RMAN-06023: no backup or copy of datafile 107 found to restore
RMAN-06023: no backup or copy of datafile 106 found to restore
RMAN-06023: no backup or copy of datafile 105 found to restore
RMAN-06023: no backup or copy of datafile 104 found to restore
RMAN-06023: no backup or copy of datafile 103 found to restore
RMAN-06023: no backup or copy of datafile 102 found to restore
RMAN-06023: no backup or copy of datafile 101 found to restore
RMAN-06023: no backup or copy of datafile 100 found to restore
RMAN-06023: no backup or copy of datafile 99 found to restore
RMAN-06023: no backup or copy of datafile 98 found to restore
RMAN-06023: no backup or copy of datafile 97 found to restore
RMAN-06023: no backup or copy of datafile 96 found to restore
RMAN-06023: no backup or copy of datafile 95 found to restore
RMAN-06023: no backup or copy of datafile 94 found to restore
RMAN-06023: no backup or copy of datafile 93 found to restore
RMAN-06023: no backup or copy of datafile 92 found to restore
RMAN-06023: no backup or copy of datafile 91 found to restore
RMAN-06023: no backup or copy of datafile 90 found to restore
RMAN-06023: no backup or copy of datafile 89 found to restore
RMAN-06023: no backup or copy of datafile 88 found to restore
RMAN-06023: no backup or copy of datafile 87 found to restore
RMAN-06023: no backup or copy of datafile 86 found to restore
RMAN-06023: no backup or copy of datafile 85 found to restore
RMAN-06023: no backup or copy of datafile 84 found to restore
RMAN-06023: no backup or copy of datafile 83 found to restore
RMAN-06023: no backup or copy of datafile 82 found to restore
RMAN-06023: no backup or copy of datafile 81 found to restore
RMAN-06023: no backup or copy of datafile 80 found to restore
RMAN-06023: no backup or copy of datafile 79 found to restore
RMAN-06023: no backup or copy of datafile 78 found to restore
RMAN-06023: no backup or copy of datafile 77 found to restore
RMAN-06023: no backup or copy of datafile 76 found to restore
RMAN-06023: no backup or copy of datafile 75 found to restore
RMAN-06023: no backup or copy of datafile 74 found to restore
RMAN-06023: no backup or copy of datafile 73 found to restore
RMAN-06023: no backup or copy of datafile 72 found to restore
RMAN-06023: no backup or copy of datafile 71 found to restore
RMAN-06023: no backup or copy of datafile 70 found to restore
RMAN-06023: no backup or copy of datafile 69 found to restore
RMAN-06023: no backup or copy of datafile 68 found to restore
RMAN-06023: no backup or copy of datafile 67 found to restore
RMAN-06023: no backup or copy of datafile 66 found to restore
RMAN-06023: no backup or copy of datafile 65 found to restore
RMAN-06023: no backup or copy of datafile 64 found to restore
RMAN-06023: no backup or copy of datafile 63 found to restore
RMAN-06023: no backup or copy of datafile 62 found to restore
RMAN-06023: no backup or copy of datafile 61 found to restore
RMAN-06023: no backup or copy of datafile 60 found to restore
RMAN-06023: no backup or copy of datafile 59 found to restore
RMAN-06023: no backup or copy of datafile 58 found to restore
RMAN-06023: no backup or copy of datafile 57 found to restore
RMAN-06023: no backup or copy of datafile 56 found to restore
RMAN-06023: no backup or copy of datafile 55 found to restore
RMAN-06023: no backup or copy of datafile 54 found to restore
RMAN-06023: no backup or copy of datafile 53 found to restore
RMAN-06023: no backup or copy of datafile 52 found to restore
RMAN-06023: no backup or copy of datafile 51 found to restore
RMAN-06023: no backup or copy of datafile 50 found to restore
RMAN-06023: no backup or copy of datafile 49 found to restore
RMAN-06023: no backup or copy of datafile 48 found to restore
RMAN-06023: no backup or copy of datafile 47 found to restore
RMAN-06023: no backup or copy of datafile 46 found to restore
RMAN-06023: no backup or copy of datafile 45 found to restore
RMAN-06023: no backup or copy of datafile 44 found to restore
RMAN-06023: no backup or copy of datafile 43 found to restore
RMAN-06023: no backup or copy of datafile 42 found to restore
RMAN-06023: no backup or copy of datafile 41 found to restore
RMAN-06023: no backup or copy of datafile 40 found to restore
RMAN-06023: no backup or copy of datafile 39 found to restore
RMAN-06023: no backup or copy of datafile 38 found to restore
RMAN-06023: no backup or copy of datafile 37 found to restore
RMAN-06023: no backup or copy of datafile 36 found to restore
RMAN-06023: no backup or copy of datafile 35 found to restore
RMAN-06023: no backup or copy of datafile 34 found to restore
RMAN-06023: no backup or copy of datafile 33 found to restore
RMAN-06023: no backup or copy of datafile 32 found to restore
RMAN-06023: no backup or copy of datafile 31 found to restore
RMAN-06023: no backup or copy of datafile 30 found to restore
RMAN-06023: no backup or copy of datafile 29 found to restore
RMAN-06023: no backup or copy of datafile 28 found to restore
RMAN-06023: no backup or copy of datafile 27 found to restore
RMAN-06023: no backup or copy of datafile 26 found to restore
RMAN-06023: no backup or copy of datafile 25 found to restore
RMAN-06023: no backup or copy of datafile 24 found to restore
RMAN-06023: no backup or copy of datafile 23 found to restore
RMAN-06023: no backup or copy of datafile 22 found to restore
RMAN-06023: no backup or copy of datafile 21 found to restore
RMAN-06023: no backup or copy of datafile 20 found to restore
RMAN-06023: no backup or copy of datafile 19 found to restore
RMAN-06023: no backup or copy of datafile 18 found to restore
RMAN-06023: no backup or copy of datafile 17 found to restore
RMAN-06023: no backup or copy of datafile 16 found to restore
RMAN-06023: no backup or copy of datafile 15 found to restore
RMAN-06023: no backup or copy of datafile 14 found to restore
RMAN-06023: no backup or copy of datafile 13 found to restore
RMAN-06023: no backup or copy of datafile 12 found to restore
RMAN-06023: no backup or copy of datafile 11 found to restore
RMAN-06023: no backup or copy of datafile 10 found to restore
RMAN-06023: no backup or copy of datafile 9 found to restore
RMAN-06023: no backup or copy of datafile 8 found to restore
RMAN-06023: no backup or copy of datafile 7 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to 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 restore
RMAN> Exit
Recovery Manager complete.
Edited by: kerrygm on Jun 15, 2011 11:36 AMMaybe making progress.
I got into RMAN and did a List backup command. In looking at the output, I see that it does have the 5/20 backup showing. Here is part of the output:
BS Key Type LV Size Device Type Elapsed Time Completion Time
965689 Full 19.86M DISK 00:00:01 16-JUN-11
BP Key: 967942 Status: AVAILABLE Compressed: NO Tag: TAG20110616T231223
Piece Name: F:\BACKUPS\CSPROD\C-368871413-20110616-01
SPFILE Included: Modification time: 16-JUN-11
SPFILE db_unique_name: CSPROD
Control File Included: Ckp SCN: 369596068 Ckp time: 16-JUN-11
BS Key Size Device Type Elapsed Time Completion Time
966218 403.84M DISK 00:00:00 20-MAY-11
BP Key: 967842 Status: AVAILABLE Compressed: YES Tag: TAG20110520T231012
Piece Name: F:\BACKUPS\CSPROD\A1\CSPROD_ARCH_5844
List of Archived Logs in backup set 966218
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2112 237027300 20-MAY-11 237046947 20-MAY-11
1 2113 *237046947* 20-MAY-11 237059284 20-MAY-11
1 2114 237059284 20-MAY-11 237216514 20-MAY-11
1 2115 237216514 20-MAY-11 237709545 20-MAY-11
1 2116 237709545 20-MAY-11 237722825 20-MAY-11
1 2117 237722825 20-MAY-11 237730431 20-MAY-11
1 2118 237730431 20-MAY-11 237860199 20-MAY-11
I then changed my rman script to use the *237046947* SCN number that says it is from 5/20. I them kicked off my rman script and got the following result.
Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
Recovery Manager11.1.0.7.0
RMAN> #connect catalog 'rmancat/rmancat@rmancat';
2> # target is the source and auxiliary is destination
3> #connect target sys/<pwd>@csprod
4> #connect auxiliary /
5>
6> run {
7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
12> ##Archivelog number get from sql archive log list command
13> set until sequence 237046947;
14> ##set until time "to_date('2011-05-20 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
15> duplicate target database to CSPRSUM1 nofilenamecheck
16> logfile
17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
20> }
allocated channel: d1
channel d1: SID=532 device type=DISK
allocated channel: d2
channel d2: SID=533 device type=DISK
allocated channel: d3
channel d3: SID=531 device type=DISK
allocated channel: d4
channel d4: SID=555 device type=DISK
allocated channel: a1
channel a1: SID=534 device type=DISK
executing command: SET until clause
Starting Duplicate Db at 17-JUN-11
RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
contents of Memory Script:
set until scn 373021170;
set newname for datafile 1 to
"+data";
set newname for datafile 2 to
Starting restore at 17-JUN-11
channel d1: starting datafile backup set restore
channel d1: specifying datafile(s) to restore from backup set
channel d1: restoring datafile 00003 to +DATA
channel d2: restoring datafile 00122 to +DATA
channel d2: reading from backup piece F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149
channel d3: starting datafile backup set restore
channel d3: specifying datafile(s) to restore from backup set
channel d3: restoring datafile 00002 to +DATA
channel d3: restoring datafile 00020 to +DATA
channel d4: restoring datafile 00120 to +DATA
channel d4: reading from backup piece F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147
channel d1: piece handle=F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 tag=TAG20110616T230013
channel d1: restored backup piece 1
channel d1: restore complete, elapsed time: 00:01:15
channel d4: piece handle=F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147 tag=TAG20110616T230013
channel d4: restored backup piece 1
channel d4: restore complete, elapsed time: 00:03:15
channel d2: piece handle=F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149 tag=TAG20110616T230013
channel d2: restored backup piece 1
channel d2: restore complete, elapsed time: 00:03:35
channel d3: piece handle=F:\BACKUPS\CSPROD\D1\CSPROD_DATA_6146 tag=TAG20110616T230013
channel d3: restored backup piece 1
channel d3: restore complete, elapsed time: 00:04:55
Finished restore at 17-JUN-11
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CSPRSUM1" RESETLOGS ARCHIVELOG
MAXLOGFILES 23
MAXLOGMEMBERS 3
MAXDATAFILES 1021
MAXINSTANCES 8
MAXLOGHISTORY 584
LOGFILE
GROUP 1 ( '+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log' ) SIZE 50 M ,
GROUP 2 ( '+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log' ) SIZE 50 M ,
GROUP 3 ( '+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log' ) SIZE 50 M
DATAFILE
'+DATA/csprsum1/datafile/system.1535.754067379'
CHARACTER SET WE8MSWIN1252
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy RECID=1 STAMP=754067676 file name=+DATA/csprsum1/datafile/sysaux.1536.754067379
datafile 121 switched to datafile copy
input datafile copy RECID=120 STAMP=754067677 file name=+DATA/csprsum1/datafile/waapp.1653.754067403
datafile 122 switched to datafile copy
input datafile copy RECID=121 STAMP=754067677 file name=+DATA/csprsum1/datafile/cu_custom.1549.754067381
contents of Memory Script:
set until scn 373021170;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 17-JUN-11
starting media recovery
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '+DATA/csprsum1/datafile/system.1535.754067379'
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: a1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/17/2011 15:14:54
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 3818 and starting SCN of 372868482 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3817 and starting SCN of 372685133 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3816 and starting SCN of 372593528 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3815 and starting SCN of 372374385 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3814 and starting SCN of 372325053 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3813 and starting SCN of 372316138 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3812 and starting SCN of 372249619 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3811 and starting SCN of 371775981 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3810 and starting SCN of 371643855 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3809 and starting SCN of 371614442 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3808 and starting SCN of 371432892 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3807 and starting SCN of 371121955 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3806 and starting SCN of 371047786 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3805 and starting SCN of 371029095 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3804 and starting SCN of 371018252 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3803 and starting SCN of 370947755 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3802 and starting SCN of 370857440 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3801 and starting SCN of 370814417 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3800 and starting SCN of 370797061 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3799 and starting SCN of 370756569 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3798 and starting SCN of 370746833 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3797 and starting SCN of 370746693 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3796 and starting SCN of 370746568 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3795 and starting SCN of 370746068 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3794 and starting SCN of 370745451 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3793 and starting SCN of 370733767 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3792 and starting SCN of 370674629 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3791 and starting SCN of 370501026 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3790 and starting SCN of 370498513 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3789 and starting SCN of 370497977 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3788 and starting SCN of 370497635 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3787 and starting SCN of 370497319 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3786 and starting SCN of 370496938 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3785 and starting SCN of 370495428 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3784 and starting SCN of 370491173 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3783 and starting SCN of 370390074 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3782 and starting SCN of 370385574 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3781 and starting SCN of 370385310 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3780 and starting SCN of 370385044 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3779 and starting SCN of 370368486 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3778 and starting SCN of 370333960 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3777 and starting SCN of 370330980 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3776 and starting SCN of 370327876 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3775 and starting SCN of 370174433 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3774 and starting SCN of 370148373 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3773 and starting SCN of 370147821 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3772 and starting SCN of 370147623 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3771 and starting SCN of 370141528 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3770 and starting SCN of 369711271 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3769 and starting SCN of 369621694 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3768 and starting SCN of 369595614 found to restore
RMAN> Exit
Recovery Manager complete.
What I am not sure is if the SCN I used in my set until sequence command was from 5/20, when I look at the backup pieces that it is reading to restore from, they appear to be from backup files taken from June.
(e.g channel d1: reading from backup piece F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 -- this is a 6/16 backup file).
Also, as you can see it was not able to do a media recovery.
Thanks in advance for your help. -
Unable to restore and recover my Database from RMAN Backup
Dear All,
Iam practicing RMAN in Windows environment.
My configurations are
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:\Backup\%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\ORACLE\DATABASE\SNCFORCL.ORA';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'F:\Backup\%U.bak';
Then i took the RMAN backup, now iam shutdown my DB and removed one logfile..
then i tried to startup the DB but it is saying
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: 'E:\ORADATA\ORCL\REDO03.LOG'
So i tried to restore the Database with my rman backup
RMAN> restore database;
But i am unable to restore my logfile in the Datafiles location where as all other datafiles are restored but redo logfiles are not restored.
So, i am unable to recover my DB
Please tell me whether i am doing any mistake, what is the solution for my problem.
Thanks in advance
MahiAll you restored was your datafiles.
Now issue recover database and that will apply the archive logs.
This is in the oracle documentation.
"You must restore backups of these archived logs for recovery to proceed. You can restore either to the default or nondefault location. If you do not have backups, then you must performing incomplete recovery up to an SCN before the first missing redo log and open RESETLOGS."
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/osrecvry.htm
In this case after issuing restore database in RMAN, then issue this.
"Recover database"
It will then be an incomplete recovery. They should have been multiplexed. Did you restore your controlfile with this backup? You may have to issue an "Alter database open resetlogs;" -
G4Ti4200-VTD64 voltage incompatibility with MSI K7N2 Delta-ILSR??
Hello,
I have the MSI G4Ti4200-VTD64 (4X) video card.. I want to upgrade my motherboard to K7N2 Delta-ILSR. Is there any voltage incompatibility?? I heard that new mother boards will support only AGP 1.5V. Is the AGP voltage of K7N2 Delta-ILSR 1.5volts?? Is my video card compatible with this voltage?? I really want to retain my current video card as I am quite satisfied with it and I'm not willing to invest on a new one at the moment. If there is an incompatibility could you suggest another Socket A MB with good performance and SATA RAID support.
Thanks in advance
Regards,
JosephJoseph,
All 4X Vid Cards work on all 4X and 8X mobos. All 4X mobos work with all 4X and 8X Vid Cards.
Take Care,
Richard -
RMAN, RAC, NFS, and server lock ups
Good day. My environment is:
--a 2-node RAC
--Enterprise Edition 11.2.0.3
--RHEL 5.1
The goal is to use RMAN to push backups to a shared NFS mount (on a different server). Both nodes will have access to this location (in the event one node goes down, the other can still run backups). Easy, right?
Wrong.
I've tried every NFS mount option in the book. Most work just fine, some don't. When I use the recommended NFS mount options:
rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp, vers=3,timeo=600, actimeo=0
or
rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,noac,forcedirectio, vers=3,suid
The mount works normally. I can "ls" and "mkdir" and "touch" and "vi" and "cp" files back and forth from the NFS backup location to the RAC node all day long. No problems. However, when I try to do almost anything in RMAN which requires writing to the NFS backup location such as the command "backup archive all delete input;" (or even things as simple as a Crosscheck or RMAN configuration change which writes any changes back to the autobackup ControlFile) the node locks up. There are no errors (or if there are, I don't know where to find them), even when I use RMAN log.
Just to recap: I run a Crosscheck (or any RMAN process that writes to the NFS backup location), the node will lock up, and I can let it sit for a day, inaccessible, with CRSCTL on the other node saying it's offline, and the node will never come out of a "frozen" state. It cannot be pinged or connected to.
I think I can safely rule out NFS mount options at this point.
I understand (after extensive reading of MOS docs and testing) that RAC RMAN can and does suffer from inefficient I/O when writing to an NFS mount. I don't think that's the culprit either. The autobackup ControlFile is not that big and I cannot see how running a simple Crosscheck would lock an entire node.
I am hoping someone has encountered this in the past and hopefully it's just a simple misconfiguration somewhere.My NFS line in /etc/fstab is (these options are for supporting 11.2.0.3, 11.1.0.7, and 10.2.0.4/5 simultaneously): server.domain:/NFS_Export /backup nfs rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,vers=3,timeo=600 0 0
Before you installed GI, did you by chance do a yum update? I've encountered a similar issue which ended up being due to mkinitrd creating a corrupted kernel; mkinitrd is invoked during the GI installation when the ADVM drivers are added and in my case mkinitrd created a new kernel prior to the new kernel being installed. Second to that, make sure you have the matching kernel headers to your kernel version. If they are different then you could probably get away with just creating a new kernel with mkinitrd and relinking GI/RDBMS homes, but be prepared to wipe GI and reinstall. -
10.5.7 Fundamental Incompatibility with Mac Pro - Screen/System Lock ups
Hi all.
It looks like 10.5.7 is causing a lot of problems, but I think I found a problem that is very fundamental.
First, my system. It's one of the original Mac Pros with Quad Xeons at 2.66GHz. It has 24GB of RAM and several drives in there. I have 3 30" displays plugged into 3 NVIDIA GeForce 7300GT cards. I originally ran a 10.5.7 combo update on my 10.5.6 system, and experienced these problems (detailed below). As I was also running a beta of iTunes and the iPhone SDK (the 3rd release), and beta 2 of Safari 4, I thought this may have caused some trouble. So, I tried an experiment.
I bought a new Corsair 256GB SSD for my startup drive. Loaded my family pack of 10.5.6 onto it as a fresh install, and just applied the 10.5.7 combo update. I get the exact same behavior with no further software. So, this is a fundamental incompatibility of 10.5.7 with a machine having these specs.
Now the problems. They start with the primary (in my case center) screen locking while the other two screens keep working. Meaning, the primary display "works" but none of the windows move, the clock freezes...yet, if you move the mouse there and luckily grab a window, you could move it out onto the other 2 displays and it would allow you to continue to use the application. If you hit the CONTROLkey and scroll up and down (zooming the display in and out) it can sometimes "unlock" the primary display, but then there are many artifacts. For example, the shadows cast by windows appear as plain grey "dashboard esque" blocks and have black stripes at the edges. Also, at random times, the machine just seems to hang completely, and unlock a minute or 2 later. Eventually it locks for good.
Unfortunately this has lead me into a deadlock situation. My iTunes has been updated to the 3rd beta in the iPhone 3.0 SDK release. The library has been modified and only works with that version now. That version requires 10.5.7. So if I revert back to 10.5.6, I lose my iTunes Library or have to wait till the offical version of iTunes is realeased (although that may still require 10.5.7).
I see lots of people are having Firewire (800 in particular) problems, and I have several drives I need on Firewire. It's not a solution to yank them. It all works fine under 10.5.6, of course.
So the question is...is help on it's way? What to do!?
Thanks for any insights.
More info on the system below:
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 24 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005C.B08
SMC Version (system): 1.7f10
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x8
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-2
PCIe Lane Width: x8
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-3
PCIe Lane Width: x4
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
ATA Bus:
SONY DVD RW DW-D150A:
Model: SONY DVD RW DW-D150A
Revision: 1.MD
Serial Number:
Detachable Drive: No
Protocol: ATAPI
Unit Number: 0
Socket Type: Internal
Low Power Polling: No
Power Off: No
TSSTcorpCD/DVDW SH-S162L:
Model: TSSTcorpCD/DVDW SH-S162L
Revision: LC02
Serial Number:
Detachable Drive: No
Protocol: ATAPI
Unit Number: 1
Socket Type: Internal
Low Power Polling: No
Power Off: No
FireWire Bus:
Maximum Speed: Up to 800 Mb/sec
Built-in Hub:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
FreeAgent Go FW:
Manufacturer: Seagate
Model: 0x2200
GUID: 0x20370200105F82
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 200 Mb/sec
Sub-units:
FreeAgent Go FW Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x110
Product Revision Level: 410G
Sub-units:
FreeAgent Go FW SBP-LUN:
Capacity: 149.05 GB
Removable Media: Yes
BSD Name: disk5
Mac OS 9 Drivers: No
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Not Supported
Volumes:
Seagate149GBTote:
Capacity: 148.73 GB
Available: 132.95 GB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk5s2
Mount Point: /Volumes/Seagate149GBTote
Unknown Device:
Manufacturer: Unknown
Model: Unknown
GUID: 0x0
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
OEM ATA Device 00:
Manufacturer: OEM
Model: 0x0
GUID: 0x30E102E0454B7D
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 200 Mb/sec
Sub-units:
OEM ATA Device 00 Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x110
Product Revision Level:
Sub-units:
OEM ATA Device 00 SBP-LUN:
Capacity: 931.51 GB
Removable Media: Yes
BSD Name: disk4
Mac OS 9 Drivers: No
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Not Supported
Volumes:
TimeMachine:
Capacity: 931.19 GB
Available: 606.63 GB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk4s2
Mount Point: /Volumes/TimeMachine
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Memory Slots:
ECC: Enabled
DIMM Riser A/DIMM 1:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02007D11
DIMM Riser A/DIMM 2:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02006013
DIMM Riser B/DIMM 1:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x0200711F
DIMM Riser B/DIMM 2:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02007012
DIMM Riser A/DIMM 3:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xA4730244
DIMM Riser A/DIMM 4:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0x70780241
DIMM Riser B/DIMM 3:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xE4760245
DIMM Riser B/DIMM 4:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xF0770241I can only tell you that I've run 10.5.7 on my Mac Pro, same model as yours, without any problems. As a beta tester my Mac Pro was the main hardware on which 10.5.7 was tested. I currently have it installed on a first generation iMac, MacBook, and MacBook Pro as well as a second generation MacBook Pro. So far not a single problem.
But, I don't have multiple video cards nor do I use any beta version of iTunes (didn't know there was one since each system upgrade includes the current release) but I do use the Safari 4 Beta - the most recent version just released when 10.5.7 was released.)
I can suggest you read the following about updates of system software:
Essential Steps Before Updating OS X!
Please do things right before updating OS X in order to avoid problems.
A. Repair Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger, and 4.1 for Leopard) and/or TechTool Pro (4.6.1 for Leopard) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
B. Clone Using Restore Option of Disk Utility
1. Open Disk Utility from the Utilities folder.
2. Select the destination volume from the left side list.
3. Click on the Erase tab in the DU main window. Set the format type to Mac OS Extended (journaled, if available) and click on the Erase button. This step can be skipped if the destination has already been freshly erased.
4. Click on the Restore tab in the DU main window.
5. Select the destination volume from the left side list and drag it to the Destination entry field.
6. Select the source volume from the left side list and drag it to the Source entry field.
7. Double-check you got it right, then click on the Restore button.
Destination means your backup drive (should be erased first.)
Source means your startup drive or volume.
C. Download the Standalone Combo Updater from Apple.
Be sure you quit all running applications and disconnect all peripherals (except original keyboard and mouse) before running the installer. When the installer is running do not use the computer in any way other than to respond to an installer dialog.
Install the update by double-clicking on the installer package icon. When the installation is completed Restart the computer. Your computer will boot twice - this is normal. Upon completion of the update use Disk Utility to repair permissions. Not all permissions will seem repaired. You will get spurious reports regarding permissions related to iTunes, Front Row. These can be ignored. They will appear every time you repair permissions.
Following these basic steps should prevent most if not all updating problems. Note that if you have unrepairable disk problems reported in Step A then DO NOT update your system until those problems are resolved.
If you find that you did not follow these suggestions, then you might consider reinstalling OS X and going about the process properly in the hope of a successful result:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update. -
Using rman to backup a remote database
I am after a good guide or advice on how (what) to install and (how to) run Oracle RMAN
to backup a remote Oracle database.
RMAN must be installed and run on a Solaris (SunOS 5.8) box remote from the Solaris
box (also SunOS 5.8) running the Oracle database but connected to it via a TCP/IP
network.
The Oracle Recovery Manager and Database version is 9.2.0.1.0.
RMAN must perform the backup of the remote database over the network and store
the backup on a disk local to the RMAN box.
The backups may be full or incremental and may be "hot" backups taken while the
Oracle database is open.
The disk files are to be then backed up to tape using Veritas.
What software do I need to install on the RMAN box ?
What software do I need to install on the remote Oracle database box ?
Thanks,
Brett Morgan.writes to a NFS-mounted diskRman is writing to disk or tape (when is bundled (libraries needed) with some backup software for tapes such as Veritas). The disk device could be local, or mounted disk form other host or storage (over NFS as Werner mentioned, SMB and others).
Maybe you are looking for
-
Issue with normal page link redirecting to SSO page / forbidden page
Hi, I am having an issue with a number of pages within my portal. I have a 'List of Objects' that has been working for some time, each link in the list linked to another page. Just lately a number of pages that are linked to within this list are not
-
How to clear/reset "Installed Software" in Software Center?
Hello! I've done a big mistake with my application objects! I did have two applications in SCCM 2012 with the same MSI-installation package. The reason for this is because i would like to have one that is deployed as Required (with primary device)
-
Selective redundancy compression of the user menu - per user
Hi gurus, We would like to activate the redundancy compression of the user's role menus in the session manager. Problem is that some users have our new roles with the new menu structure, and others have the old lot still... In the new concept users h
-
My phone is currently linked to an apple id i forgot id
my phone is currently linked to an apple id i forgot id & paasword hw i will recover & activate my phone please help me
-
"I/O Error" when trying to open an Appleworks 5 document in 6.2.9
I recently updated to Appleworks 6.2.9 to avoid the printing problems in earlier versions. Now I cannot open any Appleworks 5 files or convert from Appleworks 5 (older files I occassionally need to access). In other words, all of my older Appleworks