Hitachi

Hitachi Advanced Database Setup and Operation Guide

6.3.3 Determining the memory requirement for starting the HADB server

When you use the adbstart command to start the HADB server, the HADB server uses the types of memories listed below. Therefore, determine the requirement for each type of memory.

■ Shared memory

  • Shared memory management area

  • Global buffer page

  • Process common memory

  • Real thread private memory

■ Process memory

  • Heap memory

The following subsections describe the formulas for determining the required amounts of each of these types of memory.

Organization of this subsection

(1) Determining the shared memory management area requirement (for starting the HADB server)

Use the following formula to determine the shared memory management area requirement (SHMMAN) for starting the HADB server.

Formula (kilobytes)

[Figure]

Explanation of variables

rthd_num

Value specified for the adb_sys_rthd_num operand in the server definition

max_users

Value specified for the adb_sys_max_users operand in the server definition

multi_num

Use the following formula to determine its value.

Formula

[Figure]
SHM_LSGBUF

Shared memory that stores the content displayed by the adbls -d gbuf command

Substitute the following value:

Value (kilobytes)

SHM_LSGBUF = 337
SHM_LSLBUF

Shared memory that stores the content displayed by the adbls -d lbuf command

Substitute the following value:

Value (kilobytes)

SHM_LSLBUF = 33

To Page Top

(2) Determining the global buffer page requirement (for starting the HADB server)

Use the following formula to determine the global buffer page requirement (SHM_BUFGLOBAL) for starting the HADB server.

Formula (kilobytes)

[Figure]

Explanation of variables

MSTPAGES: Pages in the master directory DB area

Use the following formula to determine its value.

Formula (bytes)

[Figure]

RTHNUM: See the description of the variable RTHNUM in (a) Determining the variable SCI under (3) Determining the process common memory requirement (for starting the HADB server).

WRKPAGES: Pages in the work table DB area

Use the following formula to determine its value.

Formula (bytes)
WRKPAGES = (wrk_page_num + 1) × wrk_page_size

  • wrk_page_num

    Value specified for the adb_dbbuff_wrktbl_glb_blk_num operand in the server definition

  • wrk_page_size

    Determine this value in bytes based on the explanation of the page size of the work table DB area in Table 6‒3: DB area page size.

Σ(BUFPAGES + SCANPAGES): Sum total of the BUFPAGES and SCANPAGES variable values calculated for all specified adbbuff operands

This total value also includes the following adbbuff operands:

  • adbbuff operand with the -o option specified

  • adbbuff operand without the -n or -o option specified

The following explains each of these in detail.

adbbuff operand with the -o option specified

When the -o option is specified, DB areas that are not specified in the -n option of the adbbuff operand are classified according to page size and the adbbuff operand is defined automatically. Keep this in mind when determining the value of BUFPAGES. An example follows.

Example: When the following four DB areas are not specified in the -n option

■ Target DB areas

  • ADBDIC, ADBSTBL, ADBUTBL01, ADBUTBL02 (page size: 4 kilobytes)

  • ADBUTBL03 (page size: 32 kilobytes)

■ Server definition specification example

adbbuff -g SAMPLEBUF -o -p 100

In this case, the four DB areas are classified according to page size and are defined automatically. If any of the options (-p, -a) is specified in the adbbuff operand for which the -o option is specified, the option specification values are also defined automatically.

■ Example of automatic definition

adbbuff -g SAMPLEBUF#0000004096 -n ADBDIC, ADBSTBL, ADBUTBL01, ADBUTBL02 -p 100
adbbuff -g SAMPLEBUF#0000032768 -n ADBUTBL03 -p 100

Note: The underlined portions are the global buffer names that are added during automatic definition.

adbbuff operand without the -n or -o option specified

When there are DB areas that are not specified in the -n option of the adbbuff operand, and the -o option is not specified either, the DB areas are classified according to page size, as is the case when the -o option is specified, and the adbbuff operand is defined automatically. Keep this in mind when determining the value of BUFPAGES. An example follows.

Example: When the following four DB areas are not specified in the -n option, and the -o option is not specified either

■ Target DB areas

  • ADBDIC, ADBSTBL, ADBUTBL01, ADBUTBL02 (page size: 4 kilobytes)

  • ADBUTBL03 (page size: 32 kilobytes)

■ Server definition specification example

  • Not specified.

