Quantcast
Channel: Primavera Online Interaction » PMDB
Viewing all articles
Browse latest Browse all 92

prim21628:ORA-01631 Max # Extents(nnn) reached in table (xxx)

$
0
0
Solution ID: prim21628
ORA-01631 Max # Extents(nnn) reached in table (xxx)
Status: Reviewed
Version(s): 3.5, 3.5.1, 3.5.1, 4.0, 4.1



Problem: During normal user functions of Project Manager / Management such as creating projects, adding activities, resources, codes or updating projects, the following error may occur:

ORA-01631 Max # Extents(nnn) reached in table (xxx)


Where nnn = # of Extents and xxx = PMDB table name

Cause:

For each table a maximum number of extents can be specified.  This error means that in order to accommodate some new data, Oracle needed to extend a table but could not because the maximum number of extents have been reached.  The error reports back both the current (maximum) number of extents and the table name.


This error is often also symptomatic of the next extent size being too small.

Fix:

NOTE: The following steps should be performed by the Oracle DBA:


Increase the maximum number of extents allowed for the table, i.e:



alter table <table-name> storage (maxextents 500);


or alternately remove the limit on the number of extents, i.e.:



alter table <table-name> storage (maxextents unlimited);


Viewing all articles
Browse latest Browse all 92

Trending Articles