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 |
Prinergy crashes with errors in the debug logs showing database errors. This message appears in the D:\Orant\Rdbms80\Trace\creoALRT.log file: kccrsz: requested to expand controlfile section 11 by 51318 record(s) limited expansion to 14217 records since maximum numrecs is 65535 kccexpd: controlfile not expanded: would require 23934 block(s), max is 20000 krcpwnc: following controlfile record written over: RECID #4239 Recno 4239 Record timestamp |
|
|
|
||
Cause |
Whenever a new archived log file is created, Oracle logs the archived log file name in the control file. In Prinergy 1.1, the default setting for how long these log file entries are saved in the control file is set to 365 days. The control file automatically expands to allow more entries to be logged but the control file has reached its maximum size. The size of the control file is limited to 20,000 * db block size. In the Prinergy database, the db block size is 4096 bytes. Thus, the control file has a maximum size of 81920000 bytes (81MB). | |
|
|
||
Solution |
Change the entry "Control_File_Record_Keep_Time" in the D:\Orant\Database\Initcreo.ora file from 365 to 90 (90 days). The file can be opened in Notepad and hand-edited. The database must then be stopped and restarted for the change to take effect. (Stop Prinergy, then stop/restart the Oracle services. Restart Prinergy.) Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
daemon, oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
||
Date submitted |
||