The following formula is used to obtain the total size of all system log files.
Total size of all system log files (bytes) = (![]() ![]() ![]() |
pd_log_rec_leng = 1024: 1000
pd_log_rec_leng = 2048: 2000
pd_log_rec_leng = 4096: 4000
The following formula is used to obtain the amount of system log information that will be output.
Amount of system log information to be output (bytes) = ![]() ![]() ![]() ![]() ![]() + f |
Execution of UAP using the HiRDB library to implement a connection method that supports multi-threading and complies with X/Open, and use of the transaction transfer facility | Use of recovery-unnecessary front-end server | Formula |
---|---|---|
Used | Not used (cannot be used) | (![]() ![]() ![]() |
Not used | Used | 0 |
Not used | Not used | 2 x value of pd_log_rec_leng operand |
The system includes a front-end server that uses a recovery-unnecessary front-end server | pd_rpl_reflect_mode operand specification value | Formula |
---|---|---|
Yes | uap | Value of pd_log_rec_leng operand + ![]() ![]() ![]() |
server | ||
No | uap | |
server | 2 x value of pd_log_rec_leng operand |
Large amounts of system log information are output when the following SQLs are executed. Since system log file capacity might run short, execute these only after determining the amount of system log information that will be output. If your calculations indicate that system log file capacity will be insufficient, take the actions indicated below.
SQL statements that output large amounts of system log information | How to avoid running short of system log file capacity |
---|---|
CREATE INDEX, Method 1 (index definition) | Define an index that specifies EMPTY in its index option, and create the index using the database reorganization utility (pdrorg). When you create the index, specify pre-update log acquisition mode as the log acquisition mode. |
CREATE INDEX, Method 2 (index definition) CREATE INDEX, Method 3 (substructure index definition) | Execute the SQL code in no-log mode. When you execute one of the SQLs at left, a particularly large amount of system log information will be output. For this reason, we recommend running on no-log mode regardless of the amount of system log file capacity. For details about operation when UAPs or utilities are executed in the no-log mode, see the HiRDB Version 9 System Operation Guide. |
DROP SCHEMA (delete schema) | Individually delete the definitions shown below in the schema of the specified authorization identifier to reduce the amount of system log information that is output at once.
|