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 used to configure 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 errors are included in call_stack_dump_activation_list.

Error Number

Error Message

-2

Internal system failure: no more specific information is available.

-7

Trying to format disk volume xxx with an incorrect value xxx for number of pages.

-13

An I/O error occurred while reading page xxx of volume xxx.

-14

An I/O error occurred while writing page xxx of volume xxx.

-17

Internal error: fetching deallocated pageid xxx of volume xxx.

-19

Internal error: pageptr = xxx of page xxx of volume xxx is not fixed.

-21

Internal error: unknown sector xxx of volume xxx.

-22

Internal error: unknown page xxx of volume xxx.

-45

Slot xxx on page xxx of volume xxx is allocated to an anchored record. A new record cannot be inserted here.

-46

Internal error: slot xxx on page xxx of volume xxx is not allocated.

-48

Accessing deleted object xxx|xxx|xxx.

-50

Internal error: relocation record of object xxx|xxx|xxx may be corrupted.

-51

Internal error: object xxx|xxx|xxx may be corrupted.

-52

Internal error: object overflow address xxx|xxx|xxx may be corrupted.

-76

Your transaction (index xxx, xxx@xxx|xxx) timed out waiting on xxx on page xxx|xxx. You are waiting for user(s) xxx to release the page lock.

-78

Internal error: an I/O error occurred while reading logical log page xxx (physical page xxx) of xxx.

-79

Internal error: an I/O error occurred while writing logical log page xxx (physical page xxx) of xxx.

-81

Internal error: logical log page xxx may be corrupted.

-90

Redo logging is always a page level logging operation. A data page pointer must be given as part of the address.

-96

Media recovery may be needed on volume xxx.

-97

Internal error: unable to find log page xxx in log archives.

-313

Object buffer underflow while reading.

-314

Object buffer overflow while writing.

-407

Unknown key xxx referenced in B+tree index {vfid: (xxx, xxx), rt_pgid: xxx, key_type: xxx}.

-414

Unknown class identifier: xxx|xxx|xxx.

-415

Invalid class identifier: xxx|xxx|xxx.

-416

Unknown representation identifier: xxx.

-417

Invalid representation identifier: xxx.

-583

Trying to allocate an invalid number (xxx) of pages.

-603

Internal Error: Sector/page table of file VFID xxx|xxx seems corrupted.

-836

LATCH ON PAGE(xxx|xxx) TIMEDOUT

-859

LATCH ON PAGE(xxx|xxx) ABORTED

-890

Partition failed.

-891

Appropriate partition does not exist.

-976

Internal error: Table size overflow (allocated size: xxx, accessed size: xxx) at file table page xxx|xxx(volume xxx)

-1040

HA generic: xxx.

-1075

Descending index scan aborted because of lower priority on B+tree with index identifier: (vfid = (xxx, xxx), rt_pgid: xxx).

If error numbers are configured in call_stack_dump_activation_list of cubrid.conf, it is working like configuration done including errors above.

The following example shows how to make error numbers -115, -116, and error numbers perform call-stack dump.

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 used to configure 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 is set to 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 used to configure whether or not to dump a call stack when an error occurs in the database server. If this parameter is set to no, a call stack for any errors is not dumped. If it is set to yes, a call stack for all errors is dumped. The default value is no.

error_log

error_log is a server/client parameter used to configure 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 used to configure an 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

error_log_warning is a parameter used to configure 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 error_log_level is set to NOTIFICATION. For this reason, you must set error_log_warning to yes to store WARNING messages to an error log file.

error_log_size

error_log_size is a parameter used to configure 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.