ok, Platform is NT4, SP5.
Database is 8.1.7
PC 256 Mb ram, 800Mhz, 6+gb free.
I have an 8.1.7 database on this machine. I installed Dev & Designer 6i into a new oracle home as instructed by the install guide.
Now when i run svrmgrl it fails to work properly, even after I use the Oracle Home Selector for the installer to point at the 8i home of the database.
In Svrmgrl I get:
Microsoft(R) Windows NT(TM)
(C) Copyright 1985-1996 Microsoft Corp.
Oracle Server Manager Release 188.8.131.52.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
Oracle8i Enterprise Edition Release 184.108.40.206.0 - Production
JServer Release 220.127.116.11.0 - Production
SVRMGR> connect internal
ORA-01081: cannot start already-running ORACLE - shut it down first
ORA-01034: ORACLE not available
In sqlplus I get similar when I connect internal
SQL*Plus: Release 18.104.22.168.0 - Production on Mon Jun 25 09:49:49 2001
(c) Copyright 2000 Oracle Corporation. All rights reserved.
LRM-00109: could not open parameter file
ORA-01078: failure in processing system parameters
06-25-2001, 06:23 AM
you can do one thing if it is NT Server Stop the Oracle instance services and then again start the service that's all ok
if it is Linux, Solaris, Unix kill the process Or Restart the server it work's fine...
and please check once again The init.ora parameters...
06-25-2001, 06:36 AM
and see what happens
06-25-2001, 09:44 AM
In the windows env, try stopping and starting through the services and it would fix. The server manager option was about to be removed.
Try first shutting down as
shutdown abort and then starting it again. One other thing is instead of connecting through the server manager, try connecting as
sqlplus sys/passwd as sysdba
SQL> shutdown immediate
or if it was a fresh install, then try
Hope this would help you.
06-26-2001, 06:05 AM
yes, you are of course right. I got so caught up in thinking about multiple-homes, and why dev/designer should affect svrmgrl that I missed the obvious thing of trying a shutdown abort. After that, the db and svrmgrl acted normally... I guess that the dev/des thikng was just a red herring :-)