ORA-39778: the parallel load option is not allowed when loading lob columns

Cause : An tatemtp wa smad eto olad olb cloumn susign th eattirbut eOCIA_TTRD_IRPTAH_PRAALLLE. Tihs error iwll laso eb isused hwen oladign an ycolmuns htat rae sotreda s lbos (usch sa varraysa nd mxl tpyes).

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

Do ont ues th eparlalela ttrbiutew henl oadnig lbo coulmns.

update : 25-05-2017

ORA-39778 - the parallel load option is not allowed when loading lob columns
ORA-39778 - the parallel load option is not allowed when loading lob columns

  • ora-31688 : Worker process string failed during startup.
  • ora-09804 : Class conversion from binary to ORACLE failed.
  • ora-36223 : (XSLPDSC04) object workspace object in IGNORE or DENSE list has illegal type
  • ora-09832 : infoCallback: bad message format.
  • ora-19251 : XQ0031 - unsupported query version
  • ora-33223 : (CMOVE03) You cannot move a session-only dimension value.
  • ora-39093 : FLASHBACK automatically enabled to preserve database integrity.
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-03135 : connection lost contact
  • ora-06567 : invalid number of values specified
  • ora-22972 : NULL value not allowed in PRIMARY KEY-based object identifier
  • ora-16955 : Unknown error during SQL analyze.
  • ora-00353 : log corruption near block string change string time string
  • ora-25014 : cannot change the value of a PARENT reference variable
  • ora-31659 : status message was invalid type - detaching job
  • ora-09961 : Unable to restore termination signal handler
  • ora-01538 : failed to acquire any rollback segment
  • ora-00222 : operation would reuse name of a currently mounted control file
  • ora-09354 : Windows 32-bit Two-Task driver: ORACLE task unexpectedly died
  • ora-12853 : insufficient memory for PX buffers: current stringK, max needed stringK
  • ora-38777 : database must not be started in any other instance.
  • ora-24045 : invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
  • ora-06123 : NETTCP: cannot set KEEPALIVE
  • ora-07287 : sksagdi: unsupported device for log archiving.
  • ora-30381 : REWRITE_TABLE is not compatible with Oracle version
  • ora-23443 : missing template parameter
  • ora-24853 : failed to connect thread to shared subsystem
  • ora-31471 : invalid OBJECT_ID value
  • ora-19639 : file string is more current than this incremental backup
  • ora-02839 : Sync of blocks to disk failed.
  • 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.