ORA-19688: control file autobackup format(string) for string does not have %F

Cause : control file autobackup format must contain %F for the device.

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

Change control file format using RMAN command CONGIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE TO .

update : 25-04-2017
ORA-19688

ORA-19688 - control file autobackup format(string) for string does not have %F
ORA-19688 - control file autobackup format(string) for string does not have %F

  • ora-39137 : cannot specify a TABLE_EXISTS_ACTION of string for a job with no metadata
  • ora-28182 : cannot acquire Kerberos service ticket for client
  • ora-16029 : cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations
  • ora-31105 : User does not own lock "string"
  • ora-31041 : Property string: Memory type (string) not compatible with database type (string)
  • ora-13123 : invalid name specified
  • ora-06709 : TLI Driver: message send failure
  • ora-09929 : GLB of two labels is invalid
  • ora-14507 : partition corrupt. all rows do not fall within partition bounds
  • ora-36964 : (XSRELTBL09) workspace object is not a valid level relation.
  • ora-03209 : DBMS_ADMIN_PACKAGE invalid file/block specification
  • ora-01636 : rollback segment 'string' is already online
  • ora-31213 : DBMS_LDAP: PL/SQL - Invalid LDAP mod option.
  • ora-14048 : a partition maintenance operation may not be combined with other operations
  • ora-28232 : invalid input length for obfuscation toolkit
  • ora-09300 : osncon: unable to connect, DPMI not available
  • ora-13237 : internal error during R-tree concurrent updates: [string]
  • ora-16113 : applying change to table or sequence string
  • ora-01213 : MAXINSTANCES may not exceed string
  • ora-16186 : Modifying LOG_ARCHIVE_CONFIG requires SID='*' qualifier
  • ora-04064 : not executed, invalidated string
  • ora-21706 : duration does not exist or is invalid
  • ora-30991 : cannot use DOM to add special attribute to schema-based parent
  • ora-34344 : (MXDSS03) Analytic workspace string is not attached.
  • ora-04067 : not executed, string does not exist
  • ora-07224 : sfnfy: failed to obtain file size limit; errno = string.
  • ora-07514 : scgcan: $deq unexpected return while canceling lock
  • ora-30132 : invalid key index supplied
  • ora-01350 : must specify a tablespace name
  • ora-23402 : refresh was aborted because of conflicts caused by deferred txns
  • 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.