ORA-01435: "User does not exist" Error When Using Common User in Oracle Agent Collections (4376047)

The Oracle agent may trigger an error or alarm such as:

Failed to execute collection [DBO_Maintenance], reason=ORA-01435: User does not exist

This can occur during various collections, including:

• DBO_Startup
• DBO_Maintenance
• DBO_Instance_General

This issue typically arises when using a common user that was created with a non-common temporary tablespace.

The error is caused by creating a common user with a temporary tablespace that is not common across all PDBs. This often happens when the following command is used before user creation:

This command bypasses Oracle's safeguards and allows the use of local (non-common) resources, such as:

In this example, PDB_TEMP is not a common tablespace, which leads to the user being invalid in PDBs where PDB_TEMP does not exist.

Note: Using "_ORACLE_SCRIPT"=true is not recommended unless explicitly advised by Oracle Support.

1. Avoid specifying a non-common temporary tablespace when creating a common user.
2. Use a common tablespace such as SYSAUX, or omit the TEMPORARY TABLESPACE clause entirely.
   Recommended User Creation Steps
   

   CREATE USER C##USERNAME IDENTIFIED BY PASSWORD CONTAINER=ALL;
GRANT CONNECT TO C##USERNAME CONTAINER=ALL;

3. Complete the Agent Setup:
   • During the Oracle agent installation wizard, provide a SYSDBA account to grant necessary permissions,
     or
   • Run the permissions script manually using the newly created common user.

• You can verify which tablespaces are common by running the following query:

  SELECT tablespace_name, con_id FROM cdb_tablespaces;

• Ensure that the user is valid across all containers by avoiding local-only resources.
• If the issue persists, review the user creation script and confirm that no session-level overrides (e.g., _ORACLE_SCRIPT) were used.