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.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
After a Prinergy 1.1 to 2.0 upgrade, a major update install fails or hangs while it performs database changes. |
|
|
|
||
Cause |
The database is in Archivelog mode, but the Oracle archiving process, which automatically archives the redo log files, has not been started. Background: When Prinergy is installed, the database is in NOARCHIVELOG mode. The utility InitializeOracleBackupManager will change it to ARCHIVELOG mode and modify the initCreo.ora file to start the archiving process when Prinergy is started for the first time. The 1.1 to 2.0 migration script changes the database to ARCHIVELOG mode but does not change the initCreo.ora file to automatically start up the archiving process. When InitializeOracleBackupManager.cmd is run during the Prinergy startup, it detects that the database is already in ARCHIVELOG mode and does not uncomment the log_archive_start parameter in the initCreo.ora file. Thus, the archiving process never starts and Oracle hangs waiting for the online log files to be archived. |
|
|
|
||
Solution |
The solution involves two steps. The first step is to archive the existing redo log files to get the major update to complete. The second step is to modify the initCreo.ora file and restart Oracle to start the archiving process whenever Oracle is started. To archive the existing redo log files: 1) Start SQLPLUS and log in as internal - D:\> sqlplus internal/creo 2) In SQLPLUS, enter: - SQL> alter system archive log start; This starts the archiving process temporarily for the instance. If the instance is shut down and restarted, the archiving process will not be restarted. After the major update is completed, you MUST modify the initCreo.ora file to enable archiving. 3) Open the D:\Ora816\Database\initCreo.ora file in Notepad. 4) Remove the '#' from the following lines (if they are commented): . #LOG_ARCHIVE_START = True . #LOG_ARCHIVE_DEST = E:\Orant\..... . #LOG_ARCHIVE_FORMAT="%%ORACLE_SID%%T%TS%S.ARC" 5) Save the file. 6) Stop and restart Oracle. In SQLPLUS, enter: - SQL> connect internal/creo - SQL> shutdown immediate - SQL> startup Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
1.1 to 2.0 Upgrades, oracle, patches |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
09 Oct 2001 |
|