Upgrading an ArcSDE geodatabase for DB2 on z/OS

You must upload the JCL script via FTP to the z/OS machine and run it. Then run the Upgrade Geodatabase geoprocessing tool from the Windows client.

  1. Make a backup of the subsystem that comprises the ArcSDE geodatabase.
  2. Uninstall ArcSDE from the Windows client computer.
  3. Install the new release of ArcSDE on the Windows client computer.
  4. Update the ESRIOBJ.XMIT and ESRIDBRM.XMIT files on DB2. New copies of these files are in the SDEHOME\tools\db2zos directory. To load them into DB2, do the following:
    1. As a SYSADM, upload the datasets to the z/OS system using FTP.

      The data is in Time Sharing Option/Extension (TSO/E) Transmit/Receive format and must be uploaded to the z/OS using a BINARY transfer.

    2. Assuming FTP is used for the transfer, the two datasets must eventually be defined on z/OS with the following characteristics:


      Typically, FTP systems are setup such that for any data that is received and results in a new dataset, the resultant new dataset will not be in the required format. However, that can be changed by using FTP commands. Make sure the FTP is in binary mode, then type the command appropriate to your operating system.

      The command to transfer via FTP from Windows is as follows:

      quote site recfm=fb lrecl=80 blksize=3120

      If you are logged onto the z/OS and pull the files using FTP, the command is as follows:

      locsite recfm=fm lrecl=80 blksize=3120

    3. The datasets must be TSO/E RECEIVED by a user account on the z/OS system. Log onto a SYSADM user account ID on the z/OS system and open option 6 (the command panel) of Interactive System Productivity Facility (ISPF).
    4. The two datasets that are uploaded are ESRIOBJ.XMIT and ESRIDBRM.XMIT, so issue the following TSO/E commands, one at a time, to receive the datasets:


      For each of these, a command prompt for specification of dataset creation overrides is returned. If you do not provide any overrides, two datasets are created under the high-level qualifier (HLQ) of the User-ID with which you logged in.

      You should now have two corresponding datasets in SCR03:


    5. Review the names of the datasets. If they are correct, they are to be referenced in the ESRI UDF installation job that is uploaded in the next step.
  5. Check the function, SDE_V_NOT_DEFAULT by issuing the following SQL expression:
    SELECT count(*) 
    FROM sysibm.sysroutines
    WHERE name like 'SDE_V_NOT_DEFAULT'
  6. If one record is returned from the SQL run in the previous step, proceed to step 8.
  7. If no records are returned from the SQL run, submit the ESRIS2D step of the ESRIUDFI JCL script provided in %SDEHOME%\tools\db2zos.

    You must customize the ESRIUDFI script using information specific to your implementation, then upload and run the script on z/OS. The script itself includes instructions.

    Running the script re-creates the UDF.

  8. Install the new release of ArcGIS Desktop on the Windows client computer.

    See the installation guide included with ArcGIS Desktop for instructions.

  9. Start ArcCatalog by clicking Start > All Programs > ArcGIS > ArcCatalog 10.
  10. Expand the Database Connections folder in the Catalog tree.
  11. You must make a direct connection to the geodatabase as the ArcSDE administrator. If such a connection file does not already exist under Database Connections, create one by double-clicking Add Spatial Database Connection and providing connection information.
  12. Right-click the geodatabase connection in the Catalog tree and click Properties.
  13. Click the General tab.

    If an upgrade is needed, the Upgrade Geodatabase button is active.

    If the Upgrade Geodatabase button is not active, it could be because the connecting client is at the same release as the ArcSDE geodatabase, your DBMS is not at a supported upgradable release, you are using an ArcSDE service connection rather than a direct connection to the geodatabase, or you are connecting from an ArcGIS Desktop client running under an ArcView license.

  14. Click the Upgrade Geodatabase button.

    The Upgrade Geodatabase geoprocessing tool opens. The Input geodatabase text box is prepopulated with the geodatabase connection information when launched using the Upgrade Geodatabase button.

  15. NoteNote:

    You cannot run the Upgrade Geodatabase tool if any other geoprocessing tools are currently running as background processes on the client machine.

  16. Esri recommends that you leave both the Pre-requisites check and Upgrade geodatabase options checked on the Upgrade Geodatabase geoprocessing tool. That way, the tool checks to see if the prerequisites to upgrade have been met before continuing with the geodatabase upgrade.

    The prerequisite check detects other active connections to the geodatabase, whether the connecting user has sufficient privileges to upgrade the geodatabase, that the database can support XML columns, and makes sure all datasets can be opened. If any prerequisites are not met, the tool terminates. You must correct any problems before you run the upgrade procedure again.

    The results of this check are reported on the geoprocessing tool dialog box and the GDBUpgrade<#>.log, which can be found in the system TEMP directory.

  17. Click OK to start the checks and upgrade.
  18. If all checks are passed, the tool proceeds with the upgrade. The status for the prerequisites check and the upgrade are shown on the geoprocessing tool progress dialog box as well as the GDBUpgrade<#>.log. Additional information can be found in the sdesetup log, which is also created in the system TEMP directory.
  19. When the tool successfully completes, click Close to close the geoprocessing tool progress dialog box.

Your geodatabase is upgraded to the latest release.

Related Topics