Archival Error, no source redo log file

Printable View

01-25-2005, 09:13 PM
jwu1023

Archival Error, no source redo log file

Dear all,

I just start to be an Oracle DBA. When I checked the alert log file this morning, I found the following error message in the alert log file. Could you please give me some clue to solve the issue? I do appreciate.

My understanding is: in my primary database, no redo log file /u05/arch/1_3907.dbf exists, so there is no way for standby database to archive the log file. Am I right? What should I do?

**********************************************************************

Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc0_17043.trc:
ORA-16055: FAL request rejected
ARC0: Begin FAL archive (thread 1 sequence 3904 destination tr_db_standby)
Tue Jan 25 16:51:22 2005
ARC1: Begin FAL archive (thread 1 sequence 3905 destination tr_db_standby)
Tue Jan 25 16:51:22 2005
ARC0: FAL archive, source redo log file not found: /u05/arch/1_3904.dbf
Tue Jan 25 16:51:22 2005
ARC1: FAL archive, source redo log file not found: /u05/arch/1_3905.dbf
Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc0_17043.trc:
ORA-19505: failed to identify file "/u05/arch/1_3904.dbf"
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc1_17045.trc:
ORA-19505: failed to identify file "/u05/arch/1_3905.dbf"
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Tue Jan 25 16:51:22 2005
ARC0: FAL archive failed, see trace file.
Tue Jan 25 16:51:22 2005
ARC1: FAL archive failed, see trace file.
Tue Jan 25 16:51:22 2005
ARCH: FAL archive failed. Archiver continuing
Tue Jan 25 16:51:22 2005
ARCH: FAL archive failed. Archiver continuing
Tue Jan 25 16:51:22 2005
ORACLE Instance ladb - Archival Error. Archiver continuing.
Tue Jan 25 16:51:22 2005
ORACLE Instance ladb - Archival Error. Archiver continuing.
Tue Jan 25 16:51:22 2005
ARCH: Connecting to console port...
Tue Jan 25 16:51:22 2005
ARCH: Connecting to console port...
Tue Jan 25 16:51:22 2005
ORA-16055: FAL request rejected
Tue Jan 25 16:51:22 2005
ORA-16055: FAL request rejected
Tue Jan 25 16:51:22 2005
ARCH: Connecting to console port...
Tue Jan 25 16:51:22 2005
ARCH: Connecting to console port...
Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc0_17043.trc:
ORA-16055: FAL request rejected
Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc1_17045.trc:
ORA-16055: FAL request rejected
Tue Jan 25 16:51:22 2005
ARC0: Begin FAL archive (thread 1 sequence 3907 destination tr_db_standby)
ARC0: FAL archive, source redo log file not found: /u05/arch/1_3907.dbf
Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc0_17043.trc:
ORA-19505: failed to identify file "/u05/arch/1_3907.dbf"
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
ARC0: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
Tue Jan 25 16:51:22 2005
ORACLE Instance ladb - Archival Error. Archiver continuing.
ARCH: Connecting to console port...
Tue Jan 25 16:51:22 2005
ORA-16055: FAL request rejected
ARCH: Connecting to console port...

**************************************************************

thanks a lot,

Jian
01-25-2005, 09:48 PM
stmontgo

Re: Archival Error, no source redo log file

Quote:

Originally posted by jwu1023
Dear all,

I just start to be an Oracle DBA. When I checked the alert log file this morning, I found the following error message in the alert log file. Could you please give me some clue to solve the issue? I do appreciate.

My understanding is: in my primary database, no redo log file /u05/arch/1_3907.dbf exists, so there is no way for standby database to archive the log file. Am I right? What should I do?

