Red Hat Bugzilla – Bug 797325
RHQ_ALERT_NOTIFICATION created with NOLOGGING option in Oracle
Last modified: 2012-04-25 08:50:28 EDT
Description of problem:
RHQ_ALERT_NOTIFICATION table is created with the NOLOGGING option in an Oracle schema, but should be created without the option as it concerns configuration. In the case of a database issue on the user side and the user relying on redo logging to rebuild the database, the usage of NOLOGGING means that the user will have to manually review the alert notification configuration for every alert in order to confirm that their notifications are properly configured.
Depending upon the number of alerts, this could require many man hours to verify, or could mean that a user relying on the notifications for monitoring will overlook error/warning states that they should have been aware of if they do not check that the RHQ_ALERT_NOTIFICATION table was restored properly.
Version-Release number of selected component (if applicable):
RHQ 4.2.0/JON 3.0.0
triage asantos, mfoley, crouch, loleary ...JON 3.1
looks like we should be removing the NOLOGGING option from RHQ_ALERT_NOTIFICATION table.
The work around until we patch the dbsetup/dbupgrade code is to run the SQL:
alter table rhq_alert_notification logging
master commit aea4f08 adds dbsetup and dbupgrade code to enable oracle logging on rhq_alert_notification table.
attaching an image which shows RHQ_ALERT_NOTIFICATION table still has LOGGING=NO.
marking failed to verify.
Created attachment 579078 [details]
logging in oracle schema
Created attachment 579091 [details]
my server log
I'm reverting this until bug #814839 is discussed. It turns out, EVERY table has NOLOGGING enabled. Read bug #814839 for the conversation. Teh current thinking is we do not want or need LOGGING.
Created attachment 579978 [details]
turn on oracle logging on relevant tables
see attached for a .sql file you can execute to turn on LOGGING on all relevent tables. Use this if you want to enable LOGGING on RHQ database tables if you already have RHQ installed.
See bug 814839 for tracking the issue of fixing this on initial install.
closing this as duplicate - see bug #814839
*** This bug has been marked as a duplicate of bug 814839 ***