Re: sysptprof

Hello Dirk > I looked at sysptprof, but find that there can be more than one > entry for a specific table. Is this because of fragmentation ? Yes. Since your table is fragmented, it has different TBLSpaces in different dbspaces, hence it has multiple entries in sysptprof. You may also notice indexes if they are detatched (explicitly created with the IN dbs? in CREATE INDEX). If your index names are the same as the table names (which was true in our case) this can create additional entries with the same name. > And then the isreads and iswrites, are these record reads and writes These are indexed reads and indexed writes. I think "is" stands for "Index Sequential". I have used this to monitor a client's production system to get an idea of the disk reads and writes across dbspaces (and disks) so I could suggest a physical database layout strategy to smooth out the accesses across disks. I used the following SQL: database sysmaster; select tabname, (isreads+iswrites+isdeletes+isrewrites+seqscans) activity from sysptprof where dbsname = <database_name>; Then I sorted the output on the activity column and used a Perl script to write out the first line to file1, the second line to file2, the third line to file3, fourth to file4, the fifth to file1 again, and so on. I had 4 dbspaces to layout the database, so the tables in file1 went to dbspace1, and so on. After that I smoothed out the activity manually. Not rocket science, but it seemed to work. HTH Sujit Pal