ORA-00322: log 4 of thread 1 is not current copy

Hi Team,
We are having 10g DB setup the db is in real time sync.
in alert logfile getting the below error
ORA-00322: log 4 of thread 1 is not current copy
ORA-00312: online log 4 thread 1: '/data02/oradata/***/redo/stdby_log07.dbf'
Even though i have enabled managed recover mode in v$ARCHIVE_DEST_STATUS it is showing as IDLE.
Please help to resolve the same..!
Thanks

Several options are available:
1. Apply the fix for the Bug 5238386.
2. Upgrade the database to the version 10.2.0.4 where the issue has been fixed.
3. Drop the log group and recreate it, or restore correct file or reset logs.

Similar Messages

ORA-00322: log 1 of thread 1 is not current copy

can you please help me.
Im using oracle express edition.
Regrds
upul Indika.
SQL> startup
ORACLE instance started.
Total System Global Area 146800640 bytes
Fixed Size 1286220 bytes
Variable Size 83890100 bytes
Database Buffers 58720256 bytes
Redo Buffers 2904064 bytes
Database mounted.
ORA-00322: log 1 of thread 1 is not current copy
ORA-00312: online log 1 thread 1:
'D:\PROGRAMEFILES\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_307BLHJ3_.
LOG'
SQL>
SQL>
Message was edited by:
Upul Indika

00322, 00000, "log %s of thread %s is not current copy"
// *Cause: Check of log file header at database open found that an online
// log appears to be an incorrectly restored backup.
// *Action: Restore correct file or reset logs.

ORA-00322: log 19 of thread 1 is not current copy

Hi,
On my standby database I am getting this error.
I am using Oracle 10g on linux server.
why this error occurs?
After this the media recovery is going on.
Thanks,
Kavitha

00322, 00000, "log %s of thread %s is not current copy"
// *Cause: Check of log file header at database open found that an online
// log appears to be an incorrectly restored backup.
// *Action: Restore correct file or reset logs.

ORA-00338: ORA-00338: log 2 of thread 1 is more recent than control file

Hi, I am getting error "ORA-00338: log 2 of thread 1 is more recent than control file"
My os is RHEL 5.5, 64-bit
Database version is 11.1.0.7
Help !

VinodNagpure wrote:
But we were not cloning this instance, and the instance which was being cloned is ok. The database as well as the application is open. The issue is with another database running on the same server.I suspect that the "working" DB has a file that over-wrote a file of the DB reporting the errors.
*NIX OS is not idiotproofed against somebody fumble fingering file name.

ORA-00314: log 1 of thread 1, expected sequence# 416 doesn't match 413

Hi,
SQL> startup
ORACLE instance started.
Total System Global Area 289406976 bytes
Fixed Size 1248576 bytes
Variable Size 117441216 bytes
Database Buffers 163577856 bytes
Redo Buffers 7139328 bytes
Database mounted.
ORA-00314: log 1 of thread 1, expected sequence# 416 doesn't match 413
ORA-00312: online log 1 thread 1:
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG'.
Help me how to solve it.
thankx

The Result of Your Suggested Commands is
SQL> select f.group#, f.member, l.status, l.bytes/1048576 sz
2 from v$logfile f, v$log l
3 where f.group#=l.group#
4 order by f.group#, f.member;
GROUP#
MEMBER
STATUS SZ
1
D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG
CURRENT 50
2
D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG
INACTIVE 50
GROUP#
MEMBER
STATUS SZ
3
D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
INACTIVE 50
SQL>

ORA-00338: log 2 of thread 1 is more recent than control file

We got this error in NSA (redo transport process) trace file last night. Everything looks fine now. Does anyone know what can be causing this error?
Thanks.

aDBA wrote:
We got this error in NSA (redo transport process) trace file last night. Everything looks fine now. Does anyone know what can be causing this error?
Thanks.always post your question with oracle version and operating system name and version.
refer:https://kr.forums.oracle.com/forums/thread.jspa?threadID=2173829

ORA-00322, ORA-00312

