ORG 1.0 User Guide

4. Diagnostics and Troubleshooting

4.1 Potential Pitfalls

The ORG system does not return information about the status of a request itself, rather it returns the Oracle server response to a request. This is usually useful information but not always. For example, when an update is performed, each field in the update form is updated, whether a change was made or not. If inappropriate data is entered in a field, the server will reject the field displaying something cryptic like this:

1 row updated 1 row updated 1 row updated set install_date = 'dddddddddddf' * ERROR at line 2: ORA-01401: inserted value too large for column 1 row updated 1 row updated

With some effort, you can determine that the fourth field was rejected, but this could be handled nicer and might be a future enhancement.

ORG provides no support for restricting field value options or rejecting invalid values from the HTML/CGI end of things. It is up to the Oracle developer to establish field constraints.

4.2 HTML problems

Building input forms and search documents can be time consuming and is the first place problems are likely to occur. Some common errors are:

Refer to the templates and verify your HTML tags look like those in the template or example listing. Double check your Oracle table.

4.3 Problems between gateway and tables

Any Oracle table intended for use with ORG must have as its first field a unique identifier. This can be generated any way you like but I recommend using a sequencer. When adding a new record to the table, there must be a field for the unique identifier which tells Oracle to generate a new ID for the new record.

Other problems that can arise:

Refer to Oracle manuals for more information.

<< >>