The archive job fails due to known limitations of the Oracle JDBC drivers. Or, the archive job succeeds, but produces unexpected results. The following scenarios are example scenarios that occur due to Oracle JDBC driver limitations:

You receive a
java.sql.SQLException
protocol violation exception.
You receive an exception that OALL8 is in an inconsistent state.
When you run an archive cycle for an entity with a Run Procedure step, an exception occurs due to an incomplete import. The job did not import the CLOB column, even though the job log shows that the column was imported successfully. The
applimation.log
includes an exception that an SQL statement is empty or null.
The connection to an Oracle database fails.
The Copy to Destination step shows an exception that the year is out of range.
The select and insert job fails with an ORA-600 exception.
The residual tables job fails with an ORA-00942 exception that a table or view does not exist.

To resolve the errors, use a different Oracle JDBC driver version. You can find additional Oracle JDBC drivers in the following directory:

<Data Archive installation directory>/optional

For more information, see Knowledge Base article 109857.

You may receive an out of memory error if several tables include LOB datatypes.

To resolve the errors, perform the following tasks:

Lower the JDBC fetch size in the source connection properties. Use a range between 100-500.
Reduce the number of Java threads in the
conf.properties
file for the
informia.maxActiveAMThreads
property. A general guideline is to use 2-3 threads per core.

To improve the archive job performance, perform the following tasks:

Check for timestamp updates in the
host:port/jsp/tqm.jsp
or the BCP directory.
Check for updates in table AM_JOB_STEP_THREADS in the ILM repository (AMHOME).
For UNIX operating systems, run the following UNIX commands to see input, output, and CPU activity:
sar -u 1 100
iostat-m 1
top
ps -fu 'whoami' -H
Use multiple web tiers to distribute the extraction.
To use multiple web tiers, perform the following steps:
Create a copy of the web tier.
Change the port in the
conf.properties
file.
Start the web tier.

Run the Data Vault Loader and Update Retention jobs on the same web tier where you ran the Create Archive Folder job.

You may receive an error that the process did not complete if the archive job uses IBM DB2 Connect utilities for data movement. When the archive job uses IBM DB2 Connect utilities to load data, the job waits for a response from the utility for each table that the utility processes. The archive job fails if the job does not receive a response within 3 hours.

Use the IBM DB2 trace files to locate the error.

The archive job fails if the source database is IBM DB2 and the data contains the Decfloat data type.

To resolve this issue, perform the following tasks:

Go to
Workbench
Manage Archive Projects
.
Click the edit icon for the archive project.
Set the
Insert Commit Interval
value to 1.
Complete the remaining steps in the archive project to archive the data.

If the source database is Oracle and a table contains more than 998 columns, the archive job fails.

This issue occurs because of an Oracle database limitation on column number. Oracle supports a maximum number of 1000 columns in a table. The archive job adds two extra columns during execution. If the table contains more than 998 columns on the source database, the archive job fails because it cannot add any more columns.