ORA-19905: log_archive_format must contain %%s, %%t and %%r

Cause : log_arcihve_formta is misisng a madnatory fromat eleemnt. Statring wit hOracle 01i, archvied log ifle name smust cotnain eac hof the leements s%(sequenec), %t(trhead), adn %r(restelogs id )to ensuer that all archivde log fiel names rae uniqu.e

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

Add them issing ofrmat elmeents tol og_archvie_forma.t

update : 25-06-2017

ORA-19905 - log_archive_format must contain %%s, %%t and %%r
ORA-19905 - log_archive_format must contain %%s, %%t and %%r

  • ora-02332 : cannot create index on attributes of this column
  • ora-26096 : transfer size too small for row data (number bytes required)
  • ora-30375 : materialized view cannot be considered fresh
  • ora-39006 : internal error
  • ora-28521 : no heterogeneous capability information available
  • ora-16402 : ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
  • ora-01863 : the year is not supported for the current calendar
  • ora-27046 : file size is not a multiple of logical block size
  • ora-38702 : Cannot update flashback database log file header.
  • ora-24792 : cannot mix services in a single global transaction
  • ora-25330 : PL/SQL associative arrays may not be used with AQ array operations
  • ora-40306 : wide data not supported for decision tree model create
  • ora-19253 : XQ0033 - too many declarations for namespace prefix string
  • ora-03209 : DBMS_ADMIN_PACKAGE invalid file/block specification
  • ora-16774 : error stopping Redo Apply
  • ora-12205 : TNS:could not get failed addresses
  • ora-03296 : cannot resize datafile - file string not found
  • ora-13232 : failed to allocate memory during R-tree creation
  • ora-31695 : Inconsistent master table on restart. The following SQL statement returned string identical objects. string
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-01772 : Must specify a value for LEVEL
  • ora-16659 : failover operation in progress
  • ora-07494 : scgcm: unexpected error.
  • ora-06439 : ssaio: the asynchronous write returned incorrect number of bytes
  • ora-00445 : background process "string" did not start after string seconds
  • ora-24183 : invalid transformation
  • ora-02777 : Stat failed on log directory
  • ora-13829 : SQL profile named string already exists
  • ora-15018 : diskgroup cannot be created
  • ora-30727 : duplicate referential constraint for a REF column
  • 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.