CUBRIDMAN-222 :매뉴얼 수정 작업

en/admin/config.rst

@@ -1042,7 +1042,7 @@ The following are parameters related to concurrency control and locks of the dat
 
     *   **TRAN_SERIALIZABLE** : This isolation level ensures the highest level of consistency. For details, see :ref:`isolation-level-6`.
 
-    *   **TRAN_REP_READ** : This isolation level can incur phantom read. For details, see :ref:`isolation-level-5`.
+    *   **TRAN_REP_READ** : This isolation level prevents dirty reads, non-repeatable reads, and phantom reads due to snapshot isolation. For details, see :ref:`isolation-level-5`.
 
     *   **TRAN_READ_COMMITTED** : This isolation level can incur unrepeatable read. For details, see :ref:`isolation-level-4`.
 
@@ -2003,13 +2003,17 @@ Query Plan Cache-Related Parameters
 
 The following are parameters related to the query plan cache functionality. The type and value range for each parameter are as follows:
 
-+-------------------------------+--------+----------+----------+----------+
-| Parameter Name                | Type   | Default  | Min      | Max      |
-+===============================+========+==========+==========+==========+
-| max_plan_cache_entries        | int    | 1,000    |          |          |
-+-------------------------------+--------+----------+----------+----------+
-| max_filter_pred_cache_entries | int    | 1,000    |          |          |
-+-------------------------------+--------+----------+----------+----------+
++--------------------------------------+--------+---------+---------+---------+
+| Parameter Name                       | Type   | Default | Min     | Max     |
++======================================+========+=========+=========+=========+
+| max_plan_cache_entries               | int    | 1,000   |         |         |
++--------------------------------------+--------+---------+---------+---------+
+| max_plan_cache_clones                | int    | 1,000   |         |         |
++--------------------------------------+--------+---------+---------+---------+
+| xasl_cache_time_threshold_in_minutes | int    | 360     |         |         |
++--------------------------------------+--------+---------+---------+---------+
+| max_filter_pred_cache_entries        | int    | 1,000   |         |         |
++--------------------------------------+--------+---------+---------+---------+
 
 **max_plan_cache_entries**
 
@@ -2019,6 +2023,13 @@ The following are parameters related to the query plan cache functionality. The
 
         max_plan_cache_entries=1000
 
+**max_plan_cache_clones**
+     The plan cache stores the XASL for a query in a serializable form. When executing the query, the XASL is converted back into its deserialized form, populated with values, and then executed.
+     The clone cache stores deserialized XASL to reuse it instead of discarding. The **max_plan_cache_clones** is a parameter that sets the maximum number of cloned cache entries a single plan can hold, and its default value is set to 1000. When a plan is deleted, its clones are also deleted.
+
+**xasl_cache_time_threshold_in_minutes**
+    It is a parameter that determines the time threshold for deciding whether to recompile (clean-up) a cached plan. It is also used when searching for a candidate plan to remove when there is no space in the plan cache. This parameter can be set in minutes, with a default value of 360 minutes.
+
 **max_filter_pred_cache_entries**
 
     **max_filter_pred_cache_entries** is a parameter used to specify the maximum number of filtered index expressions. The filtered index expressions are stored with them complied and can be immediately used in server. If it is not stored in cache, the process is required which filtered index expressions are fetched from database schema and interpreted.

en/ha.rst

@@ -1398,6 +1398,55 @@ This utility is used to output the information of CUBRID HA group and CUBRID HA
        Copylogdb testdb@nodeA:/home/cubrid/DB/testdb_nodeA (pid 2505, state registered)
        Server testdb (pid 2393, state registered_and_standby)
 
