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; Prinergy Connect 2.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
ORA-03206: maximum file size of (4352000) blocks in AUTOEXTEND clause is out of range |
|
|
|
||
Symptoms |
The USRDAT1 datafile has reached it's maximum size but attempts to change the MAXSIZE of the datafile in SVRMGRL fails. |
|
|
|
||
Cause |
The Oracle database has a physical limit on the size of the datafile. This limit is 4 Million blocks times the blocksize. In the Prinergy database, the maximum size is 4 M blocks X 4096 bytes/block = 16 GB or 17,179,869,184 bytes. | |
|
|
||
Solution |
Another datafile must be added to the tablespace. 1) Start SVRMGR30 (Prinergy 1.1) or SVRMGRL (Prinergy 2.0) * D:\> SVRMGRL 2) Connect to the database as INTERNAL * SVRMGR> connect internal/creo@araxidbserver 3) Check the location of the existing datafiles * SRVMGR> select file_name from dba_data_files; FILE_NAME ------------------------------------------------------------ G:\ORANT\ORACLE\DATA\SYSCREO.ORA G:\ORANT\ORACLE\SORTSPACE\TMP1CREO.ORA G:\ORANT\ORACLE\DATA\USR1CREO.ORA G:\ORANT\ORACLE\DATA\RBS1CREO.ORA G:\ORANT\ORACLE\DATA\USR2CREO.ORA 4) Add the datafile: * SVRMGR> alter tablespace USRDAT1 add datafile '<drive>:\ORANT\ORACLE\DATA\USR2CREO.ORA' size 200M autoextend on next 50M maxsize 16379M; **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. **NOTE: Put the new datafile in the same drive/folder as the original datafile (in this example USR2CREO.ORA is added to the folder holding the USR1CREO.ORA datafile). 5) Ensure that the drive used to hold the database backups is large enough for the new file when it reaches it's maximum size. A larger disk drive may be necessary to accomodate the database backups. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
||