Contents

• Notices

• Preface

• Part 1: Description

  • 1. Overview

    • 1.1 HADB for managing data in the information explosion age

    • 1.2 HADB features

      • 1.2.1 High-speed retrieval of data from a large volume of data

      • 1.2.2 Capability to build a large-scale database (up to exabytes)

      • 1.2.3 Scale-out for load distribution (Multi-node function)

    • 1.3 HADB system configuration

      • 1.3.1 HADB server

      • 1.3.2 HADB client

  • 2. Architecture

    • 2.1 Types of tables

      • 2.1.1 Base tables

      • 2.1.2 Viewed tables

    • 2.2 Base table types

      • 2.2.1 Row store tables and column store tables

      • 2.2.2 Single-chunk tables and multi-chunk tables

    • 2.3 Index types

      • 2.3.1 B-tree indexes

      • 2.3.2 Text indexes

      • 2.3.3 Range indexes

    • 2.4 DB areas (areas for storing tables and indexes)

      • 2.4.1 DB areas

      • 2.4.2 DB area types

      • 2.4.3 DB area structure (segments and pages)

      • 2.4.4 DB area file configuration

      • 2.4.5 DB area automatic extension

    • 2.5 Users and schemas

      • 2.5.1 User types (OS users and HADB users)

      • 2.5.2 Schemas

    • 2.6 User authorization

    • 2.7 Privileges

      • 2.7.1 Privilege types

      • 2.7.2 User privileges

      • 2.7.3 Schema operation privilege

      • 2.7.4 Audit privilege

      • 2.7.5 Access privileges

      • 2.7.6 Access privileges for viewed tables

      • 2.7.7 Scope of information in dictionary tables and system tables that can be referenced by HADB users

      • 2.7.8 Example of granting privileges to HADB users

    • 2.8 Database access method

      • 2.8.1 Global buffers

      • 2.8.2 Database updating method

      • 2.8.3 Database retrieval method (out-of-order execution)

    • 2.9 Transaction control

      • 2.9.1 Start and end of a transaction

      • 2.9.2 Transaction isolation levels supported by HADB

      • 2.9.3 Concurrent execution control of transactions

      • 2.9.4 Synchronization point processing of a transaction

      • 2.9.5 Transaction access modes

    • 2.10 Locking

      • 2.10.1 Lock modes

      • 2.10.2 Locked resources

      • 2.10.3 Period during which locked resources are reserved

      • 2.10.4 Locked resources that are reserved and their lock modes

      • 2.10.5 Base tables for which a lock is obtained when dictionary tables and system tables are referenced

      • 2.10.6 Dictionary tables and system tables locked when a database is referenced or updated

      • 2.10.7 Examples of locks

    • 2.11 Database recovery

      • 2.11.1 Recovery flow based on a restart

    • 2.12 Client-group facility

      • 2.12.1 Overview of the client-group facility

      • 2.12.2 Types of groups that can be set by the client-group facility

      • 2.12.3 Setting the numbers of connections and processing real threads for each group

    • 2.13 Centralized management of client definitions

      • 2.13.1 What is centralized management of client definitions?

      • 2.13.2 Files to be created before using centralized management of client definitions

      • 2.13.3 Application example of the processing by centralized management of client definitions

    • 2.14 Background-import facility

      • 2.14.1 About background import

      • 2.14.2 Managing data in data-import units (chunks)

      • 2.14.3 Relationship between chunks and range indexes

    • 2.15 Chunk archiving function (compressing data in a chunk)

      • 2.15.1 Overview of the chunk archiving function

      • 2.15.2 When the chunk archiving function is to be used

      • 2.15.3 Searching an archivable multi-chunk table

      • 2.15.4 Expanding (unarchiving) data

    • 2.16 Retrieving data from CSV files

    • 2.17 Searching text data

      • 2.17.1 Correction search

      • 2.17.2 Search using a regular expression

      • 2.17.3 Synonym search

      • 2.17.4 Word-context search

    • 2.18 Audit trail facility

      • 2.18.1 Overview of the audit trail facility

      • 2.18.2 Creating an auditor

      • 2.18.3 Operations that trigger audit trail output (audit target events)

      • 2.18.4 Information output in an audit trail

      • 2.18.5 Output destination of audit trails (audit trail file)

      • 2.18.6 Referencing audit trails

      • 2.18.7 Enabling and disabling the audit trail facility

      • 2.18.8 Preparing the disks used by the audit trail facility

      • 2.18.9 Conversion of audit trail information (linkage with JP1/Audit Management - Manager)

    • 2.19 Multi-node function

      • 2.19.1 About the multi-node function

      • 2.19.2 Nodes on which transactions and commands are executed

      • 2.19.3 Managing nodes with HA Monitor

      • 2.19.4 Separating a node from a multi-node configuration

      • 2.19.5 Returning a node to the multi-node configuration

      • 2.19.6 System configuration example that uses the multi-node function

    • 2.20 Memory structure of the HADB server

      • 2.20.1 Memory used by the HADB server

      • 2.20.2 Relationship with server definition operands

• Part 2: Exercise

  • 3. Guide for Building a Hands-on Environment

    • 3.1 General procedure for building a hands-on environment

      • 3.1.1 System configuration of the HADB server to be built

      • 3.1.2 Data stored in a table in the hands-on environment

    • 3.2 Installing the HADB server

      • 3.2.1 Preparations necessary for installation

      • 3.2.2 Installation

    • 3.3 Setting the kernel parameters

      • 3.3.1 Setting and checking the kernel parameters

    • 3.4 Creating the DB directory

      • 3.4.1 Creating and checking the DB directory

    • 3.5 Setting environment variables and definition files

      • 3.5.1 Setting environment variables

      • 3.5.2 Editing the definition files

    • 3.6 Creating DB areas (initializing the database)

      • 3.6.1 Editing the initialization option file

      • 3.6.2 Creating a DB area

    • 3.7 Creating an HADB user for creating and retrieving tables

      • 3.7.1 Starting the HADB server

      • 3.7.2 Connecting to the HADB server

      • 3.7.3 Creating an HADB user

      • 3.7.4 Granting privileges to the created HADB user

    • 3.8 Creating tables

      • 3.8.1 Connecting to the HADB server

      • 3.8.2 Defining a schema

      • 3.8.3 Creating tables

    • 3.9 Storing data

      • 3.9.1 Preparation for storing data

      • 3.9.2 Storing data in the table

    • 3.10 Retrieving the stored data

      • 3.10.1 Connecting to the HADB server and retrieving data

    • 3.11 Uninstalling the HADB server

      • 3.11.1 Deleting the server directory

      • 3.11.2 Deleting the directory that stores the installation data

      • 3.11.3 Deleting the directories that store communication-information files

      • 3.11.4 Deleting the HADB administrator and HADB administrators group

    • 3.12 Frequently asked questions and corrective actions

      • 3.12.1 I created the DB directory as a superuser by mistake

      • 3.12.2 I cannot create a table

      • 3.12.3 The KFAA91104-Q message is output during startup of the HADB server

      • 3.12.4 The KFAA30561-E message is output while attempting to connect to the HADB server

