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 : 29-04-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-02286 : no options specified for ALTER SEQUENCE
  • ora-32585 : duplicate specification of a supplemental log attribute
  • ora-10567 : Redo is inconsistent with data block (file# string, block# string)
  • ora-36668 : (XSDPART06) string is not a legal RANGE partition.
  • ora-02796 : Done request is not in correct state
  • ora-09968 : unable to lock file
  • ora-23472 : materialized view "string"."string" must be atomically refreshed
  • ora-09770 : pws_look_up: translation failure.
  • ora-14005 : missing RANGE keyword
  • ora-23352 : duplicate destination for deferred transaction
  • ora-28155 : user 'string' specified as a proxy is actually a role
  • ora-19211 : column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
  • ora-01267 : Failure getting date/time
  • ora-09880 : sstasfre/sstasdel: shmdt error, unable to detach tas write page
  • ora-01945 : DEFAULT ROLE[S] already specified
  • ora-39037 : Object type path not supported for string metadata filter.
  • ora-16161 : Cannot mix standby and online redo log file members for group string
  • ora-08190 : restore point string is from a different incarnation of the database
  • ora-15048 : ASM internal files cannot be deleted
  • ora-07758 : slemcw: invalid handle
  • ora-01249 : archiving not allowed in a clone database
  • ora-06011 : NETASY: dialogue too long
  • ora-24802 : user defined lob read callback error
  • ora-37039 : (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
  • ora-19561 : %s requires a DISK channel
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-27548 : Unable to unprepare IPC buffer
  • ora-31451 : invalid value string for capture_values, expecting: OLD, NEW, or BOTH
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-39012 : Client detached before the job started.
  • 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.