Oracle Forms Debugging
Cheatsheet: Oracle Forms Debugging
Cheatsheet: Oracle Forms Debugging
Hi Forms family! AuraPlayer is back again and dedicated as always to gathering useful tips & tricks for your Oracle investments.
Oracle Forms has been around for decades but when it comes to debugging errors it remains a mystery to most. At least in our experience.
This blog is made for anyone who is knee-deep in the challenges of Oracle Forms debugging. We are here today with some fresh testing solutions. In addition, we’re sharing a general treasure map for investigating Forms errors to make your life easier!
Today, we will cover:
What are the common Oracle Forms, Reports and Weblogic log files?
What are the locations of common log files?
Tips on how to look for errors in Enterprise Manager.
What is AuraTester? How can it help us prevent production issues and monitor critical application workflows?
Let’s Get Down To Business
We’ll start by looking at what parts make up a Forms server:
- Database
- Weblogic Middleware
- HTTP server
- Forms server
- Reports server
- Weblogic Admin server
- Weblogic Node manager
Any error that we receive feels like looking for a needle in about 7 haystacks. Below is a cheat sheet of where to find the log files for each layer of the Oracle Forms application and how to test your application quickly and effectively.
Firstly, you will find all documents below starting from the top-level folder:
For example: C:/Oracle/user_projects/domains/frdomain
After that, you can find the log files for each of the relevant modules. Please fill in your directory, using the examples below:
For AdminServer | /servers/AdminServer/logs For example: C:/Oracle/user_projects/domains/frdomain/servers/AdminServer/logs |
For Forms | /servers/WLS_FORMS/logs For example: C:/Oracle/user_projects/domains/frdomain/servers/WLS_FORMS/logs |
For Reports | /servers/WLS_REPORTS/logs For example: C:/Oracle/user_projects/domains/frdomain/servers/WLS_REPORTS/logs |
For HTTP Server | /servers/OHS1/logs For example: C:/Oracle/user_projects/domains/frdomain/servers/OHS1/logs |
For Standalone Reports server | /servers/repserver1/logs For example: C:/Oracle/user_projects/domains/frdomain/servers/repserver1/logs |
For Nodemanager Log for OHS | /servers/ohs/logs For example: C:/Oracle/user_projects/domains/frdomain/servers/ohs/logs |
For formsTool | /servers/forms1/logs For example: C:/Oracle/user_projects/domains/frdomain/servers/forms1/logs |
You may also want to look for the following in Oracle’s Enterprise Manager Console:
- Errors
- SQL statements
- Trace files


Debugging errors in production can be a tricky business. It’s always best to take preventative measures before using the application to begin with. Wouldn’t you agree that it’s always better to have your system functional and load tested before going live and then monitor your environment to get notified about new errors before they occur. When it comes to QA and testing Forms and Reports specifically, there are not a lot of 3rd party tools that help us achieve successful results and deliver projects on time.
AuraTester, a QA automation testing tool, was created specifically for Oracle Forms and EBS applications. It’s a user-friendly, testing tool that automates Oracle Forms and Oracle EBS functional tests. It also builds comprehensive testing groups, and validates projected results.
In addition, you can schedule automated health-checks to ensure system stability, integrate with any existing testing framework (such as Taza, Junit, WebLOAD, Jenkins, JMeter, and many more!), as well as trigger alerts (such as expected time response and specific data values). Feel free to download our comprehensive guide to Oracle Forms Testing here.
As always, feel free to reach out for a free consultation or if you run into any trouble during your Oracle Forms upgrade – Book a session here!
We hope you enjoyed our blog and stay tuned for more coming soon. For more information on debugging and AuraTester, click here .
Happy Debugging!