Hi,
please help me,
I have to restart my computer, but if I started the computer, I wanted to start database with startup command, but I got following errors:
ORA-00322: log 3 of thread 1 is not current copy
ORA-00312: online log 3 thread 1 :
'/u01/app/oracle/flash_recovery_area/ORCL/onlinelog/o1_mf_3_79fz3gx8_.log'
ORA-00322: log 3 of thread 1 is not current copy
ORA-00312: online log 3 thread 1 :
'/u01/app/oracle/oradata/ORCL/onlinelog/o1_mf_3_79fz3g1v_.log'
I read a lot of materials about this problem, but I can't resolve this. I'm not a expert in this, so please help me.
I use version of oracle: 10.2.0.1.0 and I dont' have any backup of my database.
I realy need to resolve this as soon as possible.
Please help
Thank you.

Please Follow these steps:
1) Network Configuration Assistant:
For Linux:
a) Go to bin folder using "oracle" user and type "./netca" in terminal
b) Reconfigure listner, naming method and SID
and click finish.
For window go to "bin" of oracle installation folder and execute "netca"
2) Type following when you go in "bin" folder using cmd or linux terminal:
1)conn / as sysdba
2)[Enter sys or system user password]
3)shutdown immediate;
4)startup mount;
5)Recover database using backup controlfile;
[Provide path where your redo log file locate. Try various redo log files in your case serach .log files in "/u01/app/oracle/oradata/ORCL/" folder or any futher nested folder e.g. type path like without quotes "/u01/app/oracle/oradata/ORCL/redo01.log After trying various log file you will stop when u see this message "
Log applied.
Media recovery complete." ]
6)alter database open resetlogs;
7)shutdown immediate;
8)startup
Hope it will help you.
Check following link as well:
http://mrrame.blogspot.com/2009/08/ora-00214-controlfile-inconsistent.html

ORA-16014: log 1 sequence# 40845 not archived, no available destinations

Hi,
My RMAN archive script gives the following error. I'm not sure why - there is still about 16 GB diskspace and an archivelog is not more than 50 MB. Does anyone know what could be the cause of this error? Thanks.
Recovery Manager: Release 8.1.7.4.1 - Production
RMAN-06005: connected to target database: PROD (DBID=1412471481)
RMAN-06009: using target database controlfile instead of recovery catalog
RMAN> sql 'alter system archive log current';
2> change archivelog all validate;
3> run{
4> allocate channel c1 type DISK;
5> allocate channel c2 type DISK;
6> backup filesperset 10
7> format 'C:\backup\rman\PROD\%d_ARCHIVES_%u_%s.bak'
8> archivelog all delete input;
9> release channel c1;
10> release channel c2;
11> }
12>
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter system archive log current
RMAN-03023: executing command: sql
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03006: non-retryable error occurred during execution of command: sql
RMAN-07004: unhandled exception during command execution on channel default
RMAN-20000: abnormal termination of job step
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current
RMAN-11001: Oracle Error: ORA-16014: log 1 sequence# 40845 not archived, no available destinations
ORA-00312: online log 1 thread 1: 'C:\ORACLE\ORADATA\PROD\REDO01.LOG'
Recovery Manager complete.

NAME TYPE VALUE
log_archive_dest string
log_archive_dest_1 string LOCATION=/ora MANDATORY R
EOPEN=300
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
NAME TYPE VALUE
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable

Thread: ORA-12514: TNS:listener does not currently know of service request

