Request job condition goes into DB ERROR status

Document ID : KB000088393
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
When running a REQUEST JOB condition the job will go into a DB ERROR status. In the RmiServer debug logs (RmiServer<timestamp>.log) on the Master you will see an error similar to this:
 
ErrorMsg: AwE-5001 Database Query Error (03/05/16 11:01)
Details: aw5.aw_condition_action
0 jobid: IN:NUMERIC:java.math.BigDecimal:27641
1 condition_order: IN:NUMERIC:java.math.BigDecimal:5
2 action: IN:VARCHAR2:java.lang.String:REQUEST JOB
3 performed: IN:OUT:VARCHAR2:java.lang.String:A
4 actionArg: IN:VARCHAR2:java.lang.String:-m TEST_JOB -u NEWUSER -s Y -o WIN3 -q BATCH -f STORE -argh 12345
5 results: OUT:NUMERIC::null
6 text: OUT:VARCHAR2::null
 
jdbc:oracle:thin:@/vwasram8u01:1530/test:AMPROD
java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error: character string buffer too small 

After multiple reset attempts, with no changes being made to the job, the job will eventually complete.
Resolution:
This is a User Groups issue.

User groups do not inherit permissions from each other. This only gives you access to the user group object, not the objects the user group has permissions to. For more information see Working with User Groups in the Application Manager documentation.

Code changes relating to User Groups (roles) have been made to make AM more secure.  Therefore, if you have upgraded from an older version of Applications Manager and you experience this issue, you will want to ensure that you add a User Group to the user that has access to the Agent first.

When you "inactivate" an Agent, you have to Edit the Agent and uncheck the Active button, then click Apply/Ok.

In order to Edit any object within AM, you must have Edit access to ALL of the objects assigned to that object (including User Groups). To resolve this, you would add the "non-edit" user group to your "edit" user group. You do not have to assign the non-edit user group to your User itself.