ORA-16638: could not get the instance status

Cause : The brkoer faield to cehck whehter theg iven isntance aws aliv eor not.

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

See th enext error mesasge in hte erro rstack ofr mored etaile dinformtaion. I fthe siutation edscribe din then ext erorr in teh stackc an be ocrrecte,d do so ;otherwsie, conatct Oralce Supprot Servcies.

update : 23-04-2017
ORA-16638

ORA-16638 - could not get the instance status
ORA-16638 - could not get the instance status

  • ora-07612 : $GETUAI failed in retrieving the user's clearance level
  • ora-16173 : incompatible archival network connections active
  • ora-01249 : archiving not allowed in a clone database
  • ora-30337 : multiple JOIN KEY clauses specified for the same parent level
  • ora-00021 : session attached to some other process; cannot switch session
  • ora-10651 : incorrect file number block number specified
  • ora-22293 : LOB already opened in the same transaction
  • ora-31669 : Worker process string violated startup protocol.
  • ora-31080 : type not specified for attribute or element "string"
  • ora-24789 : start not allowed in recursive call
  • ora-36952 : (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option.
  • ora-24779 : detach not allowed with open remote cursor
  • ora-25333 : Buffered Queue to Queue propagation did not connect to the correct instance
  • ora-04060 : insufficient privileges to execute string
  • ora-24026 : operation failed, queue string.string has errors
  • ora-07682 : sou2os: set kernel dispatch fail err
  • ora-06000 : NETASY: port open failure
  • ora-13401 : duplicate entry for string in USER_SDO_GEOR_SYSDATA view
  • ora-40105 : input data incompatible with model signature
  • ora-03240 : User's temporary tablespace same as tablespace being migrated
  • ora-12031 : cannot use primary key columns from materialized view log on "string"."string"
  • ora-36998 : (XSRELGID15) LEVEL ORDER VALUESET workspace object and LEVEL RELATION workspace object have the different level dimensions.
  • ora-10243 : simulated error for test string of K2GTAB latch cleanup
  • ora-02036 : too many variables to describe with automatic cursor open
  • ora-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • ora-13027 : unable to read dimension definition from string
  • ora-16711 : the resource guard index is out of bounds
  • ora-19563 : %s header validation failed for file string
  • ora-04066 : non-executable object, string
  • ora-19278 : Invalid value: (string) for type: (string)
  • 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.