12.1.01 version upgrade did not work as expected
Article ID: 381156
Updated On:
Products
Issue/Introduction
When trying to upgrade Autosys to 12.1.1 with an Oracle 19c backend database the following error was seen:
2024-11-02 06:09:18,562 [main] INFO com.ca.autosys.db.utils.CommandExecutor(49) - Command return value:02024-11-02 06:09:18,562 [main] DEBUG com.ca.autosys.db.utils.CommandExecutor(51) - RetVal =02024-11-02 06:09:18,562 [main] WARN com.ca.autosys.db.install.CreateInstanceSchema(491) - Found error pattern ORA-009722024-11-02 06:09:18,562 [main] ERROR com.ca.autosys.db.install.CreateInstanceSchema(160) - database was not created or updated.2024-11-02 06:09:18,562 [main] ERROR com.ca.wla.ae.installer.mm.action.UpgradeDatabaseAction(114) - Database was not created or updated.2024-11-02 06:09:18,563 [main] ERROR com.ca.wla.ae.installer.logger.LogHelper(45) - FatalException : E_AE_Create_Database_Error [CAUAJM_E_116408] An error occurred while creating or upgrading the <INSTANCE ID> database. For more information, refer to the log file.2024-11-02 06:09:18,565 [main] INFO com.ca.wla.ae.installer.mm.rules.UpgradeDatabaseRule(26) - Evalute custom rule before upgrading database2024-11-02 06:09:18,565 [main] INFO com.ca.wla.ae.installer.mm.rules.UpgradeDatabaseRule(31) - Upgrading database2024-11-02 06:09:19,870 [main] INFO com.ca.wla.ae.installer.customaction.AEComposePostInstallMessage(33) - Composing post install message2024-11-02 06:09:19,871 [main] DEBUG com.ca.wla.ae.installer.customaction.AEComposePostInstallMessage(41) - Error message=Encountered fatal error: [CAUAJM_E_116408] An error occurred while creating or upgrading the <INSTANCE ID> database. For more information, refer to the log file.
2024-11-02 06:09:19,871 [main] DEBUG com.ca.wla.ae.installer.customaction.AEComposePostInstallMessage(72) - msg:Encountered fatal error: [CAUAJM_E_116408] An error occurred while creating or upgrading the <INSTANCE ID> database. For more information, refer to the log file.Post-installation logs will be written to:
Additional errors from the logs:
Example 1:2024-11-02 06:07:51,590 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - Elapsed: 00:00:00.022024-11-02 06:07:51,609 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ALTER TABLE ujo_temp_jobruns DROP CONSTRAINT xpkujo_temp_jobruns2024-11-02 06:07:51,609 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - *2024-11-02 06:07:51,609 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ERROR at line 1:2024-11-02 06:07:51,609 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ORA-02443: Cannot drop constraint - nonexistent constraint2024-11-02 06:07:51,609 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - 2024-11-02 06:07:51,609 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - 2024-11-02 06:07:51,609 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - Elapsed: 00:00:00.012024-11-02 06:07:51,630 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - DROP INDEX xpkujo_temp_jobruns2024-11-02 06:07:51,630 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - *2024-11-02 06:07:51,630 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ERROR at line 1:2024-11-02 06:07:51,630 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ORA-01418: specified index does not exist
Example 2:2024-11-02 06:08:00,187 [main] INFO com.ca.autosys.db.install.CreateInstanceSchema(489) - Found skip pattern ORA-014182024-11-02 06:08:00,187 [main] INFO com.ca.autosys.db.install.CreateInstanceSchema(489) - Found skip pattern ORA-01418
Example 3:2024-11-02 06:09:14,450 [Thread-24] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - CREATE OR REPLACE FUNCTION ujo_delete_strings_from_generic (2024-11-02 06:09:14,450 [Thread-24] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - *2024-11-02 06:09:14,450 [Thread-24] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ERROR at line 1:2024-11-02 06:09:14,450 [Thread-24] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ORA-00972: identifier is too long2024-11-02 06:09:14,450 [Thread-24] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - 2024-11-02 06:09:14,450 [Thread-24] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - 2024-11-02 06:09:14,479 [Thread-24] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - grant execute on ujo_delete_strings_from_generic to ujoadmin2024-11-02 06:09:14,479 [Thread-24] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - *2024-11-02 06:09:14,479 [Thread-24] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ERROR at line 1:2024-11-02 06:09:14,479 [Thread-24] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ORA-00903: invalid table name
Environment
Autosys 12.x
Oracle 19c
Cause
The oracle database was in 12.x compatibility mode.
Resolution
Run the below query on the Autosys target database
SELECT name, value FROM v$parameter WHERE name = 'compatible';
Example output:
NAME
--------------------------------------------------------------------------------
VALUE
--------------------------------------------------------------------------------
compatible
12.1.0.2.0
This is the root cause of this issue R12.x must run on Oracle 19C or newer database
Autosys Support Matrix
To resolve the problem restore a known good backup of the database.
have the DBA change the compatibility mode.
Run the upgrade again.
Feedback
