When converting HiRDB from 32-bit to 64-bit mode, execute the pdobjconv command. This command converts the information in the following dictionaries to support 64-bit mode. If you do not execute this command after upgrading your HiRDB to 64-bit mode, the existing view tables, procedures, and functions will be unusable.
- View analysis information
- SQL objects for procedures
- SQL objects for functions
- Trigger SQL objects
When upgrading from 32-bit to 64-bit mode, HiRDB automatically executes the pdobjconv command (after executing the pdvrup command). Therefore, there is usually no need for the user to execute this command.
When you execute the pdobjconv command, the execution result (SQL object conversion information) is output to the following file:
- pdobjconv command automatically executed by HiRDB
$PDDIR/spool/pdobjconv.log
- pdobjconv command executed by the user
pdobjconv.log in the current directory
The following shows an output example of SQL object conversion information:
<< SQL OBJECT Converter >> [15]START TIME : YYYY/MM/DD HH:MM:SS
[1]VIEW DEF COUNT : 1
[2]PROCEDURE COUNT : 12
[3]FUNCTION COUNT : 1
[4]TRIGGER COUNT : 1
[5] [6] [7] [8]
*VIEW* INVALID : USER01.USER_VIEW01
KFPX21103-I...
[5] [6] [7] [8]
*PROCEDURE* VALID : MASTER.REGISTRY_DELETE_CONTEXT (REGISTRY_DELETE_CONTEXT)
KFPX21102-I...
*PROCEDURE* VALID : MASTER.REGISTRY_DELETE_KEY (REGISTRY_DELETE_KEY)
KFPX21102-I...
*PROCEDURE* VALID : MASTER.REGISTRY_GET_CONTEXT (REGISTRY_GET_CONTEXT)
KFPX21102-I...
*PROCEDURE* VALID : MASTER.REGISTRY_GET_LVALUE (REGISTRY_GET_LVALUE)
KFPX21102-I...
*PROCEDURE* VALID : MASTER.REGISTRY_GET_SVALUE (REGISTRY_GET_SVALUE)
KFPX21102-I...
*PROCEDURE* VALID : MASTER.REGISTRY_GET_VALUE_SIZE (REGISTRY_GET_VALUE_SIZE)
KFPX21102-I...
*PROCEDURE* VALID : MASTER.REGISTRY_NEW_CONTEXT (REGISTRY_NEW_CONTEXT)
KFPX21102-I...
*PROCEDURE* VALID : MASTER.REGISTRY_RESET_LVALUE (REGISTRY_RESET_LVALUE)
KFPX21102-I...
*PROCEDURE* VALID : MASTER.REGISTRY_RESET_SVALUE (REGISTRY_RESET_SVALUE)
KFPX21102-I...
*PROCEDURE* VALID : MASTER.REGISTRY_SET_LVALUE (REGISTRY_SET_LVALUE)
KFPX21102-I...
*PROCEDURE* VALID : MASTER.REGISTRY_SET_SVALUE (REGISTRY_SET_SVALUE)
KFPX21102-I...
*PROCEDURE* INVALID : USER01.USER_PROC01 (USER_PROC01)
KFPX21103-I...
[5] [6] [7] [8] [9]
*FUNCTION* INVALID : USER01.USER_FUNC01 (FUSER_FUNC010000000028)
KFPX21103-I...
[5] [6] [7] [8]
*TRIGGER* INVALID : USER01.(TRIG2002080112300000) ((TRIG2002080112300000))
KFPX21103-I...
<< RESULT REPORT >> [16]ENDED TIME : 1999/08/13 10:46:17
[10] [11] [12] [13] [14]
= RESOURCE == = SUCCESS === = FAILURE === = PASS ====== = TOTAL =====
*VIEW* 1 0 0 1
*PROCEDURE* 1 0 11 12
*FUNCTION* 1 0 0 1
*TOTAL* 3 0 11 14 |
- Explanation
- Number of view tables
- Number of procedures
- Number of functions
- Number of triggers
- SQL object ID character string:
VIEW: View table
PROCEDURE: Procedure
FUNCTION: Function
TRIGGER: Trigger
- SQL object status:
INVALID: Invalid
VALID: Valid
- Authorization identifier
- View table name, procedure name, or function name
- Specified name
- SQL object ID character string:
VIEW: View table
PROCEDURE: Procedure
FUNCTION: Function
TRIGGER: Trigger
- Number of SQL objects that were re-registered successfully
- Number of SQL objects resulting in a re-registration error
- Number of SQL objects that were not re-registered
- Total number of SQL objects
- pdobjconv command start time
- pdobjconv command termination time