grand_national
Member
Forgive me for posting to multiple forums.
Maybe the CNC forum is more appropriate since I now have more information about this issue.
JDE: 9.1, TR 9.1.3, SS DB
Maybe the CNC forum is more appropriate since I now have more information about this issue.
JDE: 9.1, TR 9.1.3, SS DB
===================
We needed a table trigger to insert into a log table.
The TER code was changed.
The change was built and deployed.
Everything worked as expected.
--
We now want to turn off that table trigger insert.
The TER code was commented out.
The change was built and deployed.
*Except, the table trigger is still now in place; inserts still occurring into log table.
--
We noticed on the initial implementation of the trigger code, the jdbtrg2.dll file was updated in the pathcode folder on the enterprise server.
Our recent change to comment out the trigger code, did not update this file.
--
We did not do the initial build and deployment ourselves, so we are 100% familiar with the process which was used.
--
[update: Oracle has acknowledged a bug] ( Doc ID 2120700.1 ) Bug 18163361
This is what is provided:
Workaround
Run a manual generation of the table followed by a clear cache of the serialized objects in server manager.
The table with the trigger is fully populated with data.
Gen'ing the table to clear the table which I don't want to do.
If the problem is with the serialized object code, when couldn't we just serialize that TER code?
If so, how would we do that differently from doing our normal package build of the table object, which doesn't work?
--
Thanks in advance for all help on this.
We needed a table trigger to insert into a log table.
The TER code was changed.
The change was built and deployed.
Everything worked as expected.
--
We now want to turn off that table trigger insert.
The TER code was commented out.
The change was built and deployed.
*Except, the table trigger is still now in place; inserts still occurring into log table.
--
We noticed on the initial implementation of the trigger code, the jdbtrg2.dll file was updated in the pathcode folder on the enterprise server.
Our recent change to comment out the trigger code, did not update this file.
--
We did not do the initial build and deployment ourselves, so we are 100% familiar with the process which was used.
--
[update: Oracle has acknowledged a bug] ( Doc ID 2120700.1 ) Bug 18163361
This is what is provided:
Workaround
Run a manual generation of the table followed by a clear cache of the serialized objects in server manager.
The table with the trigger is fully populated with data.
Gen'ing the table to clear the table which I don't want to do.
If the problem is with the serialized object code, when couldn't we just serialize that TER code?
If so, how would we do that differently from doing our normal package build of the table object, which doesn't work?
--
Thanks in advance for all help on this.