• Part 3: Design

  • 4. System Design

    • 4.1 System design flow

    • 4.2 Estimating resource requirements

      • 4.2.1 Estimating the size of the DB directory

      • 4.2.2 Estimating the size of the server directory

      • 4.2.3 Estimating the size of the archive directory

      • 4.2.4 Estimating the size of the unload file directory

      • 4.2.5 Estimating the size of the synonym dictionary file directory

      • 4.2.6 Estimating the size of the multi-node synonym dictionary storage directory

    • 4.3 Estimating memory requirements

      • 4.3.1 Estimating memory requirements during normal operation

      • 4.3.2 Estimating memory requirements during execution of the adbimport command

      • 4.3.3 Estimating memory requirements during execution of the adbidxrebuild command

      • 4.3.4 Estimating memory requirements during execution of the adbgetcst command

      • 4.3.5 Estimating memory requirements during execution of the adbexport command

      • 4.3.6 Estimating memory requirements during execution of the adbmergechunk command

      • 4.3.7 Estimating memory requirements during execution of the adbarchivechunk command

      • 4.3.8 Estimating memory requirements during execution of the adbunarchivechunk command

  • 5. Designing a Database

    • 5.1 Database design procedure

    • 5.2 Designing a table

      • 5.2.1 Flow of table design

      • 5.2.2 Criteria for selecting row store tables and column store tables

      • 5.2.3 Criteria for selecting single or multi-chunk tables

      • 5.2.4 Points to consider in defining a multi-chunk table

      • 5.2.5 Points to consider in defining an archivable multi-chunk table [Row store table]

      • 5.2.6 Normalizing a table [Row store table]

      • 5.2.7 Fixing the row length (FIX specification) [Row store table]

      • 5.2.8 Setting a default value for a column (DEFAULT clause)

      • 5.2.9 Specifying a primary key (uniqueness constraint definition) (PRIMARY KEY) [Single-chunk table]

      • 5.2.10 Specifying a foreign key (FOREIGN KEY)

      • 5.2.11 Allocating an unused area inside the data page (PCTFREE) [Row store table]

      • 5.2.12 Branch specification for column data of variable-length data types (BRANCH) [Row store table]

    • 5.3 Designing a B-tree index

      • 5.3.1 Notes on defining B-tree indexes (unfinished status of B-tree indexes)

      • 5.3.2 Points to consider in determining the columns to be defined for a B-tree index

      • 5.3.3 Whether to use a single-column index or a multiple-column index

      • 5.3.4 Allocating an unused area inside a B-tree index page (PCTFREE)

      • 5.3.5 Points to consider in determining the columns to be defined for a unique index

      • 5.3.6 Setting a null-value exclusion specification (EXCLUDE NULL VALUES)

    • 5.4 Designing a text index

      • 5.4.1  Points to consider in determining the columns to be defined for a text index

      • 5.4.2 Allocating an unused area inside a text index page (PCTFREE)

      • 5.4.3 Notes on defining text indexes (unfinished status of text indexes)

      • 5.4.4 Notation-correction-search text-index specification (CORRECTIONRULE)

      • 5.4.5 Specifying a text index for a word-context search (TEXT WORDCONTEXT)

      • 5.4.6 Selecting the delimiting characters for word-context searches (DELIMITER)

    • 5.5 Designing a range index

      • 5.5.1 Points to consider when defining a range index

      • 5.5.2 Estimating the number of pages for the global buffer used exclusively for range indexes

      • 5.5.3 Pre-reading of range indexes

      • 5.5.4 Notes on defining range indexes (unfinished status of range indexes)

    • 5.6 Designing a data DB area

      • 5.6.1 Points to consider when designing a data DB area

      • 5.6.2 Points to consider in storing a multi-chunk table in the data DB area

      • 5.6.3 Points to consider when determining the page size in data DB areas

    • 5.7 Designing a work table DB area

    • 5.8 Estimating the size of the data DB area

      • 5.8.1 Determining the total number of pages in the data DB area

      • 5.8.2 Determining the number of pages for storing each type of row

      • 5.8.3 Determining the number of storage pages for each B-tree index segment

      • 5.8.4 Determining the key length (KEYSZ) of a B-tree index

      • 5.8.5 Determining the number of storage pages for each text index segment

      • 5.8.6 Determining the number of segments for storing each range index

    • 5.9 Estimating the size of the work table DB area

      • 5.9.1 Determining the total number of pages in the work table DB area

      • 5.9.2 Determining the number of pages for base rows that are needed for storing work tables

    • 5.10 Estimating the size of the master directory DB area

    • 5.11 Estimating the size of the dictionary DB area

    • 5.12 Estimating the size of the system-table DB area

      • 5.12.1 Estimating the sizes of system tables

  • 6. Preparing Resources

    • 6.1 Preparing disks

      • 6.1.1 Points to consider when preparing disks

      • 6.1.2 Points to consider when setting up an LVM

      • 6.1.3 Points to consider regarding power outages

    • 6.2 Estimating the kernel parameters

    • 6.3 Estimating the HADB server's memory requirement

      • 6.3.1 Determining the shared memory requirement

      • 6.3.2 Determining the process memory requirement

      • 6.3.3 Determining the memory requirement for starting the HADB server

      • 6.3.4 Determining the memory requirement during normal operation

      • 6.3.5 Determining the memory requirement for executing the adbinit command

      • 6.3.6 Determining the memory requirement for executing the adbimport command

      • 6.3.7 Determining the memory requirement for executing the adbidxrebuild command

      • 6.3.8 Determining the memory requirement for executing the adbgetcst command

      • 6.3.9 Determining the memory requirement for executing the adbdbstatus command

      • 6.3.10 Determining the memory requirement for executing the adbexport command

      • 6.3.11 Determining the memory requirement for executing the adbstat command

      • 6.3.12 Determining the memory requirement for executing the adbmodarea command

      • 6.3.13 Determining the memory requirement for executing the adbmergechunk command

      • 6.3.14 Determining the memory requirement for executing the adbchgchunkcomment command

      • 6.3.15 Determining the memory requirement for executing the adbchgchunkstatus command

      • 6.3.16 Determining the memory requirement for executing the adbarchivechunk command

      • 6.3.17 Determining the memory requirement for executing the adbunarchivechunk command

      • 6.3.18 Determining the memory requirement for executing the adbreorgsystemdata command

      • 6.3.19 Determining the memory requirement for executing the adbclientdefmang command

      • 6.3.20 Determining the memory requirement for executing the adbsyndict command

      • 6.3.21 Determining the memory requirement for executing the adbaudittrail command

      • 6.3.22 Determining the memory requirement for executing the adbconvertaudittrailfile command

    • 6.4 Files that increase continuously over time when using the HADB server

    • 6.5 Estimating the size of the server message log file

    • 6.6 Estimating the size of error information (core file)

    • 6.7 Estimating the size of HADB dump files

    • 6.8 Estimating the size of a statistics log file

    • 6.9 Estimating the size of an SQL trace file

    • 6.10 Estimating the size of files required for the updated-row columnizing facility

    • 6.11 Estimating the size of access path search information log files

    • 6.12 Estimating the size of the system log files

      • 6.12.1 Determining the size of the master log file

      • 6.12.2 Determining the size of the user log files

      • 6.12.3 Determining the size of the user logs that are output during execution of a definition SQL statement (variable max_user_log)

      • 6.12.4 Determining the size of the user logs that are output during execution of the adbimport command (variable max_user_log)

      • 6.12.5 Determining the size of the user logs that are output during execution of the adbidxrebuild command (variable max_user_log)

      • 6.12.6 Determining the size of the user logs that are output during execution of the adbmergechunk command (variable max_user_log)

      • 6.12.7 Determining the size of the user logs that are output during database updating (variable max_user_log)

      • 6.12.8 Determining the size of the user logs that are output during execution of the TRUNCATE TABLE statement (variable max_user_log)

      • 6.12.9 Determining the size of the user logs that are output during execution of the PURGE CHUNK statement (variable max_user_log)

      • 6.12.10 Determining the size of the user logs that are output during execution of the adbchgchunkstatus command (variable max_user_log)

      • 6.12.11 Determining the size of the user logs that are output during execution of the adbarchivechunk command (variable max_user_log)

      • 6.12.12 Determining the size of the user logs that are output during execution of the adbunarchivechunk command (variable max_user_log)

      • 6.12.13 Determining the size of the user logs that are output during execution of the adbreorgsystemdata command (variable max_user_log)

      • 6.12.14 Determining the size of user logs that are required for the maintenance processing of the updated-row columnizing facility (variable max_user_log)

      • 6.12.15 Determining the number of user log files

    • 6.13 Estimating the size of the archive directory

    • 6.14 Estimating the size of the synonym dictionary file directory

    • 6.15 Estimating the size of the audit trail directory

    • 6.16 Estimating the size of the output-directory for common format audit trails

    • 6.17 Estimating the size of the multi-node synonym dictionary storage directory

    • 6.18 Estimating the size of a file output by the adbexport command

    • 6.19 Estimating the size of files required to reorganize a base table

    • 6.20 Estimating the size of an unload file

    • 6.21 Estimating the size of the temporary work file for executing a command

      • 6.21.1 Estimating the size of the temporary work file for executing the adbimport command

      • 6.21.2 Estimating the size of the temporary work file for executing the adbidxrebuild command

      • 6.21.3 Estimating the size of the temporary work file for executing the adbmergechunk command

      • 6.21.4 Estimating the size of the temporary work file for executing the adbunarchivechunk command

      • 6.21.5 Estimating the size of the temporary work file for executing the adbreorgsystemdata command

      • 6.21.6 Estimating the size of the temporary work file for executing the adbsyndict command

    • 6.22 Estimating the increase in the amount of data that occurs during command execution

      • 6.22.1 Estimating the increase in the amount of data that occurs when the adbmergechunk command is executed

    • 6.23 Points to consider when executing commands concurrently

      • 6.23.1 Maximum number of commands that can be executed concurrently

      • 6.23.2 Points to consider about the number of processing real threads to be used during command execution

      • 6.23.3 Points to consider about locking during concurrent command execution

      • 6.23.4 Points to consider about memory requirements during concurrent command execution

      • 6.23.5 Points to consider about the size of the system log files during concurrent command execution

    • 6.24 Points to consider when using the client-group facility

      • 6.24.1 Points to consider when specifying the number of connections for a group

      • 6.24.2 Points to consider when specifying the number of processing real threads for a group

      • 6.24.3 Relationship between the number of connections and the number of processing real threads that are used by the client-group facility

    • 6.25 Estimates related to work tables

      • 6.25.1 Estimating the number of pages in the global buffer for global work tables

      • 6.25.2 Estimating the number of pages in the buffer for local work tables

      • 6.25.3 Number of work tables created during retrieval using hash tables

  • 7. Designing the Server Definition

    • 7.1 Specification formats for server definition operands

    • 7.2 Detailed descriptions of the server definition operands

      • 7.2.1 Operands related to system configuration (set format)

      • 7.2.2 Operands related to performance (set format)

      • 7.2.3 Operands related to system logs (set format)

      • 7.2.4 Operands related to status monitoring (set format)

      • 7.2.5 Operands related to SQL statements (set format)

      • 7.2.6 Operands related to range indexes (set format)

      • 7.2.7 Operands related to statistical information (set format)

      • 7.2.8 Operands related to synonym search (set format)

      • 7.2.9 Operands related to audit trail facility (set format)

      • 7.2.10 Operands related to the multi-node function (set format)

      • 7.2.11 Operands and options related to global buffers (command format)

      • 7.2.12 Operands and options related to the client-group facility (command format)

    • 7.3 Syntax rules for the server definition

      • 7.3.1 Details of syntax rules for the server definition

