Hitachi

uCosminexus Service Platform Setup and Operation Guide

2.3.6 Estimating the number of exclusive requests of the database (HiRDB)

The number of exclusive requests must be estimated while deleting execution history if the database used by HCSC server is HiRDB. Setting is not necessary if the database is not used.

This section describes the estimation method of the number of exclusive requests when execution history is deleted. The number of estimated exclusive requests must be defined in HiRDB definition file. For details on HiRDB definition file and the operands defined in the definition file, see the contents related to estimation of the number of exclusive resources in "HiRDB Version 9 System Definition".

Organization of this subsection

(1) Estimating the number of exclusive requests while deleting process instance execution history (cscpidelete command)

This section describes estimation of the number of exclusive requests while deleting process instance execution history (cscpidelete command). For details on the how to delete process instance execution history by cscpidelete command, see "6.1.4(2) Using commands to delete execution logs".

Estimation target

Estimation target SQL is "DELETE (if there is no LOCK TABLE and for index key value non-exclusive method)" of operation system SQL.

For details on "DELETE (if there is no LOCK TABLE and for index key value non-exclusive method)", see the contents related to estimation of the number of exclusive resources in "HiRDB system definition".

Estimation method

Calculate the number of exclusive resources in all tables in estimation of the number of exclusive requests. For the number of exclusive resources, use the values shown in "Table 2-12 Values used in estimating the number of exclusive resources (deleting process instance execution history by cscpidelete command)" and calculate.

After calculation, add the surplus value in the largest number of exclusive resources in the number of exclusive resources and then estimate the number of exclusive requests.

Define the number of estimated exclusive requests in HiRDB definition file.

For details on how to estimate the number of exclusive resources and how to set the number of estimated exclusive requests, see the contents related to estimation of the number of exclusive resources in "HiRDB system definition" and the contents related to "pd_lck_pool_size" of the operand related to exclusive control.

The following table describes the values used in estimating the number of exclusive resources when process instance execution history is to be deleted (cscpidelete command):

Table 2‒12: Values used in estimating the number of exclusive resources (deleting process instance execution history by cscpidelete command)

Item number

Item

Specified value

A

B

C

D

E

F

G

H

I

1

Number of RD areas to be deleted

2

2

3

2

2

2

2

4

2

2

Number of deleted rows

1

Maximum value of the number of activities defined in 1 business process

Maximum value of the number of links defined in 1 business process

Maximum value of the number of correlation sets defined in 1 business process

Maximum value of the number of string type variables of global variables defined in 1 business process

Maximum value of the number of numeric type variables of global variables defined in 1 business process

Maximum value of the number of boolean type variables of global variables defined in 1 business process

Maximum value of the number of message type variables of global variables defined in 1 business process

Maximum value of the number of activities defined in 1 business process

3

Number of switches

1

1

1

1

1

1

1

1

1

4

Number of columns over 256 bytes in VARCHAR, NVARCHAR, MVARCHAR

0

0

0

0

0

0

0

0

0

5

Number of BINARY types that cannot be stored in 1 page

0

0

0

0

0

0

1

0

0

6

Number of deleted LOB data items

-

-

-

-

-

-

-

-

-

7

Number of deleted LOB data storage segments

-

-

-

-

-

-

-

-

-

8

Data type plug-in or index type plug-in

-

-

-

-

-

-

-

-

-

9

pd_inner_replica_control operand (in UNIX version HiRDB)

-

-

-

-

-

-

-

-

-

10

Routine

-

-

-

-

-

-

-

-

-

11

Preprocessing

See "Table 2-13 Values used in estimating the number of exclusive requests for preprocessing (while deleting process instance execution history)".

(Legend)

A:CSCBP_<Cluster name>_PROCESS table

B:CSCBP_<Cluster name>_ACTIVITY table

C:CSCBP_<Cluster name>_LINK table

D:CSCBP_<Cluster name>_CORRELATIONSET table

E:CSCBP_<Cluster name>_STR_VARIABLE table

F:CSCBP_<Cluster name>_NUM_VARIABLE table

G:CSCBP_<Cluster name>_BOOL_VARIABLE table

H:CSCBP_<Cluster name>_MSG_VARIABLE table

I:CSCBP_<Cluster name>_MSG_RELATION table

-: Undefined or unused item.

The following table describes the values used in estimating the number of exclusive requests for preprocessing. For the number of exclusive requests for preprocessing, see "HiRDB Version 9 System Definition".

Table 2‒13: Values used in estimating the number of exclusive requests for preprocessing (while deleting process instance execution history)

Item number

