ALTIBASE records trace logs for important status information and errors for each module in the $ALTIBASE_HOME/trc path, which is the installed path.
Classification of trace logs
The trace log recorded by ALTIBASE is as follows.
|Records start/stop the process and overall DBMS log|
Records logs related to checkpoints and tablespaces
Records logs related to DDL execution and query processing
Records logs related to replication
|Records logs related to DB Link|
Records logs related to XA transaction
|Records logs created when processing the main module|
Records logs related to errors occurring on the server
Records debugging logs for errors occurring on the server.
By default, the log files are circulated to altibase_xx.log-[1-10], including altibase_xx.log, to record 10 log files.
In the following, messages that are meaningful to the user are explained separately for each trace log.
The user must check altibase_boot.log first when an error occurs in DBMS. The orange color mark in the table is an error that the user must resolve.
ERR-0108d (errno=0) License is invalid or expired.
This error occurs when the license file is missing or incorrect when starting up. The user must check the license information in ALTIBASE and have it reissued if necessary.
ERR-01052(errno=13) Unable to invoke open() function on [/dbs/mydb-0-0]
This error occurs when the DB has not been created before the initial operation or when there is no permission to access the file. The user must create a DB or check if the user has permission to access directories and files. Alternatively, it may be the case that the data file was deleted by mistake by the user. In this case, a procedure to recover using a backup copy is required.
ERR-01052(errno=2) Unable to invoke open() function on [/dblog01/logfile536358]
During the Altibase operation phase, automatic recovery is performed, which occurs when the redo log file required for this process is damaged or does not exist. The user must request technical support from the ALTIBASE HQ.
ERR-0001c(errno=76) Unable to shutdown the communication channel
During the ALTIBASE shutdown phase, a warning message from the session-related cleanup process has no effect on the operation.
ERR-71019 (errno=104) Failed to invoke a system function, write() (read, accept, select)
This error occurs by an error in a disk or network. The user must check the file system or make sure there are no network problems. Alternatively, system calls may fail due to insufficient memory.
ERR-40029 (errno=16) Failed to invoke a system function, flock_trywrlock()
This error occurs when ALTIBASE is already running or ALTIBASE is restarting while it is already running. Or, it can occur when the system call fails due to insufficient memory.
ERR-11018 (errno=2) The version of data file for backup is not compatible with the version of storage manager. Backup DB => [ Version ID = 5.4.1, Bit = 64, Endian = LITTLE LogSize = 10485760 Transaction Table Size = 1024 ] Server=>[ Version ID = 5.4.1, Bit = 64, Endian = LITTLE LogSize = 10485760 Transaction Table Size = 2049 ]
This error occurs when attempting to recover with a data file that is incompatible with the ALTIBASE version currently in use while running with the backed-up data. Or, this occurs when attempting to run in a different state from the ALTIBASE setting value set at the time of backup.
[ERROR] first write () operation failed. errno=32
This error occurs in the read/write system call while the session is disconnected, so the information is recorded in the form of a warning. This log is also recorded when an application forces a shutdown without a normal disconnection command. The operation is not affected.
ERR-7101d(errno=11) Protocol header error. (TCP 188.8.131.52:63847)
When a session accessed with the ALTIBASE connection port attempts to connect with a version that is not compatible with the ALTIBASE server version, the user must traceback with the output connection information to check whether the server/client versions are compatible. The operation is not affected.
ERR-4000f(errno=2) No Error Message Loaded
This error occurs when the files located in the $ALTIBASE_HOME/msg/ path do not exist or are not compatible. with the version. Or, this occurs when the user does not have permission to read on the path.
[Notify : Query Timeout] Query Canceled by Server : Session ID = 102373
When TIMEOUT occurs due to QUERY/FETCH/UTRANS/IDLE TIMEOUT setting, a warning type log is recorded. If there is a problem, the session information is recorded along with the message, so the user must track the session and resolve it.
ERR-01027(errno=0) No more IPC channel (MAX=50, USED=50, BUFSIZE=65536)
This error occurs when attempting more IPC access than available resources.
[Warning] Memory allocation failed. Size:524320 Timeout: 0
This error occurs when an internally required memory allocation fails due to insufficient memory. In this case, the user must determine the cause of insufficient memory and resolve it. If a case of insufficient swap memory occurs, ALTIBASE may terminate abnormally without warning.
This error occurs when there is a temporary problem with performing system calls between socket or disk I/O operations. Generally, this can be ignored, but it is recommended to check the network or disk.
WARNING : write error number : 0, file name : /dblog01/logfile537572, file handle : 440, intended size : 10485760, writed size : 10485760
When creating a file that ALTIBASE requires due to insufficient disk capacity, this is a warning that the file could not be created normally due to insufficient capacity. The user must check the disk capacity and resolve it.
altibase.sm.log is an important basis for determining whether checkpoints are being executed and whether there are long-running queries.
This means the checkpoint has started.
Remove Online Log File at LFG : File[220 ~ 227]
This message removes the transaction log files that are no longer needed for recovery as the checkpoint is performed. If it is continuously displayed as File [None], it is necessary to check whether there are any queries that have been executed for a long time or that there are no untransmitted parts due to the replication.
[CHECKPOINT-summary] BeginChkptLSN=[0,83,9820280], EndChkptLSN=[0,83,9820721], DiskRecLSN=[0,83,9820280]
When the checkpoint has been successfully completed, summary information about checkpoint performance information is recorded in the log.
This means the checkpoint has been successfully completed.
Minimum LSN = [0,83,9824136]
The above value is the offset position of the log file being recorded of the transaction in progress. Therefore, if that value does not change and keeps the same value, it is necessary to check whether there is a query that is executed for a long time as in the Remove log above, or whether the replication is not transmitted.
Database-Level Backup Completed [SUCCESS]
This means the backup has been successfully completed.
DISK TABLESPACE .... DATABASE ....
This means the backup of disk tablespaces has been performed.
~/loganchor0 BACKUP TO
This means that the backup of the log anchor has been performed.
MEMORY TABLESPACE DATAFILE …. BACKUP TO ….
This means that the backup of memory tablespace has been performed.
In altibase_qp.log, a log of the DDL executed by the user and the case of changing DB property values with “ALTER SYSTEM” statement, etc. are recorded. They are classified as follows.
[EXEC_DDL_BEGIN : create index T1_IDX on T1 (A)]
Log indicating the start of DDL executed by the user
[EXEC_DDL_END : SUCCESS]
Log indicating the normal completing of DDL executed by the user
[EXEC_DDL_END : FAILURE] errorcode 1627549735.
Log indicating the error details of DDL executed by the user
Log indicating when the user changes the DP property setting value that affects the entire system
Because altiabse.rp.log records the operation state of replication and queries when various conflicts occur, it provides important tracks for replication problems.
ERR-31017(errno=0) Replication not found
This error occurs when the replication target objects do not exist when executing DDL. Therefore, it is necessary to check whether the replication target objects exist.
ERR-6200f(errno=16) [Sender] Stop sender thread REP1 at , Restart SN
This log is created when the replication sender is explicitly stopped by the user
ERR-71017(errno=79) Failed to invoke a system function, connect()
This is the log when the replication sender cannot connect to the other side's server and attempts to reconnect.
It is necessary to check whether the other side's server, network status, and ALTIBASE are running properly. If the other party's replication is explicitly dropped, it is a normal error.
[Recovery Sender] Replication REP1 Start... at 
This is the log when the replication and the sender have started.
[Receiver] Replication REP1 Started ...
This is the log when receiver and replication have started properly.
RECEIVER:REPLICATION STOP MSG arrived!
This is when the replication of other server is explicitly stopped by the user.
ERR-61047(errno=0) [Receiver] REP1 receiver has error in recvXlog()
This error occurs when the replication of the other server is explicitly stopped by the user.
ERR-61036(errno=0) [Receiver] err_not found in deleteXlog()
In the process of executing the DELETE transaction received through replication, if the corresponding record does not exist, this conflict error is recorded.
ERR-61035(errno=0) [Receiver] An update conflict encountered.
This error occurs when a conflict error is recorded because the before/after values of the corresponding record are different during the process of executing the UPDATE transaction received through replication.
ERR-6103a(errno=0) [Receiver] err_not_found in updateXlog()
In the process of executing the UPDATE transaction received replication, if the corresponding record does not exist, this conflict error is recorded.
ERR-11058(errno=0) The row already exists in a unique index.
In the process of executing the INSERT received through replication, the corresponding record already exists on the receiving side. (There are data with the same PK)
The name of the replication object used in the example above is “REP1”. Since the name of the replication object specified by the user will be different, it should be considered when searching for errors, and it is recommended to detect the operation state of the replication Sender/Receiver and conflict errors.
In addition, if a conflict occurs, it is important to find the cause of the conflict with the SQL statement that remains when the conflict occurs, because there is a possibility that data inconsistency may have occurred due to either not properly complying with the considerations of the replication environment described above.
In altibase_dk.log, various information and errors that may occur in the environment using the Database Link are recorded.
ERR-b1070(errno=0) ODBC problem occurred [0:IM002:[unixODBC][Driver Manager]Data source name not found, and no default driver specified]
This error occurs when the specified data source name is not found or LD_LIBRARY_PATH is not set.
ERR-b1070(errno=239) ODBC problem occurred [327730:08001:Client unable to establish connection.]
This error occurs when it is not possible to connect to the Altibase server or when the odbc.ini environment variable is not set. This can be resolved by checking the server running state and adding odbc.ini to the environment variable.
The altibase_error.log provides tracks for analyzing the cause of abnormal termination of ALTIBASE.
When ALTIBASE is abnormally terminated due to a bug, its own trace log is outputted in which process occurred. If this error occurs, the ALTIBASE process is terminated. First, backup all files in $ALTIBASE_HOME/trc/. Then backup the redo log files and, if there is enough disk space, even get the database file. When such file backup is completed, resolve it by restarting ALTIBASE and contact ALTIBASE for technical support.