Re: manual creation

From: Curtis <cmarchand_at_norambar.ca>
Date: 14 May 2004 06:07:02 -0700
Message-ID: <77459c6d.0405140507.27335cf4_at_posting.google.com>


I found this, hope it helps you out.

Oracle cannot write to the alert_<SID>.log file because the ownership and/or permissions on the BACKGROUND_DUMP_DEST directory are incorrect.

Solution
Modify the ownership and permissions of directory BACKGROUND_DUMP_DEST. To allow oracle to write to the BACKGROUND_DUMP_DEST directory (contains alert_<SID>.log), modify the ownership of directory BACKGROUND_DUMP_DEST so that the oracle user (software owner) is the owner and make the permissions on directory BACKGROUND_DUMP_DEST 755.  

Follow these steps:

  1. Determine the location of the BACKGROUND_DUMP_DEST parameter defined in the init<SID>.ora or config<SID>.ora files.
  2. Login as root.
  3. Change directory to the location of BACKGROUND_DUMP_DEST.
  4. Change the owner of all the files and the directory to the software owner. For example:
    % chown oracle *
  5. Change the permissions on the directory to 755.
    % chmod 755 .

Solution Explanation:
Changing the ownership and permissions of the BACKGROUND_DUMP_DEST directory, enables oracle to write to the alert_<SID>.log file.

Is there any other message in your alert log?

   SQL> startup
    ORACLE instance started.  

    Total System Global Area 252478536 bytes

    Fixed Size                   279624 bytes 
    Variable Size             167772160 bytes 
    Database Buffers           83886080 bytes 
    Redo Buffers                 540672 bytes 
    Database mounted.  

    ORA-01092: ORACLE instance terminated. Disconnection forced No background processes are started.  

ORA-01092: Oracle instance terminated. Disconnection forced

    Cause: The instance connected to was terminated abnormally, probably

           due to a SHUTDOWN ABORT.  The current process was forced to  
           disconnect from the instance. 
   Action: Contact the database administrator to determine when the  
           instance is restarted.  Attempt to reconnect after the instance  
           is running again. 
 

Solution Description
In the alert.log file there is additional information on the error context:  

    SMON: enabling cache recovery
    Thu Aug 2 14:19:45 2001
    Errors in file /ora/ora901/admin/V901/udump/v901_ora_21863.trc:     ORA-30012: undo tablespace 'UNDO1' does not exist or of wrong type     Thu Aug 2 14:19:45 2001
    Error 30012 happened during db open, shutting down database     USER: terminating instance due to error 30012     Instance terminated by USER, pid = 21863     ORA-1092 signalled during: ALTER DATABASE OPEN...    

You have three options to resolve this issue: 1. If an UNDO tablespace currently exists in the database, edit the

    init<SID>.ora file to set the UNDO_TABLESPACE parameter to the name of the     existing UNDO tablespace and restart the database. - OR -
2. If no UNDO tablespace exists, edit the init<SID>.ora file to comment out

    the UNDO_MANAGEMENT parameter: the default value for UNDO_MANAGEMENT is     MANUAL.
    Then, after starting the database, do one of the following:

  1. Create a non UNDO tablespace with at least one online rollback segment. The instance can work this way. -OR-
  2. Create a new UNDO tablespace. If you want the instance to work under Automatic Undo Management,
  3. Set the UNDO_MANAGEMENT back to AUTO
  4. Set the UNDO_TABLESPACE parameter to the name of the new UNDO tablespace
  5. Restart the database

Explanation
The database is using Automatic Undo Management (AUM). In the init<SID>.ora file, the parameter UNDO_MANAGEMENT is set to AUTO and UNDO_TABLESPACE to a tablespace that does not exist or is not an UNDO type tablespace.

Curtis Received on Fri May 14 2004 - 15:07:02 CEST

Original text of this message