| Database cloning issue [message #637828] |
Tue, 26 May 2015 22:20  |
 |
hassan12
Messages: 5
Registered: May 2015
|
Junior Member |
|
|
Good morning Experts,
I clone one of the database using Duplicate command, every this works fine but at the end when I try to open the database I got error message
Any thought ?
please reply...
************************************************************************************
SQL> alter database open RESETLOGS;
alter database open RESETLOGS
*
ERROR at line 1:
ORA-00392: log 3 of thread 1 is being cleared, operation not allowed
ORA-00312: online log 3 thread 1:
'/u01/app/oracle/oradata/.'clonedb'/redo03.log'
************************************************************************************
login as: oracle
oracle@192.168.1.21's password:
Last login: Mon May 25 22:32:27 2015 from 192.168.1.20
[oracle@machine6 ~]$
[oracle@machine6 ~]$
[oracle@machine6 ~]$
[oracle@machine6 ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Wed May 27 13:55:17 2015
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
[oracle@machine6 ~]$ export ORACLE_SID=clonedb
[oracle@machine6 ~]$
[oracle@machine6 ~]$ oraenv
ORACLE_SID = [clonedb] ? clonedb
The Oracle base remains unchanged with value /u01/app/oracle
[oracle@machine6 ~]$
[oracle@machine6 ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Wed May 27 13:57:48 2015
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open RESETLOGS;
alter database open RESETLOGS
*
ERROR at line 1:
ORA-00392: log 3 of thread 1 is being cleared, operation not allowed
ORA-00312: online log 3 thread 1:
'/u01/app/oracle/oradata/.'clonedb'/redo03.log'
SQL> set linesize 2000
SQL>
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES BLOCKSIZE MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME
---------- ---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- --------- ------------ ---------
1 1 0 104857600 512 1 YES UNUSED 0 0
3 1 0 52428800 512 1 YES CLEARING_CURRENT 0 0
2 1 0 104857600 512 1 YES UNUSED 0 0
|
|
|
|
|
|
| Re: Database cloning issue [message #637833 is a reply to message #637832] |
Tue, 26 May 2015 23:24  |
|
hassan12
Messages: 5
Registered: May 2015
|
Junior Member |
|
|
please review the trace file that was generated during duplicate process..
****************************************************************************************
Trace file /u01/app/oracle/diag/rdbms/clonedb/clonedb/trace/clonedb_ora_3823.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1
System name: Linux
Node name: machine6
Release: 3.8.13-44.1.1.el6uek.x86_64
Version: #2 SMP Wed Sep 10 06:10:25 PDT 2014
Machine: x86_64
Instance name: clonedb
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 3823, image: oracle@machine6 (TNS V1-V3)
*** 2015-05-25 20:29:31.321
*** SESSION ID:(1.5) 2015-05-25 20:29:31.321
*** CLIENT ID:() 2015-05-25 20:29:31.321
*** SERVICE NAME:() 2015-05-25 20:29:31.321
*** MODULE NAME:(sqlplus@machine6 (TNS V1-V3)) 2015-05-25 20:29:31.321
*** ACTION NAME:() 2015-05-25 20:29:31.321
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
*** 2015-05-25 20:30:30.419
Prior to RESETLOGS processing...
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE start
*** 2015-05-25 20:30:30.420 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/oradata/.'clonedb'/redo01.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
DDE rules only execution for: ORA 312
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, 5 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, 196018181 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
logfile 1 open failed:313
*** 2015-05-25 20:30:30.422 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/oradata/.'clonedb'/redo02.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
logfile 2 open failed:313
*** 2015-05-25 20:30:30.423 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/oradata/.'clonedb'/redo03.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
logfile 3 open failed:313
No logfiles qualified for archival
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
*** 2015-05-25 20:30:30.424 4320 krsh.c
Archive all online redo logfiles failed:392
*** 2015-05-25 20:37:58.006
Prior to RESETLOGS processing...
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE start
*** 2015-05-25 20:37:58.006 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/oradata/.'clonedb'/redo01.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
DDE rules only execution for: ORA 312
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, 5 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, 196018181 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
logfile 1 open failed:313
*** 2015-05-25 20:37:58.007 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/oradata/.'clonedb'/redo02.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
logfile 2 open failed:313
*** 2015-05-25 20:37:58.007 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/oradata/.'clonedb'/redo03.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
logfile 3 open failed:313
No logfiles qualified for archival
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
*** 2015-05-25 20:37:58.008 4320 krsh.c
Archive all online redo logfiles failed:392
DDE rules only execution for: ORA 312
*** 2015-05-25 20:59:08.452
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
*** 2015-05-25 20:59:44.561
Prior to RESETLOGS processing...
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE start
*** 2015-05-25 20:59:44.561 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_1_bp7k97kf_.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
Logfile 1 is not used
*** 2015-05-25 20:59:44.561 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_2_bp7kb63b_.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
Logfile 2 is not used
*** 2015-05-25 20:59:44.561 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/oradata/.'clonedb'/redo03.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, 47185925 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
logfile 3 open failed:313
No logfiles qualified for archival
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
*** 2015-05-25 20:59:44.562 4320 krsh.c
Archive all online redo logfiles failed:392
************************************************************************************************************************************* ******************
please review this trace file also
*******************************************************
Trace file /u01/app/oracle/diag/rdbms/clonedb/clonedb/trace/clonedb_ora_3850.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1
System name: Linux
Node name: machine6
Release: 3.8.13-44.1.1.el6uek.x86_64
Version: #2 SMP Wed Sep 10 06:10:25 PDT 2014
Machine: x86_64
Instance name: clonedb
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 3850, image: oracle@machine6 (TNS V1-V3)
*** 2015-05-27 13:53:26.693
*** SESSION ID:(1.5) 2015-05-27 13:53:26.693
*** CLIENT ID:() 2015-05-27 13:53:26.693
*** SERVICE NAME:() 2015-05-27 13:53:26.693
*** MODULE NAME:(sqlplus@machine6 (TNS V1-V3)) 2015-05-27 13:53:26.693
*** ACTION NAME:() 2015-05-27 13:53:26.693
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
*** 2015-05-27 13:53:56.128
Prior to RESETLOGS processing...
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE start
*** 2015-05-27 13:53:56.134 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_1_bp7k97kf_.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
DDE rules only execution for: ORA 312
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 4 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 4 csec) -----
logfile 1 header verification failed:367
*** 2015-05-27 13:53:56.296 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_2_bp7kb63b_.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 2 thread 1: '/u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_2_bp7kb63b_.log'
logfile 2 header verification failed:367
*** 2015-05-27 13:53:56.297 3903 krsq.c
Archiving online redo logfile /u01/app/oracle/oradata/.'clonedb'/redo03.log
******************************************************
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
******************************************************
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, 154468357 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
logfile 3 open failed:313
No logfiles qualified for archival
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE complete
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 1 thread 1: '/u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_1_bp7k97kf_.log'
*** 2015-05-27 13:53:56.392 4320 krsh.c
Clearing online redo logfile 1 /u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_1_bp7k97kf_.log
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 1 thread 1: '/u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_1_bp7k97kf_.log'
ORA-00367: checksum error in log file header
ORA-00305: log 1 of thread 1 inconsistent; belongs to another database
ORA-00312: online log 1 thread 1: '/u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_1_bp7k97kf_.log'
*** 2015-05-27 13:53:57.140
*** 2015-05-27 13:53:57.140 4320 krsh.c
Clearing online redo logfile 1 complete
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 2 thread 1: '/u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_2_bp7kb63b_.log'
*** 2015-05-27 13:53:57.140 4320 krsh.c
Clearing online redo logfile 2 /u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_2_bp7kb63b_.log
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 2 thread 1: '/u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_2_bp7kb63b_.log'
ORA-00367: checksum error in log file header
ORA-00305: log 2 of thread 1 inconsistent; belongs to another database
ORA-00312: online log 2 thread 1: '/u01/app/oracle/fast_recovery_area/CLONEDB/onlinelog/o1_mf_2_bp7kb63b_.log'
*** 2015-05-27 13:53:58.635
*** 2015-05-27 13:53:58.635 4320 krsh.c
Clearing online redo logfile 2 complete
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
*** 2015-05-27 13:53:58.637 4320 krsh.c
Clearing online redo logfile 3 /u01/app/oracle/oradata/.'clonedb'/redo03.log
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Error 344 creating/clearing online redo logfile 3
*** 2015-05-27 13:53:58.654 4320 krsh.c
Clearing online redo logfile 3 complete
*** 2015-05-27 13:53:58.654
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Database cloning issue [message #637875 is a reply to message #637857] |
Thu, 28 May 2015 03:07 |
gazzag
Messages: 1119
Registered: November 2010
Location: Bedwas, UK
|
Senior Member |
|
|
From your initial post:
[oracle@machine6 ~]$ oraenv
Apart from anything else, that isn't going to work anyway. oraenv must be run thus:
As Mahesh said, you must copy and paste exactly what you did for people to assist you.
|
|
|
|
|
|
| Re: Database cloning issue [message #637899 is a reply to message #637897] |
Thu, 28 May 2015 09:21 |
 |
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
|
Senior Member |
|
|
>ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/.'clonedb'/redo01.log'
>'/u01/app/oracle/oradata/.'clonedb'/redo03.log'
that certainly is an pathname
Problem Exists Between Keyboard And Chair
Oracle is the victim; not the culprit.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
