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

Thread: ora-12162/mgr-00310 using dbstart/dbshut after upgrade db from 816 to 817

  1. #1
    Join Date
    Jul 2001
    Posts
    11
    Dear DBAs,

    We upgraded our 816 db to 817 successfully.

    However, using the dbstart/dbshut script gave the following error:

    ORA-12162: TNS:service name is incorrectly specified
    SVRMGR> Password:
    Password:
    ORA-12162: TNS:service name is incorrectly specified
    SVRMGR> MGR-00310: cannot open parameter file ""
    SVRMGR>
    Server Manager complete.

    If we use svrmgrl from the unix prompt, and startup/shutdown the db, we do not get such errors.

    Why would the dbstart/dbshut script give these errors?

    Any help appreciated.

    Thank you,

    Tony

  2. #2
    Join Date
    Jul 2000
    Posts
    243
    Hi

    i'm not next to server, or ave any access to metalink at the moment to check this, but as far as i remember, in this script has as a standard shutdown normal, and we changed it. so, look at your script and see if your guy's changed it as well, and that is the reasone for your problems

  3. #3
    Join Date
    Oct 2000
    Location
    Germany
    Posts
    1,185
    Does your script specify the TNS_ADMIN location, the PATH, and the ORACLE_HOME correctly?

    If the values are set for the old instance, maybe that is your problem.

    Good luck.
    David Knight
    OCP DBA 8i, 9i, 10g

  4. #4
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    Check your oratab file, if you are in the Unix env and make sure that the instance's ORACLE_HOME had been defined properly.

    Sam
    Thanx
    Sam



    Life is a journey, not a destination!


  5. #5
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Are you using the 8.1.6 or the 8.1.7 dbstart/dbshut script?
    Jeff Hunter

  6. #6
    Join Date
    Jul 2001
    Posts
    11
    Thanks guys!

    Firsty, nothing was changed in the dbstart/dbshut scripts. We used the standard scripts supplied.

    Yes, we used the scripts supplied with 817, and the new Oracle Home was entered into the oratab file.

    The 817 scripts do not have TNS_ADMIN location and neither did the 816 scripts. We do have TNS_ADMIN set in the UNIX envirnment though which is the new 817 path.

    Using svrmgrl to startup/shutdwn the DB do not give these errors. Only using the dbstart/dbshut scripts.

    The listener started up properly and we were able to connect via SQL*NET clients.

    While this error is not life threatening, it would be nice to solve this riddle.

    Thanks again!

  7. #7
    Join Date
    Jul 2001
    Posts
    11
    Fellow DBAs,

    Thought you might be interested to know that the cause of this problem was the following entry in the oratab file:

    *:/app/oracle/product/8.1.7:Y

    By commenting this entry out, or by changing the last item Y to N, solved the problem.

    Seems 817 did not like this at all -- there was no problem with 816.

    Thanks again for all your help and time.


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