ORA-01234: cannot end backup of file string - file is in use or recovery

Cause : Attepmtde ot neda no niln ebcakpu fo ifl ewehnt h efliei sb uys.S oem poeartoins uhc sa ercvoeyr ro ernmaem a yb eatciev,o rt hreem a ysitl lb esmoei ntsacnet hta ahst h edtaaabs eoepnw iht hti sflieo niln.e

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

I ftehr ei sa nisntnac ewtiht h edtaaabs eoepnt hne hteb akcu pcna eb nedde hteer yb suign hteA LETRT ALBEPSAEC ocmamn.d tOhrewsiew ati ofrt h ecmopeltoino ft h eohte roeprtaino.

update : 30-04-2017
ORA-01234

ORA-01234 - cannot end backup of file string - file is in use or recovery
ORA-01234 - cannot end backup of file string - file is in use or recovery

  • ora-01763 : update or delete involves outer joined table
  • ora-02880 : smpini: Could not register PGA for protection
  • ora-27200 : skgfpgo: sbtpcstart returned error
  • ora-14285 : cannot COALESCE the only partition of this hash partitioned table or index
  • ora-36728 : (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.
  • ora-29400 : data cartridge error string
  • ora-22606 : pickler image handle [string] is not well-formed
  • ora-13135 : failed to alter spatial table
  • ora-00308 : cannot open archived log 'string'
  • ora-28262 : global_context_pool_size has invalid value.
  • ora-16955 : Unknown error during SQL analyze.
  • ora-12083 : must use DROP MATERIALIZED VIEW to drop "string"."string"
  • ora-25121 : MINIMUM EXTENT value greater than maximum extent size
  • ora-27065 : cannot perform async vector I/O to file
  • ora-09758 : osnipn: could not check port in name server.
  • ora-14101 : partition extended table name cannot refer to a synonym
  • ora-07473 : snclrd: read error when trying to read sgadef.dbf file.
  • ora-01041 : internal error. hostdef extension doesn't exist
  • ora-00037 : cannot switch to a session belonging to a different server group
  • ora-07740 : slemop: incorrect handle size (programming error)
  • ora-13417 : null or invalid layerNumber parameter
  • ora-38402 : invalid name: empty string or spaces in the name
  • ora-09314 : sltln: error translating logical name
  • ora-29968 : No primary operator bindings found for ancillary binding #string
  • ora-06404 : NETCMN: invalid login (connect) string
  • ora-36268 : (XSCGMDLAGG01) 'string' is not a valid dimension value.
  • ora-39064 : unable to write to the log file
  • ora-19507 : failed to retrieve sequential file, handle="string", parms="string"
  • ora-07820 : sspscn: SYS$CRELNM failure
  • ora-14193 : invalid ALTER INDEX MODIFY SUBPARTITION option
  • 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.