Common Problems - Forms Record and Playback

Forms record and playback is more dependent on Oracle software than is the DataLoad Macro functionality. This is because while DataLoad prepares the playback file it is the Oracle Forms runtime than loads the file. However, problems can also arise from user errors and problems in DataLoad, and the following sections describe the most common issues.

Playback Doesn't Work

Where no playback occurs it is almost always a problem with the setup. A small amount of setup and configuration is required to enable playback and that is described here. If playback does not work at all please check that the setup has been performed correctly.

Oracle Forms Bugs and Issues

• Picklists/List of Values. Oracle Forms support for pick lists (list of values) on playback can be poor and problems have been identified where either the value is not inserted into the field or the wrong value is inserted. To avoid such problems it is strongly recommended that data is not picked from a list of values in order to populate a cell during forms recording. Instead, the data should be directly typed into the field. Typing the data into the field also makes for a more performant playback and often makes editing the load easier. Where a pick list must be used the behaviour of the pick list on playback should be carefully tested to ensure the field is populated with the correct data.

• FRM-92100. Forms 6i, 6.0.8.8 or 6.0.8.14.2, Applications 11.5.1. When playback finishes the server process terminates, the client session disappears and there maybe a FRM=92100 error in the Java console. The full text of the error in the Java Console is a follows:

FRM-92100: Your connection to the server was interrupted.
java.io.EOFException
at java.io.DataInputStream.readUnsignedByte(Compiled Code)
at oracle.forms.engine.Message.readDetails(Compiled Code)
at oracle.forms.engine.Message.readDetails(Compiled Code)
at oracle.forms.net.StreamMessageReader.run(Compiled Code)

This issue is fixed by recording the forms session at the same time as running the playback. See the Setup page for information on using the record and play parameters at the same time.

• FRM-41096. Forms 6i, patch 5a, 6.0.8.14.2, Applications 11.5.1. If there is a resize command for the Navigator window then a playback will stop at that point with the following error message -  "FRM-41096 Cannot resize view: Invalid Size". Commands such as the following cause this error and should be manually removed from the forms load file:

WINDOW FNDSCSGN NAVIGATOR RESIZE 5900 4500 1

• Incorrect Recordings. The file recorded by Oracle Forms is missing the first keyword on each line, thus rendering the file useless. This behaviour has been seen on Windows and Solaris servers, but may affect other platforms too. The problem is introduced by the later Developer 2000 1.6.1 (Forms 4.5) patches and has been found to be an issue after Patches 14 and 16, but again may be introduced by other patches too.

• Large load failures. Some loads will work perfectly for relatively small loads, say less than 100 records, but fail for larger loads, say over 300 records. When the load fails there is often a network error but other errors may be reported. This is caused by a bug in the particular form or the forms runtime software. The cause is most often a memory issue and the entry of multiple records means the memory issue builds up over time and eventually an error results. It is often the case that such errors are not only 100% reproducible but the error will often occur after the same number of errors on every load. The solution to this problem is to upgrade the form or forms software, or both.

• Other Fixes for Playback Failures. If none of the suggestions above help and you can rule out User or DataLoad issues, see below, try the following:
  
  • Minimise the Oracle Applications Window during Playback. This helps fix random playback errors that appear to be caused by the forms client not being able to keep up with the playback. This can help when the playback fails after just a few records. Minimising the Oracle window as soon as it opens fixes this issue. If the Oracle window is minimised you can check the load progress by monitoring the file that Oracle records to during playback.
    
  • Use oracle.forms.engine.Main instead of MainRT. The MainRT Java class can occasionally cause issues. If persistent playback errors occur try reverting to the Main Java class. To do this remove "&code=oracle.forms.engine.MainRT" from the playback URL/profile value or remove the "&config=playback" parameter if you use that to cause MainRT to be used. This results in the forms not being displayed during playback however they are displayed when the playback stops, either because the load finished or an error occurred.

User Errors

It is easy to build a forms playback file, however certain 'rules' must be followed when recording data entry that will later be edited in DataLoad. Where these rules are not followed you cannot be sure that the load will work correctly or at all. It is therefore essential that the file is recorded as described in the rules pages.

DataLoad Issues

If you suspect DataLoad is incorrectly editing the file then DataLoad Support need to be able to identify the problem. It is also worth proving that the problem is caused by DataLoad and not by an Oracle issue. The process for doing this is as follows.

First, record the entry of your data in Oracle. For this test it is worth recording around 5 records of data being entered. Now play that file back without editing it in DataLoad. If the values to be entered in Oracle Applications must be unique edit the file in a text editor and change only the values to be entered. Find the values you entered when recording the file and change just those values to be something else. If that file plays back correctly you have proved that Oracle playback in this form is working correctly. However, if this playback fails then the problem is with Oracle forms playback and the issue should be reported to Oracle Support.

Where the file that was not edited in DataLoad does playback correctly but an edited version does not replay please email both files to DataLoad Support. DataLoad Support will analyse the differences in the files and report back why the edited version does not replay. If applicable a fixed version of DataLoad will be produced that does edit the file correctly.