ORA-09986: wrong number of bytes read from SGA definition file

Cause : Struct skgmsdef size differs from no. of bytes read from SGA file

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

Compare the two struct definitions and ensure that they are identical in size and structure.

update : 27-05-2017
ORA-09986

ORA-09986 - wrong number of bytes read from SGA definition file
ORA-09986 - wrong number of bytes read from SGA definition file

  • ora-15079 : ASM file is closed
  • ora-33002 : (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument of number must be less than the CEILING argument of number.
  • ora-09342 : Detached process terminated by Oracle during shutdown abort
  • ora-39113 : Unable to determine database version
  • ora-01251 : Unknown File Header Version read for file number string
  • ora-39142 : incompatible version number string in dump file "string"
  • ora-08236 : smsget: cannot share subcube with listener
  • ora-02437 : cannot validate (string.string) - primary key violated
  • ora-36267 : (XSCGMDLAGG09) workspace object has no dimensions, so it cannot have a qualified data reference.
  • ora-24191 : the property name string has existed
  • ora-01870 : the intervals or datetimes are not mutually comparable
  • ora-31535 : cannot support change source string in this configuration
  • ora-24410 : scrollable cursor max size exceeded
  • ora-16257 : Switchover initiated stop apply successfully completed
  • ora-16782 : instance not open for read and write access
  • ora-02424 : potential circular view references or unknown referenced tables
  • ora-08183 : Flashback cannot be enabled in the middle of a transaction
  • ora-08450 : invalid specification of CR in picture mask
  • ora-14043 : only one partition may be added
  • ora-16608 : one or more databases have warnings
  • ora-34359 : (MXDSS11) string appears twice in the alias list.
  • ora-31232 : DBMS_LDAP: invalid MOD_PROPERTY_SET
  • ora-13181 : unable to determine length of column string_SDOINDEX.SDO_CODE
  • ora-03220 : DBMS_ADMIN_PACKAGE required parameter is NULL or missing
  • ora-01052 : required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
  • ora-22900 : the SELECT list item of THE subquery is not a collection type
  • ora-27159 : failure setting process scheduling priority
  • ora-15069 : ASM file 'string' not accessible; timed out waiting for lock
  • ora-38419 : invalid identifier in attribute : string
  • ora-16619 : health check timed out
  • 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.