CA Service Management

Hi Team,

We have upgraded our r12.6 setup to r14.1.03.2 in our swing box env. However, I'm getting lot of animator errors in the stdlog. Some of the entries are as below:

03/22 10:47:19.13 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826464 (chg:1355241) for atev:9546823 missed 1 firings, the first at 03/22/2017 01:53:58
03/22 10:47:19.24 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826465 (chg:1435701) for atev:10257623 missed 1 firings, the first at 03/22/2017 01:53:58
03/22 10:47:19.35 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826466 (chg:1438867) for atev:10284588 missed 1 firings, the first at 03/22/2017 01:53:58
03/22 10:47:19.52 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826467 (chg:1445983) for atev:10343128 missed 1 firings, the first at 03/22/2017 01:53:58
03/22 10:47:19.65 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826468 (chg:1445977) for atev:10343092 missed 1 firings, the first at 03/22/2017 01:53:58
03/22 10:47:19.72 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826469 (chg:1438903) for atev:10284934 missed 1 firings, the first at 03/22/2017 01:53:59
03/22 10:47:19.82 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826470 (chg:1333433) for atev:9350617 missed 1 firings, the first at 03/22/2017 01:53:59
03/22 10:47:19.83 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826471 (chg:1364780) for atev:9632887 missed 1 firings, the first at 03/22/2017 01:53:59
03/22 10:47:19.90 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826472 (chg:1438918) for atev:10285106 missed 1 firings, the first at 03/22/2017 01:53:59
03/22 10:47:19.91 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826473 (chg:1364769) for atev:9632756 missed 1 firings, the first at 03/22/2017 01:53:59
03/22 10:47:19.97 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826474 (chg:1401621) for atev:9974104 missed 1 firings, the first at 03/22/2017 01:53:59
03/22 10:47:20.00 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826475 (cr:780561) for atev:9303234 missed 1 firings, the first at 03/22/2017 01:53:59
03/22 10:47:20.05 HJTESTISERVE02 animator_nxd        12648 ERROR        animator_nxd.c        2471 Recurring animator ANI:52826476 (cr:816116) for atev:10297682 missed 1 firings, the first at 03/22/2017 01:53:59

Please suggest

Hi,

here is 2 (known by me) possible issues:

- invalid customization: check stdlog for SPEL failures, could looks like:

spelsrvr 19424 ERROR macro.spl 516 AHD03025:Attempt to modify non_CO value
animator_nxd 95940 ERROR animator_nxd.c 2720 Method 2 failed for event zUpdateCI in animator ANI:277288282 (cr:7905527) for atev:94014184

- performance lack: dedicated domsrvr for animator could be a solution: https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.tec1885548.html 

Regards,

cdtj

I think that If you have those errors right after your upgrade and put back your system online, this must just be normal and your system work correctly.

If those events was suppose to fire during the downtime processing your upgrade or restored an mdb then they missed the time and you receive the errors.

Of course they need to be watched and those must disappears. over the time.

My 2 cents

/J

just recalled another one in case errors persist (in fact you may want to check if this happen with newly created ticket too)

You need to look into your config and make sure that your SDM setup on your swing box is connecting to the correct MDB.

I did see others having such problem in the past because both system was addressing the same database.

Hope this help.

/J