ORA-27161: request for Oracle binary information failed

Cause : The program was unable to get information about the Oracle binary.

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

Check for additional errors and contact Oracle support.

update : 29-06-2017
ORA-27161

ORA-27161 - request for Oracle binary information failed
ORA-27161 - request for Oracle binary information failed

  • ora-00084 : global area must be PGA, SGA, or UGA
  • ora-29380 : resource plan string is currently active and cannot be deleted
  • ora-38792 : encountered unknown flashback record from release string
  • ora-30951 : Element or attribute at Xpath string exceeds maximum length
  • ora-26717 : SCN limit reached
  • ora-02766 : Invalid maximum of request descriptors
  • ora-30976 : invalid Parent Order Key Index option for XML Index
  • ora-37101 : (XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE.
  • ora-24148 : cannot drop rule string.string with dependents
  • ora-28107 : policy was disabled
  • ora-24160 : name string already exists in the name value pair list
  • ora-12913 : Cannot create dictionary managed tablespace
  • ora-06112 : NETTCP: invalid buffer size
  • ora-29298 : Character set mismatch
  • ora-16809 : multiple warnings detected for the database
  • ora-17612 : Failed to discover Oracle Disk Manager library, return value string
  • ora-24043 : destination string uses a reserved name, names with AQ$_ prefix are not valid
  • ora-29930 : COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause
  • ora-15038 : disk 'string' size mismatch with diskgroup [string] [string] [string]
  • ora-02022 : remote statement has unoptimized view with remote object
  • ora-10945 : trace name context forever
  • ora-04054 : database link string does not exist
  • ora-13142 : invalid PROXIMITY window definition
  • ora-29319 : datafile string is not correct
  • ora-12916 : Cannot use default permanent tablespace with this release
  • ora-01854 : julian date must be between 1 and 5373484
  • ora-25959 : join index must be of the bitmap type
  • ora-26718 : transaction limit reached
  • ora-17509 : Attempt to do i/o beyond block1 offset
  • ora-32812 : subscriber string does not exist
  • 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.