ORA-19582: archivelog file header validation for string failed

Cause : Archived log file header is corrupt and could not be validated.

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

Provide a valid archivelog file and retry the operation.

update : 17-08-2017
ORA-19582

ORA-19582 - archivelog file header validation for string failed
ORA-19582 - archivelog file header validation for string failed

  • ora-03275 : duplicate DEALLOCATE option specification
  • ora-10387 : parallel query server interrupt (normal)
  • ora-06011 : NETASY: dialogue too long
  • ora-01967 : invalid option for CREATE CONTROLFILE
  • ora-27140 : attach to post/wait facility failed
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-31673 : worker process interrupt for normal exit by master process
  • ora-23449 : missing user name
  • ora-04934 : unable to obtain the current sequence number
  • ora-25312 : Cannot specify nonzero sender protocol
  • ora-16716 : clearing parameter LOG_ARCHIVE_DEST failed
  • ora-16192 : Primary and standby network integrity mismatch
  • ora-01664 : Transaction which has expanded the Sort Segment has aborted
  • ora-13408 : invalid blockSize storage parameter
  • ora-34360 : (MXDSS15) number other users writing
  • ora-02338 : missing or invalid column constraint specification
  • ora-29808 : specified primary operator binding does not exist
  • ora-13199 : %s
  • ora-12525 : TNS:listener has not received client's request in time allowed
  • ora-01190 : control file or data file string is from before the last RESETLOGS
  • ora-02427 : create view failed
  • ora-29852 : keyword IS is missing
  • ora-38959 : Failed to update block 0 to new version 10 format
  • ora-38759 : Database must be mounted by only one instance and not open.
  • ora-34260 : (MXDCL25) You cannot use number to dimension a string because it is, or involves, a dimension composite. Use the composite's bases instead.
  • ora-32057 : invalid lock mode
  • ora-28339 : missing or invalid encryption algorithm
  • ora-12321 : database (link name string) is not open and AUTO_MOUNTING=FALSE
  • ora-32034 : unsupported use of WITH clause
  • ora-00378 : buffer pools cannot be created as specified
  • 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.