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 : 29-04-2017

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-16172 : archive logs detected beyond Terminal End-Of-Redo
  • ora-30104 : 'string' is not a legal integer for 'string'
  • ora-30078 : partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals
  • ora-02140 : invalid tablespace name
  • ora-00163 : internal database name length string is greater than maximum (string)
  • ora-30084 : invalid data type for datetime primary with time zone modifier
  • ora-03214 : File Size specified is smaller than minimum required
  • ora-16659 : failover operation in progress
  • ora-37138 : (XSCCOMP13) You cannot delete values from workspace object because it is an aggregated COMPRESSED COMPOSITE.
  • ora-36999 : (XSRELGID16) OBJECT workspace object is not a surrogate dimension, a source relation must be specified when creating any non-surrogate grouping id.
  • ora-15019 : discovered duplicate path 'string' for 'string'
  • ora-23358 : invalid remote user
  • ora-22289 : cannot perform string operation on an unopened file or LOB
  • ora-09202 : sfifi: error identifying file
  • ora-02194 : event specification syntax error string (minor error string) near 'string'
  • ora-07850 : sllfop: bad option
  • ora-01505 : error in adding log files
  • ora-24029 : operation not allowed on a single-consumer queue
  • ora-07408 : slbtpd: overflow while converting to packed decimal.
  • ora-00067 : invalid value string for parameter string; must be at least string
  • ora-24150 : evaluation context string.string does not exist
  • ora-30505 : system triggers should not reference a column in a WHEN clause
  • ora-27300 : OS system dependent operation:string failed with status: string
  • ora-02426 : privilege grant failed
  • ora-02815 : Unable to attach shared memory
  • ora-28665 : table and partition must have same compression attribute
  • ora-22140 : given size [string] must be in the range of 0 to [string]
  • ora-31104 : Cannot find lock with token "string" on "string" for unlock
  • ora-07270 : spalck: setitimer error, unable to set interval timer.
  • ora-13830 : SQL profile with category string already exists for this SQL statement
  • 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.