Notices

Preface

1. HiRDB Startup and Termination

1.1 Startup

1.1.1 Startup modes

1.1.2 Server machine where the pdstart command is executed

1.1.3 Automatic startup

1.1.4 Reduced activation (applicable to HiRDB parallel server configurations only)

1.1.5 Example (HiRDB normal startup)

1.1.6 Checking for startup completion

1.2 Termination

1.2.1 Termination modes

1.2.2 Server machine where the pdstop command is executed

1.2.3 Example (HiRDB normal termination)

1.2.4 Terminating HiRDB during OS shutdown

1.3 Special startup procedures

1.3.1 Startup procedure used to reinitialize a database (pdstart -i)

1.3.2 Startup procedure used in the event of an error in the master directory RDAREA (pdstart -r [-t])

1.3.3 Startup procedure used when the front-end server is in SUSPEND status due to an error in a data dictionary RDAREA (pdstart -a)

1.4 Startup and termination of a unit (applicable to HiRDB parallel server configurations only)

1.5 Startup and termination of a server (applicable to HiRDB parallel server configurations only)

1.6 Notes on startup

1.6.1 Notes on HiRDB startup

1.6.2 Notes on forced startup of HiRDB (or a unit)

1.6.3 Notes on HiRDB startup processing errors (applicable to HiRDB parallel server configurations only)

1.7 Notes on termination

1.7.1 Notes on HiRDB termination

1.7.2 Notes on planned termination, forced termination, and abnormal termination

1.8 Reducing the HiRDB startup processing time

2. Security Definition

2.1 About security

2.2 Setting user privileges

2.2.1 Granting the DBA privilege to users who manage user privileges

2.2.2 Granting the CONNECT privilege, schema definition privilege, and RDAREA usage privilege to users who create tables

2.2.3 Granting CONNECT and access privileges to users who access tables (database)

2.3 Revoking user privileges

2.4 Setting a referencing privilege for data dictionary tables

2.5 Facility for simple authentication of OS login users

2.5.1 Preparations for using the facility for simple authentication of OS login users

2.5.2 Using the facility for simple authentication of OS login users to connect to the HiRDB server

2.5.3 Application conditions for HiRDB password authentication and simple authentication of OS login users

2.5.4 Privileges that can be granted to simple authenticated users

2.5.5 Notes about using the facility for simple authentication of OS login users

3. Handling System Log Files

3.1 Basics

3.2 Unloading the system log

3.2.1 HiRDB single server configuration

3.2.2 HiRDB parallel server configuration

3.3 Operating without unloading the system log

3.3.1 HiRDB single server configuration

3.3.2 HiRDB parallel server configuration

3.4 Releasing checking of unload status

3.5 Procedures for manipulating system log files

3.5.1 Checking for files in swappable target status

3.5.2 When there is no file in swappable target status

3.5.3 Unloading the current file

3.5.4 Unloading a file in unload completed status

3.5.5 When the system log in a file in unload wait status is not needed

3.5.6 Changing a file's status

3.5.7 Increasing (or reducing) the system log file size during HiRDB operation

3.5.8 Adding a new system log file

3.5.9 Deleting a system log file

3.6 Status changes of system log files

3.7 Changing the system log file record length

3.7.1 Example 1 (system log unloading operation)

3.7.2 Example 2 (operation without unloading the system log)

3.8 Using the automatic log unloading facility

3.8.1 Overview of automatic log unloading facility

3.8.2 Environment setup

3.8.3 Application example 1 (using a single directory for unload log files)

3.8.4 Application example 2 (using two directories for unload log files)

3.8.5 Error handling

3.8.6 Notes on HiRDB termination

3.9 Monitoring the free area for system log files

3.9.1 What is monitoring the free area for system log files?

3.9.2 Environment setting

3.9.3 HiRDB processing when the percentage of free area falls below the warning value

3.9.4 Tasks performed by the HiRDB administrator when the percentage of free area falls below the warning value

3.9.5 Notes

3.9.6 Output of status information file for system log files (function for monitoring the free area)

3.10 Using the system log file automatic extension facility

3.10.1 The system log file automatic extension facility

3.10.2 Environment configuration

3.10.3 HiRDB processing during automatic extension

3.10.4 Actions to be taken by the HiRDB administrator when system log files cannot be automatically extended

3.10.5 Relationship of this facility with other facilities

3.10.6 Notes

3.10.7 Outputting the system log file status information file (automatic extension facility)

3.11 Identifying the unload log files necessary for database recovery

3.11.1 Acquiring information on the first unload log file to be specified (during backup acquisition)

3.11.2 Acquiring information on the last unload log file to be specified (during database recovery)

3.11.3 Rearranging the unload log files (creating a time-ordered list)

4. Handling Synchronization Point Dump Files

4.1 Basics

4.2 Setting the synchronization point dump interval

4.3 Procedures for manipulating synchronization point dump files

4.3.1 When the status of a synchronization point dump file has changed

4.3.2 When there are no overwrite enabled files

4.3.3 Increasing (or reducing) the synchronization point dump file size during HiRDB operation

4.3.4 Changing the file status

4.3.5 Adding a new synchronization point dump file

4.3.6 Deleting a synchronization point dump file

4.3.7 Obtaining the system log file corresponding to a synchronization point dump in file

4.3.8 Increasing the number of synchronization point dump file guaranteed-valid generations

4.4 Status changes of synchronization point dump files

5. Handling Status Files

5.1 Basics

5.2 Procedures for manipulating status files

5.2.1 When status files are swapped

5.2.2 When there are no spare files

5.2.3 Increasing (or reducing) the status file size during HiRDB operation

5.2.4 Changing the file status

5.2.5 Changing the current file

5.2.6 Adding a new status file