In this case, the four DB areas are classified according to page size and are defined automatically. The value that is assumed when the -p option is omitted is defined.

■ Example of automatic definition

adbbuff -g ##ADBOTHER#0000004096 -n ADBDIC, ADBSTBL, ADBUTBL01, ADBUTBL02
adbbuff -g ##ADBOTHER#0000032768 -n ADBUTBL03

Note: The underlined portions are the global buffer names that are defined automatically.

BUFPAGES: Page area

Use the following formula to determine its value.

Formula (bytes)
BUFPAGES = (GLBPAGES + OPTTYPES) × page_size
GLBPAGES:

Sum total of the values specified for the various options (-p, -a) of the adbbuff operand in the server definition

OPTTYPES:

The number of adbbuff operand options (-p, -a) that are specified in the server definition

If all options are omitted, use 1 for OPTTYPES. For example, in the following specification example, OPTTYPES is 2, because the -p and -a options are specified.

Example

adbbuff -g SAMPLEBUF -n ADBUTBL01 -p 10 -a 10
page_size:

Page size of the DB area specified in the -n option of the adbbuff operand in the server definition (bytes)

Determine this value based on the explanation of the page size of the data DB area in Table 6‒3: DB area page size.

SCANPAGES: Table scan pages

Determine the value from the formula shown below. However, if the -v option and -k option of the adbbuff operand in the server definition are omitted, substitute 0 for SCANPAGES.

Formula (bytes)
SCANPAGES = SCANBLOCKS × 4,194,304
SCANBLOCKS:

Number of blocks in the table scan buffer

Use the following formula to determine the value:

[Figure]
adbbuff_opt_v:

Value specified for size-of-memory-used-by-table-scan-buffer in the -v option of the adbbuff operand in the server definition

However, if the -k option of the adbbuff operand is specified in the server definition, use the following formula to determine the value:

value specified for -k option of adbbuff operand × 4
page_size:

Page size of the DB area specified in the -n option of the adbbuff operand in the server definition (bytes)

Determine this value based on the explanation of the page size of the data DB area in Table 6‒3: DB area page size.

Table 6‒3: DB area page size

No.

DB area type

Page size (bytes)

1

Master directory DB area

4,096

2

Dictionary DB area

3

System-table DB area

4

Work table DB area

 
↑work_page_size ÷ 32↑ × 32 × 1,024

For work_page_size, specify the following value:

If the adb_dbarea_wrk_page_size operand is specified in the server definition:

Value of the adb_dbarea_wrk_page_size operand in the server definition

If the adb_dbarea_wrk_page_size operand is not specified in the server definition

Value of the adb_init_wrk_page_size operand for the initialization option of the adbinit command

5

Data DB area
If the DB area was created using the adbinit command

Use the following formula to determine the page size:

  Specification value of the -p option specified in 
the adbinitdbarea initialization option × 1,024
If the DB area was created using the adbmodarea command

Use the following formula to determine the page size:

  Specification value of the -p option specified in 
the adbaddarea DB area addition and modification option × 1,024
Note

If a database has been built, you can also use a command to check the page size of the DB area as follows:

For the work table DB area:

  • Use the adbls -d gbuf command to obtain information about the global buffers.

  • Use the adbls -d lbuf command to obtain information about the buffer for the local work table.

For the data DB area:

  • Use the adbdbstatus -d summary -c dbarea command to obtain the summary information about the DB area.

  • Use the adbls -d gbuf command to obtain information about the global buffers.

rthd_num:

Value specified for the adb_sys_rthd_num operand in the server definition

To Page Top

(3) Determining the process common memory requirement (for starting the HADB server)

Use the following formula to determine the requirement for the process common memory (PROC_STARTSZ) for starting the HADB server.

Formula (kilobytes)

[Figure]
Explanation of variables

(a) Determining the variable SCI

Use the following formula to determine the value of variable SCI.

Formula (kilobytes)

[Figure]
#1

Add this value when you use the multi-node function.

#2

Add this value when you use the client-group facility.

#3

Add this value when you use centralized management of client definitions.

Explanation of the variables

CON: Connection control setting

Use the following formula to determine its value.

Formula (bytes)

[Figure]
max_users

Value specified for the adb_sys_max_users operand in the server definition

RTH: Real thread control setting

Use the following formula to determine its value.

Formula (bytes)

