Technote

(troubleshooting)

acpload utility takes a long time to load Access Control Policy to DB2 database

Problem(Abstract)

You experience a load time of over an hour for the acpload utility. Typically, it takes only a few minutes to load Access Control Policy data to a WebSphere Commerce DB2 database using the acpload utility.

Resolving the problem If a table has been updated or reorganized, run runstats on the this table before using the acpload utility. Without a change in the statistics, DB2 optimizer may choose an access plan that will cause the SQL statement to take a longer time to execute than required, and hence acpload takes a long time to load data.
For example, to improve the time to load the Access Control Policy:
DB tuning steps:
DB2 ACTIVATE DATABASE <DATABASE NAME>
DB2 ALTER BUFFERPOOL IBMDEFAULTBP SIZE 10000
DB2 ALTER TABLE ATTRVALUE VOLATILE
DB2 UPDATE DB CFG FOR <DATABASE NAME> USING LOCKLIST 2400
DB2 -TVF RUNSTATS.SQL

The attached SQL file is a sample file and contains the SchemaName hard coded as DB2INST3. Change the SchemaName accordingly before running runstats.sql

Related information

Maintaining a WebSphere Commerce DB2 database

Cross Reference information

Segment	Product	Component	Platform	Version	Edition
Commerce	WebSphere Commerce Business Edition	General	AIX, Linux, Solaris, Windows	5.6, 5.6.0.7, 5.6.1, 5.6.1.1, 5.6.1.2, 5.6.1.3

   

Document Information

Current web document: http://www.ibm.com/support/docview.wss?uid=swg21247789