PROUTIL PARTITIONMANAGE VIEW qualifier

Partition management option to view information about table partitions.

Syntax

proutil db-name -C partitionmanage view 
    [ table table-name 
    [ partition table-partition-name | composite initial ]]
    { list | state | status }

Parameters

db-name

Specifies the database where you are performing partition management.

table table-name

Specifies the table for the PARTITIONMANAGE VIEW operation.

partition table-partition-name

Specifies the partition instance that PARTITIONMANAGE VIEW is to report on.

composite initial

Specifies that PARTITIONMANAGE VIEW is to report on the composite initial partition of the table.

list

Specifies that PARTITIONMANAGE VIEW is to list partitions by partition definition order (adjacent definitions not by partition Id).

state

Specifies that PARTITIONMANAGE VIEW is to report on the state of a partition. Partitions states are:

• No state reported (blank) — The partition has no special characteristics, and is readable and writable.
• Rebuilding — The partition is involved in a partition rebuild operation. The rebuilding type indicates the type of rebuild (split, merge, truncate, etc) and if the partition is the source or target.
• Read Only — The partition is set to read only.
• Deallocated — The partition is deallocated.

status

Specifies that PARTITIONMANAGE VIEW is to report on the status of a partition that is in a rebuilding state. The number of rows in each partition is reported and can be used to measure progress of a partition operation such as split or merge.

Sample output

Depending on the qualifier chosen, PARTITIONMANAGE VIEW displays different output. The following samples illustrate the different types:

• List output for a partition that is partitioned on three columns

  PROGRESS Partition View Database: /usr1/docsample/tpdb Date: Wed Nov 12 11:10:36 2014 Partition List: -------------------------- Table Column Partitioning Values PUB.order RenamedOrderPart1:26 1 4 01/01/2015 00:00:00.000

• State output for allocated partitions in a default state

  PROGRESS Partition View Database: /usr1/docsample/tpdb_np Date: Wed Nov 12 11:20:24 2014 PARTITION STATE --------------------- Table State Description PUB.history initial:0 hist_ware1_to2020:0

• State output for a partition in a split-pending state

  PROGRESS Partition View Database: /usr1/docsample/tpdb_np Date: Wed Nov 12 11:30:24 2014 PARTITION STATE --------------------- Table State Description PUB.history initial:0 Read Only hist_ware1_to1980:2 Rebuilding, Deallocated, Read Only Split (T) Source = Composite initial:0 hist_ware1_to1990:3 Rebuilding, Deallocated, Read Only Split (T) Source = Composite initial:0 hist_ware1_to2000:4 Rebuilding, Deallocated, Read Only Split (T) Source = Composite initial:0 hist_ware1_to2010:5 Rebuilding, Deallocated, Read Only Split (T) Source = Composite initial:0 hist_ware1_to2020:1 Rebuilding, Deallocated, Read Only Split (T) Source = Composite initial:0

• Status output for a partition

  PROGRESS Partition View Database: /usr1/docsample/tpdb Date: Wed Nov 12 11:40:51 2014 PARTITION STATUS ---------------------- Table Rows PUB.customer initial:0 0 cust_id_llr_10:10 0 cust_id_llr_8:8 26 cust_id_llr_7:7 34 cust_id_llr_9:9 28 cust_id_llr_6:6 41 cust_id_llr_5:5 21 cust_id_llr_3:3 35 cust_id_llr_2:2 26 cust_id_llr_4:4 37 cust_id_llr_1:1 1 cust_id_llr_20:20 0 cust_id_llr_18:18 42 cust_id_llr_17:17 64 cust_id_llr_19:19 72 cust_id_llr_16:16 58 cust_id_llr_15:15 67 cust_id_llr_13:13 74 cust_id_llr_12:12 0 cust_id_llr_14:14 62 RenamedCustomerPart1:11 9 cust_id_llr_30:30 0 cust_id_llr_28:28 52 cust_id_llr_27:27 51 cust_id_llr_29:29 58 cust_id_llr_26:26 67 cust_id_llr_25:25 51 cust_id_llr_23:23 51 cust_id_llr_22:22 66 cust_id_llr_24:24 74 cust_id_llr_21:21 4 cust_id_llr_40:40 0 cust_id_llr_38:38 53 cust_id_llr_37:37 53 cust_id_llr_39:39 68 cust_id_llr_36:36 87 cust_id_llr_35:35 66 cust_id_llr_33:33 62 cust_id_llr_32:32 64 cust_id_llr_34:34 53 cust_id_llr_31:31 2 cust_id_llr_50:50 0 cust_id_llr_48:48 75 cust_id_llr_47:47 65 cust_id_llr_49:49 74 cust_id_llr_46:46 74 cust_id_llr_45:45 59 cust_id_llr_43:43 60 cust_id_llr_42:42 50 cust_id_llr_44:44 39 cust_id_llr_41:41 5

  Note: You can use the number of rows to track the progress of partition operations such as split or merge.

Notes

• PARTITIONMANAGE VIEW runs against databases that are both online and offline.
• Multiple instances of PARTITIONMANAGE VIEW can run simultaneously provided they operate on different partitions.
• PARTITIONMANAGE VIEW runs against both Replication source and target databases.
• If db-name is a UTF-8 database, you must specify -cpinternal UTF-8 on the command line. If not specified, an error message is generated and PARTITIONMANAGE VIEW exits.