About answer to 2th question: Where can I found this information?
Whether will Maxdb distribute some feature to display this informaion? You know,it is important to performance tuning.
About answer to 4th question:
In fact,in my test which is tpc-c maxdb don't work well because of deadlock;even if we changed these parameters。If we reduced the REQUEST_TIMEOUT's value, the rollback was too much.If we change the value of DEADLOCK_DETECTION,we didn't see any new phenomenon.Can you explain how to use the DEADLOCK_DETECTION and what's the meaning of it?
questionFrom: "Zabach, Elke" <[EMAIL PROTECTED]> To: "liu xiaotao" <[EMAIL PROTECTED]>, <[email protected]> CC: <[EMAIL PROTECTED]> Subject: AW: Why I can't get response Date: Fri, 1 Apr 2005 08:48:08 +0200
liu xiaotao wrote:
>
> I've ever ask some question but can't get reponse.So I ask this
> again, who can help me?to
>
> I want to ask four question about MaxDB 7.5.Please help me!
>
> One,are there index reorganiztion and merge function in maxdb? And how
something having to do with some kind of reorganization (see above)?> use it?
NO reorganization in MaxDB needed.
What do you mean with 'merge-function'? A function like substr/length or
shuold
>
> Two,how to get information about the execution plan in maxdb? (It
non-user-read/understandable form.> not be explain functon,which is too simple).
Only explain available for users.
For developers some other info is available, but in a
generate
>
> Three,can you give me a test case which will generate a deadlock and be
> tested by maxdb,then maxdb cancel one of the transactions which
I> deadlock.
As with all all database systems, a testcase will be:
Transaction A Transaction B Update record xyz Update record abc Try to update/read (with isolation level > 0) record abc Try to update/read (with isolation level > 0) record xyz
>
> Four,whether maxdb has function to kill deadlock by user and where can
REQUEST_TIMEOUT> find it?
To kill if deadlock happened? None
To help shortening waiting times: see installation parameter
To help finding DEADLOCKS (if it is not such easy one with exactly twotasks concerned. See parameter DEADLOCK_DETECTION, which will (per default) have an acceptable value of 4.
http://messenger.msn.com/cn
Elke
SAP Labs Berlin
>
> _________________________________________________________________
> 与联机的朋友进行交流,请使用 MSN Messenger:
>http://lists.mysql.com/[EMAIL PROTECTED]
>
> --
> MaxDB Discussion Mailing List
> For list archives: http://lists.mysql.com/maxdb
> To unsubscribe:
_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
