Log sequence in RAC database
10.2 Doc. says: http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta008.htm#RCMRF106
>
Although the SEQUENCE parameter does not require that THREAD be specified, a given log sequence always implies a thread
>
Does this mean that the log sequence is unique for all threads ? If not what does this sentence mean ?
Note that in my 10.2.0.1 RAC database log sequence is unique only for a given thread:
1 select thread#, sequence#, name, status
2 from v$archived_log
3 where sequence# between 34 and 35
4* order by sequence#
SQL> /
THREAD# SEQUENCE# NAME S
1 34 D
2 34 /u02/fra/RAC/archivelog/2010_08_20/o1_mf_2_34_66xb2ttb_.arc A
1 34 /u02/fra/RAC/archivelog/2010_08_20/o1_mf_1_34_66xcgmbn_.arc A
2 35 /u02/fra/RAC/archivelog/2010_08_20/o1_mf_2_35_66xb48b8_.arc A
1 35 /u02/fra/RAC/archivelog/2010_08_20/o1_mf_1_35_66xcgkk0_.arc A
1 35 D
6 rows selected.
I sent mail to the writer and got this in reply:
The sentence will be rewritten to state that: "When you do not explicitly specify a thread number with the sequence number in the command, thread number 1 is used."
-----------------
Similar Messages
-
Next log sequence to archive in Standby Database (RAC Dataguard Issue)
Hi All,
I just had implemented Data Guard in our server. My primary Database is RAC configured, but it is only single node. The other Instance was removed and converted it to Developement Instance. For the reason I kept the primary as RAC is when I will implement dataguard, my Primary Database is RAC with 7 nodes.
The first test is successful, and I was able to "switchover" from my primary to standby. I failed in the 'FAILOVER" test.
I restore my primary server and redo the setup.
BTW, my standby DB is physical standby.
When I try to switchover again and issue archive log list, below is my output.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
*Next log sequence to archive 0*
Current log sequence 38
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
MOUNTED PHYSICAL STANDBY
===============================================
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
*Next log sequence to archive 38*
Current log sequence 38
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
READ WRITE PRIMARY
In my first attempt to switchover before I failed in "FAILOVER" test, I also issue +archive log list+ in both primary and standby database, and if I remember it right, next log sequence on both should be identical. Am I right on this?
Thanks in Advance.
Jay AOr Am i just overthinking on this?
Is dataguard only looking for the current and oldest log sequence? -
Log sequence difference among RAC Instances
RDBMS Version : 11.2
Platform : Solaris 10
In our RAC DB, we have 6 redo logs.
SQL> select * from v$logfile order by 1,2;
GROUP# STATUS TYPE MEMBER IS_
1 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log01.dbf NO
2 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log02.dbf NO
3 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log03.dbf NO
4 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log04.dbf NO
5 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log05.dbf NO
6 ONLINE +ORCL_ARCH01/ORCL_ARCH/orcl_log06.dbf NO
6 rows selected.
Logically or shall I say 'internally' , 3 redo logs are allocated per thread. But they all belong to one database.
SQL> select group#,thread#,members from v$log order by 1,2;
GROUP# THREAD# MEMBERS
1 1 1
2 1 1
3 1 1
4 2 1
5 2 1
6 2 1
6 rows selected.
SQL> exit;If all these 6 redo log files belong to one database, then why do they have different max (sequence#) ?
ie. The 'Oldest online log sequence' in Node1 shows 3432 and
''Oldest online log sequence' in Node2 shows 3188 (a difference of 244 )
-- Instance1 in Node1
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ORCL_ARCH01/ORCL_ARCH
Oldest online log sequence 3432 ------------------------->
Next log sequence to archive 3434
Current log sequence 3434
-- Instance 2 in Node2
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ORCL_ARCH01/ORCL_ARCH
Oldest online log sequence 3188 ------------------------> ( 3432 - 3188 = 244)
Next log sequence to archive 3190
Current log sequence 3190So, this means Node1 is more loaded than Node2 ?
So, in a properly configured RAC set both instances should show almost similar number for 'Oldest online log sequence' ? (ignoring the manual switches) -
Generate log sequence 1 at standby database everyday
Hi All,
We have standby dataguard set up namely CRMSTDY of 3 node RAC clusterware. It has been observed that log sequence number 1 is generated since last 4 days on standby database. There is nothing more information in alert_standby.log file and the same file is visible when we checked with ASMCMD utility. Below mentioned details:
ASMCMD> ls -ltr*
Type Redund Striped Time Sys Name*
N ARCHIVELOG/*
N AUTOBACKUP/*
N ONLINELOG/*
N controlfile/*
N primarch/*
N 1_1_748661470.dbf => FRA/CRMSTBY/ARCHIVELOG/2011_04_17/thread_1_seq_1.6721.748666233+*
N 1_1_748747875.dbf => FRA/CRMSTBY/ARCHIVELOG/2011_04_18/thread_1_seq_1.6142.748752703+*
N 1_1_748834274.dbf => FRA/CRMSTBY/ARCHIVELOG/2011_04_19/thread_1_seq_1.4771.748839479+*
N 1_1_748920673.dbf => FRA/CRMSTBY/ARCHIVELOG/2011_04_20/thread_1_seq_1.656.748925823+*
N 1_1_749007075.dbf => FRA/CRMSTBY/ARCHIVELOG/2011_04_21/thread_1_seq_1.1768.749012141+*
Below mentioned system information.
DB : Release 10.2.0.4.0
OS : Linux Enterprise release 5.2 (Carthage)
Regards,
VishalHi All,
We have standby dataguard set up namely CRMSTDY of 3 node RAC clusterware. It has been observed that log sequence number 1 is generated since last 4 days on standby database. There is nothing more information in alert_standby.log file and the same file is visible when we checked with ASMCMD utility. Below mentioned details:
ASMCMD> ls -ltr*
Type Redund Striped Time Sys Name*
N ARCHIVELOG/*
N AUTOBACKUP/*
N ONLINELOG/*
N controlfile/*
N primarch/*
N 1_1_748661470.dbf => FRA/CRMSTBY/ARCHIVELOG/2011_04_17/thread_1_seq_1.6721.748666233+*
N 1_1_748747875.dbf => FRA/CRMSTBY/ARCHIVELOG/2011_04_18/thread_1_seq_1.6142.748752703+*
N 1_1_748834274.dbf => FRA/CRMSTBY/ARCHIVELOG/2011_04_19/thread_1_seq_1.4771.748839479+*
N 1_1_748920673.dbf => FRA/CRMSTBY/ARCHIVELOG/2011_04_20/thread_1_seq_1.656.748925823+*
N 1_1_749007075.dbf => FRA/CRMSTBY/ARCHIVELOG/2011_04_21/thread_1_seq_1.1768.749012141+*
Below mentioned system information.
DB : Release 10.2.0.4.0
OS : Linux Enterprise release 5.2 (Carthage)
Regards,
Vishal -
How I can log Sequence File version number to database?
Hi,
As in the subject.
How I can log Sequence File version number to database?
There is nothing like that under Logging object.Do you need it in a separate field in the databse?
One option is to just add it as an additional result in a step in your sequence file.
RunState.SequenceFile.AsPropertyObjectFile.Version
Hope this helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~ -
Hi,
Oracle RAC database 10.2.0.3/RedHat4 with 2 nodes.
In the begining we had an error ORA-600[12803] so only sys can connect to database I find the note 1026653.6 this note said that we need to create AUDSES$ sequence but befor that we have to restart the database.
When we stop the datanbase we had another ORA-600 and it's impossible to start it!!
Here is a coppy of our alert file:
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes = 300
sessions = 335
sga_max_size = 524288000
__shared_pool_size = 310378496
__large_pool_size = 4194304
__java_pool_size = 8388608
__streams_pool_size = 8388608
spfile = +DATA/osista/spfileosista.ora
nls_language = FRENCH
nls_territory = FRANCE
nls_length_semantics = CHAR
sga_target = 524288000
control_files = DATA/osista/controlfile/control01.ctl, DATA/osista/controlfile/control02.ctl
db_block_size = 8192
__db_cache_size = 184549376
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=USE_DB_RECOVERY_FILE_DEST
db_file_multiblock_read_count= 16
cluster_database = TRUE
cluster_database_instances= 2
db_create_file_dest = +DATA
db_recovery_file_dest = +FLASH
db_recovery_file_dest_size= 68543315968
thread = 2
instance_number = 2
undo_management = AUTO
undo_tablespace = UNDOTBS2
undo_retention = 29880
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=OSISTAXDB)
local_listener = (address=(protocol=tcp)(port=1521)(host=132.147.160.243))
remote_listener = LISTENERS_OSISTA
job_queue_processes = 10
background_dump_dest = /oracle/product/admin/OSISTA/bdump
user_dump_dest = /oracle/product/admin/OSISTA/udump
core_dump_dest = /oracle/product/admin/OSISTA/cdump
audit_file_dest = /oracle/product/admin/OSISTA/adump
db_name = OSISTA
open_cursors = 300
pga_aggregate_target = 104857600
aq_tm_processes = 1
Cluster communication is configured to use the following interface(s) for this instance
172.16.0.2
Wed Jun 13 11:04:30 2012
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=8560
DIAG started with pid=3, OS id=8562
PSP0 started with pid=4, OS id=8566
LMON started with pid=5, OS id=8570
LMD0 started with pid=6, OS id=8574
LMS0 started with pid=7, OS id=8576
LMS1 started with pid=8, OS id=8580
MMAN started with pid=9, OS id=8584
DBW0 started with pid=10, OS id=8586
LGWR started with pid=11, OS id=8588
CKPT started with pid=12, OS id=8590
SMON started with pid=13, OS id=8592
RECO started with pid=14, OS id=8594
CJQ0 started with pid=15, OS id=8596
MMON started with pid=16, OS id=8598
Wed Jun 13 11:04:31 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=17, OS id=8600
Wed Jun 13 11:04:31 2012
starting up 1 shared server(s) ...
Wed Jun 13 11:04:31 2012
lmon registered with NM - instance id 2 (internal mem no 1)
Wed Jun 13 11:04:31 2012
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
1
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Wed Jun 13 11:04:31 2012
LMS 0: 0 GCS shadows cancelled, 0 closed
Wed Jun 13 11:04:31 2012
LMS 1: 0 GCS shadows cancelled, 0 closed
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Post SMON to start 1st pass IR
Wed Jun 13 11:04:31 2012
LMS 0: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:04:31 2012
LMS 1: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:04:31 2012
Submitted all GCS remote-cache requests
Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=20, OS id=8877
Wed Jun 13 11:04:43 2012
alter database mount
Wed Jun 13 11:04:43 2012
This instance was first to mount
Wed Jun 13 11:04:43 2012
Starting background process ASMB
ASMB started with pid=25, OS id=10068
Starting background process RBAL
RBAL started with pid=26, OS id=10072
Wed Jun 13 11:04:47 2012
SUCCESS: diskgroup DATA was mounted
Wed Jun 13 11:04:51 2012
Setting recovery target incarnation to 1
Wed Jun 13 11:04:52 2012
Successful mount of redo thread 2, with mount id 3005749259
Wed Jun 13 11:04:52 2012
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: alter database mount
Wed Jun 13 11:05:06 2012
alter database open
Wed Jun 13 11:05:06 2012
This instance was first to open
Wed Jun 13 11:05:06 2012
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Wed Jun 13 11:05:07 2012
Started redo scan
Wed Jun 13 11:05:07 2012
Completed redo scan
61 redo blocks read, 4 data blocks need recovery
Wed Jun 13 11:05:07 2012
Started redo application at
Thread 1: logseq 7924, block 3, scn 506098125
Wed Jun 13 11:05:07 2012
Recovery of Online Redo Log: Thread 1 Group 2 Seq 7924 Reading mem 0
Mem# 0: +DATA/osista/onlinelog/group_2.372.742132543
Wed Jun 13 11:05:07 2012
Completed redo application
Wed Jun 13 11:05:07 2012
Completed crash recovery at
Thread 1: logseq 7924, block 64, scn 506118186
4 data blocks read, 4 data blocks written, 61 redo blocks read
Switch log for thread 1 to sequence 7925
Picked broadcast on commit scheme to generate SCNs
db_recovery_file_dest_size of 65368 MB is 0.61% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
SUCCESS: diskgroup FLASH was mounted
SUCCESS: diskgroup FLASH was dismounted
Thread 1 advanced to log sequence 7926
SUCCESS: diskgroup FLASH was mounted
SUCCESS: diskgroup FLASH was dismounted
Thread 1 advanced to log sequence 7927
Wed Jun 13 11:05:11 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=31, OS id=12747
Wed Jun 13 11:05:11 2012
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=32, OS id=12749
Wed Jun 13 11:05:12 2012
Thread 2 opened at log sequence 7176
Current log# 4 seq# 7176 mem# 0: +DATA/osista/onlinelog/group_4.289.742134597
Wed Jun 13 11:05:12 2012
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Wed Jun 13 11:05:12 2012
Successful open of redo thread 2
Wed Jun 13 11:05:12 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Jun 13 11:05:12 2012
ARC0: Becoming the heartbeat ARCH
Wed Jun 13 11:05:12 2012
SMON: enabling cache recovery
Wed Jun 13 11:05:15 2012
Successfully onlined Undo Tablespace 20.
Wed Jun 13 11:05:15 2012
SMON: enabling tx recovery
Wed Jun 13 11:05:15 2012
Database Characterset is AL32UTF8
Wed Jun 13 11:05:16 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_9174.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Wed Jun 13 11:05:16 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_9174.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
USER: terminating instance due to error 600
Instance terminated by USER, pid = 9174
ORA-1092 signalled during: alter database open...
Wed Jun 13 11:06:16 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 eth0 172.16.0.0 configured from OCR for use as a cluster interconnect
Interface type 1 bond0 132.147.160.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes = 300
sessions = 335
sga_max_size = 524288000
__shared_pool_size = 314572800
__large_pool_size = 4194304
__java_pool_size = 8388608
__streams_pool_size = 8388608
spfile = +DATA/osista/spfileosista.ora
nls_language = FRENCH
nls_territory = FRANCE
nls_length_semantics = CHAR
sga_target = 524288000
control_files = DATA/osista/controlfile/control01.ctl, DATA/osista/controlfile/control02.ctl
db_block_size = 8192
__db_cache_size = 180355072
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=USE_DB_RECOVERY_FILE_DEST
db_file_multiblock_read_count= 16
cluster_database = TRUE
cluster_database_instances= 2
db_create_file_dest = +DATA
db_recovery_file_dest = +FLASH
db_recovery_file_dest_size= 68543315968
thread = 2
instance_number = 2
undo_management = AUTO
undo_tablespace = UNDOTBS2
undo_retention = 29880
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=OSISTAXDB)
local_listener = (address=(protocol=tcp)(port=1521)(host=132.147.160.243))
remote_listener = LISTENERS_OSISTA
job_queue_processes = 10
background_dump_dest = /oracle/product/admin/OSISTA/bdump
user_dump_dest = /oracle/product/admin/OSISTA/udump
core_dump_dest = /oracle/product/admin/OSISTA/cdump
audit_file_dest = /oracle/product/admin/OSISTA/adump
db_name = OSISTA
open_cursors = 300
pga_aggregate_target = 104857600
aq_tm_processes = 1
Cluster communication is configured to use the following interface(s) for this instance
172.16.0.2
Wed Jun 13 11:06:16 2012
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=18682
DIAG started with pid=3, OS id=18684
PSP0 started with pid=4, OS id=18695
LMON started with pid=5, OS id=18704
LMD0 started with pid=6, OS id=18721
LMS0 started with pid=7, OS id=18735
LMS1 started with pid=8, OS id=18753
MMAN started with pid=9, OS id=18767
DBW0 started with pid=10, OS id=18788
LGWR started with pid=11, OS id=18796
CKPT started with pid=12, OS id=18799
SMON started with pid=13, OS id=18801
RECO started with pid=14, OS id=18803
CJQ0 started with pid=15, OS id=18805
MMON started with pid=16, OS id=18807
Wed Jun 13 11:06:17 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=17, OS id=18809
Wed Jun 13 11:06:17 2012
starting up 1 shared server(s) ...
Wed Jun 13 11:06:17 2012
lmon registered with NM - instance id 2 (internal mem no 1)
Wed Jun 13 11:06:17 2012
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
1
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Wed Jun 13 11:06:18 2012
LMS 0: 0 GCS shadows cancelled, 0 closed
Wed Jun 13 11:06:18 2012
LMS 1: 0 GCS shadows cancelled, 0 closed
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Post SMON to start 1st pass IR
Wed Jun 13 11:06:18 2012
LMS 0: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:06:18 2012
LMS 1: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:06:18 2012
Submitted all GCS remote-cache requests
Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=20, OS id=18816
Wed Jun 13 11:06:18 2012
ALTER DATABASE MOUNT
Wed Jun 13 11:06:18 2012
This instance was first to mount
Wed Jun 13 11:06:18 2012
Reconfiguration started (old inc 2, new inc 4)
List of nodes:
0 1
Wed Jun 13 11:06:18 2012
Starting background process ASMB
Wed Jun 13 11:06:18 2012
Global Resource Directory frozen
Communication channels reestablished
ASMB started with pid=22, OS id=18913
Starting background process RBAL
* domain 0 valid = 0 according to instance 0
Wed Jun 13 11:06:18 2012
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Wed Jun 13 11:06:18 2012
LMS 0: 0 GCS shadows cancelled, 0 closed
Wed Jun 13 11:06:18 2012
LMS 1: 0 GCS shadows cancelled, 0 closed
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Wed Jun 13 11:06:18 2012
LMS 0: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:06:18 2012
LMS 1: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:06:18 2012
Submitted all GCS remote-cache requests
Fix write in gcs resources
RBAL started with pid=23, OS id=18917
Reconfiguration complete
Wed Jun 13 11:06:22 2012
SUCCESS: diskgroup DATA was mounted
Wed Jun 13 11:06:26 2012
Setting recovery target incarnation to 1
Wed Jun 13 11:06:26 2012
Successful mount of redo thread 2, with mount id 3005703530
Wed Jun 13 11:06:26 2012
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: ALTER DATABASE MOUNT
Wed Jun 13 11:06:27 2012
ALTER DATABASE OPEN
This instance was first to open
Wed Jun 13 11:06:27 2012
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Wed Jun 13 11:06:27 2012
Started redo scan
Wed Jun 13 11:06:27 2012
Completed redo scan
61 redo blocks read, 4 data blocks need recovery
Wed Jun 13 11:06:28 2012
Started redo application at
Thread 2: logseq 7176, block 3
Wed Jun 13 11:06:28 2012
Recovery of Online Redo Log: Thread 2 Group 4 Seq 7176 Reading mem 0
Mem# 0: +DATA/osista/onlinelog/group_4.289.742134597
Wed Jun 13 11:06:28 2012
Completed redo application
Wed Jun 13 11:06:28 2012
Completed crash recovery at
Thread 2: logseq 7176, block 64, scn 506138248
4 data blocks read, 4 data blocks written, 61 redo blocks read
Picked broadcast on commit scheme to generate SCNs
Wed Jun 13 11:06:28 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=28, OS id=19692
Wed Jun 13 11:06:28 2012
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=29, OS id=19695
Wed Jun 13 11:06:28 2012
Thread 2 advanced to log sequence 7177
Thread 2 opened at log sequence 7177
Current log# 3 seq# 7177 mem# 0: +DATA/osista/onlinelog/group_3.291.742134597
Successful open of redo thread 2
Wed Jun 13 11:06:28 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Jun 13 11:06:28 2012
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Wed Jun 13 11:06:28 2012
ARC1: Becoming the heartbeat ARCH
Wed Jun 13 11:06:28 2012
SMON: enabling cache recovery
Wed Jun 13 11:06:28 2012
db_recovery_file_dest_size of 65368 MB is 0.61% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
SUCCESS: diskgroup FLASH was mounted
SUCCESS: diskgroup FLASH was dismounted
Wed Jun 13 11:06:31 2012
Successfully onlined Undo Tablespace 20.
Wed Jun 13 11:06:31 2012
SMON: enabling tx recovery
Wed Jun 13 11:06:31 2012
Database Characterset is AL32UTF8
Wed Jun 13 11:06:31 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_19596.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Wed Jun 13 11:06:32 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_19596.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
USER: terminating instance due to error 600
Instance terminated by USER, pid = 19596
ORA-1092 signalled during: ALTER DATABASE OPEN...
Wed Jun 13 11:11:35 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 eth0 172.16.0.0 configured from OCR for use as a cluster interconnect
Interface type 1 bond0 132.147.160.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes = 300
sessions = 335
sga_max_size = 524288000
__shared_pool_size = 318767104
__large_pool_size = 4194304
__java_pool_size = 8388608
__streams_pool_size = 8388608
spfile = +DATA/osista/spfileosista.ora
nls_language = FRENCH
nls_territory = FRANCE
nls_length_semantics = CHAR
sga_target = 524288000
control_files = DATA/osista/controlfile/control01.ctl, DATA/osista/controlfile/control02.ctl
db_block_size = 8192
__db_cache_size = 176160768
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=USE_DB_RECOVERY_FILE_DEST
db_file_multiblock_read_count= 16
cluster_database = TRUE
cluster_database_instances= 2
db_create_file_dest = +DATA
db_recovery_file_dest = +FLASH
db_recovery_file_dest_size= 68543315968
thread = 2
instance_number = 2
undo_management = AUTO
undo_tablespace = UNDOTBS2
undo_retention = 29880
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=OSISTAXDB)
local_listener = (address=(protocol=tcp)(port=1521)(host=132.147.160.243))
remote_listener = LISTENERS_OSISTA
job_queue_processes = 10
background_dump_dest = /oracle/product/admin/OSISTA/bdump
user_dump_dest = /oracle/product/admin/OSISTA/udump
core_dump_dest = /oracle/product/admin/OSISTA/cdump
audit_file_dest = /oracle/product/admin/OSISTA/adump
db_name = OSISTA
open_cursors = 300
pga_aggregate_target = 104857600
aq_tm_processes = 1
Cluster communication is configured to use the following interface(s) for this instance
172.16.0.2
Wed Jun 13 11:11:35 2012
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=16101
DIAG started with pid=3, OS id=16103
PSP0 started with pid=4, OS id=16105
LMON started with pid=5, OS id=16107
LMD0 started with pid=6, OS id=16110
LMS0 started with pid=7, OS id=16112
LMS1 started with pid=8, OS id=16116
MMAN started with pid=9, OS id=16120
DBW0 started with pid=10, OS id=16132
LGWR started with pid=11, OS id=16148
CKPT started with pid=12, OS id=16169
SMON started with pid=13, OS id=16185
RECO started with pid=14, OS id=16203
CJQ0 started with pid=15, OS id=16219
MMON started with pid=16, OS id=16227
Wed Jun 13 11:11:36 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=17, OS id=16229
Wed Jun 13 11:11:36 2012
starting up 1 shared server(s) ...
Wed Jun 13 11:11:36 2012
lmon registered with NM - instance id 2 (internal mem no 1)
Wed Jun 13 11:11:36 2012
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
1
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Wed Jun 13 11:11:36 2012
LMS 0: 0 GCS shadows cancelled, 0 closed
Wed Jun 13 11:11:36 2012
LMS 1: 0 GCS shadows cancelled, 0 closed
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Post SMON to start 1st pass IR
Wed Jun 13 11:11:36 2012
LMS 1: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:11:36 2012
LMS 0: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:11:36 2012
Submitted all GCS remote-cache requests
Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=20, OS id=16235
Wed Jun 13 11:11:37 2012
ALTER DATABASE MOUNT
Wed Jun 13 11:11:37 2012
This instance was first to mount
Wed Jun 13 11:11:37 2012
Starting background process ASMB
ASMB started with pid=22, OS id=16343
Starting background process RBAL
RBAL started with pid=23, OS id=16347
Wed Jun 13 11:11:44 2012
SUCCESS: diskgroup DATA was mounted
Wed Jun 13 11:11:49 2012
Setting recovery target incarnation to 1
Wed Jun 13 11:11:49 2012
Successful mount of redo thread 2, with mount id 3005745065
Wed Jun 13 11:11:49 2012
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: ALTER DATABASE MOUNT
Wed Jun 13 11:22:25 2012
alter database open
This instance was first to open
Wed Jun 13 11:22:26 2012
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Wed Jun 13 11:22:26 2012
Started redo scan
Wed Jun 13 11:22:26 2012
Completed redo scan
61 redo blocks read, 4 data blocks need recovery
Wed Jun 13 11:22:26 2012
Started redo application at
Thread 1: logseq 7927, block 3
Wed Jun 13 11:22:26 2012
Recovery of Online Redo Log: Thread 1 Group 1 Seq 7927 Reading mem 0
Mem# 0: +DATA/osista/onlinelog/group_1.283.742132543
Wed Jun 13 11:22:26 2012
Completed redo application
Wed Jun 13 11:22:26 2012
Completed crash recovery at
Thread 1: logseq 7927, block 64, scn 506178382
4 data blocks read, 4 data blocks written, 61 redo blocks read
Switch log for thread 1 to sequence 7928
Picked broadcast on commit scheme to generate SCNs
Wed Jun 13 11:22:27 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=31, OS id=13010
Wed Jun 13 11:22:27 2012
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=32, OS id=13033
Wed Jun 13 11:22:27 2012
Thread 2 opened at log sequence 7178
Current log# 4 seq# 7178 mem# 0: +DATA/osista/onlinelog/group_4.289.742134597
Successful open of redo thread 2
Wed Jun 13 11:22:27 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Jun 13 11:22:27 2012
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Wed Jun 13 11:22:27 2012
ARC1: Becoming the heartbeat ARCH
Wed Jun 13 11:22:27 2012
SMON: enabling cache recovery
Wed Jun 13 11:22:30 2012
db_recovery_file_dest_size of 65368 MB is 0.61% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
SUCCESS: diskgroup FLASH was mounted
SUCCESS: diskgroup FLASH was dismounted
Wed Jun 13 11:22:31 2012
Successfully onlined Undo Tablespace 20.
Wed Jun 13 11:22:31 2012
SMON: enabling tx recovery
Wed Jun 13 11:22:32 2012
Database Characterset is AL32UTF8
Wed Jun 13 11:22:32 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_11751.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Wed Jun 13 11:22:33 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_11751.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
USER: terminating instance due to error 600
Instance terminated by USER, pid = 11751
ORA-1092 signalled during: alter database open...
regards,Hi;
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_9174.trc:Did you check trc file?
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []You are getting oracle internal error(ORA 600) which mean you could need to work wiht oracle support team. Please see below note, if its not help than i suggest log a sr:
Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool [ID 153788.1]
for your future rac issue please use Forum Home » High Availability » RAC, ASM & Clusterware Installation which is RAC dedicated forum site.
Regard
Helios -
Get the table's rowid of the session that is locking in RAC database
I am a developer and not a DBA and I need to find th correct query to find the exact rowid of the record locked on a table. This is for a RAC database and locked record can be from the web form in oracle application server. When I try to get the correct row id, I get the following error:
ORA-01410 - Invalid row id
For the criteria, the output is Dbms_Rowid.rowid_create(1, -1, 36, 7845, 0), why I get a -1 for the ROW_WAIT_OBJ#?
Additional Information: The lock type is DML and the lock mode is: Row Exclusive, the table is locked and the program is web oracle forms executiong.
I am executing the query in Oracle Database 11g Enterprise Edition Release 11.1.0.7.0
How to accomplish gettting the correct rowid? Below is the selection criteria I have:
select vs.inst_id,
vs.audsid audsid,
locks.sid sid,
locks.type,
locks.id1 id1,
locks.id2 id2,
locks.lmode lmode,
locks.request request,
locks.ctime ctime,
locks.block block,
vs.serial# serial#,
vs.username oracle_user,
vs.osuser os_user,
vs.program program,
vs.module module,
vs.action action,
vs.process process,
decode(locks.lmode,
0, '0 None',
1, '1 NULL',
2, '2 Row Share',
3, '3 Row Exclusive',
4, '4 Share',
5, '5 Share Row Exclusive',
6, '6 Exclusive', '?') lock_mode_held,
decode(locks.request,
0, '0 None',
1, '1 NULL',
2, '2 Row Share',
3, '3 Row Exclusive',
4, '4 Share',
5, '5 Share Row Exclusive',
6, '6 Exclusive', '?') lock_mode_requested,
decode(locks.type,
'MR', 'Media Recovery',
'RT', 'Redo Thread',
'UN', 'User Name',
'TX', 'Transaction',
'TM', 'DML',
'UL', 'PL/SQL User Lock',
'DX', 'Distributed Xaction',
'CF', 'Control File',
'IS', 'Instance State',
'FS', 'File Set',
'IR', 'Instance Recovery',
'ST', 'Disk Space Transaction',
'TS', 'Temp Segment',
'IV', 'Library Cache Invalidation',
'LS', 'Log Start or Log Switch',
'RW', 'Row Wait',
'SQ', 'Sequence Number',
'TE', 'Extend Table',
'TT', 'Temp Table',
locks.type) lock_type,
vs.row_wait_obj# row_wait_obj#,
vs.row_wait_file# row_wait_file,
vs.row_wait_block# row_wait_block#,
vs.row_wait_row# row_wait_row#,
dbms_rowid.rowid_create ( 1, vs.ROW_WAIT_OBJ#, vs.ROW_WAIT_FILE#, vs.ROW_WAIT_BLOCK#, vs.ROW_WAIT_ROW# ) rowid_created,
objs.owner object_owner,
objs.object_name object_name,
objs.object_type object_type,
round( locks.ctime/60, 2 ) lock_time_in_minutes,
from gv$session vs,
gv$lock locks,
dba_objects objs,
dba_tables tbls
where locks.id1 = objs.object_id
and vs.sid = locks.sid
and objs.owner = tbls.owner
and objs.object_name = tbls.table_name
and objs.owner != 'SYS'
-- and locks.type in ('TM', 'TX')
order by lock_time_in_minutes;
Edited by: user3564713 on Jun 10, 2012 10:56 PMFirstly, read this thread
Identifying locked rows
And the last bit from Randolf
>
It is a common misconception that you can locate a locked row in Oracle via a query. The point is that the information that you're querying only gets populated in case of a blocking lock, and even then not in every case, since you might have blocking locks that do not refer to a particular row.
Oracle stores the lock information within the block, so if you identified in which block the row is located that you've attempted to lock, you could get detailed information about the row locks of that block by performing a block dump.
Other than that Oracle doesn't maintain this information anywhere else and it is only externalized for blocking situations - it is a matter of design that there is no central lock manager in Oracle that would inherently limit scalability, hence the downside of that approach is that there is no central information pool where you could obtain detailed information about row level locks.
>
However, if you see support note "Sample Code to Select from a Table EXCLUDING Locked Rows [ID 186531.1]"
You can take the same code from the script in that note to identify rowid of the locked rows. -
Another RMAN duplicate problem - RAC database to single instance
Hi,
I have a problem with the RMAN duplicate procedure and was hoping someone can help.
I would like to create a duplicate of our production RAC database on a separate, stand-alone, database server on another site. This duplicate will be used for intensive querying by another business unit who I don't want to have access to our production database.
My procedure goes like this:
1. Create a disk (not ASM) based backup of the datafiles and any archived redo logs:
"run {
allocate channel d1 type disk;
backup format '/u02/stage/df_t%t_s%s_p%p' database plus archivelog delete input;
release channel d1;
2. Tar and scp these files to the same location on the stand-alone database server.
3. In the meantime, work has been happening on the production database and further archived redo logs have been generated. I don't really care about these logs for the purposes of the duplicate however, I just want to duplicate to the point of the recent backup. To do this, I run the following SQL to determine the sequence number that I should be duplicating up to:
"select max(sequence#), thread# from v$archived_log where deleted='YES' group by thread#;"
4. Duplicate the production database to the stand-alone database (all the SQL Net stuff is working).
"run {
set until sequence (value returned by above SQL statement);
duplicate target database to XXX;
However, my problem arises because I don't know how to handle the fact that there are two threads. I understand that each thread relates to one of the RAC instances, I just don't know which one to specify for the duplicate. We have a database service which the client application connects through, and that service runs on on or other of the instances. Should I just care about the logs from the instance where the service is currently running?
Am I even approaching this is the correct way?
I look forward to any help that people may be able to offer.
Regards,
PhilHi Werner,
Thanks again for your help, there is still something wrong though. "list backup of archivelog all;" shows:
BS Key Size Device Type Elapsed Time Completion Time
3784 202.34M DISK 00:00:08 28-OCT-09
BP Key: 3784 Status: AVAILABLE Compressed: NO Tag: TAG20091028T111718
Piece Name: /u02/stage/df_t701435838_s3820_p1
List of Archived Logs in backup set 3784
Thrd Seq Low SCN Low Time Next SCN Next Time
1 9746 569095777 28-OCT-09 569150229 28-OCT-09
1 9747 569150229 28-OCT-09 569187892 28-OCT-09
1 9748 569187892 28-OCT-09 569231956 28-OCT-09
1 9749 569231956 28-OCT-09 569259816 28-OCT-09
2 7931 569095774 28-OCT-09 569187902 28-OCT-09
2 7932 569187902 28-OCT-09 569259814 28-OCT-09
BS Key Size Device Type Elapsed Time Completion Time
3787 1.04M DISK 00:00:02 28-OCT-09
BP Key: 3787 Status: AVAILABLE Compressed: NO Tag: TAG20091028T112222
Piece Name: /u02/stage/df_t701436142_s3823_p1
List of Archived Logs in backup set 3787
Thrd Seq Low SCN Low Time Next SCN Next Time
1 9750 569259816 28-OCT-09 569261110 28-OCT-09
2 7933 569259814 28-OCT-09 569261108 28-OCT-09
You can see that the highest sequence number is 9750 of thread 1, and that the Low and Next SCNs are 569259816 and 56926111. However, when I look at the output of the RMAN duplicate command:
contents of Memory Script:
set until scn 569505448;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 28-OCT-09
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=39 devtype=DISK
starting media recovery
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 4 needs more recovery to be consistent
ORA-01110: data file 4: '/u02/sca-standby/data/users.260.623418479'
RMAN-03002: failure of Duplicate Db command at 10/28/2009 16:12:55
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 log thread 2 seq 7936 lowscn 569411744 found to restore
RMAN-06025: no backup of log thread 2 seq 7935 lowscn 569321987 found to restore
RMAN-06025: no backup of log thread 2 seq 7934 lowscn 569261108 found to restore
RMAN-06025: no backup of log thread 1 seq 9758 lowscn 569471890 found to restore
RMAN-06025: no backup of log thread 1 seq 9757 lowscn 569440076 found to restore
RMAN-06025: no backup of log thread 1 seq 9756 lowscn 569411439 found to restore
RMAN-06025: no backup of log thread 1 seq 9755 lowscn 569378529 found to restore
RMAN-06025: no backup of log thread 1 seq 9754 lowscn 569358970 found to restore
RMAN-06025: no backup of log thread 1 seq 9753 lowscn 569321882 found to restore
RMAN-06025: no backup of log thread 1 seq 9752 lowscn 569284238 found to restore
RMAN-06025: no backup of log thread 1 seq 9751 lowscn 569261110 found to restore
you can see that something is setting the recovery SCN to 569505448 which higher even then any of the archived logs mentioned above. If I select current_scn from the production database, this gives me 569528258 which is closer to the value which RMAN is expecting to recover to than any of the archived redo logs.
Can you think what might be causing RMAN to try to recover to this value? and why does it appear to be ignoring the SET UNTIL SEQUENCE command?
Cheers,
Phil -
Thread 1 cannot allocate new log, sequence 1558 Checkpoint not complete
hi,
i m working on oracle 10g rac database on aix machine . i m getting this error on peck time
Thread 1 cannot allocate new log, sequence 1558 Checkpoint not complete
i read lots of documents and they asked to increase size of redo file or add more redo files.
can u plz describe me y m i getting this error ? & how adding redo file can help in this error.
thxswhen yours current redo log filled and then started to switch another log then checkpoint occurs ,this checkpoint started to write dirty buffer from buffer cache to datafile , you cannot reuse this logfile unless checkpoint process writes alls dirty buffer from buffer cache to disk which contained this redo log file.If you attempt to reuse the same log file which cause to checkpoint upon log switch then you will get this error.
Typically this error comes where yours number of redo log switches occuring too frequently or you have less number of redo logs.
lets say if you have 2 redolog file A and B,yours A redolog filled and then oracle switch from redo log A to B,checkpoint occurs,DBWRn started to write dirty buffer to disk meanwhile yours redo log B also get filled antoher log switch occurs to be attempt to reuse redo log file A ,but redo log A will not be entertain unless the previous checpoint completed to write alls dirty block from buffer cache to hard disk which is contained thats redo log A.
Adding redo log will be helpful in this case that redo log will switch to another new added redo log say C and A log file will get more time to be completed checkpoint which he/she contains contents.
Khurram -
Rebuilding RAC database from RAC database
Hi All,
Oracle : 10.2.0.4
OS : Linux
I am rebuilding a new RAC database from different RAC database manually from hot bacckup.
Everthing is ok for me but when we try to recoer the new db it will asks you archs to apply.
It will prompt you for the first arch from any thread , after applying the 1st it will not prompt you without giving next arch sequence no from any thread.
I spent time on it and finally get to know that its an oracle bug .
I just want to know wheather is thr any options for us by which we can know the arch sequence no.
Any suggestions wud b appreciated.
Thanks.
VirenderHi Hemant,
I know the v4recovery_log option to check the next archive.
ut below is the situation m facing.
M trying to apply the arch asked by oracle but still its not applying it and showig it in v$recovery_log. Kindly check teh below output:
SQL> startup nomount
ORACLE instance started.
Total System Global Area 5033164800 bytes
Fixed Size 2090880 bytes
Variable Size 2097154176 bytes
Database Buffers 2919235584 bytes
Redo Buffers 14684160 bytes
SQL> @controlfile.sql
Control file created.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 135795310 generated at 03/25/2010 16:05:37 needed for thread
3
ORA-00289: suggestion :
/etrade/plt/eeo/dbs/PLTEC2R/arch/arch_PLTEC2R_3_1585_710012162.log
ORA-00280: change 135795310 for thread 3 is in sequence #1585
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/etrade/plt/eeo/rac/PLTEC2R1/bkup/bkup1/arch_PLTEP2R_3_1585_710012162.log
ORA-00279: change 135795310 generated at needed for thread 1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/etrade/plt/eeo/rac/PLTEC2R1/bkup/bkup1/arch_PLTEP2R_3_1586_710012162.log
ORA-00325: archived log for thread 1, wrong thread # 3 in header
ORA-00334: archived log:
'/etrade/plt/eeo/rac/PLTEC2R1/bkup/bkup1/arch_PLTEP2R_3_1586_710012162.log'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1:
'/etrade/plt/eeo/dbs/PLTEC2R/data1/PLTEC2R.system_01.dbf'
SQL> select * from v$recovery_log;
THREAD# SEQUENCE# TIME
ARCHIVE_NAME
3 1585 25-MAR-10
/etrade/plt/eeo/dbs/PLTEC2R/arch/arch_PLTEC2R_3_1585_710012162.log -
Enable Archivelog Mode On 2 Node RAC DATABASE
hi,
We are having 2 Node Rac 10g Database Installed on Windows.
Currently the Database is in Non Archivelog Mode.
I want to convert it to Archivelog Mode.
I come to know the steps to convert cluster database to Archivelog mode.
i.e.
set archive parameters like Disk Location and Archivelog File format.
then Convert the database in Exclusive Mode
ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
then
C:\> srvctl stop database -d <Global_DB_SID>
then enable Archivelog Mode.
SQL> STARTUP MOUNT;
SQL> ARCHIVE LOG START;
SQL> ALTER DATABASE ARCHIVELOG;
SQL> ALTER DATABASE SET cluster_database=TRUE SCOPE=spfile;
SQL> SHUTDOWN IMMEDIATE
C:\> srvctl start database -d <Global_DB_SID>
But I am confuse with Do i need to RUN this commands in both the nodes seperatly or only on any one node.
Please Reply,comments embeddedf
Node 1: OSERP1
Log on to OSERP1 Server
C:\> sqlplus sys/oracle@racdb2 as sysdba
SQL> ALTER SYSTEM SET log_archive_format='arch_%t_%s.arc' SCOPE=spfile ; -- this needs to be database wide
SQL > ALTER SYSTEM SET log_archive_dest_1='location=\\OSERP1\archive$\ERP1 ' SCOPE=spfile sid ='ERP1'; -- required quotes added
-- not required
SQL> ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
not required to connect to other node
-- not required
SQL> ALTER SYSTEM SET log_archive_format='arch_%t_%s.arc' SCOPE=spfile sid =ERP2;
SQL > ALTER SYSTEM SET log_archive_dest_1='location=\\OSERP2\archive$\ERP2 ' SCOPE=spfile sid ='ERP2'; -- quotes added
-- not required, and database wide setting
SQL> ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
Then following commands will be run connecting any of the instance
-- database has to be stopped first, if you stick to switching it to a non-cluster database
C:\> set ORACLE_SID=<local_instance_id>
C:\> sqlplus / as sysdba
SQL> STARTUP MOUNT;
-- wrong sequence of commands
SQL> ARCHIVE LOG START;
SQL> ALTER DATABASE ARCHIVELOG;
-- not required (see previous steps)
SQL> ALTER DATABASE SET cluster_database=TRUE SCOPE=spfile;
SQL> SHUTDOWN IMMEDIATE;
6. Start the cluster database.
C:\> srvctl start database -d <Global_DB_SID>
-- There is no such thing as a <Global_DB_SID>. There is a database name.
Please note your tnsnames.ora, in a standard install, needs to have the following service names.
ERP
ERP1
ERP2
I'm not sure why you have the non-standard service_name racdb2.
Somehow it looks like you both don't understand the RAC concept, and didn't understand my answer. I had to correct several things I already corrected in my previous response. I'm not sure why I'm not getting through.
Sybrand Bakker
Senior Oracle DBA -
Unable to startup 12c RAC database, can't open spfile in ASM
hello,
I'm testing 12cRAC database on RHEL5 and need your help to troubleshoot and fix the following issue -
DBCA fails at the end of the configuration to create and startup new RAC database with the following errors
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+DATA/TDB1/spfileTDB1.ora'
ORA-17503: ksfdopn:2 Failed to open file +DATA/TDB1/spfileTDB1.ora
ORA-15056: additional error message
ORA-17503: ksfdopn:2 Failed to open file +DATA/TDB1/spfiletdb1.ora
ORA-01017: invalid username/password; logon denied
I also tried executing script (which was created by DBCA) to create the new DB manually and got the same results - it happens during first attempt to start it up using SPFILE after new DB was successfully created (it was started up using pfile)
Clusterware with ASM install was successful, binaries were also installed without issues,
cluster seems healthy, I see correct files within ASM using asmcmd etc ..
got stuck here and need some directions ... very confused by ORA-01017 password error
wonder if anyone had same or similar issues ?
Thank you !Fixed.
Thank you everyone for suggestions and recommendations -
ASM is accessible using asmcmd and I can see all the DB files incuding spfile, they were created by DBCA, alert log showed same information I posted
After extensive troubleshooting and testing the issue was idedntified and fixed - 'dba' group needs to be the primary group for 'oracle' user, not the secondary one. I suspected that something was not right with 'oracle' user access to asm based on that strange password error. There is more I need to check as the issue and fix with swapping groups seems strange. Secondary group is not enough ti have proper rights ??? my first reaction was - seriously ? wtf ?
Anyway - I need to move one now ...
Thank you again ! -
Hi guys,
as I am still new to RMAN I would be greatfull to You for some help and guidance here.
I am cloning database with RMAN duplicate database command and at the and of the script I got RMAN-06055: could not find log sequence 86362 thread 1 .
The script is :
RMAN> RUN {
2> allocate channel t1 type 'SBT_TAPE';
3> ALLOCATE AUXILIARY CHANNEL aux1 type 'SBT_TAPE';
4> ALLOCATE AUXILIARY CHANNEL aux2 type 'SBT_TAPE';
5> send 'NSR_ENV=(NSR_SERVER=servername,NSR_CLIENT=clientname)';
6> SET UNTIL TIME "to_date( '25.03.2008 08:00:00','dd.mm.yyyy hh24:mi:ss')";
7> DUPLICATE TARGET DATABASE TO GMIGR3
8> DB_FILE_NAME_CONVERT =('/lun0/prod/','/u01/lun0/gmigr3/'
9> '/lun1/prod/','/u01/lun0/gmigr3/'
10> '/lun2/prod/','/u01/lun0/gmigr3/'
11> '/lun3/prod/','/u01/lun0/gmigr3/'
12> '/lun4/prod/','/u01/lun0/gmigr3/'
13> )
14> PFILE = '?/dbs/initGMIGR3.ora'
15> LOGFILE
16> GROUP 1 ('/u01/lun0/gmigr3/log1a.dbf', '/u01/lun0/gmigr3/log1b.dbf') SIZE 100M,
17> GROUP 2 ('/u01/lun0/gmigr3/log2a.dbf', '/u01/lun0/gmigr3/log2b.dbf') SIZE 100M,
18> GROUP 3 ('/u01/lun0/gmigr3/log3a.dbf', '/u01/lun0/gmigr3/log3b.dbf') SIZE 100M,
19> GROUP 4 ('/u01/lun0/gmigr3/log4a.dbf', '/u01/lun0/gmigr3/log4b.dbf') SIZE 100M,
20> GROUP 5 ('/u01/lun0/gmigr3/log5a.dbf', '/u01/lun0/gmigr3/log5b.dbf') SIZE 100M REUSE
21> ;
22> release channel aux1;
23> release channel aux2;
24> release channel t1;and here is the log,
so what would be your advice on this :
allocated channel: t1
channel t1: sid=1339 devtype=SBT_TAPE
channel t1: NMO v4.5.0.0
allocated channel: aux1
channel aux1: sid=870 devtype=SBT_TAPE
channel aux1: NMO v4.5.0.0
allocated channel: aux2
channel aux2: sid=872 devtype=SBT_TAPE
channel aux2: NMO v4.5.0.0
sent command to channel: t1
sent command to channel: aux1
sent command to channel: aux2
executing command: SET until clause
Starting Duplicate Db at 25-MAR-08
contents of Memory Script:
set until scn 8177337546005;
set newname for datafile 1 to
"/u01/lun0/hanfa2/system01.dbf";
set newname for datafile 2 to
"/u01/lun0/hanfa2/system02.dbf";
set newname for datafile 3 to
"/u01/lun0/hanfa2/system03.dbf";
set newname for datafile 4 to
"/u01/lun0/hanfa2/system04.dbf";
set newname for datafile 5 to
"/u01/lun0/hanfa2/system05.dbf";
set newname for datafile 6 to
"/u01/lun0/hanfa2/ctxd01.dbf";
set newname for datafile 7 to
"/u01/lun0/hanfa2/owad01.dbf";
set newname for datafile 8 to
"/u01/lun0/hanfa2/a_queue02.dbf";
set newname for datafile 9 to
"/u01/lun0/hanfa2/odm.dbf";
set newname for datafile 10 to
"/u01/lun0/hanfa2/olap.dbf";
set newname for datafile 11 to
"/u01/lun0/hanfa2/xxcounter03.dbf";
set newname for datafile 12 to
"/u01/lun0/hanfa2/xxcounter02.dbf";
set newname for datafile 13 to
"/u01/lun0/hanfa2/xxcounter01.dbf";
set newname for datafile 14 to
"/u01/lun0/hanfa2/sysaux01.dbf";
set newname for datafile 15 to
"/u01/lun0/hanfa2/system12.dbf";
set newname for datafile 16 to
"/u01/lun0/hanfa2/undo06.dbf";
set newname for datafile 17 to
"/u01/lun0/hanfa2/disco01.dbf";
set newname for datafile 18 to
"/u01/lun0/hanfa2/disco02.dbf";
set newname for datafile 19 to
"/u01/lun0/hanfa2/disco03.dbf";
set newname for datafile 20 to
"/u01/lun0/hanfa2/a_conv01.dbf";
set newname for datafile 21 to
"/u01/lun0/hanfa2/a_conv02.dbf";
set newname for datafile 22 to
"/u01/lun0/hanfa2/a_conv03.dbf";
set newname for datafile 23 to
"/u01/lun0/hanfa2/a_conv04.dbf";
set newname for datafile 24 to
"/u01/lun0/hanfa2/a_int02.dbf";
set newname for datafile 25 to
"/u01/lun0/hanfa2/tools.dbf";
set newname for datafile 26 to
"/u01/lun0/hanfa2/a_txn_data04.dbf";
set newname for datafile 27 to
"/u01/lun0/hanfa2/a_txn_ind06.dbf";
set newname for datafile 28 to
"/u01/lun0/hanfa2/undo05.dbf";
set newname for datafile 29 to
"/u01/lun0/hanfa2/undo04.dbf";
set newname for datafile 30 to
"/u01/lun0/hanfa2/undo03.dbf";
set newname for datafile 31 to
"/u01/lun0/hanfa2/undo02.dbf";
set newname for datafile 32 to
"/u01/lun0/hanfa2/undo01.dbf";
set newname for datafile 33 to
"/u01/lun0/hanfa2/a_ts_mview03.dbf";
set newname for datafile 34 to
"/u01/lun0/hanfa2/a_ts_mview02.dbf";
set newname for datafile 35 to
"/u01/lun0/hanfa2/a_ts_mview01.dbf";
set newname for datafile 36 to
"/u01/lun0/hanfa2/foglight_ts.dbf";
set newname for datafile 37 to
"/u01/lun0/hanfa2/a_txn_data05.dbf";
set newname for datafile 38 to
"/u01/lun0/hanfa2/a_txn_data06.dbf";
set newname for datafile 39 to
"/u01/lun0/hanfa2/a_txn_data07.dbf";
set newname for datafile 40 to
"/u01/lun0/hanfa2/a_txn_ind07.dbf";
set newname for datafile 41 to
"/u01/lun0/hanfa2/a_txn_ind08.dbf";
set newname for datafile 42 to
"/u01/lun0/hanfa2/dwh01.dbf";
set newname for datafile 43 to
"/u01/lun0/hanfa2/dwh02.dbf";
set newname for datafile 288 to
"/u01/lun0/hanfa2/system10.dbf";
set newname for datafile 295 to
"/u01/lun0/hanfa2/system06.dbf";
set newname for datafile 314 to
"/u01/lun0/hanfa2/portal01.dbf";
set newname for datafile 351 to
"/u01/lun0/hanfa2/system07.dbf";
set newname for datafile 352 to
"/u01/lun0/hanfa2/system09.dbf";
set newname for datafile 353 to
"/u01/lun0/hanfa2/system08.dbf";
set newname for datafile 354 to
"/u01/lun0/hanfa2/system11.dbf";
set newname for datafile 392 to
"/u01/lun0/hanfa2/a_txn_data01.dbf";
set newname for datafile 393 to
"/u01/lun0/hanfa2/a_txn_ind01.dbf";
set newname for datafile 394 to
"/u01/lun0/hanfa2/a_ref01.dbf";
set newname for datafile 395 to
"/u01/lun0/hanfa2/a_int01.dbf";
set newname for datafile 396 to
"/u01/lun0/hanfa2/a_summ01.dbf";
set newname for datafile 397 to
"/u01/lun0/hanfa2/a_nolog01.dbf";
set newname for datafile 398 to
"/u01/lun0/hanfa2/a_archive01.dbf";
set newname for datafile 399 to
"/u01/lun0/hanfa2/a_queue01.dbf";
set newname for datafile 400 to
"/u01/lun0/hanfa2/a_media01.dbf";
set newname for datafile 401 to
"/u01/lun0/hanfa2/a_txn_data02.dbf";
set newname for datafile 402 to
"/u01/lun0/hanfa2/a_txn_data03.dbf";
set newname for datafile 403 to
"/u01/lun0/hanfa2/a_txn_ind02.dbf";
set newname for datafile 404 to
"/u01/lun0/hanfa2/a_txn_ind03.dbf";
set newname for datafile 405 to
"/u01/lun0/hanfa2/a_txn_ind04.dbf";
set newname for datafile 406 to
"/u01/lun0/hanfa2/a_txn_ind05.dbf";
set newname for datafile 407 to
"/u01/lun0/hanfa2/a_ref02.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
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 25-MAR-08
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00024 to /u01/lun0/hanfa2/a_int02.dbf
restoring datafile 00402 to /u01/lun0/hanfa2/a_txn_data03.dbf
channel aux2: reading from backup piece /full_PROD_s7jc4d6g_1_1/
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00395 to /u01/lun0/hanfa2/a_int01.dbf
restoring datafile 00404 to /u01/lun0/hanfa2/a_txn_ind03.dbf
channel aux1: reading from backup piece /full_PROD_s8jc4d6g_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_s8jc4d6g_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:48:09
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00026 to /u01/lun0/hanfa2/a_txn_data04.dbf
restoring datafile 00030 to /u01/lun0/hanfa2/undo03.dbf
channel aux1: reading from backup piece /full_PROD_s9jc4ene_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_s7jc4d6g_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:59:15
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00027 to /u01/lun0/hanfa2/a_txn_ind06.dbf
restoring datafile 00401 to /u01/lun0/hanfa2/a_txn_data02.dbf
channel aux2: reading from backup piece /full_PROD_sajc4evd_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_s9jc4ene_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:25:44
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00031 to /u01/lun0/hanfa2/undo02.dbf
restoring datafile 00397 to /u01/lun0/hanfa2/a_nolog01.dbf
channel aux1: reading from backup piece /full_PROD_sbjc4fbo_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_sajc4evd_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:26:55
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00039 to /u01/lun0/hanfa2/a_txn_data07.dbf
restoring datafile 00403 to /u01/lun0/hanfa2/a_txn_ind02.dbf
channel aux2: reading from backup piece /full_PROD_scjc4fkl_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sbjc4fbo_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:26:14
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00025 to /u01/lun0/hanfa2/tools.dbf
restoring datafile 00037 to /u01/lun0/hanfa2/a_txn_data05.dbf
channel aux1: reading from backup piece /full_PROD_sdjc4g03_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_scjc4fkl_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:21:14
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00028 to /u01/lun0/hanfa2/undo05.dbf
restoring datafile 00393 to /u01/lun0/hanfa2/a_txn_ind01.dbf
channel aux2: reading from backup piece /full_PROD_sejc4g5i_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sdjc4g03_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:22:02
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00032 to /u01/lun0/hanfa2/undo01.dbf
restoring datafile 00038 to /u01/lun0/hanfa2/a_txn_data06.dbf
channel aux1: reading from backup piece /full_PROD_sfjc4gf3_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_sejc4g5i_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:23:13
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00352 to /u01/lun0/hanfa2/system09.dbf
restoring datafile 00392 to /u01/lun0/hanfa2/a_txn_data01.dbf
channel aux2: reading from backup piece /full_PROD_sgjc4gkj_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sfjc4gf3_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:21:12
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00400 to /u01/lun0/hanfa2/a_media01.dbf
restoring datafile 00405 to /u01/lun0/hanfa2/a_txn_ind04.dbf
channel aux1: reading from backup piece /full_PROD_shjc4gtq_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_sgjc4gkj_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:16:32
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00033 to /u01/lun0/hanfa2/a_ts_mview03.dbf
restoring datafile 00406 to /u01/lun0/hanfa2/a_txn_ind05.dbf
channel aux2: reading from backup piece /full_PROD_sijc4h14_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_shjc4gtq_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:15:51
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00022 to /u01/lun0/hanfa2/a_conv03.dbf
restoring datafile 00029 to /u01/lun0/hanfa2/undo04.dbf
channel aux1: reading from backup piece /full_PROD_skjc4hcm_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_sijc4h14_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:13:42
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00035 to /u01/lun0/hanfa2/a_ts_mview01.dbf
restoring datafile 00041 to /u01/lun0/hanfa2/a_txn_ind08.dbf
channel aux2: reading from backup piece /full_PROD_sjjc4h9n_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_skjc4hcm_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:12:13
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00040 to /u01/lun0/hanfa2/a_txn_ind07.dbf
restoring datafile 00353 to /u01/lun0/hanfa2/system08.dbf
channel aux1: reading from backup piece /full_PROD_sljc4hjo_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_sjjc4h9n_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:12:53
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u01/lun0/hanfa2/system01.dbf
restoring datafile 00034 to /u01/lun0/hanfa2/a_ts_mview02.dbf
channel aux2: reading from backup piece /full_PROD_smjc4hkr_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sljc4hjo_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:10:21
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00396 to /u01/lun0/hanfa2/a_summ01.dbf
restoring datafile 00399 to /u01/lun0/hanfa2/a_queue01.dbf
channel aux1: reading from backup piece /full_PROD_sojc4hrb_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_smjc4hkr_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:08:08
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00016 to /u01/lun0/hanfa2/undo06.dbf
restoring datafile 00023 to /u01/lun0/hanfa2/a_conv04.dbf
channel aux2: reading from backup piece /full_PROD_snjc4hr8_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sojc4hrb_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:06:39
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00014 to /u01/lun0/hanfa2/sysaux01.dbf
restoring datafile 00015 to /u01/lun0/hanfa2/system12.dbf
channel aux1: reading from backup piece /full_PROD_sqjc4i1a_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_snjc4hr8_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:07:21
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00008 to /u01/lun0/hanfa2/a_queue02.dbf
restoring datafile 00394 to /u01/lun0/hanfa2/a_ref01.dbf
channel aux2: reading from backup piece /full_PROD_srjc4i49_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_sqjc4i1a_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:02:30
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00398 to /u01/lun0/hanfa2/a_archive01.dbf
restoring datafile 00407 to /u01/lun0/hanfa2/a_ref02.dbf
channel aux1: reading from backup piece /full_PROD_ssjc4i7s_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_srjc4i49_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:04:01
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00295 to /u01/lun0/hanfa2/system06.dbf
restoring datafile 00351 to /u01/lun0/hanfa2/system07.dbf
channel aux2: reading from backup piece /full_PROD_stjc4ia7_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_ssjc4i7s_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:03:51
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00042 to /u01/lun0/hanfa2/dwh01.dbf
channel aux1: reading from backup piece /full_PROD_spjc4huk_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_stjc4ia7_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:11:11
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00002 to /u01/lun0/hanfa2/system02.dbf
restoring datafile 00003 to /u01/lun0/hanfa2/system03.dbf
channel aux2: reading from backup piece /full_PROD_sujc4ics_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_spjc4huk_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:13:32
channel aux2: restored backup piece 1
piece handle=/full_PROD_sujc4ics_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:03:56
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00288 to /u01/lun0/hanfa2/system10.dbf
restoring datafile 00354 to /u01/lun0/hanfa2/system11.dbf
channel aux1: reading from backup piece /full_PROD_t0jc4if5_1_1/
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00004 to /u01/lun0/hanfa2/system04.dbf
restoring datafile 00005 to /u01/lun0/hanfa2/system05.dbf
channel aux2: reading from backup piece /full_PROD_svjc4ieu_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t0jc4if5_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:04:46
channel aux2: restored backup piece 1
piece handle=/full_PROD_svjc4ieu_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:04:46
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00020 to /u01/lun0/hanfa2/a_conv01.dbf
restoring datafile 00021 to /u01/lun0/hanfa2/a_conv02.dbf
channel aux1: reading from backup piece /full_PROD_t1jc4ihg_1_1/
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00006 to /u01/lun0/hanfa2/ctxd01.dbf
restoring datafile 00036 to /u01/lun0/hanfa2/foglight_ts.dbf
channel aux2: reading from backup piece /full_PROD_t3jc4iiu_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t1jc4ihg_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:01:45
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00013 to /u01/lun0/hanfa2/xxcounter01.dbf
restoring datafile 00018 to /u01/lun0/hanfa2/disco02.dbf
channel aux1: reading from backup piece /full_PROD_t4jc4ijd_1_1/
channel aux2: restored backup piece 1
piece handle=/full_PROD_t3jc4iiu_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:01:46
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00043 to /u01/lun0/hanfa2/dwh02.dbf
channel aux2: reading from backup piece /full_PROD_t2jc4ihh_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t4jc4ijd_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:00:36
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00009 to /u01/lun0/hanfa2/odm.dbf
restoring datafile 00314 to /u01/lun0/hanfa2/portal01.dbf
channel aux1: reading from backup piece /full_PROD_t6jc4ijs_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t6jc4ijs_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:01:16
channel aux2: restored backup piece 1
piece handle=/full_PROD_t2jc4ihh_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:01:51
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00017 to /u01/lun0/hanfa2/disco01.dbf
restoring datafile 00019 to /u01/lun0/hanfa2/disco03.dbf
channel aux1: reading from backup piece /full_PROD_t5jc4ijs_1_1/
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00011 to /u01/lun0/hanfa2/xxcounter03.dbf
restoring datafile 00012 to /u01/lun0/hanfa2/xxcounter02.dbf
channel aux2: reading from backup piece /full_PROD_t7jc4ik0_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t5jc4ijs_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:00:55
channel aux2: restored backup piece 1
piece handle=/full_PROD_t7jc4ik0_1_1/ tag=TAG20080325T041511
channel aux2: restore complete, elapsed time: 00:00:55
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00007 to /u01/lun0/hanfa2/owad01.dbf
restoring datafile 00010 to /u01/lun0/hanfa2/olap.dbf
channel aux1: reading from backup piece /full_PROD_t8jc4ik0_1_1/
channel aux1: restored backup piece 1
piece handle=/full_PROD_t8jc4ik0_1_1/ tag=TAG20080325T041511
channel aux1: restore complete, elapsed time: 00:00:45
Finished restore at 25-MAR-08
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "HANFA2" RESETLOGS ARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 5
MAXDATAFILES 512
MAXINSTANCES 8
MAXLOGHISTORY 7303
LOGFILE
GROUP 1 ( '/u01/lun0/hanfa2/log1a.dbf', '/u01/lun0/hanfa2/log1b.dbf' ) SIZE 100 M ,
GROUP 2 ( '/u01/lun0/hanfa2/log2a.dbf', '/u01/lun0/hanfa2/log2b.dbf' ) SIZE 100 M ,
GROUP 3 ( '/u01/lun0/hanfa2/log3a.dbf', '/u01/lun0/hanfa2/log3b.dbf' ) SIZE 100 M ,
GROUP 4 ( '/u01/lun0/hanfa2/log4a.dbf', '/u01/lun0/hanfa2/log4b.dbf' ) SIZE 100 M ,
GROUP 5 ( '/u01/lun0/hanfa2/log5a.dbf', '/u01/lun0/hanfa2/log5b.dbf' ) SIZE 100 M REUSE
DATAFILE
'/u01/lun0/hanfa2/system01.dbf'
CHARACTER SET UTF8
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=650311810 filename=/u01/lun0/hanfa2/system02.dbf
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=650311810 filename=/u01/lun0/hanfa2/system03.dbf
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=650311810 filename=/u01/lun0/hanfa2/system04.dbf
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=650311810 filename=/u01/lun0/hanfa2/system05.dbf
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=650311810 filename=/u01/lun0/hanfa2/ctxd01.dbf
datafile 7 switched to datafile copy
input datafile copy recid=6 stamp=650311810 filename=/u01/lun0/hanfa2/owad01.dbf
datafile 8 switched to datafile copy
input datafile copy recid=7 stamp=650311810 filename=/u01/lun0/hanfa2/a_queue02.dbf
datafile 9 switched to datafile copy
input datafile copy recid=8 stamp=650311810 filename=/u01/lun0/hanfa2/odm.dbf
datafile 10 switched to datafile copy
input datafile copy recid=9 stamp=650311810 filename=/u01/lun0/hanfa2/olap.dbf
datafile 11 switched to datafile copy
input datafile copy recid=10 stamp=650311810 filename=/u01/lun0/hanfa2/xxcounter03.dbf
datafile 12 switched to datafile copy
input datafile copy recid=11 stamp=650311810 filename=/u01/lun0/hanfa2/xxcounter02.dbf
datafile 13 switched to datafile copy
input datafile copy recid=12 stamp=650311810 filename=/u01/lun0/hanfa2/xxcounter01.dbf
datafile 14 switched to datafile copy
input datafile copy recid=13 stamp=650311810 filename=/u01/lun0/hanfa2/sysaux01.dbf
datafile 15 switched to datafile copy
input datafile copy recid=14 stamp=650311810 filename=/u01/lun0/hanfa2/system12.dbf
datafile 16 switched to datafile copy
input datafile copy recid=15 stamp=650311810 filename=/u01/lun0/hanfa2/undo06.dbf
datafile 17 switched to datafile copy
input datafile copy recid=16 stamp=650311810 filename=/u01/lun0/hanfa2/disco01.dbf
datafile 18 switched to datafile copy
input datafile copy recid=17 stamp=650311810 filename=/u01/lun0/hanfa2/disco02.dbf
datafile 19 switched to datafile copy
input datafile copy recid=18 stamp=650311810 filename=/u01/lun0/hanfa2/disco03.dbf
datafile 20 switched to datafile copy
input datafile copy recid=19 stamp=650311810 filename=/u01/lun0/hanfa2/a_conv01.dbf
datafile 21 switched to datafile copy
input datafile copy recid=20 stamp=650311810 filename=/u01/lun0/hanfa2/a_conv02.dbf
datafile 22 switched to datafile copy
input datafile copy recid=21 stamp=650311810 filename=/u01/lun0/hanfa2/a_conv03.dbf
datafile 23 switched to datafile copy
input datafile copy recid=22 stamp=650311810 filename=/u01/lun0/hanfa2/a_conv04.dbf
datafile 24 switched to datafile copy
input datafile copy recid=23 stamp=650311810 filename=/u01/lun0/hanfa2/a_int02.dbf
datafile 25 switched to datafile copy
input datafile copy recid=24 stamp=650311810 filename=/u01/lun0/hanfa2/tools.dbf
datafile 26 switched to datafile copy
input datafile copy recid=25 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_data04.dbf
datafile 27 switched to datafile copy
input datafile copy recid=26 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_ind06.dbf
datafile 28 switched to datafile copy
input datafile copy recid=27 stamp=650311810 filename=/u01/lun0/hanfa2/undo05.dbf
datafile 29 switched to datafile copy
input datafile copy recid=28 stamp=650311810 filename=/u01/lun0/hanfa2/undo04.dbf
datafile 30 switched to datafile copy
input datafile copy recid=29 stamp=650311810 filename=/u01/lun0/hanfa2/undo03.dbf
datafile 31 switched to datafile copy
input datafile copy recid=30 stamp=650311810 filename=/u01/lun0/hanfa2/undo02.dbf
datafile 32 switched to datafile copy
input datafile copy recid=31 stamp=650311810 filename=/u01/lun0/hanfa2/undo01.dbf
datafile 33 switched to datafile copy
input datafile copy recid=32 stamp=650311810 filename=/u01/lun0/hanfa2/a_ts_mview03.dbf
datafile 34 switched to datafile copy
input datafile copy recid=33 stamp=650311810 filename=/u01/lun0/hanfa2/a_ts_mview02.dbf
datafile 35 switched to datafile copy
input datafile copy recid=34 stamp=650311810 filename=/u01/lun0/hanfa2/a_ts_mview01.dbf
datafile 36 switched to datafile copy
input datafile copy recid=35 stamp=650311810 filename=/u01/lun0/hanfa2/foglight_ts.dbf
datafile 37 switched to datafile copy
input datafile copy recid=36 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_data05.dbf
datafile 38 switched to datafile copy
input datafile copy recid=37 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_data06.dbf
datafile 39 switched to datafile copy
input datafile copy recid=38 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_data07.dbf
datafile 40 switched to datafile copy
input datafile copy recid=39 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_ind07.dbf
datafile 41 switched to datafile copy
input datafile copy recid=40 stamp=650311810 filename=/u01/lun0/hanfa2/a_txn_ind08.dbf
datafile 42 switched to datafile copy
input datafile copy recid=41 stamp=650311810 filename=/u01/lun0/hanfa2/dwh01.dbf
datafile 43 switched to datafile copy
input datafile copy recid=42 stamp=650311810 filename=/u01/lun0/hanfa2/dwh02.dbf
datafile 288 switched to datafile copy
input datafile copy recid=43 stamp=650311810 filename=/u01/lun0/hanfa2/system10.dbf
datafile 295 switched to datafile copy
input datafile copy recid=44 stamp=650311810 filename=/u01/lun0/hanfa2/system06.dbf
datafile 314 switched to datafile copy
input datafile copy recid=45 stamp=650311810 filename=/u01/lun0/hanfa2/portal01.dbf
datafile 351 switched to datafile copy
input datafile copy recid=46 stamp=650311810 filename=/u01/lun0/hanfa2/system07.dbf
datafile 352 switched to datafile copy
input datafile copy recid=47 stamp=650311811 filename=/u01/lun0/hanfa2/system09.dbf
datafile 353 switched to datafile copy
input datafile copy recid=48 stamp=650311811 filename=/u01/lun0/hanfa2/system08.dbf
datafile 354 switched to datafile copy
input datafile copy recid=49 stamp=650311811 filename=/u01/lun0/hanfa2/system11.dbf
datafile 392 switched to datafile copy
input datafile copy recid=50 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_data01.dbf
datafile 393 switched to datafile copy
input datafile copy recid=51 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_ind01.dbf
datafile 394 switched to datafile copy
input datafile copy recid=52 stamp=650311811 filename=/u01/lun0/hanfa2/a_ref01.dbf
datafile 395 switched to datafile copy
input datafile copy recid=53 stamp=650311811 filename=/u01/lun0/hanfa2/a_int01.dbf
datafile 396 switched to datafile copy
input datafile copy recid=54 stamp=650311811 filename=/u01/lun0/hanfa2/a_summ01.dbf
datafile 397 switched to datafile copy
input datafile copy recid=55 stamp=650311811 filename=/u01/lun0/hanfa2/a_nolog01.dbf
datafile 398 switched to datafile copy
input datafile copy recid=56 stamp=650311811 filename=/u01/lun0/hanfa2/a_archive01.dbf
datafile 399 switched to datafile copy
input datafile copy recid=57 stamp=650311811 filename=/u01/lun0/hanfa2/a_queue01.dbf
datafile 400 switched to datafile copy
input datafile copy recid=58 stamp=650311811 filename=/u01/lun0/hanfa2/a_media01.dbf
datafile 401 switched to datafile copy
input datafile copy recid=59 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_data02.dbf
datafile 402 switched to datafile copy
input datafile copy recid=60 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_data03.dbf
datafile 403 switched to datafile copy
input datafile copy recid=61 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_ind02.dbf
datafile 404 switched to datafile copy
input datafile copy recid=62 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_ind03.dbf
datafile 405 switched to datafile copy
input datafile copy recid=63 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_ind04.dbf
datafile 406 switched to datafile copy
input datafile copy recid=64 stamp=650311811 filename=/u01/lun0/hanfa2/a_txn_ind05.dbf
datafile 407 switched to datafile copy
input datafile copy recid=65 stamp=650311811 filename=/u01/lun0/hanfa2/a_ref02.dbf
contents of Memory Script:
set until time "to_date( '25.03.2008 08:00:00','dd.mm.yyyy hh24:mi:ss')";
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 25-MAR-08
starting media recovery
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=86375
channel aux1: restoring archive log
archive log thread=1 sequence=86376
channel aux1: restoring archive log
archive log thread=1 sequence=86377
channel aux1: restoring archive log
archive log thread=1 sequence=86378
channel aux1: restoring archive log
archive log thread=1 sequence=86379
channel aux1: restoring archive log
archive log thread=1 sequence=86380
channel aux1: restoring archive log
archive log thread=1 sequence=86381
channel aux1: restoring archive log
archive log thread=1 sequence=86382
channel aux1: restoring archive log
archive log thread=1 sequence=86383
channel aux1: restoring archive log
archive log thread=1 sequence=86384
channel aux1: restoring archive log
archive log thread=1 sequence=86385
channel aux1: restoring archive log
archive log thread=1 sequence=86386
channel aux1: restoring archive log
archive log thread=1 sequence=86387
channel aux1: restoring archive log
archive log thread=1 sequence=86388
channel aux1: restoring archive log
archive log thread=1 sequence=86389
channel aux1: restoring archive log
archive log thread=1 sequence=86390
channel aux1: restoring archive log
archive log thread=1 sequence=86391
channel aux1: restoring archive log
archive log thread=1 sequence=86392
channel aux1: restoring archive log
archive log thread=1 sequence=86393
channel aux1: restoring archive log
archive log thread=1 sequence=86394
channel aux1: restoring archive log
archive log thread=1 sequence=86395
channel aux1: restoring archive log
archive log thread=1 sequence=86396
channel aux1: restoring archive log
archive log thread=1 sequence=86397
channel aux1: restoring archive log
archive log thread=1 sequence=86398
channel aux1: reading from backup piece /arch1_PROD_tdjc4jd7/
channel aux1: restored backup piece 1
piece handle=/arch1_PROD_tdjc4jd7/ tag=TAG20080325T060110
channel aux1: restore complete, elapsed time: 00:07:36
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=86356
channel aux1: restoring archive log
archive log thread=1 sequence=86357
channel aux1: restoring archive log
archive log thread=1 sequence=86358
channel aux1: restoring archive log
archive log thread=1 sequence=86359
channel aux1: restoring archive log
archive log thread=1 sequence=86360
channel aux1: restoring archive log
archive log thread=1 sequence=86361
channel aux1: restoring archive log
archive log thread=1 sequence=86362
channel aux1: restoring archive log
archive log thread=1 sequence=86363
channel aux1: restoring archive log
archive log thread=1 sequence=86364
channel aux1: restoring archive log
archive log thread=1 sequence=86365
channel aux1: restoring archive log
archive log thread=1 sequence=86366
channel aux1: restoring archive log
archive log thread=1 sequence=86367
channel aux1: restoring archive log
archive log thread=1 sequence=86368
channel aux1: restoring archive log
archive log thread=1 sequence=86369
channel aux1: restoring archive log
archive log thread=1 sequence=86370
channel aux1: restoring archive log
archive log thread=1 sequence=86371
channel aux1: restoring archive log
archive log thread=1 sequence=86372
channel aux1: restoring archive log
archive log thread=1 sequence=86373
channel aux1: restoring archive log
archive log thread=1 sequence=86374
channel aux1: reading from backup piece /arch1_PROD_tcjc4jd7/
ORA-19870: error reading backup piece /arch1_PROD_tcjc4jd7/
ORA-19510: failed to set size of 182123 blocks for file "/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86358.log" (blocksize=512)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=86399
channel aux1: restoring archive log
archive log thread=1 sequence=86400
channel aux1: restoring archive log
archive log thread=1 sequence=86401
channel aux1: restoring archive log
archive log thread=1 sequence=86402
channel aux1: restoring archive log
archive log thread=1 sequence=86403
channel aux1: restoring archive log
archive log thread=1 sequence=86404
channel aux1: reading from backup piece /arch1_PROD_tgjc4qf4/
channel aux2: starting archive log restore to default destination
channel aux2: restoring archive log
archive log thread=1 sequence=86356
channel aux2: restoring archive log
archive log thread=1 sequence=86357
channel aux2: restoring archive log
archive log thread=1 sequence=86358
channel aux2: restoring archive log
archive log thread=1 sequence=86359
channel aux2: restoring archive log
archive log thread=1 sequence=86360
channel aux2: restoring archive log
archive log thread=1 sequence=86361
channel aux2: restoring archive log
archive log thread=1 sequence=86363
channel aux2: restoring archive log
archive log thread=1 sequence=86364
channel aux2: restoring archive log
archive log thread=1 sequence=86365
channel aux2: restoring archive log
archive log thread=1 sequence=86366
channel aux2: restoring archive log
archive log thread=1 sequence=86367
channel aux2: restoring archive log
archive log thread=1 sequence=86368
channel aux2: restoring archive log
archive log thread=1 sequence=86369
channel aux2: restoring archive log
archive log thread=1 sequence=86370
channel aux2: restoring archive log
archive log thread=1 sequence=86371
channel aux2: restoring archive log
archive log thread=1 sequence=86372
channel aux2: restoring archive log
archive log thread=1 sequence=86373
channel aux2: restoring archive log
archive log thread=1 sequence=86374
channel aux2: reading from backup piece /arch1_PROD_t9jc4iki/
channel aux1: restored backup piece 1
piece handle=/arch1_PROD_tgjc4qf4/ tag=TAG20080325T080139
channel aux1: restore complete, elapsed time: 00:01:56
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=86405
channel aux1: restoring archive log
archive log thread=1 sequence=86406
channel aux1: restoring archive log
archive log thread=1 sequence=86407
channel aux1: restoring archive log
archive log thread=1 sequence=86408
channel aux1: reading from backup piece /arch1_PROD_tfjc4qf4/
channel aux1: restored backup piece 1
piece handle=/arch1_PROD_tfjc4qf4/ tag=TAG20080325T080139
channel aux1: restore complete, elapsed time: 00:02:05
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=86409
channel aux1: reading from backup piece /arch1_PROD_tkjc51fm/
channel aux1: restored backup piece 1
piece handle=/arch1_PROD_tkjc51fm/ tag=TAG20080325T100124
channel aux1: restore complete, elapsed time: 00:02:15
channel aux2: restored backup piece 1
piece handle=/arch1_PROD_t9jc4iki/ tag=TAG20080325T054759
channel aux2: restore complete, elapsed time: 00:12:10
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86356.log thread=1 sequence=86356
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86356.log recid=44 stamp=650313112
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86357.log thread=1 sequence=86357
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86357.log recid=45 stamp=650313112
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86358.log thread=1 sequence=86358
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86358.log recid=37 stamp=650313085
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86359.log thread=1 sequence=86359
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86359.log recid=38 stamp=650313085
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86360.log thread=1 sequence=86360
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86360.log recid=52 stamp=650313135
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86361.log thread=1 sequence=86361
channel clone_default: deleting archive log(s)
archive log filename=/u01/lun0/hanfa2/arch/prodarch_23b63f7_1_625608313_86361.log recid=40 stamp=650313085
unable to find archive log
archive log thread=1 sequence=86362
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/lun0/hanfa2/system01.dbf'
released channel: t1
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/25/2008 18:32:26
RMAN-03015: error occurred in stored script Memory Script
RMAN-06055: could not find log sequence 86362 thread 1
Recovery Manager complete.Yes :-).
Also when i run recover database using backup controlfile;and try to apply redo logs i am getting:ORA-00309: log belongs to wrong database Do you have any advice on this ? -
Hi all.
This is the scenario:
I have a 2 node cluster Microsoft Windows 2012 R2 x86_64, the nodes are part of domain.
Installed Oracle 12cR1 (12.1.0.2.0) as follows:
Installation done using domain administrator named "installoracle" that has been EXPLICIT promoted to local administrator in both nodes.
One domain user named "oracle12c" with no administrator privileges neither in the domain or nodes.
Installation, after a lot of customization in the OS of the nodes, has gone ok, perfect indeed, not even a warning during runinstaller execution.
All services and resources are up & running, I have rebooted nodes and all comes back ok in place. In windows services I can see some services started with "oracle12c" user, and all windows groups: DBA, SYSKM, etc, has been created.
Now I have to install Oracle RAC database in 11gR2 version (11.2.0.4.0) to accomplish with application requirements.
So, I execute runInstaller (setup.exe) logged as administrator via domain administrator "installoracle" (the one that was able to do the smooth 12c GI installation) and the gui comes with out problems, but at 4th screen the one in which you have to choose what kind of installation you want to do (Single, RAC or RoN) I select RAC option, the gui returns error: crs is not running in the local node...
Finally, in order to deliver some database 11.2.0.4.0 for my customer, I try to do installation of SW for Single Node, I did using "installoracle". The sw has been installed in one of the nodes. Then I have created a database and I have stored datafiles in ASM (this ASM is part of 12c clusterware) and also register the 11gR2 single instance database in the Grid Infrastructure listener
So, whats next??? Why is this behavior??? I did similar installations in Linux/Solaris with no issue (well as everyone can imagine, always there are some issues, but when solved you got GI in 12c and databases in the release that you want 12c, 11g, 10g...)
Any clue?
Thanks in advance!!
Best Regards!!To go back to old version (without changing compatible parameter), you can perform downgrade.
Instructions are available at
How to Downgrade from Database 11.2 to Previous Release (Includes 11.2.0.4 - 11.2.0.1) (Doc ID 883335.1)
In this case you will having all the data file including the new one.
But remember database may not be in the same status as before (Before upgrade). it may have invalid objects of higher version after downgrade.
Downgrade is applicable only to successfully upgraded databases. In case upgrade faced some issue, do not try downgrade there.
Your second approach it not correct. Note that each datafile header will have db version. We can not open database in normal mode when header version and binary versions are different. -
Data Guard configuration for RAC database disappeared from Grid control
Primary Database Environment - Three node cluster
RAC Database 10.2.0.1.0
Linux Red Hat 4.0 2.6.9-22 64bit
ASM 10.2.0.1.0
Management Agent 10.2.0.2.0
Standby Database Environment - one Node database
Oracle Enterprise Edition 10.2.0.1.0 Single standby
Linux Red Hat 4.0 2.6.9-22 64bit
ASM 10.2.0.1.0
Management Agent 10.2.0.2.0
Grid Control 10.2.0.1.0 - Node separate from standby and cluster environments
Oracle 10.1.0.1.0
Grid Control 10.2.0.1.0
Red Hat 4.0 2.6.9-22 32bit
After adding a logical standby database through Grid Control for a RAC database, I noticed sometime later the Data Guard configuration disappeared from Grid Control. Not sure why but it is gone. I did notice that something went wrong with the standby creation but i did not get much feedback from Grid Control. The last thing I did was to view the configuration, see output below.
Initializing
Connected to instance qdcls0427:ELCDV3
Starting alert log monitor...
Updating Data Guard link on database homepage...
Data Protection Settings:
Protection mode : Maximum Performance
Log Transport Mode settings:
ELCDV.qdx.com: ARCH
ELXDV: ARCH
Checking standby redo log files.....OK
Checking Data Guard status
ELCDV.qdx.com : ORA-16809: multiple warnings detected for the database
ELXDV : Creation status unknown
Checking Inconsistent Properties
Checking agent status
ELCDV.qdx.com
qdcls0387.qdx.com ... OK
qdcls0388.qdx.com ... OK
qdcls0427.qdx.com ... OK
ELXDV ... WARNING: No credentials available for target ELXDV
Attempting agent ping ... OK
Switching log file 672.Done
WARNING: Skipping check for applied log on ELXDV : disabled
Processing completed.
Here are the steps followed to add the standby database in Grid Control
Maintenance tab
Setup and Manage Data Guard
Logged in as sys
Add standby database
Create a new logical standby database
Perform a live backup of the primary database
Specify backup directory for staging area
Specify standby database name and Oracle home location
Specify file location staging area on standby node
At the end am presented with a review of the selected options and then the standby database is created
Has any body come across a similar issue?
Thanks,Any resolution on this?
I just created a Logical Standby database and I'm getting the same warning (WARNING: No credentials available for target ...) when I do a 'Verify Configuration' from the Data Guard page.
Everything else seems to be working fine. Logs are being applied, etc.
I can't figure out what credentials its looking for.
Maybe you are looking for
-
How to show dependency Arrrow in Project Gantt chart ?
Hi, I have a requirement in which I need to show a Gantt chart showing Project and corresponding task of it. If Say Task2 is dependent on Task1 then I need to show an arrrow between these two tasks showing the dependency direction. But in my prototyp
-
Problem changing imported video from "music" to "tv show" category
i imported some tv shows that i already had on my computer (i didn't get the from the itunes music store) and, by default, the video shows up under the "movies" category in my ipod. i have some other tv shows that i did buy from the itunes music stor
-
CANNOT OVERRIDE DOCUMENT ROUTING ID FOR SPECIFIC TRADING PARTNER FOR ROSETT
Cannot override Document Routing ID for specific trading partner for RosettaNet transactions. The Document Routing ID for other transactions types (e.g EDI) can be overridden when creating operation capability for a trading partner by unchecking "Use
-
If you have a connection to on a non-blocking socket channel will the socket, is it possible that it will stop streaming all the data available into the buffer? If so how can you check that this has happened? If you buffer being used by the socket is
-
Illustrator cs6 gradient mesh issue
Trying to work with gradient mesh colouring the nodes and every few nodes I colour the selection stops working and i cant select the mesh. Doesn't matter if which selection tool I use or even the gradient mesh tool its still the same issue. I can see