How to resolve a Could not load Century Cutoff cache alert

October 24th, 2023

0 min read

We don’t see Could not load Century Cutoff cache alerts often at ERP Suites. So when they do occur we look to the UBE job log first to verify it is true.

This type of alert typically appears when using RUNUBEXML to override Processing Options and Report Interconnects. If the associated XML files are longer than 256 characters, the XML parse code in the engine will not be able to read them correctly.

Could not load Century Cutoff cache is a reported Oracle bug. Open a service request with Oracle to initiate a fix.

Topics:

ERP Suites Clarity 23A

How to resolve a Could not load Century Cutoff cache alert

Related Articles

How to resolve a Result set time out alert

Security Monitor

Synthetic Monitor is not Collecting

Application Monitor is not collecting

How to resolve a STUCK alert

Adding a new user in Clarity

How to resolve a JDB9900255 alert

Validating Application Analytics in Clarity

Database Monitor

Service account setup

Alert Subscriptions