**********************************************************************

Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc0_17043.trc:
ORA-16055: FAL request rejected
ARC0: Begin FAL archive (thread 1 sequence 3904 destination tr_db_standby)
Tue Jan 25 16:51:22 2005
ARC1: Begin FAL archive (thread 1 sequence 3905 destination tr_db_standby)
Tue Jan 25 16:51:22 2005
ARC0: FAL archive, source redo log file not found: /u05/arch/1_3904.dbf
Tue Jan 25 16:51:22 2005
ARC1: FAL archive, source redo log file not found: /u05/arch/1_3905.dbf
Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc0_17043.trc:
ORA-19505: failed to identify file "/u05/arch/1_3904.dbf"
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc1_17045.trc:
ORA-19505: failed to identify file "/u05/arch/1_3905.dbf"
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Tue Jan 25 16:51:22 2005
ARC0: FAL archive failed, see trace file.
Tue Jan 25 16:51:22 2005
ARC1: FAL archive failed, see trace file.
Tue Jan 25 16:51:22 2005
ARCH: FAL archive failed. Archiver continuing
Tue Jan 25 16:51:22 2005
ARCH: FAL archive failed. Archiver continuing
Tue Jan 25 16:51:22 2005
ORACLE Instance ladb - Archival Error. Archiver continuing.
Tue Jan 25 16:51:22 2005
ORACLE Instance ladb - Archival Error. Archiver continuing.
Tue Jan 25 16:51:22 2005
ARCH: Connecting to console port...
Tue Jan 25 16:51:22 2005
ARCH: Connecting to console port...
Tue Jan 25 16:51:22 2005
ORA-16055: FAL request rejected
Tue Jan 25 16:51:22 2005
ORA-16055: FAL request rejected
Tue Jan 25 16:51:22 2005
ARCH: Connecting to console port...
Tue Jan 25 16:51:22 2005
ARCH: Connecting to console port...
Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc0_17043.trc:
ORA-16055: FAL request rejected
Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc1_17045.trc:
ORA-16055: FAL request rejected
Tue Jan 25 16:51:22 2005
ARC0: Begin FAL archive (thread 1 sequence 3907 destination tr_db_standby)
ARC0: FAL archive, source redo log file not found: /u05/arch/1_3907.dbf
Tue Jan 25 16:51:22 2005
Errors in file /u05/bdump/ladb_arc0_17043.trc:
ORA-19505: failed to identify file "/u05/arch/1_3907.dbf"
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
ARC0: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
Tue Jan 25 16:51:22 2005
ORACLE Instance ladb - Archival Error. Archiver continuing.
ARCH: Connecting to console port...
Tue Jan 25 16:51:22 2005
ORA-16055: FAL request rejected
ARCH: Connecting to console port...

**************************************************************

thanks a lot,

Jian

you have a standby database and the standby needs a log that likely you already removed where it thinks it should be /u05/arch/
01-26-2005, 01:11 PM
jwu1023

Thanks for your help, stmontgo.

Another new "DBA" like me deleted all the files in dicrectory /u05/arch on the standby. So does that mean I have to create a log file with the same name? If so, could you tell me the steps of creating a log file? I do appreciate your help.

Jian
01-26-2005, 02:24 PM
stmontgo

Quote:

Originally posted by jwu1023
Thanks for your help, stmontgo.

Another new "DBA" like me deleted all the files in dicrectory /u05/arch on the standby. So does that mean I have to create a log file with the same name? If so, could you tell me the steps of creating a log file? I do appreciate your help.

Jian

Well the thing is there was a gap detected in the sequence of archive logs to applied at the standby - namely among others /u05/arch/1_3904.dbf. The standby is not being kept current and will not be until you can retrieve the missing logs. If you cannot retrieve the missing logs you need to recerate the standby with a new backup from production.
01-26-2005, 04:07 PM
jwu1023

Hi stmontgo,

May be this is stupid question, can I retrieve the miss log from the back up tape? If so, how could I reach the tape drive in Linux?

And if I couldn't find the miss log, is there any drawback to create a new standby?

Thanks for your patience and time.

Jian
01-26-2005, 04:22 PM
davey23uk

ask you SA as they probably control your backup software

no downside to recreating the standby, apart from the hassle of doing it if you have no experience
01-26-2005, 05:34 PM
DaPi

Quote:

Originally posted by davey23uk
no downside to recreating the standby, apart from the hassle of doing it if you have no experience

You are going to need to have this "under your belt" anyway, since recreation is needed if ever you restore & partially recover the primary or when you test the activation of the standby. Whoever first created the standby should have left instruction on how to do it.
01-26-2005, 05:47 PM
jwu1023

Hi DaPi and davey23uk,

Thank you all so much for the helpful input. I will ask our SA for instruction. You all have a nice afternoon:)

Jian
01-27-2005, 01:03 PM
jwu1023

Dear all,

Another junior DBA suggested me to solve the issue in this way:

1. shut down the primary database and clean all the logs.

2. shut down the standby database and clean all the logs.

3. start and mount the primary database and standby database.

Could anybody tell me whether it is a good way? Is there any risk? After the above steps, should we create the log on both databases and how could we create the log file matched on both database? Thank you for your help in advance.

Jian
01-27-2005, 02:00 PM
davey23uk

no, your standby needs to be be in sync with the primary with missing lpgs it cannot do that.

Do this.

Shutdown primary and standby

remove current standby

backup and restore primary onto standby machine

open up standy in standby mode.

Can't invent logs which it needs
01-27-2005, 02:17 PM
jwu1023

Thank you so much, davey23uk.

Since I never do this before, could you please tell me how to:

1. remove current standby

2. backup and restore primary onto standby machine

3. open up standy in standby mode.

Sorry for bothering you so much. I appreciate your help.

Jian
01-27-2005, 08:55 PM
stmontgo

Quote:

Originally posted by jwu1023
Thank you so much, davey23uk.

Since I never do this before, could you please tell me how to:

1. remove current standby

2. backup and restore primary onto standby machine

3. open up standy in standby mode.

Sorry for bothering you so much. I appreciate your help.

Jian

it's all here you really need to read through this and know it upside down. It's best to this an then ask specific questions on what you have researched or tried