Joerg von Frantzius wrote :
>Hi all,
>when I issue these simple commands on a vanilla demo database:
>------
>create table "_documentTypes" ("name" varchar(255) not null, "plural"
>varchar(255) not null, "modifier" varchar(255) not null, "xPosition"
integer
>not null, "yPosition" integer not null, "enableCaching" varchar(255) not
>null)
>create index "_documentTypes_name" on "_documentTypes"("name")
>alter table "_documentTypes" add primary key ("name")
>------
>I will get the following error on the last command:
>"[-9205] System error: AK Catalog information not
>found:00000000000002AD00670001"
This is a bug. The alter table implementation does not expect, that a column
to become a key is already indexed.
Since SAPDB stores tables in B* trees sorted by the key, an index over the
key makes no sense and therefore is not permitted.
The correction of this bug will drop the index explicitly.
Until then please drop the index by hand before altering the table.
>When I try to add the primary key first and create the index afterwards, it
>says that that column is already indexed, although I can't see any index
for
>the table in SQLStudio.
This is the expected behavior. Maybe the error explanation is a little bit
misleading.
Thomas
---
Thomas Anhaus
SAPDB, SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
