I'm not sure about the upgrade from WinNT to Win2K, but the easiest remedy
for the DB not auto-starting is to delete and re-create the service.

You can use ORADIM, and then while re-creating the service, you can use
option of autostart.

Regards
Naveen

-----Original Message-----
Sent: Wednesday, October 16, 2002 8:29 PM
To: Multiple recipients of list ORACLE-L



All
 I apologise I haven't had time to thank those who responded to my
question about passing a list of variables to a stored procedure. 

There have been many fires burning here... so I haven't had time to
respond.

The problem I'm experiencing is this

Management decided to upgrade the OS on our one of our development
servers. No one asked for any input from me... but guess who they are
asking to fix it??
I assure you all I had absolutely nothing to do with upgrading the OS
without checking compatibility issues.
<sigh...>

We have 30 instances
5 - 7.34
5 - 8.05
20 - 8.1.6
Running on NT 4.0 sp6a  4G ram, twin 500 processors. All these databases
are *not* production but rather development databases. The physical
server's resources seemed to be more than adequate and never were an
issue

The problem began when the OS was upgraded to WIN2K server, now all the
8.16 dbs will not start automatically (upon boot) If I look at the
service it says "starting" rather than started. Trying to connect with
sql plus as internal I get "connected to an idle instance" So the only
way to start the db is to pass sql plus the startup pfile=....
Then I'm good to go.

I have a tar with Oracle and did the following recommendations
1. Applied the highest patch to 8.16 + a special 1 off patch, made no
difference
At that point Oracle suggested to upgrade to 8.17 as 8.16 is not
supported on WIN2K server
2. Installed Oracle 8.17, set the home to 8.17 migrated 1 db as a test;
all other dbs were started via batch script

The new (migrated db still exhibits the original symptoms after the
upgrade) which were
If you try to connect via sql+ I get Oracle not available
The db is listed as "starting" rather than started"
I must physically start the db using SQL> startup pfile=...
Or

e.g.
[startup.bat]
svrmgrl.exe command='@C:\db_startup\initdb8i.sql' 
C:\sleep 3
svrmgrl.exe command='@C:\db_startup\initdbdev.sql' 
...

[initdb8i.sql]
connect internal/password@db8i
startup pfile=T:\Admin\db8i\PFILE\initdb8i.ora
exit 

Oracle is saying this is bug 1266248 which precisely describes the
problem

Does anyone have any info or a solution for this??

As always many thanks....

Bob

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Bob Metelsky
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Naveen Nahata
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to