Logs consist of Broker, Manager and Database logs. There can be sub-nodes such as Access, Error and Admin logs. Each log consists as follows:
10.1. Broker Log
The access log file records information about application client access, and it analyzes and outputs what is saved with the name of " broker_name.access." In addition, if the LOG_BACKUP parameter is configured to " ON" in the broker configuration file, the information about the termination date and time is stored additionally to the log file upon successful termination of the broker operation.
The error log file records information about errors that occurred during the client's request processing and is saved with the name of " broker_name_app_server_num.err."
The following is an example and description of an error log:
Time: 02/04/09 13:45:17.687 - SYNTAX ERROR *** ERROR CODE = -493, Tran = 1, EID = 38
Syntax: Unknown class "unknown_tbl". select * from unknown_tbl
Error Log Trace
You also can trace the broker error log for SYNTAX ERROR Type.
Click the [Trace Error] action, will pop up the error trace result dialog.
The admin log records the history about the service operation and termination.
10.2. Manager Log
The access log files records information about the CUBRID Manager access. You can see user accounts, operation history, and time when operations are performed.
The error log file records information about errors that occurred while connecting the CUBRID Manager.
10.3. Database Log
This admin log records information about errors that occurred while server is running. The format of output file is as follows: < database_name> _< date> _< time> .err.