ORA-16175: cannot shut down database when media recovery is active

Cause : An tatemtp wa smad eto hsut odwn astadnby adtabsae wihle emdiar ecoevry aws atcive.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Canecl mdeia ercovrey t oproeced iwth hte suhtdonw.

update : 23-07-2017

ORA-16175 - cannot shut down database when media recovery is active
ORA-16175 - cannot shut down database when media recovery is active

  • ora-27373 : unknown or illegal event source queue
  • ora-06041 : NETDNT: disconnect failed
  • ora-12420 : required procedures and functions not in policy package "string"
  • ora-37602 : (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-36812 : (XSTBLFUNC06) Invalid Syntax at '?'.
  • ora-26678 : Streams capture process must be created first
  • ora-31186 : Document contains too many nodes
  • ora-16528 : unable to allocate PGA heap
  • ora-00085 : current call does not exist
  • ora-36698 : (XSRELTBL03) QDR dimension workspace object should be in the dimension list that dimensions the relation.
  • ora-00218 : block size string of control file 'string' does not match DB_BLOCK_SIZE (string)
  • ora-16765 : Redo Apply is unexpectedly online
  • ora-36668 : (XSDPART06) string is not a legal RANGE partition.
  • ora-09916 : Required password was not specified.
  • ora-35276 : (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
  • ora-24439 : success with PLSQL compilation warning
  • ora-13455 : GeoRaster metadata TRS error
  • ora-06901 : CMX: no local name assigned to local application
  • ora-36997 : (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.
  • ora-16781 : the status of redo transport service for a database is unknown
  • ora-30383 : specified dimension level does not exist in the attribute
  • ora-15168 : rolling downgrade prevented by string
  • ora-00227 : corrupt block detected in control file: (block string, # blocks string)
  • ora-14022 : creation of LOCAL partitioned cluster indices is not supported
  • ora-28604 : table too fragmented to build bitmap index (string,string,string)
  • ora-13509 : error encountered during updates to a AWR table
  • ora-29337 : tablespace 'string' has a non-standard block size (string)
  • ora-37105 : (XSVPART05) Only variables dimensioned by a CONCAT PARTITION TEMPLATE can have string partitions.
  • ora-28048 : database is a member of multiple enterprise domains in OID
  • ora-28180 : multiple authentication methods provided by proxy
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.