Oracle Extension 3.1.3 - ORA-00904 "MAX_AUDIT_SIZE" and ORA-00942 Warnings

DB1 — Mon, 03 Aug 2026 09:14:25 GMT

Hi Community,

I'm looking for guidance on an Oracle Database extension issue that we're seeing in a pre-production environment.

Extension Version:

Oracle Database Extension 3.1.3

Symptoms:

The monitored endpoint is reachable and metrics are being collected, but the extension intermittently reports the following warnings:

1 ORA-00904: "MAX_AUDIT_SIZE": invalid identifier

2 ORA-00942: table or view does not exist

The warning appears as a query failure rather than a complete connection failure.

What we've checked so far:

Database connectivity is working.
The Oracle monitoring user permissions have been reviewed.
DBA team has confirmed the monitoring account has the same permissions as our production environment.
The issue is limited to this environment; production is not reporting the same warning.
We are using the standard Dynatrace Oracle extension configuration.

Questions:

Has anyone seen MAX_AUDIT_SIZE related errors with Oracle Extension 3.1.3?
Is this typically caused by:
- Oracle version differences?
- Auditing configuration differences?
- Missing Oracle objects/views?
- Extension compatibility issues?
Is there a way within Dynatrace to identify the exact SQL query behind this warning?
Are there specific Oracle audit-related views or features that must exist for this metric to work?
Has anyone successfully resolved a similar combination of:

1 ORA-00904: MAX_AUDIT_SIZE

2 ORA-00942: table or view does not exist

and if so, what was the root cause

Any troubleshooting advice or experiences would be greatly appreciated.

Thanks in advance!

Re: Oracle Extension 3.1.3 - ORA-00904 "MAX_AUDIT_SIZE" and ORA-00942 Warnings

sujit_k_singh — Mon, 10 Aug 2026 03:33:14 GMT

Hi @DB1

I've seen similar errors when the extension executes queries against Oracle views or columns that are not available in a particular database version or configuration.

ORA-00904: MAX_AUDIT_SIZE usually indicates the extension is referencing a column that doesn't exist in that Oracle version or audit configuration.
ORA-00942 typically means the monitoring user cannot access a required table/view, or the object doesn't exist in that environment

To see the exact SQL statement failing on the database: Go to the ActiveGate running the Oracle extension and check the log file.
If you can identify the missing table/view or the query containing MAX_AUDIT_SIZE, that will likely point to the root cause fairly quickly.

Thanks

Sujit

topic Re: Oracle Extension 3.1.3 - ORA-00904 "MAX_AUDIT_SIZE" and ORA-00942 Warnings in Extensions

Oracle Extension 3.1.3 - ORA-00904 "MAX_AUDIT_SIZE" and ORA-00942 Warnings

Re: Oracle Extension 3.1.3 - ORA-00904 "MAX_AUDIT_SIZE" and ORA-00942 Warnings