Recently, an oracle exception occurred at the brother company Kunshan plant, which was unavailable to all DBA users during rebuild em. I always thought it happened after rebuild. I can see his mail today. It turns out that he cannot use it when deleting em.
I also encountered this problem in February. At that time, after modifying the IP address reconstruction em in the test environment, the EM of the official database was rebuilt at noon. The results produced line report Program If it cannot be used, stop it. Later, in the test environment, it was found that the EM could not be re-built online, because when the EM database was deleted, the instance would be in the quiesced state and refused to be used by users other than sys & system. The test status is as follows:
After the emca-deconfig dbcontrol DB-repos drop command is run,
SQL> select database_status, status, active_state from V $ instance;
Database_status status active_state
----------------------------------
Active open Quiesced
In this case, the user cannot use the database. After the deletion is completed, it automatically changes to normal. During the re-creation process, the database remains in the normal state as follows:
After emca-config dbcontrol DB-repos create
SQL> select database_status, status, active_state from V $ instance;
database_status status active_state
--------------- ------ -------------
active open normal
