Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to drop table, corrupt SYSTABLES

Status
Not open for further replies.

bluealien

MIS
Jan 27, 2005
2
US
So I've got this pretty sizeable DB that I can't unload because it gets stuck on SYSADM.COMMSQL. COMMSQL shouldn't *truly* exist, so I think "no problem, I'll drop it". Problem is, it won't drop:

"Table has not been created".

Yet the table quite clearly exists. If I create it, it just creates another COMMSQL, and I somehow end up with two of them. I get some phantom errors regarding foreign keys in some user tables, but it all comes down to this issue in SYSTABLES. So...

Anyone got any ideas how I can either drop this table, or unload SYSTABLES (that hangs), or ammend SYSTABLES to remove any reference to COMMSQL?
 
Do you try and drop it as 'SYSADM' ? Or try logging on as the table owner before dropping it.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top