11.0

- Make sure that the World Wide Web Publishing service is running in 32-bit mode:

3. In Oracle DBMS, create a user, e.g. FCUSER, and assign the CONNECT and DBA roles to this user. One

FlexiCapture database corresponds to one user. If several FlexiCapture databases running under Oracle

DBMS are required, create a user for each database.

Note: If, for security reasons, you do not want to have a user with the DBA role, then after creating the data-

base you can revoke the DBA role from the user. The CONNECT role and the privileges for all objects of the

user scheme must be preserved (they must be granted by default), and the privilege for TABLESPACE

where the FlexiCapture database is located should be granted explicitly (ALTER USER user QUOTA unlim-

ited ON tablespace;). It should be noted that with these settings, you will not be able to apply patches to your

database via the Administration and Monitoring Console, but this is seldom required (patches are provided

by ABBYY technical support in case of problems with the database). For the time the patch is applied, the

user should be reassigned the DBA role.

The user must also have privileges for the standard dbms_lock batch. To grant these privileges to the user,

run the following command as the database server administrator:

Grant Execute On dbms_lock To FCUSER;

where FCUSER is the name of the user you created for ABBYY FlexiCapture. It is assumed that when you

run this command, no database has yet been created under this user’s account in the Administration and

Monitoring Console.

Note: If you have already created a database in the Administration and Monitoring Console using this user’s

account, you need to run the following additional commands:

Alter Procedure FCUSER.CleanUp_ELDayCleanUp Compile;

Wait for the command to complete and then run

Alter Procedure FCUSER.CleanUp_StartCleanUpJob Compile;

where FCUSER is the name of the user you created for ABBYY FlexiCapture.

4. Establish the connection between the client and the Oracle server using the Net Manager utility, which is in-

stalled together with the Oracle client (in the Administration configuration) and the database server. In the

client utility, create a new Service Naming element (a local naming method), which must be connected with

the Oracle database server by its SID. Test the connection with the database server on behalf of the user

account created in step 2. Go to the next stop only if the connection test succeeds. If you cannot set up the

connection, consult the Oracle documentation.