A quick tour of setting up a geodatabase in DB2

Before you can create a geodatabase in an IBM DB2 database management system (DBMS), you must first install the DB2 software, configure the DBMS, create a database, and register it with the Spatial Extender.

Configuring the DBMS involves setting up storage spaces for the tables, indexes, and files that are stored in the database instance and providing adequate memory allocation. You should give consideration to the names, types, and locations of tables, indexes, and storage spaces you create; how large to make your backup log files; and what size to make the temporary space. As the database administrator, you know the naming conventions used at your site as well as what type of configuration your site requires.

You must also decide in what language your data will be stored. If you want to set up your database to use languages other than the default language of the DBMS, you must configure your DBMS for that.

Once the database is ready, install ArcSDE. This gets you the files needed to create and configure the geodatabase in the DB2 database.

See System requirements for ArcSDE for DB2 to see the requirements to install ArcSDE.

The following are summaries of the steps you take to set up a geodatabase in DB2 on various operating systems. These summaries contain links to more information for instructions specific to ArcSDE. For general DB2 tasks, such as creating users, see your DB2 documentation.

Summary for setting up a geodatabase in DB2 on Linux or UNIX

1. Create an operating system (OS) account with the user name sde.
2. Install the DB2 DBMS software and the Spatial Extender module.
3. Create a database. See Creating a DB2 database on Linux or UNIX.
4. Configure the database and DB2 instance, including creating table spaces, setting heap sizes, and setting up transaction logs. See your DB2 documentation for information on configuring the database.
5. Grant DBADM on the database to the sde user.
6. Set variables for the sde user. See Setting variables for the sde OS user on Linux or UNIX for more information.
7. Spatially enable the database using Spatial Extender tools.
8. Install ArcSDE. See Installing ArcSDE for DB2 on Linux or UNIX.
9. Alter the parameters under the DATA_DICTIONARY keyword in the dbtune.sde file to specify a table space for specific ArcSDE system tables. If you do not, the default table space will be used, which is usually too small for this.
   Tip:

   While altering the dbtune.sde file for the repository tables, you could also alter other parameters for user data.

10. If you will use an ArcSDE service to connect to the geodatabase, add an entry for the service in the operating system services file and the services file in the $SDEHOME\etc directory.
11. Run the sdesetup command to create the geodatabase and authorize it with an ArcGIS Server Enterprise license. See Creating a geodatabase in DB2 on Linux or UNIX.
12. Run the sdemon command to start a service if you are using one. See Starting a local ArcSDE service on Linux or UNIX or Starting a remote ArcSDE service on UNIX for instructions.
13. Create other users and grant them permissions in the database.
14. If you will be using direct connections to the geodatabase, install the DB2 client on all client computers from which a direct connection will be made and configure the client.
15. If ArcSDE and DB2 are on different servers, set the SDE_DATABASE environment variable in the dbinit.sde file to your remote DB2 database on the machine where ArcSDE is installed. See Installing DB2 and ArcSDE on separate servers for more information.

Summary for setting up a geodatabase in DB2 on Windows

1. Create an operating system account with the user name sde.
2. Install the DB2 DBMS software and the Spatial Extender module.
3. Create a database. See Creating a DB2 database on Windows.
4. Configure the database and DB2 instance, including creating table spaces, setting heap sizes, and setting up transaction logs. See your DB2 documentation for information on configuring the database.
5. Grant DBADM on the database to the sde user.
6. Spatially enable the database using Spatial Extender tools. See Spatially enabling a DB2 database and your DB2 documentation for details.
7. Install ArcSDE using the installation wizard. See Installing ArcSDE for DB2 on Windows.
8. Alter the parameters under the DATA_DICTIONARY keyword in the dbtune.sde file to specify a table space for specific ArcSDE system tables. If you do not, the default table space will be used, which is usually too small for this.
   Note:

   You must alter the dbtune.sde file before creating a geodatabase (step 9) to specify adequate table space for the system tables affected by the parameters under the DATA_DICTIONARY configuration keyword.

9. Run the ArcSDE for DB2 Post Installation wizard to create the geodatabase and authorize it with an ArcGIS Server Enterprise license. See Creating a geodatabase in DB2 on Windows.
10. If you plan to use an ArcSDE service to make connections to the geodatabase, use the Post Installation wizard to create and start the service.
11. Create other users and grant them permissions in the database.
12. If you will be using direct connections to the geodatabase, install the DB2 client on all client computers from which a direct connection will be made and configure the client.
13. If ArcSDE and DB2 are on different servers, set the SDE_DATABASE environment variable in the dbinit.sde file to your remote DB2 database on the machine where ArcSDE is installed. See Installing DB2 and ArcSDE on separate servers for more information.

Summary for installing ArcSDE for DB2 on z/OS and creating a geodatabase

Note:

When DB2 is installed on an IBM Z operating system (z/OS), you must install ArcSDE on a remote Windows server. From this and all other connecting client machines, you make a direct connection to the geodatabase on z/OS.

1. Install and configure the DB2 DBMS on z/OS.
2. Install the DB2 client on the Windows client machine where ArcSDE will be installed. See Setting up a direct connection to DB2 and your DB2 documentation.
3. Create a local sde user on the Windows client.
4. Configure the ZPARMs on DB2 and refresh DB2 with the setting. See Configuring ZPARMs to use ArcSDE with DB2 on z/OS.
5. Use the Resource Access Control Facility (RACF) to create a user, sde, in z/OS for ArcSDE administration and enable secondary authorization IDs (RACF groups). See Creating an sde user on IBM z/OS.
6. Transfer z/OS specific files to the target multiple virtual storage (MVS) system. See Transferring files to z/OS for ArcSDE setup.
7. Submit the JCL script, ESRIUDFI, to create the storage groups, databases, and user-defined functions (UDFs) for ArcSDE. See Creating databases in DB2 on z/OS.
8. Spatially enable the database subsystem. See the DB2 z/OS documentation for details.
9. Grant privileges to the sde user and ArcGIS user group on DB2. See Granting permissions and privileges to sde and the ArcGIS user group in DB2 on z/OS.
10. Install ArcSDE on the Windows client using the wizard. See Installing ArcSDE for DB2 on Windows.
11. Alter the parameters in the dbtune.sde and giomgr.defs file.
    Tip:

    While altering the dbtune.sde file for the repository tables, you could also alter other parameters for user data.

    See Customizing ArcSDE files before creating a geodatabase in DB2 on z/OS.
12. Run the sdesetup command from the Windows client to create the geodatabase in the DB2 DBMS and authorize it with an ArcGIS Server Enterprise license. See Creating a geodatabase in DB2 for z/OS.
13. Submit the JCL script, ESRIUDFB, that binds the DBRMs required to run the ESRI UDFs.
    Tip:

    The DBRM was loaded when you completed this step: Transferring files to z/OS for ArcSDE setup.

14. Verify the installation. See Verifying the geodatabase was created in DB2 on z/OS.
15. Create ArcSDE users for the usage of ArcSDE and ArcGIS applications. See Creating nonadministrative users in DB2 on z/OS.
16. Install and configure the DB2 client on all client machines.
17. Create local users on the client machines to access the geodatabase through direct connections.