can't open database

SQL> select database_status from v$instance;

DATABASE_STATUS
-----------------
ACTIVE

How can I make it open, or what command will take it from active to open mode. I tried alter database open and it did not work

Issue

Alter database open;

Sam

I already did but it did not work. So I tried

SQL> alter database mount;
alter database mount
*
ERROR at line 1:
ORA-00205: error in identifying controlfile, check alert log for more info

I checked the controfile and got this

Mon May 7 11:12:43 2001
ORA-00202: controlfile: '/u09/ora09/POLICY/ctrlPOLICY01.ctl'
ORA-27086: skgfglk: unable to lock file - already in use

Are you sure it is not in open mode,
When I do a query on my db, it give:
DEVDB> select database_status,status from v$instance;

DATABASE_STATUS STATUS
----------------- -------
ACTIVE OPEN

Dragon

This is whay I got from your query:

SQL> select database_status,status from v$instance;


DATABASE_STATUS STATUS
----------------- -------
ACTIVE STARTED

Do a shutdown immediate on the system. BTW what is your OS and DB (name and version)


Sam

SQL> shutdown immediate
ORA-01507: database not mounted

ORACLE instance shut down.

SQL> startup
ORACLE instance started.

Total System Global Area 45166484 bytes
Fixed Size 73620 bytes
Variable Size 31813632 bytes
Database Buffers 13107200 bytes
Redo Buffers 172032 bytes
ORA-00205: error in identifying controlfile, check alert log for more info

I checked the alert file and got this:
ORA-27086 skgfglk: unable to lock file - already in use

The name of the database is POLICY running on IBM AIX Oracle 8.1.7





[Edited by panjub_raj on 05-07-2001 at 12:15 PM]

Issue shutdown abort

Check your alertSID.log for the primary cause of the problem. Is it your test/prod/dev server?


Issue the commands one by one and let us know the status.


Set your ORACLE_SID= in the env

$ svrmgrl
SVRMGR> connect internal as sysdba
SVRMGR> startup nomount;
SVRMGR> alter database mount;
SVRMGR> recover database; (If your database is in the archive mode)
SVRMGR> alter database open;




Here are some of the secanrios and their displays

SVRMGR> connect internal
Connected.
SVRMGR> startup nomount;
ORACLE instance started.
Total System Global Area 278446240 bytes
Fixed Size 73888 bytes
Variable Size 101072896 bytes
Database Buffers 177119232 bytes
Redo Buffers 180224 bytes
SVRMGR> select database_status, status from v$instance;
DATABASE_STATUS STATUS
----------------- -------
ACTIVE STARTED
1 row selected.
SVRMGR> alter database mount;
Statement processed.
SVRMGR> select database_status, status from v$instance;
DATABASE_STATUS STATUS
----------------- -------
ACTIVE MOUNTED
1 row selected.
SVRMGR> alter database open;
Statement processed.
SVRMGR> select database_status, status from v$instance;
DATABASE_STATUS STATUS
----------------- -------
ACTIVE OPEN
1 row selected.
SVRMGR>


Hope this would help you.

Sam

I di but I received another message. Below is what I did:

SVRMGR> connect internal
Connected.
SVRMGR> startup nomount;
ORA-01081: cannot start already-running ORACLE - shut it down first
SVRMGR> shutdown immediate;
ORA-01507: database not mounted
ORACLE instance shut down.
SVRMGR> connect internal
Connected.
SVRMGR> startup nomount;
ORACLE instance started.
Total System Global Area 45166484 bytes
Fixed Size 73620 bytes
Variable Size 31813632 bytes
Database Buffers 13107200 bytes
Redo Buffers 172032 bytes
SVRMGR> select database_status, status from v$instance;
DATABASE_STATUS STATUS
----------------- -------
ACTIVE STARTED
1 row selected.
SVRMGR> alter database mount;
alter database mount
*
ORA-00205: error in identifying controlfile, check alert log for more info
SVRMGR>


CONTENTS OF ALERT LOG
-----------------------------
ORA-00202: controlfile: '/u09/ora09/POLICY/ctrlPOLICY01.ctl'
ORA-27086: skgfglk: unable to lock file - already in use
IBM AIX RISC System/6000 Error: 13: Permission denied
Additional information: 8
Additional information: 95084

[Edited by panjub_raj on 05-07-2001 at 12:24 PM]

Is it a parallel server setup? If not I the suggestion at this point would be that if it was not a production server and you can afford to bounce it, then bounce the server. There seems to be some kind of problem in getting the lock on the control file.


Before bouncing your server, lets try this.

shutdown your instance

shutdown immediate/abort

do a ps -ef|grep instance_name and see if there are any unkilled processes. If you see any, kill them. Now try to start the instance, at nomount --> then mount --> then recover --> and then open.


Let me know whether this helps. In the past I have noticed that there had been some kind of wierd problem people had been experiencing with the startup of 8.1.7 instances. The last resolution of bouncing thier server was the fix for thier problems. If you have oracle support, pound at their doors and ask why the heck it is happening. :o

Sam

No it's not parrallel server. It's not in archive mode

Okay I killoed all the processes and did the following:

$ svrmgrl

Oracle Server Manager Release 3.1.7.0.0 - Production

Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.

Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production

SVRMGR> connect internal
Connected.
SVRMGR> startup nomount
ORACLE instance started.
Total System Global Area 45166484 bytes
Fixed Size 73620 bytes
Variable Size 31813632 bytes
Database Buffers 13107200 bytes
Redo Buffers 172032 bytes
SVRMGR> alter database mount
2> /
Statement processed.
SVRMGR>



QUESTION: since it's not in archive mode, do I still need to issue the recover command?



[Edited by panjub_raj on 05-07-2001 at 01:32 PM]

No. You can directly open the database

i.e

alter database open;


Sam