Error Message :
ErrorMsg: AwE-5001 Database Query Error
On a new install of Applications Manager (AM) the Automation Engine (Master) starts but remains in a TROUBLE status when the Master name is long (over 20 characters).
- Install an AM Master using the name DEV_APP_MANAGER_ENGINE (22 characters long)
- Start the AM processes (startso all)
- The Master will stay in a TROUBLE status and any jobs that are launched will stay in a RUNNING status.
- Enable RmiServer debugging and look at the RmiServer<timestamp>.log files that are generated in the AM log directory.
The following errors are displayed:
14:30:00.315 rfp0: .DBAccess: checkError 6502
14:30:00.316 rfp0: AwE-5001
14:30:00.316 rfp0: SQL Error: 6502
14:30:00.317 rfp0: .AxOptions: NoErrorMsgProperties=false
ErrorMsg: AwE-5001 Database Query Error (11/29/16 2:30 PM)
0 name: IN:VARCHAR2:java.lang.String:DEV_APP_MANAGER_ENGINE
1 progname: IN:VARCHAR2:java.lang.String:RMIMASTER
2 sessionId: IN:NUMERIC:java.math.BigDecimal:45408
3 status: IN:OUT:VARCHAR2:java.lang.String:STARTING
4 cpuUsage: IN:VARCHAR2::null
java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "APPMGR_REPO.AW5", line 1824
ORA-06512: at line 1
The issue is a result of a procedure being called that inserts into the SO_JOB_HISTORY table. The record that is being inserted records the status change of the Master. When it does this it tries to insert the name of the Master (DEV_APP_MANAGER_ENGINE) a dash (-) and the type (RMIMASTER). This display name that it is trying to insert into the SO_MODULE field of the SO_JOB_HISTORY table exceeds the 30 charater limit defined for that field, since ‘DEV_APP_MANAGER_ENGINE-RMIMASTER’ is 32 characters long. This causes the Master to go into a TROUBLE state.