Concurrent program errors when trace is disabled and completes successfully after turning trace on
On an upgraded environment (from 12.1.3 to 12.2.9) a concurrent program is erroring out when trace is disabled. Turning trace on resolves the issue.
We didn't encounter this on 12.1.3. The database is also upgraded from 12c to 19c.
Is this a known issue? We are concerned that keeping trace on is not a long term solution as it will create performance and space issues.
Thanks!