- 6.2.3 DUMP Codes 2000 to 2999
- 6.2.3.1 DUMP 2300
- 6.2.3.2 DUMP 2301
- 6.2.3.3 DUMP 2302
- 6.2.3.4 DUMP 2303
- 6.2.3.5 DUMP 2304
- 6.2.3.6 DUMP 2305
- 6.2.3.7 DUMP 2308
- 6.2.3.8 DUMP 2315
- 6.2.3.9 DUMP 2350
- 6.2.3.10 DUMP 2352
- 6.2.3.11 DUMP 2400
- 6.2.3.12 DUMP 2401
- 6.2.3.13 DUMP 2402
- 6.2.3.14 DUMP 2403
- 6.2.3.15 DUMP 2404
- 6.2.3.16 DUMP 2405
- 6.2.3.17 DUMP 2406
- 6.2.3.18 DUMP 2500
- 6.2.3.19 DUMP 2501
- 6.2.3.20 DUMP 2502
- 6.2.3.21 DUMP 2503
- 6.2.3.22 DUMP 2504
- 6.2.3.23 DUMP 2505
- 6.2.3.24 DUMP 2506
- 6.2.3.25 DUMP 2507
- 6.2.3.26 DUMP 2508
- 6.2.3.27 DUMP 2509
- 6.2.3.28 DUMP 2510
- 6.2.3.29 DUMP 2511
- 6.2.3.30 DUMP 2512
- 6.2.3.31 DUMP 2513
- 6.2.3.32 DUMP 2514
- 6.2.3.33 DUMP 2515
- 6.2.3.34 DUMP 2550
- 6.2.3.35 DUMP 2600
- 6.2.3.36 DUMP 2601
- 6.2.3.37 DUMP 2602
- 6.2.3.38 DUMP 2603
- 6.2.3.39 DUMP 2604
| Code | Symbol | Kernel Block(s) |
2512 [delay] |
TcStartDumpIndexOpCount |
DBTC |
Description.
Dumps the value of
MaxNoOfConcurrentOperations, and the
current resource usage, in a continuous loop. The
delay time between reports can
optionally be specified (in seconds), with the default being
1 and the maximum value being 25 (values greater than 25 are
silently coerced to 25).
Sample Output. (Single report:)
Node 2: IndexOpCount: pool: 8192 free: 8192
Additional Information.
There appears to be no way to disable the repeated checking
of MaxNoOfConcurrentOperations once
started by this command, except by restarting the data node.
It may be preferable for this reason to use DUMP
2513 instead (see
Section 6.2.3.31, “DUMP 2513”).
