Component : Oracle -

Solution : https://service.sap.com/sap/support/notes/1044758 (SAP Service marketplace login required)

Summary :
When using Oracle 10.2, if the EMCA utility is deployed either to develop or remove the Enterprise Manager repository, the corresponding SAP applications may encounter disruptions. The utility triggers the database to enter QUIESCE mode, prioritizing its operations and therefore preventing access for common SAP-related Oracle users such as SAPR3 and SAP. This behavior can be identified by the 'QUIESCED' status via an SQL query. The solution involves terminating the EMCA process and executing 'alter system unquiesce' in SQL*Plus as SYSDBA, to revert the database to its normal operational state. For reference, see Oracle Metalink Note 375946.1.

Key words :
'emca -config dbcontrol db -repos recreate''emca -deconfig dbcontrol db -repos drop', concurrent alter system quiesce/unquiesce command, sysdba               sql > alter system unquiesce, sql > alter system unquiesce, alter system unquiesce error, enterprise manager database control, 'emca' command, emca switches, database alert log, referenceoracle metalink note 375946

Related Notes :

619188

FAQ: Oracle wait events