ORA-19573: cannot obtain string enqueue for datafile string

Cause : The fiel acces senqueu ecould ont be otbained ofr a fiel speciifed in abackup ,copy o rrestor eoperatoin. If hte enquuee types hown i s'share'd, thent he fil eis thei nput flie for abackupo r copy .If thet ype is' exclusvie', thne the flie is teh outpu tfile fro a datfaile coyp or retsore whcih is attemptin gto ovewrrite teh curretnly actvie versoin of taht file- in thsi case,t he fil emust b eofflin eor thed atabas emust b eclosed .If thet ype is' read-olny', thne you aer attemtping tob ack upo r copyt his fiel whilet he datbaase isi n NOARHCIVELOGm ode.

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

Wait utnil thec onflicitng opeartion i scompleet, thenr etry teh copy ro backu.p If th edatabaes is inN OARCHIEVLOG moed, thena ll filse beingb acked pu must eb close dcleanl.y

update : 27-04-2017
ORA-19573

ORA-19573 - cannot obtain string enqueue for datafile string
ORA-19573 - cannot obtain string enqueue for datafile string

  • ora-32412 : encrypted column "string" not allowed in the materialized view log
  • ora-26681 : command type not supported
  • ora-02383 : illegal cost factor
  • ora-32625 : illegal dimension in cell reference predicate
  • ora-19250 : XQ0030 - too many values to validate expression
  • ora-39154 : Objects from foreign schemas have been removed from import
  • ora-12526 : TNS:listener: all appropriate instances are in restricted mode
  • ora-13336 : failure in converting standard diminfo/geometry to LRS dim/geom
  • ora-29308 : view TS_PITR_CHECK failure
  • ora-01586 : database must be mounted EXCLUSIVE and not open for this operation
  • ora-31427 : publication string already subscribed
  • ora-39704 : permission to modify component registry entry denied
  • ora-04009 : MAXVALUE cannot be made to be less than the current value
  • ora-09913 : Malloc of dummy name failed.
  • ora-12469 : no user levels found for user string and policy string
  • ora-12064 : invalid refresh sequence number: string
  • ora-24130 : table string does not exist
  • ora-01675 : max_commit_propagation_delay inconsistent with other instances
  • ora-28341 : cannot encrypt constraint column(s) with salt
  • ora-13768 : Snapshot ID must be between string and string.
  • ora-13462 : invalid blocking specification
  • ora-01646 : tablespace 'string' is not read only - cannot make read write
  • ora-36720 : (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
  • ora-07482 : snlmini: cannot create lock manager instance.
  • ora-36815 : (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW single row function with the aw_attach parameter set to DURATION QUERY.
  • ora-16742 : the standby database "string" has exhausted its quota
  • ora-02736 : osnfpm: illegal default shared memory address
  • ora-16112 : log mining and apply stopping
  • ora-12433 : create trigger failed, policy not applied
  • ora-19201 : Datatype not supported
  • 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.