XML export memory error: export exceeded available memory

Exporting a large table with thousands of records without proper filtering, causing the entire dataset to load into memory simultaneously. (high likelihood)

Exporting update sets containing numerous large records or records with extensive field data that exceed available heap space. (high likelihood)

Insufficient JVM heap memory allocation on the ServiceNow node processing the export request. (medium likelihood)

Concurrent memory-intensive operations running on the same node during the export process, reducing available memory. (medium likelihood)

Records containing large attachment data or long text fields that consume excessive memory during XML serialization. (low likelihood)

Step 1: Check the application logs at System Diagnostics > Log > Application Log to confirm the exact timing and context of the memory error.

Step 2: Navigate to the table or update set causing the issue and review the total record count and estimated data size to assess export scope.

Step 3: If exporting a table, use the Advanced view to add filters reducing the record count to under 10,000 records per export batch.

Step 4: For large exports, enable chunked exports by setting the system property 'glide.export.chunk_size' to 5000 or lower in System Properties.

Step 5: Split large update sets into smaller components using Update Set utilities or export individual application files separately.

Step 6: If memory issues persist, coordinate with your ServiceNow administrator to schedule exports during low-usage periods to maximize available memory.

Step 7: For enterprise instances, consider requesting node memory increases through ServiceNow support if exports consistently fail due to legitimate business requirements.

Step 8: Test the modified export approach with a small subset first, then gradually increase batch sizes until you find the optimal balance.