문서유형ㅣ기술정보
분야ㅣ관리/환경설정
적용제품버전ㅣ6FS07
문서번호ㅣTADTI042
개요
CM retry_cnt 값 변경하는 방법을 소개합니다.
방법
1. 기존 설정 확인 (기본값 : 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. cmrctl modify 명령어로 변경
[tibero1]tibero@localhost:/home/tibero> cmrctl modify db --name tibero1 --retry_cnt 1 MSG SENDING SUCCESS!
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 : 1 Failed retry count : 0 Retry interval : 1 sec Cluster : cls1 ======================================
4. 적용 여부 확인
DB 종료 후, retry_cnt = 1 만큼 Restart 시도 후 기동 실패하여 deactivate 된 것을 확인할 수 있습니다.
(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'