• Part 4: Setup

  • 8. Building a System

    • 8.1 System construction procedure

    • 8.2 Installing the HADB server

      • 8.2.1 Tasks that must be performed before installation

      • 8.2.2 Installation procedure

      • 8.2.3 Tasks that must be performed after installation

    • 8.3 Setting kernel parameters

    • 8.4 Setting environment variables

    • 8.5 Creating and modifying a server definition

      • 8.5.1 Server definition creation method and storage destination

      • 8.5.2 Modifying the server definition

    • 8.6 Upgrading the HADB server version

      • 8.6.1 Steps to take before upgrading the server version

      • 8.6.2 Upgrading the server version

      • 8.6.3 Steps to take after version upgrading

      • 8.6.4 Steps to take when version upgrading fails

      • 8.6.5 Notes on version upgrading

    • 8.7 Downgrading the HADB server version (restoring the previous version)

      • 8.7.1 Using a backup of the previous version of the database

      • 8.7.2 Rebuilding the database by using the previous version

      • 8.7.3 If the previous version needs to be restored because a version upgrade has failed

    • 8.8 Swapping the HADB server with its revised version

      • 8.8.1 Steps to take before swapping the HADB server with its revised version

      • 8.8.2 Procedure for swapping the HADB server with its revised version

    • 8.9 Temporarily upgrading the HADB server version and then downgrading it (test for checking operational behavior)

      • 8.9.1 Steps to take before upgrading the server version (test for checking operational behavior)

      • 8.9.2 Upgrading the server version (test for checking operational behavior)

      • 8.9.3 Steps to take after upgrading the server version (test for checking operational behavior)

      • 8.9.4 Downgrading the server version (test for checking operational behavior)

      • 8.9.5 Steps to take after downgrading the server version (test for checking operational behavior)

    • 8.10 Changing the time in the server machine's OS

      • 8.10.1 Notes (when changing the OS time)

      • 8.10.2 Moving the time forward in the server machine's OS

      • 8.10.3 Moving back the time in the server machine's OS

    • 8.11 Changing the host name or IP address of the server machine's OS

    • 8.12 Uninstallation

      • 8.12.1 Uninstallation procedure

      • 8.12.2 Tasks that must be performed following uninstallation

  • 9. Creating a Database

    • 9.1 Steps for creating a database

    • 9.2 Initializing a database (creating data DB areas)

    • 9.3 Starting the HADB server

    • 9.4 Creating an HADB user to define base tables

      • 9.4.1 Creating an HADB user

      • 9.4.2 Authorization identifier specification rules

      • 9.4.3 Password specification rules

    • 9.5 Defining schemas, tables, and indexes

    • 9.6 Importing data into a base table

    • 9.7 Collecting cost information

