E1: 17: Cache Cursor Not Properly Closed In Contract Revisions (P1721) (Doc ID 3045769.1)

Last updated on SEPTEMBER 06, 2024

Applies to:

Symptoms

When updating contracts through the application P1720 (Work with Contracts), the cache cursor is not being properly closed, and as a result, the cache records are also not cleared after executing cache terminate all.  The following activity can be seen in the log after cache terminate all is processed:
Starting jdeCallObject  hCache:[000001a67d0412a0] Nm:[1SCEDTL_3_OUSPXK7I] Recs:2 Curs:1 Hnds:10 Cchs:4 TERM all Usr: <Name unavailable>  Env: <Name unavailable>
With records and caches still open, this could lead to potential memory issues when users process larger data sets of records. 

Steps
1. Enable the data pointer trace in jde.ini
2. Launch P1720 and inquire a contract
3. Go to contract revision through row exit (Row Contract Detail)
4. Edit the “Customer PO Number” for line “3” as “Test ABC” and  exit the row (click on the line row 4)
5. Edit again the “Customer PO Number” for line “3” as “Test XYZ” and  exit the row (click on the line row 4)
6. Save the transaction and capture the JDE Debug log

Changes

Cause

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