ORA-19716: error processing format string to generate name for backup

Cause : Therew ere errors wihle prcoessin gthe fromat t ogenertae nam efor bcakup.

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

Chang ethe fromat.

update : 28-04-2017
ORA-19716

ORA-19716 - error processing format string to generate name for backup
ORA-19716 - error processing format string to generate name for backup

  • ora-01757 : Must specify an object number
  • ora-30744 : "string" is not an object table
  • ora-01633 : Real Application Clusters Option needed for this operation
  • ora-36886 : (XSSRF05) Error rewritting OLAP DML expression. Rewritten expression is greater than number bytes
  • ora-39502 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-28544 : connect to agent failed, probable Net8 administration error
  • ora-07261 : spdde: kill error, unable to send signal to process.
  • ora-30768 : Cannot evaluate pipelined function
  • ora-32588 : supplemental logging attribute string exists
  • ora-40286 : remote operations not permitted on mining models
  • ora-23342 : invalid parameter column string
  • ora-16011 : Archivelog Remote File Server process in Error state
  • ora-02733 : osnsnf: database string too long
  • ora-02465 : Inappropriate use of the HASH IS option
  • ora-02455 : The number of cluster key column must be 1
  • ora-13389 : unable to compute buffers or intersections in analysis function
  • ora-07803 : slpdtb: invalid packed decimal nibble
  • ora-16809 : multiple warnings detected for the database
  • ora-02773 : Invalid maximum client wait time
  • ora-39143 : dump file "string" may be an original export dump file
  • ora-02051 : another session in same transaction failed
  • ora-36966 : (XSRELTBL10) workspace object must be a dimension.
  • ora-12589 : TNS:connection not bequeathable
  • ora-06756 : TLI Driver: cannot open oratab
  • ora-16631 : operation requires shutdown of database/instance "string"
  • ora-07713 : sksamtd: could not mount archival device (SYS$MOUNT failure)
  • ora-37143 : (XSSQLMDQ03) string is not a valid analytic workspace name.
  • ora-39056 : invalid log file specification.
  • ora-16587 : ambiguous object specified to Data Guard broker
  • ora-01940 : cannot drop a user that is currently connected
  • 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.