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 1.1 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
OracleBackupManager shows the error: Traceback (innermost last): File "E:\Prinergy\CreoAraxi\bin\OracleBackupManager.cmd", line 37, in ? File "E:\Prinergy\lib\python\com\creo\araxi\database\BackupDatabase.py", line 26, in ? from com.creo.araxi.database.BackupLog import Log File "E:\Prinergy\lib\python\com\creo\araxi\database\BackupLog.py", line 35, in ? Log = OracleLogWriter() File "E:\Prinergy\lib\python\com\creo\araxi\database\BackupLog.py", line 30, in OracleLogWriter FileFunctions.CreateNewFileVersion(logFileName, 60) File "E:\Prinergy\lib\python\com\creo\utilities\FileFunctions.py", line 95, in CreateNewFileVersion os.rename(sourceFileName,newFileName) os.error: (13, 'Permission denied') |
|
|
|
||
Cause |
OracleBackupManager is trying to access the log file \Orant\Creo\Logs\OracleBackupLogFile.log, which is held open by another instance of OracleBackupManager or the database backup python scripts, which may be running in the background. | |
|
|
||
Solution |
Close any other instance of OracleBackupManager and terminate the python script that is running the backup script. To terminate the python script do one of the following: Procedure 1: 1) Stop Prinergy. 2) Kill the backup software used for the system backup - NTBACKUP.EXE or SAVEGRP.EXE if it is still running. 3) Kill the python scripts using the command 'Kill python' in a command prompt window. 4) Restart Prinergy. Procedure 2: 1) Kill the backup software used for the system backup - NTBACKUP.EXE or SAVEGRP.EXE if it is still running. 2) In a command prompt window, run the command 'Kill python'. Prinergy's UADM will display an warning that the Diagnostic View Daemon has crashed. 3) In the command prompt window, run the command 'Kill PDiagnosticD', this kills the Diagnostic Log Daemon. It will restart automatically along with the Diagnostic View Daemon. Note: Some debugging information may be lost during the time that the Diagnostic Log Daemon is terminated. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup, oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
||
Date submitted |
||