Job Aborts when trying to Import a new Application


Article ID: 87598


Updated On:


CA Automic Applications Manager (AM)


Error Message :
ERROR at line 1:
ORA-20024: No such (get_object_seq_aw)Notification as "DOH_TEST_NOTIF" rtype=n
edit=N my_dba=Y my useq=1*-5-7-9-10

When importing new jobs into Applications Manager the job aborts. The job's output file will contain the error listed above. It should only occur when an Application with a Notification attached to it is exported and then imported into a new source instance.


When encountering the above error you should:
  1. Look in the source (the instance where the new Application was imported).
  2. Find the name of the Notification referenced in the error.
  3. Highlight that Notification and press the Usage button.
  4. If the Notificaiton is in use by the Application that was exported and imported into this instnace, follow the workaround below to resolve. 



Root Cause: This happens when a notification is attached to an application that is exported out. The issue is the Application is ahead of the Notification that references it in the export file. This will be reordered in the export sequence.


Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent


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):
Application Manager 9.1.2 - Available

Additional Information

Workaround :
Export and import the notification first. Then export the Application and import it into the new instance.