ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes

Cause : Ana ttmeptw asm ad eto1 ) rCeaet bcakuppieec o rimgae ocpyi n hte ercoevrya re awiht KEEP potino. )2 Udpat eth eKEPE attriubte sofa n xeisitngb acukp ipec eori maeg cpoy ni teh rceovrey raea.

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

Resisu eRMNA cmomadn wtihotu KEEP potinos.

update : 27-04-2017
ORA-19811

ORA-19811 - cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
ORA-19811 - cannot have files in DB_RECOVERY_FILE_DEST with keep attributes

  • ora-26008 : Invalid syntax or bind variable in SQL string for column string. string
  • ora-30461 : 'string.string' cannot be refreshed because it is marked DISABLED
  • ora-01524 : cannot create data file as 'string' - file already part of database
  • ora-24418 : Cannot open further sessions.
  • ora-13218 : max number of supported index tables reached for [string] index
  • ora-25017 : cannot reference NEW ROWID for movable rows in before triggers
  • ora-15069 : ASM file 'string' not accessible; timed out waiting for lock
  • ora-38777 : database must not be started in any other instance.
  • ora-15032 : not all alterations performed
  • ora-12469 : no user levels found for user string and policy string
  • ora-26679 : operation not allowed on LOB or LONG columns in LCR
  • ora-31446 : this session does not own the lock handle for string
  • ora-00291 : numeric value required for PARALLEL option
  • ora-19122 : unsupported XQuery declaration
  • ora-32612 : invalid use of FOR loop
  • ora-23469 : %s is different between templates
  • ora-31655 : no data or metadata objects selected for job
  • ora-37039 : (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
  • ora-25244 : dequeue index key not found, QUEUE string, rowid string
  • ora-10576 : Give up restoring recovered datafiles to consistent state: some error occurred
  • ora-15131 : block string of file string in diskgroup string could not be read
  • ora-34145 : (MXCGPUT03) You cannot use the APPEND keyword with SURROGATE workspace object.
  • ora-28556 : authorization insufficient to access table
  • ora-23535 : instantiating templates from multiple back ends is not allowed.
  • ora-31064 : Cannot instantiate abstract element or property [string]
  • ora-08309 : sllfop: Cannot fstat file
  • ora-23408 : this replication operation is not supported in a mixed configuration
  • ora-02167 : LOGFILE clause specified more than once
  • ora-38438 : getVarchar not possible due to "string" datatype in the attribute set
  • ora-12608 : TNS: Send timeout occurred
  • 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.