Problems with multiple calling lists: OCM 7.2

[Fra]

oh yeah yeah, just meant to say "take the decision of having 2 database tables instead of one"

[RC]

cavagnaro: sounds like we may not have configured out table(s) correctly; you are running 11 lists within one campaign; so does that mean you have 11 different tables in your database that each of these lists uses? and do you run these lists concurrently? We run up to 10 lists concurrently, but they are all referencing the same table, but each list is unique records; our dba tells us that we are causing database deadlocks since each list's stored procedure is searching the same table for records and is bumping into other concurrent processes; so is the solution as simple as multiple tables and duplicating the data, but being very careful not have the same record in more than one lists

[cavagnaro]

Logic procedure is:

TableAccess1 in DB1 with table name ListMarketing1
TableAccess2 in DB1 with table name ListMarketing2
.
.
.
.
TableAccess11 in DB1 with table name ListMarketing11

Then you will have:
CallingList 1 pointing to TableAccess1
CallingList 2 pointing to TableAccess2
CallingList 3 pointing to TableAccess3
.
.
.
CallingList 11 pointing to TableAccess11

So having all table accesses point to just 1 table or all calling lists point to one unique table access is insane and is really amazing that Genesys didn't make an observation on this.

I do have the 11 calling lists running on one single campaign at the same time.

Now why to have several calling lists with same data?
Unless you have one campaign for collects and other for sales with same targets will be useless.

[cavagnaro]

[quote author=Fra link=topic=3839.msg16710#msg16710 date=1234519842]
[quote author=cavagnaro link=topic=3839.msg16698#msg16698 date=1234486274]
[quote author=RC link=topic=3839.msg16694#msg16694 date=1234474003]
Each list accesses the same database table, but each list contains unique records. 
[/quote]

How is that possible? Each calling list should have its own Table access where you define the DBServer used and the table name. So if 3 calling lists share same table in DB means you only have 1 table access? What is the idea of this configuration?
[/quote]
Well, I would never do that, but Genesys states you can, from the Outbound Contact Deployment Guide:
[i]
"Each table in the database requires a separate Table Access Point object.
The Table Access Point object is a property of the Calling List
object in Configuration Manager. One or more calling list objects can share the
same Table Access Point object.".
[/i]
Dangerous cause you have got to have dialing filters which split the DB table in subsets that are supposed to have different unique records.
RC, your issue is not about having multiple calling lists, rather the fact you have many calling lists using the same database table. Instead, have the dba create two DB tables, then create two Table Access Points associated with two calling lists. Add them to your campaign and let us know if you still face any deadlock.
Without logs is anyway really hard troubleshooting.

Fra
[/quote]

Funny, can't think of a valid reason to do this...one customer contacted by one agent of another campaign and wam! you are done.

[Fra]

I do agree with you, Cav, and as I said I woulnd't ever do it, but technically you are allowed to.

Fra