outdated IRM instances

DionisMotor — Thu, 24 Apr 2025 14:21:17 GMT

Hi community,

I'm facing a strange situation and would appreciate any insights.

We have a chain of job flows, and all steps executed successfully — each instance completed with status "Completed Successfully".

Then I simply restarted SASServer8_1 — no other changes, no manipulation with input or landing areas.

However, after the restart, some instances were unexpectedly downgraded to outdated versions. Even more concerning: all tables inside the affected instances were deleted.

What I found in SASIRMServer.log:

...
IRM [localhost-startStop-1] 24Apr25 13:00:17,369 INFO  com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService  - Entering JobFlowGraph.buildJobFlowGraph for instance EBA Post Processing
IRM [localhost-startStop-1] 24Apr25 13:00:17,370 INFO  com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService  - Starting normalizeInputsOutputs for job flow EBA Post Processing
IRM [localhost-startStop-1] 24Apr25 13:00:17,476 INFO  com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService  - Deleting output links for 22 tasks of flow instance "EBA Post Processing" (1693137507)
IRM [localhost-startStop-1] 24Apr25 13:00:17,548 INFO  com.sas.solutions.risk.irm.server.pooling.OutputPool  - Deleting 22 unreferenced outputs. [/opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1636, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1648, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1643, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1651, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1638, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1652, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1653, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1655, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1641, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1650, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1635, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1640, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1637, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1649, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1639, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1654, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1634, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1642, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1645, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1647, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1646, /opt/sas/stratum/config/Lev1/AppData/SASIRM/pa/pool/_1644]
IRM [localhost-startStop-1] 24Apr25 13:00:18,400 INFO  com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService  - Done normalizeInputsOutputs for job flow EBA Post Processing in 1030ms.
IRM [localhost-startStop-1] 24Apr25 13:00:18,400 INFO  com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService  - Leaving JobFlowGraph.buildJobFlowGraph for instance EBA Post Processing
IRM [localhost-startStop-1] 24Apr25 13:00:18,400 INFO  com.sas.solutions.risk.irm.server.jobflowexec.JobFlowExecutor  - Leaving JobFlowExecutor.buildJobFlowGraph for instance EBA Post Processing (key: 1693137507)
IRM [localhost-startStop-1] 24Apr25 13:00:18,417 INFO  com.sas.solutions.risk.irm.server.engine.JobFlowService  - Updated job flow instance 1693137507 in the cache.
...

Has anyone experienced something similar or knows what might cause this behavior?

Thanks in advance!

Re: outdated IRM instances

ElizabethKyria — Mon, 12 May 2025 12:52:42 GMT

Hi there

I've been advised that you'd need to reach out to tech support to assist with your question, contact: SAS Technical Support | SAS Support

Regards

Elizabeth Kyriacou

Re: outdated IRM instances

DionisMotor — Fri, 16 May 2025 12:29:35 GMT

I’ve opened a ticket, but so far we’re still at the stage of "Please send the Deployment Registry Report" 😞

topic Re: outdated IRM instances in SAS Risk Management

outdated IRM instances

Re: outdated IRM instances

Re: outdated IRM instances