![]()
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy 1.1; Prinergy Connect 2.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
||
|
|
||
Cause |
||
|
|
||
Solution |
This workaround briefly describes the steps necessary to preserve the integrity of the Oracle database if the RAID is to be backed up and restored. Examples of when this would be done is if the RAID is to be replaced or if the drives in the RAID are replaced with larger capacity drives. To properly back up the RAID or copy the contents of the RAID to some other storage location, the Oracle database must be stopped. If the Oracle database is left running, the database files that are backed up will be useless. If the Oracle database should start up before the files are restored, the database will have to be repaired before it is usable. To prevent these problems, follow this procedure to back up the RAID: 1) Stop the Oracle services. In Control Panel | Services, stop the two services: - OracleStartCreo (Prinergy 1.1) or OracleStarter (Prinergy2.0) - OracleServiceCreo 2) Change the startup for the two Oracle services to Disabled. This will ensure that the services will not be inadvertently started if the system is rebooted before the database files are restored. 3) Perform the RAID backup using the backup method of choice. 4) Perform whatever hardware servicing is required on the RAID. 5) Restore the files back onto the RAID. 6) Set the OracleServiceCreo, OracleStartCreo (or OracleStarter) services to Automatic. 7) Restart the two Oracle services. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup, oracle, RAID |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
||
Date submitted |
||