AutoSys Upgrade: Database Upgrade Fails with ORA-12609 TNS Receive Timeout

Products

• Autosys Workload Automation

Issue/Introduction

When upgrading AutoSys from version 24.0.1 to 24.2, the installer may report a successful installation of binaries while the database (AEDB) schema upgrade fails.

This issue is typically characterized by an ORA-12609 error in the installation logs, leading to a state where binaries are updated but the application cannot start due to a partially upgraded database. This article provides the steps to revert the database version metadata and re-run the upgrade successfully.

 

Symptoms
Users may observe the following behavior during the upgrade process:

The installer reports that the database was not created or updated.

2026-04-30 09:52:32,649 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - 
2026-04-30 09:52:32,649 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - Elapsed: 00:00:00.02
2026-04-30 09:52:32,799 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - 
2026-04-30 09:52:32,799 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - PL/SQL procedure successfully completed.
2026-04-30 09:52:32,799 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - 
2026-04-30 09:52:32,799 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - Elapsed: 00:00:00.15
2026-04-30 09:52:40,668 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - 
2026-04-30 09:52:40,668 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - Index created.
2026-04-30 09:52:40,668 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - 
2026-04-30 09:52:40,668 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - Elapsed: 00:00:07.87
2026-04-30 09:52:51,075 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - CREATE INDEX xak4ujo_proc_event ON ujo_proc_event
2026-04-30 09:52:51,075 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) -                                    *
2026-04-30 09:52:51,075 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ERROR at line 1:
2026-04-30 09:52:51,075 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ORA-12609: TNS: Receive timeout occurred
2026-04-30 09:52:51,075 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - 
2026-04-30 09:52:51,075 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - 
2026-04-30 09:52:51,075 [Thread-19] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - Elapsed: 00:00:10.41

Cause

The issue is caused by a TNS receive timeout during the execution of SQL commands (e.g., creating an index) during the schema upgrade.

In documented cases, Oracle parameters in $TNS_ADMIN/sqlnet.ora like SQLNET.RECV_TIMEOUT, SQLNET.INBOUND_CONNECT_TIMEOUT and SQLNET.OUTBOUND_CONNECT_TIMEOUT were set to 10 seconds, causing the operation to terminate if it exceeded this duration.

Resolution

Increase the timeouts in the sqlnet.ora file (to 60 or 120 ) and re-run the upgrade again.