Slowness and 500 Timeout error when opening deliveries or delivery templates
This article discusses the issue where on-premises instances using Oracle as a database encounter slowness and a 500 Timeout error when opening deliveries or delivery templates.
Description description
Environment
Adobe Campaign Classic v7 (ACC v7) with Oracle DB connection
Issue
For on-premises instances that use Oracle as a database, opening deliveries or delivery templates is slow and results in 500 Timeout errors.
Steps to reproduce:
- Connect to Adobe Campaign Console on an on-premises instance that uses Oracle as a database.
- Open a delivery or a delivery template. The console freezes, and after a couple of minutes, a 500 Timeout error is displayed.
- Confirm with your Oracle DBA that while reproducing the slowness there’s a query on
NmsDeliverytable that is long. - This can be noticed with Verbose and TraceFilter logs enabled in the web process as well. Refer to Log Precisionin Campaign Classic v7 documentation to enable it.
NOTE: Verbose and TraceFilter logs should be enabled only on Dev/Stage instances and not in Production.
Resolution resolution
To resolve the issue, follow these steps:
- Manually change the
nms:deliveryform by replacing:@linkedDelivery-id,linkedDelivery/*,
with@linkedDelivery-id,linkedDelivery/@id, - Save the form.
- Disconnect and reconnect to the Adobe Campaign Console to see the difference.
Note:
- The query will still exist, but it will not load all the columns.
- The above solution should be first confirmed in Dev and Stage before being applied to Production.
- Engineering will provide this improvement under a fix in a future patch.
Cause
The slowness issue is caused by a large query that Adobe Campaign runs on the Oracle database server.
The product generates the query and loads excessive data because there is a wildcard on linkedDelivery/* in the nms:delivery form.