ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

DB Archive fails with 'out of memory for query result'.

book

Article ID: 199086

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine

Issue/Introduction

The DB Archive is failing with an out of memory error when it's trying to archive client 0.

20200608/161522.386 - U00009909 TRACE: (BINDPAR:  RT_AH_Idnr        )                                          0x7f1647108d64 000004
                                00000000  A288BC01                             >¢ˆ¼.<
20200608/161522.386 -                                        >29132962<
20200608/161522.386 - U00009909 TRACE: (BINDPAR:  RT_Type           )                                          0x7f1647108d68 000003
                                00000000  4C4F47                               >LOG<
20200608/161522.386 - Select RT_MsgNr, RT_MsgInsert, RT_TimeStamp, RT_Content from RT where RT_AH_Idnr = ? and RT_Type = ? order by RT_Lnr ASC
20200608/161522.386 - U00029179 PGSQRY: 'PGSQuery::ExecuteX(BEGIN)'
20200608/162109.763 - U00003590 UCUDB - DB error: 'out of memory for query result', '', '', ''

 

Cause

This was caused by a very large report of a proxy agent that contained 3.5 million lines.

20200806/140742.032 - U00009909 TRACE: (DB-DATEN: AH_OH_Idnr ) 0x7f3421015100 000004 00000000 188C0100 >.Œ..<

20200806/140742.032 - >101400<

20200806/140742.032 - U00009909 TRACE: (DB-DATEN: AH_Name ) 0x7f3421016365 000017 00000000 5445435F 50524F58 595F5052 4F445F31 >PROXY_AGENT< 00000010 31 >1<

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Database: PostgreSQL

Resolution

The RT record needed to be deleted manually and then the DB Archive could be resumed.