+The -v option displays detailed information about the node.
+* score: Indicates the priority of the node, with a lower score indicating a higher priority.
+* missed heartbeat: Indicates the loss rate of heartbeat signals sent between nodes configured in a HA environment. If this value is unusually high, the configuration, network, or firewall settings should be inspected.
+
+The event occurrence times for the Applylogdb, Copylogdb, and Server processes are also displayed. If no event has occurred, it is displayed as "00:00:00.000."
+* registered-time: The time when a process startup request was made via a user command.
+* deregistered-time: The time when a remote process stop request was made via a user command (applicable only to copylogdb and applylogdb).
+* shutdown-time : The time that HA-manager(cub_master) stopped the process
+* start-time : The time that HA-manager(cub_master) restarted the process
+
+**Example**
+
+::
+
+    $ cubrid heartbeat status -v
+    @ cubrid heartbeat status
+
+    HA-Node Info (current cubrid1, state master)
+      Node cubrid2 (priority 2, state slave)
+        - score 2
+        - missed heartbeat 0
+      Node cubrid1 (priority 1, state master)
+        - score -32767
+        - missed heartbeat 0
+
+    HA-Process Info (master 7392, state master)
+    Copylogdb testdb@cubrid2:/home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/databases/testdb_cubrid2 (pid 7841, state registered)
+     - exec-path [/home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/bin/cub_admin]
+     - argv      [cub_admin copylogdb -L /home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/databases/testdb_cubrid2 -m sync testdb@bagus2 ]
+     - registered-time   08/26/24 14:28:37.019
+     - deregistered-time 00/00/00 00:00:00.000
+     - shutdown-time     08/26/24 14:28:35.010
+     - start-time        08/26/24 14:28:36.012
+    Applylogdb testdb@localhost:/home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/databases/testdb_cubrid2 (pid 7746, state registered)
+     - exec-path [/home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/bin/cub_admin]
+     - argv      [cub_admin applylogdb -L /home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/databases/testdb_cubrid2 --max-mem-size=300 testdb@localhost ]
+      - registered-time   08/26/24 14:27:14.566
+      - deregistered-time 00/00/00 00:00:00.000
+      - shutdown-time     08/26/24 14:27:12.552
+      - start-time        08/26/24 14:27:13.558
+     Server testdb (pid 7904, state registered_and_active)
+      - exec-path [/home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/bin/cub_server]
+      - argv      [cub_server testdb ]
+      - registered-time   08/26/24 14:29:28.955
+      - deregistered-time 00/00/00 00:00:00.000
+      - shutdown-time     08/26/24 14:29:27.593
+      - start-time        08/26/24 14:29:28.594
+
+
 .. note:: **act**, **deact**, and **deregister** commands which were used in versions lower than CUBRID 9.0 are no longer used.
 
 .. _cubrid-service-util:

en/release_note/index.rst

@@ -37,7 +37,7 @@ CUBRID welcomes your active participation in bug reporting and looks forward to
 License
 -------
 
-The Apache license 2.0 applies to the CUBRID server engine, and the BSD license applies to CUBRID MANAGER and interfaces (APIs). For more information, see the License Policy on https://www.cubrid.org/cubrid .
+The Apache license 2.0 applies to the CUBRID server engine, and the BSD license applies to CUBRID MANAGER and interfaces (APIs). For more information, see the License Policy on https://www.cubrid.org/license.
 
 Additional Information
 ----------------------

en/sql/transaction.rst

