Question

1
Replies
249
Views
YasoKiranR Member since 2014 1 post
Optum Global Solutions
Posted: November 20, 2018
Last activity: December 13, 2018
Closed

PR_LOG_REPORTSTATS table is becoming unavailable

Hi Team,
In Production, the table PR_LOG_REPORTSTATS is going to unavailable state. Which is leading to increasing the log size (with PR_LOG_REPORTSTATS related exceptions)
Every time we had to drop and recreate this table. This is happening quite often.
We are looking for a root cause to see what is causing this issue.
DBA's confirmed that this table is created with the configuration set to "NOT LOGGED INITIALLY". So, we were not able find any clue in identifying which transaction caused the table turn un-available.
1. We would like to know what would be the impact if we remove the "Not Logged initially" clause for this table.
Note: We observed that approximately 50 thousand records are added in a week day.
2. Is there a way in restricting these log exceptions in the log file.
Below is the sample exception:
2018-11-02 00:39:49,605 [.PRPCWorkManager : 1] [ STANDARD] [aimsConnect:15.18.01] ( internal.access.Saver) ERROR - Encountered an error when saving instance "LOG-REPORTSTATISTICS HC6C88878FF8D55F59784B99ADAF29B88!928329C92B81B4C446329F1AAB271BD8!RULE-OBJ-REPORT-DEFINITION INDEX-OPERATOR-WORKGROUPS PXGETOPERATORWORKGROUPS #20130919T012558.499 GMT!EMBEDDED!20181102T053949.597 GMT" of class Log-ReportStatistics
com.ibm.db2.jcc.am.SqlException: For table "TCH.PR_LOG_REPORTSTATS" an object "21" in table space "4" cannot be accessed.. SQLCODE=-1477, SQLSTATE=55019, DRIVER=3.67.27
Moderation Team has archived post
Share this page LinkedIn