Question & Answer
Question
What kind of data is recorded in tables LLRC_LOG_RECORDS and LRPR_RECORD_PROPERTIES
Answer
What kind of data is recorded in the following two tables in the TWS_LOG table space?
- LLRC_LOG_RECORDS
- LRPR_RECORD_PROPERTIES
This table space stores information related to event rules and auditing capabilities.
From DWC "System status and health", the following items are applicable.
-Event rule monitor
-Operation message monitor
-Monitor triggered actions
In addition, the mechanism for cleaning up these tables is as follows.
optman ls key'logHistory' (default 10 days) will automatically clean up the tables.
The table cleanup begins 10 days after the new event rule fires.
If you want to change this default 10 day setting, change logHistory.
In order to reflect the change, it is necessary to cross the daily processing.
The cleanup will be started at a certain time (or later) and event rules of the same type will be executed and added to the DB.
That is, when TWS needs to add a new entry to these tables, it will perform cleanup on the same type of objects in the DB if they are overdue.
Therefore, once a record is added, this existing record will not be automatically cleaned up unless a new record is created.
If user want to delete, user can delete the record of this table with SQL command.
From the TWS point of view, it is recommended to reduce the value of logHistory to reduce the capacity of the table.Manually clearing LOG.LLRC_LOG_RECORDS should not cause any TWS issues.
Regarding the SQL command to execute, it is recommended to consult with the Oracle DB administrator or DB2 administrator because a full backup should be the first.
Example: Delete All Rows You can delete all columns in the table without deleting the table.
The table structure, attributes and indexes remain the same.
DELETE FROM table_name
Or
DELETE * FROM table_name.
User can set auditHistory to the smallest possible value, for example, set it to "0", but there are following considerations:
IWS9.4 has a function to retain and restore the history of changes in various definition information such as jobs and job streams.
Note that if auditHistory is set to 0, the change history will be lost due to the change made the next day, and this definition will not be restored.
* Refer to the definition information from Workload Designer, and there is a "Version" tab.
If user have a backup to a text file with Composer create each time you change the definition, there is no problem even if it is 0.
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"ARM Category":[{"code":"a8m0z000000GnQ9AAK","label":"Components->MDM"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
12 February 2021
UID
ibm16353347