My Oracle Support Banner

E1: TDA: Table Event Rule Causes Memory Violation and Error "bad pReportSpace in ubeReport_GetName" (Doc ID 2464093.1)

Last updated on OCTOBER 24, 2018

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms


A custom table trigger fails during execution with the following errors written to the debug log:

Line 414951: Oct 08 13:47:02.201893 - --UBE--[0]-- ERROR: bad pReportSpace in ubeReport_GetName
Line 427924: Oct 08 13:47:02.576334 - --UBE--[0]-- ERROR: bad pReportSpace in ubeReport_GetName
Line 433247: Oct 08 13:47:02.967672 - --UBE--[0]-- EventRule : The ER line [52] for Event [13] in Section [ ReportSectionName] has caused a memory violation.
Line 433250: Oct 08 13:47:02.967675 - --UBE--[0]-- { "ERROR:", 30, 50, 1, 0, 0,
Line 433252: Oct 08 13:47:02.967677 - --UBE--[0]-- { "EventRule : The ER line [52] for Event [13] in Section [ ReportSectionName] has caused a memory violation.", 30, 450, 1, 0, 0,



Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.