Kbase P147284: When large files were enabled on source database, but not target, error (1178) occurs.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/30/2009 |
|
Status: Verified
SYMPTOM(s):
When large files were enabled on source database, but not target, error (1178) occurs.
(10601) SYSTEM ERROR: Attempted to exceed maximum size on file /cli/db.b6.
Large files were enable on Source database to resolve the problem of the bi extent hitting the 2 GB limit.
After large files were enabled error (1178) was received.
The shared memory is version <num>; expected <num> (1178)
(13198) The after-image management daemon cannot find a destination in its current list with enough space to continue archiving extents.
(1178) The shared memory is version 10213; expected 10174
(10429) The user failed to connect to database /cli/db with error -1 in rpDB_OpenDatabase.
(10717) The Fathom Replication Utility cannot connect to database /cli/db.
(9407) Connection failure for host cli-test port 4387 transport TCP.
(11713) A communications error -4008 in rpCOM_RecvMsg
(10661) The Fathom Replication Server is beginning recovery for agent agent1.
(10842) Connecting to Fathom Replication Agent agent1.
(10396) The Fathom Replication Server cannot connect to the database broker on cli-test at the port -1.
(10397) The connection attempt to the Fathom Replication Agent agent1 failed
(10697) The Fathom Replication Server was unable to reconnect to agent agent1. Recovery for this agent will not be performed.
(10698) The Fathom Replication Server will shutdown but the source database will remain active.
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge Replication
CHANGE:
Large files had been enabled on the source database, but not the target database, when a bi file on the source hit the 2 GB limit.
CAUSE:
Replication Source and Target database must have the same settings, therefore, Enabling large files on the source database resulted in the 1178 errors.
FIX:
Enable Large Files on the target database using the following:
1. Stop Target database if it is still running.
2. Enable large files on the target database using:
proutil <db-name> -C EnableLargeFiles
3. Restart the Target database.
4. Restart the replication server on the source database using:
dsrutil <dbname> -C restart server