ORA-01347: Supplemental log data no longer found

Cause : The osurced atabsae intsancep roduicng lgo filse fort his oLgMinre sesison wsa altreed t ono lnoger olg supplemetnal dtaa.

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

Destory thsi Logimner esssio.n Re-neables upplmeenta llog adta o nthe osurces yste mand rceatea newL ogMienr session.

update : 24-08-2017

ORA-01347 - Supplemental log data no longer found
ORA-01347 - Supplemental log data no longer found

  • ora-09313 : slsprom: error prompting user
  • ora-15122 : ASM file name 'string' contains an invalid file number
  • ora-00703 : maximum number of row cache instance locks exceeded
  • ora-16072 : a minimum of one standby database destination is required
  • ora-29515 : exit called from Java code with status string
  • ora-31121 : The string operator can not be FALSE
  • ora-12493 : invalid MLS binary label
  • ora-13800 : concurrent DDL failure on SQL repository objects
  • ora-13388 : invalid value for dst_spec parameter
  • ora-14318 : DEFAULT partition must be last partition specified
  • ora-03136 : inbound connection timed out
  • ora-29830 : operator does not exist
  • ora-12462 : undefined compartment string for policy string
  • ora-37129 : (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-02021 : DDL operations are not allowed on a remote database
  • ora-31624 : A job cannot be modified after it has started.
  • ora-22926 : specified trim length is greater than current LOB value's length
  • ora-22805 : cannot insert NULL object into object tables or nested tables
  • ora-14134 : indexes cannot use both DESC and REVERSE
  • ora-27148 : spawn wait error
  • ora-16525 : the Data Guard broker is not yet available
  • ora-01571 : redo version string incompatible with ORACLE version string
  • ora-13153 : invalid high water mark specified
  • ora-24054 : cannot propagate to an Oracle 8.0.3 release or lower release
  • ora-12702 : invalid NLS parameter string used in SQL function
  • ora-07759 : slemtr: invalid destination
  • ora-23359 : error on creating a ddl record for a repcatlog record
  • ora-26747 : The one-to-many transformation function string encountered the following error: string
  • ora-07635 : smsdbp: $SETPRT failure
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • 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.