Posted: Fri May 06, 2005 7:35 am Post subject: Pub/Sub and "Maximum LOB Locators" errors
Novice
Joined: 13 Feb 2003 Posts: 15
Both databases of the broker and configuration manager have tables to store pub/sub things, all tables have LOB columns (the Topic, for example). I am getting a "Maximum LOB Locators" error. This causes execution groups and/or the configuration manager to crash and not start up until those tables are cleared.
I have found that using a LobCacheSize parameter in db2cli.ini with great enough value we can avoid using LOB locators. The parameter seems to be the solution of the problem for the broker, but now the configuration manager refuses to deploy anything when this parameter is set.
Is there a suggested solution for the "maximum LOB Locators" problem using massive pub/sub in a broker? Is using LobCacheSize a good one? Why can't the configuration manager can deal with this parameter (and only in deploy operations)?
Joined: 27 Jan 2005 Posts: 397 Location: Philadelphia, PA
I dont think u explained ur problem very well. Can u describe the sequence of events that causes the problem. For example I dont understand what u mean when u say massive pub sub. Does that mean you have large topic namespace, lots of subscribers?? Waht does this have to do with deploy? _________________ Mikhail Malamud
http://www.netflexity.com http://groups.google.com/group/qflex
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum