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 |
3.0.2.0 | |
Platform |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
||
|
|
||
Symptoms |
After upgrading to Prinergy 3.0.2, diagview logs indicates that path migration cannot run due to low disk space on the E: drive. |
|
|
|
||
Cause |
Path migration calculates how much space is required to run. The calculation is as follows: 1) Leave 4 GB free for JTP temp files. 2) Leave 0.7 * database size (or 1.0 * database size for 3.0.2.0 -3.0.2.1). 3) The rest of the free disk space is available for path migration. In 3.0.2.2 and up, at least 200MB of archived log files will be allocated for path migration, regardless of how much free space is available. This ensures that path migration will always proceed, albiet at a slow rate. |
|
|
|
||
Solution |
To free up disk space for path migration do one or some of the following: 1) Temporarily move the database backups (backup_destination parameter in OracleBackupManager) to another drive. 2) Temporarily move the database backup zip files (zip_files_destination parameter in OracleBackupManager) to another drive. 3) Move the Prinergy snapshot to another drive. 4) Temporarily move the pagefile to another drive. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
patches |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
31 Oct 2005 |
|