Help!

Mikael A Olesen mao@krifapost.dk
Fri, 13 Oct 2000 12:08:26 +0200


Hi

Thanx for all the answers - but we have already done alle these things and
nothing helps.....
We have had Oracle experts to look at it as well and there are no problems
with out Oracle base.

Still hoping

Regards
Mikael A. Olesen
Programmør
Den Kristelige Fagbevægelse
(tlf) Kontor  +45 8911 2390
(tlf) Hjemmearbejdsplads 8745 0890



                                                                                                     
                    "Fry, Mark"                                                                      
                    <Mark.Fry@COG        To:     'Mikael A Olesen' <mao@krifapost.dk>,               
                    NOS.com>             powerh-l@sphere.swau.edu                                    
                                         cc:                                                         
                    13-10-00             Subject:     RE: Help!                                      
                    12.01                                                                            
                                                                                                     
                                                                                                     




Hi Mikael,

>From the database side, without knowing how the tables in the database are
structured, what the volumes of data in the tables are, and how the indexes
are defined, it's hard to give you a specific answer.  As Michel Adam said,
checking the indexes is probably the place to start.  In a relational
database, indexes are added to speed up retrieval performance, but
conversely they often have a detrimental effect on update performance, so
you have to choose carefully where and when to add indexes.  Also, it
doesn't necessarily follow that adding an index will speed up retrieval -
sometimes it has the opposite effect [if data volumes in the table are low,
or if the number of discrete values in a column is low, or...].  You might
find the best approach to be adding an index, then re-executing the query
to
see what the effect on performance is.  The trick is in knowing where to
add
the index, and which columns to include as segments.

Have you looked at the SQL being passed from QUICK to ORACLE?  To do this,
you can use the dbaudit=full switch on quick, which gives you both
information about the relational transactions, and shows you the SQL being
passed to the database.  This will give you an idea of how tables are being
accessed, and should point you in the right direction for identifying where
an index could speed things up. Before you add any indexes, go into SQLPLUS
and run the same SQL query from there. Does it take a similarly long time?

Other things to look at are on the QDESIGN side.  Are you using SELECT
statements after the file declarations?  These can usually be replaced with
ACCESS statements, which pass the filtering to the database, and can speed
things up tremendously. Something else to check is whether sorting is being
done unnecessarily.  For example, are you using ACCESS ORDERED or ACCESS
ORDERBY <column> in your screen?  This would be forcing the database to
perform a sort before returning the data to the quick screen, and you can
see this in the SQL too - it appears as an ORDER BY clause.  If you're not
worried about the order of the rows coming back, then you could speed
things
up by removing the ORDERED or ORDERBY clause.

Maybe you could start by looking at these, and let us know how you get on?

Best regards,

Mark Fry
Cognos Limited
email: Mark.Fry@Cognos.com



-----Original Message-----
From: Mikael A Olesen [mailto:mao@krifapost.dk]
Sent: 12 October 2000 21:02
To: powerh-l@sphere.swau.edu
Subject: Help!


Hi

Hope this mail gets out on the list - this is my third try!! ?

Are there anyone out there that runs HP on HP3000 on a Oracle database?
We have just moved some of our Image bases to Oracle and have run into
major performance problems. A quick screen takes 2-3% cpu and each search
can take from between 15 sec to 15 minutes! - The normal time is 1-2 sec!

Does anyone out there have any experience on this?

Regards

Mikael Olesen
dkf-Denmark

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.



= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.