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.

User with the DBA privileges

None

1. You can execute the pdobjconv command while HiRDB is active.
2. The pdobjconv command must be executed at the server machine that contains the single server or where the system manager is located.
3. To execute the pdobjconv command, the system RDAREAs must be open and in non-shutdown status.

1. If the user executes the pdobjconv command, the SQL object conversion information is created in the current directory. Therefore, the user executing this command must have the file creation privilege.
2. Do not execute more than one pdobjconv command at any one time.
3. If both the following conditions are satisfied, the results of searching the user-defined view table may not match before and after execution of the pdobjconv command:
   
   • Before migration, the view table was defined by means of the following procedure:
     1. The user defines a function.
     2. The function defined in step 1 is used to define a view table.
     3. The user who performed step 1 also defines another function with the same name and the same number of arguments.
     
   • After the view table satisfying the above condition was defined, the pdobjconv command was executed.
4. You can determine the result of the pdobjconv command with the following return code:
   

   0

   The pdobjconv command terminated normally.

   4

   Although there was a warning error, the pdobjconv command terminated normally.

   8

   Conversion failed on some SQL objects. Check the message or SQL object conversion information and eliminate the cause of the error.

   Alternatively, an execution error occurred on the pdobjconv command.

   12

   The pdobjconv command terminated abnormally. Check the message or SQL object conversion information and eliminate the cause of the error.

   If the pdobjconv command is cancelled with the pdcancel command or an error occurs on the pdobjconv command process, code 12 is returned.

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

1. Number of view tables
2. Number of procedures
3. Number of functions
4. Number of triggers
5. SQL object ID character string:
   VIEW: View table
   PROCEDURE: Procedure
   FUNCTION: Function
   TRIGGER: Trigger
   
6. SQL object status:
   INVALID: Invalid
   VALID: Valid
   
7. Authorization identifier
8. View table name, procedure name, or function name
9. Specified name
10. SQL object ID character string:
    VIEW: View table
    PROCEDURE: Procedure
    FUNCTION: Function
    TRIGGER: Trigger
    
11. Number of SQL objects that were re-registered successfully
12. Number of SQL objects resulting in a re-registration error
13. Number of SQL objects that were not re-registered
14. Total number of SQL objects
15. pdobjconv command start time
16. pdobjconv command termination time