5.2.7 Deleting a status file

5.2.8 Checking the information in a status file

5.3 Status changes of status files

6. Backup Procedures

6.1 Backup

6.1.1 Basics

6.1.2 Optional items

6.2 Backup acquisition mode

6.3 RDAREAs to be backed up together

6.4 Examples of backup

6.4.1 Example 1 (Using the HiRDB Control Manager wizard to back up a system)

6.4.2 Example 2 (Using the HiRDB Control Manager wizard to back up individual RDAREAs)

6.4.3 Example 3 (backing up a system)

6.4.4 Example 4 (backing up a system)

6.4.5 Example 5 (backing up a system)

6.4.6 Example 6 (backing up a unit)

6.4.7 Example 7 (backing up a server)

6.4.8 Example 8 (backing up specified RDAREAs)

6.5 Acquiring a differential backup

6.5.1 Differential backup facility overview

6.5.2 Preparations for using the differential backup facility

6.5.3 Examples of using the differential backup facility

6.5.4 Creating an accumulation-differential backup

6.5.5 Referencing the history file for differential backups

6.5.6 Restoring a differential backup management file

6.6 Example of shell for backing up after synchronization point dump validation

6.7 Backup acquisition using backup-hold (backup without using the pdcopy command)

6.7.1 About backup-hold