[Figure]
RTHNUM: Total number of real threads

Formula

[Figure]
#

Add this value when you use the multi-node function.

rthd_num

Value specified for the adb_sys_rthd_num operand in the server definition

CTHNUM: Number of connection threads

Formula

CTHNUM = 3 + max_users
max_users

Value specified for the adb_sys_max_users operand in the server definition

MLTNUM: Number of threads exclusively for the multi-node function

Determine this value when you use the multi-node function.

Formula

MLTNUM = multi_node_num × 2 + 3
multi_node_num

Number of host names specified in the adb_sys_multi_node_info operand in the server definition

UTH: Pseudo real thread control setting

Use the following formula to determine its value.

Formula (bytes)

[Figure]
UTHNUM: Total number of pseudo-threads

Formula

UTHNUM = 2 + uthd_num

uthd_num: Value specified for the adb_sys_uthd_num operand in the server definition

RTHNUM

See the variable RTHNUM in the description of the variable RTH in (a) Determining the variable SCI.

TRN: Transaction management setting

Use the following formula to determine its value.

Formula (bytes)

[Figure]
max_users

Value specified for the adb_sys_max_users operand in the server definition

DEF: Definition analysis result setting

Use the following formula to determine this value.

Formula (bytes)
DEF = 3,701 + 475 × dbbuff_defnum

dbbuff_defnum: Number of adbbuff operands specified in the server definition

MLT: Multi-node control information

Determine this value when you use the multi-node function.

Formula (bytes)

[Figure]
multi_node_num

Number of host names specified in the adb_sys_multi_node_info operand in the server definition

CGR: Client group control information

Determine this value when you use the client-group facility.

Formula (bytes)

[Figure]
cltgrp_num

Number of client groups specified in the adbcltgrp operand in the server definition

CMI: Information for centralized management of client definitions

Determine this value when you use centralized management of client definitions.

Formula (bytes)

[Figure]
cltmng_num

Total number of adbclientmang operands (for client-managing definition) specified in the client management definition file

authid_num

Total number of authorization identifiers specified for the adbclientmang operands in the client-managing definition

(b) Determining the variable RPCS

Use the following formula to determine the value of variable RPCS.

Formula (kilobytes)

[Figure]

Explanation of variables

CTHNUM

See the description of the variable CTHNUM in (a) Determining the variable SCI.

MLTNUM

See the description of the variable MLTNUM in (a) Determining the variable SCI.

ipv4_num

Number of valid IPv4 addresses of the local node (addresses)

(c) Determining the variable DICS

Use the following formula to determine the value of variable DICS.

Formula (kilobytes)

DICS = tbldef_cache_size + 84
Explanation of variables

tbldef_cache_size: Value specified for the adb_sql_tbldef_cache_size operand in the server definition

(d) Determining the variable BUFGLOBAL

Use the following formula to determine the value of variable BUFGLOBAL.

Formula (kilobytes)

[Figure]
#

Add this value when you use the multi-node function.

Explanation of variables

BUFDEF: adbbuff operand analysis

Use the following formula to determine its value.

Formula (bytes)

BUFDEF = 3,640 + 608 × BUFOPE_NUM
BUFOPE_NUM: Number of times the adbbuff operand in the server definition is defined

This total value also includes the following adbbuff operands:

  • adbbuff operand with the -o option specified

  • adbbuff operand without the -n or -o option specified

The following explains each of these in detail.

adbbuff operand with the -o option specified

When the -o option is specified, DB areas that are not specified in the -n option of the adbbuff operand are classified according to page size, and the adbbuff operand is defined automatically. Keep this in mind when determining the value of BUFOPE_NUM. An example follows.

Example: When the following four DB areas are not specified in the -n option

▪ Target DB areas

  • ADBDIC, ADBSTBL, ADBUTBL01, ADBUTBL02 (page size: 4 kilobytes)

  • ADBUTBL03 (page size: 32 kilobytes)

▪ Server definition specification example

adbbuff -g SAMPLEBUF -o

In this case, the four DB areas are classified according to page size and are defined automatically. Therefore, BUFOPE_NUM becomes 2,

▪ Example of automatic definition

adbbuff -g SAMPLEBUF#0000004096 -n ADBDIC, ADBSTBL, ADBUTBL01, ADBUTBL02
adbbuff -g SAMPLEBUF#0000032768 -n ADBUTBL03

