Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Schildberg, Steffen (steffen.schildbergsap.com)
Date: Mon Apr 02 2007 - 03:53:09 CDT
sorry for the delay in answering your question.
Martin Cordova wrote:
> Betreff: "Duplicated key" errors after importing schema
> I am using MaxDB 220.127.116.11.
> I have noticed that after importing a schema, I have to do a full
> backup otherwise the data will be read only. No problem with that.
Ok, the reason to force a backup is that in this case the load runs without
logging the changes in data. That's why it is so fast (among others).
> What's really a problem is that If I use a sequence to feed a primary
> key during inserts, the first time an insert is executed, i receive a
> "duplicated key...." error, which happens only the first time. After
> that inserts proceed normally.
> Is there a way to avoid this behaviour?
It seems that the Loader in corporation with the kernel in this version does
not generate at all or not the appropriate CREATE SEQUENCE statement during
export of the catalog. At least did the tests here in Berlin reveal this
behavior. I still can't not say what's the reason.
To avoid the duplicate key error you need to create the used sequence with
a start value equal to the last inserted key value directly after your backup
is successfully done.
Sorry for the inconvenience.
SAP Labs Berlin
Sitz der Gesellschaft/Registered Office: Walldorf, Germany
Vorstand/SAP Executive Board: Henning Kagermann
(Sprecher/CEO), Shai Agassi, Léo Apotheker, Werner Brandt,
Claus Heinrich, Gerhard Oswald, Peter Zencke
Vorsitzender des Aufsichtsrats/Chairperson of the SAP
Supervisory Board: Hasso Plattner
Registergericht/Commercial Register Mannheim No HRB 350269
This e-mail may contain trade secrets or privileged,
undisclosed, or otherwise confidential information. If you
have received this e-mail in error, you are hereby notified
that any review, copying, or distribution of it is strictly
prohibited. Please inform us immediately and destroy the
original transmittal. Thank you for your cooperation.
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb