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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Table Ownership problem??

Status
Not open for further replies.

seniorpeon

Programmer
Feb 12, 2002
4
US
I am trying to drop a table in my database (so that I can rebuild it with no indexes and load a bunch of data into the table in a faster manner). The vendor of the accounting software that set up this informix database says:

...
There may be different
glg_gen_mstr tables owned by two different people.
...
you may have to drop them individually
because they are probably owned by somebody different.

When I use

DBACCESS

and do the following:

Drop
Table
glg_gen_mstr (table name)

I get:

214: Cannot remove file for table (bsi.glg_gen_mstr).
106: ISAM error: non-exclusive access.

(There are no other users on the box.)

Is this really an ownership issue?
If so, how do I change the ownership (other tables, that I am able to drop looks like this: 'bsidba'.ar_acct_mstr whereas the offending table looks like this: glg_gen_mstr)

I have spoken given this info to the vendor, but haven't heard back from them yet.

TIA
 
You should ba a table owner or dba - in your case - "bsi" or "informix", and !!! attach to database containing table first (this is not in your script)!!!

you can :

drop table bsi.glg_gen_mstr restrict ;
not touching constraints (good idea)

drop table bsi.glg_gen_mstr cascade ;
dropping references indices views associated with table (bad idea)
 
note that there will be no yes/no warnigs - tables will get away immediatly without a good possibility to recover!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 
Thanks gheist, for you tip. I didn't know about the less scary option for dropping a table. In this case my errors were caused by a "leftover" job running that really was blocking the table being dropped. I'm new to Unix and these phantom jobs keep rearing their ugly head. I'm going to have to get used to boucing informix/the system as a first try to fixing problems!
 
there shoild be some graceful way for stopping database clients

like onstat -u shows them
and onmode -z <session number> kills then - no need to reboot whole system/informix
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top