Maximo Performance on SQL Server - Turning off Page Locking

Technote (troubleshooting)


Problem(Abstract)

Slow transactions or apparent hanging during multi-user operations in Maximo applications with a SQL Server 2000, 2005, or 2008 database can result if page locking has not been turned off on the tables and indexes.

Cause

A newly installed or upgraded Maximo 6 or higher system on SQL Server does not have page locking turned off on any tables unless the table has been modified by the Configure utility. Page locking can cause performance problems.

Resolving the problem

Connect to the Maximo database using Query Analyzer. Set the Query output to go to a file, then execute the following statement. This command must be broken onto two lines exactly as shown.

select 'sp_indexoption '''+tablename+''',''AllowPageLocks'',''false''
go' from maxtable order by tablename

Set the Query output back to screen.
Click on File - Open and read in the file you just created.
Delete the header and row count lines at the top and bottom of the set of commands.
Click Edit - Select All, then F5 to execute all of the sp_indexoption commands.

This will set page locking off for all tables and their indexes. Once turned off, it will remain off. The Maximo Database Configuration application will maintain page locking off if it rebuilds a table or index.


Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management Tivoli Asset Management for IT All
Systems and Asset Management IBM Maximo Asset Management Essentials All

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Maximo Asset Management

Software version:

6.0, 6.1, 6.2, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 7.1, 7.1.1, 7.5

Operating system(s):

Windows

Software edition:

All Editions

Reference #:

1268567

Modified date:

2007-10-01

Translate my page

Machine Translation

Content navigation