This content has been marked as final. Show 2 replies
The problem most likely does lie within the AUX table definition. The primary key columns are not meant to be modifiable, but it appears that changing the precision on a number column gets applied to the LT table. Will continue looking at this, but I would recommend filing a SR if you need an immediate fix.
Yes, after some experiencies, namely after trying to drop the primary key, i got the error:
WM_ERROR_199 primary key columns cannot be
added/dropped/*modified*/reordered for version enabled tables
... and i found out that primary keys are not meant to be modifiable.
I solved my problem making a workspace-level export of the table, disableVersioning, alter column, enableVersioning and import.
Don't know if it was the best solution, but the problem was solved.
It's maybe relevant adding:
- protection (raise exception) when trying to alter primary key columns.
- more info in the documentation. I read Oracle® Database Workspace Manager Developer's Guide 11g Release 2 (11.2) and i couldn't find anything about this limitation (just in Workspace Manager Error Messages - WM_ERROR_199). Maybe add something in section 1.8 or 4.beginDDL.
Thank you for your help.