Sample Code/Error
Failed to execute: 'ALTER TABLE DSSMDSYSPROP ADD PRIMARY KEY (NAME)'
Execute Query failed.
Error type: Odbc error. Odbc operation attempted: SQLExecDirect. ORA-02260: table can have only one primary key
This will be accompanied by an entry of the following nature in the DSSErrors log file on the Intelligence Server machine:
2011-11-14 10:50:33.379+02:00 Execute Query failed.
Error type: Odbc error. Odbc operation attempted: SQLExecDirect. ORA-02260: table can have only one primary key Connection String: DSN=Migros_Metadata;UID=MICRO;HOST=10.34.2.187;PORT=1521;SID=MICRO;. SQL Statement: ALTER TABLE DSSMDSYSPROP ADD PRIMARY KEY (NAME).
The error persists when attempting the upgrade from multiple Windows 2008 machines and after creating a new ODBC DSN connection via the Strategy Connectivity Wizard.
CAUSE:This issue is thrown due to the presence of more than one primary key on one of the Oracle tables.
ACTION:It is possible to resolve this issue by running the following SQL from the DB Query Tool to drop the primary key manually from the related table before running the upgrade process:
ALTER TABLE DSSMDSYSPROP
DROP PRIMARY KEY CASCADE;
Metadata Modification:WARNING:Manually editing values in the Strategy Metadata incorrectly may cause serious, project-wide problems that may make your project unusable. Since these are user-initiated changes, they are not covered by any Strategy warranty. Users are strongly encouraged to backup Metadata prior to any alteration. Third Party Software Installation:WARNING:The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
