HITACHI Inspire The Next

For UNIX Systems

Scalable Database Server

HiRDB Version 8

System Operation Guide

3000-6-354(E)


Contents

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 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)
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 only)
1.5 Startup and termination of a server (applicable to HiRDB/Parallel Server 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 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
3. Handling System Log Files
3.1 Basics
3.2 Unloading the system log
3.2.1 HiRDB/Single Server
3.2.2 HiRDB/Parallel Server
3.3 Operating without unloading the system log
3.3.1 HiRDB/Single Server
3.3.2 HiRDB/Parallel Server
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 Application example 3 (making a backup)
3.8.6 Creating a time series list of unload log files (identifying the unload log files required for database restoration)
3.8.7 Error handling
3.8.8 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
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 (backing up a system)
6.4.2 Example 2 (backing up a system)
6.4.3 Example 3 (backing up a system)
6.4.4 Example 4 (backing up a unit)
6.4.5 Example 5 (backing up a server)
6.4.6 Example 6 (Backing up 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 JP1/OmniBack II (applicable to HP-UX only)
6.7.1 System configuration example
6.7.2 Environment setup
6.7.3 Notes on backup acquisition
6.7.4 Example 1 (HiRDB/Single Server)
6.7.5 Example 2 (HiRDB/Parallel Server)
6.8 Backup acquisition using backup-hold (backup without using the pdcopy command)
6.8.1 About backup-hold
6.8.2 Example 1 (using another product's backup facilities)
6.8.3 Example 2 (using the mirror disk facility)
6.9 Backup acquisition when the frozen update command (pddbfrz command) is used
6.9.1 Operation subject to the frozen update command
6.9.2 Operation of the frozen update command (pddbfrz command)
6.9.3 Operation example
6.9.4 Checking for files with full data pages
6.9.5 Manipulating user LOB RDAREAs for which the frozen update command has been executed
6.9.6 Relationship between RDAREAs and automatic extensions
6.9.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)
8.1.4 Suppressing message output to syslogfile
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)
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
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
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 to a HiRDB/Parallel Server
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 Example 1: Migrating a table
12.1.3 Example 2: Migrating tables of a schema
12.1.4 Example of a control statements file when migrating tables to a different schema
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)
13.3.2 Example 2: Reorganizing a table (HiRDB/Parallel Server)
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 (unloading in DAT format)
13.6.6 Example 5: 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 Relationship with other facilities
13.13 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 Re-registering the data
13.13.4 Reusing RDAREAs
13.13.5 Examples of the database reorganization utility and database load utility
13.13.6 Splitting or combining a table containing a non-partitioning key index
13.13.7 Splitting or combining when an index is incomplete
13.13.8 Checking the number of items of data following splitting or combining
13.13.9 Operation when an error occurs
13.13.10 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)
13.16 Migrating data to another table
13.16.1 Example 1: Migrating data to a table with the same table definition
13.16.2 Example 2: Migrating data to a table with a different table definition
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.22.4 Distributed database environment
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 Deleting an index
14.4 Creating a definition SQL from an existing index
14.5 Reducing the number of index page splits (unbalanced index split)
14.6 Error handling during batch index creation
14.6.1 Example of recovery when reloading (data loading) was performed in the log acquisition mode or the pre-update log acquisition mode
14.6.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.6.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.6.4 Example of recovery in the event of an error on the disk that contains the index storage RDAREA
14.7 Delayed batch creation of a plug-in index
14.7.1 Delayed batch creation of a plug-in index
14.7.2 Environment setup
14.7.3 Procedure during UAP execution
14.7.4 Notes
14.7.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 Increasing the size of an RDAREA or modifying its attributes (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 opening trigger attribute (RDAREA modification)
15.5.1 Before changing the RDAREA opening trigger attribute
15.5.2 Example
15.6 Deleting an RDAREA
15.6.1 Before deleting an RDAREA
15.6.2 Example
15.7 RDAREA automatic extension
15.7.1 Automatic extension of an RDAREA
15.7.2 Example
15.7.3 Handling space shortages in HiRDB file system areas
15.7.4 Actions to take when the number of extents reaches the maximum value
15.8 Moving an RDAREA (RDAREA migration)
15.8.1 Before moving RDAREAs
15.8.2 Example 1 (Moving RDAREAs to the back-end server on a new server machine)
15.8.3 Example 2 (Moving RDAREAs to a back-end server in a different unit)
15.8.4 Example 3 (Moving RDAREAs to a different back-end server in the same unit)
15.8.5 Example 4 (Moving RDAREAs containing a row-partitioned table)
15.8.6 Example 5 (Moving inner replica RDAREAs)
15.8.7 Example 6 (Moving RDAREAs containing an abstract data type)
15.9 Re-using used free pages and used free segments
15.9.1 Page and segment status
15.9.2 Reusing used free pages
15.9.3 Reusing used free segments
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 only)
18. Error Handling Procedures
18.1 HiRDB processing and the HiRDB administrator's action in the event of an error
18.1.1 Actions to be taken by the HiRDB administrator when an error occurs
18.1.2 Information collected by HiRDB when an error occurs
18.1.3 HiRDB processing in the event of an error
18.1.4 Handling of HiRDB process errors
18.1.5 Information inherited during a HiRDB restart
18.1.6 Facility for changing the process-down message when a transaction is cancelled
18.2 When a UAP does not execute correctly
18.3 When operation commands do not execute correctly
18.3.1 Actions to be taken when operation commands will not execute
18.3.2 Actions to be taken when an operation command results in a timeout while waiting for a response
18.4 When HiRDB does not start
18.4.1 When HiRDB does not start normally
18.4.2 When HiRDB does not restart
18.4.3 Actions to be taken in the event of an error in the master directory RDAREA
18.4.4 Actions to be taken in the event of other errors
18.5 When HiRDB does not terminate
18.6 Handling of system log file errors
18.6.1 Actions to be taken in the event of an error in the current file
18.6.2 Actions to be taken when HiRDB Datareplicator is being used
18.6.3 Actions to be taken when a HiRDB (unit) cannot be restarted due to an error in both versions of the current file
18.7 Handling of synchronization point dump file errors
18.8 Handling of status file errors
18.8.1 Actions to be taken in the event of an error in the current file
18.8.2 Procedure for starting a HiRDB (unit) while there is an erroneous status file
18.8.3 Actions to be taken when a HiRDB (unit) cannot be restarted due to an error in both versions of the current file
18.9 Handling of errors in files other than system files
18.9.1 Errors in the HiRDB system definitions file
18.9.2 Errors in the message log file
18.9.3 Errors in the statistics log file
18.9.4 Errors in the data linkage file (HiRDB Datareplicator)
18.10 When the OS terminates abnormally
18.11 Handling of errors while linked to an OLTP system
18.11.1 Actions to be taken when a communication error occurs while HiRDB is linked to an OLTP system
18.11.2 Actions to be taken when a transaction is placed in FORGETTING status due to an error
18.11.3 Actions to be taken when transactions remain resident due to inactivity of a unit with a front-end server
18.12 Handling of communication errors, CPU errors, and power failures
18.12.1 Handling of communication errors
18.12.2 Handling of CPU errors
18.12.3 Handling of a power failure
18.13 When HiRDB cannot be terminated because a user is still connected
18.13.1 Corrective procedure
18.13.2 Connected user data file and connected user details file
18.14 Actions when there is an undetermined transaction
18.14.1 Forcing determination of uncompleted transactions
18.14.2 Performing transaction determination manually on undetermined transactions
18.15 Handling of reduced activation (HiRDB/Parallel Server only)
18.16 Handling of disk errors
18.17 When a HiRDB (unit) terminates due to a system log file space shortage
18.17.1 Restart procedure
18.17.2 Determining the minimum number of system log files to be added
18.17.3 Creating a file in swappable target status
18.17.4 Creating a HiRDB file system area for system files
18.17.5 Determining the number of system log files to be used as input files during restart
18.17.6 Checking for synchronization point dump validation
18.18 When a utility terminates abnormally during execution of a reorganization with synchronization points set
18.18.1 Overview of actions
18.18.2 Example
18.18.3 Actions to be taken when a utility terminates abnormally before unload data files have been consolidated (HiRDB/Parallel Server only)
18.18.4 Notes
18.19 Actions when page destruction in an RDAREA is detected
18.19.1 Causes of page destruction
18.19.2 Actions to be taken
18.20 Actions to take when an RDAREA I/O error occurs
18.21 Checking the transaction completion type when an error occurs during commit processing (HiRDB/Parallel Server)
18.22 Actions to take when an error occurs while a local buffer is being used to update a shared table (HiRDB/Parallel Server only)
18.23 Actions to take when an error occurs in the system manager unit
18.24 Actions to take when a mismatch occurs between the original and the mirror duplicate
18.25 Recovery of HiRDB directory
18.25.1 When installation directory is available
18.25.2 When installation directory is not available
18.25.3 When a backup is available for the disk on which the HiRDB directory is located
18.26 Handling errors in the HiRDB file system areas
18.26.1 Unmanageable files and unreferenceable areas
18.26.2 Corruption of the area management information (applicable to HiRDB version 07-02 and earlier)
19. Database Recovery Procedures
19.1 Overview of database recovery
19.1.1 Database recovery point
19.1.2 Relationship to the backup acquisition mode
19.1.3 Relationship to the log acquisition mode
19.1.4 Notes on recovery of various types of RDAREAs
19.1.5 For users of 64-bit-mode HiRDB
19.2 Recovering a database to the point at which a backup was made
19.2.1 Example 1: Recovering all RDAREAs
19.2.2 Example 2: Recovering specified RDAREAs
19.2.3 Example 3: When JP1/OmniBack II is used for recovery
19.3 Recovering a database to the most recent synchronization point
19.3.1 Example 1: Recovering all RDAREAs
19.3.2 Example 2: Recovering specified RDAREAs
19.3.3 Example 3: Recovering specified RDAREAs (operation without unloading the system log)
19.3.4 Example 4: When JP1/OmniBack II is used for recovery)
19.4 Database recovery using the differential backup facility
19.4.1 Example 1: Recover to the most recent differential backup acquisition point
19.4.2 Example 2: Recover to the most recent synchronization point
19.4.3 Recovery when a differential backup management file is not available
19.5 Recovery procedure when the backup was not made with the pdcopy command
19.5.1 Example 1: Recovering all RDAREAs to the point at which a backup was made
19.5.2 Example 2: Recovering specified RDAREAs to the point at which a backup was made
19.5.3 Example 3: Recovering all RDAREAs to the most recent synchronization point
19.5.4 Example 4: Recovering specified RDAREAs
19.5.5 Example 5: Recovering the master directory RDAREA only
20. Obtaining Tuning Information
20.1 Collecting tuning information from the statistics log
20.1.1 Tuning information that can be collected from the statistics log
20.1.2 Preparing for collecting tuning information
20.1.3 Collecting tuning information
20.1.4 Shell script for creating unload statistics log files at a specified server machine
20.1.5 When linked to an OLTP system
20.2 Collecting tuning information from the system log
20.3 Using the database condition analysis utility to collect tuning information
21. Tuning
21.1 Tuning global buffer pools
21.1.1 Using the pdbufls command to collect statistical information
21.1.2 Using the statistics analysis utility to collect statistical information
21.2 Tuning deferred write processing
21.3 Tuning the synchronization point processing time when deferred write processing is used
21.3.1 Tuning procedure
21.3.2 How to interpret statistical information about deferred write processing
21.3.3 How to reduce the synchronization point processing time
21.4 Tuning the synchronization point dump interval
21.5 Tuning buffer lengths
21.5.1 Tuning the buffer length for table definition information
21.5.2 Tuning the buffer length for view analysis information
21.5.3 Tuning the buffer length for user privilege information
21.5.4 Tuning the buffer length for SQL objects
21.5.5 Tuning the buffer length for user-defined type information
21.5.6 Tuning the buffer length for routine definition information
21.5.7 Tuning the buffer length for registry information
21.6 Tuning the number of processes
21.6.1 Tuning the maximum number of active processes
21.6.2 Tuning the number of resident processes
21.6.3 Tuning the number of processes in asynchronous READ processing
21.7 Tuning indexes
21.8 Tuning the database
21.9 Tuning SQLs
21.10 Tuning the system's internal processing
22. Using the Security Audit Facility
22.1 Overview of the security audit facility
22.1.1 About the security audit facility
22.1.2 Triggers for collecting audit trails
22.1.3 Examples of audit trail collection
22.1.4 Information collected in an audit trail
22.1.5 Accessing an audit trail
22.1.6 System configuration requirements
22.1.7 Audited events
22.2 Information output to an audit trail file
22.3 Audit trail output patterns
22.3.1 Output patterns during privilege checking
22.3.2 Output patterns at event termination
22.3.3 Relationships among audit trails
22.4 Environment settings
22.4.1 Security audit facility operand specifications
22.4.2 Creation of the HiRDB file system area for the audit trail files
22.4.3 Auditor registration, creation of the RDAREA to store the audit trail table, and creation of the audit trail table
22.4.4 Audit event definition
22.5 Operating procedure
22.5.1 Actions performed by the HiRDB administrator
22.5.2 Actions performed by the auditor
22.6 Operation of audit trail files
22.6.1 Creation of audit trail files
22.6.2 Status of audit trail files
22.6.3 Swapping of audit trail files
22.7 Recording data in the audit trail table
22.7.1 Example 1: Data loading from specified audit trail files
22.7.2 Example 2: Data loading from all audit trail files in the HiRDB file system area
22.7.3 Procedure when an error occurs during data loading
22.8 Audit trail table columns
22.9 Narrowing the audit trails
22.10 Audit trail file error handling
22.11 Linkage with other facilities
22.12 Audit trail record items (during privilege checking)
22.13 Audit trail record items (at event termination)
22.14 Audit trail output destination unit during utility execution (HiRDB/Parallel Server only)
22.15 Notes on version upgrading
23. Using the Connection Security Facility
23.1 Overview of the connection security facility
23.1.1 About the connection security facility
23.1.2 Password character string restrictions
23.1.3 Limit on the number of consecutive certification failures
23.2 Setting password character string restrictions
23.3 Changing a password character string restriction
23.3.1 Special notes on changing password character string restrictions
23.3.2 Procedure for changing a password character string restriction
23.4 Releasing the password-invalid account lock state
23.4.1 Releasing individual users from password-invalid account lock state
23.4.2 Releasing all users from password-invalid account lock state
23.5 Checking for users who will be placed in password-invalid account lock state
23.6 Privilege granting or revocation for users in password-invalid account lock state
23.7 Cancelling the password character string restrictions
23.8 Relationships between password character string restrictions and other facilities
23.8.1 Notes on using a Directory Server linkage facility
23.8.2 Notes on using the security audit facility
23.9 Setting and cancelling the limit on number of consecutive certification failures
23.9.1 Setting a new limit on the number of consecutive certification failures
23.9.2 Cancelling the limit on the number of consecutive certification failures
23.9.3 Changing the limit on the number of consecutive certification failures
23.9.4 Checking the permitted number of consecutive certification failures and the account lock period
23.10 Checking for users in consecutive certification failure account lock state
23.11 Releasing consecutive certification failure account lock state
23.12 Notes on using the connection security facility
23.12.1 Releasing a double lock
23.12.2 Notes on restoring a dictionary RDAREA
24. Using the Directory Server Linkage Facility
24.1 Overview of the Directory Server linkage facility
24.1.1 About the Directory Server linkage facility
24.1.2 Directory servers that can be linked
24.1.3 Capabilities of the Directory Server linkage facility
24.2 System configuration
24.2.1 Software configuration
24.2.2 Example system configurations
24.3 Environment setup
24.3.1 Notes on HiRDB environment setup
24.3.2 Procedure for setting up environment for Directory Server linkage facility
24.3.3 Handling upper-case and lower-case letters specified in user IDs, passwords, and roles
24.4 User privileges setup
24.4.1 DBA privilege setup
24.4.2 Auditor privilege setup
24.4.3 CONNECT privilege setup
24.4.4 Schema definition privilege setup
24.4.5 RDAREA usage privilege setup
24.4.6 Table access privilege setup
24.5 Operating procedures
24.5.1 Adding, modifying, or deleting a user or role
24.5.2 Acquiring table access privileges information
24.5.3 Suspending the Directory Server linkage facility
24.6 Operations in the event of an error
24.7 Creating the HiRDB LDAP Option environment definition file
25. Using the System Switchover Facility
25.1 Overview of the system switchover facility
25.1.1 System switchover facility (standby system switchover facility)
25.1.2 Standby-less system switchover facilities
25.1.3 Application criteria for the system switchover facilities
25.1.4 Cluster software supported by HiRDB
25.1.5 Monitor mode and server mode
25.2 System configuration examples
25.2.1 System configuration examples of a HiRDB/Single Server (standby system switchover)
25.2.2 System configuration examples of a HiRDB/Parallel Server
25.2.3 System configuration examples of standby-less system switchover (1:1)
25.2.4 System configuration examples of standby-less system switchover (effects distributed)
25.3 IP address configuration examples
25.4 Handling of host names depending on whether or not IP addresses are inherited
25.4.1 HiRDB/Single Server
25.4.2 HiRDB/Parallel Server
25.5 HiRDB preparations
25.5.1 Conditions and notes
25.5.2 Preparing a shared disk unit
25.5.3 Creating HiRDB system definitions
25.5.4 Client environment definition specification
25.5.5 Specification examples of host names in HiRDB system definitions and client environment definitions
25.5.6 RDAREA creation
25.5.7 Definition of global buffers (standby-less system switchover (1:1) facility only)
25.5.8 Definition of global buffers (standby-less system switchover (effects distributed) facility only)
25.5.9 Using audit trail files
25.6 HA monitor preparations
25.6.1 sysdef definition statement
25.6.2 server definition statement
25.7 MC/ServiceGuard preparations
25.7.1 Package
25.7.2 Shell script for starting HiRDB
25.7.3 Shell script for terminating HiRDB
25.7.4 Shell script for generating a dummy process (services monitored by MC/ServiceGuard) (monitor mode only)
25.7.5 Package IP address
25.7.6 Example of grouped MC/ServiceGuard and HiRDB configuration
25.8 VERITAS Cluster Server preparations
25.8.1 Groups and resources
25.8.2 HiRDB resource type definition
25.8.3 Agent definition pre-preparation
25.8.4 Agent definition
25.8.5 Environment setup file creation
25.9 Sun Cluster preparations
25.9.1 Cluster startup
25.9.2 Shared disk setup (disk group creation)
25.9.3 Network setup (PNM setup)
25.9.4 Logical host creation
25.9.5 Service creation and registration
25.10 HACMP preparations
25.11 ClusterPerfect preparations
25.11.1 System configurations unable to perform system switchover
25.11.2 Network configuration examples
25.11.3 Scenario preparations
25.11.4 Shells used when setting HiRDB scenarios
25.12 Hitachi HA Toolkit Extension preparations (server mode only)
25.12.1 sysdef definition statement
25.12.2 server definition statement
25.13 Differences in the HiRDB operating procedures
25.13.1 Starting HiRDB (in the server mode)
25.13.2 Starting HiRDB (in the monitor mode)
25.13.3 Terminating HiRDB (in the server mode)
25.13.4 Terminating HiRDB (in the monitor mode)
25.13.5 Monitoring statuses
25.13.6 Handling of statistics log files
25.13.7 Notes on operations
25.13.8 Notes on using the standby-less system switchover facility
25.14 Planned system switchover
25.15 Grouped system switchover
25.16 Actions to be taken by the HiRDB administrator when errors occur
25.17 Operating procedures after system switchover
25.18 Reducing system switchover time (user server hot standby, rapid system switchover facility)
25.18.1 User server hot standby
25.18.2 Rapid system switchover facility
25.18.3 System configuration examples when using the rapid system switchover facility
25.18.4 Checking procedure when activation of standby system takes much time
25.18.5 Notes on using the rapid system switchover facility
25.19 Transaction queuing facility
25.20 System switchover when errors other than server failures occur
25.20.1 A large number of server processes has terminated abnormally
25.20.2 RDAREA I/O error (path error) has occurred
25.21 Actions to take when a stopped unit prevents switching of the system manager unit
25.21.1 Using reduced activation
25.21.2 Specifying the pd_ha_mgr_rerun operand
26. Using the Facility for Monitoring MIB Performance Information
26.1 Overview of the facility for monitoring MIB performance information
26.1.1 About the facility for monitoring MIB performance information
26.1.2 Objectives of the facility for monitoring MIB performance information
26.1.3 MIB definition file
26.1.4 MIB environment definition file
26.2 System configuration
26.3 Environment setup
26.4 MIB definition file
26.5 Server status table (hirServerStatusTable)
26.6 Work table HiRDB file system area table (hirFileSystemTable)
26.7 RDAREA table (hirRdareaStatusTable)
26.8 RDAREA details table (hirRdareaDetStatusTable)
26.9 Global buffer table (hirBufferStatusTable)
26.10 HiRDB file system area (RDAREAs) table (hirRdareaFileTable)
26.11 SYS statistics table (hirStatisInfSysTable)
26.12 Disk usage
27. Using a Distributed Database (applicable to HP-UX and AIX 5L only)
27.1 Overview of a distributed database
27.1.1 Scope of distributed database
27.1.2 Remote database access facility
27.1.3 Character codes environment
27.1.4 Handling of authorization identifiers
27.1.5 Handling of passwords
27.1.6 Notes on establishing connection with another node's HiRDB
27.2 Environment setup for a distributed database
27.2.1 HiRDB environment setup
27.2.2 DF/UX environment setup
27.2.3 DF/UX Extension environment setup
27.3 Distributed database security
27.4 Information output when a communication error occurs (Distributed Server facility only)
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 only)
E. Using Performance Improvement Facilities
E.1 BES connection holding facility (HiRDB/Parallel Server only)
Index