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 |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
Print Engine Error message: 'Error detected by database DLL' Oracle Alert log file (Ora816\Rdbms\Trace\creoALRT.log) error message: 'ORA-1652: unable to extend temp segment by <NNNN> in tablespace SYSTMP1' - where NNNN is the number of blocks that Oracle is attempting to increase the segment by. |
|
|
|
||
Symptoms |
The database reports fail with a Print Engine Error message indicating that an error was detected by the database DLL. The Oracle Alert log file Ora816\Rdbms\Trace\creoALRT.log displays an error indicating that the temp segment size could not be increased. |
|
|
|
||
Cause |
More space is needed in the SYSTMP1 tablespace to generate the report. The SYSTMP1 tablespace is limited to 50 MB on a standard Prinergy 2.0 system. The amount of temp space needed by the database reports is dependent upon the size of the reporting tables in the database. | |
|
|
||
Solution |
NOTE: Increasing the size limit for the temp tablespace SYSTMP1 may result in an increase in the size of the database backup files. Make sure there is enough free disk space in the drive holding the database backup files for the larger backup files. That is, if you increase the tablespace by 500 MB, you may require an extra 600 MB of disk space for the backup. (You will require room for the .BCK backup file as well as the .ZIP file during backup.) **WARNING: Do not set the size limit to 16 GB (16384MB) or unlimited. If the datafile extends to 16 GB, the database will become corrupted by Oracle bug # 1668488. 1) Open a Command Prompt window. 2) Start SVRMGRL. 3) Enter: - SVRMGR> connect internal/creo - SVRMGR> select maxbytes, file_name from dba_data_files; 4) Search for the <drive>:\ORANT\ORACLE\SORTSPACE\TMP1CREO.ORA datafile. Copy the entire file name including the drive letter into the "alter database" statement below: NOTE: The entire filename must be entered in UPPERCASE. - SVRMGR> alter database datafile '<datafile name>' autoextend on maxsize 500M; Example: - SVRMGR> alter database datafile 'G:\ORANT\ORACLE\SORTSPACE\TMP1CREO.ORA' autoextend on maxsize 500M; 5) The datafile is now allowed to grow to a maximum of 500 MB. This should be sufficient for most database reports. If the report still fails due to insufficient space in the temp tablespace, increase the limit. 6) Exit SVRMGRL by typing SVRMGR> exit. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
Database Reports, oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
12 Apr 2002 |
|