Can DB look up option set up using SQL cluster

venkatesh · ‎09-16-2013

Could you please confirm, if the DB look up feature in ICM can be set up using SQL cluster.

If, yes, could you please confirm, if this right configuration.

Registry : \\CORPVCLUCSQL899\MSSQLP899\ETN_ICMContactLookup=(ETNICMLookup,l000kOnly)

ICM configuration\Database look up explorer :

\\MSSQLP899\DEBN_3701

SQL Cluster server name : CORPVCLUCSQL899

Instance name : MSSQLP899

Table name :

DEBN_3701

david.macias · ‎09-16-2013

I've never done it, but can't really think of any reason why it wouldn't work. Are you getting an error? You understand that ICM's DB lookup is extremly basic and really doesn't work well with any kind of advanced queries.

david

Blog

venkatesh · ‎09-16-2013

I tried various combination of updating the path. But still getting same error. Please find below log of DB worker. Yes, we are aware that it supports only minimal feture.

17:15:55:093 ra-dbw Add of ScriptTable complete. externaldb (5000).

17:15:55:093 ra-dbw Trace: Invalid pathname for externaldb: \\CORPVCLUCSQL899\MSSQLP899\DEBN_3701

17:15:55:094 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))

17:15:55:094 ra-dbw Trace: Action=4 type=0 count=0

17:15:55:094 ra-dbw Trace: Action=1 type=127 count=1

17:15:55:094 ra-dbw Trace: Action=5 type=0 count=0

17:15:55:094 ra-dbw Trace: Transaction complete.

17:15:55:094 ra-dbw Add of ScriptTableColumn complete. ID 5000.

17:15:55:094 ra-dbw Trace: Invalid pathname for externaldb: \\CORPVCLUCSQL899\MSSQLP899\DEBN_3701

17:15:55:094 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.

17:18:24:502 ra-dbw Trace: Action=4 type=0 count=0

17:18:24:504 ra-dbw Trace: Action=3 type=126 count=1

17:18:24:505 ra-dbw Trace: Action=5 type=0 count=0

17:18:24:506 ra-dbw Trace: Transaction complete.

17:18:24:506 ra-dbw Update of ScriptTable complete. externaldb (5000).

17:18:24:506 ra-dbw Trace: Invalid pathname for externaldb: \\MSSQLP899\DEBN_3701

17:18:24:506 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))

17:18:24:506 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.

17:34:21:436 ra-dbw Trace: Action=4 type=0 count=0

17:34:21:437 ra-dbw Trace: Action=3 type=126 count=1

17:34:21:437 ra-dbw Trace: Action=5 type=0 count=0

17:34:21:437 ra-dbw Trace: Transaction complete.

17:34:21:437 ra-dbw Update of ScriptTable complete. externaldb (5000).

17:34:21:438 ra-dbw Trace: Invalid pathname for externaldb: \\151.110.200.190\MSSQLP899\DEBN_3701

17:34:21:438 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))

17:34:21:438 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.

17:36:40:954 ra-dbw Unable to parse SQL login info string.

17:38:18:725 ra-dbw Unable to parse SQL login info string.

17:45:54:366 ra-dbw SQL login info updated.

17:46:55:926 ra-dbw Trace: Action=4 type=0 count=0

17:46:55:926 ra-dbw Trace: Action=3 type=126 count=1

17:46:55:927 ra-dbw Trace: Action=5 type=0 count=0

17:46:55:927 ra-dbw Trace: Transaction complete.

17:46:55:927 ra-dbw Update of ScriptTable complete. externaldb (5000).

17:46:55:928 ra-dbw Trace: Invalid pathname for externaldb: \\151.110.200.190\ETN_ICMContactLookup

17:46:55:928 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))

17:46:55:928 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.

18:02:54:302 ra-dbw SQL login info updated.

18:51:57:417 ra-dbw Trace: Action=4 type=0 count=0

18:51:57:417 ra-dbw Trace: Action=3 type=126 count=1

18:51:57:418 ra-dbw Trace: Action=5 type=0 count=0

18:51:57:418 ra-dbw Trace: Transaction complete.

18:51:57:419 ra-dbw Update of ScriptTable complete. externaldb (5000).

18:51:57:419 ra-dbw Trace: Invalid pathname for externaldb: \\ETN_ICMContactLookup\DEBN_3701

18:51:57:419 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))

18:51:57:420 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.

18:59:46:937 ra-dbw Trace: Action=4 type=0 count=0

18:59:46:937 ra-dbw Trace: Action=3 type=126 count=1

18:59:46:937 ra-dbw Trace: Action=5 type=0 count=0

18:59:46:938 ra-dbw Trace: Transaction complete.

18:59:46:938 ra-dbw Update of ScriptTable complete. externaldb (5000).

18:59:46:939 ra-dbw Trace: Invalid pathname for externaldb: \\ICMLOOKUP\ETN_ICMContactLookup\DEBN_3701

18:59:46:939 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))

18:59:46:939 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.

19:00:28:945 ra-dbw Trace: Action=4 type=0 count=0

19:00:28:945 ra-dbw Trace: Action=3 type=126 count=1

19:00:28:945 ra-dbw Trace: Action=5 type=0 count=0

19:00:28:946 ra-dbw Trace: Transaction complete.

19:00:28:946 ra-dbw Update of ScriptTable complete. externaldb (5000).

19:00:28:946 ra-dbw Trace: Invalid pathname for externaldb: \\ICMLOOKUP\ETN_ICMContactLookup

19:00:28:946 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))

19:00:28:947 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.

david.macias · ‎09-18-2013

What version of ICM and what version of SQL?

david

Blog

venkatesh · ‎09-18-2013

Identified that SQL cluster can be integrated but only with default instance. Named instance is not supported.

jpsweeney77 · ‎09-18-2013

Is this official? From whom? Seems like I recall someone getting this working with an Alias.

venkatesh · ‎09-18-2013

Tried with Alias name as well. But it was not working. I got it confirmed with TAC.