Re: how to determine who/what is opening the database
- From: troach@xxxxxxxxx
- To: Chris.Stephens@xxxxxxx,"'harel.safra@xxxxxxxxx'" <harel.safra@xxxxxxxxx>,"'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx>
- Date: Sun, 25 Jul 2010 18:39:06 +0000
I seconds this.
Also if it is just datafiles within an existing tablespace then just take it
offline before moving them.
Sent from my Verizon Wireless BlackBerry
-----Original Message-----
From: "Stephens, Chris" <Chris.Stephens@xxxxxxx>
Sender: oracle-l-bounce@xxxxxxxxxxxxx
Date: Sun, 25 Jul 2010 13:33:10
To: 'harel.safra@xxxxxxxxx'<harel.safra@xxxxxxxxx>;
'oracle-l@xxxxxxxxxxxxx'<oracle-l@xxxxxxxxxxxxx>
Reply-To: Chris.Stephens@xxxxxxx
Subject: Re: how to determine who/what is opening the database
I'm away from computer now but this may very well be it.
________________________________
From: Harel Safra <harel.safra@xxxxxxxxx>
To: Stephens, Chris; 'ORACLE-L' <oracle-l@xxxxxxxxxxxxx>
Sent: Sun Jul 25 12:58:41 2010
Subject: RE: how to determine who/what is opening the database
I think I've seen the data guard broker do things like this.
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Stephens, Chris
Sent: Sunday, July 25, 2010 7:33 PM
To: Stephens, Chris; ORACLE-L
Subject: RE: how to determine who/what is opening the database
This is almost certainly coming from some sort of automated process. The
database is only opened by something else once the database is mounted (and I’m
trying to rename my database files!!).
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Stephens, Chris
Sent: Sunday, July 25, 2010 11:26 AM
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.
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.
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:
