Question & Answer
Question
Why do we get exceptions on Guardium aggregator in Schedule Job Exception report that partitions for tables can not be added prior the last partition?
Example of exceptions we get:
Schedule Job Exception report.: AGG_ADD_PARTITION Table:GDM_CONSTRUCT_TEXT Stage:Get last partition info; error:Partition for 2019-03-17 00:00:00 can not be added prior the last partition ( 2019-03-24)
Answer
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Component":"","Platform":[{"code":"PF004","label":"Appliance"}],"Version":"v10","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
04 April 2019
UID
ibm10879543
The reason for this exception is that a day is imported from a collector that is earlier than the earliest data already existing on the aggregator.
The data will still be imported and reports should work as normal - The only affect of the exception is how the data is held in the aggregator internal database structure.
If you did this on purpose you can ignore the exception - For example if you intentionally exported data from a collector older than 10 days, but aggregator purge period is 5 days.
If you are unsure why the exception is there, you may need to investigate - For example one of the collectors may unintentionally have different export settings than the rest. This kind of configuration difference should be corrected manually if it was not intentional.