×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Table Ownership problem??

Table Ownership problem??

Table Ownership problem??

(OP)
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

RE: Table Ownership problem??

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)

RE: Table Ownership problem??

note that there will be no yes/no warnigs - tables will get away immediatly without a good possibility to recover!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

RE: Table Ownership problem??

(OP)
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!

RE: Table Ownership problem??

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

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close