Maintaining the SQL Error Log Tables:

Overview:

There are SQL procedures that run within the Oracle DBMS system that are called by EWDB API functions.

Some of these SQL procedures will log error information to a 'test' table within the DBMS The information is logged in a cryptic manner, but can be very helpful to developers, in conjunction with program log files, in determining what went wrong and how to fix it.

Maintaning the Test Table:

There are two maintenance duties required of the DBMS operator with respect to this test table: monitoring it, and cleaning it.

1. Monitoring the Test table

Occasionally (once a week), the operator should check the error log table:

- connect to the DBMS using "sqlplus" as the main EWDB user, and run the following command:

- select * from test;

- Save the output from the command.
- Analyze the output:

a) If there are no rows in the table, then everything is good and the operator's task is finished.

b) If the table is not empty, the operator may wish to alert the EWDB development team of potential problems, and send them the output from the SQL Query.

1. Cleaning the Test table

After saving the contents of the "Monitoring" SQL Query, the operator should clean the "test" table by deleting its contents, so as to prevent the table from accumulating size over time. To clean the table, connect to the DBMS using "sqlplus" as the main EWDB user, and run the following commands:

- delete test;
- commit;

Remember that the contents of the test table are most useful to developers when combined the the logfiles from applications. Please try to save application logfiles for at least a short time after providing "test" table contents to the EWDB development team.