cancel
Showing results for 
Search instead for 
Did you mean: 

Table increase with reorganization

oxya_oxya2
Explorer
0 Kudos

Hello,

We are experiencing troubles with online reorganization of tables on our BI7 with oracle 10.2.0.4 with brspace since the size of our tables after the reorganization is bigger than before.

Our SAP system is at the following level:

Software component Release level

SAP_ABA 700 14

SAP_BASIS 700 14

ST-PI 2005_1_700 6

PI_BASIS 2005_1_700 14

SAP_BW 700 16

FINBASIS 600 7

BI_CONT 703 8

SEM-BW 600 7

ST-A/PI 01K_BCO700 0

The system is running under HP-UX B.11 at the release B.11.23 and with a kernel at the level 150.

The oracle patch 10.2.0.4 has been set thereu2019s one month ago.

We did not experienced that problem before the setup of the new oracle patch.

These are the parameters for one of our table, we reorganized and for which the table increased after the operation:

Options for reorganization of tables: SAPR3./BIC/EZDAYSLS1 (degree 1)

1 ~ New destination tablespace (newts) ........ [PSAPUSEREORD]

2 ~ Separate index tablespace (indts) ......... [PSAPUSEREORI]

3 - Parallel threads (parallel) ............... [1]

4 ~ Table/index parallel degree (degree) ...... []

5 - Create DDL statements (ddl) ............... [yes]

6 ~ Category of initial extent size (initial) . []

7 ~ Sort by fields of index (sortind) ......... []

8 - Table reorganization mode (mode) .......... [online]

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

As a result, the table increased from 8 413 184 KB , 1 051 648 blocks and 287 extents, with 10% of free in used blocks to 10 071 616 KB, 1 258 952 blocks and 285 extents with 0% of free in used blocks.

As we have to get some place into our database in order to prepare future increases of tablespaces in our production system, do you know what we do wrong or what need to be changed?

Thanks

View Entire Topic
oxya_oxya2
Explorer
0 Kudos

Hello,

There's nothing into the log about the drop table step. Nevertheless, as the reorganization has been performed with a move into another tablespace, the drop of the table into the old one does impact the size of the table into the new tablespace.

Christophe

0 Kudos

Hello,

two questions here:

1. what's the type of your tablespaces(ASSM etc) for old and new?

2. how you caculate the size and free space from the table? By dbms_space?

--->As a result, the table increased from 8 413 184 KB , 1 051 648 blocks and 287 extents, with 10% of free in used blocks to 10 071 616 KB, 1 258 952 blocks and 285 extents with 0% of free in used blocks.

Regards,

Mike