Note: The underlined portions are the global buffer names that are added during automatic definition.

adbbuff operand without the -n or -o option specified

When there are DB areas that are not specified in the -n option of the adbbuff operand, and the -o option is not specified either, DB areas are classified according to page size, as is the case when the -o option is specified, and the adbbuff operand is defined automatically. Keep this in mind when determining the value of BUFOPE_NUM. An example follows.

Example: When a DB area (ADBDIC, ADBSTBL) is not specified in the -n option, and the -o option is not specified either

▪ Target DB areas

  • ADBDIC, ADBUTBL01, ADBUTBL02 (page size: 4 kilobytes)

  • ADBUTBL03 (page size: 32 kilobytes)

▪ Server definition specification example

adbbuff -g SAMPLEBUF01 -n ADBUTBL01, ADBUTBL02
adbbuff -g SAMPLEBUF02 -n ADBUTBL03

In this case, ADBDIC and ADBSTBL, which have not been specified, are defined automatically. Therefore, BUFOPE_NUM becomes 4, which is for ADBDIC plus the two that are specified.

▪ Example of automatic definition

adbbuff -g ##ADBOTHER#0000004096 -n ADBDIC, ADBSTBL

Note: The underlined portions are the global buffer names that are defined automatically.

BUFCTL: Global buffer control area

Use the following formula to determine its value.

Formula (bytes)

[Figure]
ΣOPTTYPES: Total number of options (-p, -a) specified in each adbbuff operand

This total value also includes the following adbbuff operands:

  • adbbuff operand with the -o option specified

  • adbbuff operand without the -n or -o option specified

For details, see the description of the variable Σ(BUFPAGES + SCANPAGES) in (2) Determining the global buffer page requirement (for starting the HADB server).

An example of how to determine the number of option specifications follows.

Example

When the adbbuff operand is defined as shown in the following, the total number of specified options is 5 (1 + 2 + 1 + 1), including the automatically defined ADBDIC and ADBSTBL.

▪ Server definition specification example

    adbbuff -g SAMPLEBUF1 -n ADBUTBL01 -p 100
    adbbuff -g SAMPLEBUF2 -n ADBUTBL02 -p 100 -a 100
    adbbuff -g SAMPLEBUF3 -n ADBUTBL03#

#: The -p option is assumed.

▪ Example of automatic definition

adbbuff -g ##ADBOTHER#0000004096 -n ADBDIC, ADBSTBL#

Note: The underlined portions are the global buffer names that are defined automatically.

#: The -p option is assumed.

DBAREA_NUM:

Total number of DB areas

BUFOPT_V_NUM:

Number of defined adbbuff operands with the -v option or -k option specified

RTHNUM:

See the description of the variable RTHNUM in (a) Determining the variable SCI.

BUFINT: Temporary area for multiplexed initialization

Use the following formula to determine its value.

Formula (bytes)

BUFINT = 480 + 80 × ΣBUFWRK_NUM + 8 × rthd_num + INITQUE
rthd_num:

Value specified for the adb_sys_rthd_num operand in the server definition

INITQUE: Initialization processing queue

Use the following formula to determine its value.

Formula (bytes)

INITQUE = 80 × RTHNUM × RTHNUM + 632 × RTHNUM + 960 + 64 × ΣBUFWRK_NUM

RTHNUM: See the description of the variable RTHNUM in (a) Determining the variable SCI.

ΣBUFWRK_NUM: Sum total of the BUFWRK_NUM variables calculated for each adbbuff operand

This total value also includes the following adbbuff operands:

  • adbbuff operand with the -o option specified

  • adbbuff operand without the -n or -o option specified

For details, see the description of the variable Σ(BUFPAGES + SCANPAGES) in (2) Determining the global buffer page requirement (for starting the HADB server).

BUFWRK_NUM: Use the following formula to determine its value.

Formula (count)

[Figure]
OPTTYPES:

See the description of the variable OPTTYPES in (2) Determining the global buffer page requirement (for starting the HADB server).

adbbuff_opt_p:

Value specified for the -p option of the adbbuff operand

adbbuff_opt_a:

Value specified for the -a option of the adbbuff operand

BUFOPT_V: Whether the -v option or -k option of the adbbuff operand is specified

Substitute 1 if the -v option or -k option is specified; otherwise substitute 0.

