Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

Versions available for this page: CUBRID 8.2.1 |  CUBRID 8.3.0 |  CUBRID 8.3.1 |  CUBRID 8.4.0 |  CUBRID 8.4.1 |  CUBRID 8.4.3 |  CUBRID 9.0.0 | 



Error Message-Related Parameters

The following are parameters related to processing error messages recorded by CUBRID. The type and value range for each parameter are as follows:

Parameter Name

Type

Default Value

call_stack_dump_activation_list

string

NULL

call_stack_dump_deactivation_list

string

NULL

call_stack_dump_on_error

bool

no

error_log

string

cub_client.err, cub_server.err

error_log_level

string

SYNTAX

error_log_warning

bool

no

error_log_size

int

8000000

call_stack_dump_activation_list

call_stack_dump_activation_list is a parameter that specifies a certain error number for which a call stack is to be dumped as an exception even when you configure that a call stack will not be dumped for any errors. Therefore, the call_stack_dump_activation_list parameter is effective only when call_stack_dump_on_error=no. The following example shows how to configure the parameter so that call stacks will not be dumped for any errors, except the ones whose numbers are -115 and -116.

call_stack_dump_on_error= no

call_stack_dump_activation_list=-115,-116

call_stack_dump_deactivation_list

call_stack_dump_deactivation_list is a parameter that specifies a certain error number for which a call stack is not to be dumped when you configure that a call stack will be dumped for any errors. Therefore, the call_stack_dump_deactivation_list parameter is effective only when call_stack_dump_on_error=yes. The following example shows how to configure the parameter so that call stacks will be dumped for any errors, except the ones whose numbers are -115 and -116.

call_stack_dump_on_error= yes

call_stack_dump_deactivation_list=-115,-116

call_stack_dump_on_error

call_stack_dump_on_error is a parameter that determines whether or not to dump a call stack when an error occurs in the Database Server. If this parameter is configured to no, a call stack for any errors is not dumped. If it is configured to yes, a call stack for all errors is dumped. The default value is no.

error_log

error_log is a server/client parameter that specifies the name of the error log file when an error occurs in the database server. The name of the error log file must be in the form of <database_name>_<date>_<time>.err. However, the naming rule of the error log file does not apply to errors for which the system cannot find the Database Server information. Therefore, error logs are recorded in the cubrid.err file. The error log file cubrid.err is stored in the $CUBRID/log/server directory.

error_log_level

error_log_level is a server parameter that specifies a error message to be stored based on severity. There are five different levels which ranges from NOTIFICATION (lowest level), WARNING, SYNTAX, ERROR, and SYNTAX (highest level). An error message with SYNTAX, ERROR, and FATAL levels are stored in the log file if severity of error is SYNTAX, default value.

error_log_warning

The server parameter error_log_warning specifies whether or not error messages with a severity level of WARNING are to be displayed. Its default value is no. Therefore, only error messages with levels other than WARNING will be stored even when it is set to error_log_level = NOTIFICATION. For this reason, you must set error_log_warning = yes to store WARNING messages to an error log file.

error_log_size

error_log_size is a parameter that specifies the maximum number of lines per an error log file. The default value is 8,000,000. If it reaches up the specified number, the <database_name>_<date>_<time>.err.bak file is created.