DataSourcer HA Configuration

I’m having a problem getting DataSourcer to work in hot-standby…

I have T-Server 7.6 running in hot standby and I’ve configured the DataSourcers (7.2.100.18) and StatServers (7.5.000.25) as per the documentation:

DS1:
Backup Server: DS2
Redundancy Type: Hot Standby
Connections to SS1 and SS2

DS2:
Backup Server: none
Redundancy Type: Hot Standby
Connections to SS1 and SS2

SS1:
Backup Server: SS2
Redundancy Type: Warm Standby
accept-client-in-backup = yes

SS2:
Backup Server: none
Redundancy Type: Warm Standby
accept-client-in-backup = yes

When I try to start DS1/DS2 and they initialize, wait for a couple of minutes and then stop.

I can’t see anything userfull in the logs either (all level logging):

Application name: DS1
Application type: DataSourcer (38)
Command line: data_sourcer.exe -service CCADataSourcer_1 -app DS1 -host 01 -port 2020 -sstart
Host name: 01
DST: TZ = 1, timeb = 1
Time zone: 0, GMT Standard Time, GMT Daylight Time
UTC time: 2009-04-28T06:32:50.854
Local time: 2009-04-28T07:32:50.854
Start time (UTC): 2009-04-28T06:32:50
Running time: 0:00:00:00
Host info: Windows 5.2.3790, 2, Service Pack 2, 2.0, 0110, 3
File: (1) D:\DataSourcer\DS_01.20090428_073250_854.log

07:32:50.838 Std 04106 Log Messages file ‘DataSourcer.lms’ successfully loaded
07:32:54.135 Std 04503 Connected to StatServer-02:6020[2668] ‘SS2’ at host ‘02’, port 6020
07:32:54.150 Std 04503 Connected to StatServer-01:6020[2352] ‘SS1’ at host ‘01’, port 6020
07:32:54.900 Std 04503 Connected to DAP ODSDAP [2692] at DBServer ‘ODSDBS1’ at host ‘01’, port 6040
07:32:56.259 Std 04503 Connected to DAP ODSDAP [2960] at DBServer ‘ODSDBS1’ at host ‘01’, port 6040
07:32:56.384 Std 04503 Connected to DAP ODSDAP [3288] at DBServer ‘ODSDBS1’ at host ‘01’, port 6040

Application name: DS2
Application type: DataSourcer (38)
Command line: data_sourcer.exe -service CCADataSourcer_1 -app DS2 -host 01 -port 2020 -sstart
Host name: 02
DST: TZ = 1, timeb = 1
Time zone: 0, GMT Standard Time, GMT Daylight Time
UTC time: 2009-04-28T06:33:26.284
Local time: 2009-04-28T07:33:26.284
Start time (UTC): 2009-04-28T06:33:26
Running time: 0:00:00:00
Host info: Windows 5.2.3790, 2, Service Pack 2, 2.0, 0110, 3
File: (1) D:\DataSourcer\DS_02.20090428_073326_285.log

07:33:26.284 Std 04106 Log Messages file ‘DataSourcer.lms’ successfully loaded
07:33:29.628 Std 04503 Connected to StatServer-gs2fwrep02:6020[2672] ‘SS2’ at host ‘02’, port 6020
07:33:29.628 Std 04503 Connected to StatServer-gs2fwrep01:6020[2092] ‘SS1’ at host ‘01’, port 6020
07:33:29.769 Std 04503 Connected to DAP ODSDAP [2692] at DBServer ‘ODSDBS1’ at host ‘01’, port 6040
07:33:29.941 Std 04503 Connected to DAP ODSDAP [2960] at DBServer ‘ODSDBS1’ at host ‘01’, port 6040
07:33:29.956 Std 30001 Too much data was written to the database within the specified threshold.
07:33:30.769 Std 04503 Connected to DAP ODSDAP [3060] at DBServer ‘ODSDBS1’ at host ‘01’, port 6040

Have I missed something here?

Cheers

Hi Ben,

Couple question here for you.

How do you know that they are not running in Hot standby already?
Is your loging option verbose set to all?
Do you have any Report layouts configured in DMA and activated?
How did you configure the ODS? Do you have one for both DS or two?
Did you set Stat Server option on all SS accept-clients-in-backup-mode?

Cheers,
e.

Hi ecki

DS is currently configured as Warm Standby (but obviously this doesn’t work and isn’t supported). However both backup and primary DS will start and run happily when configured like this.

Verbose is set to standard (I thought it was all, but it isn’t… Will change this over)

Yes, report layouts are configured and activated. Reporting works fine if I don’t change redundancy type to Hot Standby…

One ODS for both DS

SS option accept-clients-in-backup-mode = yes

What will happen when you just run one DS at a time? Did you test it?

Edited above regarding log settings…

If I try and start one on its own and it does the same thing - initializes for a few minutes then stops.

And still nothing useful in the logs?

Ben,

Please set logging level to “debug” or “all”, start both DS and post logs here.

R.

Will obtain logs and post them as soon as I can…

Thanks for the help so far

New log…

Application name: DS01
Application type: DataSourcer (38)
Command line: data_sourcer.exe -service CCADataSourcer_1 -app DS01 -host 01 -port 2020 -sstart
Host name: 01
DST: TZ = 1, timeb = 1
Time zone: 0, GMT Standard Time, GMT Daylight Time
UTC time: 2009-05-06T06:04:32.538
Local time: 2009-05-06T07:04:32.538
Start time (UTC): 2009-05-06T06:04:32
Running time: 0:00:00:00
Host info: Windows 5.2.3790, 2, Service Pack 2, 2.0, 0110, 3
File: (1) D:\GCTI\DS01.20090506_070432_539.log

07:04:32.538 Trc 04112 The Log Output of type ‘D:\GCTI\DS01’ has been created and opened
07:04:32.538 Trc 04110 Option ‘buffering’ has been set to the value ‘no’
07:04:32.538 Trc 04110 Option ‘spool’ has been set to the value ‘’
07:04:32.538 Trc 04110 Option ‘keep-startup-file’ has been set to the value ‘no’
07:04:32.538 Trc 04110 Option ‘MessageFile’ has been set to the value ‘DataSourcer.lms’
07:04:32.538 Trc 04110 Option ‘time-format’ has been set to the value ‘time’
07:04:32.538 Trc 04110 Option ‘time-convert’ has been set to the value ‘local’
07:04:32.538 Trc 04110 Option ‘message-format’ has been set to the value ‘short’
07:04:32.538 Trc 04110 Option ‘memory-storage-size’ has been set to the value ‘2 Mb’
07:04:32.538 Trc 04110 Option ‘compatible-output-priority’ has been set to the value ‘no’
07:04:32.538 Trc 04110 Option ‘print-attributes’ has been set to the value ‘no’
07:04:32.538 Trc 04110 Option ‘check-point’ has been set to the value ‘1’
07:04:32.538 Std 04106 Log Messages file ‘DataSourcer.lms’ successfully loaded
07:04:32.538 Trc 04112 The Log Output of type ‘D:\GCTI\DS01’ has been created and opened
07:04:32.538 Trc 04100 Logging service started
2009-05-06 07:04:32.538 LCALayer: Register LCA client
Open LCALayer on port=4999
LCA Library version 7.5.000.05
2009-05-06 07:04:32.554 DataSourcer, Version: 7.2.100.18 Compiled: Jul 21 2008 10:53:00
2009-05-06 07:04:32.554 Genesys Telecommunications Laboratories, Inc. (c) 2003-2008
2009-05-06 07:04:32.554 Reading configuration options for ‘DS01’…
2009-05-06 07:04:32.554 Options Section collector
07:04:32.554 Trc 06084 Configuration option set: ‘collector’:‘create-sample-templates’ = ‘FALSE’
07:04:32.554 Trc 06084 Configuration option set: ‘collector’:‘emergency-save-directory’ = ‘C:\GCTI\DataSourcer\EmergencySave\DS01’
07:04:32.554 Trc 06084 Configuration option set: ‘collector’:‘data-table-size’ = ‘1000000’
07:04:32.554 Trc 06084 Configuration option set: ‘collector’:‘activate-new-layouts’ = ‘FALSE’
2009-05-06 07:04:32.554 Options Section log
2009-05-06 07:04:32.554 Loading connected tenants.

