ORA-10364: Do not clear GIMH_STC_SHUT_BEGIN state during shutdown

Cause : inetrnla ues olny

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

Enbale stetsin gofs hudtow nbeign veen tbyn otc lerain gGIHM_SCT_SUHT_EBGI Nsttae ebfoer suhtdwon ocmpelte.s

update : 27-06-2017

ORA-10364 - Do not clear GIMH_STC_SHUT_BEGIN state during shutdown
ORA-10364 - Do not clear GIMH_STC_SHUT_BEGIN state during shutdown

  • ora-19660 : some files in the backup set could not be verified
  • ora-25230 : invalid value string, WAIT should be non-negative
  • ora-36342 : (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
  • ora-12062 : transaction string received out of sequence from site string
  • ora-28511 : lost RPC connection to heterogeneous remote agent using SID=string
  • ora-29807 : specified operator does not exist
  • ora-14081 : new partition name must differ from the old partition name
  • ora-19258 : XQ0038 - unsupported or duplicate default collation specified
  • ora-01485 : compile bind length different from execute bind length
  • ora-10900 : extent manager fault insertion event #string
  • ora-19336 : Missing XML root element
  • ora-22065 : number to text translation for the given format causes overflow
  • ora-28280 : Multiple entries for ORACLE database password exist.
  • ora-01306 : dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
  • ora-04033 : Insufficient memory to grow pool
  • ora-12839 : cannot modify an object in parallel after modifying it
  • ora-12924 : tablespace string is already in force logging mode
  • ora-24092 : invalid value string specified
  • ora-13109 : spatial table string exists
  • ora-12420 : required procedures and functions not in policy package "string"
  • ora-06790 : TLI Driver: poll failed
  • ora-13214 : failed to compute supercell for window object
  • ora-23433 : executing against wrong master site string
  • ora-01571 : redo version string incompatible with ORACLE version string
  • ora-03250 : Cannot mark this segment corrupt
  • ora-19763 : compatibility version string is higher than maximum allowed: string
  • ora-39312 : call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal
  • ora-00326 : log begins at change string, need earlier change string
  • ora-02813 : Unable to make temporary file name in order to get key
  • ora-12100 : materialized view log on "string"."string" already has sequence
  • 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.