RE: how to determine who/what is opening the database

  • From: "Goulet, Richard" <Richard.Goulet@xxxxxxxxxxx>
  • To: <Chris.Stephens@xxxxxxx>, "ORACLE-L" <oracle-l@xxxxxxxxxxxxx>
  • Date: Mon, 26 Jul 2010 09:29:50 -0400

Chris,
 
    Have the system admin check if the init daemon is doing it for you.
I've set up db's on HP-UX where the database started automatically when
the init level changed to 5.  Consequently if I shutdown the database
fro maintenance I needed to have the sysadmin lower the init level to 4.
Else what you are seeing happened.
 

Dick Goulet 
Senior Oracle DBA/NA Team Lead 
PAREXEL International 

 

________________________________

From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Stephens, Chris
Sent: Sunday, July 25, 2010 12:26 PM
To: ORACLE-L
Subject: how to determine who/what is opening the database



10.2.0.4 on RHEL 5

 

I'm in doing some datafile renaming for my own sanity.

 

The thing is, once I mount the database and rename a few datafiles, I
start getting messages that the database is open.

 

ERROR at line 1:

ORA-01511: error in renaming log/data files

ORA-01121: cannot rename database file 2 - file is in use or recovery

ORA-01110: data file 2: '/u01/oradata/db_name/undotbs01.dbf'

 

SYS@remgt> alter database open;

alter database open

*

ERROR at line 1:

ORA-01531: a database already open by the instance

 

 

How would I go about figuring out what or who is opening the database?
This has happened repeatedly.

 

I have contact the system administrators and they can't think of any
monitoring software they have configured to do thiat.


CONFIDENTIALITY NOTICE:
This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If the
reader of this message is not the intended recipient or the employee or
agent responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or copying
of this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by email reply.



Other related posts: