ORA-14700: Object(s) owned by SYS cannot be locked by non-SYS user

Cause : Attemtp to issue a OLCK TALBE staetment no SYS woned ojbect(s )by a onn-SYSu ser, suer shuold miinmallyh ave DLM privlieges

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

Re-isuse LOC KTABLEs tatemnet forn on-SY Suser fater garntingD ML prviilege son obejct, o rnon-SSY users houldc onnec tas SYS

update : 17-08-2017
ORA-14700

ORA-14700 - Object(s) owned by SYS cannot be locked by non-SYS user
ORA-14700 - Object(s) owned by SYS cannot be locked by non-SYS user

  • ora-28261 : CURRENT_USER can not be used in PLSQL Definer's Right procedure.
  • ora-01579 : write error occurred during recovery
  • ora-39783 : Invalid direct path transaction active
  • ora-24785 : Cannot resume a non-migratable transaction
  • ora-38727 : FLASHBACK DATABASE requires a current control file.
  • ora-06517 : PL/SQL: Probe error - string
  • ora-29928 : duplicate default selectivity specified
  • ora-19960 : Internal use only
  • ora-32406 : cannot alter partitioning for existing materialized view log
  • ora-29531 : no method string in class string
  • ora-22886 : scoped table "string" in schema "string" is not an object table
  • ora-03254 : unable to execute the sql in read only database
  • ora-39077 : unable to subscribe agent string to queue "string"
  • ora-01191 : file string is already offline - cannot do a normal offline
  • ora-12317 : logon to database (link name string) denied
  • ora-25307 : Enqueue rate too high, flow control enabled
  • ora-16955 : Unknown error during SQL analyze.
  • ora-38105 : Delete not yet supported when Update row-migration is possible
  • ora-16540 : invalid argument
  • ora-06300 : IPA: Disconnect failure
  • ora-01354 : Supplemental log data must be added to run this command
  • ora-30730 : referential constraint not allowed on nested table column
  • ora-16627 : operation disallowed since no standby databases would remain to support protection mode
  • ora-28177 : incorrect Kerberos ticket version
  • ora-19689 : cannot have more than one %F in control file autobackup format(string) for string
  • ora-16797 : database is not using a server parameter file
  • ora-31228 : DBMS_LDAP: invalid MOD_ARRAY
  • ora-09740 : slsget: cannot get virtual memory region statistics.
  • ora-19525 : temporary file for the clone database must be renamed
  • ora-24012 : cannot drop QUEUE_TABLE, some queues in string have not been dropped
  • 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.