I appreciate the response, but I don't think it's this. Our loads are well-behaved around Cube Logging, and I have confirmed by checking tm1s.log myself.
Entries to FX Rates, and some, small user-driven cubes are captured, but the larger process-based loads are not appearing in the log, thank goodness.
Original Message:
Sent: Mon October 21, 2024 08:57 AM
From: Terry Hamlet
Subject: Unregistered object count exceeds max
Hi Isabel,
On your TI processes are you turning the logging off? I'm wondering if your system was crashing due to log files. But instead threw a different error. Long shot, but.....
On Prolog tab: CUBESETLOGCHANGES(LoadCube, 0);
and switch back on epilog Tab: CUBESETLOGCHANGES(LoadCube, 1);
Otherwise, how are your typical views written on Prolog tab? I assume the view and subsets are temporary with a 1 at end. Those should delete when each process completes. Are you running multiple processes within another processes?
------------------------------
Terry Hamlet
Original Message:
Sent: Fri October 18, 2024 12:15 PM
From: Isabel Krasa
Subject: Unregistered object count exceeds max
2.09.18
We upgraded recently to resolve crashes caused by too many temporary objects.
Recently we had an issue where any processes kicked off by the prod service account failed with this message:
TM1.Client DIAG: Unregistered object count exceeds max. User 'CAMID("Cognos ANT:u:ProdServiceAccount")' being shut down.
If the process was creating a temporary view or subset.
We've never seen this message before, and Google knows very little about it.
We attempted to remediate by deleting tens of thousands of unneeded views and subsets. This did not work.
Restarting the Tm1 Instance worked, but is there a way to clear temporary objects without a restart?If the max is based on user, could we prevent this with a second Service Account?
And yes, this model is too big, and doing too much. We are working to split it into smaller models.
------------------------------
Isabel Krasa
------------------------------