Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy 3.x, 4.x | |
Platform |
||
Operating system |
Windows 2000/2003 server |
|
|
|
||
Error |
System Event Log: Event Type: Warning Event Source: Dblhook Event Category: Resources Event ID: 8196 Date: 10/6/2006 Time: 6:44:49 AM User: N/A Computer: P3LAB2600 Description: The maximum amount of memory for replication queuing has been reached. Replication is stopped and memory is being freed. Data: 0000: 00 00 04 00 01 00 5c 00 ......\. 0008: 02 00 00 00 04 20 f1 8f ..... ñ� 0010: b3 14 34 93 00 00 00 00 ³.4?.... 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 90 ec 00 08 �ì.. |
|
|
|
||
Symptoms |
Dblhook logs an Event 8196 to the System Event Log. Replication is stopped and a remirror is triggered. If e-mail notification is enabled, an e-mail with the following message is sent: Description: The maximum amount of memory for replication queuing has been reached. Replication is stopped and memory is being freed. Server: P3LAB2600 Source: Dblhook Id: 8196 Severity: Warning Category: Resources Time: 10/06/2006 06:44:49 |
|
|
|
||
Cause |
Event 8196 occurs when the replication queue cannot be flushed fast enough. This may occur when the server is very busy, or the DoubleTake kernel driver being overwhelmed by the amount of data changes in the source folders. | |
|
|
||
Solution |
Do the following on the server where the problem is seen. 1. Change the DoubleTake disk queue from the Data drive (usually J:\) to a drive which is not very busy. 2. If using an anti-virus software, exclude DoubleTake.exe and the DoubleTake disk queue from real-time virus scan. 3. If there is available physical memory, increase the DoubleTake memory queue. 4. If error is on a Primary server, exclude *.bck files (in the OracleBackupFolder) in the PrinergyDB replication set. The repset needs to be disconnected and modified. This is done using the DT Management Console. Right-click on the repset and select properties. Use the Rules tab to modify the repset. Save the modified repset. 5. Run dblhook.reg in <\\ccafs6\araxidata\PR Data\PSamaniego\PSAO-158> to apply settings to the registry. 6. Reboot the server. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
EPM, administrator, backup |
|
|
|
||
Technical contact(s) |
Philip Samaniego |
|
Submitted by |
Philip Samaniego |
|
Date submitted |
30 Nov 2006 |
|