ORACLE instance terminated. Disconnection forced

Posted on 2004-11-30
Last Modified: 2013-12-11
Hi ,
I am running Oracle 9i on RH Linux. I created a database. Everything went smooth till when I am trying to start  the database  I get  ORACLE instance terminated. Disconnection forced it works just fine with STARTUP NOMOUNT . Further looking into alert_${ORACLE_SID}.log I see
"ORA-1092 signalled during: ALTER DATABASE OPEN.." . After going through error manual I understand  The environment variables ORA_sid_PWFILE and ORA_PWFILE are not set.
Before I define these enviornment variable what should be the exact path to these orapw file . I have one $ORACLE_HOME/dbs/orapw${ORACLE_SID} and other in $ORACLE_BASE/oradata/$ORACLE_SID/orapw. Are these the correct path ?
Another question related to the same issue is initiallay in my init${ORACLE_SID}.ora. I had
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE set, later to overcome this issue I set
REMOTE_LOGIN_PASSWORDFILE=NONE but still having the same problem why? Do I need to change control file or some thing ?
Question by:sanjoybasu
    LVL 8

    Expert Comment

    by:Pierrick LOUBIER
    Try to set :


    If you set parameter REMOTE_LOGIN_PASSWORDFILE to NONE, you have to use secure connections (like ssh, not telnet). You may need to recreate the password file and set REMOTE_LOGIN_PASSWORDFILE back to EXCLUSIVE.

    Here is part of official documentation :

    In addition to creating the password file, you must also set the initialization parameter REMOTE_LOGIN_PASSWORDFILE to the appropriate value. The values recognized are:

    NONE: Setting this parameter to NONE causes Oracle Database to behave as if the password file does not exist. That is, no privileged connections are allowed over nonsecure connections. NONE is the default value for this parameter.

    EXCLUSIVE: An EXCLUSIVE password file can be used with only one database. Only an EXCLUSIVE file can contain the names of users other than SYS. Using an EXCLUSIVE password file lets you grant SYSDBA and SYSOPER system privileges to individual users and have them connect as themselves.

    SHARED: A SHARED password file can be used by multiple databases running on the same server. However, the only user recognized by a SHARED password file is SYS. You cannot add users to a SHARED password file. All users needing SYSDBA or SYSOPER system privileges must connect using the same name, SYS, and password. This option is useful if you have a single DBA administering multiple databases.


    To achieve the greatest level of security, you should set the REMOTE_LOGIN_PASSWORDFILE initialization parameter to EXCLUSIVE immediately after creating the password file.
    LVL 47

    Expert Comment

    You have to ensure correct values in
    environment variables.
    Check these variables.
    It seems they are changed and so the spfile could not be found.
    To open the database find in $ORACLE_BASE/admin/.../pfile directory and copy the parameter file
    to a file like init.ora.
    Try to open so:
    SQL>startup pfile=......./init.ora
    LVL 47

    Accepted Solution

    And if this is more likely this is an Oracle bug, fixed in the next releases.
    LVL 10

    Expert Comment

    You're NOT using the init.ora file, you're using the spfile.


    or rename in $ORACLE_HOME/dbs the spfile to use the init.ora file.

    It will work.
    LVL 10

    Expert Comment


    to modify the spfile directly

    Author Comment

    Thanks for your overwhelming response. I am working and will get back with status

    Author Comment

    Thanks all for your time however I would like to specially thanks schwertner for final solution. I was using and after exhausting all method I decided to go for dbca still remains a major heart burn. Manually creating database works fine..
    Thank you once again schwertner.

    Featured Post

    Looking for New Ways to Advertise?

    Engage with tech pros in our community with native advertising, as a Vendor Expert, and more.

    Join & Write a Comment

    This article started out as an Experts-Exchange question, which then grew into a quick tip to go along with an IOUG presentation for the Collaborate confernce and then later grew again into a full blown article with expanded functionality and legacy…
    Note: this article covers simple compression. Oracle introduced in version 11g release 2 a new feature called Advanced Compression which is not covered here. General principle of Oracle compression Oracle compression is a way of reducing the d…
    Via a live example show how to connect to RMAN, make basic configuration settings changes and then take a backup of a demo database
    Via a live example, show how to restore a database from backup after a simulated disk failure using RMAN.

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now