Skip to main content

Search

Welcome to Tibero GTS!

Precautions When Setting LSNR_INVITED_IP and LSNR_INVITED_IP_FILE

Document Type | Troubleshooting

Category | Administration

Applicable Product Versions | 6FS06, 6FS07, 7FS02

Document Number | TADTS029

 

Issue

Note

This phenomenon occurred in Tibero6 FS06 version.

 

While using the LSNR_INVITED_IP_FILE option in the Tibero configuration file (TIP file), the user mistakenly specified the delimiter (comma ,) when creating the IP list file (invited_ip.lst) and applied the setting dynamically.
As a result, multiple IPs were recognized as a single incorrect IP, causing the tblistener process to terminate abnormally.
 
sys.log
[07-25T17:22:34.650142] [CT-01] [I] network_recv_fd: Connection from the listener was closed.
[07-25T17:22:34.653221] [FRM-00] [I] LISTENER EXITED ABNORMALLY!
[07-25T17:22:34.753766] [FRM-00] [I] LISTENER (196368) EXITED ABNORMALLY! RECREATE LISTENER!
[07-25T17:22:34.753947] [FRM-00] [I] PROCESS (PID 196368) is terminated by signal. (signal number=11)
...

 

Cause

If an unspecified delimiter is used, multiple IP entries may be incorrectly recognized as a single IP.
If this single IP string exceeds 128 bytes, the system cannot process it properly, causing the tblistener process to terminate abnormally.
 
 

Solutions

Rewrite the IP list using the correct delimiter (;) and then dynamically apply the LSNR_INVITED_IP_FILE setting using the following query to resolve the issue.
SQL> alter system listener parameter reload;

Note

If patch 308360 is applied, when the IP string is excessively long, the tblistener process may terminate or display the message "LSNR_INVITED_IP_FILE is invalid" without applying the setting.
Caution
Apply the patch through technical support provided by Tmax Tibero.

 

 

 

Related to