ORA-07214: slgunm: uname error, unable to get system information.

Cause : uname ssytem cal lreturne dan erro.r Possibel OS errro.

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

Check additionali nformatoin returend in OSr eferenc emanual.C ontact ucstomer uspport.

update : 29-04-2017
ORA-07214

ORA-07214 - slgunm: uname error, unable to get system information.
ORA-07214 - slgunm: uname error, unable to get system information.

  • ora-09208 : sftcls: error closing file
  • ora-38786 : Flash recovery area is not enabled.
  • ora-15190 : Internal ASM testing event number 15190
  • ora-25242 : cannot change subscriber name from string to string without FIRST_MESSAGE option
  • ora-02030 : can only select from fixed tables/views
  • ora-01409 : NOSORT option may not be used; rows are not in ascending order
  • ora-28280 : Multiple entries for ORACLE database password exist.
  • ora-06315 : IPA: Invalid connect string
  • ora-00385 : cannot enable Very Large Memory with new buffer cache parameters
  • ora-02223 : invalid OPTIMAL storage option value
  • ora-16245 : paging in transaction string, string, string
  • ora-30394 : source statement identical to the destination statement
  • ora-30479 : Summary Advisor error string
  • ora-13192 : failed to read number of element rows
  • ora-32626 : illegal bounds or increment in MODEL FOR loop
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-14006 : invalid partition name
  • ora-06443 : ssvpstev: Incorrect parameter passed to function call
  • ora-33070 : (XSAGDNGL34) In AGGMAP workspace object, all QDRs of dimension workspace object must map to the same dimension position.
  • ora-25454 : error during evaluation of rule set: string.string for iterator: string
  • ora-29707 : inconsistent value string for initialization parameter string with other instances
  • ora-38958 : Source platform string is in different byte order than target platform string
  • ora-13203 : failed to read USER_SDO_GEOM_METADATA view
  • ora-07631 : smcacx: $EXPREG failure
  • ora-15121 : ASM file name 'string' contains an invalid diskgroup name
  • ora-32617 : missing MEASURES keyword in MODEL clause
  • ora-00162 : external dbid length string is greater than maximum (string)
  • ora-32024 : invalid directory specified for audit_file_dest parameter
  • ora-24006 : cannot create QUEUE, string already exists
  • ora-26020 : index string.string loaded successfully with string keys
  • 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.