ACR Summary v9.2 - History file out of space error code #UBS045E & #UBS042E

Follow

Angela Koronkiewicz

• March 05, 2020 15:19

Hi -

I am having an issue when running against the History file with a maximum number of Job-id keys reached, I have run a reorg against the History file but this does not seem to be working.   Can someone please help me on trying to get this History file re-allocated, I have to apologize I am system person not an application person therefore I do not normally perform these tasks.  If you would like to speak to me please feel free to call me (860.954.7009).  I really need this resolved ASAP as I am trying to apply the our New License Key applied and this is part of the test.   Thank in advance for your support...

0

• 

  Brenda Stoetzer

  • March 05, 2020 16:38

  Hi Angela,

  The REORG is the correct course of action, but I noticed that our REORG article was ambiguous about which options to use to resolve these errors. This has now been updated to specifically call out the option to REORG into a new database.

  After selecting the option to REORG into a new database, the key value will be the Estimated number of Job IDs. This will need to be a larger number than what your current history database has. If you aren’t certain what your current Job ID limit is, a List History report will provide this information. This article has also been updated with instructions and a screenshot example of what to look for to increase Job IDs.

  0

  Comment actions Permalink
• 

  Angela Koronkiewicz

  • March 05, 2020 19:26

  Hi Brenda -

  I actually had performed what you suggested but it is not working.  So it appears I am doing something incorrectly.  Is there a webex we can do to see what I am doing wrong?  Please let me know... Thanks

   

  0

  Comment actions Permalink
• 

  Brenda Stoetzer

  • March 05, 2020 20:12

  Hi Angela,

  I'll email you to set up a webex to help resolve your issue.

  Thank you.

  0

  Comment actions Permalink
• 

  Angela Koronkiewicz

  • March 05, 2020 20:14

  Thank you.. I have tried everything and still receiving the same error...

  0

  Comment actions Permalink
• 

  Brenda Stoetzer

  • March 06, 2020 18:19

  Hi Angela,

  Glad to hear that the issue was resolved! To document the resolution here: the history database was originally created by an ID that is no longer active in the system. The contents of the history database were blank, so a fresh database was created under a system ID. The ACR jobs functioned after pointing to the new History database.

  0

  Comment actions Permalink

Please sign in to leave a comment.