Q

Change the DBID using NID

We need to change the DBID using NID. To do this the database can not be open. We startup mount and find that the database is open. What could be causing this condition? Startup NOmount also opens the database. This is Oracle EE 9.2.0.5. on Solaris 2.8.
If you perform SHUTDOWN IMMEDIATE followed by STARTUP MOUNT, then your database will not be OPEN. This can be verified by querying V$INSTANCE. When I perform these operations on Oracle 9.2.0.6 on Sun Solaris, I get the following:

SQL> shutdown immediate
Database closed.
Database dismounted.
SQL> startup mount
ORACLE instance started.
...
Database mounted.
SQL> select status from v$instance; STATUS
-----------
MOUNTED

If you perform the same operations and the query from V$INSTANCE is reporting OPEN, then there must be some other process that is opening the database. Is it possible that you have a cron or OEM job that does something to this affect?

This was last published in April 2005

Dig Deeper on Oracle database design and architecture

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide

SearchDataCenter

SearchContentManagement

SearchFinancialApplications

Close