DBAsupport.com Forums - Powered by vBulletin
Results 1 to 2 of 2

Thread: ORA-01092: ORACLE instance terminated. Disconnection forced

  1. #1
    Join Date
    Nov 2000
    Posts
    42

    Unhappy

    Hello.

    On Windows NT 4.0 + Oracle 8i, I'm trying to connect my DB via ServerManager

    SVRMGR> connect;
    Username: system
    Password: xxxx
    ORA-01092: ORACLE instance terminated. Disconnection forced

    And if I try to startup my DB:

    SVRMGR> connect internal;
    Password: xxxx
    Connected.
    SVRMGR> startup;
    ORA-01081: cannot start already-running ORACLE - shut it down first
    SVRMGR> shutdown immediate;
    ORA-03114: not connected to ORACLE

    What is happening?

    Regards.
    ========
    LARRY ELLISON

  2. #2
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    4,166
    I found this on Metalink:
    Check to see if the Alert log is being written to.

    Doc ID: Note:1038418.6
    Subject: ORA-01092 STARTING UP ORACLE RDBMS DATABASE
    Type: PROBLEM
    Status: PUBLISHED
    Content Type: TEXT/PLAIN
    Creation Date: 17-NOV-1997
    Last Revision Date: 06-JUL-1999



    Problem Summary:
    ================

    ORA-01092 starting up Oracle RDBMS database.


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

    When you startup your Oracle RDBMS database, you receive the following error:

    ORA-01092: ORACLE instance terminated. Disconnection forced.


    Problem Explanation:
    ====================

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

    Solution Summary:
    =================

    Modify the ownership and permissions of directory BACKGROUND_DUMP_DEST.


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

    To allow oracle to write to the BACKGROUND_DUMP_DEST directory (contains
    alert_.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.ora or config.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_.log file.
    .



    --------------------------------------------------------------------------------

    Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal Notices and Terms of Use.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width