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 Connect 2.0 ; Prinergy Direct 2.0 ; Prinergy Connect 2.1 ; Prinergy Direct 2.1 ; Prinergy 2.x, 3.x, EPM+, | |
Platform |
Intel |
|
Operating system |
Windows |
|
|
|
||
Error |
Oracle failed to start |
|
|
|
||
Symptoms |
After EPM+ failover, Prinergy reports that Oracle has failed to start, but Oracle has actually started and is running OK. "Oracle failed to start" dialog box appears in Prinergy Administrator |
|
|
|
||
Cause |
This is caused by an Oracle error in a trace file in d:\ora816\rdbms\trace on the failover server that dates before EPM+ was configured. This may not have anything to do with Oracle's current state, but the Prinergy error parser doesn't always detect errors. If it finds an old error it will report that Oracle has failed to start, even though it actually has. | |
|
|
||
Solution |
With the system running in normal mode (not failed over), shut off VSR replication, delete all files in the d:\ora816\rdbms\trace folder on the failover server only, and restart replication. This will replace the trace files with those on the Primary. Reboot the Failover server. Prinergy should start fine with the next failover. Note: This can happen with VSR and DoubleTake (newer installs). The fix remains the same for both. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
EPM, Emergency Platemaking (EPM), Hot Standby, administrator, oracle |
|
|
|
||
Technical contact(s) |
Robyn Lundstrom |
|
Submitted by |
Robyn Lundstrom |
|
Date submitted |
07 Jun 2005 |
|