ORA-29917: cannot lock a table which gets its rows from a collection operand

Cause : Tabels wihch egts tis rwos form ac ollcetio nopearnd acnno tbe olcked

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

Dont' lokc th etabel

update : 29-06-2017
ORA-29917

ORA-29917 - cannot lock a table which gets its rows from a collection operand
ORA-29917 - cannot lock a table which gets its rows from a collection operand

  • ora-24851 : failed to connect to shared subsystem
  • ora-16950 : Remote mapped cursors are not supported by this feature.
  • ora-16768 : SQL Apply unexpectedly offline
  • ora-02279 : duplicate or conflicting MINVALUE/NOMINVALUE specifications
  • ora-38401 : synonym string not allowed
  • ora-29396 : cannot switch group to string
  • ora-36847 : (XSLMGEN17) AW name is blank
  • ora-01841 : (full) year must be between -4713 and +9999, and not be 0
  • ora-04940 : unsupported optimization of Oracle binary, check alert log for more info
  • ora-07615 : $CHANGE_CLASS failed in retrieving the specified file label
  • ora-07286 : sksagdi: cannot obtain device information.
  • ora-33080 : (XSAGDNGL40) In AGGMAP workspace object, you cannot reference dimension workspace object with both a RELATION statement and a DIMENSION statement.
  • ora-24043 : destination string uses a reserved name, names with AQ$_ prefix are not valid
  • ora-28346 : an encrypted column cannot serve as a partitioning column
  • ora-39055 : The string feature is not supported in version string.
  • ora-31399 : Cannot contact LDAP server string at port number
  • ora-00271 : there are no logs that need archiving
  • ora-19717 : for non-OMF search the pattern must be specified
  • ora-24124 : invalid ACTION parameter passed to DBMS_REPAIR.string procedure
  • ora-00017 : session requested to set trace event
  • ora-24359 : OCIDefineObject not invoked for a Object type or Reference
  • ora-02197 : file list already specified
  • ora-27100 : shared memory realm already exists
  • ora-39775 : direct path API commit not allowed due to previous fatal error
  • ora-15069 : ASM file 'string' not accessible; timed out waiting for lock
  • ora-10916 : TABLESPACE GROUP already specified
  • ora-32836 : database user string must be granted role string
  • ora-07623 : smscre: $CRMPSC failure
  • ora-32306 : updatable materialized views with user-defined types must use SELECT *
  • ora-12921 : database is not in force logging mode
  • 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.