Pure bvllsh1t.
Slap a sql trace on the process and find out what's actually going on. Stop
the madness before some damager makes a stupid decision...
In the end, they might be right. But isn't it better to be certain?
on 11/17/03 3:49 AM, Carel-Jan Engel at [EMAIL PROTECTED] wrote:
Hi
Hi Tim, and all others for your replies. Reminds me I've forgotten to close
this thread. Some 'specialist' of the reseller came along, still convinced
the characterset was wrong. Until he had to admit that he'd forgotten to
create an index..
I was just asking the question to the List
At 18:24 17-11-03 -0800, you wrote:
Hi,
Since everyone is just guessing, can you say more detail about the
bad performance? High CPU usage with no idle so client wait for CPU time?
or Low CPu usage but client still wait? or High disk io rate with 100%
disk busy?
Can you show us some
Hi List,
One of my customers gets HP Servicedesk 4.5 implemented. The database that
has been created by on of the DBA's for the application is Oracle 8.1.7.4,
on AIX 4.3.
The database has characterset UTF8, which is the standard here.
Now ServiceDesk has bad performance. HP claims that the
Carel-Jan,
About two weeks ago, Faan DeSwardt [EMAIL PROTECTED] posted to the thread
Unicode: UTF-16 to UTF-8 conversion, saying UTF-8 is variable-length encoding
and so is slower than the fixed-width UTF-16, and also US7ASCII. Maybe it's the
same issue here comparing UTF-8 with WE8ISO8859P15.
Hi!
Only string manipulation/comparision is slower with variable width charsets
than with fixed width ones, because with variable width ones (UTF-8) you
have to check the highest bit of each byte to check whether it shows that
the next byte is part of current character or is part of next
At 10:34 17-11-03 -0800, you wrote:
Performance depends on a lot of things, such how much string operations you
got, what are the contents of your strings (are they mainly latin chars or
are there lots of asian ones etc..).
Tanel.
Thanks Tanel for your respond. I doubt whether a query will go
Thanks Yong. I doubt whether this can have such a significant effect, or it
must be that due to some incompatability an index can't be used (or simply
isn't even there). They have to trace the session, alas I'm not allowed to
touch the system (other project, other budget blah blah)
At 06:54
Here's a wild guess. If the character set is changed, a 10 MB segment (from the
first extent to high water mark) may become 20 MB or 5 MB. Then CBO changes the
plan and it happens to be a bad one.
Yong Huang
--- Carel-Jan [EMAIL PROTECTED] wrote:
At 10:34 17-11-03 -0800, you wrote:
No characterset changed yet. They want us to recreate the database. the
system is going live in a few weeks. I simply hate changing things because
someone says so. It might be the quickest solution, but most probably not,
and then it's a waste of time, energy etc.
Here's a wild guess. If the
Carel-Jan
Look at it this way. Easier to fix the character set now. And if the
performance is still bad, then they've got one less excuse. Being a DBA
means learning to live with disappointment.
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Monday,
DENNIS WILLIAMS wrote:
Being a DBA means learning to live with disappointment.
Well said, well spoken, Dennis.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Daniel Fink
INET: [EMAIL PROTECTED]
Fat City Network Services-- 858-538-5051 http://www.fatcity.com
The fun part is that if the database will perform better after recreation
for some reason, then the HP guys (and probably your bosses) will tell you,
we said so or smth like that :)
Of course when performance goes bad again after a week, HP guys will
probably ask for a block size change + db
I really hate to admit it, but I agree. Doing otherwise is a simple recipe for
hypertension, stroke an early death. Besides, it's so much more gratifying be
able to say I TOLD YOU SO.
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-Original Message-
Sent: Monday, November
Hi,
Since everyone is just guessing, can you say more detail about the bad
performance? High CPU usage with no idle so client wait for CPU time? or Low CPu usage
but client still wait? or High disk io rate with 100% disk busy?
Can you show us some data about your aix box and statspack
15 matches
Mail list logo
