![]()
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.1 ; Prinergy Direct 2.1 ; Prinergy Access 2.1 ; Prinergy Powerpack 2.1 | |
Platform |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
Oracle backup processing ended for unexpected reasons. Contact the Response Center. There may be insufficient disk space for the backup files. If so, please free up some space, otherwise next backup will fail again. Executing C:\Ora816\Creo\Util\UnSuccessfulBackup.cmd Error: exceptions.SystemExit, 1, <traceback object at e133b8> traceback: Exception in process 2196, thread 2076 Traceback (innermost last): File "C:\Prinergy2.0.4\lib\Python\com\creo\araxi\database\BackupDatabase.py", line 652, in backupOracle sys.exit(1) exceptions.SystemExit: 1 |
|
|
|
||
Symptoms |
The system was rehosted onto new hardware. The Oracle software installation folder on the new server is different than the old server. (Normally Oracle is installed in the ORA816 folder.) The database backups fail with a generic error message as shown. |
|
|
|
||
Cause |
RMAN saves a copy of the control file which is called a snapshot control file. The location defaults to the %ORACLEHOME%\Database folder, but once an initial snapshot controlfile is created, RMAN will always write the snapshot controlfile to the same location. (RMAN does not update it if the Oracle installation folder changes). | |
|
|
||
Solution |
You must manually change the location of the snapshot controlfile. 1) Start RMAN. - D:\> RMAN TARGET INTERNAL/CREO@ARAXIDBSERVER NOCATALOG 2) Change the location of the snapshot controlfile. - RMAN> SET SNAPSHOT CONTROLFILE NAME TO 'D:\ORA816\DATABASE\SNCFCREO.ORA'; - RMAN> EXIT 3) Run a test backup using OracleBackupManager. - D:\> ORACLEBACKUPMANAGER - Araxi_OracleMgr> BACKUP DATABASE Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup, oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
03 Feb 2005 |
|