LCALayer: REventRegistered on LCA…

2009-05-06 07:04:32.554 Collector’s tenant ‘Resources’ (101)
2009-05-06 07:04:32.569 Collector’s tenant ‘Environment’ (1), single-tenant mode.
2009-05-06 07:04:32.569 Loading switches.
2009-05-06 07:04:32.600 Loaded 3 switches.
2009-05-06 07:04:32.600 Loading connected servers.
2009-05-06 07:04:32.600 Server LOGMSG_01 DBID(169) protocol addp timeout local/remote 10/15 mode 1
2009-05-06 07:04:32.647 Server SS1 DBID(201) protocol addp timeout local/remote 10/15 mode 1
2009-05-06 07:04:32.679 Server ODSDAP DBID(205) protocol timeout local/remote 30/30 mode 1
2009-05-06 07:04:32.741 Server SS2 DBID(202) protocol addp timeout local/remote 10/15 mode 0
2009-05-06 07:04:32.741 Initialize StatCluster…
2009-05-06 07:04:32.741 Started thread ‘StatCluster’ id 1812
2009-05-06 07:04:32.741 Setting ODS update mode…
2009-05-06 07:04:32.741 Setting ODS update mode…
2009-05-06 07:04:32.788 Waiting for 3 seconds before checking StatCluster configuration…
2009-05-06 07:04:35.788 Checking StatCluster configuration…
2009-05-06 07:04:35.788 StatCluster connection SS1 DBID(201) protocol addp timeout local/remote 10/15 mode 1
2009-05-06 07:04:35.788 StatServer-01:6020[-1] Processing server configuration…
2009-05-06 07:04:35.788 StatServer-01:6020[-1] List of connected tenants:
2009-05-06 07:04:35.788 StatServer-01:6020[-1] … Tenant ‘Resources’ (DBID 101)
2009-05-06 07:04:35.788 StatServer-01:6020[-1] Processing options…
2009-05-06 07:04:35.803 StatServer-01:6020[-1] Server configuration processed.
2009-05-06 07:04:35.819 StatCluster connection SS2 DBID(202) protocol addp timeout local/remote 10/15 mode 1 backup
2009-05-06 07:04:35.819 StatServer-02:6020[-1] Processing server configuration…
2009-05-06 07:04:35.819 StatServer-02:6020[-1] List of connected tenants:
2009-05-06 07:04:35.819 StatServer-g02:6020[-1] … Tenant ‘Resources’ (DBID 101)
2009-05-06 07:04:35.819 StatServer-02:6020[-1] Processing options…
2009-05-06 07:04:35.834 StatServer-02:6020[-1] Server configuration processed.
2009-05-06 07:04:35.834 Collector initialization exception, Wrong configuration, more than one StatServer!
2009-05-06 07:04:35.834 Collector started initialization (attempt 2)…
2009-05-06 07:04:35.850 LCALayer: Register LCA client
2009-05-06 07:04:35.850 DataSourcer, Version: 7.2.100.18 Compiled: Jul 21 2008 10:53:00
2009-05-06 07:04:35.850 Genesys Telecommunications Laboratories, Inc. (c) 2003-2008
2009-05-06 07:04:35.850 Reading configuration options for ‘DS01’…
2009-05-06 07:04:35.850 Options Section collector
07:04:35.850 Trc 06084 Configuration option set: ‘collector’:‘create-sample-templates’ = ‘FALSE’
07:04:35.850 Trc 06084 Configuration option set: ‘collector’:‘emergency-save-directory’ = ‘C:\GCTI\DataSourcer\EmergencySave\DS01’
07:04:35.850 Trc 06084 Configuration option set: ‘collector’:‘data-table-size’ = ‘1000000’
07:04:35.850 Trc 06084 Configuration option set: ‘collector’:‘activate-new-layouts’ = ‘FALSE’
2009-05-06 07:04:35.850 Options Section log
2009-05-06 07:04:35.850 Loading connected tenants.
2009-05-06 07:04:35.850 Loading switches.
2009-05-06 07:04:35.866 Loaded 3 switches.
2009-05-06 07:04:35.866 Loading connected servers.
2009-05-06 07:04:35.866 Server LOG01 DBID(169) protocol addp timeout local/remote 10/15 mode 1
2009-05-06 07:04:35.881 Server SS1 DBID(201) protocol addp timeout local/remote 10/15 mode 1
2009-05-06 07:04:35.881 Server ODSDAP DBID(205) protocol timeout local/remote 30/30 mode 1
2009-05-06 07:04:35.881 Server SS2 DBID(202) protocol addp timeout local/remote 10/15 mode 0
2009-05-06 07:04:35.881 Setting ODS update mode…
2009-05-06 07:04:35.881 Setting ODS update mode…
2009-05-06 07:04:35.881 Configuration Error, more than one DB Access Point specified.
2009-05-06 07:04:35.881 Collector initialization exception, Configuration Error
2009-05-06 07:04:35.881 Collector started initialization (attempt 3)…

