CHASE CAUAJM MESSAGES
Article ID: 19787
Updated On:
Products
Issue/Introduction
Description:
The purpose of this document is to give brief idea of all chase reported error/warning/informational messages to enable customers write their parsingutilities to find the message and take corrective action.
This document will be useful for the WA AE users/Administrators in identifying what the error message or alarms is and proceed accordingly
Solution:
NOTE:
The chase message numbers are going to be changed in WA AE r11.3 SP1 INC2 to be in compatible with WA AE r11.3.5 and future releases. Following table presents a mapping of changed chase message numbers in the releases r11.3SP1 INC1 and r11.3 SP1 INC2. For example, CAUAJM_I_50285 in WA AE r11.3 SP1 INC1 will become CAUAJM_I_50291 in r11.3 SP1 INC2. We advise users to take note of it and change their tools accordingly.
| WAAE r11.3 SP1 INC1 | WAAE r11.3 SP1 INC2 |
| CAUAJM_I_50285 | CAUAJM_I_50291 |
| CAUAJM_E_50286 | CAUAJM_E_50292 |
| CAUAJM_E_50287 | CAUAJM_E_50293 |
| CAUAJM_E_50288 | CAUAJM_E_50294 |
| CAUAJM_E_50289 | CAUAJM_E_50295 |
| CAUAJM_E_50290 | CAUAJM_E_50296 |
| CAUAJM_I_50291 | CAUAJM_I_50297 |
| CAUAJM_I_50292 | CAUAJM_I_50298 |
| CAUAJM_I_50293 | CAUAJM_I_50299 |
| CAUAJM_E_50294 | CAUAJM_E_50286 |
| CAUAJM_E_50295 | CAUAJM_E_50287 |
| CAUAJM_E_50296 | CAUAJM_E_50288 |
CAUAJM_E_20054 Chase cannot run as FAT Client.
Reason:
The AS_TXLOCAL variable must not be set to run the chase utility.
CAUAJM_E_50061 db_get_chase_rows () failed.
Reason:
This indicates application server could not able to fetch the rows from the database i.e jobs that are in STARTING OR RUNNING state.
CAUAJM_E_50061 dbstrx_send_sql () failed.
Reason:
This indicates application server could not able to fetch the rows from the database while processing each job.
i.e gets the pid information from ujo_job_status table.
CAUAJM_E_10245 Trouble with the stored procedure: chase_state.
Reason:
When chase is started it builds a ujo_chase table by getting all the jobs that are running or starting. This error message is issues when there is a problem in executing the ujo_chase_state stored procedure.
CAUAJM_I_50154 Running the Chase process.
CAUAJM_I_50155 Chase is done.
CAUAJM_I_50156 There are no jobs in a STARTING or RUNNING state.
CAUAJM_I_50157 Chase is successful.
CAUAJM_I_50158 Checking on jobs in the xxxxxxx state…
Note: It can be STARTING or RUNNING state.
CAUAJM_I_50159 There are no jobs that have been in the STARTING state
CAUAJM_I_50160 more than 120 seconds.
CAUAJM_I_50161 Examining job: xxxxxxx
CAUAJM_I_50162 Job has been in the STARTING state more than 120 seconds. Manual intervention may be required.
CAUAJM_I_50164 There are no jobs in the RUNNING state.
CAUAJM_E_50165 Unable to inspect any jobs on machine: xxxxxxx
Note: Application server constructs chase string based on the job run information and sends the chase message to the Agent which runs it as an internal job. For some reason If app server cannot communicate with the Agent, then the above error message will be received and it try to reattempt to send the chase string to the Agent to get the required information.
Possible causes: Agent is down or Encryption problem or any communication problems.
CAUAJM_I_50166 Examining job: xxxxxxx on machine: xxxxxxx
CAUAJM_E_50168 ERROR: Job in RUNNING state, but run_machine is empty. Job may have been manually changed to RUNNING state.
Note: Chase utility gets the list of jobs that are in RUNNING state and it will try to get the machine name associated with that job run. If the machine name is not found for that job run, then chase will give this error message. However this is not applicable to r11.3 Agent. This message was carry forwarded from r4.5 code.
CAUAJM_E_50169 ERROR: Receiving information from the agent. CAUAJM_E_50169 The index pointed to a zero ''joid'': chase[xxx].joid = 0. chase_string=xxxxxxxx
Note: This is not applicable to r11.3. This message was carry forwarded from r4.5 code.
CAUAJM_E_50170 ERROR: Receiving information from the agent. CAUAJM_E_50170 The index for xxxxxxxx pointed to a zero ''joid'': chase[xxx].joid = 0. chase_string=xxxxxxxx
Note: This is not applicable to r11.3. This message was carry forwarded from r4.5 code.
CAUAJM_I_50172 Both the agent and the job are still running.
CAUAJM_I_50173 The job_type_name job is still running.
CAUAJM_I_50175 An event for this job has come in during examination. Everything is fine.
Note: It is issued if the job's current status is RUNNING but its a different run of the job i.e. different pid or jc_pid, doesn't match information in chase table.
CAUAJM_E_50178 Could not get row for joid = xxxxxx
Note: This may not be applicable to r11.3. This message was carry forwarded from r4.5 code.
CAUAJM_I_50179 *** ALARM Sent! ***
CAUAJM_I_50298 Job and Agent are not RUNNING. chase sending a FAILURE event.
CAUAJM_I_50299 Job is not RUNNING. chase sending a FAILURE event.
CAUAJM_E_50180 Chase failed to send the CHANGE_STATUS FAILURE event.
Reason:
If the job is not Running at the Agent but the database shows it is RUNNING, then the chase sends a FAILURE event for that job.
If the event 'FAILURE" is not successfully sent, then the 'CAUAJM_E_50180' message will be displayed.
CAUAJM_I_50181 A CHANGE_STATUS to FAILURE has been sent.
Reason:
If the job is not Running at the Agent but the database shows it is RUNNING, then the chase sends a FAILURE event for that job.
If the event 'FAILURE" is successfully sent, then the 'CAUAJM_I_50181' message will be displayed.
CAUAJM_I_50291 Possible chase anomaly: The agent is running, but the job is not, on machine: xxxxxxx
CAUAJM_I_50174 The agent may be in the process of sending the final event back. Check again in a few seconds.
Note: This message is appeared after 'CAUAJM_I_50291'.
CAUAJM_E_50292 *** ERROR: The product's agent is not running, but the user job is, on machine = xxxxxxx
Note: This is also not applicable to r11.3 agent. It is specific to legacy where parent process is not found.
CAUAJM_E_50293 ERROR: File watcher is in RUNNING state, but the agent is not available on machine: xxxxxxx
CAUAJM_E_50294 ERROR: Job is in RUNNING state, but both the product's agent and the user process are not running on machine: xxxxxxx
Note: The above two messages appeared if job is in running state and agent is not running.
These are specific to legacy agent.
CAUAJM_E_50295 Could not connect to machine: xxxxxxx The machine or the network must be down.
Note: It happens if scheduler is not able to connect to the socket of agent's machine. Agent may be down.
Please check the connectivity between the Scheduler and the Agent(Eg: autoping).
CAUAJM_I_50176 Can not determine the status of job_name. Manual investigation is necessary.
This message is appeared after 'CAUAJM_E_50295'.
CAUAJM_E_50296 Error in finding the actual state of the job: xxxxxxx on machine = xxxxxxx
Note: No information about the actual state of the specified job on the specified machine could be obtained.
Inspect the agent log files to determine the state of the job.
CAUAJM_I_50297 Job has been in the RUNNING state for more than n minutes. Manual intervention may be required.
CAUAJM_E_50286 ERROR: Job in RUNNING state, but The user process is not running on machine: xxxxxxx
CAUAJM_E_50287 ERROR: File watcher in RUNNING state, but the file is not being watched by agent on machine: xxxxxxx
CAUAJM_E_50288 ERROR: The job_type_name job is in RUNNING state, but the job is not running on machine: xxxxxxx
Note: The above three message are appeared if actual job's process is not running. Here are 3 different ID's for different job types. These are specific to r11.3.
286 is meant for CMD job type, 287 is meant for FW job and 288 is for all other job types that r11.3 supports.
In this case, somehow job is stuck at RUNNING. Application server gets the information from the jobs that are RUNNING and contact the Agent for the corresponding information. This message would be returned in the chase output/scheduler log, if the Agent could not find the job's process.
CAUAJM_E_50421 Make three more attempts to inspect machine: xxxxxxx, before giving up.
CAUAJM_E_50422 Three attempts failed to inspect jobs on machine : xxxxxxx.
Note: The above two messages appeared after "CAUAJM_E_50165".
Application server constructs chase string based on the job run information and sends the chase message to the Agent which runs it as an internal job. For some reason If app server cannot communicate with the Agent, then the error message" CAUAJM_E_50165" will be received and it try to reattempt to send the chase string to the Agent to get the required information. If all attempts are failed, then the message "CAUAJM_E_50422" is received.
CAUAJM_I_50503 The agent may be in the process of sending an event back. Check the status of the Scheduler.
Reason:
There is communication problem in between scheduler and Agent. For Eg: Scheduler is down or encryption error or other communication problems.
CAUAJM_W_50505 The user process is not running on machine: xxxxxxx. The Scheduler is inactive.
CAUAJM_W_50506 The job_type_name job is not running on machine: xxxxxxx, The Scheduler is inactive.
Reason:
The above two messages refer to the same cause. The user process is not running on the specified machine. It has been determined that the Scheduler is not running thus the job's status may not be accurately reflected.
Action: Start the sceduler.
The message CAUAJM_W_50505 is specific to CMD job type where as CAUAJM_W_50506 refers other job types that 11.3 supported.
CAUAJM_W_50507 The user process is not running on machine: xxxxxxx, an attempt to communicate with the Scheduler failed.
CAUAJM_W_50508 The job_type_name job is not running on machine: xxxxxxx, an attempt to communicate with the Scheduler failed.
Reason:
The user process is not running on the specified machine, an attempt to communicate with the Scheduler failed.
In this case the scheduler is active but the Agent cannot communicate to the scheduler for some reason. Please check the status of the scheduler.
CAUAJM_W_50509 The user process is not running on machine: xxxxxxx, it seems Scheduler is unresponsive.
CAUAJM_W_50510 The job_type_name job is not running on machine: xxxxxxx, it seems Scheduler is unresponsive.
Reason:
The user process is not running on the specified machine, it seems Scheduler is unresponsive. In this case the Scheduler might be hung. Please check the status of the scheduler.
CAUAJM_W_50511 The user process is not running on machine: xxxxxxx, as the Scheduler status is pending high availability fail-over.
CAUAJM_W_50512 The job_type_name job is not running on machine: xxxxxxx, as the Scheduler status is pending high availability fail-over.
Reason:
The user process is not running on the specified machine, as the Scheduler status is pending high availability fail-over. Please wait for the Scheduler's High Availbaility status to be resolved.
CAUAJM_W_50513 The user process is not running on machine: xxxxxxx. The Scheduler status is unknown.
CAUAJM_W_50514 The job_type_name is not running on machine: xxxxxxx. The Scheduler status is unknown.
Reason:
The user process is not running on the specified machine, the Scheduler status is unknown. Please check the status of the database.
CAUAJM_W_50515 The user process is not running on machine: xxxxxxx, the Scheduler has not yet reestablished communication with the Agent.
CAUAJM_W_50516 The job_type_name job is not running on machine: xxxxxxx, the Scheduler has not yet reestablished communication with the Agent.
Reason:
The user process is not running on the specified machine, the Scheduler has not yet reestablished communication with the Agent.
It means the first handshake has not been done yet between the Agent and the Scheduler after services has been started. Please wait for some time or check
Environment
Component:
Feedback
