9.2 SP3 Upgrade Scripts - Oracle

The following implementation scripts must be run on your Responder Oracle database to add the correct tables, views, and indices to upgrade Responder to version 9.2 SP3. When upgrading Responder execute ONLY the Upgrade script(s) that fall between your previous release and the new release to which you are upgrading. Do NOT execute any Implementation Scripts.

Responder requires two schemas: Responder and Archive. Some scripts are run on the Responder schema and some on the Archive schema. In the list below, the schema on which the script should be executed is in parentheses.

  • 920sp3_01_RxTables_oracle.sql (Responder)

  • 920sp3_02_ArchiveTables_oracle.sql (Archive)

  • 920sp3_03_ArcJoinViews_oracle.sql (Responder)

    TIP: The instructions below do not execute the scripts in the order listed above. Note that the first and third scripts are executed on the Responder database first. The second script is executed on the Archive database last. The instructions execute them in this order simply for the implementer's convenience.
  1. Log in to the Responder schema as RESPONDER (i.e., schema owner). Use an application such as SQL Plus.
  2. Execute the 920sp3_01_RxTables_oracle.sql script by entering "@" followed by a path to the script (an example follows) and pressing Enter. This script creates the database tables required by Responder.
    @ D:\Program Files\Miner and Miner\Responder\Developer Resources\
    9.2.0 SP2 - 9.2.0 SP3 Upgrade Scripts\Oracle\920sp3_01_RxTables_oracle.sql
  3. The 920sp3_03_ArcJoinViews_oracle.sql script creates the views that are used to display Responder data in ArcMap. Execute 920sp3_03_ArcJoinViews_oracle.sql using a similar statement as in step 2. Even if you executed this script as part of the initial implementation, execute it again.
    NOTE: Before executing this script, you will need to modify the feature class names within it to match those in your geodatabase. Open the script and ensure that the feature class names in the script match the corresponding feature class names in your geodatabase. If you have done this for a previous release, you may use the prior script and copy/paste the new views into it. This would prevent the need to re-update feature class names for all views.
  4. Log in to the Archive schema as ARCHIVE (i.e., schema owner).
  5. Execute the 920sp3_02_ArchiveTables_oracle.sql script in the same manner as the first script. Enter "@" followed by a path to the script and press Enter. This script creates the database tables required by Responder Archive Explorer.
QR code for this page

Was this helpful?