connect internal
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 8 of 8

Thread: connect internal

  1. #1
    Join Date
    Apr 2001
    Posts
    20
    Hi all,

    The connect internal is not working after the first session exit.
    The scenario is
    --the oracle is down
    --go to svrmgr...connect internal...startup
    --oracle started
    --now any select statement at svrmgr prompt is working fine.
    --exit from this session
    --go to srvrmgr..connect internal...give a select statement
    --gives the ERROR : ORA-01012 Not logged in

    all subsequent svrmgr, connect internal, select statement gives error.

    when connect internal is given, connected message is displayed promptly..

    ORACLE 8.0.5 on NT

    could someone give tips to resolve this nagging problem

    Thanks in advance
    STS

  2. #2
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    It might be some OS level issue. So, try rebooting the NT and then connecting using connect internal


    Sam
    Thanx
    Sam



    Life is a journey, not a destination!


  3. #3
    Join Date
    Jun 2001
    Posts
    8
    We have tried rebooting the server. That didn't fix the issue. Any other ideas?

  4. #4
    Join Date
    Mar 2001
    Posts
    635
    Hi

    This is what metalink has to say about ur error

    Error: ORA 1012
    Text: not logged on
    -------------------------------------------------------------------------------
    Cause: A host language program issued an Oracle call, other than OLON or
    OLOGON, without being logged on to Oracle.
    This can occur when a user process attempts to access the database
    after the instance it is connected to terminates, forcing the process
    to disconnect.
    Action: Log on to Oracle, by calling OLON or OLOGON, before issuing any Oracle
    calls.
    When the instance has been restarted, retry the action

    Try the above action if not open a tar with oracle

    Regards
    Santosh

  5. #5
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    try

    c:> svrmgrl

    SVRMGR> connect sys/passwd as sysdba

    Hope this would help. BTW, what happen for the database to come down. Check your alert logs for any problem symptoms.


    sam
    Thanx
    Sam



    Life is a journey, not a destination!


  6. #6
    Join Date
    Jun 2001
    Posts
    8
    Hi Sam,
    When we do a "connect sys/passwd as sysdba", we get a message that it is "connected". If we issue any select statement, we get the "ORA-01012: not logged on" error message. If we "connect sys/passwd", we are able to enter any select statement with a problem.

    The database operates fine in this state. The big issue with this current situation is that the only way we are currently able to shutdown this database is to stop the two Oracle services through Control Panel...Services. This (of course) is very dangerous, because it causes the database to abort, and a database recovery is required upon startup.

    Any help would be appreciated. Thanks, Wally

  7. #7
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    Did you get to try santoshym's approach. If you are able to connect to the instance as sysdba then once after connecting in, try issuing shutdown immediate. It might take some time to shutdown. Once it shuts down start you database as startup.

    If your instances are in the archive mode, then you can try the other approach of shuting them using the control pannel and startup in the recovery mode.


    Sam
    Thanx
    Sam



    Life is a journey, not a destination!


  8. #8
    Join Date
    Jun 2001
    Posts
    8
    Hi,
    I have never connected with either OLON or OLOGON. Not sure how to do that. I also connect to the database from the operating system level through either SVRMGR30 or SQLPLUS.

    We do have archiving on. If we issue a "shutdown immediate" after doing a "connect sys/passwd as sysdba", we get the "ORA-01012: not logged on" error. We are only able to shutdown the database by stopping the 2 Oracle services.
    Thanks, Wally

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