Oracle Forms Builder crashes when opened Form / Canvas

Oracle Developer Form builder might crash when tried to open a form or canvas with possible error uiw60.dll.

Both the errors should be handled differently.

Form builder crashes when tried to open a form (.FMB)

1) This could be related to version mismatch between the FMB and form builder. Forms developer version should match the Oracle Application version.
2) Make sure all the suggested Oracle developer edition patches are applied to match with desktop OS (32/64 Bit).


Form builder crashes while opening Canvas

1) Canvas physical width and height should be in the limit of run time Window.
2) Open other canvases from same form or different forms and then open the canvas that's failing.
3) Place the form in directory where TEMPLATE.fmb and other dependent forms exists along with PLL's and try opening the canvas.
4) Delete all the Graphics from canvas and open the canvas.

FRM-40401: no changes to save

Error message can be suppressed by following ways

• Set system.message_level value before your commit_form or DML command. You can assign any value between 0 to 20 where 0 allows all error messages to be displayed where as setting to 20 shows most important message.
:system.message_level := 5;
• Use standard.commit instead of commit_form;

FRM-40301: Query caused no records to be retrieved fix

Step 1
Check if your data block query is correct. To do so, navigate to Help --> Diagnostics --> Examine on the toolbar. When prompted enter your database password. Check you last query using the SYSTEM block.



If your query retrieves correct data then go to below debugging steps else fix your query.

Step 2:
Debugging

1. Check the length of fields used in data block. If a non-database/database item is defined in the block and value passed exceeding its maximum length defined then query fails.

   Eg: Customer_Name defined max. length as 30 chars where as query populates more than 30 characters.

   
    
2.  Check if block has non database fields but set database item to yes.
3.  Check if all the required fields are populated else set required property to no.
4.  Check if initialization of form is done set-org-context-in-oracle-apps-11i/R12.

Hopefully above debugging steps would resolve the error.

APP-FND-01926 - The custom event WHEN-LOGON-CHANGED raised unhandled exception.

"APP-FND-01926 - The custom event WHEN-LOGON-CHANGED raised unhandled exception. ORA-06508 PL/SQL could not find program unit being called"

Usually this error occurs when opening Form in application.

This happens mostly after Upgrade/Clone of applications.

Reason being invalid objects in Custom.pll, form throws an error when opened.

This solution applicable in most cases when apps is cloned.

Compilation of pll's from Unix will compile only standard pll's. Custom pll's used has to be compiled manually.

To know existing custom Pll's open custom.pll in forms developer and expand Attached Libraries. The libraries you see there are probably the pll's that has to be compiled from Unix.

Compile custom pll's using the following command to generate plx.

f60gen module=.pll userid=userid/pwd output_file=$AU_TOP/resource/.plx module_type=library batch=no compile_all=special

Eg:

f60gen module=ABC.pll userid=APPS/PWD output_file=$AU_TOP/resource/ABC.plx module_type=library batch=no compile_all=special


For Upgrade

Check CUSTOM package body in custom.pll, you might have missed some objects that are referred. If any DB objects are missing, compiling (SHIFT+CTRL+K) form might help.