OraFAQ Forum: Data Guard » ORA-00257 archiver error. Connect internal only until freed

Home » Server Options » Data Guard » ORA-00257 archiver error. Connect internal only until freed (Oracle EE database 9.0.1.4, Solaris 8)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

ORA-00257 archiver error. Connect internal only until freed [message #674834]

Mon, 18 February 2019 22:35

reym21
Messages: 241
Registered: February 2010
Location: Philippines

Senior Member

Our Standby database encountered an ORA-01666 error after startup yesterday.
What my colleague executed on that morning was to "SELECT SWITCHOVER_STATUS FROM V$DATABASE"
on both Production & Standby databases.

After this the "archiver error" appeared, both database and application is now inaccessible.

Please assist us on what to do.

Thank you in advance.

Attachment: excerpts_alert.txt
(Size: 1.64KB, Downloaded 5024 times)

Report message to a moderator

Re: ORA-00257 archiver error. Connect internal only until freed [message #674835 is a reply to message #674834]

Tue, 19 February 2019 00:24

Michel Cadot
Messages: 68732
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

ORA-01666: control file is for a standby database
 *Cause:  Attempting to mount, recover, or open a standby database without
          the appropriate command option to designate a standby database.
 *Action: Use the standby option or appropriate commands, or mount with
          the primary control file.

Report message to a moderator

Re: ORA-00257 archiver error. Connect internal only until freed [message #674836 is a reply to message #674835]

Tue, 19 February 2019 00:26

Michel Cadot
Messages: 68732
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

ORA-00257: archiver error. Connect internal only, until freed.
 *Cause:  The archiver process received an error while trying to archive
         a redo log.  If the problem is not resolved soon, the database
         will stop executing transactions. The most likely cause of this
         message is the destination device is out of space to store the
         redo log file.
 *Action:  Check archiver trace file for a detailed description
          of the problem. Also verify that the
         device specified in the initialization parameter
         ARCHIVE_LOG_DEST is set up properly for archiving.

Report message to a moderator

Re: ORA-00257 archiver error. Connect internal only until freed [message #674837 is a reply to message #674834]

Tue, 19 February 2019 01:48

John Watson
Messages: 8964
Registered: January 2010
Location: Global Village

Senior Member

To avoid the ora-01666 you need to run
STARTUP NOMOUNT;
ALTER DATABASE MOUNT STANDBY DATABASE;

The ora-00257 is because you have not removed old archive logfiles. Do it with RMAN.

Data Guard did work in 9i release 1, but you have to do a lot of the management yourself. The automation was not complete.

Report message to a moderator

Re: ORA-00257 archiver error. Connect internal only until freed [message #674842 is a reply to message #674836]

Tue, 19 February 2019 04:38

reym21
Messages: 241
Registered: February 2010
Location: Philippines

Senior Member

Sir,

We have re-set the archive destination folder,
then refreshed the archiver process.
dB and Apps are now accessible.

Thanks for your prompt assistance.

Best regards,

Report message to a moderator

Re: ORA-00257 archiver error. Connect internal only until freed [message #674843 is a reply to message #674837]

Tue, 19 February 2019 04:40

reym21
Messages: 241
Registered: February 2010
Location: Philippines

Senior Member

Yes Sir, we did that also prior to stop and restarting the archive process.

Thank you.

Report message to a moderator

Re: ORA-00257 archiver error. Connect internal only until freed [message #674844 is a reply to message #674836]

Tue, 19 February 2019 04:40

reym21
Messages: 241
Registered: February 2010
Location: Philippines

Senior Member

Sir Michel,

We have re-set the archive destination folder,
then refreshed the archiver process.
dB and Apps are now accessible.

Thanks for your prompt assistance.

Best regards,

[Updated on: Tue, 19 February 2019 04:40]

Report message to a moderator

Previous Topic:	Error 12154 received logging on to the standby (split from hijacked topic)
Next Topic:	ORA-00603: ORACLE server session terminated by fatal error

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Feb 02 11:51:30 CST 2025