Database Largefile support has to be enabled for BOTH the source and the target database.
When setting up the replication baseline for the first time:A PROREST where NO pre-existing target structure exists, will result in a large-file enabled database.
A PROREST where a pre-existing target structure exists, will result in whatever the setting is on the target structure, so it is important to run the 'proutil target -C enablelargefiles' prior to the prorest of the source baseline for target creation.
When enabling largefile support after the replication baseline has been established:In both the source and target database perspective, replication will break until the largefile support is enabled on both databases.
For example: When enablelargefiles is run against the source database:
The Replication agent (RPLA) and Replication Server stop, with the following in the Replication enabled target database lg file:
The source and target databases must both have large files enabled. (10386)
An error occurred during connection. Fathom Replication cannot continue (10534)
The Replication Server has been terminated or the Source database has been shutdown. The Agents will enter PRE-TRANSITION, waiting for re-connection from the Replication Server. (12688) Replication will will remain in pre-transistion status until largefile support is enabled.
STEPS: Enable largefiles on the target1. If the target database is still running, shut it down:
$ proshut target -by
2. Ensure an Enterprise Database license is in place and enable largefiles on the target:
$ proutil target -C enablelargefiles
3. Start target database.
The reverse applies were largefilesupport enabled on the target first.