6.7.2 Example 1 (using another product's backup facilities)

6.7.3 Example 2 (using the mirror disk facility)

6.8 Backup acquisition when the frozen update command (pddbfrz command) is used

6.8.1 Operation subject to the frozen update command

6.8.2 Operation of the frozen update command (pddbfrz command)

6.8.3 Operation example

6.8.4 Checking for files with full data pages

6.8.5 Manipulating user LOB RDAREAs for which the frozen update command has been executed

6.8.6 Relationship between RDAREAs and automatic extensions

6.8.7 Notes

7. Operation Without Acquiring a Database Update Log

7.1 Database update log acquisition modes

7.2 Procedure for executing a UAP or utility in the pre-update log acquisition mode

7.3 Procedure for executing a UAP or utility in the no-log mode

8. Obtaining the System Operating Environment (Monitoring the System Status)

8.1 Using the message log to check the system execution status

8.1.1 Referencing the message log (message log output destination)

8.1.2 Using the message log files

8.1.3 Selecting a message log output method (applicable only to a HiRDB parallel server configuration)

8.1.4 Suppressing message output to syslogfile

8.1.5 Changing the severity of the messages to be output to syslogfile

8.1.6 Suppressing output of information messages during utility execution

8.1.7 Improving the reliability of syslogfile and converting the character code (Linux edition only)

8.2 When a UAP or utility execution takes too long

8.3 When HiRDB startup or termination processing takes too long

8.4 Obtaining RDAREA status

8.5 Obtaining shared memory utilization status

8.6 In the event of deadlock

8.6.1 Basics

8.6.2 Deadlock information that is output

8.6.3 Timeout information that is output

8.6.4 Resource types and resource information

8.6.5 Interpreting resource information

8.7 In the event of a shortage of locked resources management tables

8.8 Monitoring UAP status (skipped effective synchronization point dump monitoring facility)

8.9 Output of warning information about the time required for SQL execution (SQL runtime warning output facility)

8.9.1 Overview of the SQL runtime warning output facility

8.9.2 Using the SQL runtime warning output facility

8.9.3 Information output to the SQL runtime warning information file

8.9.4 Output of the KFPA20009-W message

8.9.5 Notes

8.10 Monitoring the execution time of UAPs and utilities (reducing the effects of nonresponding programs)

8.11 Monitoring resource utilization factors

8.12 Monitoring the status of server processes (message queue monitoring facility)

8.13 Monitoring the number of times server processes terminate abnormally (abnormal termination monitoring facility)

8.14 Monitoring the memory size of server processes (facility for monitoring the memory size of server processes)

8.15 Method for verifying that rollback processing is taking place

8.15.1 Execution result of the pdls -d trn -a command

8.15.2 KFPS02235-I message

8.15.3 Rollback completion criterion

8.15.4 Notes

9. Modifying the System Operating Environment

9.1 Modifying HiRDB system definitions

9.2 Modifying HiRDB system definitions while HiRDB is running (system reconfiguration command)

9.2.1 Modification procedure

9.2.2 Notes on changing operand specification values

9.2.3 Notes on executing the system reconfiguration command

9.2.4 HiRDB status after the system reconfiguration command has executed

9.2.5 Relationship with other facilities

9.2.6 Actions to take when an error occurs

9.3 Adding, modifying, and deleting global buffers while HiRDB is running (dynamic updating of global buffers)

9.3.1 Overview of dynamic updating of global buffers

9.3.2 Application examples

9.4 Changing the number of server processes

9.5 Handling an increase in the number of users

9.6 Accommodating clients that cannot connect to HiRDB (connection frame guarantee facility for client groups)

9.7 Specifying a range of port numbers for use in communication processing

9.8 Changing the host name

9.9 Changing the deadlock priority value for commands

9.9.1 Deadlock priority value for commands

9.9.2 Environment assignment

9.9.3 Operation method

9.10 Partitioning the lock pool

9.11 Changing the transaction recovery message queue size

9.12 Changing the time used by the OS

9.12.1 Methods for moving the time back

9.12.2 Moving the time back using method 1

9.12.3 Moving the time back using method 2

9.12.4 Restoring the database using method 2 in the event of an error occurrence after the time was moved back

9.12.5 Restrictions on using method 2 to move back the time

9.12.6 Notes on using method 2 to move back the time

10. Handling HiRDB File System Areas

10.1 Obtaining information about a HiRDB file system area

10.2 Creating (initializing) a HiRDB file system area

10.3 Backing up a HiRDB file system area

10.4 Restoring a HiRDB file system area

10.5 Deleting a HiRDB file system area

10.6 Facility for taking a unit down when a file access error is detected

10.7 Using the HDP facility to virtualize HiRDB file system areas

10.7.1 About the HDP facility

10.7.2 How to efficiently virtualize HiRDB file system areas

10.7.3 Operation for using storage efficiently

11. Modifying the System Configuration

11.1 Adding a unit

11.1.1 Adding a unit while HiRDB is running

11.1.2 Adding a unit while HiRDB is stopped

11.2 Removing a unit

11.2.1 Removing a unit while HiRDB is running

11.2.2 Removing a unit while HiRDB is stopped

11.3 Moving a unit

11.3.1 Moving a unit while HiRDB is running

11.3.2 Moving a unit while HiRDB is stopped

11.4 Adding a server

11.4.1 Adding a server while HiRDB is running

11.4.2 Adding a server while HiRDB is stopped

11.5 Removing a server

11.5.1 Removing a server while HiRDB is running

11.5.2 Removing a server while HiRDB is stopped

11.6 Moving a server

11.6.1 Moving a server while HiRDB is running

11.6.2 Moving a server while HiRDB is stopped

11.7 Migrating a HiRDB single server configuration to a HiRDB parallel server configuration

11.7.1 Preparations for migration

11.7.2 Migration procedure

11.7.3 Points to be noted about migrating multiple user RDAREAs to different back-end servers

11.8 Migrating back-end servers for load balancing

11.8.1 Back-end server load balancing based on a scenario

11.8.2 Prerequisites and conditions for the target jobs

11.8.3 Using a scenario

11.8.4 Back-end server configuration examples

11.8.5 Preparations related to HiRDB

11.8.6 Back-end server load balancing performed by the user

12. Migrating Resources Between Systems

12.1 Migrating a table to another HiRDB system

12.1.1 Migrating a table to another HiRDB system

12.1.2 Method that migrates table definition information and table data simultaneously

12.1.3 Method that migrates table definition information and table data separately

12.1.4 Example 1: Migrating table definition information and table data simultaneously

12.1.5 Example 2: Migrating table definition information and table data separately for each table

12.1.6 Example 2: Migrating tables of a schema

12.1.7 Example of a control statements file when migrating tables to a different schema

12.1.8 Example 4: Migrating a table containing binary data to a system that has a different endian format

12.1.9 Example 5: Migrating table data after expanding the column definition size of fixed-size character data

12.1.10 Actions to take when an error occurs during import

12.2 Migrating a stored procedure to another HiRDB system

12.2.1 Preparations for migrating a stored procedure to another HiRDB system

12.2.2 Example

13. Handling Tables

13.1 Checking table storage efficiency

13.1.1 Executing the database condition analysis utility on a regular basis

13.1.2 Messages indicating poor data storage efficiency

13.1.3 When expected retrieval performance cannot be achieved

13.2 Reorganizing a table

13.2.1 Table reorganization

13.2.2 Execution units for table reorganization

13.2.3 Selecting an update log acquisition mode for a database

13.2.4 Before reorganizing a table

13.3 Reorganizing a table (examples)

13.3.1 Example 1: Reorganizing a table (HiRDB single server configuration)

13.3.2 Example 2: Reorganizing a table (HiRDB parallel server configuration)

13.3.3 Example 3: Reorganizing an RDAREA

13.3.4 Example 4: Reorganizing a schema

13.3.5 Example 5: Reorganizing a table in which a LOB column is defined

13.3.6 Example 6: Reorganizing data dictionary tables

13.3.7 Example 7: Reorganizing in no-log mode

13.3.8 Example 8: Reorganizing a table in which an abstract data type is defined

13.4 Predicting table reorganization time (facility for predicting reorganization time)

13.4.1 Predicting reorganization time

13.4.2 Preparations for using the facility for predicting reorganization time

13.4.3 Operational flow

13.4.4 Notes on using the facility for predicting reorganization time

13.4.5 Stopping reorganization time prediction

13.4.6 Customizing reorganization time prediction

13.5 Deleting data from a table

13.6 Adding a column

13.6.1 Preparations for adding a column

13.6.2 Example 1: Adding a column to a table without the FIX attribute

13.6.3 Example 2: Adding a LOB column

13.6.4 Example 3: Adding an abstract data type column

13.6.5 Example 4: Adding a column to a table with the FIX attribute (defining a reserved column)

13.6.6 Example 5: Adding a column to a table with the FIX attribute (unloading in DAT format)

13.6.7 Example 6: Adding a column to a table with the FIX attribute (unloading in binary format)

13.7 Deleting a column

13.7.1 Example: Deleting a column

13.8 Modifying a table's definition

13.8.1 Example: Changing the data size of a column

13.9 Changing a table name or column name

13.9.1 Example 1: Changing a table name

13.9.2 Example 2: Changing a column name

13.10 Increasing the number of table row partitions

13.10.1 Example 1: Increasing the number of row partitions in a table with key range partitioning

13.10.2 Example 2: Increasing the number of row partitions in a table with flexible hash partitioning

13.10.3 Example 3: Increasing the number of row partitions in a table with FIX hash partitioning

13.11 Increasing the number of table row partitions (using the hash facility for hash row partitioning)

13.11.1 Overview of the hash facility for hash row partitioning

13.11.2 Preparations for using the hash facility for hash row partitioning

13.11.3 Example: Increasing the number of row partitions in a rebalancing table

13.11.4 Using the rebalancing utility (when table rebalancing takes time)

13.11.5 Notes on a table with FIX hash partitioning

13.12 Changing a table's partitioning storage conditions

13.12.1 Purpose of changing partitioning storage conditions

13.12.2 Facilities used to change partitioning storage conditions

13.12.3 Prerequisites

13.12.4 How to change partitioning storage conditions (in the case of boundary value specification)

13.12.5 Splitting an RDAREA (in the case of boundary value specification)

13.12.6 Combining RDAREAs (in the case of boundary value specification)

13.12.7 How to change partitioning storage conditions (in the case of storage condition specification)

13.12.8 Splitting an RDAREA (in the case of storage condition specification)

13.12.9 Combining RDAREAs (in the case of storage condition specification)

13.12.10 Changing the partitioning storage conditions (in the case of matrix partitioning)

13.12.11 Partitioning an RDAREA (matrix partitioning)

13.12.12 Combining RDAREAs (matrix partitioning)

13.12.13 Relationship with other facilities

13.13 Operation when changing a table's partitioning storage conditions

13.13.1 Examples (in the case of boundary value specification)

13.13.2 Examples (in the case of storage condition specification)

13.13.3 Examples (matrix partitioning)

13.13.4 Re-registering the data

13.13.5 Reusing RDAREAs

13.13.6 Examples of the database reorganization utility and database load utility

13.13.7 Splitting or combining a table containing a non-partitioning key index

13.13.8 Splitting or combining when an index is incomplete

13.13.9 Checking the number of items of data following splitting or combining

13.13.10 Operation when an error occurs

13.13.11 Handling when referential constraint and check constraint are used

13.14 Changing the hash function

13.14.1 Example 1: Flexible hash partitioning

13.14.2 Example 2: FIX hash partitioning

13.15 Changing a table's partitioning definition

13.15.1 Example 1: Changing from key range partitioning to hash partitioning and changing the partitioning key column

13.15.2 Example 2: Changing from hash partitioning to key range partitioning

13.15.3 Example 3: Allocating a different RDAREA each month (when matrix partitioning is not used)

13.15.4 Example 4: Allocating a different RDAREA each month (in the case of matrix partitioning)

13.15.5 Example 5: Allocating a different RDAREA each day (in a case in which matrix partitioning is not used)

13.15.6 Example 6: Allocating a different RDAREA each day (in the case of matrix partitioning)

13.16 Migrating data to another table

13.16.1 Example 1: Migrating data to another table

13.16.2 Example 2: Migrating data containing XML-type columns by table

13.16.3 Specification examples of column structure information files

13.17 Deleting a table

13.18 Deleting a schema

13.19 Deleting an abstract data type

13.20 Creating a definition SQL from an existing table

13.21 Managing a list (narrowed search)

13.22 Standardizing spaces in table data

13.22.1 Overview of space conversion facility

13.22.2 Setting the space conversion level

13.22.3 Standardizing space characters in a table

13.23 Converting the sign portion of the decimal type

13.23.1 Overview of the facility for conversion to a decimal signed normalized number

13.23.2 Normalizing existing data

14. Handling Indexes

14.1 Improving index storage efficiency (index reorganization)

14.1.1 Overview of index reorganization

14.1.2 Example 1: Reorganizing an index

14.1.3 Actions when an error occurs during index reorganization

14.1.4 Example 2: When an RDAREA shortage occurs during index reorganization (execution in a mode other than no-log mode)

14.1.5 Example 3: When an RDAREA shortage occurs during index reorganization (execution in no-log mode)

14.2 Defining an index for a table that contains data

14.3 Changing an index name

14.4 Deleting an index

14.5 Creating a definition SQL from an existing index

14.6 Reducing the number of index page splits (unbalanced index split)

14.7 Error handling during batch index creation

14.7.1 Example of recovery when reloading (data loading) was performed in the log acquisition mode or the pre-update log acquisition mode

14.7.2 Example of recovery when reloading (data loading) was performed in the no-log mode (when the RDAREA storing the index contains no other tables or indexes)

14.7.3 Example of recovery when reloading (data loading) was executed in the no-log mode (when the RDAREA storing the index contains other tables or indexes)

14.7.4 Example of recovery in the event of an error on the disk that contains the index storage RDAREA

14.8 Delayed batch creation of a plug-in index

14.8.1 Delayed batch creation of a plug-in index

14.8.2 Environment setup

14.8.3 Procedure during UAP execution

14.8.4 Notes

14.8.5 Error handling procedures

15. Handling RDAREAs

15.1 RDAREA space shortage

15.2 Creating an RDAREA (RDAREA addition)

15.2.1 Before adding an RDAREA

15.2.2 Example

15.3 Increasing the size of an RDAREA (RDAREA expansion)

15.3.1 Before expanding an RDAREA

15.3.2 Example

15.4 Modifying the size or attributes of an RDAREA (RDAREA reinitialization)

15.4.1 Before reinitializing an RDAREA

15.4.2 Example 1 (index is defined)

15.4.3 Example 2 (index is defined)

15.4.4 Example 3 (LOB column is defined)

15.4.5 Example 4 (LOB column is defined)

15.4.6 Example 5 (abstract data type is defined)

15.4.7 Example 6 (abstract data type is defined)

15.4.8 Example 7 (using a UAP, all RDAREAs associated with a table are reinitialized, and data is recovered)

15.4.9 Example 8 (using a UAP, all RDAREAs associated with a table are reinitialized, and data is recovered)

15.4.10 Example 9 (changing the disk layout for RDAREAs)

15.5 Modifying an RDAREA name (RDAREA attribute modification)

15.5.1 Before modifying an RDAREA name

15.5.2 Example

15.5.3 Recovering an RDAREA that was not backed up during RDAREA name modification

15.6 Modifying an RDAREA opening trigger attribute (RDAREA modification)

15.6.1 Before changing the RDAREA opening trigger attribute

15.6.2 Example

15.7 Deleting an RDAREA

15.7.1 Before deleting an RDAREA

15.7.2 Example

15.8 RDAREA automatic extension

15.8.1 Automatic extension of an RDAREA

15.8.2 Notes on applying RDAREA automatic extension

15.8.3 Method that automatically expands the HiRDB file system area

15.8.4 Method that expands HiRDB files in the HiRDB file system area

15.8.5 Example (method that automatically expands the HiRDB file system area)

15.8.6 Example (method that expands HiRDB files in the HiRDB file system area)

15.9 Moving an RDAREA (RDAREA migration)

15.9.1 Before moving RDAREAs

15.9.2 Example 1 (Moving RDAREAs to the back-end server on a new server machine)

15.9.3 Example 2 (Moving RDAREAs to a back-end server in a different unit)

15.9.4 Example 3 (Moving RDAREAs to a different back-end server in the same unit)

15.9.5 Example 4 (Moving RDAREAs containing a row-partitioned table)

15.9.6 Example 5 (Moving inner replica RDAREAs)

15.9.7 Example 6 (Moving RDAREAs containing an abstract data type)

15.10 Moving HiRDB file system areas that store RDAREAs

15.10.1 Before moving HiRDB file system areas

15.10.2 Example

15.11 Re-using used free pages and used free segments

15.11.1 Page and segment status

15.11.2 Reusing used free pages

15.11.3 Reusing used free segments

15.12 Facility for taking a unit down when a physical error is detected

16. Handling Stored Procedures and Stored Functions

16.1 Before creating (registering) stored procedures or stored functions

16.2 Creating (registering) a stored procedure or stored function

16.3 Re-creating an invalidated stored procedure or stored function

16.4 Deleting a stored procedure or stored function

16.5 Creating a definition SQL from an existing stored procedure

17. Using Java Stored Procedures and Java Stored Functions

17.1 Overview of Java stored procedures and Java stored functions

17.2 System configuration for using Java stored procedures and Java stored functions

17.3 Environment setup

17.4 JAR file operations

17.4.1 When an error occurs in a JAR file

17.4.2 When the server configuration is modified (HiRDB parallel server configuration only)

18. Using C Stored Procedures and C Stored Functions

18.1 Environment setup for using C stored procedures and C stored functions

18.1.1 Flow for creating an execution environment for C stored procedures or C stored functions

18.1.2 Registering a new C library file

18.1.3 Re-registering the C library file

18.1.4 Deleting a C library file

18.2 Action to take when an error occurs in a C library file

19. Using Optimization Information

19.1 About optimizing information

19.1.1 Overview of optimizing information

19.1.2 Registering optimizing information

19.1.3 Contents of optimizing information

19.1.4 Optimizing information collection levels

19.2 Using optimizing information

19.2.1 Collecting and registering optimizing information

19.2.2 Updating optimizing information

19.2.3 Restoring optimizing information

19.2.4 Deleting optimizing information

19.3 Using a parameter file that contains optimized information

19.3.1 About parameter files that contain optimized information

19.3.2 Registering optimizing information by using a parameter file that contains optimized information

19.3.3 Saving optimizing information to a parameter file that contains optimized information

19.4 Notes on using optimizing information

19.4.1 Using a parameter file that contains optimized information after table and index definitions are modified

19.4.2 Using pdgetcst after optimizing information is saved, and restoring optimizing information

19.4.3 If an error occurs while registering, updating, or deleting optimizing information

20. Error Handling Procedures

20.1 HiRDB processing and the HiRDB administrator's action in the event of an error

20.1.1 Actions to be taken by the HiRDB administrator when an error occurs

20.1.2 Information collected by HiRDB when an error occurs

20.1.3 HiRDB processing in the event of an error

20.1.4 Actions to take when an error occurs in a server process

20.1.5 Information inherited during a HiRDB restart

20.1.6 Facility for changing the process-down message when a transaction is canceled

20.1.7 Facility for acquiring global buffer control information traces

20.2 When a UAP does not execute correctly

20.3 When operation commands do not execute correctly

20.3.1 Actions to be taken when operation commands will not execute

20.3.2 Actions to be taken when an operation command results in a timeout while waiting for a response

20.4 When HiRDB does not start

20.4.1 When HiRDB does not start normally

20.4.2 When HiRDB does not restart

20.4.3 Actions to be taken in the event of an error in the master directory RDAREA

20.4.4 Actions to be taken in the event of other errors

20.5 When HiRDB does not terminate

20.6 Handling of system log file errors

20.6.1 Actions to be taken in the event of an error in the current file

20.6.2 Actions to be taken when HiRDB Datareplicator is being used

20.6.3 Actions to be taken when a HiRDB (unit) cannot be restarted due to an error in both versions of the current file

20.7 Handling of synchronization point dump file errors

20.8 Handling of status file errors

20.8.1 Actions to be taken in the event of an error in the current file

20.8.2 Procedure for starting a HiRDB (unit) while there is an erroneous status file

20.8.3 Actions to be taken when a HiRDB (unit) cannot be restarted due to an error in both versions of the current file

20.9 Handling of errors in files other than system files

20.9.1 Errors in the HiRDB system definitions file

20.9.2 Errors in the message log file

20.9.3 Errors in the statistics log file

20.9.4 Errors in the data linkage file (HiRDB Datareplicator)

20.10 When the OS terminates abnormally

20.11 Handling of errors while linked to an OLTP system

20.11.1 Actions to be taken when a communication error occurs while HiRDB is linked to an OLTP system

20.11.2 Actions to be taken when a transaction is placed in FORGETTING status due to an error

20.11.3 Actions to be taken when transactions remain resident due to inactivity of a unit with a front-end server

20.12 Handling of communication errors, CPU errors, and power failures

20.12.1 Handling of communication errors

20.12.2 Handling of CPU errors

20.12.3 Handling of a power failure

20.13 When HiRDB cannot be terminated because a user is still connected

20.13.1 Corrective procedure

20.13.2 Connected user data file and connected user details file

20.14 Actions when there is an undetermined transaction

20.14.1 Forcing determination of uncompleted transactions

20.14.2 Performing transaction determination manually on undetermined transactions

20.15 Handling of reduced activation (HiRDB parallel server configurations only)

20.16 Handling of disk errors

20.17 When a HiRDB (unit) terminates abnormally due to a system log file shortage

20.17.1 Unit-restarting procedure (with priority given to restarting the unit)

20.17.2 Unit-restarting procedure (restarting the unit after adding a system log file)

20.17.3 Unit-restarting procedure (restarting the unit after identifying the cause)

20.17.4 Unit-restarting procedure (after the cause of the system log file shortage has been identified)

20.17.5 Changing a system log file to unloaded status

20.17.6 Determining the number of records necessary for unit restart

20.17.7 Adding system log files

20.17.8 Deleting the system log files that were added

20.17.9 Action to take when there are system log files that are in extracting status

20.17.10 Actions to take after eliminating the system log file shortage

20.18 When a utility terminates abnormally during execution of a reorganization with synchronization points set

20.18.1 Overview of actions

20.18.2 Example

20.18.3 Actions to be taken when a utility terminates abnormally before unload data files have been consolidated (HiRDB parallel server configurations only)

20.18.4 Notes

20.19 Actions when page destruction in an RDAREA is detected

20.19.1 Causes of page destruction

20.19.2 Actions to be taken

20.20 Actions to take when an RDAREA I/O error occurs

20.21 Checking the transaction completion type when an error occurs during commit processing (HiRDB parallel server configurations only)

20.22 Actions to take when an error occurs while a local buffer is being used to update a shared table (HiRDB parallel server configurations only)

20.23 Actions to take when an error occurs in the system manager unit

20.24 Actions to take when a mismatch occurs between the original and the mirror duplicate

20.25 Recovery of HiRDB directory

20.25.1 When installation directory is available

20.25.2 When installation directory is not available

20.25.3 When a backup is available for the disk on which the HiRDB directory is located

20.26 Handling errors in the HiRDB file system areas

20.26.1 Unmanageable files and unreferenceable areas

20.26.2 Corruption of the area management information (applicable to HiRDB version 07-02 and earlier)

21. Database Recovery Procedures

21.1 Overview of database recovery

21.1.1 Database recovery point

21.1.2 Relationship to the backup acquisition mode

21.1.3 Relationship to the log acquisition mode

21.1.4 Notes on recovery of various types of RDAREAs

21.1.5 Same log reuse check

21.1.6 For users of 64-bit-mode HiRDB

21.2 Recovering a database to the point at which a backup was made

21.2.1 Example 1: Using the HiRDB Control Manager wizard to recover all RDAREAs

21.2.2 Example 1: Recovering all RDAREAs

21.2.3 Example 2: Recovering specified RDAREAs

21.2.4 Example 3: Recovering specified RDAREAs (including the master directory RDAREA)

21.3 Recovering a database to the most recent synchronization point

21.3.1 Example 1: Recovering all RDAREAs

21.3.2 Example 2: Using a HiRDB Control Manager wizard to recover specified RDAREAs

21.3.3 Example 2: Recovering specified RDAREAs

21.3.4 Example 3: Recovering specified RDAREAs (including the master directory RDAREA)

21.3.5 Example 4: Recovering specified RDAREAs (when operation without unloading system log is used)

21.4 Database recovery using the differential backup facility

21.4.1 Example 1: Recover to the most recent differential backup acquisition point

21.4.2 Example 2: Recover to the most recent synchronization point

21.4.3 Recovery when a differential backup management file is not available

21.5 Using a backup from another HiRDB system to recover a database

21.5.1 Example (migrating a backup acquired in HiRDB system A in a test environment to HiRDB system B in an actual operating environment)

21.6 Recovery procedure when the backup was not made with the pdcopy command

21.6.1 Example 1: Recovering all RDAREAs to the point at which a backup was made

21.6.2 Example 2: Recovering specified RDAREAs to the point at which a backup was made

21.6.3 Example 3: Recovering all RDAREAs to the most recent synchronization point

21.6.4 Example 4: Recovering specified RDAREAs

21.6.5 Example 5: Recovering the master directory RDAREA only

22. Obtaining Tuning Information

22.1 Collecting tuning information from the statistics log

22.1.1 Tuning information that can be collected from the statistics log

22.1.2 Preparing for collecting tuning information

22.1.3 Collecting tuning information

22.1.4 Shell script for creating unload statistics log files at a specified server machine

22.1.5 Accessing HiRDB from an application

22.2 Collecting tuning information from the system log

22.3 Using the database condition analysis utility to collect tuning information

23. Tuning

23.1 Tuning global buffer pools

23.1.1 Using the pdbufls command to collect statistical information

23.1.2 Using the statistics analysis utility to collect statistical information

23.2 Tuning deferred write processing

23.3 Tuning the synchronization point processing time when deferred write processing is used

23.3.1 Tuning procedure

23.3.2 How to interpret statistical information about deferred write processing

23.3.3 How to reduce the synchronization point processing time

23.4 Tuning the synchronization point dump interval

23.5 Tuning buffer lengths

23.5.1 Tuning the buffer length for table definition information

23.5.2 Tuning the buffer length for view analysis information

23.5.3 Tuning the buffer length for user privilege information

23.5.4 Tuning the buffer length for SQL objects

23.5.5 Tuning the buffer length for user-defined type information

23.5.6 Tuning the buffer length for routine definition information

23.5.7 Tuning the buffer length for registry information

23.6 Tuning the number of processes

23.6.1 Tuning the maximum number of active processes

23.6.2 Tuning the number of resident processes

23.6.3 Tuning the number of asynchronous READ processes

23.7 Tuning indexes

23.8 Tuning the database

23.9 Tuning SQLs

23.10 Tuning the system's internal processing

23.11 Tuning the sector count of a log input buffer for rollback

24. Using the Security Audit Facility

24.1 Overview of the security audit facility

24.1.1 About the security audit facility

24.1.2 Triggers for collecting audit trails

24.1.3 Examples of audit trail collection

24.1.4 Information collected in an audit trail

24.1.5 Accessing an audit trail

24.1.6 System configuration requirements

24.1.7 Audited events

24.1.8 Facility for automatically loading audit trail table data

24.2 Information output to an audit trail file

24.3 Audit trail output patterns

24.3.1 Output patterns during privilege checking

24.3.2 Output patterns at event termination

24.3.3 Relationships among audit trails

24.4 Environment settings

24.4.1 Security audit facility operand specifications

24.4.2 Creation of the HiRDB file system area for the audit trail files

24.4.3 Auditor registration, creation of the RDAREA to store the audit trail table, and creation of the audit trail table

24.4.4 Audit event definition

24.5 Operating procedure

24.5.1 Actions performed by the HiRDB administrator

24.5.2 Actions performed by the auditor

24.5.3 Operation using the facility for automatically loading audit trail table data

24.6 Operation of audit trail files

24.6.1 Creation of audit trail files

24.6.2 Status of audit trail files

24.6.3 Swapping of audit trail files

24.7 Recording data in the audit trail table

24.7.1 Example 1: Data loading from specified audit trail files

24.7.2 Example 2: Data loading from all audit trail files in the HiRDB file system area

24.7.3 Procedure when an error occurs during data loading

24.8 Audit trail table columns

24.9 Narrowing the audit trails

24.10 Audit trail file error handling

24.11 Actions to take when an error occurs while the facility for automatic loading is being used

24.12 Linkage with other facilities

24.13 Audit trail record items (during privilege checking)

24.14 Audit trail record items (at event termination)

24.15 Audit trail output destination unit during utility execution (HiRDB parallel server configurations only)

24.16 Notes on version upgrading

25. Using the Connection Security Facility

25.1 Overview of the connection security facility

25.1.1 About the connection security facility

25.1.2 Password character string restrictions

25.1.3 Limit on the number of consecutive certification failures

25.2 Setting password character string restrictions

25.3 Changing a password character string restriction

25.3.1 Special notes on changing password character string restrictions

25.3.2 Procedure for changing a password character string restriction

25.4 Releasing the password-invalid account lock state

25.4.1 Releasing individual users from password-invalid account lock state

25.4.2 Releasing all users from password-invalid account lock state

25.5 Checking for users who will be placed in password-invalid account lock state

25.6 Privilege granting or revocation for users in password-invalid account lock state

25.7 Canceling the password character string restrictions

25.8 Notes on using the security audit facility

25.9 Setting and canceling the limit on number of consecutive certification failures

25.9.1 Setting a new limit on the number of consecutive certification failures

25.9.2 Canceling the limit on the number of consecutive certification failures

25.9.3 Changing the limit on the number of consecutive certification failures

25.9.4 Checking the permitted number of consecutive certification failures and the account lock period

25.10 Checking for users in consecutive certification failure account lock state

25.11 Releasing consecutive certification failure account lock state

25.12 Notes on using the connection security facility

25.12.1 Releasing a double lock

25.12.2 Notes on restoring a dictionary RDAREA

26. Using the System Switchover Facility

26.1 Overview of the system switchover facility

26.1.1 System switchover facility (standby system switchover facility)

26.1.2 Standby system switchover facility

26.1.3 Standby-less system switchover facilities

26.1.4 Application criteria for the system switchover facilities

26.1.5 Cluster software products supported by HiRDB

26.2 Configuring a standby system switchover system (monitor mode)

26.2.1 System configuration examples

26.2.2 IP address configuration examples

26.2.3 Handling of host names depending on whether IP addresses are inherited

26.2.4 HiRDB preparations

26.2.5 HA Monitor preparations

26.2.6 MC/ServiceGuard preparations

26.2.7 VERITAS Cluster Server preparations

26.2.8 Sun Cluster preparations

26.2.9 HACMP preparations

26.2.10 PowerHA preparations

26.2.11 ClusterPerfect preparations

26.2.12 LifeKeeper preparations

26.3 Configuring a standby system switchover system (server mode)

26.3.1 System configuration examples

26.3.2 IP address configuration examples

26.3.3 Handling of host names depending on whether IP addresses are inherited

26.3.4 HiRDB preparations

26.3.5 HA Monitor preparations

26.3.6 Preparations for cluster software products other than HA Monitor

26.3.7 Hitachi HA Toolkit Extension preparations

26.4 Configuring a standby-less system switchover (1:1) system

26.4.1 System configuration examples

26.4.2 IP address configuration examples

26.4.3 HiRDB preparations

26.4.4 HA Monitor preparations

26.4.5 Preparations for cluster software products other than HA Monitor

26.4.6 Hitachi HA Toolkit Extension preparations

26.5 Configuring a standby-less system switchover (effects distributed) system

26.5.1 System configuration examples

26.5.2 HiRDB preparations

26.5.3 HA Monitor preparations

26.5.4 Preparations for cluster software products other than HA Monitor

26.5.5 Hitachi HA Toolkit Extension preparations

26.6 Standby system switchover (monitor mode) operation

26.6.1 Differences in the HiRDB operating procedures

26.6.2 Planned system switchover

26.6.3 Grouped system switchover

26.6.4 Operating procedures after a system switchover

26.6.5 Actions the HiRDB administrator takes when an error occurs

26.6.6 Notes on using the standby system switchover facility (monitor mode)

26.6.7 System switchover when an error other than a server failure occurs

26.6.8 Actions to take when a stopped unit prevents switching of the system manager unit

26.7 Standby system switchover (server mode) operation

26.7.1 Differences in the HiRDB operating procedures

26.7.2 Planned system switchover

26.7.3 Grouped system switchover

26.7.4 Operating procedures after a system switchover

26.7.5 Actions the HiRDB administrator takes when an error occurs

26.7.6 Notes on using the standby system switchover facility (server mode)

26.7.7 Reducing the system switchover time (user server hot standby, rapid system switchover facility)

26.7.8 System switchover when an error other than a server failure occurs

26.7.9 Notes on system switchovers for the system manager unit

26.7.10 Transaction queuing facility (for the rapid system switchover facility only)

26.8 Standby-less system switchover (1:1) operation

26.8.1 Differences in the HiRDB operating procedures

26.8.2 Planned system switchover

26.8.3 Grouped system switchover

26.8.4 Operating procedures after a system switchover

26.8.5 Actions the HiRDB administrator takes when an error occurs

26.8.6 Notes on using the standby-less system switchover (1:1) facility

26.8.7 System switchover when an error other than a server failure occurs

26.8.8 Transaction queuing facility

26.9 Standby-less system switchover (effects distributed) operation

26.9.1 Differences in the HiRDB operating procedures

26.9.2 Planned system switchover

26.9.3 Grouped system switchover

26.9.4 Operating procedures after a system switchover

26.9.5 Actions the HiRDB administrator takes when an error occurs

26.9.6 Notes on using the standby-less system switchover (effects distributed) facility

26.9.7 System switchover when an error other than a server failure occurs

26.9.8 Transaction queuing facility

27. Using the Facility for Monitoring MIB Performance Information

27.1 Overview of the facility for monitoring MIB performance information

27.1.1 About the facility for monitoring MIB performance information

27.1.2 Objectives of the facility for monitoring MIB performance information

27.1.3 MIB definition file

27.1.4 MIB environment definition file

27.2 System configuration

27.3 Environment setup

27.4 MIB definition file

27.5 Server status table (hirServerStatusTable)

27.6 Work table HiRDB file system area table (hirFileSystemTable)

27.7 RDAREA table (hirRdareaStatusTable)

27.8 RDAREA details table (hirRdareaDetStatusTable)

27.9 Global buffer table (hirBufferStatusTable)

27.10 HiRDB file system area (RDAREAs) table (hirRdareaFileTable)

27.11 SYS statistics table (hirStatisInfSysTable)

27.12 Disk usage

28. Performance Trace Facility

28.1 About the performance trace facility

28.1.1 Processes targeted by the performance trace facility

28.1.2 Settings for collecting performance trace information

28.1.3 Using the performance trace information file

28.1.4 Acquiring performance trace information when linked with Hitachi Application Server

28.2 Procedure for viewing performance trace information

28.2.1 Collected content of performance trace information

28.3 Notes

28.4 Details about performance trace information and collection points

28.4.1 Details about performance trace information and the collection points during execution of SQL code

28.4.2 Details about performance trace information and the collection points during utility execution

29. Configuring and Operating HiRDB With a Batch Job Distributed Execution System

29.1 Batch job distributed execution systems and HiRDB

29.1.1 System configuration example that uses a batch job distributed execution system with HiRDB

29.1.2 Parallel execution of batch jobs by adding units to HiRDB

29.2 Operating procedure for a batch job distributed execution system

29.3 Configuring HiRDB

29.3.1 Configuring a base unit

29.3.2 Configuring a HiRDB expansion unit

29.4 Starting HiRDB and HiRDB expansion units

29.4.1 Starting HiRDB

29.4.2 Starting a HiRDB expansion unit

29.5 Terminating HiRDB expansion units and HiRDB

29.5.1 Terminating HiRDB expansion units

29.5.2 Terminating HiRDB

29.6 Troubleshooting

29.7 Notes and limitations

29.7.1 Notes

29.7.2 Limitations

Appendixes

A. Q&A

A.1 System log files

A.2 Synchronization point dump files

A.3 Status files

A.4 Errors

A.5 Tables and indexes

A.6 HiRDB startup

A.7 HiRDB termination

A.8 Performance

A.9 Backup

A.10 RDAREA recovery

A.11 Other

B. Operations When Using a DVD-RAM Library Device

C. Information Needed for Troubleshooting

D. Notes on Running HiRDB Around the Clock

D.1 System reconfiguration command (pdchgconf command)

D.2 Specifying HiRDB system definitions

D.3 Making backups

D.4 Reorganizing databases

D.5 Reusing used free pages and free space within pages

D.6 Expanding RDAREAs

D.7 Dynamic updating of global buffers

D.8 Deleting troubleshooting information

D.9 System switchover facility

D.10 Program maintenance facility (upgrade to update version)

D.11 Recovery-unnecessary front-end server (HiRDB parallel server configurations only)

E. Using Performance Improvement Facilities

E.1 BES connection holding facility (HiRDB parallel server configurations only)

F. Linkage to HiRDB Control Manager

F.1 Starting HiRDB Control Manager - Console

F.2 Registering Management HiRDB

Index

[Trademarks]

All Rights Reserved. Copyright (C) 2011, 2015, Hitachi, Ltd.