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.1 ; Prinergy Direct 2.1 ; Prinergy Access 2.1 ; Prinergy Powerpack 2.1 | |
Platform |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
Tablespace filename will be J:\DATA\ORACLE\DATA\RBSTMP.ORA ERROR: exception occurred; SQLCODE = -1543 SQLERRM = ORA-01543: tablespace 'RBSTMP' already exists PL/SQL procedure successfully completed. SQL> Disconnected from Oracle8i Release 8.1.6.1.0 - Production JServer Release 8.1.6.0.0 - Production 21-Jan-2003 16:12:36 TRACEBACK: Exception in process 332, thread 1788 Traceback (innermost last): File "E:\Temp\~ppu.0\ppuinstall.py", line 499, in InstallPatch PPUScript.install( self ) File "E:\Temp\~ppu.0\PPUScript.py", line 432, in install None File "E:\Temp\~ppu.0\PPUScript.py", line 1304, in UpgradeDatabase None File "E:\Temp\~ppu.0\PPUScript.py", line 9417, in UpgradeSchema None Exception: Error: Failed to upgrade database schema. Details: exceptions.Exception Error: Failed to create Oracle rollback segment. Details: exceptions.Exception Error: Failed to execute command. |
|
|
|
||
Symptoms |
When installing minor update 2.1.0.10 the installation fails and rolls back. The ppu.log files contains the error message below. |
|
|
|
||
Cause |
The Oracle database is installed in a non-standard location. The upgrade script assumes the database is installed in the Orant folder. The upgrade script is finding the drive where the Oracle database is installed and appending the path Orant\Oracle\Data for the location of the rollback segment instead of taking the root folder and appending just the path Oracle\Data. |
|
|
|
||
Solution |
To be able to install 2.1.0.10, we must move the control file, redo log files, and datafiles to the Orant folder. This procedure should only be done by someone familiar with Oracle and the Oracle utilities. 1) Shutdown the database and rename the root folder to Orant. (Example: J:\Orant) 2) Edit the D:\Ora816\Database\initCreo.ora, change the control_files entry with the new location for the control file. (Example: J:\Orant\ControlFile\CTL2CREO.ORA) 3) In SVRMGRL, mount the database. 4) To get a list of the datafile names, run the query: SELECT name FROM v$datafile; 5) Update the locations of the datafiles. For each datafile that was moved, run the command: ALTER DATABASE RENAME FILE '<old_datafile_name>' TO '<new_datafile_name>'; (Example: alter database rename file 'J:\BLAH\ORACLE\DATA\SYSCREO.ORA' to 'J:\ORANT\ORACLE\DATA\SYSCREO.ORA'; 6) To get a list of all redo log files, run the command: SELECT member FROM v$logfile; 7) Update the locations of the redo log files. For each redo log file that was moved, run the command: ALTER DATABASE RENAME FILE '<old_log_file_name>' TO '<new_log_file_name>'; (Example: alter database rename file 'J:\BLAH\ORACLE\ONLINELOGFILES\LOG1CREO.ORA' to 'J:\ORANT\ORACLE\ONLINELOGFILES\LOG1CREO.ORA'; 8) Open the database, enter: ALTER DATABASE OPEN; Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
oracle, patches |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
22 Jan 2003 |
|