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 : 30-05-2017
ORA-16638

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

  • ora-27092 : size of file exceeds file size limit of the process
  • ora-01489 : result of string concatenation is too long
  • ora-19861 : additional backup pieces cannot be validated in this conversation
  • ora-10651 : incorrect file number block number specified
  • ora-16064 : remote archival is disabled by another instance
  • ora-03008 : parameter COMPATIBLE >= string needed for string
  • ora-01296 : character set mismatch between dictionary string and logfiles
  • ora-24460 : Native Net Internal Error
  • ora-13114 : [string]_NODE$ table does not exist
  • ora-01119 : error in creating database file 'string'
  • ora-23330 : column group string already exists
  • ora-08429 : raw data has invalid digit in display type data
  • ora-30205 : invalid Character set
  • ora-01854 : julian date must be between 1 and 5373484
  • ora-31428 : no publication contains all the specified columns
  • ora-01909 : REUSE keyword expected
  • ora-12090 : cannot online redefine table "string"."string"
  • ora-30732 : table contains no user-visible columns
  • ora-01104 : number of control files (string) does not equal string
  • ora-26063 : Can not flashback to specified SCN value - Wrap: string Base: string.
  • ora-19025 : EXTRACTVALUE returns value of only one node
  • ora-03207 : subpartitioned type must be specified for composite object
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-39058 : current object skipped: string of type string
  • ora-31199 : Warning in processing file string
  • ora-09916 : Required password was not specified.
  • ora-04095 : trigger 'string' already exists on another table, cannot replace it
  • ora-28560 : error in configuration of agent process
  • ora-12657 : No algorithms installed
  • ora-22924 : snapshot too old
  • 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.