ORA-19555: invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value

Cause : The vaule of praameterL OG_ARCIHVE_MINS_UCCEEDD_EST wa snot se twithint he valdi range.

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

Specif ya corrcet valu efor paarmeter OLG_ARCHVIE_MIN_USCCEED_EDST. Ift he arcihve logp arametres LOG_RACHIVE_EDST or OLG_ARCHVIE_DUPLXE_DEST rae in ues, set apramete rLOG_ARHCIVE_MI_NSUCCEE_DDEST t oeither1 or 2.

update : 27-04-2017

ORA-19555 - invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
ORA-19555 - invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value

  • ora-28054 : the password has expired. string Grace logins are left
  • ora-00325 : archived log for thread string, wrong thread # string in header
  • ora-28518 : data dictionary translation has illegal translation type
  • ora-12077 : temporary updatable materialized view log does not exist
  • ora-31168 : Node localname and namespace values should be less than 64K
  • ora-00104 : deadlock detected; all public servers blocked waiting for resources
  • ora-39014 : One or more workers have prematurely exited.
  • ora-01296 : character set mismatch between dictionary string and logfiles
  • ora-14057 : partition "string": sum of PCTUSED and PCTFREE may not exceed 100
  • ora-12171 : TNS:could not resolve connect identifier: string
  • ora-28022 : cannot grant external roles to global user or role
  • ora-38959 : Failed to update block 0 to new version 10 format
  • ora-00082 : memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring
  • ora-29539 : Java system classes already installed
  • ora-16559 : out of memory at string
  • ora-38733 : Physical size string less than needed string.
  • ora-32345 : fail to refresh the materialized view string.string due to the changed synonym
  • ora-38718 : Invalid thread number specified in the DUMP FLASHBACK command.
  • ora-01306 : dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
  • ora-22850 : duplicate LOB storage option specificed
  • ora-38707 : Media recovery is not enabled.
  • ora-06124 : NETTCP: timeout waiting for ORASRV
  • ora-09363 : Windows 3.1 Two-Task driver invalid context area
  • ora-16191 : Primary log shipping client not logged on standby
  • ora-23383 : registration for materialized view repgroup "string"."string" failed at site string
  • ora-29508 : query derived from USING clause did not select a value of type string
  • ora-01181 : file string created before last known RESETLOGS, cannot recreate
  • ora-15206 : duplicate diskgroup string specified
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-01251 : Unknown File Header Version read for file number string
  • 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.