• Part 5: Operation

  • 10. Scheduled Operations

    • 10.1 List of operation items

    • 10.2 Starting and terminating the HADB server and its operation modes

      • 10.2.1 Starting the HADB server

      • 10.2.2 Terminating the HADB server

      • 10.2.3 HADB server operation modes

      • 10.2.4 Setting up the HADB server to restart automatically

    • 10.3 Backing up a database

      • 10.3.1 Backup acquisition method

      • 10.3.2 Recovering the database from the backup

      • 10.3.3 Backup operation example (using OS commands)

      • 10.3.4 Backup operation example (using ShadowImage)

    • 10.4 Checking the messages

      • 10.4.1 Message output destinations

      • 10.4.2 Viewing the message logs (message log output destination)

      • 10.4.3 Working with the message log files

      • 10.4.4 Fall-back mode of the message log file

      • 10.4.5 Suppressing message output to syslog

      • 10.4.6 Converting character encoding and improving reliability for syslog (Applying the extended syslog function)

    • 10.5 Monitoring the resource usage (list of messages to be monitored)

    • 10.6 Checking the memory usage

      • 10.6.1 Checking the usage status of all memory

      • 10.6.2 Checking the usage status of the shared memory

      • 10.6.3 Checking the memory usage status for each real thread

    • 10.7 Checking the threads running on the HADB server

    • 10.8 Checking the transaction processing status

      • 10.8.1 Checking the application or command processing status

      • 10.8.2 Checking whether the process of allocating processing real threads has gone into wait status

      • 10.8.3 Checking whether the process of reserving locked resources has gone into wait status

      • 10.8.4 Checking the status when the transaction has been rolled back

    • 10.9 Checking the database status and usage

      • 10.9.1 Checking the database usage

      • 10.9.2 Checking the status and usage of a base table

      • 10.9.3 Checking the status and usage of a B-tree index

      • 10.9.4 Checking the status and usage of a text index

      • 10.9.5 Checking the status and usage of range indexes

      • 10.9.6 Checking the usage of DB area files

      • 10.9.7 Checking the size of archive files

    • 10.10 Performing statistical analysis (checking HADB server operation information)

      • 10.10.1 Using the HADB server's statistical information

      • 10.10.2 Using the connection operation information

      • 10.10.3 Using the global buffer statistical information

      • 10.10.4 Using the SQL statement statistical information

      • 10.10.5 Using the statistics log files

      • 10.10.6 Estimating the size of information that is output from the statistics log files when the adbstat command is executed

    • 10.11 Running SQL tracing

      • 10.11.1 About SQL tracing

      • 10.11.2 Information that is output as SQL trace information

      • 10.11.3 Examples of output of and output items for access path statistical information

      • 10.11.4 Examples of output of SQL trace information and how to interpret the information

      • 10.11.5 Preparations for outputting SQL trace information

      • 10.11.6 Operation when SQL trace information is set to be output

      • 10.11.7 Using SQL trace information to determine the cause of errors in SQL statements

      • 10.11.8 Using SQL trace information to tune SQL statements

      • 10.11.9 Corrective action to take if SQL trace information was not output due to an error

      • 10.11.10 Stopping using SQL tracing

      • 10.11.11 Notes about using the multi-node function

    • 10.12 Working with the system log files

      • 10.12.1 System log file configuration and server definition specification

      • 10.12.2 Trigger for reducing the size of the system log files

  • 11. Unscheduled Operations

    • 11.1 Base table operations

      • 11.1.1 Defining a base table

      • 11.1.2 Adding a column to a base table

      • 11.1.3 Changing the column name of a base table

      • 11.1.4 Retrieving and updating data in a base table

      • 11.1.5 Deleting all rows from a base table

      • 11.1.6 Changing a single-chunk table to a multi-chunk table

      • 11.1.7 Storing data in a base table (data import)

      • 11.1.8 Outputting data from a base table to a file (data export)

      • 11.1.9 Checking whether a single-chunk table needs to be reorganized

      • 11.1.10 Reorganizing a single-chunk table

      • 11.1.11 Changing a row store table to a column store table

      • 11.1.12 Changing a column store table to a row store table

      • 11.1.13 Checking the definition information for a base table (searching a dictionary table)

      • 11.1.14 Changing the data DB area that stores a base table

      • 11.1.15 Deleting base tables

    • 11.2 Viewed table operations

      • 11.2.1 Defining a viewed table

      • 11.2.2 Retrieving, updating, adding, and deleting data in viewed tables

      • 11.2.3 Outputting data from a viewed table to a file (data export)

      • 11.2.4 Rebuilding a viewed table

      • 11.2.5 Deleting a viewed table

      • 11.2.6 Checking whether a viewed table is updatable

      • 11.2.7 Checking whether a viewed table has been invalidated

      • 11.2.8 Releasing a viewed table from invalidation

      • 11.2.9 Deleting invalidated viewed tables

      • 11.2.10 Checking the underlying tables of a viewed table

      • 11.2.11 Checking dependent viewed tables

      • 11.2.12 Checking the access privileges for a viewed table

      • 11.2.13 Operation example of using viewed tables

    • 11.3 Index operations

      • 11.3.1 Defining indexes

      • 11.3.2 Rebuilding B-tree indexes

      • 11.3.3 Rebuilding text indexes

      • 11.3.4 Checking a text index (checking the index option that was specified)

      • 11.3.5 Rebuilding range indexes

      • 11.3.6 Checking a range index (whether it can skip chunks)

      • 11.3.7 Redefining a range index (setting up chunk skipping)

      • 11.3.8 Changing the data DB area that stores indexes

      • 11.3.9 Deleting an index

    • 11.4 Performing operations on multi-chunk tables

      • 11.4.1 Defining a multi-chunk table

      • 11.4.2 Storing data in a multi-chunk table (background import)

      • 11.4.3 Notes on retrieving and updating data in an archivable multi-chunk table

      • 11.4.4 Temporarily excluding data to be imported to a multi-chunk table from retrieval (creating a chunk in wait status)

      • 11.4.5 Exporting data in units of chunks

      • 11.4.6 Deleting data in units of chunks

      • 11.4.7 Deleting data stored in a multi-chunk table in a batch

      • 11.4.8 Checking the chunk status and the number of chunks created

      • 11.4.9 Merging chunks (to reduce the number of chunks)

      • 11.4.10 Changing the maximum number of chunks

      • 11.4.11 Changing the comment for a chunk

      • 11.4.12 Changing the chunk status

      • 11.4.13 Checking whether a multi-chunk table needs to be reorganized

      • 11.4.14 Reorganizing a multi-chunk table: Chunk-based reorganization

      • 11.4.15 Reorganizing a multi-chunk table: Reorganization of an entire table

      • 11.4.16 Reorganizing a multi-chunk table: Reorganization using a sample shell script

      • 11.4.17 Archiving chunks (when using an archivable multi-chunk table)

      • 11.4.18 Unarchiving chunks (when using an archivable multi-chunk table)

      • 11.4.19 Checking archived chunks

      • 11.4.20 Changing a regular multi-chunk table to an archivable multi-chunk table

      • 11.4.21 Changing an archivable multi-chunk table to a regular multi-chunk table

      • 11.4.22 Deleting a multi-chunk table

      • 11.4.23 Operation taking background import and chunks into consideration (Example 1: Adding and deleting data on a regular basis)

      • 11.4.24 Operation taking background import and chunks into consideration (Example 2: Using chunks in wait status)

      • 11.4.25 Operation taking archive of chunks into consideration

    • 11.5 Collecting cost information

    • 11.6 Managing HADB users

      • 11.6.1 Creating HADB users

      • 11.6.2 Changing an HADB user's password

      • 11.6.3 Deleting HADB users

    • 11.7 Managing user privileges and the schema operation privilege

      • 11.7.1 Granting user privileges and the schema operation privilege to HADB users

      • 11.7.2 Checking the user privileges and schema operation privilege granted to an HADB user

      • 11.7.3 Revoking an HADB user's user privileges and schema operation privilege

    • 11.8 Managing access privileges

      • 11.8.1 Granting access privileges to an HADB user

      • 11.8.2 Checking the access privileges granted to an HADB user

      • 11.8.3 Revoking access privileges that were granted to HADB users

      • 11.8.4 Revoking only the grant options for access privileges that were granted to HADB users

      • 11.8.5 Changing the access privileges granted to an HADB user

    • 11.9 Handling schemas

      • 11.9.1 Defining a schema

      • 11.9.2 Deleting a schema

    • 11.10 Handling data DB areas

      • 11.10.1 Adding data DB areas

      • 11.10.2 Deleting a data DB area

      • 11.10.3 Expanding a data DB area (adding a data DB area file)

      • 11.10.4 Re-initializing a data DB area

      • 11.10.5 Changing the storage location of data DB area files

      • 11.10.6 Securing free space in a data DB area

    • 11.11 Handling the work table DB area

      • 11.11.1 Changing the storage location of a work table DB area file

      • 11.11.2 Reducing the size of a work table DB area file

    • 11.12 Performing operations on buffers

      • 11.12.1 Changing the local work table buffer

    • 11.13 Checking client group settings

      • 11.13.1 Identifying the group to which the HADB client that executed an application belongs

      • 11.13.2 Identifying the groups to which the HADB clients using real threads belong

      • 11.13.3 Checking the numbers of connections and processing real threads set for each group

    • 11.14 Operating centralized management of client definitions

      • 11.14.1 Flow of using the function for centrally managing client definitions

      • 11.14.2 Files required for the function for centrally managing client definitions

      • 11.14.3 Newly using the function for centrally managing client definitions

      • 11.14.4 Changing the definitions of how the function for centrally managing client definitions is applied

      • 11.14.5 Example of using the function for centrally managing client definitions

      • 11.14.6 Stopping the use of the function for centrally managing client definitions

    • 11.15 Handling of data retrieval from CSV files

      • 11.15.1 Preparatory tasks

      • 11.15.2 Data retrieval method

    • 11.16 Performing synonym search operations

      • 11.16.1 Preparing for synonym search operations

      • 11.16.2 Performing synonym search operations

      • 11.16.3 Checking the synonyms registered in a synonym dictionary

      • 11.16.4 Checking the information about synonym dictionaries

      • 11.16.5 Adding synonyms

      • 11.16.6 Deleting synonyms

      • 11.16.7 Adding synonym groups

      • 11.16.8 Registering a synonym dictionary

      • 11.16.9 Deleting synonym dictionaries

      • 11.16.10 Changing a synonym dictionary to support correction search

      • 11.16.11 Tuning synonym search function

      • 11.16.12 Checking the free space required for the directory for storing synonym dictionary files

      • 11.16.13 Changing the directory for storing synonym dictionary files

      • 11.16.14 Rebuilding a synonym list definition file (when a synonym list definition file is lost)

      • 11.16.15 Specification rules for a synonym list definition file

      • 11.16.16 Specification rules for a dictionary creation file

    • 11.17 Reorganizing system tables

      • 11.17.1 Reason for reorganizing a system table

      • 11.17.2 Timing for reorganizing a system table

      • 11.17.3 Reorganizing a system table

      • 11.17.4 Reorganization of a system table and lock control

      • 11.17.5 Checking the status and amount of use of system tables

    • 11.18 Using the updated-row columnizing facility (maintaining the retrieval performance for column store tables)

      • 11.18.1 Overview of the updated-row columnizing facility

      • 11.18.2 Preparation tasks

      • 11.18.3 How to check the status of the updated-row columnizing facility (whether the facility is enabled or disabled)

      • 11.18.4 Cases where the updated-row columnizing facility must be disabled temporarily

      • 11.18.5 Action to be taken when an error related to the updated-row columnizing facility occurs

      • 11.18.6 Action to be taken if the maintenance processing is not performed

      • 11.18.7 Details of the maintenance processing

  • 12. Audit Trail Facility Operations

    • 12.1 Matters to consider when using the audit trail facility

      • 12.1.1 Considering audit target definitions (selecting events for which to output audit trails)

      • 12.1.2 Designing the disks used by the audit trail facility

      • 12.1.3 Estimating the size of audit trail data

      • 12.1.4 Estimating the compressibility of audit trail files

      • 12.1.5 Estimating the size of directories used by the audit trail facility

      • 12.1.6 Appointing auditors

      • 12.1.7 Considering the approach to take when attempts to write to the audit trail file fail

    • 12.2 Setting up the audit trail facility environment

      • 12.2.1 Normally terminating the HADB server

      • 12.2.2 Preparing the directories used by the audit trail facility

      • 12.2.3 Specifying server definition entries used by the audit trail facility

      • 12.2.4 Starting the HADB server normally (offline mode)

      • 12.2.5 Creating auditors

      • 12.2.6 Enabling the audit trail facility

      • 12.2.7 Defining audit targets

      • 12.2.8 Changing the HADB server operation mode (To normal mode)

    • 12.3 Scheduled operations for audit trail facility

      • 12.3.1 Moving audit trail files (to audit trail storage directory)

      • 12.3.2 Moving audit trail files (to audit trail long-term storage directory)

      • 12.3.3 Referencing audit trails (when using SELECT statements to reference audit trails)

      • 12.3.4 Referencing audit trails (when referencing audit trail data converted to CSV format)

    • 12.4 Non-scheduled operations for the audit trail facility

      • 12.4.1 Adding, deleting, and changing auditors (granting or revoking audit privileges)

      • 12.4.2 Swapping the current audit trail file

      • 12.4.3 Checking audit target definitions

      • 12.4.4 Changing audit target definitions

      • 12.4.5 Checking the operational status of the audit trail facility

    • 12.5 Troubleshooting the audit trail facility

      • 12.5.1 Steps to take when the disk containing the audit trail directory is full

      • 12.5.2 Steps to take when a failure occurs in the disk containing the audit trail directory

      • 12.5.3 Steps to take when there are insufficient file descriptors

    • 12.6 Stopping use of the audit trail facility

    • 12.7 Audit trail facility operation example

      • 12.7.1 Configuration of information analysis system operated by Company A

      • 12.7.2 Design

      • 12.7.3 Environment setup

      • 12.7.4 Scheduled operations

      • 12.7.5 Performing regular auditing

      • 12.7.6 Investigating security incidents

    • 12.8 Linkage between the audit trail facility and JP1/Audit Management - Manager

      • 12.8.1 Overview of linkage between the audit trail facility and JP1/Audit

      • 12.8.2 Format and output items of common format audit trail files

      • 12.8.3 Environment settings for linking the audit trail facility with JP1/Audit

      • 12.8.4 Operation methods available with linkage between the audit trail facility and JP1/Audit

      • 12.8.5 Performing auditing

    • 12.9 Audit target events and column structure of table function derived tables

      • 12.9.1 List of audit target events and output items

      • 12.9.2 Column structure of table function derived table when retrieving audit trails

      • 12.9.3 Audit trail output triggers and output items

    • 12.10 Notes about using the audit trail facility

      • 12.10.1 Situations where multiple audit trails are output for a single event

      • 12.10.2 Notes about audit trails output during command execution

  • 13. Tuning

    • 13.1 Tuning to improve processing performance

      • 13.1.1 Pre-reading of range indexes

      • 13.1.2 Re-evaluating the defined range indexes

      • 13.1.3 Re-evaluating the defined text indexes

      • 13.1.4 Reducing the HADB server startup time (by applying HugePages)

      • 13.1.5 Preventing SQL statement execution wait status from occurring

      • 13.1.6 Reducing the SQL statement processing time

      • 13.1.7 Expanding the user log buffers

      • 13.1.8 Expanding the initial size of user log files

      • 13.1.9 Re-evaluating the trigger size for reducing user log files

      • 13.1.10 Preventing automatic extension of DB areas

      • 13.1.11 Changing the file configuration of the work table DB area

    • 13.2 Tuning to shorten SQL statement execution time by re-examining the buffers

      • 13.2.1 Points to be checked before performing tuning

      • 13.2.2 Reducing the SQL statement execution time

      • 13.2.3 Reducing the execution time of an SQL statement that creates a global work table

      • 13.2.4 Reducing the execution time of an SQL statement that creates a local work table

      • 13.2.5 Reducing the execution time of SQL statements that perform table scans

    • 13.3 Tuning to shorten command execution time

      • 13.3.1 Reducing the adbimport command's execution time

      • 13.3.2 Reducing the execution time of the adbidxrebuild command

      • 13.3.3 Reducing the execution time of the adbgetcst command

      • 13.3.4 Reducing the execution time of the adbexport command

      • 13.3.5 Reducing the execution time of the adbmergechunk command

      • 13.3.6 Reducing the execution time of the adbarchivechunk command

    • 13.4 Tuning to reduce memory usage

      • 13.4.1 Reducing the usage of shared memory to which HugePages is applied

      • 13.4.2 Reducing memory usage by re-evaluating the global buffers

      • 13.4.3 Reducing memory usage by re-evaluating buffers for local work tables

    • 13.5 Tuning to shorten SQL statement execution time by re-examining the hash table area size

    • 13.6 Tuning to shorten SQL statement execution time by re-examining the hash group area size

    • 13.7 Tuning to shorten SQL statement execution time by re-examining the join order of INNER JOINs to which a hash join is applied

    • 13.8 Tuning to shorten SQL statement execution time by re-examining the hash filter area size

    • 13.9 Tuning to shorten SQL statement execution time by re-examining the table-definition pool size

  • 14. Error Handling

    • 14.1 Error-handling flow

      • 14.1.1 Steps to take when the HADB server terminated abnormally

      • 14.1.2 Steps to take when the HADB server did not terminate abnormally

    • 14.2 Collecting troubleshooting information (adbinfoget command)

    • 14.3 Deleting troubleshooting information (adbinfosweep command)

  • 15. Troubleshooting

    • 15.1 Application-related problems

      • 15.1.1 Steps to take when an application does not terminate or terminates abnormally

      • 15.1.2 Steps to take when an application cannot be executed (when the KFAA40005-E message is output)

      • 15.1.3 Steps to take when connection from the application program to the HADB server takes time

    • 15.2 Command-related problems

      • 15.2.1 Steps to take when a command results in a time-out

      • 15.2.2 Steps to take when a command cannot be executed (when the KFAA40005-E message is output)

      • 15.2.3 Steps to take when the adbimport or adbidxrebuild command cannot be re-executed

      • 15.2.4 Steps to take when the adbunarchivechunk command cannot be re-executed

      • 15.2.5 Steps to take in the event of a shortage of disk space for storing temporary work files during command execution

    • 15.3 Problems related to free space on the disk

      • 15.3.1 When a free space shortage is caused by an increase in the size of the DB area files

      • 15.3.2 When a free space shortage is caused by failed DB area automatic extension

      • 15.3.3 When a free space shortage is caused by an increase in the size of files other than the DB area files

    • 15.4 Disk-related problems

      • 15.4.1 Recovering the database

      • 15.4.2 Recovering the server directory

      • 15.4.3 Recovering the client directory

    • 15.5 Problems related to files under the DB directory

      • 15.5.1 Steps to take when a failure occurs in a DB area file

      • 15.5.2 Steps to take when a problem occurs in a system log file

    • 15.6 Memory-related problems

      • 15.6.1 Steps to take when a memory shortage occurs during HADB server startup

      • 15.6.2 Steps to take when a memory shortage occurs during execution of an SQL statement or command

    • 15.7 Problems related to DB areas

      • 15.7.1 Steps to take when a data DB area becomes full

      • 15.7.2 Steps to take when a data DB area can no longer be added

      • 15.7.3 Steps to take when a data DB area can no longer be expanded

    • 15.8 Problems related to base tables

      • 15.8.1 Steps to take when a base table becomes non-updatable

      • 15.8.2 When a column cannot be added to a base table

    • 15.9 Problems related to B-tree indexes

      • 15.9.1 Steps to take when unfinished status is applied to a B-tree index

      • 15.9.2 Steps to take when the uniqueness constraint is violated (when the KFAA61205-W message is output)

    • 15.10 Problems related to text indexes

      • 15.10.1 Steps to take when unfinished status is applied to a text index

    • 15.11 Problems related to range indexes

      • 15.11.1 Steps to take when unfinished status is applied to a range index

    • 15.12 Problems related to the background-import facility

      • 15.12.1 Reducing the number of chunks that were created during background import

      • 15.12.2 Increasing the maximum number of chunks that can be created during background import

      • 15.12.3 Steps to take when the number of chunks that are created during background import cannot be changed

    • 15.13 Problems related to archive directories

      • 15.13.1 Steps to take when a failure occurs in an archive file

      • 15.13.2 Steps to take if free space in the archive directory is insufficient

    • 15.14 Problems related to synonym dictionary files

      • 15.14.1 Steps to take when a failure occurs in a synonym dictionary file

      • 15.14.2 Steps to take if free space in the directory for storing synonym dictionary files is insufficient

      • 15.14.3 Steps to take if synonym dictionary files or their storage directory is accidentally deleted

    • 15.15 Problems related to unload files

      • 15.15.1 Steps to take in the event of a shortage of disk space for storing unload files

    • 15.16 Problems related to the message log file

      • 15.16.1 Releasing the message log file from fall-back mode

    • 15.17 Problems related to restart of the HADB server

      • 15.17.1 Steps to take when the processing time for restarting the HADB server takes too long

