ORA-16014,接着   …

Alertlog:

 

Starting background process SMCO
Tue Dec 24 22:17:20 2013
SMCO started with pid=45, OS id=3850
Tue Dec 24 22:17:28 2013
Starting background process CJQ0
Tue Dec 24 22:17:28 2013
CJQ0 started with pid=34, OS id=3866
Tue Dec 24 22:17:35 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance TEST3 - Archival Error
ORA-16014: log 2 sequence# 335 not archived, no available destinations
ORA-00312: online log 2 thread 1: '/pool08/test3/db/apps_st/data/log02b.dbf'
ORA-00312: online log 2 thread 1: '/pool08/test3/db/apps_st/data/log02a.dbf'
Errors in file /pool08/test3/db/tech_st/11.1.0/log/diag/rdbms/test3/TEST3/trace/TEST3_arc0_3817.trc:
ORA-16014: log 2 sequence# 335 not archived, no available destinations
ORA-00312: online log 2 thread 1: '/pool08/test3/db/apps_st/data/log02b.dbf'
ORA-00312: online log 2 thread 1: '/pool08/test3/db/apps_st/data/log02a.dbf'
Tue Dec 24 22:19:22 2013
WARNING: -------------------------------
WARNING: oradism did not start up correctly.
  Dynamic ISM can not be locked.----------------------------------------
oradism creation failed for unknown reasons 0 8 315
WARNING: -------------------------------
WARNING: oradism did not start up correctly.
  Dynamic ISM can not be locked.-----------------------

 

 

参考文档：

 

***Checked for relevance on 14-Jun-2012***

Problem Description:
====================

You are attempting to startup your database and receive the following errors:

    ORA-16014: log string sequence# string not archived, no available
               destinations
        Cause: An attempt was made to archive the named log, but the archive
               was unsuccessful. The archive failed because there were no
               archive log destinations specified or all destinations
               experienced debilitating errors.
       Action: Verify that archive log destinations are being specified and/or
               take the necessary step to correct any errors that may have
               occurred.

    ORA-00312: online log string thread string: 'string'
        Cause: This message reports the file name for details of another
               message.
       Action: Other messages will accompany this message. See the associated
               messages for the appropriate action to take.

Prior to this, the system was functioning correctly.  The database went down
suddenly and now it fails to start.

Solution Description:
=====================

1. Verify that the log_archive_dest is pointing to a valid directory. 

2. Make sure that there is sufficient space on disk to hold the
   archived logs.

   If necessary, move the existing archived logs off of this file system to
   either tape or another drive to make room. 

3. Once sufficient room has been made, start up the database. It should come
   up without errors.

4. If log_archive_dest_n (where n = 1 to 5) is specified for a standby database,
   make sure that the primary can send the archived log to the standby.

Explanation:
============

If you are in archivelog mode, you not only need to have the log_archive_dest
parameter pointing to a valid directory, but must have space on that disk to
create the archived files.  You will get the above errors if there is no space
left for the archiver to archive a redo log.

With the database in archive log mode, you have the additional task of making
sure that the archive log destination always has free space.  This can be done
manually or automated with either a 'cron' job or 'at' job system or some other
way of moving file to another location so that the directory never fills up.

If log_archive_dest_n is specified as mandatory, but the primary database cannot
send the archived logs to the standby, these errors will be returned.

Search Words:
=============

ORA-312