(a) Number of files created

An index information file is created for each RDAREA that stores the plug-in index. Therefore, the number of index information files created equals the number of RDAREAs that store the plug-in index updated by the UAP.

(b) Names of created files

The names to be assigned to index information files are determined by the index identifiers and RDAREA names (according to the rules shown below). These index information file names are specified in the control statements file of the database reorganization utility (pdrorg command).

Condition	Index information file name
When all the following conditions are satisfied: index-identifier-length + RDAREA-name-length < 30 bytes The index identifier and RDAREA name are character strings, as explained in the note below.	index-identifier.RDAREA-name
When all the following conditions are satisfied: index-identifier-length + RDAREA-name-length 30 bytes The index identifier and RDAREA name are character strings, as explained in the note below.	index-ID.RDAREA-ID.leading-portion-of-index-identifier#
The index identifier and RDAREA name consist of character strings other than as explained in the note below.	index-ID.RDAREA-ID

Note

A character string consists of the characters A to Z, a to z, 0 to 9, period (.), underline (_), and at mark (@). We recommend that index identifiers and RDAREA names be assigned according to this rule.

#: First 12 bytes of the index identifier

When the inner replica facility is being used

When a replica RDAREA contains a plug-in index, the index information file name is determined according to the following conditions:

Condition	Index information file name
The name of the directory containing the index information file is specified in the pd_plugin_ixmk_dir operand.	index-identifier.original-RDAREA-name.RDAREA-generation-number
Both of the following conditions are satisfied: index-identifier-length = RDAREA-name-length < 27 bytes The index identifier and the RDAREA name are character strings, as explained in the note below.
The following condition is satisfied: index-identifier-length + RDAREA-name-length 27 bytes The index identifier and the RDAREA name are character strings, as explained in the note below.	index-ID.RDAREA-ID.leading-portion-of-index-identifier#.RDAREA-generation-number
The index identifier or the RDAREA name consists of a character string other than that explained in the note below.	index-ID.RDAREA-ID.RDAREA-generation-number

Note

A character string consists of the characters A to Z, a to z, 0 to 9, period (.), underline (_), and at mark (@). We recommend that index identifiers and RDAREA names be assigned according to this rule.

#: First 9 bytes of the index identifier

(c) Size of a created file

The size of an index information file will be large. The size of one file can be determined from the following formula (note that if you specify a HiRDB file system area name in the pd_plugin_ixmk_dir operand, the size of the file must be rounded up to a multiple of 1,024 bytes):

(12 + E) (A + B + C D) + 1,024 (bytes)

A: Number of row data items added (number of data items updated by INSERT statement)

B: Number of row data items updated (number of data items updated by UPDATE statement)

C: Number of UAPs specifying delayed batch creation of plug-in index

D: Number of COMMIT statements issued in the UAP

E: Depends on the type of plug-in; for the HiRDB Text Search Plug-in, the value is 27.

(d) File deletion

Index information files are deleted automatically by HiRDB when they are no longer needed. The files are deleted at the following times:

• When batch creation of plug-in index is completed successfully
• When re-creation of plug-in index has been executed

The files are deleted automatically only when this processing is executed; otherwise, such files must be deleted manually by the user.

Once the UAP executes, conformity is lost between the table's data and the plug-in index's data until batch creation of plug-in index is completed. Thus, a backup of the data should not be made during this time.

If more than one UAP specifying delayed batch creation of plug-in index is executed on the same row-partitioned table, deadlock might occur on the index information files.

Delayed batch creation of plug-in index is not supported for stored procedures and stored functions created under HiRDB Version 5.0 05-02 or earlier. If an attempt is made in such a case to execute delayed batch creation of plug-in index by specifying PDPLGIXMK=YES, the KFPA11537-E message will be output and an error will result. When this happens, take one of the following actions.

• To execute delayed batch creation of a plug-in index
  Execute ALTER ROUTINE or ALTER PROCEDURE on the stored procedures and stored functions that update the plug-in index.
  
• To not execute delayed batch creation of a plug-in index
  Execute the UAP with PDPLGIXMK=NO specified.