Friday, 24 April 2015

introspective logging–why do I get this?

This tells you a lot about what is going on with a running UBE

Job Is Not Responding 
Job Is Not Responding

Please look for the highlighted fields, correct the entries, and resubmit your request.

 

 


 


image


The above is annoying, but sensible.  The job only is looking for these interrupts (when you say “hey enable logging”) when JDE is in ER and looping through it’s own engine.  When the UBE is running a massive SQL statement, it’s not out there listening for you to tell it to enable logging. 


Generally if you get the above warning you need to go into EM (if you are oracle or guess if you are other platforms [just kidding there are some other good monitoring tools out there'] and see the statement that is running.  What you need to do is request logging / introspection when the UBE is likely to run some ER… / runtime engine code.


If the SQL statement takes 20 mins to run, you are not going to get introspective logging for ages…


image

1 comment:

sandeep said...

hi i am getting the next id error in oracle JDE its is also prompting please look for the highlighted fields correct the entries and resubmit the request.

could you please help me in that.

Extending JDE to generative AI