Processing Options values loss at runtime

Hi List,

We've been running live in production with our new Xe SP23_Q1 platform since Tuesday.
Since that day, i had several complete loss of processing values in some versions.
It happens only in some versions (not all the version of an application), when it happens all the values are blank (not only some values). And it's not values that has gone during the installation process. There were here, people used the versions, but in the middle of the day, values are gone.
I had the problem on several versions of P4210, P42040, P4205, ...
So far i had the problem twice on the same version (of P4210). I had put the values back, they were well here and people worked with it, and 2 days after, they all disapeared again.
I don't think it could be someone erasing it by mistake because we have processing options security, and in addition, we have a bug in web and we cannot even see the processing options values (even user that should have the right to).

Any idea of what's going on ?
It's a real pain in the ass because i have to put back all the values with hand (as values are recorded into BLOB, and so i cannot use sql) !!

Thanks for your help,

Rgds,

Hi guys,
I am getting the same issues here right now when we port over from one environment to another. It only occurs on this particular application. I tried mapping the processing option back to the application and tested it but all I get is the same results: Processing Options Value Blank.

Anybody has a solution for it? Would really appreciate it.

Adrian
Technical Consultant
OneWorld

Hey guys,
It's so silly of me. The reason why the Processing Options Value was not passed in is because the Form Interconnect that calls the internal form was looking at a Version that does not exist.

Adrian Gan
Technical Consultant
OneWorld

Hi list,

Here are some news about that issue.
After more than a year, the case is closed. As far as Oracle know, we are the only customer that met this issue.
Oracle couldn't discover what was causing the problem.
What we know is that sometimes, the read of po values was returning a zero lenght string. And the po engine in web is designed in that case, to overwrite the povalues (a zero length is considered to be like corrupted, because even when all your PO values are null, you should get a string with the pipes used as delimiter).
So the thing is that there was a problem reading po values (but we couldn't discover why at a moment the request returned some wrong result), and then the system was updating the po values to null. And then, on the next readings of povalues, the values were all null.

For several weeks, we were meeting several PO losses per day.

Oracle had to develop a workaround in the java classes (especially the poengine class) to do the following :
- if a read of po values returns a zero length string, then they try to do other fetches to read it again.

Since the modified java classes have been put on the websphere servers, we didn't notice any new PO values loss.

Many directions were explorered (jde engine, oracle database, jdbc, ...) but we still don't know why it's happening.
(For instance :
- we checked if something (from the inside or the outside of JDE) was updating the povalues. But it's well the JDE engine
which was updating the po values, after the po reading.
- we installed some Oracle patches with no results.
- Some oracle jdbc specialist noticed that the way connexions were called is not the last recommendation way to do it, but due to multiplatform concern, it couldn't be changed to test).

Oracle opened a SAR, in order to include the workaround code in the next service pack probably (SP24).

Here is the number in case some are interested :
8845083

hi, we are on SP23 O1 and also encountered the same issue that Processing Option value lost. May I know the fix from Oracle? Is it on SP23 or SP24 as per SAR#8845083?