Hello,

Here the informations of CDB CDB1 and PDB PDB1 , where it didn"t work in that environment:

CHECK_NAME           INST_ID Parameter                 Session Value        Instance Value
----------------- ---------- ------------------------- -------------------- -------------------------
Hidden Parameters          1 _system_trig_enabled      FALSE                FALSE

In a working environment, the parameter "_system_trig_enabled" is set to TRUE :

CHECK_NAME           INST_ID Parameter                 Session Value        Instance Value
----------------- ---------- ------------------------- -------------------- -------------------------
Hidden Parameters          1 _system_trig_enabled      TRUE                 TRUE

Before I asked the question in the community, I had asked questions internally in the database team as to whether something had been installed or changed in this container database: NO

Now after your question regarding this parameter, the feedback came immediately: YES

JVM was installed, but the container database (CDB) was not restarted, we have the following JVM install instructions :

startup mount
alter system set "_system_trig_enabled" = false scope=memory;
alter database open;
@?/javavm/install/initjvm.sql
@?/xdk/admin/initxml.sql
@?/xdk/admin/xmlja.sql
@?/rdbms/admin/catjava.sql
shutdown immediate;

After the parameter "_system_trig_enabled" was set again, The environment variable ORACLE_PDB_SID work again.

Thank you very much for your great support.

But the parameter "_system_trig_enabled" has other effects, I found also those MOS note :

Health Check Alert: Set the database initialization parameter '_system_trig_enabled' to TRUE (Doc ID 957512.1)