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 : 29-04-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-31111 : table string cannot be hierarchically enabled
  • ora-22920 : row containing the LOB value is not locked
  • ora-36768 : (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT must have the same base dimensions.
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-30354 : Query rewrite not allowed on SYS relations
  • ora-32103 : error from OCI call
  • ora-22053 : overflow error
  • ora-27062 : could not find pending async I/Os
  • ora-40215 : model string is incompatible with current operation
  • ora-01273 : STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher
  • ora-07216 : slghst: gethostname error, unable to get name of current host.
  • ora-02050 : transaction string rolled back, some remote DBs may be in-doubt
  • ora-27025 : skgfqsbi: invalid media manager context area size
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-02466 : The SIZE and INITRANS options cannot be altered for HASH CLUSTERS.
  • ora-39781 : Direct path stream loads are not allowed after another context loading the same table has ended
  • ora-31194 : Resource string is already deleted
  • ora-32332 : cannot refresh materialized view "string"."string" as type evolution has occured
  • ora-16052 : DB_UNIQUE_NAME attribute is required
  • ora-02786 : Size needed for shared region is greater than segment size
  • ora-13217 : invalid parameters supplied in ALTER INDEX statement
  • ora-25442 : too many column values for table alias: string
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-12708 : error while loading create database NLS parameter string
  • ora-13485 : error occurred during compression or decompression: string
  • ora-36644 : (XSDUNION07) Concat dimension workspace object contains a previously detected leaf dimension.
  • ora-24045 : invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
  • ora-07585 : spdcr: $PARSE failure
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-02782 : Both read and write functions were not specified
  • 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.