@@ -278,7 +278,7 @@ You can set an isolation level by using the :ref:`set-transaction-isolation-leve
 +================================+========+===============+==========+========================+
 | :ref:`isolation-level-6` (6)   | X      | X             | X        | X                      |
 +--------------------------------+--------+---------------+----------+------------------------+
-| :ref:`isolation-level-5` (5)   | X      | X             | O        | X                      |
+| :ref:`isolation-level-5` (5)   | X      | X             | X        | X                      |
 +--------------------------------+--------+---------------+----------+------------------------+
 | :ref:`isolation-level-4` (4)   | X      | O             | O        | X                      |
 +--------------------------------+--------+---------------+----------+------------------------+
@@ -1288,7 +1288,6 @@ You can set the level of transaction isolation by using **isolation_level** and
 |                       | Transaction T1 may experience R read (non-repeatable read) that was updated and committed by another transaction T2 when it is repeatedly retrieving the record R.                  |
 +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 | REPEATABLE READ (5)   | Another transaction T2 cannot update the schema of table A while transaction T1 is viewing table A.                                                                                 |
-|                       | Transaction T1 may experience phantom read for the record R that was inserted by another transaction T2 when it is repeatedly retrieving a specific record.                         |
 +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 | SERIALIZABLE (6)      | Temporarily disabled - details in :ref:`isolation-level-6`                                                                                                                          |
 +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

en/upgrade.rst

@@ -44,6 +44,25 @@
 
     In 2008 R4.0 or before, TIMESTAMP '1970-01-01 00:00:00'(GMT) is the minimum value of TIMESTAMP, but in 2008 4.1 or later, it is recognized as zerodate and TIMESTAMP '1970-01-01 00:00:01'(GMT) is the minimum value of TIMESTAMP.
 
+**Compatibility table**
+
++-----------+-----+-----+-----+-----+-----+-----+
+| Vesion    | 11.3| 11.2| 11.0| 10.2| 10.1| 10.0|
++===========+=====+=====+=====+=====+=====+=====+
+| 11.3      | O   | O   |     |     |     |     |
++-----------+-----+-----+-----+-----+-----+-----+
+| 11.2      | O   | O   |     |     |     |     |
++-----------+-----+-----+-----+-----+-----+-----+
+| 11.0      |     |     | O   |     |     |     |
++-----------+-----+-----+-----+-----+-----+-----+
+| 10.2      |     |     |     | O   |     |     |
++-----------+-----+-----+-----+-----+-----+-----+
+| 10.1      |     |     |     |     | O   |     |
++-----------+-----+-----+-----+-----+-----+-----+
+| 10.0      |     |     |     |     |     | O   |
++-----------+-----+-----+-----+-----+-----+-----+
+
+
 **Reconfiguring environments for replication or HA**
 
 *   From 2008 R4.0, the replication feature is no longer supported; therefore, it is recommended to reconfigure the DB migration and HA environment for systems in which previous replication versions are used. In addition, for systems that use Linux Heartbeat-based HA feature, which is provided in CUBRID 2008 R2.0 and 2008 R2.1, you must reconfigure to DB migration and the CUBRID Heartbeat-based HA environment for better operational stability(see :ref:`ha-db-migration`).
@@ -55,7 +74,7 @@
 *   **Java SP server** should be started before using Java stored procedure/function. See :ref:`jsp-starting-javasp`.
 
 Upgrading from CUBRID 9.2/9.3/10.0/10.1/10.2/11.0/11.2 to CUBRID 11.3
 ----------------------------------------------------------------
 
 Users who are using versions CUBRID 9.2/9.3/10.0/10.1/10.2/11.0/11.2 should install 11.3 in the different directory, migrate the databases to 11.3 and modify parameter values in the previous environment configuration file.
 

ko/admin/config.rst

@@ -1037,7 +1037,7 @@ CUBRID 설치 시 생성되는 기본 데이터베이스 환경 설정 파일(**
 
     *   **TRAN_SERIALIZABLE** : 가장 높은 수준의 일관성을 보장하는 격리 수준이며, :ref:`isolation-level-6` 을 참고한다.
 
-    *   **TRAN_REP_READ** : 유령 읽기(phantom read)가 발생할 수 있는 격리 수준이며, :ref:`isolation-level-5` 를 참고한다.
+    *   **TRAN_REP_READ** : snapshot isolation 때문에 더티 읽기, 반복 불가능한 읽기 및 유령 읽기가 발생하지 않는 수준이며, :ref:`isolation-level-5` 를 참고한다.
 
     *   **TRAN_READ_COMMITTED** : 반복 불가능한 읽기(unrepeatable read)가 발생할 수 있는 격리 수준이며, :ref:`isolation-level-4` 를 참고한다.
 
@@ -1975,13 +1975,17 @@ CUBRID 설치 시 생성되는 기본 데이터베이스 환경 설정 파일(**
 
 다음은 질의 계획에 대한 캐시 기능과 관련된 파라미터로 각 파라미터의 타입과 설정 가능한 값의 범위는 다음과 같다.
 
-+-------------------------------+--------+---------+---------+---------+
-| 파라미터 이름                 | 타입   | 기본값  | 최소값  | 최대값  |
-+===============================+========+=========+=========+=========+
-| max_plan_cache_entries        | int    | 1,000   |         |         |
-+-------------------------------+--------+---------+---------+---------+
-| max_filter_pred_cache_entries | int    | 1,000   |         |         |
-+-------------------------------+--------+---------+---------+---------+
++--------------------------------------+--------+---------+---------+---------+
+| 파라미터 이름                        | 타입   | 기본값  | 최소값  | 최대값  |
++======================================+========+=========+=========+=========+
+| max_plan_cache_entries               | int    | 1,000   |         |         |
++--------------------------------------+--------+---------+---------+---------+
+| max_plan_cache_clones                | int    | 1,000   |         |         |
++--------------------------------------+--------+---------+---------+---------+
+| xasl_cache_time_threshold_in_minutes | int    | 360     |         |         |
++--------------------------------------+--------+---------+---------+---------+
+| max_filter_pred_cache_entries        | int    | 1,000   |         |         |
++--------------------------------------+--------+---------+---------+---------+
 
 **max_plan_cache_entries**
 
@@ -1991,6 +1995,14 @@ CUBRID 설치 시 생성되는 기본 데이터베이스 환경 설정 파일(**
 
         max_plan_cache_entries=1000
 
+**max_plan_cache_clones**
+
+    플랜 캐시(plan cache)에는 질의에 대한 직렬화(serializable)된 xasl 저장되어 있는데, 질의 수행기는 플랜 캐시에 저장된 작렬화된 xasl를 역직렬화(deserializable)한 후 사용할 값과 함께 수행한다. 클론 캐시(clone cache)는 질의 수행기가  최소한의 역직렬화 수행하기 위해 역직렬화된 xasl을 저장하여 재 사용하기 위한 캐시 파라미터이다. 기본값은 1000이며, 하나의 플랜이 최대로 가질 수 있는 캐시 값입니다. 플랜이 삭제되면 해당 플랜의 클론 캐시에 저장된 역직렬화된 xasl도 함께 삭제된다. 
+
+**xasl_cache_time_threshold_in_minutes**
+
+     캐시된 플랜을 재 수행(clean-up)할 것인지를 판단하는 파라미터로, 해당 파라미터는 플랜 캐시에 추가할 공간이 없는 경우도 제거할 대상을 찾기 위해 사용된다. 분단위로 설정 가능하며, 기본값은 360분이다.
+
 **max_filter_pred_cache_entries**
 
     **max_filter_pred_cache_entries** 는 메모리에 캐시하는 필터링된 인덱스 표현식의 최대 개수를 설정하는 파라미터이다. 필터링된 인덱스 표현식은 컴파일된 상태로 저장되므로, 서버에서 즉시 사용할 수 있다. 캐시에 저장되어 있지 않을 경우, 필터링된 인덱스 표현식을 데이터베이스 스키마에서 가져와서 해석하는 과정이 필요하다.

ko/ha.rst

@@ -1394,6 +1394,57 @@ CUBRID HA 그룹 정보와 CUBRID HA 구성 요소의 정보를 확인할 수 
        Copylogdb testdb@nodeA:/home/cubrid/DB/testdb_nodeA (pid 2505, state registered)
        Server testdb (pid 2393, state registered_and_standby)
 
+
+-v의 경우, 해당노드의 상세정보를 출력한다.
+* score는 노드의 우선순위를 나타내며, 낮을 수록 높은 우선순위를 가진다.
+* missed heartbeat은 서로의 노드를 인식하는 heartbeat의 유실율을 나타내며, 해당 값이 높은 경우 환경설정/네트워크/방화벽 등을 점검해야 한다.
+
+Applylogdb, Copylogdb, Server 프로세스에 이벤트 발생 시간이며,이벤트가 발생하지 않은 경우 00:00:00.000으로 표기된다.
+
+* registered-time : 명령어를 통하여 프로세스 구동 요청 시간
+* deregistered-time : 명령어를 통하여 원격 프로세스 정지 요청 시간 (copylogdb와 applylogdb만 해당)
+* shutdown-time : HA 매니저(cub_master)가 프로세스를 정지한 시간
+* start-time : HA 매니저(cub_master)가 프로세스를 재 구동시간 
+
+**예시** 
+
+::
+
+    $ cubrid heartbeat status -v
+    @ cubrid heartbeat status
+
+    HA-Node Info (current cubrid1, state master)
+      Node cubrid2 (priority 2, state slave)
+        - score 2
+        - missed heartbeat 0
+      Node cubrid1 (priority 1, state master)
+        - score -32767
+        - missed heartbeat 0
+
+    HA-Process Info (master 7392, state master)
+    Copylogdb testdb@cubrid2:/home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/databases/testdb_cubrid2 (pid 7841, state registered)
+     - exec-path [/home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/bin/cub_admin]
+     - argv      [cub_admin copylogdb -L /home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/databases/testdb_cubrid2 -m sync testdb@bagus2 ]
+     - registered-time   08/26/24 14:28:37.019
+     - deregistered-time 00/00/00 00:00:00.000
+     - shutdown-time     08/26/24 14:28:35.010
+     - start-time        08/26/24 14:28:36.012
+    Applylogdb testdb@localhost:/home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/databases/testdb_cubrid2 (pid 7746, state registered)
+     - exec-path [/home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/bin/cub_admin]
+     - argv      [cub_admin applylogdb -L /home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/databases/testdb_cubrid2 --max-mem-size=300 testdb@localhost ]
+     - registered-time   08/26/24 14:27:14.566
+     - deregistered-time 00/00/00 00:00:00.000
+     - shutdown-time     08/26/24 14:27:12.552
+     - start-time        08/26/24 14:27:13.558
+    Server testdb (pid 7904, state registered_and_active)
+     - exec-path [/home/cubha/CUBRID-11.3.1.1142-bee7aa8-Linux.x86_64/bin/cub_server]
+     - argv      [cub_server testdb ]
+     - registered-time   08/26/24 14:29:28.955
+     - deregistered-time 00/00/00 00:00:00.000
+     - shutdown-time     08/26/24 14:29:27.593
+     - start-time        08/26/24 14:29:28.594
+
+
 .. note:: CUBRID 9.0 미만 버전에서 사용되었던 **act**, **deact**, **deregister** 명령은 더 이상 사용되지 않는다.
 
 .. _cubrid-service-util:

ko/release_note/index.rst

@@ -37,7 +37,7 @@ CUBRID 프로젝트에서는 사용자의 거침없는 버그 리포트와 솔
 라이선스
 --------
 
-CUBRID의 서버 엔진에는 Apache 라이선스 2.0 이 적용되고 CUBRID 매니저 및 인터페이스(API)에는 BSD 라이선스가 적용된다. 보다 상세한 정보는 CUBRID 공식 사이트의 라이선스 가이드(https://www.cubrid.org/cubrid) 를 참고한다.
+CUBRID의 서버 엔진에는 Apache 라이선스 2.0 이 적용되고 CUBRID 매니저 및 인터페이스(API)에는 BSD 라이선스가 적용된다. 보다 상세한 정보는 CUBRID 공식 사이트의 라이선스 가이드(https://www.cubrid.org/license) 를 참고한다.
 
 추가 정보
 ---------