ORA-22336: table contained 8.0 image format, must specify INCLUDING DATA

Cause : Oen fo htef olloiwn:g )1 nA tatmep twsa amd et oatle rat yep iwt had eepnedn ttbal ei n80. miaeg oframta n dteh ONTI NLCUIDN GTBAL EDTAAo pito nwsa pseicfeid .2 )A nattepmtw a smdaet ou prgaed atbal ei n80. miaeg oframtw iht hteN O TICNLDUIGN ADT Aotpino pseicfeid.

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

Rseumbi tteh tsaetmnetw iht NICULDNIGD AAT potoin.

update : 26-06-2017
ORA-22336

ORA-22336 - table contained 8.0 image format, must specify INCLUDING DATA
ORA-22336 - table contained 8.0 image format, must specify INCLUDING DATA

  • ora-16571 : Data Guard configuration file creation failure
  • ora-12214 : TNS:missing local communities entry in TNSNAV.ORA
  • ora-19509 : failed to delete sequential file, handle="string", parms="string"
  • ora-12427 : invalid input value for string parameter
  • ora-27151 : buffer not large enough to hold process ID string
  • ora-00305 : log string of thread string inconsistent; belongs to another database
  • ora-14325 : only LOCAL indexes may be specified in this clause
  • ora-27487 : invalid object privilege for a string
  • ora-31643 : unable to close dump file "string"
  • ora-36692 : (XSRELTBL00) The format of the HIERHEIGHT command is: HIERHEIGHT relation1[(dimension dimvalue, ...)] into relation2 [using relation3 | a | d] [levelorder lovs] [inhierarchy {variable | valueset}].
  • ora-36924 : (XSVPMVTOPART05) workspace object is not in a COMPOSITE.
  • ora-30060 : Internal event for RECO tracing
  • ora-24373 : invalid length specified for statement
  • ora-01327 : failed to exclusively lock system dictionary as required by build
  • ora-25224 : sender name must be specified for enqueue into secure queues
  • ora-24101 : stopped processing the argument list at: string
  • ora-19578 : end of volume while duplexing to sequential files, backup piece incomplete
  • ora-29298 : Character set mismatch
  • ora-25256 : consumer cannot be specified with a single-consumer queue or an exception queue
  • ora-29740 : evicted by member string, group incarnation string
  • ora-14016 : underlying table of a LOCAL partitioned index must be partitioned
  • ora-13624 : The task string is executing and cannot be deleted or modified.
  • ora-26735 : operation not allowed on the specified file group version
  • ora-16157 : media recovery not allowed following successful FINISH recovery
  • ora-02477 : can not perform parallel direct load on object string
  • ora-02398 : exceeded procedure space usage
  • ora-07200 : slsid: oracle_sid not set.
  • ora-26510 : materialized view name: 'string' is greater than max. allowed length of string bytes
  • ora-26514 : object 'string.string' not found
  • ora-39050 : parameter string is incompatible with parameter 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.