• Part 6: Multi-Node Function

  • 16. Operations When Using the Multi-Node Function

    • 16.1 Notes on reading this chapter

    • 16.2 System configuration example that uses the multi-node function

      • 16.2.1 Prerequisite software program

      • 16.2.2 Server configuration

      • 16.2.3 Network configuration

      • 16.2.4 Storage configuration

    • 16.3 Building a system that uses the multi-node function

      • 16.3.1 Installing HA Monitor

      • 16.3.2 Installing HADB server and setting up an environment

      • 16.3.3 Installing HADB client and setting up the environment

      • 16.3.4 Setting up an HA Monitor environment

      • 16.3.5 Creating server definitions on all nodes

      • 16.3.6 Creating client definitions

      • 16.3.7 Environment settings when using the function for centrally managing client definitions

      • 16.3.8 Creating a database

    • 16.4 Starting and terminating HADB servers in the multi-node configuration

      • 16.4.1 Starting the HADB servers in the multi-node configuration

      • 16.4.2 Terminating HADB servers in the multi-node configuration

      • 16.4.3 HADB server operation modes when the multi-node function is used

    • 16.5 Application operations (when the multi-node function is being used)

      • 16.5.1 Connecting to the HADB server

      • 16.5.2 Maximum number of concurrent connections when the multi-node function is used

      • 16.5.3 Node that executes transactions

      • 16.5.4 When a node failure occurs

    • 16.6 Locking operations (when the multi-node function is being used)

    • 16.7 Switching over the master node by using a command

    • 16.8 Backing up a database (when the multi-node function is being used)

      • 16.8.1 Backup acquisition method

      • 16.8.2 Recovering a database from a backup

      • 16.8.3 Backup operation example (using OS commands)

      • 16.8.4 Backup operation example (using ShadowImage)

    • 16.9 Status monitoring (when the multi-node function is being used)

      • 16.9.1 Checking information on all nodes

      • 16.9.2 Checking the HADB server's status

      • 16.9.3 When application or command execution takes a long time

      • 16.9.4 When startup or termination processing of the HADB server takes a long time

      • 16.9.5 Checking the status of the HADB server on each node

      • 16.9.6 Checking the memory usage

    • 16.10 DB area operations (when the multi-node function is being used)

      • 16.10.1 Global buffer allocation

      • 16.10.2 Checking the database status and usage

      • 16.10.3 Adding, deleting, or expanding data DB areas (when the multi-node function is being used)

      • 16.10.4 Changing the storage location of DB areas

      • 16.10.5 Operating work table DB areas (when the multi-node function is being used)

      • 16.10.6 Operation when adding disks

    • 16.11 Schema, table, and index operations (when the multi-node function is being used)

      • 16.11.1 Schema operation (when the multi-node function is being used)

      • 16.11.2 Base table operations (when the multi-node function is being used)

      • 16.11.3 Viewed table operations (when the multi-node function is being used)

      • 16.11.4 Index operations (when the multi-node function is being used)

      • 16.11.5 Working with multi-chunk tables (when the multi-node function is being used)

      • 16.11.6 Operating archivable multi-chunk tables (when the multi-node function is used)

      • 16.11.7 Reorganizing system tables (when the multi-node function is used)

    • 16.12 System log operations (when the multi-node function is being used)

    • 16.13 Statistical information operations (when the multi-node function is being used)

    • 16.14 Tuning (when the multi-node function is being used)

    • 16.15 Operations when a node failure occurs

      • 16.15.1 When a node failure occurs on the master node

      • 16.15.2 When a node failure occurs on a slave node

      • 16.15.3 Returning a node to the multi-node configuration

    • 16.16 Troubleshooting (when the multi-node function is being used)

      • 16.16.1 Problems related to startup or termination of the HADB servers in the multi-node configuration

      • 16.16.2 Application-related problems (when the multi-node function is being used)

      • 16.16.3 Command related problems (when the multi-node function is being used)

      • 16.16.4 Problems related to DB areas (when the multi-node function is being used)

      • 16.16.5 Problems related to files in the DB directory (when the multi-node function is being used)

      • 16.16.6 Problems related to files in the server directory (during installation) (when the multi-node function is being used)

      • 16.16.7 Problems related to files in the server directory (during operation) (when the multi-node function is being used)

      • 16.16.8 Problems related to files in the client directory (when the multi-node function is being used)

      • 16.16.9 OS-related problems (when the multi-node function is being used)

      • 16.16.10 Hardware-related problems (when the multi-node function is being used)

      • 16.16.11 Problems related to HA Monitor (when the multi-node function is being used)

      • 16.16.12 Problems related to SQL statements that create work tables (when the multi-node function is being used)

      • 16.16.13 Problems related to synonym dictionary files (when the multi-node function is being used)

    • 16.17 Adding or deleting nodes

      • 16.17.1 Adding nodes

      • 16.17.2 Notes on executing the adbinit command when adding nodes

      • 16.17.3 Deleting nodes

    • 16.18 Changing the host name or IP address of the server machine's OS (when the multi-node function is being used)

    • 16.19 Migrating to a system that uses the multi-node function

      • 16.19.1 Terminating the HADB server normally

      • 16.19.2 Backing up the server directory

      • 16.19.3 Backing up the DB directory

      • 16.19.4 Upgrading the HADB server version

      • 16.19.5 Installing HA Monitor and the HADB server

      • 16.19.6 Setting up the nodes

      • 16.19.7 Preparing the DB directory

      • 16.19.8 Preparing to use the audit trail facility

      • 16.19.9 Starting the HADB servers in the multi-node configuration

      • 16.19.10 Preparing for synonym search operations

    • 16.20 Upgrading the HADB server version (when the multi-node function is used)

    • 16.21 Swapping the HADB server with its revised version (when the multi-node function is used)

      • 16.21.1 Normally terminating and then swapping the HADB server in a multi-node configuration

      • 16.21.2 Performing swapping on a per-node basis

    • 16.22 Notes about using SQL tracing (when the multi-node function is being used)

    • 16.23 Handling of data retrieval from CSV files (when the multi-node function is being used)

    • 16.24 Performing synonym search operations (when using the multi-node function)

      • 16.24.1 Preparing for synonym search operations

      • 16.24.2 Performing synonym searches

      • 16.24.3 Registering or deleting synonym dictionaries

      • 16.24.4 Adding or deleting synonyms

      • 16.24.5 Synchronizing synonym dictionary files

    • 16.25 Audit trail facility operations (when the multi-node function is being used)

      • 16.25.1 Setting up the audit trail facility environment

      • 16.25.2 Operating the audit trail facility

      • 16.25.3 Linkage with JP1/Audit Management - Manager (when the multi-node function is being used)

    • 16.26 Updated-row columnizing facility operations (when the multi-node function is being used)

    • 16.27 Notes on using the multi-node function

• Part 7: Cold Standby Configuration

  • 17. Operations When Using the Cold Standby Configuration

    • 17.1 Notes on reading this chapter

    • 17.2 Example of system configuration using the cold standby configuration

      • 17.2.1 Prerequisite software program

      • 17.2.2 Server configuration

      • 17.2.3 Network configuration

      • 17.2.4 Storage configuration

    • 17.3 Building a system with the cold standby configuration

      • 17.3.1 Installing HA Monitor

      • 17.3.2 Installing HADB server and setting up an environment

      • 17.3.3 Installing HADB client and setting up the environment

      • 17.3.4 Setting up an HA Monitor environment

      • 17.3.5 Creating server definitions on both HADB servers

      • 17.3.6 Creating client definitions

      • 17.3.7 Creating a database

    • 17.4 Starting and terminating the cold standby configuration

      • 17.4.1 How to start the cold standby configuration

      • 17.4.2 How to terminate the cold standby configuration

    • 17.5 Application operations (in the case of the cold standby configuration)

      • 17.5.1 Connecting to the HADB server

      • 17.5.2 In the event of a failure in the active system

    • 17.6 Backing up a database (in the case of the cold standby configuration)

      • 17.6.1 Backup acquisition method

      • 17.6.2 Recovering a database from a backup

      • 17.6.3 Backup operation example (using OS commands)

      • 17.6.4 Backup operation example (using ShadowImage)

    • 17.7 Status monitoring (in the case of the cold standby configuration)

      • 17.7.1 Checking the memory usage

    • 17.8 DB area operations (in the case of the cold standby configuration)

      • 17.8.1 Adding, deleting, or expanding data DB areas (in the case of the cold standby configuration)

      • 17.8.2 Work table DB area operations (in the case of the cold standby configuration)

    • 17.9 Table and index operations (in the case of the cold standby configuration)

      • 17.9.1 Base table operations (in the case of the cold standby configuration)

      • 17.9.2 Index operations (in the case of the cold standby configuration)

    • 17.10 DB directory operations (in the case of the cold standby configuration)

    • 17.11 Statistical information operations (in the case of the cold standby configuration)

    • 17.12 Operations when a failure occurs

      • 17.12.1 In the event of a failure in the active system

      • 17.12.2 In the event of a failure in the standby system

      • 17.12.3 In the event of a communication failure between the active system and the standby system

      • 17.12.4 Returning a system to the cold standby configuration

    • 17.13 Planned hot standby in the cold standby configuration

    • 17.14 Troubleshooting (in the case of the cold standby configuration)

      • 17.14.1 Problems related to startup or termination of the cold standby configuration

      • 17.14.2 Application-related problems (in the case of the cold standby configuration)

      • 17.14.3 Command related problems (in the case of the cold standby configuration)

      • 17.14.4 Problems related to files in the DB directory (in the case of the cold standby configuration)

    • 17.15 Changing the host name or IP address of the server machine's OS (in the case of the cold standby configuration)

    • 17.16 Upgrading the HADB server version (in the case of the cold standby configuration)

    • 17.17 Swapping the HADB server with its revised version (in the case of the cold standby configuration)

      • 17.17.1 Performing a normal termination of a cold standby configuration HADB server and then swapping

      • 17.17.2 Performing swapping on a per-host basis

    • 17.18 Operation when performing synonym searches in a cold standby configuration

      • 17.18.1 Preparing the file system for storing synonym dictionary files

      • 17.18.2 Changing the specification of the servers file

      • 17.18.3 Building the file system for storing synonym dictionary files

      • 17.18.4 Mounting the file system for storing synonym dictionary files

    • 17.19 Operation when using the audit trail facility in a cold standby configuration

      • 17.19.1 Preparing the file system where the audit trail directory will be created

      • 17.19.2 Preparing the file system where the audit trail storage directory will be created

      • 17.19.3 Changing the specification of the servers file

      • 17.19.4 Linkage with JP1/Audit Management - Manager (in the case of the cold standby configuration)

    • 17.20 Operation when using the updated-row columnizing facility in a cold standby configuration

• Appendixes

  • A. HADB Server Directory Configuration

    • A.1 Configuration of the server directory (for installation)

    • A.2 Configuration of the server directory (for operation)

    • A.3 DB directory configuration

  • B. Dictionary Tables

    • B.1 Dictionary table overview

    • B.2 Content of SQL_TABLES

    • B.3 Content of SQL_COLUMNS

    • B.4 Content of SQL_DIV_TABLE

    • B.5 Content of SQL_INDEXES

    • B.6 Content of SQL_DIV_INDEX

    • B.7 Content of SQL_DBAREAS

    • B.8 Content of SQL_SCHEMATA

    • B.9 Content of SQL_VIEWS

    • B.10 Content of SQL_VIEW_TABLE_USAGE

    • B.11 Content of SQL_DEFINE_SOURCE

    • B.12 Content of SQL_DEFINE_ENVIRONMENT

    • B.13 Content of SQL_USERS

    • B.14 Content of SQL_TABLE_CONSTRAINTS

    • B.15 Content of SQL_INDEX_COLINF

    • B.16 Content of SQL_KEY_COLUMN_USAGE

    • B.17 Content of SQL_REFERENTIAL_CONSTRAINTS

    • B.18 Content of SQL_TABLE_PRIVILEGES

    • B.19 Content of SQL_AUDITS

    • B.20 Base tables that are reserved when dictionary tables are referenced

    • B.21 B-tree indexes of dictionary tables (base tables)

    • B.22 Searching a dictionary table

  • C. System Tables

    • C.1 System table overview

    • C.2 Content of STATUS_TABLES

    • C.3 Content of STATUS_COLUMNS

    • C.4 Content of STATUS_INDEXES

    • C.5 Content of STATUS_CHUNKS

    • C.6 Content of STATUS_SYNONYM_DICTIONARIES

    • C.7 Base tables that are reserved when system tables are referenced

    • C.8 B-tree indexes of system tables (base tables)

    • C.9 Searching system tables

  • D. Maximum and Minimum Values in HADB

    • D.1 Maximum and minimum values related to system configuration

    • D.2 Maximum and minimum values related to database

  • E. Process That Starts When the HADB Server Starts

• Glossary

• Index

To Page Top