Applications Manager 9.6 installation or upgrade ends with fatal error trying to execute script aw_post_checks
search cancel

Applications Manager 9.6 installation or upgrade ends with fatal error trying to execute script aw_post_checks

book

Article ID: 388822

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

When running Applications Manager installation or upgrade for version 9.6, it may fail with the below error:

Starting at 02/05/25 03:48:49                script aw_post_checks
Finished at 02/05/25 03:48:49 Elapsed Time 00:00:00 script aw_post_checks
errors=ORA-06550: line 7, column 8: ORA-04063: package body "AM.AWAPI2" has errors ORA-06508: PL/SQL: could not find program unit being called: ORA-06512: at line 4 ORA-04063: package body "AM.AWAPI2" has errors ORA-06508: PL/SQL: could not find program unit being called: ORA-06512: at line 1 ORA-04063: package body "AM.AWAPI2" has errors ORA-06508: PL/SQL: could not find program unit being called: ORA-06512: at "AM.CHECK_OBJECTS", line 13 ORA-06512: at "AM.CHECK_OBJECTS", line 13 ORA-06512: at line 1
Fatal error trying to execute script aw_post_checks

Fatal error trying to execute script aw_post_checks
Fatal Error occurred - check the log /apps/appmgr9/960/install/aw_install.log 
set_path=/apps/appmgr9/960/bin/stopso
stopso all
     ==================
   Requested processes "all" not running
   stopso done

When checking the aw_post_checks.lst, the following error is seen:

re-create AQ tables
    am_aq.drop_and_create_all_am_queue_tables;
          *
ERROR at line 7:
ORA-06550: line 7, column 8: 
PLS-00114: identifier 'DROP_AND_CREATE_ALL_AM_QUEUE_T' too long 

 

Environment

Applications Manager 9.6

Cause

Prior to Oracle version 12.2, identifiers are not allowed to exceed 30 characters in length

Resolution

The Oracle database version must be 12.2 or higher.

If Oracle is on 12.2 and the error is seen, your Oracle System "Compatible" value may be set to 12.1 or lower. The following sql can be run when logged in as an oracle admin account to see your compatible value:

SELECT name, value FROM v$parameter WHERE name = 'compatible';

Refer to your Oracle DBA regarding and updating this value to 12.2 or higher as it may cause adverse effects if systems depend on the Oracle Compatible setting to be 12.1