Item

Specified value

A

B

C

D

E

F

G

H

I

1

Number of tables used

1

1

1

1

1

1

1

1

1

2

Number of view tables used

0

1

1

0

1

1

1

1

1

3

Number of columns

8

13

4

8

4

4

4

4

5

4

Number of indices

4

1

1

2

1

1

1

1

3

5

Number of table partitions

-

-

-

-

-

-

-

-

-

6

Number of index partitions

-

-

-

-

-

-

-

-

-

7

User definition type or functionality use

-

-

-

-

-

-

-

-

-

8

Optimization information

-

-

-

-

-

-

-

-

-

9

View table use

0

1

1

0

1

1

1

1

0

10

Number of columns configuring view tables

0

14

6

0

7

7

7

7

0

11

LOB column definition

-

-

-

-

-

-

-

-

-

12

Definition of user definition type column

-

-

-

-

-

-

-

-

-

13

LOB attribute

-

-

-

-

-

-

-

-

-

14

Parent type

-

-

-

-

-

-

-

-

-

15

Functionality use

-

-

-

-

-

-

-

-

-

16

Plug-in use

-

-

-

-

-

-

-

-

-

17

Routine use

-

-

-

-

-

-

-

-

-
(Legend)

A:CSCBP_<Cluster name>_PROCESS table

B:CSCBP_<Cluster name>_ACTIVITY table

C:CSCBP_<Cluster name>_LINK table

D:CSCBP_<Cluster name>_CORRELATIONSET table

E:CSCBP_<Cluster name>_STR_VARIABLE table

F:CSCBP_<Cluster name>_NUM_VARIABLE table

G:CSCBP_<Cluster name>_BOOL_VARIABLE table

H:CSCBP_<Cluster name>_MSG_VARIABLE table

I:CSCBP_<Cluster name>_MSG_RELATION table

-: Undefined or unused item.

To Page Top

(2) Estimating the number of exclusive requests while deleting process instance execution history (RD area unit)

This section describes estimation of the number of exclusive requests while deleting process instance execution history (RD area unit). For details on how to delete process instance execution history in RD area unit, see "6.1.4(3) Using database creation utility (pdload) to delete execution logs".

Estimation target

The estimation target is the database creation utility (pdload) and the database reorganization utility (pdrorg).

For details on the database creation utility (pdload) and the database reorganization utility (pdrorg), see the description related to exclusive resource estimation in "HiRDB Version 9 System Definition".

Estimation method

Calculate the number of exclusive resources by using the values shown in "Table 2-14 Values used in estimating the number of exclusive resources (while deleting process instance execution history in RD area units)".

After calculation, add the surplus value in the largest number of exclusive resources in the number of exclusive resources and then estimate the number of exclusive requests.

Define the number of estimated exclusive requests in HiRDB definition file.

The following table describes the values used in estimating the number of exclusive resources while deleting process instance execution history (RD area unit).

Table 2‒14: Values used in estimating the number of exclusive resources (while deleting process instance execution history in RD area units)

Item number

Item

Specified value

A

B

C

D

E

F

G

H

I

1

Number of table columns

9

14

5

9

5

5

5

5

6

2

Number of table indices

4

1

1

2

1

1

1

1

3

3

Number of storage RD areas in table

This depends on the contents of the SQL script file when HCSC server is set up.

4

Number of RD area segments being used for storage in table storage

You can confirm this by specifying -r option in pddbst command and executing. For details on pddbst command, see the description of database status analysis utility (pddbst) in "HiRDB command reference".

5

Number of RD area segments used for index storage

6

Number of RD area segments used for LOB

-

-

-

-

-

-

-

-

-

7

Number of items generated in used ordinal number

-

-

-

-

-

-

-

-

-

8

Number of RD areas for storage of items generated in used ordinal number

-

-

-

-

-

-

-

-

-
(Legend)

A:CSCBP_<Cluster name>_PROCESS table

B:CSCBP_<Cluster name>_ACTIVITY table

C:CSCBP_<Cluster name>_LINK table

D:CSCBP_<Cluster name>_CORRELATIONSET table

E:CSCBP_<Cluster name>_STR_VARIABLE table

F:CSCBP_<Cluster name>_NUM_VARIABLE table

G:CSCBP_<Cluster name>_BOOL_VARIABLE table

H:CSCBP_<Cluster name>_MSG_VARIABLE table

I:CSCBP_<Cluster name>_MSG_RELATION table

-: Undefined or unused item.

To Page Top

Trademarks

All Rights Reserved. Copyright (C) 2022, Hitachi, Ltd.