Database slow problem [message #439511] |
Mon, 18 January 2010 00:23 |
allianz2010
Messages: 101 Registered: October 2009 Location: Pakistan
|
Senior Member |
|
|
i have total 18 tables.
1st table has 9 records.
2nd table has 01 record.
3rd table has 01 record.
4th table has 883 record.
5th table has 05 record.
6th table has 17 record.
7th table has 243 record.
8th table has 3432 record.
9th table has 04 record.
10th table has 10 record.
11th table has 743 record.
12th table has 185 record.
13th table has 316 record.
14th table has 614 record.
15th table has 09 record.
16th table has 36 record.
17th table has 05 record.
18th table has 03 record.
i m using oracle database 10g.
i sure thats not enaugh for this database.
i m creating application on this databse in form 6i.
inster, update, delete, select statments use in this databse by using form on the daily
basis.
and now when i use any DML statmetns on this databse then its retrive records very slowly..
what can i do fast my database.
|
|
|
Re: Database slow problem [message #439512 is a reply to message #439511] |
Mon, 18 January 2010 00:50 |
|
rahulvb
Messages: 924 Registered: October 2009 Location: Somewhere Near Equator.
|
Senior Member |
|
|
allianz2010,
Quote:and now when i use any DML statmetns on this databse then its retrive records very slowly..
can you please give a specific example with DDL and DML Queries, Plan output etc Please.
-Rahul
[Updated on: Mon, 18 January 2010 00:51] Report message to a moderator
|
|
|
|
|
|
Re: Database slow problem [message #439925 is a reply to message #439886] |
Wed, 20 January 2010 03:44 |
JRowbottom
Messages: 5933 Registered: June 2006 Location: Sunny North Yorkshire, ho...
|
Senior Member |
|
|
You would only hae a problem with High Watermarks if your tables had previously had a lot more rows in the them than they do now.
The High Watermark is the mark recording the maximum number of rows the table has ever had in it, and when you do a full table scan, the database needs to read up to this mark - thus a table with few rows in it that used to have a large number can take a long time to do a full table scan on.
Can yuo show us the Where clause that is defined on the STOCK_MANAGER block?
I very much doubt that this is a database problem - it's much more likely to be a problem in the Form, or with the computer that Forms is running on.
|
|
|