Creating a Mock Run Control ID to Place in Blank 3C Engine Fields

Purpose: Use this document as a reference on how to manage/mitigate ISIR JobSet failures by using a mock Run Control ID in place of blank 3C Engine fields.

Audience: Financial Aid Staff responsible for managing/maintaining the ISIR JobSet

Background: All 33 colleges use the same FA 3C Security Groups (FASU, FAVU and FAVO) to assign onto their FA Checklists, Comments, Event Definitions and Communication Categories.

Issue: When there is a blank 3CENGINE field, PS goes through a SQL looking at the users’ 3C Security Groups and lists every institution per Event Definition, Communication Category, Checklist Item Function, etc. When a user is assigned all three FA 3C Security Group or a combination of one FA 3C Security Group and another area’s 3C Security Group (i.e. SFCO, ENRL, ADMA, etc.), the SQL goes to an error that states the process exceeded the maximum number of expressions allowable in a list.

An image of the Message Log with Message Text for SQL error highlighted in yellow

Up until now, if the user’s 3C Security Group was limited to having just FASU or FAVU and no other 3C Security Group assigned, the SQL would run to success without erroring.

As of Thursday afternoon (July 25th 2024) there is too much FA 3Cs data that even those with only FASU or FAVU are running into the SQL error.

A ticket was submitted to Oracle earlier this year on this issue and they have logged it as a defect with no estimated time for resolution.

Current Solution: Fill in each empty 3CENGINE field with a mock Run Control ID.

Note: With this new solution, the ISIR Jobset user can return to having other area’s 3C Security Group (i.e. SFCO, ENRL, ADMA, etc.) assigned

Creating a Mock Run Control ID to place in blank 3C Engine fields

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.