We have the Clarity 12.1.3 version with Oracle 11g used as back-end.
As far as, DB backup/restore operation is concerned,
CA suggested to take only off-line backup provided the clarity front-end and back-end should be down. It is good practice normally.
But, In a Live environment, We need to schedule a online backup so as to capture the incremental txn happening in live.
For that, Our DBA has enabled the archive log mode
During the Restore(using the data pump feature) of the DB backup, we are facing a error like
ORA-01578: ORACLE data block corrupted (file # 29, block # 219779)
ORA-01110: data file 29: '/qp/QP_TS01_12.dbf'
ORA-26040: Data block was loaded using the NOLOGGING option
all the transactions should be archive logged. But some txn doesn't create the archive logs which caused the restore(applying the increment archive logs on the top of offline backup ) operation fails.
And found that, For performance reasons, some clarity operations are carried out without creating the archive logs.
So, our DBA had enabled the force logging at the database level in a non-live db environment like
ALTER DATABASE force logging;
Then monitoring on the archive logs sizing which seems to be ok. Not creating huge archive logs as expected.
Hope the current archive logs doesn't have any issues. So, plan to restore with the offline + increment archive logs to check the restore db operation is a successful one or not?
Could you please advise us whether the fix for the said no-logging issue is correct or not?
And, Any best practices available on DB backup/restore especially for Live environment?