Document Type | Technical Information
Category | Administration
Applicable Product Version | 6FS07
Document Number | TADTI042
Overview
This introduces how to change the CM retry_cnt value.
Methods
1. Check the current setting (default value: 3).
[tibero1]tibero@localhost:/home/tibero> cmrctl show db --name tibero1 Instance Resource Info ====================================== Instance name : tibero1 Instance type : Database Instance Owner user id : 1000 Instance Owner group id : 1000 Env. file path : /home/tibero/.bash_profile Status : UP(NRML) Max retry count : 3 Failed retry count : 0 Retry interval : 1 sec Cluster : cls1 ======================================
2. Change using the cmrctl modify command.
[tibero1]tibero@localhost:/home/tibero> cmrctl modify db --name tibero1 --retry_cnt 1 MSG SENDING SUCCESS!
3. Verify the change.
[tibero1]tibero@localhost:/home/tibero> cmrctl show db --name tibero1 Instance Resource Info ====================================== Instance name : tibero1 Instance type : Database Instance Owner user id : 1000 Instance Owner group id : 1000 Env. file path : /home/tibero/.bash_profile Status : UP(NRML) Max retry count : 1 Failed retry count : 0 Retry interval : 1 sec Cluster : cls1 ======================================
4. Confirm application.
After shutting down the DB, it attempts to restart as many times as retry_cnt = 1 and fails to start, deactivate can be confirmed.
(trace_cm.log) 2025/04/03 10:12:03.344 [1] cm_actio:5665(04) [cls1] [CAUTION] Unexpected termination of service instance `tibero1`. conn status:13 2025/04/03 10:12:03.344 [1] cm_actio:5802(04) [cls1] Re-start resource 'tibero1' automatically 2025/04/03 10:12:03.344 [1] cm_actio:4704(04) [cls1] Start resource 'tibero1'... 2025/04/03 10:12:03.348 [1] cm_actio:4420(04) [cls1] EXECUTE CMD: dbctl_for_cm.sh boot 2025/04/03 10:12:03.615 [1] cm_actio:4439(04) [cls1] EXECUTE RESULT: 111 2025/04/03 10:12:03.616 [1] cm_actio:4100(00) cmd execution rc: 16777216 (100 < rc < 106) 2025/04/03 10:12:03.616 [1] cm_actio:4231(00) [ERROR] Cannot boot resource `tibero1` 2025/04/03 10:12:03.616 [1] cm_actio:4253(00) [ERROR] Too many successive failure of booting... deactivate the resource 'tibero1'