Our Siebel database has forced logging set to yes, but I am still getting a ton of faults

  • 0
  • 1
  • Question
  • Updated 3 years ago
  • Answered
Our Siebel database has forced logging set to yes, but I am still getting a ton of faults like the one below. Have you seen this before? SQL> SELECT force_logging FROM v$database; FOR --- YES SQL> WARNING May 17, 2015 10:34 PM MCK1 - CRM Sources/sblmck1@2015-05-17T12:43:40.768Z Title: NOLOGGING operation occurred after the last snapshot Details: NOLOGGING operation(s) occurred on database "sblmck1" between SCNs 246388237988 and 246392449360. Running queries against a VDB provisioned from this snapshot could result in Oracle corruption errors ORA-01578 and ORA-26040. Any Ideas?
Photo of Brad Drey

Brad Drey

  • 70 Points

Posted 3 years ago

  • 0
  • 1
Photo of Tim Gorman

Tim Gorman, Field Services

  • 2,794 Points 2k badge 2x thumb
Official Response
Brad,

Faults remain until "ignored" or "marked resolved", and the one cited here is almost 3 weeks old.

When was FORCE LOGGING set on the database in question?

Thanks!