Skip to main content

Search

Welcome to Tibero GTS!

Checklist when this issue, It's highly possible that the DB instance is in SESSION_FULL state, occurs

Document Type | Troubleshooting 

Category | Administration

Applicable Product Version | 6FS06

Document Number | TADTS035

 

Issue

When this issue,'It's highly possible that the DB instance is in SESSION_FULL state.', occurs, the application or server cannot connect to the DB. 
 
Excerpt from sys.log
[2025-03-20T12:10:36.981776] [SEQ-125] [I] Allocating new session for update user astatus failed. It's highly possible that the DB instance is in SESSION_FULL state. View for session and lock, and callstack dump will be helpful to investigate the problem.
[2025-03-20T12:10:40.987847] [SEQ-125] [I] Allocating new session for update session login/logout time failed. It's highly possible that the DB instance is in SESSION_FULL state. View for session and lock, and callstack dump will be helpful to investigate the problem.
..

 

Cause

It is presumed that one of the working processes terminated abnormally.
(In fact, the sessions were full, causing the SESSION_FULL state.)

 

Solutions

1. Verify Working Processes are Normal

It is necessary to check whether the working processes were running normally at that time. 
(MAX_SESSION_COUNT is set to 100, allowing 10 sessions per WP.)
 
WP046 PROCESS 48 (PID 14657) EXITED ABNORMALLY! 
(Can be confirmed from db logs or out files.)
ps -ef | grep tbsv_WP

ex) [tibero1]tibero@tibero1:/home/tibero>  ps -ef | grep tbsvr_WP
tibero    4092  4089  0 Mar19 ?        00:00:00 tbsvr_WP000    -t NORMAL -SVR_SID tibero1
tibero    4093  4089  0 Mar19 ?        00:00:00 tbsvr_WP001    -t NORMAL -SVR_SID tibero1
tibero    4094  4089  0 Mar19 ?        00:00:00 tbsvr_WP002    -t NORMAL -SVR_SID tibero1
tibero    4095  4089  0 Mar19 ?        00:00:00 tbsvr_WP003    -t NORMAL -SVR_SID tibero1
tibero    4096  4089  0 Mar19 ?        00:00:00 tbsvr_WP004    -t NORMAL -SVR_SID tibero1
tibero    4097  4089  0 Mar19 ?        00:00:00 tbsvr_WP005    -t NORMAL -SVR_SID tibero1
tibero    4098  4089  0 Mar19 ?        00:00:00 tbsvr_WP006    -t NORMAL -SVR_SID tibero1
tibero    4099  4089  0 Mar19 ?        00:00:00 tbsvr_WP007    -t NORMAL -SVR_SID tibero1
tibero    4100  4089  0 Mar19 ?        00:00:00 tbsvr_WP008    -t NORMAL -SVR_SID tibero1
tibero    4101  4089  3 Mar19 ?        01:00:32 tbsvr_WP009    -t NORMAL -SVR_SID tibero1

 

2. Check Session Count

Check the actual number of sessions connected at that time. 
select count(*) from v$session

 

3. Verify Number of Sessions

If a restart was urgently performed, you can check the number of sessions connected at that time through the _tpr_snapshot and _tpr_misc views. 
select m.snap_id, s.begin_interval_time, m.name, m.value1 
  from _tpr_misc m, _tpr_snapshot s
where m.snap_id = s.snap_id
    and m.thread# = s.thread#
    and m.value1 = (select max(value1) from _tpr_misc);
 
 
 

Related to