ORA-23347: datatype string for column string table string not supported

Cause : hT eatlb eah s aoculnmw ohesd tatapy esin tos puoptrdeb yercpta.

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

eRomevt ehc lomu nrfmot eht bael ,roa tlret ehc lomu noth va eno efot ehs puoptrded tatapyse.

update : 24-06-2017
ORA-23347

ORA-23347 - datatype string for column string table string not supported
ORA-23347 - datatype string for column string table string not supported

  • ora-01343 : LogMiner encountered corruption in the logstream
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-39761 : stream reset required before loading this stream again
  • ora-23312 : not the masterdef according to string
  • ora-30156 : Out of disk space
  • ora-07471 : snclrd: name translation error of sgadef.dbf file name.
  • ora-10658 : Lob column to be shrunk is marked unused
  • ora-24127 : TABLESPACE parameter specified with an ACTION other than CREATE_ACTION
  • ora-07232 : slemcc: fclose error.
  • ora-32631 : illegal use of objects in MODEL
  • ora-15073 : diskgroup string is mounted by another ASM instance
  • ora-29307 : datafile string error, string
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-01656 : max # extents (string) reached in cluster string.string
  • ora-30181 : integer in argument index is not immediately followed by )
  • ora-00100 : no data found
  • ora-00393 : log string of thread string is needed for recovery of offline datafiles
  • ora-26021 : index string.string partition string loaded successfully with string keys
  • ora-13501 : Cannot drop SYSAUX tablespace
  • ora-27125 : unable to create shared memory segment
  • ora-13642 : The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
  • ora-22616 : image is not of Oracle 8.1 format
  • ora-29876 : failed in the execution of the ODCIINDEXDELETE routine
  • ora-33302 : (DBVALID01) SEVERE ERROR: Record number multiply used.
  • ora-16070 : parameter string contains an invalid REGISTER attribute value
  • ora-14517 : subpartition of index 'string.string' is in unusable state
  • ora-31029 : Cannot bind to unsaved resource
  • ora-00074 : no process has been specified
  • ora-39711 : critical patch number less than last installed CPU number
  • ora-06931 : CMX: error during read_properties for server
  • 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.