HI guys,
I had installed oracle 10g on an AIX platform
now when I try to connect to the database using the normal way sqlplus dma/***@DMAN
it gives me the error:
$ ./sqlplus dma/dma@DMAN
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Sep 29 09:27:39 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
I can connect to the database specifying before the oracle SID on unix
ORACLE_SID=DMAN
export ORACLE_SID
$ ./sqlplus dma/dma
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Sep 29 09:41:02 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Release 10.2.0.1.0 - 64bit Production
SQL>
I cant understand the problem
my listener.ora is:
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = dmora1)(PORT = 1521))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /orasoft/app/oracle/DMAN)
(PROGRAM = extproc)
(SID_DESC =
(GLOBAL_DBNAME = DMAN)
(ORACLE_HOME = /orasoft/app/oracle/DMAN)
(SID_NAME = DMAN)
and my listener status:
LSNRCTL for IBM/AIX RISC System/6000: Version 10.2.0.1.0 - Production on 29-SEP-2008 09:43:19
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Welcome to LSNRCTL, type "help" for information.
LSNRCTL> status LISTENER
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dmora1)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for IBM/AIX RISC System/6000: Version 10.2.0.1.0 - Production
Start Date 29-SEP-2008 08:29:32
Uptime 0 days 1 hr. 13 min. 53 sec
Trace Level off
Security ON: Local OS Authentication
SNMP ON
Listener Parameter File /orasoft/app/oracle/DMAN/network/admin/listener.ora
Listener Log File /orasoft/app/oracle/DMAN/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)))
Services Summary...
Service "DMAN" has 2 instance(s).
Instance "DMAN", status UNKNOWN, has 1 handler(s) for this service...
Instance "DMAN", status READY, has 1 handler(s) for this service...
Service "DMANXDB" has 1 instance(s).
Instance "DMAN", status READY, has 1 handler(s) for this service...
Service "DMAN_XPT" has 1 instance(s).
Instance "DMAN", status READY, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
has any one any idea about my problem, because I have the same listener.ora in the backup machine and it works fine
Thank YOU in advance

Please don't duplicate threads :
ORA-12514: TNS:listener does not currently know of service requested in con

RMAN-05501: RMAN-11003 ORA-00353: log corruption near block 2048 change

Hi Gurus,
I've posted few days ago an issue I got while recreating my Dataguard.
The Main issue was while duplicating target from active database I got this errors during the recovery process.
The Restore Process Went fine, RMAN Copied the Datafiles very well, but stop when at the moment to start the recovery process from the auxiliary db
Yesterday I took one last try,
I follow same procedure, the one described in all Oracle Docs, Google and so on ... it's not a secret I guess.
The I got the same issue, same errors.
I read soemthing about archivelogs, and the Block corruption and so on, I've tried so many things (register the log... etc etc ), and than I read something about "catalog the logfile)
and that's waht I did.
But I was just connect to the target db.
contents of Memory Script:
set until scn 1638816629;
recover
standby
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 14-MAY-13
starting media recovery
archived log for thread 1 with sequence 32196 is already on disk as file /archives/CMOVP/stby/1_32196_810397891.arc
archived log for thread 1 with sequence 32197 is already on disk as file /archives/CMOVP/stby/1_32197_810397891.arc
archived log for thread 1 with sequence 32198 is already on disk as file /archives/CMOVP/stby/1_32198_810397891.arc
archived log for thread 1 with sequence 32199 is already on disk as file /archives/CMOVP/stby/1_32199_810397891.arc
archived log for thread 1 with sequence 32200 is already on disk as file /archives/CMOVP/stby/1_32200_810397891.arc
archived log for thread 1 with sequence 32201 is already on disk as file /archives/CMOVP/stby/1_32201_810397891.arc
archived log for thread 1 with sequence 32202 is already on disk as file /archives/CMOVP/stby/1_32202_810397891.arc
archived log for thread 1 with sequence 32203 is already on disk as file /archives/CMOVP/stby/1_32203_810397891.arc
archived log for thread 1 with sequence 32204 is already on disk as file /archives/CMOVP/stby/1_32204_810397891.arc
archived log for thread 1 with sequence 32205 is already on disk as file /archives/CMOVP/stby/1_32205_810397891.arc
archived log for thread 1 with sequence 32206 is already on disk as file /archives/CMOVP/stby/1_32206_810397891.arc
archived log for thread 1 with sequence 32207 is already on disk as file /archives/CMOVP/stby/1_32207_810397891.arc
archived log for thread 1 with sequence 32208 is already on disk as file /archives/CMOVP/stby/1_32208_810397891.arc
archived log for thread 1 with sequence 32209 is already on disk as file /archives/CMOVP/stby/1_32209_810397891.arc
archived log for thread 1 with sequence 32210 is already on disk as file /archives/CMOVP/stby/1_32210_810397891.arc
archived log for thread 1 with sequence 32211 is already on disk as file /archives/CMOVP/stby/1_32211_810397891.arc
archived log for thread 1 with sequence 32212 is already on disk as file /archives/CMOVP/stby/1_32212_810397891.arc
archived log for thread 1 with sequence 32213 is already on disk as file /archives/CMOVP/stby/1_32213_810397891.arc
archived log for thread 1 with sequence 32214 is already on disk as file /archives/CMOVP/stby/1_32214_810397891.arc
archived log for thread 1 with sequence 32215 is already on disk as file /archives/CMOVP/stby/1_32215_810397891.arc
archived log for thread 1 with sequence 32216 is already on disk as file /archives/CMOVP/stby/1_32216_810397891.arc
archived log for thread 1 with sequence 32217 is already on disk as file /archives/CMOVP/stby/1_32217_810397891.arc
archived log for thread 1 with sequence 32218 is already on disk as file /archives/CMOVP/stby/1_32218_810397891.arc
archived log for thread 1 with sequence 32219 is already on disk as file /archives/CMOVP/stby/1_32219_810397891.arc
archived log for thread 1 with sequence 32220 is already on disk as file /archives/CMOVP/stby/1_32220_810397891.arc
archived log for thread 1 with sequence 32221 is already on disk as file /archives/CMOVP/stby/1_32221_810397891.arc
archived log for thread 1 with sequence 32222 is already on disk as file /archives/CMOVP/stby/1_32222_810397891.arc
archived log for thread 1 with sequence 32223 is already on disk as file /archives/CMOVP/stby/1_32223_810397891.arc
archived log file name=/archives/CMOVP/stby/1_32196_810397891.arc thread=1 sequence=32196
released channel: prm1
released channel: stby1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/14/2013 01:11:33
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/archives/CMOVP/stby/1_32196_810397891.arc'
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 2048 change 1638686297 time 05/13/2013 22:42:03
ORA-00334: archived log: '/archives/CMOVP/stby/1_32196_810397891.arc'
################# What I did: ################################
Rma target /
RMAN>catalog archivelog '/archives/CMOVP/stby/1_32196_810397891.arc';
The I connect to target and Auxiliary again :Rman target / catalog rman/rman@rman auxiliary
and I run the last content of the failing memory script:RMAN> run
set until scn 1638816629;
recover
standby
clone database
delete archivelog
And The DB start the recovery Process and my Standby complete the recovery very weel with message "Recovery Finnish or Termintaed or Completed"
The I could configure Datagurd
And I check the process and the Log Apply was on and running fine, no gaps, perfect!!!!!
How !!! Just Cataloging an "Supposed Corrupted"archive log !!!!!!
If Any ideas, that ould be great to understand this.
Rgds
Carlos

okKarol wrote:
Hi Gurus,
I've posted few days ago an issue I got while recreating my Dataguard.
The Main issue was while duplicating target from active database I got this errors during the recovery process.
The Restore Process Went fine, RMAN Copied the Datafiles very well, but stop when at the moment to start the recovery process from the auxiliary db
Yesterday I took one last try,
I follow same procedure, the one described in all Oracle Docs, Google and so on ... it's not a secret I guess.
The I got the same issue, same errors.
I read soemthing about archivelogs, and the Block corruption and so on, I've tried so many things (register the log... etc etc ), and than I read something about "catalog the logfile)
and that's waht I did.
But I was just connect to the target db.
contents of Memory Script:
set until scn 1638816629;
recover
standby
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 14-MAY-13
starting media recovery
archived log for thread 1 with sequence 32196 is already on disk as file /archives/CMOVP/stby/1_32196_810397891.arc
archived log for thread 1 with sequence 32197 is already on disk as file /archives/CMOVP/stby/1_32197_810397891.arc
archived log for thread 1 with sequence 32198 is already on disk as file /archives/CMOVP/stby/1_32198_810397891.arc
archived log for thread 1 with sequence 32199 is already on disk as file /archives/CMOVP/stby/1_32199_810397891.arc
archived log for thread 1 with sequence 32200 is already on disk as file /archives/CMOVP/stby/1_32200_810397891.arc
archived log for thread 1 with sequence 32201 is already on disk as file /archives/CMOVP/stby/1_32201_810397891.arc
archived log for thread 1 with sequence 32202 is already on disk as file /archives/CMOVP/stby/1_32202_810397891.arc
archived log for thread 1 with sequence 32203 is already on disk as file /archives/CMOVP/stby/1_32203_810397891.arc
archived log for thread 1 with sequence 32204 is already on disk as file /archives/CMOVP/stby/1_32204_810397891.arc
archived log for thread 1 with sequence 32205 is already on disk as file /archives/CMOVP/stby/1_32205_810397891.arc
archived log for thread 1 with sequence 32206 is already on disk as file /archives/CMOVP/stby/1_32206_810397891.arc
archived log for thread 1 with sequence 32207 is already on disk as file /archives/CMOVP/stby/1_32207_810397891.arc
archived log for thread 1 with sequence 32208 is already on disk as file /archives/CMOVP/stby/1_32208_810397891.arc
archived log for thread 1 with sequence 32209 is already on disk as file /archives/CMOVP/stby/1_32209_810397891.arc
archived log for thread 1 with sequence 32210 is already on disk as file /archives/CMOVP/stby/1_32210_810397891.arc
archived log for thread 1 with sequence 32211 is already on disk as file /archives/CMOVP/stby/1_32211_810397891.arc
archived log for thread 1 with sequence 32212 is already on disk as file /archives/CMOVP/stby/1_32212_810397891.arc
archived log for thread 1 with sequence 32213 is already on disk as file /archives/CMOVP/stby/1_32213_810397891.arc
archived log for thread 1 with sequence 32214 is already on disk as file /archives/CMOVP/stby/1_32214_810397891.arc
archived log for thread 1 with sequence 32215 is already on disk as file /archives/CMOVP/stby/1_32215_810397891.arc
archived log for thread 1 with sequence 32216 is already on disk as file /archives/CMOVP/stby/1_32216_810397891.arc
archived log for thread 1 with sequence 32217 is already on disk as file /archives/CMOVP/stby/1_32217_810397891.arc
archived log for thread 1 with sequence 32218 is already on disk as file /archives/CMOVP/stby/1_32218_810397891.arc
archived log for thread 1 with sequence 32219 is already on disk as file /archives/CMOVP/stby/1_32219_810397891.arc
archived log for thread 1 with sequence 32220 is already on disk as file /archives/CMOVP/stby/1_32220_810397891.arc
archived log for thread 1 with sequence 32221 is already on disk as file /archives/CMOVP/stby/1_32221_810397891.arc
archived log for thread 1 with sequence 32222 is already on disk as file /archives/CMOVP/stby/1_32222_810397891.arc
archived log for thread 1 with sequence 32223 is already on disk as file /archives/CMOVP/stby/1_32223_810397891.arc
archived log file name=/archives/CMOVP/stby/1_32196_810397891.arc thread=1 sequence=32196
released channel: prm1
released channel: stby1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/14/2013 01:11:33
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/archives/CMOVP/stby/1_32196_810397891.arc'
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 2048 change 1638686297 time 05/13/2013 22:42:03
ORA-00334: archived log: '/archives/CMOVP/stby/1_32196_810397891.arc'
################# What I did: ################################
Rma target /
RMAN>catalog archivelog '/archives/CMOVP/stby/1_32196_810397891.arc';
The I connect to target and Auxiliary again :Rman target / catalog rman/rman@rman auxiliary
and I run the last content of the failing memory script:RMAN> run
set until scn 1638816629;
recover
standby
clone database
delete archivelog
And The DB start the recovery Process and my Standby complete the recovery very weel with message "Recovery Finnish or Termintaed or Completed"
The I could configure Datagurd
And I check the process and the Log Apply was on and running fine, no gaps, perfect!!!!!
How !!! Just Cataloging an "Supposed Corrupted"archive log !!!!!!
If Any ideas, that ould be great to understand this.
Rgds
CarlosHi,
Can you change standby database archive destination from /archives/CMOVP/stby/ other disk?
I think this problem on your disk.
Mahir
p.s. I remember you before thread, too

ORA-16038: log 1 sequence# 1292 cannot be archived ORA-19809: limit exceede

I am getting this error when starting the database 10g
ORA-16038: log 1 sequence# 1292 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1:
'/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/onlinelog/o1_mf_1_45ngtrx0_.log'
Can someone help me, it is very urgent.
Zulqarnain

It is resolved when I tried
ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 15G SCOPE=BOTH

ORA-01618: redo thread 2 is not enabled - cannot mount

Hi Guru
I am using two node RAC instance , and drop redo log . after that i startup a node which was down then i found the following error
ORA-01618: redo thread 2 is not enabled - cannot mount
Pls advise me

Hi,
At a minimum you
- need to look up the error message in the online error messages manual, prior to posting
- you need to post your platform and your 4 digit database version
In a RAC instance each instance needs to have dedicated online redolog groups, called a thread.
You need to make sure (from v$log) your instances have separate redologs.
Secondly (the error message is already pointing to that), both instances need to have a thread enabled
--> alter database enable public thread <n>; -- usually 2
Hth
Sybrand Bakker
Senior Oracle DBA

ORA-16038: log 1 sequence# 607 cannot be archived Error..

hi I Have a Problem to Start my Database.
My Database is Not in Archive Mode..
to know the detail error message is Given..
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-16038: log 1 sequence# 607 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1:
'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\REDO01.LOG'
I cam not recover My Database..
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00264: no recovery required
I think recovery nolonger needed..
pls any one help me..

Hi
ORA-19809: limit exceeded for recovery filesYou have two options now. First is to set the db_recovery_file_dest_size to a bigger size (if you have disk space available ie) and second to use RMAN to delete the archivelogs.
Rgds
Adnan

Database is not opening due to ORA-16038: log 1 sequence# 16 cannot be arch

Dear All,
I am using oracle database 10g release2 on linux platform............
I am just moving logsegment type object from one tablespace to another tablespace.
But due to low space for redo log file my alter query was hanged on and not completed sucessfully. and the directory is showing full.
then i abort the query by shutdown database by using shutdown immediate command.
After that when i m trying to startup my databse in normal mode i am getting following error....
ERROR at line 1:
ORA-16038: log 1 sequence# 16 cannot be archived
ORA-19502: write error on file "", blockno (blocksize=)
ORA-00312: online log 1 thread 1:
'/var/oracle/oradata/clone/redofiles/REDO_RLOG_01a.dbf'
ORA-00312: online log 1 thread 1:
'/var/oracle/oradata/clone/redofiles/REDO_RLOG_03b.dbf'
so pls suggest me the solution to resolve this problem.

Check your Archive log location capacity , used & free.
If archive mount point/FRA is full , then either take backup archive with delete option into another mount point'
or
as part of emergency you can move those archives into different mount point.
Once there is enough free space, bring database back again. Post if any errors again

~ORA-16038: log 2 sequence# 140 cannot be archived~ORA-19809: limit exceede

~ORA-16038: log 2 sequence# 140 cannot be archived~ORA-19809: limit exceeded for recovery files~ORA-00312: online log 2 thread 1: '/u02/oradata/PROD/redo02.log'
but my /u02/oradata/PROD/ is empty, mod is set to 777
What possible happened?
Thanks.

09:37:29 SQL> startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
see my init.ora, last three line is added by me,
is it obsolete and/or deprecated parameter(s)?
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=838860800
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/u01/app/oracle/admin/PROD/udump'
LOG_ARCHIVE_START=TRUE
LOG_ARCHIVE_DEST=/u02/archive/PROD
LOG_ARCHIVE_FORMAT=arc%s.arc

ORA-00322: log 4 of thread 1 is not current copy

Similar Messages

Maybe you are looking for