Monday, May 5, 2014

Oracle Web ADI View Log, clear log

Oracle Web ADI

 

 

I have realized after big struggle that oracle provided simplest method to see Web ADI log file, otherwise each time we have to downloading huge file to local machine is very cumbersome, and also viewing log file using putty editor is not easy for all the developers

BNE Servlet helps you to clear cache, you can view log-First, log-last, log-search options, I have explained below

 

For 11i

http://hostname:portnumber/oa_servlets/oracle.apps.bne.framework.BneAdminServlet

 

For R12

http://hostname:portnumber/OA_HTML/BneAdminServlet

Note :- It’s always better to login using system administrator in first tab then open above URL in next tab are same window, so that you no need to re-enter credentials


With BNE Servlet you can clear the BNE cache, click the "clear-cache" link.
You can also monitor the size and location of your log file, or change the log level.


Valid arguments to BNE servlet


bne:action= log-all | log-first | log-last | log-marker | log-search 
Additional Option: bne:lines = <number> (defaults to 100 if not set) 
Additional Option: bne:text = String (useful for searching or marking the log file) 
bne:action= log-set-level (Current JVM only) 
Required Option: bne:log-level=REQUIRED | CRITICAL ERROR | ERROR | WARNING | INFORMATION | DETAIL | TRACE 

bne:action= cache-clear (Current JVM only) 
bne:action= site-properties-clear (Current JVM only) 
bne:action= async-uploads (all async uploads started in the last 24 hours) 
Additional Option: bne:async-job-number = number (Report on a particular job) 
Additional Option: bne:action2=upload-cancel (Cancel a particular job)
bne:action= delete job history (clear job history > 7 days old) 
bne:action= delete performance statistics 
bne:action= threads (Current JVM only)

In R12 oracle provided default options, once BNE servlet opens you can choose whatever you want, if you are looking any specific option simply you can modify your URL based on above arguments.

 

1 comment:

  1. This comment has been removed by a blog administrator.

    ReplyDelete