Applications Manager 9 bad OriginalStartDate Error

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

Error Message :
ErrorMsg: AwE-9999 Internal error (9/3/15 4:07 PM)
Details: 12453 bad OriginalStartDate
2015-06-29 09:23:34.0 old: null

After upgrading to Applications Manager v9, you may see a pop-up error:

ErrorMsg: AwE-9999 Internal error (9/3/15 4:07 PM)
Details: 12453 bad OriginalStartDate

This is related to the WatchWorx process.  The current workaround is to:

Find and delete the referenced jobid from the so_job_history table. The jobid can be found in the "Details" line of the error and right before the "bad OriginalStartDate" error. The SQL statements used to find and delete the jobid causing the error would be:

SQL> select so_module, so_jobid from so_job_history where so_jobid='<jobid>';
SQL> delete from so_job_history where so_jobid='<jobid>';
SQL> commit;

NOTE: Replace <jobid> in the above SQL statements with the jobid found in the error message you are receiving.

If the error is being generated by the watchworx process, we recommend that you stop the watchworx process to avoid the error:

stopso watchworx

Environment

Release: AAMORS99000-9.0-Automic Applications Manager-Oracle - RMS
Component:

Cause

Cause type:
Defect
Root Cause: Users would receive a non-fatal message pop-up in the user interface: AwE-9999 Internal error "bad OriginalStartDate". This was caused by an incorrect virtual day set for the WatchWorx process when it started. Sample error included below.

Resolution

This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
Applications Manager 9.1.2 - Available

Additional Information

Workaround :
Find and delete the referenced jobid from the so_job_history table. The jobid can be found in the "Details" line of the error and right before the "bad OriginalStartDate" error. The SQL statements used to find and delete the jobid causing the error would be:SQL> select so_module, so_jobid from so_job_history where so_jobid='';SQL> delete from so_job_history where so_jobid='';SQL> commit;NOTE: Replace in the above SQL statements with the jobid found in the error message you are receiving.If the error is being generated by the watchworx process, we recommend that you stop the watchworx process to avoid the error:stopso watchworx