IBM Support

Collecting data for ITDS: Performance Issues

Technote (troubleshooting)


Problem(Abstract)

MustGather documents aid in problem determination and save time resolving Problem Management Records (PMRs). Specifically IBM Tivoli Directory Server problems related to performance with the LDAP server.

Resolving the problem


The majority of general performance problems in ITDS can be attributed to the following two causes:

1) lack of regular DB2 maintenance

2) inefficient ldapsearch operations querying the server repeatedly

Before opening a Service Request for performance issues, please see the following technote and make sure that DB2 maintenance has been performed recently:

http://www.ibm.com/support/docview.wss?uid=swg21263999


Must Gather information based on IBM Tivoli Directory Server version:





IBM Tivoli Directory Server 6.1 Must Gather Information

1. Check the last time runstats was run: Send output from the following SQL:

db2 "select card,stats_time from syscat.tables where tabname = 'LDAP_DESC'"

See the following technote for more details:

http://www.ibm.com/support/docview.wss?uid=swg21270455

2. Enable audit logging and let it run while the problem is occurring. Instructions for enabling audit logging can be found here:

http://www.ibm.com/support/docview.wss?uid=swg21405323

In 6.1 and later, there is also a new feature to enable performance audit logging. Just create an ldif file containing:

dn: cn=Audit,cn=Log Management,cn=Configuration
changetype: modify
replace: ibm-auditPerformance
ibm-auditPerformance: true

called perfaudit.ldif and run the following modify:

idsldapmodify -D <admin_dn> -w <password> -i perfaudit.ldif

in addition to the commands to enable regular audit logging above.

3. Collect the following files: ibmslapd.log, db2diag.log and ibmslapd.conf, as well as the newly generated audit.log and send them to Support. Directions for collecting these logs are here:

http://www.ibm.com/support/docview.wss?uid=swg21269702

4. DB2 database information: collect the database and database manager configuration information by following the directions in the following technote:

http://www.ibm.com/support/docview.wss?uid=swg21279126

5. Support provides scripts for monitoring resource usage on ITDS servers: Run the script provided for your platform, and provide the resulting output to Support:

Windows monitoring script:
http://www.ibm.com/support/docview.wss?uid=swg21282701

UNIX/Linux monitoring script:
http://www.ibm.com/support/docview.wss?uid=swg21282708

Return to top of page

[]IBM Tivoli Directory Server 6.0 Must Gather Information

1. Check the last time runstats was run: Send output from the following SQL:

db2 "select card,stats_time from syscat.tables where tabname = 'LDAP_DESC'"

See the following technote for more details:

http://www.ibm.com/support/docview.wss?uid=swg21270455

2. Enable audit logging and let it run while the problem is occurring. Instructions for enabling audit logging can be found here:

http://www.ibm.com/support/docview.wss?uid=swg21405323

3. Collect the following files: ibmslapd.log, db2diag.log and ibmslapd.conf, as well as the newly generated audit.log and send them to Support. Directions for collecting these logs are here:

http://www.ibm.com/support/docview.wss?uid=swg21269702

4. DB2 database information: collect the database and database manager configuration information by following the directions in the following technote:

http://www.ibm.com/support/docview.wss?uid=swg21279126

5. Support provides scripts for monitoring resource usage on ITDS servers: Run the script provided for your platform, and provide the resulting output to Support:

Windows monitoring script:
http://www.ibm.com/support/docview.wss?uid=swg21282701

UNIX/Linux monitoring script:
http://www.ibm.com/support/docview.wss?uid=swg21282708

Return to top of page

IBM Tivoli Directory Server 5.2 Must Gather Information

1. Check the last time runstats was run: Send output from the following SQL:

db2 "select card,stats_time from syscat.tables where tabname = 'LDAP_DESC'"

See the following technote for more details:

http://www.ibm.com/support/docview.wss?uid=swg21270455

2. Enable audit logging and let it run while the problem is occurring. Instructions for enabling audit logging can be found here: http://publib.boulder.ibm.com/tividd/td/IBMDS/IDSadmin52/en_US/HTML/admin_gd.htm#Header_335

3. Collect the following files: ibmslapd.log, db2diag.log, the newly generated audit.log and ibmslapd.conf and send them to Support. Directions for collecting these logs can be found here:

http://www.ibm.com/support/docview.wss?uid=swg21269702

4. DB2 database information: collect the database and database manager configuration information by following the directions in the following technote:

http://www.ibm.com/support/docview.wss?uid=swg21279126

5. Support provides scripts for monitoring resource usage on ITDS servers: Run the script provided for your platform, and provide the resulting output to Support:

Windows monitoring script:
http://www.ibm.com/support/docview.wss?uid=swg21282701

UNIX/Linux monitoring script:
http://www.ibm.com/support/docview.wss?uid=swg21282708

Return to top of page


Return to top of page

Related information

Exchange data with IBM by using ECuRep

Document information

More support for: IBM Security Directory Server
General

Software version: 5.2, 6.0, 6.1, 6.2, 6.3, 6.3.1, 6.4

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Reference #: 1270498

Modified date: 27 June 2016


Translate this page: