Oracle Forms Server Troubleshooting

Jul 12 posted in Oracle (RSS), 226 views.

Oracle Forms Server Troubleshooting

Oracle Technical White Paper

1 CHECKING FOR FORM_SUCCESS AFTER CALLING A FORMS BUILT-IN

After calling a form, through the FORM_SUCCESS built-in subroutine to return a form can be expressed as a recent success of Boolean operations, its value is TRUE (success) and FALSE (failure, a serious error). If the built-in subroutine is not the successful implementation of, and should trigger FORM_TRIGGER_FAILURE exception handler.

FORM_FAILURE / FORM_FATAL

Which FORM_FAILURE is FORM_SUCCESS correspond to the results of the FORM_FATAL value TRUE (serious error), and FALSE (success, failure)

2 TROUBLESHOOTING WITH "QUICK AND DIRTY" TECHNIQUES

The four language skills: commenting out code, using the "message" built-in, using the "debug_messages = yes" runtime option, and using the "break" built-in.

a) Note that you suspect a problem of code

Comment out the line of code commented out with :"--", If you comment out a piece of code with the :"/**/". triggers and procedures for a complete unit, then at least you need to include the code:

null;

When the repair of the problem and identify the problem, when Department, do not forget to get rid of useless comment

b) the use of message built-in subroutines

For example:

message ( 'The table contains' | | to_char (empcount) | | 'employees');
synchronize;
message ( 'Runtotals =' | |: control.runtotals);
- Runtotals will be either "YES" or "NO"
synchronize;
message ( 'Beginning Runtotals program unit');
synchronize;

message can be specified in the message line displays the text, but also of any number and date values into the text type, variables remain outside the single quotation marks, use the "| |" to connect to other strings

synchronize the display screen and forms the internal state of synchronization to ensure that a message within the code displayed in the required position

pause can replace synchronize, it not only shows simultaneously, and the suspension of procedure, until the (mandatory) the user presses a function key until the

c) the use of the form "DEBUG_MESSAGES = YES" runtime option

Can be set from the menu: Tools -> preferences, can also be set from the command line:
On windows:
c: orantinifrun60.exe module = myform userid = scott / tiger
debug_messages = yes

On Unix:
f60runm module = myform userid = scott / tiger debug_messages = yes

d) the use of BREAK built-in subroutine

Interrupt table for the implementation and display the debugger, the user can through the debugger to view the form, program, global, system variables

- Today has been watching, and behind the notes are written by the way, because there is no time saved, resulting in loss of all data updates, it makes all the hard work of a few hours in vain! ;-(~~~~~~~~