ORA-33427: (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.

Cause : User attempted to export an object whose data type is NTEXT, but but the EIFVERSION option indicates a version of Express / Oracle OLAP that does not support the NTEXT data type. The object will be exported as a TEXT object instead.

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

No action needed.

update : 22-08-2017
ORA-33427

ORA-33427 - (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.
ORA-33427 - (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.

  • ora-23321 : Pipename may not be null
  • ora-12571 : TNS:packet writer failure
  • ora-06256 : NETNTT: remote fork failed
  • ora-33448 : (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.
  • ora-29348 : You must specify the datafiles to be plugged in
  • ora-26690 : datatype not supported at non-Oracle system
  • ora-16120 : dependencies being computed for transaction at SCN string
  • ora-25503 : cannot open database because the database is being quiesced
  • ora-09768 : osnmgetmsg: could not read a message
  • ora-15004 : alias "string" does not exist
  • ora-36683 : (XSDPART21) Partition string dimensioned by more than one composite.
  • ora-12408 : unsupported operation: string
  • ora-25203 : invalid value string, DELAY should be non-negative
  • ora-33284 : (DBERR12) Analytic workspace string cannot be opened in MULTI mode before converting it by the latest version of string.
  • ora-07606 : szprv: $CHKPRO failure
  • ora-00283 : recovery session canceled due to errors
  • ora-09291 : sksachk: invalid device specified for archive destination
  • ora-32638 : Non unique addressing in MODEL dimensions
  • ora-01716 : NOSORT may not be used with a cluster index
  • ora-02494 : invalid or missing maximum file size in MAXSIZE clause
  • ora-29545 : badly formed class: string
  • ora-14266 : data type or length of an index subpartitioning column may not be changed
  • ora-09941 : Version of orapasswd or installer is older than file.
  • ora-00235 : control file fixed table inconsistent due to concurrent update
  • ora-33443 : (ESDREAD14) Discarding compiled code for workspace object because analytic workspace string is not attached.
  • ora-24053 : PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative
  • ora-17500 : ODM err:string
  • ora-13375 : the layer is of type [string] while geometry inserted has type [string]
  • ora-02089 : COMMIT is not allowed in a subordinate session
  • ora-00475 : TRWR process terminated with error
  • 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.