on 07-11-2013 4:33 PM
Turns out that this is a known issue in Oracle where eventhough the table and LOB are set to unlimited, it doesn't recognize that. It has something to do with having upgraded Oracle. There was (and forgive me as I don't know exactly what our DBA did here) a fix available from Oracle to resolve this. It was set in a previous version and couldn't be changed in the current version. Basically Oracle's resolution was to trick the system into thinking it was the older version to make the change. This is how it was explained to me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have set the table FPLAYOUTT to unlimited.
But the error occured on FPLAYOUTT~ which is the shadow table of the original object.
If you are unlucky, SUM will drop and recreate the table again with the wrong values. If that is the case you can try to catch the right moment, as soon as the object is created and the loading starts, try to either set max extents to unlimited, or increase the next extent.
Another solution could be to create a dedicated locally managed tablespace and move the table there and then retry.
A third possibility is to try to change the properties in SE11 -> storage parameters -> for new creation.
As Stefan said you should get rid of dictionary managed tablespaces as quick as possible.
Cheers Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kyle,
> We have set the table FPLAYOUTT to unlimited
Did you just set the table to max extent unlimited or the corresponding LOB segment as well? Your issue is caused by the LOB segment (SYS_LOB0000458190C00005$$) and not the "base table".
SQL> select OWNER, EXTENTS, MAX_EXTENTS from DBA_SEGMENTS where SEGMENT_NAME = 'SYS_LOB0000458190C00005$$';
SQL> alter table SAPR3."FPLAYOUTT" modify lob ("LAYOUT") (STORAGE (MAXEXTENTS UNLIMITED));
SQL> select OWNER, EXTENTS, MAX_EXTENTS from DBA_SEGMENTS where SEGMENT_NAME = 'SYS_LOB0000458190C00005$$';
By the way is there a valid reason why you still use dictionary managed tablespaces? We have passed the Oracle 8i times a looooong time ago
Regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.