pbarbosa
7th October 2002, 17:50
Hi

I use BaanIVc4 sch1 and i have some tables in Oracle 7.3....

The table tisfc010 is one of them.
In this table if i make a search , they work correctly and with a acceptable performance. If i press a key "next" they work ok too..... But if i press a "previous" key (oposite key), they works but very slowly..... Why?

The table have 8500 records.

Regards
Paiva

James
8th October 2002, 12:07
Hi Paiva,

I've seen this in tables like tccom010

I vaguely remember changing some parameters in the db_resource file to solve this. Look at your dbsinit and ora_timeout.

You'll just have to try and few different settings and see what works best overall. And of course determine if this solves the problem.

Oracle should be ok. Though try increasing your db_block_buffers parameter if changing db_resource doesn't work.

dave_23
9th October 2002, 20:48
Make sure you're generating statistics on your tables.

Also, check your porting set and Oracle version, if you're not on
6.c1.06.02 you probably should be, and if you're on an oracle
version < 7.3.4.2 you should be as well!

Is this happening in a session? or just in GTM?

Dave

pbarbosa
10th October 2002, 09:28
Originally posted by dave_23
Make sure you're generating statistics on your tables.

Also, check your porting set and Oracle version, if you're not on
6.c1.06.02 you probably should be, and if you're on an oracle
version < 7.3.4.2 you should be as well!

Is this happening in a session? or just in GTM?

Dave

Hi...

My porting set is 6.1c.06.01 and Oracle version is 7.3.2.2.0.
This problem happens in both situations....
But is stranger who alone happens in this table

Regards

dave_23
16th October 2002, 17:19
Make sure your ora_init is 0111000
your dbinit is 021
and your access methods in your ora_storage2
is 0214

Also, you might consider a porting set upgrade.

Dave

pbarbosa
16th October 2002, 17:56
Originally posted by dave_23
Make sure your ora_init is 0111000
your dbinit is 021
and your access methods in your ora_storage2
is 0214

Also, you might consider a porting set upgrade.

Dave

My db_resource

dbsinit:01
lock_retry:”0”
rds_full:10
ora_init:0111000
ora_max_array_fetch:10
ora_max_array_insert:2
ora_timeout:{60,60,60,60,60}
bdb_max_session_scheduled:10
retained_cursors:30
ssts_set_rows:5

and ora_storage

*:*:T:group:0214:5:PCTFREE 5 TABLESPACE datspace INITRANS 3
*:*:I:group:014:5:PCTFREE 5 TABLESPACE idxspace INITRANS 3

dave_23
16th October 2002, 23:29
hmmm -

I'd set
ora_max_array_fetch:2
rds_full:2

unless your doing data loads...

dbsinit:021 - although there is talk of the "2" being obsolete.

and in your ora_storage
switch your index access mode to 0214..

Dave

evertsen
17th October 2002, 00:38
Could also be an indexing problem. If the above suggestions don't help, you could try dumping the table and recreating it with bdbpre/bdbpost.

pbarbosa
21st October 2002, 17:19
Originally posted by dave_23
hmmm -

I'd set
ora_max_array_fetch:2
rds_full:2

unless your doing data loads...

dbsinit:021 - although there is talk of the "2" being obsolete.

and in your ora_storage
switch your index access mode to 0214..

Dave

I make all the alterations that you suggest.... they works.....

Thank you.....
Best Regards