Running a geocoder in batch mode

When you run a geocoder in batch mode, you translate multiple records into spatial data that goes into a specific column.

Before you begin

Before you can run a geocoder in batch mode, your user ID must hold one of the following authorities or privileges:
  • DATAACCESS authority on the database that contains the table whose data is to be geocoded
  • CONTROL privilege on this table
  • UPDATE privilege on this table

You also need the SELECT privilege on this table, so that you can specify the number of records to be processed before each commit. If you specify WHERE clauses to limit the rows on which the geocoder is to operate, you might also require the SELECT privilege on any tables and views that you reference in these clauses. Ask your database administrator.

About this task

At any time before you run a geocoder to populate a particular spatial column, you can set up geocoding operations for that column. Setting up the operations involves specifying how certain requirements are to be met when the geocoder is run. For example, suppose that you require Db2 Spatial Extender to issue a commit after every 100 input records are processed by the geocoder. When you set up the operations, you would specify 100 as the required number.

When you are ready to run the geocoder, you can override any of the values that you specified when you set up operations. Your overrides will remain in effect only for the length of the run.

If you do not set up operations, you must, each time you are ready to run the geocoder, specify how the requirements are to be met during the run.

Procedure

To run a geocoder in batch mode:

Choose how to invoke a geocoder to run in batch mode:
  • Issue the db2se run_gc command.
  • Run an application that calls the DB2GSE.ST_RUN_GEOCODING procedure.