ORA-01375: Corrupt logfile string recovered

Cause : A corrutp logfil ehas bee nrecoverde by RFS

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

None. Lgoical Stnadby sholud automtaically erstart. fI logfil eis stil lcorrupt ,may nee dto manulaly copya nd rereigster th elogfileo n the satndby.

update : 24-07-2017
ORA-01375

ORA-01375 - Corrupt logfile string recovered
ORA-01375 - Corrupt logfile string recovered

  • ora-25217 : enqueue failed, visibility must be IMMEDIATE for queue string.string
  • ora-34359 : (MXDSS11) string appears twice in the alias list.
  • ora-36674 : (XSDPART12) Invalid dimension value starting at string.
  • ora-38459 : XML Tag "string" not found for the XMLType attribute "string"
  • ora-06765 : TLI Driver: error awaiting orderly release
  • ora-16126 : loading table or sequence string
  • ora-13196 : failed to compute supercell for element string.string.string
  • ora-07276 : no dba group in /etc/group.
  • ora-01294 : error occurred while processing information in dictionary file string, possible corruption
  • ora-01109 : database not open
  • ora-12812 : only one PARALLEL or NOPARALLEL clause may be specified
  • ora-24352 : invalid COBOL display type passed into OCI call
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • ora-39038 : Object path "string" is not supported for string jobs.
  • ora-36698 : (XSRELTBL03) QDR dimension workspace object should be in the dimension list that dimensions the relation.
  • ora-13226 : interface not supported without a spatial index
  • ora-16187 : LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
  • ora-31054 : The string operator cannot have an ancillary operator
  • ora-25142 : default storage clause specified twice
  • ora-32400 : cannot use object id columns from materialized view log on "string"."string"
  • ora-01141 : error renaming data file string - new file 'string' not found
  • ora-16103 : Logical Standby apply must be stopped to allow this operation
  • ora-07609 : szprv: $HASH_PASSWORD failure
  • ora-24065 : propagation for QUEUE string and DESTINATION string already disabled
  • ora-28561 : unable to set date format on non-Oracle system
  • ora-39147 : cannot migrate Data Pump queue table ownership to this instance
  • ora-01115 : IO error reading block from file string (block # string)
  • ora-25301 : Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2
  • ora-30122 : value 'string' for 'string' must be between 'number' and 'number'
  • ora-10564 : tablespace 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.