More than one StatServer error - I thought this was supported configuration??

More than one DAP - ???

Change it back to Warm Standby and remove the connection to the backup StatServer and it starts fine - OL_DB_PROPERTIES looks correct too:

2009-05-06 07:06:48.164 Setting ODS update mode…
2009-05-06 07:06:48.226 Waiting for 3 seconds before checking StatCluster configuration…
2009-05-06 07:06:51.226 Checking StatCluster configuration…
2009-05-06 07:06:51.226 StatCluster connection SS01 DBID(201) protocol addp timeout local/remote 10/15 mode 1
2009-05-06 07:06:51.226 StatServer-01:6020[-1] Processing server configuration…
2009-05-06 07:06:51.226 StatServer-01:6020[-1] List of connected tenants:
2009-05-06 07:06:51.226 StatServer-01:6020[-1] … Tenant ‘Resources’ (DBID 101)
2009-05-06 07:06:51.226 StatServer-01:6020[-1] Processing options…
2009-05-06 07:06:51.242 StatServer-01:6020[-1] Server configuration processed.
2009-05-06 07:06:51.288 StatCluster connection SS02 DBID(202) protocol addp timeout local/remote 10/15 mode 1 backup
2009-05-06 07:06:51.288 StatServer-02:6020[-1] Processing server configuration…
2009-05-06 07:06:51.288 StatServer-02:6020[-1] List of connected tenants:
2009-05-06 07:06:51.288 StatServer-02:6020[-1] … Tenant ‘Resources’ (DBID 101)
2009-05-06 07:06:51.288 StatServer-02:6020[-1] Processing options…
2009-05-06 07:06:51.304 StatServer-02:6020[-1] Server configuration processed.
2009-05-06 07:06:51.304 Started thread ‘StatMsgThread’ id 2068
2009-05-06 07:06:51.304 StatMsgThread(StatServer-01:6020[-1]): thread started.
2009-05-06 07:06:51.304 Started thread ‘StatServer’ id 2088
2009-05-06 07:06:51.304 StatServer-01:6020[-1] addp ON, addp-timeout=10 addp-remote-timeout=15 addp-trace=no
conn: send-timeout set to 1799
2009-05-06 07:06:51.304 StatServer-01:6020[2092] connecting…
2009-05-06 07:06:51.304 StatServer-01:6020[-1] Server is not available. Waiting for connection…
2009-05-06 07:06:51.304 Started thread ‘StatMsgThread’ id 2336
2009-05-06 07:06:51.304 StatMsgThread(StatServer-02:6020[-1]): thread started.
2009-05-06 07:06:51.304 Started thread ‘StatServer’ id 2368
2009-05-06 07:06:51.304 StatServer-02:6020[-1] Server is not available. Waiting for connection…
2009-05-06 07:06:51.320 StatServer-02:6020[-1] addp ON, addp-timeout=10 addp-remote-timeout=15 addp-trace=no
conn: send-timeout set to 1799
2009-05-06 07:06:51.320 StatServer-02:6020[2676] connecting…
07:06:51.320 Std 04503 Connected to StatServer-01:6020[2092] ‘SS01’ at host ‘01’, port 6020
2009-05-06 07:06:51.320 StatServer-01:6020[2092] RunInfo 1 (primary)
07:06:51.320 Std 04503 Connected to StatServer-02:6020[2676] ‘SS02’ at host ‘02’, port 6020
2009-05-06 07:06:51.320 StatServer-02:6020[2676] RunInfo 0 (backup)
2009-05-06 07:06:51.351 Connecting to DBServer (-1)[-1] host 01:6040
07:06:51.507 Std 04503 Connected to DAP ODSDAP [2696] at DBServer ‘ODSDBS01’ at host ‘01’, port 6040
2009-05-06 07:06:51.507 Checking ODS tables…
2009-05-06 07:06:51.523 Number of DB tables is 79
…
2009-05-06 07:06:51.538 Reading OL_DB_PROPERTIES…
2009-05-06 07:06:51.882 DBProperties :
2009-05-06 07:06:51.882 version=7.2.009
2009-05-06 07:06:51.882 ConfigServer Host=01
2009-05-06 07:06:51.882 ConfigServer Port=2020
2009-05-06 07:06:51.882 InitTime=04/10/2007 13:33:36
2009-05-06 07:06:51.882 TimeZone=UTC
2009-05-06 07:06:51.882 DataSourcer DBID=200
2009-05-06 07:06:51.882 DataSourcer Backup DBID=222
2009-05-06 07:06:51.882 srcId=1
2009-05-06 07:06:51.882 brand=23FFB086
2009-05-06 07:06:51.882 Reading object types…
2009-05-06 07:06:51.882 Checking backup Data Sourcer DBID…
2009-05-06 07:06:51.882 Started thread ‘ODSLockMonitor’ id 2932
2009-05-06 07:06:51.882 ODSLockMonitor thread started
2009-05-06 07:06:51.882 ODSLockMonitor: Connecting to ODS…
2009-05-06 07:06:51.882 Connecting to DBServer (-1)[-1] host 01:6040
07:06:51.992 Std 04503 Connected to DAP ODSDAP [2964] at DBServer ‘ODSDBS01’ at host ‘01’, port 6040
2009-05-06 07:06:51.992 ODSLockMonitor: Connected to ODS.
2009-05-06 07:06:51.992 ODSLockMonitor: Trying to acquire ODS lock…
2009-05-06 07:06:52.023 ODSLockMonitor: ODS Lock acquired.
2009-05-06 07:06:52.023 LCALayer: Application set run mode [0] ‘Primary server mode’
2009-05-06 07:06:52.023 Started thread ‘DBWriter’ id 3224
2009-05-06 07:06:52.023 DBWriter: Setting ESF ‘C:\GCTI\DataSourcer\EmergencySave\DS01’…
2009-05-06 07:06:52.023 Started thread ‘DMAServer’ id 3240
2009-05-06 07:06:52.038 Loading statistical parameters of type ‘StatType’…
2009-05-06 07:06:52.038 DBWriter: Folder ‘C:\GCTI\DataSourcer\EmergencySave\DS01’ exists.
2009-05-06 07:06:52.038 DBWriter: Scanning ESF…
2009-05-06 07:06:52.038 DBWriter: ESF scan complete. Found 0 chunk files.
2009-05-06 07:06:52.038 Connecting to DBServer (-1)[-1] host 01:6040
07:06:52.132 Std 04503 Connected to DAP ODSDAP [2992] at DBServer ‘ODSDBS01’ at host ‘01’, port 6040
2009-05-06 07:06:52.132 DBWriter: ODS connection opened, queue size 0
2009-05-06 07:06:52.226 Checking statistical parameters of type ‘StatType’…

You have more than one statserver and DAP configured with one ods?

Using the same DAP, but I think it might be because of the StatServers…

What is wrong with the statserver?

Reading back through the documentation it appears you don’t actually need to have connections to both primary and backup statservers defined for each datasourcer (despite the fact that it implies you do).

Going to try that and see what happens…

Was just the StatServer Connections - working now.

Good to hear. Congratulations! Well done