cancel
Showing results for 
Search instead for 
Did you mean: 

Monitoring Replication Server connections to IQ

Former Member
0 Kudos

Hi guys, I need to know how to monitoring the RS connections and to create an alert when the connections reach a specific percentage because the value has increased to 200, and the error still occurs:

2100646 - Error 16133 'Configuration of 100 connections has been exceeded, connection rejected' fro...

This output is not clear:

1> admin show_connections

2> go


connection state  number comments

----------------- ------ -------------------------------------------------

connecting        0      in the process of connecting to a server

active            8      established connections owned and used by threads

idle              7      established connections owned but not being used

being_faded_out   0      idle connections that are being closed

already_faded_out 10     idle connections that have been closed

free              2      established connections not owned by any threads

closed            117    closed connections not owned by any threads

limbo             0      connection handles in state transition

total             144    total number of connection handlers available


Thanks


Leandro

Accepted Solutions (0)

Answers (1)

Answers (1)

c_baker
Employee
Employee
0 Kudos

Can you provide the RCL for the connection to IQ?  What When you configure the connection, what profile or errorclass/functionclass are you using for the connection to IQ?

Are you using Multipath replication or RTL or microbatching?

There should be no issues with connecting to IQ and no reason to open up another connection unless the previous application of data has not properly completed (e.g. 'commit' not issued).  Are you building up versions in IQ?

IMHO the issue is not IQ as much as your replication configuration.  More detail is needed.

Chris

c_baker
Employee
Employee
0 Kudos

The only way IQ configuration would really be involved is if IQ is not able to keep up with the inbound records.  This may indicate that you are attempting to use row-by-row inserts instead of RTL (micro-batching) or the IQ RLV feature.

Chris

Former Member
0 Kudos

Well, we have the main and the alternate connection:

-------------------------------------------------

-- main connection to IQ

-------------------------------------------------

create connection to PRD_SYB_IQ.PRD_SYB_IQ

using profile rs_ase_to_iq;standard

set username to rep_maint

set password to XXXX

create function string class my_iq_fclass

set parent to rs_iq_function_class

go

create function string rs_session_setting

for my_iq_fclass

output language

'set temporary option Minimize_Storage=''on''

set temporary option join_preference=5'

go

alter connection to PRD_SYB_IQ.PRD_SYB_IQ

set function string class to my_iq_fclass

go

alter connection to PRD_SYB_IQ.PRD_SYB_IQ

set dsi_compile_enable to 'on'

go

-------------------------------------------------

-- Alternate connection to IQ

-------------------------------------------------

create alternate connection to PRD_SYB_IQ.PRD_SYB_IQ

named PRD_SYB_IQ.cobis

using profile rs_ase_to_iq;standard

set username to cobis

set password to XXXX

alter connection to PRD_SYB_IQ.cobis

set function string class to my_iq_fclass

go

alter connection to PRD_SYB_IQ.cobis

set dsi_compile_enable to 'on'

go

alter connection to PRD_SYB_IQ.cobis

set dsi_bulk_threshold to '15'

go

We are using RS RTL, and There is something that worries me, It will be normal to observe much these issues?:


I. 2016/07/19 10:53:35. A grouped transaction of 41 individual transactions has failed in database 'PRD-SYB-IQ.cobis'. It will be broken into smaller groups and retried.

E. 2016/07/19 10:53:35. ERROR #1028 DSI EXEC(1928(1) PRD-SYB-IQ.cobis) - dsiqmint.c(4609)

    Message from server: Message: -1003002, State 0, Severity 14 -- 'SQL Anywhere Error -1003002: CtLibrary Error: 6, Severity: 0, Origin: 3, Layer: 5

Error Message: ct_connect(): network packet layer: internal net library error: Net-Library operation terminated due to disconnec.

I. 2016/07/19 10:53:48. Retry of a grouped transaction of 15 individual transactions has succeeded in database 'PRD-SYB-IQ.cobis'.

I. 2016/07/19 10:54:00. Retry of a grouped transaction of 13 individual transactions has succeeded in database 'PRD-SYB-IQ.cobis'.

I. 2016/07/19 10:54:12. Retry of a grouped transaction of 13 individual transactions has succeeded in database 'PRD-SYB-IQ.cobis'.



Thanks Chris