1 / 14

Understanding wvdbt RCBs

This guide addresses issues related to the MaxRcb settings in Unicenter NSM release 3.1, specifically when connecting to SQL CORe via WorldView Tunneling (WVDBT). Users may encounter "Repository Context" errors due to limitations on RCB connections. It explains how to increase the MaxRcb value in the registry to support more remote DSM connections, detailing the steps to modify settings and avoid running out of context. Important considerations include the default 64 RCB limitation and how many RCBs each connection utilizes.

margot
Télécharger la présentation

Understanding wvdbt RCBs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Understanding wvdbt RCBs Unicenter NSM Release 3.1 Latest Revision - September 10, 2006

  2. Disclaimer • The topics in this presentation apply to Unicenter NSM release 3.1. • For information regarding MaxRCB in Unicenter NSM r11.1 review “WorldView Tunneling (WVDBT) Insights for Unicenter NSM r11.1”

  3. 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 27. • Why?

  4. 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)

  5. MaxRcb • Each remote DSM, aws_wvgate and wvplugin uses approximately 8 RCB connections. • 1024 / 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)

  6. MaxRcb • Add MaxRcb entry to following registry hive

  7. 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

  8. wvRcbTest Tool to test WV RCB limits

  9. Connecting to Local Core Ran out of Repository Context, confirming limit of 64

  10. Connecting to Local Core 57 RCBs used by the test program

  11. wvdbt 8 RCB with each wvdbt connection. In this case, there are 2 wvdbt connections from remote DSM

  12. Checking WVAPI Connections • Use master • Select * from sysprocesses a • Where a.dbid in (select b.dbid from sysdatabases b where name = ‘TNGDB’)

  13. 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

  14. Questions and Answers Any questions?

More Related