SCAN_INIT: Area for multiplexed initialization of the table scan buffer

If the -v option or -k option of the adbbuff operand is specified, substitute the value specified for the adb_sys_rthd_num operand in the server definition. Substitute 0 if neither the -v option nor the -k option is specified.

BUFPGE: Page management area

Use the following formula to determine its value.

Formula (bytes)

BUFPGE = ΣTYPEBUF + MSTBUF + WRKBUF
ΣTYPEBUF: Sum total of the TYPEBUF variables determined for the options (-p, -a) specified in each adbbuff operand

This total value also includes the following adbbuff operands:

  • adbbuff operand with the -o option specified

  • adbbuff operand without the -n or -o option specified

For details, see the description of the variable Σ(BUFPAGES + SCANPAGES) in (2) Determining the global buffer page requirement (for starting the HADB server).

TYPEBUF: Use the following formula to determine its value.

Formula (bytes)

TYPEBUF = GCLBUF(page_num) + BUFMEM(page_num)
page_num:

Value specified for any of the options (-p, -a) specified in the adbbuff operand in the server definition

GCLBUF: Use the following formula to determine its value.

Formula (bytes)

GCLBUF(X) = 192 × RTHNUM + 192 + X × (176 + BUFLOG)
RTHNUM:

See the description of the variable RTHNUM in (a) Determining the variable SCI.

X:

Number of pages to be targeted

BUFLOG: Log area

Use the following formula to determine its value.

Formula (bytes)

BUFLOG = ↓(((16 + ((RTHNUM - 6) ÷ 8 + 1)) + 15) ÷ 16)↓ × 16
BUFMEM: Use the following formula to determine its value.

Formula (bytes)

BUFMEM(X) =
    480 × RTHNUM × RTHNUM + (584 + 24 × UTHNUM) × RTHNUM
    + (352 + 16 × RTHNUM) × HASHTBL_NUM + 80 × X + 24 × UTHNUM + 368
RTHNUM:

See the description of the variable RTHNUM in (a) Determining the variable SCI.

UTHNUM:

See the description of the variable UTHNUM in (a) Determining the variable SCI.

X:

Number of pages to be targeted

HASHTBL_NUM: Use the following formula to determine its value.

Formula

HASHTBL_NUM = X ÷ 4
MSTBUF: Use the following formula to determine its value.

Formula (bytes)

MSTBUF = RTHNUM × 2
RTHNUM:

See the description of the variable RTHNUM in (a) Determining the variable SCI.

WRKBUF:

Value specified for the adb_dbbuff_wrktbl_glb_blk_num operand in the server definition

BUFTBL: Table scan buffer

Use the following formula to determine its value.

Formula (bytes)

BUFTBL = ΣSCANBUF
ΣSCANBUF: Number of table scan buffers for batch reading specified in each adbbuff operand

This is the sum total of the SCANBUF variables calculated for each -v or -k option specified for the adbbuff operand.

SCANBUF: Use the following formula to determine its value.

Formula (bytes)

[Figure]

For adbbuff operands for which neither the -v option nor -k option is specified, assume 0 for SCANBUF.

BUFUPDLISTCTL

Area for managing the update list among nodes

Substitute the following value.

Value (bytes)

[Figure]

(e) Determining the variable DBAREAINF

Use the following formula to determine the variable DBAREAINF:

Formula (kilobytes)

[Figure]
Explanation of variables
dbarea_num

Number of all DB areas

dbarea_file_num

Number of all DB area files

table_num

Total number of user-defined base tables

column_table_num

Total number of user-defined base tables that are column store tables

index_num

Total number of user-defined indexes

SEGSIZE

Segment size in the DB area in which DB area files are defined (pages)

Use the following formula to determine the segment size:

SEGSIZE = 4,194,304 ÷ page_size
max_users

Value specified for the adb_sys_max_users operand in the server definition

rthd_num

Value specified for the adb_sys_rthd_num operand in the server definition

(f) Determining the variable DBSYSINF

For the variable DBSYSINF, substitute the following value.

Value (kilobytes)

DBSYSINF = 1,308

(g) Determining the variable RECCTL

Use the following formula to determine the value of variable RECCTL.

Formula (kilobytes)

[Figure]
Explanation of variables

log_usrbuf_num: Value specified for the adb_log_usrbuf_num operand in the server definition

