ORA-07449: sc: usnewlock failed.

Cause : Oracle failed to acquire a shared arena lock.

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

Check result code in sercerrno to determine the cause of failure.

update : 27-04-2017

ORA-07449 - sc: usnewlock failed.
ORA-07449 - sc: usnewlock failed.

  • ora-30024 : Invalid specification for CREATE UNDO TABLESPACE
  • ora-38786 : Flash recovery area is not enabled.
  • ora-36912 : (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace object cannot be simultaneous.
  • ora-22872 : OID INDEX clause not allowed on tables with primary key based object identifiers
  • ora-22629 : OCIAnyData is null
  • ora-01571 : redo version string incompatible with ORACLE version string
  • ora-32511 : cannot create watchpoint in memory needed by watchpointing code
  • ora-19661 : datafile string could not be verified
  • ora-23379 : connection qualifier "string" is too long
  • ora-31227 : DBMS_LDAP: invalid LDAP MESSAGE handle
  • ora-19910 : can not change recovery target incarnation in control file
  • ora-12734 : Instant Client Light: unsupported client national character set string
  • ora-00133 : value of string is too long
  • ora-21300 : objects option not installed
  • ora-02239 : there are objects which reference this sequence
  • ora-07256 : sptrap: cannot set up signal handler to catch exceptions.
  • ora-02805 : Unable to set handler for SIGTPA
  • ora-39201 : Dump files are not supported for estimate only jobs.
  • ora-24759 : invalid transaction start flags
  • ora-01345 : must be a LogMiner coordinator process
  • ora-24330 : internal OCI error
  • ora-23418 : cannot unregister the propagator who is currently in use
  • ora-19118 : duplicate default namespace definition - string
  • ora-13773 : insufficient privileges to select data from the cursor cache
  • ora-07562 : sldext: extension must be 3 characters
  • ora-30359 : Query rewrite is not supported on SYS materialized views
  • ora-39149 : cannot link privileged user to non-privileged user
  • ora-01653 : unable to extend table string.string by string in tablespace string
  • ora-24096 : invalid message state specified
  • ora-12705 : Cannot access NLS data files or invalid environment specified
  • 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.