Creating a single Oracle database for a Datacap application

You can create a single Oracle database for the Administration, Engine, and Fingerprint databases in a Datacap application.

About this task

You define the structure of the Datacap application databases by running SQL scripts for the Administration, Engine, and Fingerprint database schema. You can run SQL scripts for these Datacap application databases separately to create a SQL Server or Oracle database for each of the application databases.

For Oracle databases, you can run the SQL scripts together to create 1 Oracle database that contains the Administration, Engine, and Fingerprint database schema. This procedure creates a single Oracle database user for all the Datacap application databases.

Procedure

To create a single Oracle user for Datacap databases:

Start the SQLPlus tool and log on to the SYS@net service name as SYSDBA. The net service name is specific to each computer.
Run the following script to create the user:
```
CREATE USER APTOra3X
	     IDENTIFIED BY APTOra3X;

Grant resource to APTOra3X;
Grant DBA to APTOra3X;
Grant EXP_FULL_DATABASE to APTOra3X;
```
Attention: The user name APTOra3x is used as an example. You can choose a more descriptive name such as CaptureInvoiceTM or AcmeCapture to identify the function of this particular Oracle database.
Disconnect from the SYS account and log on to the user account that you created with SQLPlus.
Go to C:\Datacap\support\DBScript and find the following Oracle scripts:
- Oracle_Adm_Base.sql
- Oracle_Eng_Base.sql
- Oracle_FP_Base.sql
1. If this is not the first database that you are creating in this Datacap environment, you must modify the scripts to have unique db_index values to uniquely associate with the application:
  IDs for the db_index fields are hard-coded in the database creation scripts. If this is not the first database that you are creating in this Datacap environment, you must set a new numeric value in the db_index column in the scripts (the adminfo table in the Admin schema and the enginfo table in the Engine schema) to uniquely identify the database with this Datacap application.
  
  If you have one admin database per engine database for an application, you can use the same unique numeric ID in both databases. If you have multiple admin databases per engine database, specify different unique numeric IDs for each database, but use a numbering convention that simplifies the identification of those databases for an application.
  
  Tip: When batches are created in the Engine schema, each queue table row contains column qu_admDB. This value displays which admin database is associated with the batch.
2. Run the scripts.
Disconnect from the user account.
Copy the data from the source database by using the Application Copy Tool.
Point the Administration, Engine, and Fingerprint database schemas to the same location.
Configure the application to use the database by using the database user name that you created here.