Product

Platform

Operating system

Error

Example:

E 14Aug00 11:40:32.562-PDT [308.620] YCS172-82 ARAXI PJobD.RegisterSubPageElements620 CORB_ThreadFilter.cpp(212): caught exception, class DBIF_UnRecoverableDBException ex: [SERVERERROR] Error from Server: ORA-01653: unable to extend table ARAXI_1_0_12.DBCS_REGISTEREDFILE by 357 in tablespace USRDAT1

ORA-06512: at "ARAXI_1_0_12.DBCS_REGFILE_I", line 99

ORA-06512: at line 2

Database:AraxiDBServer- OS Error No.

The Oracle Alert log D:\Orant\Rdbms80\Trace\creoALRT.LOG may show these errors:

ORA-1654: unable to extend index ARAXI_1_0_12.DBCS_PAGEELMNT_PK by 277 in tablespace USRDAT1

ORA-1653: unable to extend table ARAXI_1_0_12.DBCS_IMPOSITIONPAGE by 317 in tablespace

ORA-1654: unable to extend index ARAXI_1_0_12.DBCS_ITEMINTASKTEMPGROUP_PK by 313 in tablespace USRDAT1

ORA-1653: unable to extend table ARAXI_1_0_12.DBCS_REGISTEREDFILE by 357 in tablespace USRDAT1

ORA-1654: unable to extend index ARAXI_1_0_12.DBCS_HISTLOGDETAIL_IDX1 by 814 in tablespace USRDAT1

Symptoms

DiagView shows database errors from various processes whenever the process tries to write to the database.

Cause

To check the maximum size of the database files (in bytes):

For Prinergy 1.1, run

D:\> SVRMGR30

For Prinergy 2.0, run

D:\>SVRMGRL

SVRMGR> connect internal/creo

SVRMGR> select maxbytes, tablespace_name, file_name from dba_data_files;

The maxbytes column will display the maximum size of each datafile.

Solution

NOTE: If the database is being backed up on the E: drive, the drive must be replaced with a larger capacity drive such as an 18 or 36 GB disk. The customer must purchase this disk drive upgrade. If the E: drive capacity is not increased, the database backups will eventually fail due to insufficient disk space.

For DELL servers the D: and E: drives are on the same physical disk and the disk is mirrored. If there is a free slot in the internal RAID chassis of the DELL, a single drive is sufficient. However, if the internal RAID chassis is full, the mirrored system drives must be replaced. This requires two disk drivess and the replacement procedure is more involved than adding a single drive.

To calculate how large a disk drive is needed for the maximum size of the database, use the following formula:

Disk space for Prinergy Temp (4 GB) + 1.2 * DB Max size + 400 MB for archived log files

For example, the database maximum size has been increased to 5 GB:

4 GB + 1.2 * 5 GB + 0.4 GB = 10.4 GB --> use an 18 GB drive for this configuration.

The database file size limit can be increased by running these commands in SVRMGR.

**WARNING: Do not increase 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: You do NOT need to shut down Prinergy or the database to perform this task.

For Prinergy 1.1, run

D:\> SVRMGR30

For Prinergy 2.0, run

D:\>SVRMGRL

Oracle Server Manager Release 3.0.5.0.0 - Productionn

(c) Copyright 1997, Oracle Corporation. All Rights Reserved.

Oracle8 Release 8.0.5.1.1 - Production

PL/SQL Release 8.0.5.1.0 - Production

SVRMGR> connect internal/creo

Connected.

SVRMGR> select name, bytes from V$Datafile;

NAME

-----------------------------------------

G:\ORANT\ORACLE\DATA\SYSCREO.ORA

G:\ORANT\ORACLE\SORTSPACE\TMP1CREO.ORA

G:\ORANT\ORACLE\DATA\USR1CREO.ORA <---- This is the datafile where the Prinergy tables are kept.

G:\ORANT\ORACLE\DATA\RBS1CREO.ORA

4 rows selected.

- This lists the name and size of the tables. By default, the user1creo.ora is 3120000K, (3 GB)

SVRMGR> alter database datafile 'G:\Orant\Oracle\Data\Usr1creo.ora' autoextend on maxsize 5120000K;

Statement processed.

- This statement changes the maxsize of the Usr1Creo to 5Gb. If the existing size of the file is already 5 GB, you may want to change the maxsize to 7680000K (7 GB) instead.

SVRMGR> exit

If the database is saved on E: drive, advise the customer to upgrade their existing E: drive to 18 GB, as their database size is growing and backup will fail if it is running out of space on the E: drive.

Permanent fix:

See also

Keywords

oracle

Technical contact(s)

Stan Yoshida

Submitted by

Stan Yoshida

Date submitted

unknown