Install issue on Oracle AI Database

[Pothen Verghese]

Dear All,

Install of AutoSys 24.1x on Oracle AI Database, is stuck with below error:

[CAUAJM_E_112517] The current database server "PDB1" version is "null".  The minimum database version required is not met. For more information, refer the AutoSys Support Matrix.

The cawa_installer.log shows:

2026-05-07 10:34:52,569 [main] DEBUG com.ca.autosys.db.connection.DBOperations(81) - Running query: SELECT VERSION FROM PRODUCT_COMPONENT_VERSION WHERE PRODUCT LIKE ? AND ROWNUM=1
2026-05-07 10:34:52,569 [main] DEBUG com.ca.autosys.db.connection.DBOperations(191) - Query params:
2026-05-07 10:34:52,569 [main] DEBUG com.ca.autosys.db.connection.DBOperations(195) - [1 : Oracle Database%]
2026-05-07 10:34:52,659 [main] INFO  com.ca.autosys.db.validation.DBValidator(179) - Database server version - null
2026-05-07 10:34:52,659 [main] DEBUG com.ca.wla.ae.installer.database.DBHelper(1530) - The server version is:null
 

If we run sql on oracle db directly the output is:

QL> SELECT * FROM PRODUCT_COMPONENT_VERSION;

PRODUCT
--------------------------------------------------------------------------------
VERSION
--------------------------------------------------------------------------------
VERSION_FULL
--------------------------------------------------------------------------------
STATUS
--------------------------------------------------------------------------------
Oracle AI Database 26ai Enterprise Edition
23.0.0.0.0
23.26.1.0.0
Production

==================================================

The install process is querying for Oracle Database%, while internally the name is Oracle AI Database%

Is there any way to correct the installer query so that install can proceed?

Regards

Pothen

-------------------------------------------

[Gene Howard]

HI, sorry you are having an issue.
You are using 24.1 Autosys, which supports Oracle 23Ai, not 26 Ai, which you are running.
https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/autosys-workload-automation/24-1-00/release-notes/ae-compatibility-matrix/autosys-server-database-support-matrix.html

The installer was made before that was available and just does not know what to do with it.
Officially, Oracle 26ai was started with Autosys 24.2
https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/autosys-workload-automation/24-2-00/release-notes-24-2-00/ae-compatibility-matrix/autosys-server-database-support-matrix.html

I would suggest you move to the 24.2 installer and that should resolve your issue.
If you must try this, the only possible way around this would be to set an environment variable.

# Try adding this to skip pre-install DB validation if supported
IA_AE_SKIP_DB_VALIDATION=1

But please note you will be setting up an unsupported combination, and that will limit your support.

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Pothen Verghese]

Hi,

Thanks for the prompt response. We tried running the install after exporting the above mentioned environment variable and hit the same error. It appears we can't skip the DB validation.

Please note the value returned by the query with correct string shows the exact same value on both Oracle 23ai as well as Oracle 26ai. Below is the output for 26ai

SQL> SELECT VERSION FROM PRODUCT_COMPONENT_VERSION WHERE PRODUCT LIKE 'Oracle AI Database%' AND ROWNUM=1;

VERSION
--------------------------------------------------------------------------------
23.0.0.0.0

So this is not really a DB version issue, but how the query is written in the installer. May be we will get the latest release of AE and try.

Thanks again

Pothen

-------------------------------------------

[Chandrasekaran Venkataraman]

Hi Pothen,

Best bet is to go with v24.2. Don't try to install v24.1 by skipping the DB check because you can't bring the Scheduler and Application server post install; it runs a more specific SQL to validate the DB version. 

We hit this problem on our operational v24.0.1 recently after Oracle DB team put Oracle patch: 38743669. The Scheduler and Application server refused to start with the following message:

03/26/2026 23:53:37]      CAUAJM_I_40275 Log Rollover level set to <MIDNIGHT,SIZE(100),PURGE(7)>.
[03/26/2026 23:53:37]      CAUAJM_I_40244 EnableIPCaching value set to <0>.
[03/26/2026 23:53:37]      CAUAJM_I_40244 AggregateStatistics value set to <1>.
[03/26/2026 23:53:37]      CAUAJM_I_10655 System is running in single server mode.  Event server:  AUTOSYS_TST.
[03/26/2026 23:53:37]      CAUAJM_E_18400 An error has occurred while interfacing with ORACLE.
[03/26/2026 23:53:37]      CAUAJM_E_18401 Function <execute> invoked from <CheckSkipCountSupport> failed at <1,238>
[03/26/2026 23:53:37]      CAUAJM_E_18416 Event Server: <AUTOSYS_TST>  Failed Query: <SELECT substr(product, 17, 4) from PRODUCT_COMPONENT_VERSION WHERE PRODUCT like 'Oracle Database %%'>
[03/26/2026 23:53:37]      CAUAJM_E_18402 ORA-01403: no data found

Since we did not have an option to rollback the Oracle patch (multi-tenanted) and had a narrow window to reach out to Broadcom Support, we resorted to a workaround:

The workaround is to create the following table, views and synonym under both AUTOSYS and AEDBADMIN schemas;

create table AUTOSYS.PRODUCT_COMPONENT_VERSION_test as  select * from PRODUCT_COMPONENT_VERSION;

update AUTOSYS.PRODUCT_COMPONENT_VERSION_test set PRODUCT='Oracle Database 23ai EE Extreme Perf' where product like '%26ai%';

create or replace view AUTOSYS.PRODUCT_COMPONENT_VERSION as select * from AUTOSYS.PRODUCT_COMPONENT_VERSION_test;

create table aedbadmin.PRODUCT_COMPONENT_VERSION_test as  select * from PRODUCT_COMPONENT_VERSION;

update aedbadmin.PRODUCT_COMPONENT_VERSION_test set PRODUCT='Oracle Database 23ai EE Extreme Perf' where product like '%26ai%';

create or replace view aedbadmin.PRODUCT_COMPONENT_VERSION as select * from aedbadmin.PRODUCT_COMPONENT_VERSION_test;

GRANT SELECT ON aedbadmin.PRODUCT_COMPONENT_VERSION TO autosys;

commit;

With the above workaround, we were able to start the Autosys engines. 

Broadcom engineering provided a fix on v24.0.1 to remove this check at Scheduler/Application server startup. 

I am not recommending this workaround but if anyone else runs into this, they can get by using this workaround for sometime. 

HTH,

Chandru V

[Venkateshwar Goud Badrigari]

We've addressed this in the latest AutoSys Workload Automation release (v24.2). You can resolve the conflict by either using an older Oracle version or upgrading your AutoSys environment to v24.2.

------------------------------
​Regards,

Venkateshwar Badrigari
Lead Software Engineer
CA Technologies - A Broadcom Company
[e-mail]
------------------------------

[Pothen Verghese]

Hi Guys,

Thanks for the insight. It is clear now and we anyway were unable to install AE 24.1.x on ORA 26AI. 

We have no other choice but to follow what is stated in the compatibility matrix and confirmed by all of you.

Thanks and Regards

Pothen

-------------------------------------------