duplicate Msys tables ?

[Robin]

After following the fabulous advice found here, my data base is appearing
more bulletproof than ever. (It probably just lit on fire as I say this.) I
have on a couple of occassions had to import all of the objects into a new
"clean" database to solve my problems.

Each time I do this I notice another instance of the Msys tables show up.
For example I now have:

MsysObjects - very dimly displayed
MsysObjects1
MsysObjects11
MsysObjects2

I have not yet considered deleting any of them as I understand the
importance of the, normally, hidden system tables. But I'm slightly curious
to know if all the duplicates are necessary or are they simply the copies
that were made when the previous tables were imported. Seems like the last
three in this instance should be able to be removed. Or are they all still
related?

Thank you,
Robin

 

[John W. Vinson]

After following the fabulous advice found here, my data base is appearing
more bulletproof than ever. (It probably just lit on fire as I say this.) I
have on a couple of occassions had to import all of the objects into a new
"clean" database to solve my problems.

Each time I do this I notice another instance of the Msys tables show up.
For example I now have:

MsysObjects - very dimly displayed
MsysObjects1
MsysObjects11
MsysObjects2

I have not yet considered deleting any of them as I understand the
importance of the, normally, hidden system tables. But I'm slightly curious
to know if all the duplicates are necessary or are they simply the copies
that were made when the previous tables were imported. Seems like the last
three in this instance should be able to be removed. Or are they all still
related?

Thank you,
Robin

Make a backup of course but... do delete all the "extra" copies. When you
import all, you should really just import all *of your own* tables, not the
(possibly corrupt) system tables.

 

[Robin]

I will delete the items after a backup is made. Since you mentioned possible
corruption of the extra tables. Do you think it is prudent to do another
decompile,cleanup, etc. ? I just did this and that's what created the last
batch. I wouldn't think it necessary but I'd hate to continue with the
possibility of carrying over the problem I just tried to solve. So far
everything seems to be great, but I don't mind the effort if it has merit.

Thank you very much for your response.
Robin

 

[John W. Vinson]

I will delete the items after a backup is made. Since you mentioned possible
corruption of the extra tables. Do you think it is prudent to do another
decompile,cleanup, etc. ? I just did this and that's what created the last
batch. I wouldn't think it necessary but I'd hate to continue with the
possibility of carrying over the problem I just tried to solve. So far
everything seems to be great, but I don't mind the effort if it has merit.

Certainly a Compact would be indicated, if only to recover the space occupied
by the extra tables.

 

[MARIAZSANETT]

After following the fabulous advice found here, my data base is appearing
more bulletproof than ever. (It probably just lit on fire as I say this.)
I
have on a couple of occassions had to import all of the objects into a new
"clean" database to solve my problems.

Each time I do this I notice another instance of the Msys tables show up.
For example I now have:

MsysObjects - very dimly displayed
MsysObjects1
MsysObjects11
MsysObjects2

I have not yet considered deleting any of them as I understand the
importance of the, normally, hidden system tables. But I'm slightly
curious
to know if all the duplicates are necessary or are they simply the copies
that were made when the previous tables were imported. Seems like the
last
three in this instance should be able to be removed. Or are they all
still
related?

Thank you,
Robin