I have modifed my $BSE/lib/ora/ora_storage parameters to set initial and next sizes for table tfacp200 company 30. I stopped Baan and started Baan again (rc.stop/rc.start). Ran session ttaad4227m000 to create tfacp200 from a sequential dump file. I selected 'Delete existing tables'.

When table tfacp200 was created for company 30 the default initial and next extents were used (16k for initial and 512k for next). Entries in ora_storage are:

tfacp200:030:T:group:0214:5:PCTFREE 5 TABLESPACE baandat INITRANS 3
STORAGE(initial 53M NEXT 1M PCTINCREASE 10)

How can I get this table created with an initial extent of 53M?

Baan version is IVc4 SP8, Oracle 8.1.6, porting set 6.1c.06.07

I have also seen this problem where some lines in the ora_storage are ignored. My way around this problem was to change the default line in the ora_storage file to reflect how I want the table created and create the table and then change the default line back. I don't believe that you have to stop and start Baan for this change to take affect. This is not the best way to resolve your issue but since ora_storage is only read when you create tables or reconfigure it should work OK.

verify that the line is the first line in the file that matches the table name. the file will be read from top to bottem and it will stop reading the file when it finds a line that matches. If you would have a line starting with *:* on the first line all tables will match and use the params on this first line.
(this could sound really obvious but i have seen people making mistakes like this)

It is the very first line after comment lines.

PV Ramone,

I always have the line *:* last in the storage file, but I have some lines for different companies before lines for individual tables. Such as

*:200
TFGLD410:201


Should I try changing the order of these lines. Or shouldn't it matter because they are for different companies.

In your posting you placed it on 2 lines, but everything should be on 1 line or end the first line with a back slash:

tfacp200:030:T:group:0214:5:PCTFREE 5 TABLESPACE baandat INITRANS 3 \
STORAGE(initial 53M NEXT 1M PCTINCREASE 10)

Hope this helps,
Dick

Hi rmbarr,

I've not seen this before - are you sure that the table was deleted from the database?

I've seen sometimes in 'Delete Tables' that the session runs, but without deleting the required table - I've seen this happen when the user Company Number/Package Combination differs from the one of the table which is being deleted.

So check that your environment is consistent.

James

My Baan user 'root' did not have the same package combination as the companies. I changed 'root' and added the back slash when using two separate line.

All seems fine now.

Many thanks to all for your help.

I'm having the same problem with my ora_storage file. I was re-orging a table from the massive DATSPACE tablespace into a separated by Package tablespace. My ora_storage states:

(all on the same line)

ti:786:T:group:0214:5:TABLESPACE BAAN_786_DATA_TI PCTFREE 5 INITRANS 3 STORAGE(INITIAL 40K NEXT 40K MAXEXTENTS 10000 PCTINCREASE 0)

Then when I run a sql for a table with one (1) record in it, here are the results:
BYTES:65536
EXTENTS:1
INITEXTENT:40960
MAXEXTENTS:(unlimited)

The bytes should equal the initial extents, right?

Where else do I have to look for these changes?

- I verified my baan user 'root' to have the correct package comb.

Any suggestions..
Thanks
-Tim

Tim,

The basic storage structure in Oracle is the block. Our block size is 8K, but it can be set to 2K, 4K, 8K, or 16K. Records are stored at the block level. PCTFREE controls how much space in the block is reserved for future update operations. PCTUSED is the level at which the block can empty to before it goes back on the freelist for more insert operations. Contiguous blocks make up an extent which means extents are sized in multiples of your block size. I'm not sure which table you got these numbers from, but I've never seen any record lengths like that in any of our Baan tables. Oracle recommends using uniform extent sizes on tablespaces using three basic extent sizes of 128K, 4M, and 128M. Oracle recommends you set MAXEXTENTS to 1024.

Gilbert Guymer
Database Administrator
Lufkin Industries, Inc.

I will probably have to modify the ora_storage file because it doesn't reflect what you say Oracle recommends.

Also, the table that I referred to is a custom table. Here is the whole entry in dba_segments table:
--------------------------
OWNER: BAAN
SEGMENT_NAME: TTIMSD001786
PARTITION_NAME:
SEGMENT_TYPE: TABLE
TABLESPACE_NAME: BAAN_786_DATA_TI
HEADER_FILE: 92
HEADER_BLOCK: 63393
BYTES: 65536
BLOCKS: 32
EXTENTS: 1
INITIAL_EXTENT: 40960
NEXT_EXTENT:
MIN_EXTENTS: 1
MAX_EXTENTS: 2147483645
PCT_INCREASE:
FREELISTS: 1
FREELIST_GROUPS: 1
RELATIVE_FNO: 92
BUFFER_ DEFAULT:
--------------------------

When I reorg'd this table to go to the separated tablespace, it seemed like it didn't use the ora_storage parameters.

If you're using locally managed tablespaces Oracle will ignore your
storage clause (ie., some of the options in your ora_storage file)

Dave