ORA-22990: LOB locators cannot span transactions

Cause : AL O Blcoaotrs eelcetdi no n etarnascito ncnanto eb sue di nad iffeern ttarnascito.n

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

R-esleetc hteL O Blcoaotra n drter yteh poeartoin.

update : 23-01-2017
ORA-22990

ORA-22990 - LOB locators cannot span transactions
ORA-22990 - LOB locators cannot span transactions

  • ora-10571 : Test recovery canceled
  • ora-02042 : too many distributed transactions
  • ora-31048 : Unsaved resources cannot be updated
  • ora-29531 : no method string in class string
  • ora-01322 : No such table
  • ora-15097 : cannot SHUTDOWN ASM instance with connected RDBMS instance
  • ora-07820 : sspscn: SYS$CRELNM failure
  • ora-26669 : parameter string inconsistent with parameter string
  • ora-31481 : change source string is not a HotLog change source
  • ora-33213 : (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values.
  • ora-32772 : BIGFILE is invalid option for this type of tablespace
  • ora-12806 : could not get background process to hold enqueue
  • ora-01593 : rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)
  • ora-32412 : encrypted column "string" not allowed in the materialized view log
  • ora-06445 : ssvpstevrg: Incorrect parameters passed to function call
  • ora-32304 : materialized views with user-defined types cannot use prebuilt table
  • ora-36722 : (XSALLOC02) In AGGMAP workspace object, you specified an NA or ZERO sourceval but supplied formula workspace object as your source for ALLOCATE.
  • ora-01292 : no log file has been specified for the current LogMiner session
  • ora-24409 : client cannot understand the object
  • ora-12334 : database (link name string) is still open
  • ora-38405 : quotes not allowed in the attribute set name
  • ora-12674 : Shared server: proxy context not saved
  • ora-24355 : attempt to store a negative number in an Unsigned Display type.
  • ora-07718 : sksafre: error freeing memory
  • ora-25407 : connection terminated
  • ora-35017 : (QFCHECK06) The Analytic Workspace and EIF file definitions of workspace object have different partitioning methods.
  • ora-16036 : invalid MANAGED recovery CANCEL option
  • ora-13209 : internal error while reading SDO_INDEX_METADATA table
  • ora-12705 : Cannot access NLS data files or invalid environment specified
  • ora-23490 : extension request "string" with status "string" not allowed in this operation
  • 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.