Hi
I got myself into a bit of trouble and i hope anybody knows a trick to correct things.
A few years ago when we where still at V9.0 i decided in a fit of enthusiasm to convert the index tables to UTS.
All worked great until we had to delete an AG. That fails with:
DSNT408I SQLCODE = -669, ERROR: THE OBJECT CANNOT BE EXPLICITLY DROPPED. REASON 0001
In a UTS you can't drop only the table, you have to drop the TABLESPACE.
I opened a PMR at that time and got the replay that V9 doesn't support UTS, that will be available in V10.
So i accepted that for the time being that whenever an Application Group needs to be deleted i first have to convert it back to Segmented tableSpace. Then the DELETE AG works fine.
But now we run at V10.1 for a while. New tables are created as UTS and i can delete these (newly created) AG without the SQLCODE -669.
However i was surprised that i still get SQLCODE -669 when i try to delete an old (pre-V10.1) AG for which i converted the TS to UTS.
On our test system i tried some hacking. I noticed in ARSSEG the MASK column het bit X'80' set for the new UTS tables, so i set this bit for an old table and then tried a DELETE AG again.
Still SQLCODE -669 !!
So i'm wondering how does CMOD knows this is a new UTS table created by V10.1 and uses a DROP TABLESPACE in stead of a DROP TABLE.
I know i'm going into unsupported area's but we are talking about definitions which must be deleted anyway.
Thanks in advance
Leo de Jong