diff --git a/Manuals/Altibase_7.3/eng/General Reference-1.Data Types & Altibase Properties.md b/Manuals/Altibase_7.3/eng/General Reference-1.Data Types & Altibase Properties.md index 1268dd7f1..e8d5523dd 100644 --- a/Manuals/Altibase_7.3/eng/General Reference-1.Data Types & Altibase Properties.md +++ b/Manuals/Altibase_7.3/eng/General Reference-1.Data Types & Altibase Properties.md @@ -3279,10 +3279,6 @@ The values in the “Alter Level” column have the following meaning: BOTH - TEMP_MAX_PAGE_COUNT - SYSTEM - - TEMP_STATS_WATCH_TIME SYSTEM @@ -3310,7 +3306,11 @@ The values in the “Alter Level” column have the following meaning: BOTH -   + TOTAL_WA_SIZE + SYSTEM + + + INIT_TOTAL_WA_SIZE SYSTEM @@ -3326,8 +3326,8 @@ The values in the “Alter Level” column have the following meaning: BOTH - S - Normal + S + Normal CM_DISCONN_DETECT_TIME   @@ -3345,7 +3345,7 @@ The values in the “Alter Level” column have the following meaning: DEFAULT_THREAD_STACK_SIZE -   +   IPC_CHANNEL_COUNT @@ -3354,6 +3354,12 @@ The values in the “Alter Level” column have the following meaning: IPC_FILEPATH + IPC_SEM_KEY + + + IPC_SHM_KEY + + IPCDA_CHANNEL_COUNT @@ -3362,7 +3368,13 @@ The values in the “Alter Level” column have the following meaning: IPCDA_FILEPATH -   +   + + + IPCDA_SEM_KEY + + + IPCDA_SHM_KEY MAX_LISTEN @@ -3446,7 +3458,7 @@ The values in the “Alter Level” column have the following meaning:   - Time-Out + Time-Out BLOCK_ALL_TX_TIME_OUT SYSTEM @@ -3479,6 +3491,10 @@ The values in the “Alter Level” column have the following meaning: BOTH + SERVICE_THREAD_RECV_TIMEOUT +   + + SHUTDOWN_IMMEDIATE_TIMEOUT SYSTEM @@ -3564,8 +3580,8 @@ The values in the “Alter Level” column have the following meaning: SYSTEM - R -   + R +   REPLICATION_ACK_XLOG_COUNT   @@ -3637,6 +3653,10 @@ The values in the “Alter Level” column have the following meaning: SYSTEM + REPLICATION_HBT_CONNECT_WAIT_TIME + SYSTEM + + REPLICATION_HBT_DETECT_HIGHWATER_MARK SYSTEM @@ -3678,6 +3698,10 @@ The values in the “Alter Level” column have the following meaning: SYSTEM + REPLICATION_META_ITEM_COUNT_DIFF_ENABLE + SYSTEM + + REPLICATION_POOL_ELEMENT_COUNT SYSTEM @@ -3706,6 +3730,10 @@ The values in the “Alter Level” column have the following meaning: SYSTEM + REPLICATION_RECEIVER_APPLIER_YIELD_COUNT +   + + REPLICATION_RECOVERY_MAX_LOGFILE   @@ -3724,6 +3752,10 @@ The values in the “Alter Level” column have the following meaning:   + REPLICATION_SENDER_IP +   + + REPLICATION_SENDER_SEND_TIMEOUT SYSTEM @@ -3775,8 +3807,8 @@ The values in the “Alter Level” column have the following meaning: SYSTEM - NM -   + NM +   IB_CONCHKSPIN   @@ -3787,7 +3819,7 @@ The values in the “Alter Level” column have the following meaning: IB_LATENCY - IB_LISTEN_DISABLE + IB_LISTENER_DISABLE IB_MAX_LISTEN @@ -3818,7 +3850,7 @@ The values in the “Alter Level” column have the following meaning: SNMP_PORT_NO -   +   SNMP_TRAP_PORT_NO @@ -3842,6 +3874,9 @@ The values in the “Alter Level” column have the following meaning: SSL_CIPHER_LIST + SSL_CIPHER_SUITES + + SSL_CLIENT_AUTHENTICATION @@ -3851,6 +3886,9 @@ The values in the “Alter Level” column have the following meaning: SSL_KEY + SSL_LOAD_CONFIG + + SSL_MAX_LISTEN @@ -3862,12 +3900,28 @@ The values in the “Alter Level” column have the following meaning:   - M -   + M +   ALL_MSGLOG_FLUSH SYSTEM + CM_MSGLOG_COUNT +   + + + CM_MSGLOG_FILE +   + + + CM_MSGLOG_SIZE +   + + + CM_MSGLOG_FLAG +   + + COLLECT_DUMP_INFO SYSTEM @@ -3884,7 +3938,7 @@ The values in the “Alter Level” column have the following meaning: DK_MSGLOG_RESERVE_SIZE -   +   DK_MSGLOG_SIZE @@ -3893,6 +3947,9 @@ The values in the “Alter Level” column have the following meaning: DUMP_MSGLOG_COUNT + DUMP_MSGLOG_FILE + + DUMP_MSGLOG_SIZE @@ -3908,6 +3965,18 @@ The values in the “Alter Level” column have the following meaning: ERROR_MSGLOG_SIZE + JOB_MSGLOG_COUNT + + + JOB_MSGLOG_FILE + + + JOB_MSGLOG_FLAG + + + JOB_MSGLOG_SIZE + + ERROR_MSGLOG_RESERVE_SIZE @@ -4013,7 +4082,7 @@ The values in the “Alter Level” column have the following meaning: SERVER_MSGLOG_DIR - ERVER_MSGLOG_FILE + SERVER_MSGLOG_FILE SERVER_MSGLOG_FLAG @@ -4038,13 +4107,31 @@ The values in the “Alter Level” column have the following meaning: SM_MSGLOG_RESERVE_SIZE -   +   SM_MSGLOG_SIZE +   + + + ST_MSGLOG_COUNT +   + + + ST_MSGLOG_FILE +   + + + ST_MSGLOG_FLAG +   + + + ST_MSGLOG_SIZE +   TRC_MSGLOG_RESERVE_SIZE +   TRCLOG_DETAIL_PREDICATE @@ -4166,8 +4253,8 @@ The values in the “Alter Level” column have the following meaning: PASSWORD_VERIFY_FUNCTION - E -   + E +   ACCESS_LIST   @@ -4207,16 +4294,23 @@ The values in the “Alter Level” column have the following meaning: JOB_THREAD_COUNT -   +   JOB_THREAD_QUEUE_SIZE +   + + + LISTAGG_PRECISION + SYSTEM MSG_QUEUE_PERMISSION + SYSTEM PSM_CHAR_DEFAULT_PRECISION +   PSM_IGNORE_NO_DATA_FOUND_ERROR @@ -4250,6 +4344,10 @@ The values in the “Alter Level” column have the following meaning: SESSION + REGEXP_MODE + BOTH + + REMOTE_SYSDBA_ENABLE SYSTEM @@ -4265,6 +4363,10 @@ The values in the “Alter Level” column have the following meaning: SERIAL_EXECUTE_MODE BOTH + + VARRAY_MEMORY_MAXIMUM + SYSTEM + @@ -6902,10 +7004,46 @@ Read-Write, Single Value ##### Description -When a disk index is created, if the keys extracted from data cannot all be sorted in memory at the same time, this property specifies the number of pages to be used for external sorting. +When creating a single disk index using the CREATE INDEX statement or rebuilding it with the ALTER INDEX ~ REBUILD statement, this property determines the number of pages used for disk index key sorting. It is utilized when the size of disk index keys is larger than DISK_INDEX_BUILD_SORT_AREA_SIZE, indeed, when it is impossible to sort all disk index keys within the designated memory space. + +If the disk I/O causes slower disk index creation (or rebuilding), adjusting the value of this property can potentially increase the speed of disk index creation (or rebuilding). However, it's recommended to set it below 10% of BUFFER_AREA_SIZE. This suggestion is because multiple transactions accessing not only disk indexes but also disk tables access BUFFER_AREA_SIZE memory area simultaneously. + +The default value of this property is approximately 1% size of the default value of BUFFER_AREA_SIZE. Adjust this property value appropriately considering the disk index when adjusting BUFFER_AREA_SIZE based on the disk table size. This property can be changed using the ALTER SYSTEM statement during system operation. +#### DISK_INDEX_BUILD_SORT_AREA_SIZE (Unit : byte) + +##### Data Type + +Unsigned Long + +##### Default Value + +10MB + +##### Attributes + +Read-Write, Single Value + +##### Range + +[512K, 264-1] + +##### Description + +When creating a single disk index using the CREATE INDEX statement or rebuilding it with the ALTER INDEX ~ REBUILD statement, this property determines the maximum memory size used for disk index key sorting. Memory is allocated as much as the size of disk index keys and increases by the amount specified in this value when necessary. + +디스크 인덱스를 생성(또는 재구축)하는 동안 할당된 메모리 크기는 V$MEMSTAT의 Storage_Disk_Index에서 확인할 수 있으며 동시에 생성(또는 재구축)하는 디스크 인덱스 수 * DISK_INDEX_BUILD_SORT_AREA_SIZE 만큼 메모리가 할당될 수 있다. + +Users can find the size of allocated memory size during disk index creation or rebuilding in Storage_Disk_Index of V$MEMSTAT. + +This memory is released immediately after the completion of sorting disk index keys. However, if the size of disk index keys is smaller than the value set in this property, which means all disk index keys are sorted within the memory specified in this property during disk index creation(or rebuilding), the memory is released when all processes are done. + +Users can adjust this property when they need to improve the disk index creation(or rebuilding) speed. The recommended value is INDEX_BUILD_THREAD_COUNT * 20MB. + +This property can be changed using the ALTER SYSTEM statement. + #### EXECUTE_STMT_MEMORY_MAXIMUM (Unit: byte) ##### Data Type @@ -6914,7 +7052,7 @@ Unsigned Long ##### Default Value -1G +2147483648 ##### Attributes @@ -8796,7 +8934,7 @@ Read-Write, Single Value ##### Range -[512K, 264-1] +[0, 264-1] ##### Description @@ -8870,11 +9008,17 @@ Read-Write, Single Value ##### Range -[1, 512] +[1, 16384] ##### Description -This property specifies the number of transaction segments (Undo segments and TTS segments) created when the server is started. +This property specifies the number of transaction segments managed by undo tablespace. There are two transaction segments, TSS segment and undo segment. The default value of 256 refers to 256 TSS segments and 256 Undo segments. + +Transaction segments are created when the Altibase server starts up. If there is an insufficiency of transaction segments during transaction processing, the system logs "TRANSACTION_SEGMENT_COUNT is full" in the altibase_boot.log file. Then, transactions wait until they are allocated available transaction segments. + +정리되지 않은 분산 트랜잭션이 있을 때 현재 값보다 작게 설정하고 Altibase 서버를 재시작한 경우 기존 언두 테이블스페이스의 공간에 접근할 수 없어 Altibase 서버 구동이 실패한다. + +If users want to set this property smaller than before in Altibase distributed database system, users should quit all distributed transactions and stop Altibase server. If an active distributed transaction remains and, Altibase server startup fails when users try restarting the server as it cannot access the space in the existing undo tablespace. This property can be changed using the ALTER SYSTEM statement while Altibase is running. @@ -9109,6 +9253,62 @@ This is a socket file created for Altibase server to connect with the client thr If the server starts, a socket file is created under $ALTIBASE_HOME/trc/cm-ipc directory, and be careful not to delete this file. +#### IPC_SEM_KEY + +##### Data Type + +Unsigned Integer + +##### Default Value + +0 + +##### Attributes + +Read-Only, Single Value + +##### Range + +[0, 4294967294] + +##### Description + +This property sets semaphore keys for IPC channel creation to the user-defined value. + +The default value is 0. Altibase generates semaphore keys based on the process identifier(PID) of the Altibase server process automatically. + +When setting this property to any other numbers, it creates IPC channels using a range of contiguous semaphore keys, starting from IPC_SEM_KEY up to IPC_SEM_KEY + (IPC_CHANNEL_COUNT + 1). The additional +1 is reserved for the IPC channel used by the SYS user to connect in administrator mode (sysdba). For instance, if IPC_SEM_KEY is set to 10000 and IPC_CHANNEL_COUNT is set to 1000, the semaphore keys range from 10000 to 11000. + +IPC channels are generated while Altibase server starts up. If the semaphore key is in use or unable to create a semaphore due to other reasons, the startup of the Altibase server will fail. In such cases, check the system error(errno) in the Altibase server trace log, altibase_boot.log, and take appropriate action. + +#### IPC_SHM_KEY + +##### Data Type + +Unsigned Integer + +##### Default Value + +0 + +##### Attributes + +Read-Only, Single Value + +##### Range + +[0, 4294967294] + +##### Description + +This property sets shared memory keys for IPC channel creation to the user-defined value. + +The default value is 0. Altibase generates shared memory keys based on the process identifier(PID) of the Altibase server process automatically. + +When setting this property to any other numbers, the IPC_SHM_KEY value is used for the shared memory key. + +IPC channels are generated while Altibase server starts up. If the shared memory key is in use or unable to create shared memory due to other reasons, the startup of the Altibase server will fail. In such cases, check the system error(errno) in the Altibase server trace log, altibase_boot.log, and take appropriate action. + #### IPCDA_CHANNEL_COUNT ##### Data Type @@ -9169,7 +9369,7 @@ String ##### Attributes -Read-Only, Multiple Value +Read-Only, Multiple Values ##### Range @@ -9181,6 +9381,62 @@ This is a socket file created for Altibase server to connect with the client thr If the server starts, a socket file is created under $ALTIBASE_HOME/trc/cm-ipcda directory, and be careful not to delete this file. +#### IPCDA_SEM_KEY + +##### Data Type + +Unsigned Integer + +##### Default Value + +0 + +##### Attributes + +Read-Only, Single Value + +##### Range + +[0, 4294967294] + +##### Description + +This property sets semaphore keys for IPCDA channel creation to the user-defined value. + +The default value is 0. Altibase generates semaphore keys based on the process identifier(PID) of the Altibase server process automatically. + +When setting this property to any other numbers, it creates IPC channels using a range of contiguous semaphore keys, starting from IPCDA_SEM_KEY up to IPCDA_SEM_KEY + IPC_CHANNEL_COUNT. For instance, if IPCDA_SEM_KEY is set to 10000 and IPC_CHANNEL_COUNT is set to 1000, the semaphore keys range from 10000 to 10999. + +IPCDA channels are generated while Altibase server starts up. If the semaphore key is in use or unable to create a semaphore due to other reasons, the startup of the Altibase server will fail. In such cases, check the system error(errno) in the Altibase server trace log, altibase_boot.log, and take appropriate action. + +#### IPCDA_SHM_KEY + +##### Data Type + +Unsigned Integer + +##### Default Value + +0 + +##### Attributes + +Read-Only, Single Value + +##### Range + +[0, 4294967294] + +##### Description + +This property sets shared memory keys for IPCDA channel creation to the user-defined value. + +The default value is 0. Altibase generates shared memory keys based on the process identifier(PID) of the Altibase server process automatically. + +When setting this property to any other numbers, two contiguous numbers from IPCDA_SHM_KEY are used for the shared memory keys. For example, if IPCDA_SHM_KEY is 10000, the shared memory keys will be 10000 and 10001. + +IPCDA channels are generated while Altibase server starts up. If the shared memory key is in use or unable to create shared memory due to other reasons, the startup of the Altibase server will fail. In such cases, check the system error(errno) in the Altibase server trace log, altibase_boot.log, and take appropriate action. + #### MAX_LISTEN ##### Data Type @@ -9474,7 +9730,7 @@ Unsigned Integer ##### Attributes -읽기 전용, 단일 값 +Read-Only, Single Value ##### Range @@ -9920,6 +10176,28 @@ This property is set to prevent abnormal increases in database memory consumptio This property can be changed using the ALTER SYSTEM or ALTER SESSION statement while Altibase is running. +#### SERVICE_THREAD_RECV_TIMEOUT(Unit : second) + +##### Data Type + +Unsigned Integer + +##### Default + +60 + +##### Attributes + +Read-Only, Single Value + +##### Range + +[0, 3600] + +##### Description + +This property is configured to prevent service threads from indefinite waiting in case of receiving malformed packets from clients. If a completed packet is not received from the client within the time set by this property, a timeout occurs, leading the server to terminate the connection. Setting the value of this property to 0 causes service threads to wait indefinitely until a completed packet is received. Conversely, setting it too low might lead to connection termination in slower network environments. Supported communication methods include TCP, Unix domain, SSL, and Infiniband. + #### SHUTDOWN_IMMEDIATE_TIMEOUT ##### Data Type @@ -10114,11 +10392,11 @@ Unsigned Integer ##### Attributes -Read-Only, Single Value +Read-Write, Single Value ##### Range -[0, 1] +[0, 2] ##### Description @@ -10128,6 +10406,8 @@ If this parameter is set to 0, the archivelog thread will output an error messag If this parameter is set to 1, the archivelog thread waits until enough disk space can be secured to perform the archive log file backup. Because the archive log files have not been backed up, care must be taken to prevent the log files from being deleted if checkpointing takes place during this waiting period. +If this parameter is set to 2, the archivelog thread will write an error message in the trace log file(altibase_sm.log) and attempt to back up the next log files in case of backup failure. Every log file takes this step in a row, so there may be log files that have not been backed up in the archivelog file path from when the log file backup failure occurs until the backup failure is resolved. At this time, if a checkpoint occurs, it may not be possible to recover the database because even the failed backup log file is judged to be an unnecessary log file and deleted. Therefore, users should take care of this when setting this property to 2. + #### ARCHIVE_MULTIPLEX_COUNT ##### Data Type @@ -10168,7 +10448,7 @@ String ##### Attributes -Read-Only, Multiple Value +Read-Only, Multiple Values ##### Range @@ -10320,7 +10600,7 @@ Unsigned Integer ##### Attributes -Read-Only, Multiple Value +Read-Only, Multiple Values ##### Range @@ -10834,7 +11114,7 @@ Read-Only, Single Value ##### Range -[1, 512] +[2, 512] ##### Description @@ -11477,7 +11757,7 @@ Although a large value for the REPLICATION_RECEIVER_APPLIER_QUEUE_SIZE property The value of this property can be altered using the ALTER SYSTEM statement while Altibase is running. -#### REPLICATION_RECOVERY_MAX_LOGFILE +#### REPLICATION_RECEIVER_APPLIER_YIELD_COUNT ##### Data Type @@ -11485,7 +11765,7 @@ Unsigned Integer ##### Default Value -0 +20000 ##### Attributes @@ -11493,19 +11773,15 @@ Read-Write, Single Value ##### Range -[0, 232–1] +[0, 232-1] ##### Description -This property specifies the maximum number of log files that are not deleted, based on a Restart Redo Point, for data recovery using replication. - -In order to recover data at the time of replication, the local server does not delete logs that have not been flushed to disk on remote servers. Even if checkpointing takes place at this time, because the log files cannot be deleted, the number of log files on the local server will continue to increase and this can ultimately lead to a disk full error. - -Thus, if the maximum log file count in the recovery options is exceeded when checkpointing occurs, replication-based recovery is aborted and the log files are deleted. Then, replication starts over. +This property specifies the number of times an Applier waits for the reflection of another Applier's transaction using the system function "yield". -If this property is set to 0 or replication runs in eager mode, this function is not used. Because log files are deleted when checkpointing occurs, the values of CHECKPOINT_INTERVAL_IN_SEC and CHECKPOINT_IN_LOG should be considered together. +When using the yield function, CPU usage occurs. Therefore, after exceeding this specified count, the timed_wait function is called, which doesn’t consume CPU resources. -#### REPLICATION_RECOVERY_MAX_TIME (Unit: second) +#### REPLICATION_RECOVERY_MAX_LOGFILE ##### Data Type @@ -11513,7 +11789,35 @@ Unsigned Integer ##### Default Value -232–1 +0 + +##### Attributes + +Read-Write, Single Value + +##### Range + +[0, 232–1] + +##### Description + +This property specifies the maximum number of log files that are not deleted, based on a Restart Redo Point, for data recovery using replication. + +In order to recover data at the time of replication, the local server does not delete logs that have not been flushed to disk on remote servers. Even if checkpointing takes place at this time, because the log files cannot be deleted, the number of log files on the local server will continue to increase and this can ultimately lead to a disk full error. + +Thus, if the maximum log file count in the recovery options is exceeded when checkpointing occurs, replication-based recovery is aborted and the log files are deleted. Then, replication starts over. + +If this property is set to 0 or replication runs in eager mode, this function is not used. Because log files are deleted when checkpointing occurs, the values of CHECKPOINT_INTERVAL_IN_SEC and CHECKPOINT_IN_LOG should be considered together. + +#### REPLICATION_RECOVERY_MAX_TIME (Unit: second) + +##### Data Type + +Unsigned Integer + +##### Default Value + +232–1 ##### Attributes @@ -11609,6 +11913,41 @@ The REPLICATION_SENDER_ENCRYPT_XLOG property sets whether or not to encrypt XLog 1: Encrypts XLogs. +#### REPLICATION_SENDER_IP + +##### Data Type + +String + +##### Default Value + +ANY + +##### Attributes + +Read-Only, Multiple Values + +##### Range + +None + +##### Description + +This property stores the IP address of the replication sender. Users can set this value to 'ANY' or a specific IP address. + +If the value is set to ANY, the default value, users can use every IP address of the local server which creates replication objects for replication communication. In this case, the IP address allocated by OS is used for the sender IP address. If the value is set to a specific IP address, users can only use that IP address when the local server communicates with a remote server(receiver). Users can set several IP addresses by adding REPLICATION_SENDER_IP = *value*. These values are used in a row. IPv4, IPv6, and IPv6 extension address formats are supported. + +##### Example + +``` +REPLICATION_SENDER_IP = 10.0.0.1 +REPLICATION_SENDER_IP = 0000:0000:0000:0000:0000:ffff:1400:0001 +``` + + + +자세한 내용은 *Replication Manual에서 [송신자 IP 주소 설정](https://github.com/ALTIBASE/Documents/blob/master/Manuals/Altibase_7.3/kor/Replication Manual.md#송신자-ip-주소-설정)* 설명을 참고한다. + #### REPLICATION_SENDER_SEND_TIMEOUT (Unit: second) ##### Data Type @@ -11954,6 +12293,32 @@ This property specifies whether to keep updated contents if an update conflict o This property can be changed using the ALTER SYSTEM statement while Altibase is running. +#### REPLICATION_META_ITEM_COUNT_DIFF_ENABLE + +##### Data Type + +Unsigned Integer + +##### Default Value + +0 + +##### Attributes + +Read-Write, Single Value + +##### Range + +[0, 1] + +##### Description + +Lazy 모드로 이중화 수행 과정에서 SPLIT PARTITION과 MERGE PARTITION, DROP PARTITION을 수행하여 Active 서버와 Standby 서버의 이중화 테이블 파티션 메타 아이템 개수가 다른 경우에 이중화를 START 할 수 있는 프로퍼티이다. 이 값을 1로 설정하면 이중화 테이블 파티션 메타 아이템 개수가 다른 경우에도 이중화를 START 할 수 있다. + +If this property is set to 1, users can START replication even if the number of replication table partitions meta items of the Active server and Standby server are different when LAZY mode replication is operating. During this process, SPLIT PARTITION, MERGE PARTITION, and DROP PARTITION are performed. + +This property can be changed using the ALTER SYSTEM statement while Altibase is running. + ### Network and Security Properties #### IB_CONCHKSPIN @@ -12672,6 +13037,96 @@ This property specifies whether or not information about message files and log f 1: Information about message files and log files are collected. +#### CM_MSGLOG_COUNT + +##### Data Type + +Unsigned Integer + +##### Default Value + +10 + +##### Attributes + +Read-Only, Single Value + +##### Range + +[0, 232-1] + +##### Description + +This property specifies the maximum number of message log files for communication(CM) module. + +#### CM_MSGLOG_FILE + +##### Data Type + +String + +##### Default Value + +altibase_cm.log + +##### Attributes + +Read-Only, Single Value + +##### Range + +None + +##### Description + +This file stores messages generated during the communication(CM) module processing. + +#### CM_MSGLOG_SIZE(Unit: byte) + +##### Data Type + +Unsigned Integer + +##### Default Value + +10 * 1024 * 1024 + +##### Attributes + +Read-Only, Single Value + +##### Range + +[0, 232-1] + +##### Description + +This property sets the maximum size of the communication(CM) module message file. + +#### CM_MSGLOG_FLAG + +##### Data Type + +Unsigned Integer + +##### Default Value + +3 + +##### Attributes + +Read-Write, Single Value + +##### Range + +[0, 232-1] + +##### Description + +This is a flag value indicating whether warning or trace messages generated by the communication (CM) module will be recorded in the CM_MSGLOG_FILE. + +If this value is 0, the messages are not recorded. If this value is larger than 0, the messages are recorded. + #### DK_MSGLOG_COUNT ##### Data Type @@ -12938,6 +13393,96 @@ Read-Only, Single value This property specifies the amount of space to be reserved in advance for the file where the server error message is stored. +#### JOB_MSGLOG_COUNT + +##### Data Type + +Unsigned Integer + +##### Default Value + +10 + +##### Attributes + +Read-Only, Single Value + +##### Range + +[0, 232-1] + +##### Description + +This property specifies the maximum number of JOB-related message log files. + +#### JOB_MSGLOG_FILE + +##### Data Type + +String + +##### Default Value + +altibase_job.log + +##### Attributes + +Read-Only, Single Value + +##### Range + +None + +##### Description + +This file stores messages generated during JOB processing. + +#### JOB_MSGLOG_FLAG + +##### Data Type + +Unsigned Integer + +##### Default Value + +2 + +##### Attributes + +Read-Write, Single Value + +##### Range + +[0, 232 –1] + +##### Description + +This is a flag value indicating whether warning or trace messages generated by JOB will be recorded in the JOB_MSGLOG_FILE. + +If this value is 0, the messages are not recorded. If this value is larger than 0, the messages are recorded. + +#### JOB_MSGLOG_SIZE(Unit : byte) + +##### Data Type + +Unsigned Integer + +##### Default Value + +10 * 1024 * 1024 + +##### Attributes + +Read-Only, Single Value + +##### Range + +[0, 232-1] + +##### Description + +This property sets the maximum size of the JOB-related message file. + #### LB_MSGLOG_COUNT ##### Data Type @@ -13170,6 +13715,28 @@ This property specifies whether to write network-related error messages in the s In an unstable network environment, in which error messages are frequently output, setting this value to 0 prevents network-related error messages from being output. +#### NETWORK_ERROR_LOG_FILE + +##### Data Type + +Unsigned Integer + +##### Default Value + +0 + +##### Attributes + +Read-Write, Single Value + +##### Range + +[0, 1] + +##### Description + +This property determines which log file will record network-related error messages. By default value 0, these errors are logged in altibase_boot.log. Setting this property to 1 will record them in altibase_cm.log. However, this property only operates effectively when NETWORK_ERROR_LOG is set to. If NETWORK_ERROR_LOG is set to 0, network-related error messages will not be output. + #### QP_MSGLOG_COUNT ##### Data Type @@ -13694,7 +14261,7 @@ Unsigned Integer ##### Default Value -7 +15 ##### Attributes @@ -13866,6 +14433,101 @@ Read-Only, Single Value This property specifies the maximum size, in bytes, of the Storage Manager message log files. +#### ST_MSGLOG_FLAG + +##### Data Type + +Unsigned Integer + +##### Default Value + +0 + +##### Attributes + +Read-Write, Single Value + +##### Range + +[0, 1] + +##### Description + +This is a flag value indicating whether spatial topological(ST) information will be recorded in the altibase_st.log file. + +If this value is 0, the messages are not recorded. If this value is larger than 0, the messages are recorded. + +altibase_st.log 파일에 st 정보를 기록한다. + +- 0: st 정보 기록하지 않는다. +- 1: st 정보를 기록한다. + +#### ST_MSGLOG_COUNT + +##### Data Type + +Unsigned Integer + +##### Default Value + +10 + +##### Attributes + +Read-Only, Single Value + +##### Range + +[0, 232-1] + +##### Description + +This property specifies the maximum number of message log files for spatial topological(ST) message files. + +#### ST_MSGLOG_FILE + +##### Data Type + +String + +##### Default Value + +altibase_st.log + +##### Attributes + +Read-Only, Single Value + +##### Range + +None + +##### Description + +This file stores messages generated during the spatial topological(ST) processing. + +#### ST_MSGLOG_SIZE + +##### Data Type + +Unsigned Integer + +##### Default Value + +10 * 1024 * 1024 + +##### Attributes + +Read-Only, Single Value + +##### Range + +[0, 232 -1] + +##### Description + +This property sets the maximum size of the spatial topological(ST) message file. + #### TRC_MSGLOG_RESERVE_SIZE (Unit : byte) ##### Data Type @@ -14302,7 +14964,7 @@ String ##### Attributes -Read-Write, Multiple Value +Read-Write, Multiple Values ##### Range @@ -14448,7 +15110,7 @@ Unsigned Integer ##### Attributes -Read-Only, Multiple Value +Read-Only, Multiple Values ##### Range @@ -14751,7 +15413,7 @@ ACCESS_LIST = permit, 192.168.3.17, 255.255.255.255, 5 -**ACCESS_LIST_FILE** +#### ACCESS_LIST_FILE ##### Data Type @@ -15038,6 +15700,30 @@ Read-Only, Single Value This property specifies the number of queues to be created at server startup for a JOB to run. If the value of this property is large, a larger number of jobs can run in a given amount of time. +#### LISTAGG_PRECISION (Unit: byte) + +##### Data Type + +Unsigned Integer + +##### Default Value + +4000 + +##### Attributes + +Read-Write, Single Value + +##### Range + +[1, 32000] + +##### Description + +This property specifies the size of the VARCHAR type that the LISTAGG function returns. + +This property can be changed using the ALTER SYSTEM statement while Altibase is running. + #### MSG_QUEUE_PERMISSION ##### Data Type @@ -15159,6 +15845,28 @@ Read-Only, Single Value Altibase determines the values specified in the PSM_NCHAR_UTF16_DEFAULT_PRECISION property as the size of NCHAR in the case Altibase character set is UTF16, and the size of NCHAR type is unspecified in parameters or return values when creating stored procedures and functions. +#### PSM_MAX_DDL_REFERENCE_DEPTH + +##### Data Type + +Unsigned Integer + +##### Default Value + +128 + +##### Attributes + +Read-Write, Single Value + +##### Range + +[64, 232-1] + +##### Description + +This property limits the number of recursion calls or reference depths when compiling PSM. If the number of recursion calls or reference depths exceeds the set value, an error occurs. + #### PSM_NCHAR_UTF8_DEFAULT_PRECISION ##### Data Type @@ -15425,3 +16133,65 @@ Supports the regular expression syntax of the Perl Compatible Regular Expression This mode can be used when the Altibase server character set is US7ASCII or UTF-8, and there is a difference in syntax from Altibase regular expression mode. For more information, please refer to [SQL Reference-Appendix A. Regular Expressions](https://github.com/ALTIBASE/Documents/blob/master/Manuals/Altibase_7.3/eng/SQL%20Reference.md#appendix-a-regular-expressions). +#### REGEXP_MODE + +##### Data Type + +Unsigned Integer + +##### Default Value + +0 + +##### Attributes + +Read-Write, Single Value + +##### Range + +[0, 1] + +##### Description + +This property configures the regular expression mode, and the meanings of its settings are as follows: + +> **0** + +Altibase regular expression mode. + +It partially supports POSIX Basic Regular Expression (BRE) and Extended Regular Expression (ERE). + +> **1** + +PCRE2 compatibility mode. + +It supports the regular expression syntax of the Perl Compatible Regular Expressions (PCRE2) library. + +This mode is available when the Altibase server character set is US7ASCII or UTF-8. It differs in syntax from the Altibase regular expression mode. For more information, please refer to [SQL Reference-A. Regular Expressions](https://github.com/ALTIBASE/Documents/blob/master/Manuals/Altibase_7.3/eng/SQL%20Reference.md#appendix-a-regular-expressions). + +#### VARRAY_MEMORY_MAXIMUM + +##### Data Type + +Unsigned Long + +##### Default Value + +209715200 (200M) + +##### Attributes + +Read-Write, Single Value + +##### Range + +[1048576, 264-1] + +##### Description + +This property limits the amount of memory available for each VARRAY variable. + +When expanding VARRAY variables, memory usage can increase. If the memory usage exceeds the limit during expansion, an error occurs. + +This property can be changed using the ALTER SYSTEM statement while Altibase is running. + diff --git a/Manuals/Altibase_7.3/eng/General Reference-2.The Data Dictionary.md b/Manuals/Altibase_7.3/eng/General Reference-2.The Data Dictionary.md index 99381f39c..7373ab5a9 100644 --- a/Manuals/Altibase_7.3/eng/General Reference-2.The Data Dictionary.md +++ b/Manuals/Altibase_7.3/eng/General Reference-2.The Data Dictionary.md @@ -1,4 +1,4 @@ -# General Reference-2.The Data Dictionary +General Reference-2.The Data Dictionary #### Altibase 7.3 @@ -2639,8 +2639,10 @@ This meta table contains information related to replication. | REPLICATION_NAME | VARCHAR(40) | The name of the replication object | | GIVE_UP_XSN | BIGINT | The XSN at which replication was most recently abandoned | | PARALLEL_APPLIER_COUNT | INTEGER | The number of appliers | -| REMOTE_XSN | BIGINT | The most recently processed SN on the remote server. | +| REMOTE_XSN | BIGINT | The most recently processed SN on the remote server | | APPLIER_INIT_BUFFER_SIZE | BIGINT | Initial size of applier buffer | +| PEER_REPLICATION_NAME | VARCHAR(40) | 로컬 이중화한 원격 이중화 이름
Local replicated remote replication name | +| REMOTE_LAST_DDL_XSN | BIGINT | The most recently processed DDL statement's SN on the remote server | [13] SN: The identification number of the log record @@ -2714,7 +2716,8 @@ This flag indicates whether to use the recovery and offline options, which are e - 2(00010): Use the offline option - 4(00100): Use the gapless option - 8(01000): Use the parallel applier option -- 16(10000): Use the replication transaction grouping option +- 16(010000): Use the replication transaction grouping option +- 32(100000): Use the local replication option ##### INVALID_RECOVERY @@ -2753,6 +2756,14 @@ This property specifies the initial buffer size of the parallel applier when rep If the number of parallel applier queues is less than the value of the property REPLICATION_RECEIVER_APPLIER_QUEUE_SIZE, then the number of parallel applier queues is set to the value specified in the property REPLICATION_RECEIVER_APPLIER_QUEUE_SIZE. +##### PEER_REPLICATION_NAME + +This is a remote replication name when using the local replication option. + +##### REMOTE_LAST_DDL_XSN + +This is the most recently processed DDL statement's SN on the remote server + #### Example \ The following is an example of returning values when using the replication gapless option and parallel applier option together on a created replication rep1. @@ -2769,6 +2780,31 @@ OPTIONS 1 row selected. ``` +### SYS_REPL_RECEIVER_ + +This meta table records the SN information of the remote server. + +| Column name | Type | Description | +| ---------------- | ----------- | --------------------------------------------------- | +| REPLICATION_NAME | VARCHAR(40) | Replication name | +| REMOTE_XSN | BIGINT | The most recently processed SN on the remote server | + +#### Column Information + +##### REPLICATION_NAME + +This is the name of the replication object, which is defined by the user, and corresponds to a REPLICATION_NAME in the SYS_REPLICATIONS_ meta table + +##### REMOTE_XSN + +This is the most recently processed SN on the remote server. When the Sender is restarted, the log with the SN smaller than the corresponding REMOTE_XSN is not sent but skipped. + +#### Reference Tables + +``` +SYS_REPLICATIONS_ +``` + ### SYS_REPL_HOSTS\_ This meta table contains information related to remote servers defined in replication objects. @@ -2844,7 +2880,7 @@ One replication object can pertain to more than one table, and SYS_REPL_ITEMS_ h ##### REPLICATION_NAME -This is the name of the replication object, which is defined by the user, and corresponds to a REPLICATION_NAME in the SYS_REPLICATIONS_ meta table +This is the name of the replication object, which is defined by the user, and corresponds to a REPLICATION_NAME in the SYS_REPLICATIONS_ meta table. ##### TABLE_OID @@ -3029,6 +3065,7 @@ This meta table is for storing information about columns that are currently repl | MT_SCALE | INTEGER | The number of digits to the right of the decimal point | | MT_ENCRYPT_PRECISION | INTEGER | The number of digits in an encrypted column | | MT_POLICY_NAME | VARCHAR(16) | The name of the policy used for an encrypted column | +| MT_SRID | INTEGER | SRID applied to the GEOMETRY column | | SM_ID | INTEGER | The column identifier | | SM_FLAG | INTEGER | An internal flag | | SM_OFFSET | INTEGER | The internal offset | @@ -3081,6 +3118,10 @@ For an encrypted numeric type column, this is the number of digits in the column For an encrypted column, this is the name of the policy used for the column. +##### MT_SRID + +For a GEOMETRY column, this is the SRID applied to the column. + ##### SM_ID This is the column identifier. Column identifiers start with 0. @@ -3233,14 +3274,23 @@ SYS_REPL_OLD_INDEX_COLUMNS_ This meta table contains information about tables currently being replicated by the replication Sender thread. -| Column name | Type | Description | -| -------------------- | ------------ | --------------------------------------- | -| REPLICATION_NAME | VARCHAR(40) | The partition name | -| TABLE_OID | BIGINT | The table object identifier | -| USER_NAME | VARCHAR(128) | The user name | -| TABLE_NAME | VARCHAR(128) | The table name | -| PARTITION_NAME | VARCHAR(128) | The name of the replication | -| PRIMARY_KEY_INDEX_ID | INTEGER | The index identifier of the primary key | +| Column name | Type | Description | +| --------------------- | ------------- | ------------------------------------------------------------ | +| REPLICATION_NAME | VARCHAR(40) | The partition name | +| TABLE_OID | BIGINT | The table object identifier | +| USER_NAME | VARCHAR(128) | The user name | +| TABLE_NAME | VARCHAR(128) | The table name | +| PARTITION_NAME | VARCHAR(128) | The name of the replication | +| PRIMARY_KEY_INDEX_ID | INTEGER | The index identifier of the primary key | +| REMOTE_USER_NAME | VARCHAR(128) | The name of a user owning a target table on the remote server | +| REMOTE_TABLE_NAME | VARCHAR(128) | The name of a target table on the remote server | +| REMOTE_PARTITION_NAME | VARCHAR(128) | The name of a partition on the remote server | +| PARTITION_ORDER | INTEGER | The position of the partition (required for hash partitions) | +| PARTITION_MIN_VALUE | VARCHAR(4000) | The minimum reference value for a partition (NULL in the case of a hash partition) | +| PARTITION_MAX_VALUE | VARCHAR(4000) | The maximum reference value for a partition (NULL in the case of a hash partition) | +| INVALID_MAX_SN | BIGINT | The highest log SN to skip | +| PARTITION_METHOD | INTEGER | The partitioning method | +| PARTITION_COUNT | INTEGER | Total number of partitioned table | #### Column Information @@ -3268,12 +3318,56 @@ This is the name of the partition containing the table being replicated on the l This is the identifier of a primary key index. +##### REMOTE_USER_NAME + +This is the user name of the owner of the replication target table in the remote system. + +##### REMOTE_TABLE_NAME + +This is the name of the replication target table in the remote system. + +##### REMOTE_PARTITION_NAME + +This is the name of the replication target partition on the remote server. + +##### PARTITION_ORDER + +This is the position of the partition among the partitions. It is required for hash partitions. + +##### PARTITION_MIN_VALUE + +This is a string that gives the minimum reference value for a partition. It is NULL for hash partitions. + +##### PARTITION_MAX_VALUE + +This is a string that gives the maximum reference value for a partition. It is NULL for hash partitions. + +##### INVALID_MAX_SN + +If DDL statements or Sync operations are executed on replication target tables, the most recently recorded SN is saved here. Table logs up to this SN are skipped when the table is replicated. + +##### PARTITION_METHOD + +This indicates the partitioning method. + +- 0: RANGE +- 1: HASH +- 2: LIST +- 3: RANGE PARTITIONING USING HASH +- 100: NONE + +##### PARTITION_COUNT + +지역 서버의 이중화 대사 테이블이 속해 있는 파티션드 테이블을 구성하는 파티션 테이블의 총 개수 + #### Reference Tables ``` +SYS_TABLES_ SYS_REPL_OLD_COLUMNS_ SYS_REPL_OLD_INDICES_ SYS_REPL_OLD_INDEX_COLUMNS_ +V$TABLESPACES ``` ### SYS_REPL_TABLE_OID_IN_USE_ @@ -4363,9 +4457,6 @@ Performance views are identified by the prefix V$. The following table lists all | V\$STABLE_MEM_DATAFILES | Information about the paths of data file(s) | | V\$STATEMENT | Information about statements for all current Altibase sessions | | V\$STATNAME | Information about the name and status of the system and sessions | -| V\$ST_ANGULAR_UNIT | Reserved for future use | -| V\$ST_AREA_UNIT | Reserved for future use | -| V\$ST_LINEAR_UNIT | Reserved for future use | | V\$SYSSTAT | Information about the status of the system | | V\$SYSTEM_CONFLICT_PAGE | Information about latch contention according to page type | | V\$SYSTEM_EVENT | Cumulative statistical information about waits from startup to the current time, classified according to wait event | @@ -7602,6 +7693,30 @@ This view displays information about stored procedures being used by the system. ##### PROC_OID +This is an OID, which is a unique object identifier for a stored procedure. + +##### PIECE + +The complete text for a stored procedure is divided into text fragments 64 bytes long and then saved. PIECE shows the serial numbers for these 64-byte fragments, starting from 0. + +##### TEXT + +This shows the contents of the 64-byte text fragment that is part of the stored procedure text. + +### V\$PROCINFO + +| Column name | Type | Description | +|--------------|-------------|----------------------------------| +| PROC_OID | BIGINT | The object identifier of the stored procedure | +| MODIFY_COUNT | INTEGER | The number of times a stored procedure was recreated or recompiled | +| STATUS | VARCHAR(7) | The status of the object. If INVALID, it is not executable | +| SESSION_ID | INTEGER | The ID of the session that changed the STATUS of the stored procedure | +| PROC_TYPE | VARCHAR(10) | The type of stored procedure | + +#### Column Information + +##### PROC_OID + The identifier of a stored procedure or stored function, which is the same as a PROC_OID value in the SYS_PROCEDURES_ meta table. ##### MODIFY_COUNT @@ -7628,30 +7743,6 @@ The type of stored procedure. The possible values are: - UNKNOWN : If the compilation of the stored procedure fails when starting the server, the internal procedure type is not known, so it is marked UNKNOWN. Subsequently, when compiled and in VALID status, the correct type is set. -### V\$PROCINFO - -| Column name | Type | Description | -|--------------|-------------|----------------------------------| -| PROC_OID | BIGINT | The object identifier of the stored procedure | -| MODIFY_COUNT | INTEGER | The number of times a stored procedure was recreated or recompiled | -| STATUS | VARCHAR(7) | The status of the object. If INVALID, it is not executable | -| SESSION_ID | INTEGER | The ID of the session that changed the STATUS of the stored procedure | -| PROC_TYPE | VARCHAR(10) | The type of stored procedure | - -#### Column Information - -##### PROC_OID - -This is an OID, which is a unique object identifier for a stored procedure. - -##### PIECE - -The complete text for a stored procedure is divided into text fragments 64 bytes long and then saved. PIECE shows the serial numbers for these 64-byte fragments, starting from 0. - -##### TEXT - -This shows the contents of the 64-byte text fragment that is part of the stored procedure text. - ### V\$PROPERTY This view displays information about all internally set Altibase properties. @@ -7698,6 +7789,20 @@ This is the maximum value that the property can have. The actual values set for the property. +### V$QUEUE_DELETE_OFF + +This view stores object identifier(OID) information of a queue table which does not allow DELETE statements. A queue table using the DELETE OFF clause in the CREATE QUEUE or ALTER QUEUE statements does not allow DELETE statements. + +| Column name | Type | Description | +| ----------- | ------ | --------------------------- | +| TABLE_OID | BIGINT | The table object identifier | + +#### Column Information + +##### TABLE_OID + +This is the table object identifier. It corresponds one-to-one with a TABLE_OID in the SYS_TABLES meta table. + ### V\$REPEXEC This view displays information related to the replication manager. @@ -8818,6 +8923,362 @@ When data in replication target tables on the local server are synchronized with While synchronization is underway, this is the number of records that have been synchronized. A value of -1 indicates that synchronization is complete. +### V$REPL_REMOTE_META_REPLICATIONS + +This view displays the sender's SYS_REPLICATIONS meta table information that the receiver holds. + +Users can access this view on the server where the receiver thread is running. + +| Column name | Type | Description | +| ------------------------ | ----------- | ------------------------------------------------------------ | +| REPLICATION_NAME | VARCHAR(40) | The replication name | +| XSN | BIGINT | The Restart SN (Sequence Number), i.e. the SN from which the Sender will resume transmission of XLogs13 | +| ITEM_COUNT | INTEGER | The number of replication target tables | +| CONFLICT_RESOLUTION | INTEGER | The replication conflict resolution method | +| REPL_MODE | INTEGER | The default replication mode | +| ROLE | INTEGER | The role of replication thread | +| OPTIONS | INTEGER | The flag for the additional replication features | +| REMOTE_FAULT_DETECT_TIME | DATE | The time at which a fault was detected on a remote server | + +#### Column Information + +##### REPLICATION_NAME + +This is the name of replication on the remote server. Users define this when they create replication. + +##### XSN + +This indicates the SN from which the Sender thread must begin sending logs when replication is started. + +##### ITEM_COUNT + +This is the number of replication target tables. This number corresponds to the number of records in the SYS_REPL_ITEMS_ meta table for this replication object, with one record corresponding to each of these tables. + +##### CONFLICT_RESOLUTION + +This describes the replication conflict resolution method. + +- 0: Default +- 1: Act as the Master server +- 2: Act as the Slave server + +Please refer to the [*Replication Manual*](https://github.com/ALTIBASE/Documents/blob/master/Manuals/Altibase_7.3/eng/Replication%20Manual.md) for more detailed information about replication conflict resolution methods. + +##### REPL_MODE + +This is the default replication mode, which is set when the replication object is created. + +- 0: LAZY MODE (default value) +- 2: EAGER MODE + +The default replication mode is used if the ALTER SESSION SET REPLICATION statement is not used to set the replication mode for a session. + +For more detailed information about the default replication mode, please refer to the [*Replication Manual*](https://github.com/ALTIBASE/Documents/blob/master/Manuals/Altibase_7.3/eng/Replication%20Manual.md). For detailed information about the ALTER SESSION SET REPLICATION statement, please refer to the [*SQL Reference*](https://github.com/ALTIBASE/Documents/blob/master/Manuals/Altibase_7.3/eng/SQL%20Reference.md). + +##### ROLE + +This indicates the role of the replication thread. + +- 0: Normal replication (Any roles are not specified) +- 1: Dedicated replication for Log Analyzer (Only use FOR ANALYSIS) +- 2: Propagable Logging (Use FOR PROPAGABLE LOGGING) +- 3: Propagation (Use FOR PROPAGATION) +- 4: Set Propagation on Log Analyzer replication(Use FOR ANALYSIS PROPAGATION) + +For more information about dedicated replication for Log Analyzer, please refer to [*Log Analyzer User's Manual*](https://github.com/ALTIBASE/Documents/blob/master/Manuals/Altibase_7.3/eng/Log%20Analyzer%20User's%20Manual.md). + +##### OPTIONS + +This flag indicates whether to use the recovery and offline options, which are extra replication features. The replication option types are as in the following. Each option is controlled by binary number and expressed as a decimal number. If more than two options are used, the sum of the binary numbers of each option is returned as decimal numbers. + +- 0(000000): Do not use any replication options +- 1(000001): Use the recovery option +- 2(000010): Use the offline option +- 4(000100): Use the replication gapless option +- 8(001000): Use the parallel receiver applier option +- 16(010000): Use the replication transaction grouping option +- 32(100000): Use the local replication option + +##### REMOTE_FAULT_DETECT_TIME + +This is the time at which a fault was detected on a remote server while replication was running. + +### V$REPL_REMOTE_META_ITEMS + +It displays the information from the SYS_REPL_ITEMS_ metadata table associated with the sender that the receiver holds. + +Users can access this view on the server where the receiver thread is running. + +| Column name | Type | Description | +| --------------------- | ------------ | ------------------------------------------------------------ | +| REPLICATION_NAME | VARCHAR(40) | The replication name | +| TABLE_OID | BIGINT | The table object identifier | +| LOCAL_USER_NAME | VARCHAR(128) | The name of a user owning a target table on the local server | +| LOCAL_TABLE_NAME | VARCHAR(128) | The name of a target table on the local server | +| LOCAL_PARTITION_NAME | VARCHAR(128) | The name of a partition on the local server | +| REMOTE_USER_NAME | VARCHAR(128) | The user name of the target table's owner on the remote server. | +| REMOTE_TABLE_NAME | VARCHAR(128) | The name of a target table on the remote server | +| REMOTE_PARTITION_NAME | VARCHAR(128) | The name of a partition on the remote server | +| INVALID_MAX_SN | BIGINT | The highest log SN to skip | + +#### Column Information + +##### REPLICATION_NAME + +This is the name of the replication object, which is defined by the user, and corresponds to a REPLICATION_NAME in the SYS_REPLICATIONS_ meta table. + +##### TABLE_OID + +This is the identifier of the replication target table or partition on the remote server, and corresponds to a TABLE_OID value in the SYS_TABLES_ meta table or a PARTITION_OID value in the SYS_TABLES_PARTITIONS meta table. + +##### LOCAL_USER_NAME + +원격 서버의 이중화 대상 테이블 소유자의 사용자 이름으로, 원격 서버의 SYS_USERS_ 메타 테이블의 한 USER_NAME 값과 동일하다. + +This is the user name of the owner of the replication target table in the local system, and corresponds to a USER_NAME in the SYS_USERS_ meta table. + +##### LOCAL_TABLE_NAME + +원격 서버의 이중화 대상 테이블의 이름으로, 원격 서버의 SYS_TABLES_ 메타 테이블의 한 TABLE_NAME 값과 동일하다. + +This is the name of the replication target table in the local system, and corresponds to a TABLE_NAME in the SYS_TABLES_ meta table. + +##### LOCAL_PARTITION_NAME + +원격 서버의 이중화 대상 파티션의 이름이다. + +This is the name of the replication target partition on the local server. + +##### REMOTE_USER_NAME + +지역 서버의 이중화 대상 테이블 소유자의 사용자 이름으로, 지역 서버의 SYS_USERS_ 메타 테이블의 한 USER_NAME 값과 동일하다. + +##### REMOTE_TABLE_NAME + +지역 서버의 이중화 대상 테이블의 이름으로, 지역 서버의 SYS_TABLES_ 메타 테이블의 한 TABLE_NAME 값과 동일하다. + +##### REMOTE_PARTITION_NAME + +지역 서버의 이중화 대상 파티션의 이름이다. + +##### INVALID_MAX_SN + +If DDL statements or Sync operations are executed on replication target tables, the most recently recorded SN is saved here. Table logs up to this SN are skipped when the table is replicated. + +### V$REPL_REMOTE_META_COLUMNS + +It displays the information from the SYS_REPL_OLD_COLUMNS_ meta data table associated with the sender that the receiver holds. + +Users can access this view on the server where the receiver thread is running. + +| Column name | Type | Description | +| -------------------- | ------------ | ------------------------------------------------------ | +| REPLICATION_NAME | VARCHAR(40) | The replication name | +| TABLE_OID | BIGINT | The table object identifier | +| COLUMN_NAME | VARCHAR(128) | The column name | +| MT_DATATYPE_ID | INTEGER | The data type identifier | +| MT_LANGUAGE_ID | INTEGER | The language identifier | +| MT_FLAG | INTEGER | An internal flag | +| MT_PRECISION | INTEGER | The number of digits | +| MT_SCALE | INTEGER | The number of digits to the right of the decimal point | +| MT_ENCRYPT_PRECISION | INTEGER | The number of digits in an encrypted column | +| MT_POLICY_NAME | VARCHAR(16) | The name of the policy used for an encrypted column | +| MT_SRID | INTEGER | The SRID applied to GEOMETRY column | +| SM_ID | INTEGER | The column identifier | +| SM_FLAG | INTEGER | An internal flag | +| SM_OFFSET | INTEGER | The internal offset | +| SM_SIZE | INTEGER | The internal size | +| QP_FLAG | INTEGER | The internal flag | + +#### Column Information + +##### REPLICATION_NAME + +This is the replication name, which is specified by the user. It corresponds to a REPLICATION_NAME in the SYS_REPLICATIONS_ meta table. + +##### TABLE_OID + +This is the identifier for a replication target table currently being used by the replication Sender thread. Its value may not correspond to any TABLE_OID value in SYS_TABLES_. + +##### COLUMN_NAME + +This is the name of a column currently being replicated by the replication Sender thread. + +##### MT_DATATYPE_ID + +This is the data type identifier, and is an internal value. + +##### MT_LANGUAGE_ID + +This is the language identifier, and is an internal value. + +##### MT_FLAG + +This is an internal flag used by Altibase server. + +##### MT_PRECISION + +For a numeric type column, this is the number of digits in the column. For a character type column, this is the length of character data types in the column. + +##### MT_SCALE + +For a numeric type column, this is the number of digits to the right of the decimal point in the column. + +##### MT_ENCRYPT_PRECISION + +For an encrypted numeric type column, this is the number of digits in the column. + +##### MT_POLICY_NAME + +For an encrypted column, this is the name of the policy used for the column. + +##### MT_SRID + +For a GEOMETRY column, this is SRID applied to the column. + +##### SM_ID + +This is the column identifier. Column identifiers start with 0. + +##### SM_FLAG + +This is a flag internally used by Altibase. + +##### SM_OFFSET + +This is an offset value internally used by Altibase. + +##### SM_SIZE + +This is a size value internally used by Altibase server. + +##### QP_FLAG + +This is the flag used internally by the Altibase server. + +### V$REPL_REMOTE_META_INDEX_COLUMNS + +It displays the information from the SYS_REPL_OLD_INDEX_COLUMNS_ meta data table associated with the sender that the receiver holds. + +Users can access this view on the server where the receiver thread is running. + +| Column name | Type | Description | +| ---------------- | ----------- | --------------------------- | +| REPLICATION_NAME | VARCHAR(40) | The replication name | +| TABLE_OID | BIGINT | The table object identifier | +| INDEX_ID | INTEGER | The index identifier | +| KEY_COLUMN_ID | INTEGER | The column identifier | +| KEY_COLUMN_FLAG | INTEGER | An internal flag | + +#### Column Information + +##### REPLICATION_NAME + +This value corresponds to a REPLICATION_NAME in the SYS_REPLICATIONS_ meta table, and is the user-defined replication name. + +##### TABLE_OID + +This is the identifier of a table currently being replicated by the replication Sender thread. Its value may not correspond to any TABLE_OID value in SYS_TABLES_. + +##### INDEX_ID + +This is the identifier of an index currently being replicated by the replication Sender thread. + +##### KEY_COLUMN_ID + +This is the identifier of the column on which the index is based. + +##### KEY_COLUMN_FLAG + +This is an internal flag for the column on which the index is based. + +### V$REPL_REMOTE_META_INDICES + +It displays the information from the SYS_REPL_OLD_INDICES_ meta data table associated with the sender that the receiver holds. + +Users can access this view on the server where the receiver thread is running. + +| Column name | Type | Description | +| ---------------- | ------------ | ------------------------------------------------------------ | +| REPLICATION_NAME | VARCHAR(40) | The replication name | +| TABLE_OID | BIGINT | The table object identifier | +| INDEX_ID | INTEGER | The index identifier | +| INDEX_NAME | VARCHAR(128) | The index name | +| TYPE_ID | INTEGER | The index type identifier | +| IS_UNIQUE | CHAR(1) | Indicates whether or not the index is globally unique | +| IS_RANGE | CHAR(1) | Indicates whether or not range scanning is possible using the index | + +#### Column Information + +##### REPLICATION_NAME + +This is the user-defined replication name. Its value corresponds to a REPLICATION_NAME value in the SYS_REPLICATIONS_ meta table. + +##### TABLE_OID + +This is the identifier of a table currently being replicated by the replication Sender thread. Its value may be different from that of TABLE_OID in the SYS_TABLES_ meta table. + +##### INDEX_ID + +This is the identifier of an index currently being replicated by the replication Sender thread. + +##### INDEX_NAME + +This is the name of an index currently being replicated by the replication Sender thread. + +##### TYPE_ID + +This is an index type identifier, and is an internal value. + +##### IS_UNIQUE + +This indicates whether or not the index is globally unique. 'Y' signifies that the index is globally unique, and 'N' signifies that it is not globally unique. + +##### IS_RANGE + +This indicates whether or not the index is locally unique. 'Y' signifies that it is locally unique, and 'N' means that it is not locally unique. + +### V$REPL_REMOTE_META_CHECKS + +This view displays the information about the replication table constraint of the sender that the receiver holds. + +Users can access this view on the server where the receiver thread is running. + +| Column name | Type | Description | +| ---------------- | ------------- | ------------------------------------------------------------ | +| REPLICATION_NAME | VARCHAR(40) | The replication name | +| TABLE_OID | BIGINT | The table object identifier | +| CONSTRAINT_ID | INTEGER | The constraint identifier | +| CONSTRAINT_NAME | VARCHAR(128) | The name of the constraint | +| COLUMN_CNT | INTEGER | The number of columns that are associated with the constraint | +| CHECK_CONDITION | VARCHAR(4000) | The character string condition of the CHECK constraint | + +#### Column Information + +##### REPLICATION_NAME + +This is the user-defined replication name. Its value corresponds to a REPLICATION_NAME value in the SYS_REPLICATIONS_ meta table. + +##### TABLE_OID + +This is the identifier of a table currently being replicated by the replication Sender thread. Its value may be different from that of TABLE_OID in the SYS_TABLES_ meta table. + +##### CONSTRAINT_ID + +This is a constraint identifier. It is automatically assigned by the system sequence. + +##### CONSTRAINT_NAME + +This is the name of the constraint. + +##### COLUMN_CNT + +This is the number of columns associated with the constraint. For example, for a constraint such as UNIQUE (i1, i2, i3), this value would be 3. + +##### CHECK_CONDITION + +This displays the Integrity Rule defined by the user at CHECK constraint specification. + ### V\$RESERVED_WORDS This view displays all the keywords supported by SQL statement. diff --git a/Manuals/Altibase_7.3/kor/General_Reference-1.Data Types & Altibase Properties.md b/Manuals/Altibase_7.3/kor/General_Reference-1.Data Types & Altibase Properties.md index d931c0175..246c0a01b 100644 --- a/Manuals/Altibase_7.3/kor/General_Reference-1.Data Types & Altibase Properties.md +++ b/Manuals/Altibase_7.3/kor/General_Reference-1.Data Types & Altibase Properties.md @@ -15732,7 +15732,7 @@ Unsigned Integer ##### 속성 -변경 가, 단일 값 +변경 가능, 단일 값 ##### 값의 범위 @@ -15907,7 +15907,7 @@ Unsigned Integer ##### 설명 -PSM을 컴파일할 때 재귀 호출 또는 참조 깊이의 수를 제한합니다. 재귀 호출 또는 참조 깊이의 수가 설정 값을 초과하면 에러가 발생한다. +PSM을 컴파일할 때 재귀 호출 또는 참조 깊이의 수를 제한한다. 재귀 호출 또는 참조 깊이의 수가 설정 값을 초과하면 에러가 발생한다. #### PSM_NCHAR_UTF16_DEFAULT_PRECISION