log_usrfile_num: Value specified for the adb_log_usrfile_num operand in the server definition

max_users: Value specified for the adb_sys_max_users operand in the server definition

(h) Determining the variable DBUPDINFMNG

Substitute the following value for the variable DBUPDINFMNG.

Note that this value changes depending on whether the multi-node function is used.

Value (kilobytes)

[Figure]

(i) Determining the variable RNGPREREADINF

Use the formulas shown below to determine the variable RNGPREREADINF. The formula to be used depends on the specification of the adb_sql_rngidx_preread operand in the server definition.

If NO is specified for the adb_sql_rngidx_preread operand, the variable RNGPREREADINF becomes 0.

■ When ALL is specified in the adb_sql_rngidx_preread operand

Formula (kilobytes)

[Figure]
Explanation of variables

uthd_num: Value specified for the adb_sys_uthd_num operand in the server definition

■ When range index names are specified in the adb_sql_rngidx_preread operand

Formula (kilobytes)

[Figure]
Explanation of variable

preread_rng_num: Number of range index names specified in the adb_sql_rngidx_preread operand

uthd_num: Value specified for the adb_sys_uthd_num operand in the server definition

(j) Determining the variable RNGPREREADHANDLE

Substitute the following value for the variable RNGPREREADHANDLE.

Value (kilobytes)

RNGPREREADHANDLE = 1

(k) Determining the variable MODA

Use the following formula to determine the value of variable MODA.

Formula (kilobytes)
MODA = 9,216 + ↑wrk_page_size ÷ 1,024↑

Explanation of variables

wrk_page_size

Page size of the work table DB area (bytes)

Determine the value as explained in Table 6‒3: DB area page size under (2) Determining the global buffer page requirement (for starting the HADB server).

(l) Determining the variable LSINF

Substitute the following value for the variable LSINF.

Value (kilobytes)

LSINF = 1

(m) Determining the variable DBHTRC

Use the following formula to determine the value of variable DBHTRC.

Formula (kilobytes)

[Figure]

Explanation of variables

RTHNUM

See the description of the variable RTHNUM in (a) Determining the variable SCI.

(n) Determining the variable LSTCMNINF

Use the following formula to determine the value of variable LSTCMNINF.

Formula (kilobytes)

[Figure]

Explanation of variables

max_users

Value specified for the adb_sys_max_users operand in the server definition

(o) Determining the variable LSTRTHDINF

Use the following formula to determine the value of variable LSTRTHDINF.

Formula (kilobytes)

[Figure]

Explanation of variables

RTHNUM

See the description of the variable RTHNUM in (a) Determining the variable SCI.

(p) Determining the variable PROC_STAINF

Use the following formula to determine the value of variable PROC_STAINF.

Formula (kilobytes)

[Figure]

Explanation of variables

max_users

Value specified for the adb_sys_max_users operand in the server definition

(q) Determining the variable SYNDICTINF

Substitute the following value for the variable SYNDICTINF.

Value (kilobytes)

[Figure]

(r) Determining the variable AUDINF

Use the following formula to determine the value of variable AUDINF. Add this value when the audit trail facility is enabled. Disabling the audit trail facility releases the value determined for variable AUDINF.

Formula (kilobytes)

AUDINF = 1 + PROC_AUDINFSZ

Explanation of variables

PROC_AUDINFSZ: Audit trail information

Use the following formula to determine the value:

Formula (kilobytes)

PROC_AUDINFSZ = 2 + (↑sql_text_size÷1,024↑)#1
             + (↑PARAM_INFO_SIZE÷1,024↑)#2
             + OBJECT_INFO_SIZE#3
             + system_info_size
#1

Add this value when executing an SQL statement.

#2

Add this value when executing an SQL statement that includes a dynamic parameter.

#3

Add this value when executing an SQL statement or a command.

sql_text_size

SQL text length (bytes)

PARAM_INFO_SIZE

Parameter storage area (bytes)

See the description of the variable PARAM_INFO_SIZE in (c) Determining the variable RTHD_EXESQLSZ under (2) Determining the real thread private memory requirement (during normal operation) in 6.3.4 Determining the memory requirement during normal operation.

OBJECT_INFO_SIZE

Object information (kilobytes)

Use the following formula to determine the value:

OBJECT_INFO_SIZE= 1 x obj_num×user_num
obj_num

