I have an LEI activity that is replicating data from an Oracle table to a Notes database. Every time the replication occurs, the database size is expanding dramatically. It went from 13 MB to 239 MB in the last five replications! I've already had to blow the DB twice as last time it went to 15 GB and became corrupt.
There are maybe 40 new docs being added to the Oracle table daily so this doesn't justify the size increase.
Obviously, this is strange behavior for LEI. Does the Oracle table include any BLOB columns? I'm guessing that it does not, but if it does you need to check the size of the data stored in that/those column(s) within the Oracle table. Before you try running the LEI activity again, open the Oracle connection document and enable the Logging option -- "Output SQL Statements to Log." Then open your Activity and select the Logging options -- "Log Key Values On Error" and under Conflict Handling "Log Conflict." Run the activity and inspect the log for anything that might indicate a problem.
Here are some things to try on the Notes side: In your Notes database, create a view that lists these same documents and that includes a "Size (bytes)" column. If the documents look OK, run a Database Design Synopsis of views and see what the LEI view looks like.
You can specify a view name in the Notes connection document for LEI, and it will create one for you each time the job runs. If you are not specifying a view in your Notes connection, look in the activity log to see the name of the view.
This was first published in October 2003