Startup open ORA_12514 error after Shutdown, just upgraded 9i to 10g

Question

Hi,
Noobe here, again! Cheers and happy New Year to all!
How should I edit script to start db that has been shutdown prior to backup?
We are having a problem with backups, failure is occurring executing SQL*Plus startup after shutdown. I successfully upgraded our 9i to 10g, 10.2.0.5.0 on Windows server 2003, 32-bit. We have a back_script.bat that runs all this, the only edits that I had to make within this were the names for the new Oracle services, but that is not a problem. When I run through the actions in the batch file, it fails at the sql>startup open; action, throws the error "ORA-12514 TNS:listener does not currently nkow of service requested in connect descriptor" What is different here between 9i and 10g that now this doesn't work? By commenting out the line calling our oracle_stop_start.sql I am getting successful >exp dumps, but there could be processes running 'cause I'm not stopping everything before proceeding with the export.
I have a complete image of the physical server running in a virtual that I am able to test on. Hopefully I'll not put too much info in here, but here is some background! Both the batch file and little stop_start script predate my involvement.
Here are the pertinent statements in our backup_script.bat:
SET NLS_LANG=AMERICAN_AMERICA.UTF8
SET ORACLE_SID=wind
net stop Windchill3_MethodServer (the third party application that uses the database wind)
sqlplus "system/manager@wind as sysdba" @D:\ptc\windchill\backups\oracle_stop_start
exp system/manager@wind owner=guest file=......\oracle_backup.dmp.....etc, etc, etc
Here is oracle_stop_start.sql
shutdown immediate;
startup open;
quit
As stated earlier, this has worked at least since 2007 when the last edits were made to the batch file. Now it fails at the sql>startup open; throwing the error ORA-12514. I can duplicate this executing each statement in a dos shell. The shutdown command closes, dismounts and shuts down the database. I have tried changing the startup statement to sql>STARTUP OPEN wind; but that makes no difference. I have found that if I exit sql*plus and log back in /nolog (in the same shell window) then I can restart the instance, what I do is:
sqlplus /nologsql>connect sys/* as sysdba;
sql>startup open wind;
This does successfully start the Oracle instance, mount and open the database. How else might I do this? I can certainly duplicate these actions, adding the necessary lines to oracle_start_stop.sql, but is there a better & cleaner way to do this? Right now I just want to make these existing scripts work. Once that is done, then I'm going to investigate and learn more about RMAN and datapump export/import and update our backup procedures.
Any thoughts & suggestions?
Thank you,
Tom

Answer 1

It might be a difference in behaviour between 9i and 10g. It looks like you are connecting through sql*net (sqlplus "system/manager@wind as sysdba), so the ORACLE_SID setting is not part of your connection. When the database is shutdown you are no longer connected to any database. When you issue the startup command the ORACLE_SID is not set so there is no service specified.
If you are running this on the database server, try setting the ORACLE_SID then running your script like:
{code}sqlplus "system/manager as sysdba" @D:\ptc\windchill\backups\oracle_stop_start{code}
and you should still have the service set for your connection.
John