Number of objects specified in the SQL statement or command

If ALL TABLES is specified in a GRANT statement or REVOKE statement, this value is the number of tables to which ALL TABLES applies.

user_num

Number of privilege grantees specified in the GRANT statement or REVOKE statement

If the SQL statement or command does not specify any privilege grantees, a value of 1 is used.

system_info_size

System information (kilobytes)

Use the following formula to determine the memory requirement when starting the HADB server:

system_info_size = ↑size-of-server-definition-file# ÷ 1,024↑
#

Specify the size of the server definition file in bytes.

Use the following formula to determine the memory requirement for situations other than HADB server startup:

  • When executing the adbclientdefmang command

    system_info_size = 2 x ↑size-of-client-management-definition-file# ÷ 1,024↑
    #

    Specify the size of the client management definition file in bytes.

  • Other than when executing the adbclientdefmang command

    system_info_size = 0

(s) Determining the variable CLMNZ

Substitute the following value for the variable CLMNZ.

Value (kilobytes)
CLMNZ = 5,120 + 1

To Page Top

(4) Determining the real thread private memory requirement (for starting the HADB server)

Use the following formula to determine the real thread private memory requirement (RTHD_STARTSZ) for starting the HADB server.

Formula (kilobytes)

[Figure]
#1

Add this value when you upgrade the HADB server version.

#2

Add this value when you use the multi-node function.

#3

Add this value when the audit trail facility is enabled.

Explanation of variables

RTI

Real thread management information

Use the following formula to determine its value.

Formula (kilobytes)

[Figure]
AIO

Asynchronous I/O management information

Use the following formula to determine its value.

Formula (bytes)

AIO = 32 × UTHNUM
UTHNUM

For details, see the description of the variable UTHNUM in (a) Determining the variable SCI under (3) Determining the process common memory requirement (for starting the HADB server).

DBI

Use the following formula to determine its value.

Formula (bytes)

DBI = 336 × UTHNUM
DICL

Substitute the following value.

Value (kilobytes)

[Figure]
DICL2

Substitute the following value.

Value (kilobytes)

[Figure]
RTHD_STAINF

Control information for statistical information

Use the following formula to determine its value.

Formula (kilobytes)

[Figure]
tables

Sum of the numbers of tables specified in all SQL statements that are executed in one transaction

max_sql_concurrent_exec_num

Maximum number of SQL statements to be executed at the same time during a transaction

MLTMNG

Multi-node function management information

Use the following formula to determine its value.

Formula (kilobytes)

[Figure]
authid_num

Total number of authorization identifiers specified for the adbclientmang operands in the client-managing definition

multi_node_num

Number of host names specified in the adb_sys_multi_node_info operand in the server definition

TRCMON

Monitor out thread management information for SQL tracing

Use the following formula to determine its value.

Formula (kilobytes)

[Figure]
#

Memory allocated when the SQL trace buffer is extended

RTHD_EXPSQLTRCSZ

Real thread private memory used when the SQL trace buffer is extended

Determine the value according to (i) Determining the variable RTHD_EXPSQLTRCSZ in (2) Determining the real thread private memory requirement (during normal operation) under 6.3.4 Determining the memory requirement during normal operation.

AUDTHDINF

Audit trail management information

Use the following formula to determine the value. Disabling the audit trail facility releases the value determined for variable AUDTHDINF.

Formula (kilobytes)

AUDTHDINF = ↑(272,631,408 + CTHNUM x 260,000) ÷ 1,024↑
CTHNUM

For details, see the description of the variable CTHNUM in (a) Determining the variable SCI under (3) Determining the process common memory requirement (for starting the HADB server).

To Page Top

(5) Determining the heap memory requirement (for starting the HADB server)

Use the following formula to determine the heap memory requirement (HEAP_STARTSZ) for starting the HADB server.

Formula (kilobytes)

HEAP_STARTSZ = 161 x UTHNUM x RTHNUM

Explanation of variables

UTHNUM

For details, see the description of the variable UTHNUM in (a) Determining the variable SCI under (3) Determining the process common memory requirement (for starting the HADB server).

RTHNUM

For details, see the description of the variable RTHNUM in (a) Determining the variable SCI under (3) Determining the process common memory requirement (for starting the HADB server).

To Page Top

All Rights Reserved. Copyright (C) 2012, 2020, Hitachi, Ltd.