5.6Reorg and Runstats

Statistics on the number of rows in the tables and what indexes are available are required for IBM DB2 to efficiently fulfill queries. It is important to update these table and index statistics after large Directory Server Markup Language (DSML) loads, HR feeds, and reconciliations.

IBM Tivoli Identity manager ships with five JCL to execute reorg and runstats against the IBM DB2 databases.

In addition to running runstats on all tables within the database, we also manually update the statistics table for the ACTIVITY, PROCESS, PROCESSDATA, and SCHEDULED_MESSAGE tables to ensure a minimum cardinality. Setting a minimum cardinality on these tables helps the IBM DB2 query optimizer and can decrease locking issues in the database.

Determining the values

JCL location

Description

 

 

hlg.SAERSAMP(AERROITM)

REORG for ITIM database

 

 

hlg.SAERSAMP(AERROLDP)

REORG for LDAP database

 

 

hlg.SAERSAMP(AERROLDC)

REORG for LDAP changelog database

 

 

hlg.SAERSAMP(AERRSITM)

RUNSTATS for ITIM database

 

 

hlg.SAERSAMP(AERRSLDP)

RUNSTATS for LDAP database

 

 

The REORG scripts above will reorganize both table spaces and indexes, improving data access performance and reclaiming fragmented space. In addition, the REORG scripts will execute a RUNSTAT for each table space after the REORG.

Caution: The REORG scripts should only be executed when the table spaces are not in use by stopping the WebSphere Application Server and LDAP first. Failure to do this will result in the table spaces in an intermediate state and will require additional attention.

Use RUNSTATS scripts on idle or lightly-used databases because it requires update locking on the system statistics table to update the database statistics. A database with a heavy load might experience transaction roll backs due to the system acquiring locks on the tables that are used by the database optimizer to fulfill queries.

Note: The LDAP REORG and RUNSTATS JCL scripts rely on the DIR_DESCX2 index. See the Indexing section for more information.

Setting the values

1)Edit the JCL to conform to your installation’s standards.

2)Update DB2 schema names, such as the database name, to match your environment.

3)Submit the JCL for execution.

4)Confirm the job’s completion code for success.

After running RUNSTATS on the ITIM database, the following should be run against the ITIM database to update the statistics for the workflow tables. The following SQL statements require DB2 system administrator privileges to perform.

UPDATE SYSIBM.SYSTABLES SET CARD = 50000

WHERE CARD < 50000 AND CREATOR = 'ENROLE' AND NAME = 'ACTIVITY'; UPDATE SYSIBM.SYSTABLES SET CARD = 50000

WHERE CARD < 50000 AND CREATOR = 'ENROLE' AND NAME = 'PROCESS'; UPDATE SYSIBM.SYSTABLES SET CARD = 50000

WHERE CARD < 50000 AND CREATOR = 'ENROLE' AND NAME = 'PROCESSDATA'; UPDATE SYSIBM.SYSTABLES SET CARD = 50000

WHERE CARD < 50000 AND CREATOR = 'ENROLE' AND NAME = 'SCHEDULED_MESSAGE';

Page 14

IBM Tivoli Identity Manager Performance Tuning Guide

Page 15 Page 17
Page 16
Image 16
IBM 4.6 manual Reorg and Runstats
Page 15 Page 17

4.6 specifications

IBM 4.6, known for its robust and versatile capabilities, represents a significant evolution in the realm of enterprise software solutions. This version is primarily associated with IBM's middleware offerings, notably IBM WebSphere Application Server. It is engineered to support the development, deployment, and management of web applications with a focus on scalability, reliability, and security.

One of the standout features of IBM 4.6 is its enhanced performance optimizations. The platform employs advanced caching strategies and efficient resource management to improve application response times and throughput. This means that businesses can handle heavier loads with fewer resources, making it an economical choice for enterprises of all sizes.

Another notable characteristic is its support for a wide range of programming models and standards, including Java EE. This allows developers to build applications using familiar tools and frameworks, accelerating development timelines and improving productivity. Additionally, IBM 4.6 offers robust integration capabilities with existing enterprise systems through its support for web services and messaging protocols.

IBM 4.6 also emphasizes security. It includes features such as role-based access control, data encryption, and comprehensive auditing capabilities. These measures help organizations safeguard sensitive information and comply with various regulatory requirements.

The compatibility with multiple platforms, including cloud environments, is another significant advantage. IBM 4.6 simplifies deployment across diverse infrastructures, enabling businesses to operate in hybrid environments seamlessly. This flexibility is particularly beneficial as organizations increasingly adopt cloud migration strategies.

Furthermore, IBM 4.6 is equipped with a range of monitoring and management tools. These tools provide insights into application performance and health, allowing IT teams to proactively identify and address potential issues before they impact users. This capability is critical in maintaining high availability and reliability of services.

In summary, IBM 4.6 stands out as a comprehensive solution for enterprise application development and management. Its key features, such as enhanced performance, support for industry standards, strong security measures, platform compatibility, and monitoring tools, make it a compelling choice for organizations seeking to modernize their IT infrastructure. Implementing IBM 4.6 can empower businesses to innovate faster while ensuring their applications remain secure and efficient in a rapidly evolving digital landscape.
Top Page Image Contents