The names of all RDAREAs, except for the master directory RDAREA, can be modified.

When an RDAREA name is modified, the RDAREA names specified in definition information and UAPs must also be modified. Therefore, before changing an RDAREA name, identify all locations where the RDAREA whose name is to be changed is specified.

The following table shows the tasks that are required when an RDAREA name is modified. Besides the items listed in this table, if there are other locations where the RDAREA name is specified, it must be changed there as well.

Table 15-1 Tasks that are required when an RDAREA name is modified

Item	Required task	Problem that occurs if the required task is not performed
pdbuffer operand in the server common definition	After HiRDB terminates normally, change the RDAREA name specified in the pdbuffer operand to the modified RDAREA name.	Following normal termination of HiRDB, if HiRDB is started normally without the RDAREA name having been modified, and if a global buffer has been specified with the -o option, that global buffer is allocated to the RDAREA with the modified name. Although this RDAREA can be accessed, processing performance might deteriorate. If no global buffer has been specified with the -o option, no global buffer is allocated to the RDAREA with the modified name. Consequently, any attempt to access the modified RDAREA causes an error.
pdlbuffer operand in the UAP environment definition	Change the RDAREA name specified in the pdlbuffer operand to the modified RDAREA name.	Exclusive use of the global buffer or locking of buffers by other UAPs might cause wait status, resulting in lower performance.
SQL procedure statement	If the warning message KFPX24238-W is issued when the database structure modification utility (pdmod) is executed, re-create the routine or trigger#.	The SQL object is invalid during routine or trigger execution, resulting in an error.
UAP	Re-create the UAP in which the pre-modification RDAREA name is specified.	The UAP might not run normally.
Option of a command or utility, or a utility control statement	Change the specified RDAREA name to the modified RDAREA name.	The command or utility might not run normally.
Related program products	Change the specified RDAREA name to the modified RDAREA name. Examples Target definition of HiRDB Datareplicator Command argument of HiRDB Dataextractor RDAREA operation information about JP1/Performance Management - Agent Option for HiRDB, HiRDB file statistical information related to database operation, and information on the facility for predicting reorganization time Mapping between RDAREA names and disk in JP1/HiCommand Protection Manager for HiRDB	The related program product might not run normally.
Operation script	If an operation script is used, change the RDAREA name specified in the script to the modified RDAREA name.	The operation script might not run normally.

#: The following is the procedure for re-creating a routine:

1. Execute ALTER ROUTINE to re-create the routine or trigger.
   If a routine or trigger specifies the pre-modification RDAREA name within an SQL procedure statement, an error occurs during the execution of ALTER ROUTINE.
   
2. From ALTER ROUTINE, execute GET DIAGNOSTICS to verify the routine or trigger for which an error is shown in the diagnosticinformation.
3. Execute DROP PROCEDURE or DROP TRIGGER to delete the routine or error that caused the error.
4. Change the RDAREA name in the SQL procedure statement to the modified RDAREA name.
5. Execute CREATE PROCEDURE or CREATE TRIGGER to re-create the routine or trigger.

1. Before changing the name of an RDAREA, use the pdhold -c command to place it in shutdown and closed status. Note, however, that the data dictionary RDAREA and data directory RDAREA must be placed in shutdown and open status.
2. Before you can use the RDAREA whose name was changed, you must use the pdrels -o command to release the RDAREA from shutdown status and place it in open status.
3. If you use the database reorganization utility (pdrorg) to reorganize a table containing a LOB column, do not modify the name of the RDAREA that stores the LOB data after the data is unloaded and before it is reloaded. If the RDAREA name is modified before the data is reloaded, an error occurs during data reloading.
4. If you execute the database load utility (pdload) or database reorganization utility (pdrorg) in the index information output mode (-i n option) to create an index later, do not modify the name of the RDAREA that stores the index after the index information file is output but before an index is created. If the RDAREA name is modified before an index is created, an error occurs during index creation.
5. If you execute delayed batch creation of the plug-in index, do not modify the name of the RDAREA that stores the plug-in index. If the RDAREA name is modified before batch creation of the plug-in index, batch creation of the plug-in index cannot be executed.
6. If you execute updatable online reorganization, do not modify the names of related RDAREAs after the preparation starts and before the operation is completed. If the RDAREA name is modified, updatable online reorganization might not work normally. For details about preparation and operation, see the HiRDB Version 9 Staticizer Option Description and User's Guide.