E_AE_Create_Database_Error - during the installation - ORA-28374: typed master key not found in wallet
search cancel

E_AE_Create_Database_Error - during the installation - ORA-28374: typed master key not found in wallet

book

Article ID: 257566

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

We are receiving the error while installing the application.

2023-01-09 11:20:08,585 [Thread-30] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - INSERT INTO ujo_alamode(int_val, str_val, type)
2023-01-09 11:20:08,585 [Thread-30] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) -             *
2023-01-09 11:20:08,585 [Thread-30] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ERROR at line 1:
2023-01-09 11:20:08,585 [Thread-30] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ORA-28374: typed master key not found in wallet

 

Environment

Release : 12.1

Resolution

The logs show that the AE installer connected to the db without issue.
It created tables.
But it could not insert any data into the tables.
Example:

2023-01-09 11:20:08,585 [Thread-30] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - INSERT INTO ujo_alamode(int_val, str_val, type)
2023-01-09 11:20:08,585 [Thread-30] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) -             *
2023-01-09 11:20:08,585 [Thread-30] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ERROR at line 1:
2023-01-09 11:20:08,585 [Thread-30] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - ORA-28374: typed master key not found in wallet

During the install interview process the installer was told to NOT create the tablespaces.
This means the dba created them ahead of time.
We recommend you engage the DBA to see if perhaps they were created with some option that might explain the above.
And/or look at the overall database as to why the above is seen.
You should be able to replicate the above error easily.
Just create a table and try to insert data into it.
Again, the dba should be engaged to address the above as the error is coming from Oracle directly.