IBM Support

Very slow performance launching Controller client, caused by using Read Only domain controller

Troubleshooting


Problem

User launches Controller client. User progresses through the steps (for example choosing database, logging onto Controller). It takes a long time for these steps to complete (before the Controller client has finally launched). The slow logons occur particularly for remote users. If a local user (located in the same location as the servers) tries to use Controller, then the client loads relatiely quickly.

Symptom

In one real-life example, the following timings were seen:


Remote PC
Local PC
Typical (other) system
Click launch Controller
00:00
00:00
00:00
"Select Database" appears
00:53
00:02

Progress bar advances 1
01:40
00:09

Progress bar advances 2
01:50
00:11

Select Actuality appears
02:27
00:18

Progress bar advances 3 (i.e. At 100%)
02:49
00:24

Screen goes black (splash disappears)
03:29
00:33

Client appears
03:38
00:34
00:14

To summarise:
  • Remote users took well over 3 minutes to launch Controller
  • Local users took just over 30 seconds to launch Controller
  • However, when comparing with a different system (a standard remote system) it took only 14 seconds to logon (despite the client and servers being located in different/separate countries).

Cause

There are many possible causes for slow client logon times.

  • TIP: For more examples, see separate IBM Technote #1367308.

This Technote specifically relates to the scenario where the cause is that the customer's application servers are using a 'read only' active directory domain controller (RODC).

Environment

Both of the following are true:

  • Controller configured to use CAM (non-native) security
  • Controller application server configured to use a read only AD domain controller (RODC).

Resolving The Problem

Modify the domain controller (which is being used by the Controller application server) to be a standard read-write (RWDC) domain controller.

Example:
In one real-life customer example, they:

  • created a new 'full' domain controller
  • demoted the old read only domain controller (RODC)
  • Reconfigured Cognos Configuration namespace to point to this new 'full' domain controller instead.
After doing the above, the login time reduced to 14 seconds (from start to finish).

[{"Product":{"code":"SS9S6B","label":"IBM Cognos Controller"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Controller","Platform":[{"code":"PF033","label":"Windows"}],"Version":"10.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 June 2018

UID

swg21696789