Understanding wvdbt RCBs - Unicenter NSM Release 3.1 Latest Revision - September 10, 2006
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. Disclaimer - The topics in this presentation apply to Unicenter NSM release For information regarding MaxRCB in Unicenter NSM r11.1 review “WorldView Tunneling (WVDBT) Insights for Unicenter NSM r11.1”
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. Challenge - While connecting to SQL CORe via wvdbt (either from Unix platform or another Windows server) we are intermittently running out of Repository Context with WorldView return code Why?
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. MaxRcb - The default WorldView setting is limited to 64 RCB per machine. - If you have several remote DSMs connecting via wvdbt, then this value should be changed - Update / Add registry entry to increase maxRCB value - Maximum value that can be set 1024 (Unicenter NSM)
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. MaxRcb - Each remote DSM, aws_wvgate and wvplugin uses approximately 8 RCB connections / 8 = maximum 128 remote connections - Don’t forget that other applications, such as 2dmap, will also require RCBs (i.e., don’t limit yourself to 128)
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. MaxRcb - Add MaxRcb entry to following registry hive -
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. MaxRcb Type must be REG_DWORD and value should not exceed 1024 (Unicenter NSM). Prior releases may require additional maintenance to use maximum settings of 1024
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. wvRcbTest Tool to test WV RCB limits
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. Connecting to Local Core Ran out of Repository Context, confirming limit of 64
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. Connecting to Local Core 57 RCBs used by the test program
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. wvdbt 8 RCB with each wvdbt connection. In this case, there are 2 wvdbt connections from remote DSM
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. Checking WVAPI Connections - Use master - Select * from sysprocesses a - Where a.dbid in (select b.dbid from sysdatabases b where name = ‘TNGDB’)
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. Summary - MaxRcb limits may become an issue if several wvdbt connections are made to a single CORe. This is due to DSM (wvplugin) making multiple connections to CORe - Each wvdbt connection takes about 8 Kernal Contexts per remote DSM - MaxRcb settings can be changed by in the registry settings - This limits the number of remote DSMs connecting via wvdbt to about 120
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. Questions and Answers Any questions?