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 |
W2K/W2K3 |
|
|
|
||
Error |
During Prinergy 4.0 upgrade, Oracle 10g install fails because the Oracle install logfile failed to grow within the timeout period. |
|
|
|
||
Symptoms |
1. Diagnostic Log does not display messages in real time. The current AraxiLog filesize does not grow, even if the explorer view is refreshed. When the log file is highlighted, the messages suddenly get displayed in DiagView. The size of the logfile suddenly grows. 2. Prinergy 4.0 install fails on Oracle 10g install. The failure is due to a timeout because the Oracle install logfile stopped growing. |
|
|
|
||
Cause |
A registry setting in DoubleTake causes this behavior. DoubleTake recommends removing the registry value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dblhook\Parameters\EnableCacheModeConversion |
|
|
|
||
Solution |
Remove the registry value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dblhook\Parameters\EnableCacheModeConversion A server reboot is required. This can also be accomplished by running dblhook.reg from "\\ccafs6\araxidata\PR Data\PSamaniego\PSAO-158" and rebooting the server. The HotStandby installer CD is being updated to reflect this change. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
EPM, administrator, diagview, oracle |
|
|
|
||
Technical contact(s) |
Philip Samaniego |
|
Submitted by |
Philip Samaniego |
|
Date submitted |
10 Apr 2007 |
|