ORA-04045 error on a 10g form

Question

I have a form 10g that runs fine on one server, then when I move the FMX over to another 100% identical server, I get the ORA04045 error as soon as i run the form. I've recompiled the form and still get the error.
The problem is that teh message on the form is truncated and I can not see which object is causing the issue.
Anyone have any ideas?

Answer 1

then when I move the FMX over to another 100% identical serverThis is a common miss-conception - you should ALWAYS compile your form on the server it will run from.
I've recompiled the form and still get the error.My first suspicion is that the servers are not 100% identical. Rather than a SQL Trace, I suggest you use the Forms Runtime Diagnostics (FRD) to trace just the Forms Session. You might need to modify the default.env and formsweg.cfg to enable FRD. Double check with your App Server admin to see if the "FORMS_TRACE_DIR=" variable is set in the DEFAULT.ENV. As long as this is set, you can enable FRD through the Forms app URL. Start your application and then add "record=collect log=<your_file_name_here.txt" to the URL to start the FRD trace. You could also have your admin modify the formsweb.cfg to create a config just for FRD. For example, I modified my local formsweb.cfg and added the following section so I can run FRD on specific forms from my workstation.
[my_frd]
otherparams=record=collect log=my_frd.txt
This setting is dependent on the FORMS_TRACE_DIR= variable in the default.env.
With this added to the formsweb.cfg, you can enable FRD by adding "config=my_frd" to the url instead of explictly passing record= and log= to the URL.
The log file produced by the FRD is quite large but, if you end your application after you receive the error, you could go to the end of the log file and work your way back until you find the error.
Hope this helps,
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.