R
Rob Fitzpatrick
Guest
Sorry Paul and James, I was wrong about -rusage 
. You get the 11480 and 11483 messages by default, at least back to 10.2B08. The -rusage param adds lines like this: [2017/07/18@14:10:14.546-0400] P-75487 T-139980717442816 I DBUTIL : (-----) Resource usage: CPU user 0.002000, system 0.001000 Resource usage: DISK reads: 80 KB at 39 KB/sec, writes: 0 KB at 0 KB/sec [2017/07/18@14:10:14.546-0400] P-75487 T-139980717442816 I DBUTIL : (-----) Resource usage: CPU user 0.003000, system 0.002999 Resource usage: DISK reads: 1640 KB at 818 KB/sec, writes: 456 KB at 227 KB/sec Not sure where i got the idea that it was tied to 11480/11483 but (not surprisingly) Paul is correct: -rusage provides info that is interesting but not critical. That said, you should also pay attention to your 11480/11483 messages and ideally you want to see 0K of temp file I/O per area.
Continue reading...
. You get the 11480 and 11483 messages by default, at least back to 10.2B08. The -rusage param adds lines like this: [2017/07/18@14:10:14.546-0400] P-75487 T-139980717442816 I DBUTIL : (-----) Resource usage: CPU user 0.002000, system 0.001000 Resource usage: DISK reads: 80 KB at 39 KB/sec, writes: 0 KB at 0 KB/sec [2017/07/18@14:10:14.546-0400] P-75487 T-139980717442816 I DBUTIL : (-----) Resource usage: CPU user 0.003000, system 0.002999 Resource usage: DISK reads: 1640 KB at 818 KB/sec, writes: 456 KB at 227 KB/sec Not sure where i got the idea that it was tied to 11480/11483 but (not surprisingly) Paul is correct: -rusage provides info that is interesting but not critical. That said, you should also pay attention to your 11480/11483 messages and ideally you want to see 0K of temp file I/O per area.Continue reading...