Oracle Database / Accounts, Security & Access
ORA-28365: check the keystore in the intended container
Encrypted data may be inaccessible when the required keystore is closed or unavailable. Confirm which database and container require the key.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT con_id, wrl_type, status, wallet_type FROM v$encryption_wallet;Read the result
Status describes the visible keystore state, which can differ by container and configuration. It does not establish that the required historical key is present.
Resolve and verify
Have the authorized key administrator restore access through the documented keystore process. Validate encrypted object access and recovery-key backups afterward.
Operational precautions
Do not copy wallets from another database or place keystore passwords in SQL scripts and tickets.