Lost partition - lost module access

In our database there is a link module which, according to its properties, is partitioned out. The effect of this is that the module is read-only for all users, including Administrator. Its containing projects have no traces of any partitions, neither partition definitions nor exported partitions, which means that I can't use the rejoin or recover functions. The module history states that it has been partitioned and rejoined once.

(We recently upgraded from 8.3 to 9.2, but I'm pretty certain that the problem existed before migration.)

I want to delete and purge the module, but I'm stuck. Does anyone know how this can be done?

BR,

/David
SystemAdmin - Wed Aug 17 05:17:12 EDT 2011

Re: Lost partition - lost module access
llandale - Wed Aug 17 15:23:03 EDT 2011

I have no idea what I'm talking about, but if this were me I'd do this:
Open module Exclusive
edit DXL:
string ErrMess = setPartitionedOut_(current Module,"whatever",false)
print ErrMess

keep it unsaved and open and see if its still partitioned.

Close the module without saving and report what it did

  • Louie

Re: Lost partition - lost module access
SystemAdmin - Thu Aug 18 03:33:51 EDT 2011

llandale - Wed Aug 17 15:23:03 EDT 2011
I have no idea what I'm talking about, but if this were me I'd do this:
Open module Exclusive
edit DXL:
string ErrMess = setPartitionedOut_(current Module,"whatever",false)
print ErrMess

keep it unsaved and open and see if its still partitioned.

Close the module without saving and report what it did

  • Louie

Good idea, I guess. However, the module cannot be opened Exclusive since it's partitioned out...

Now, keeping an undeleteable link module in the database wouldn't be a huge problem, if it were empty. But this one contains links, which can't be deleted since the link module is read-only.

Other ideas?
(BTW, in the cleanup process following our migration to 9.2, we have found a project that can't be deleted. I have absolutely no clue why. I have full access and have found no indication of anything that would prevent me from deleting it. It can be moved and converted to folder, but not deleted.)

Re: Lost partition - lost module access
llandale - Fri Aug 19 16:08:33 EDT 2011

SystemAdmin - Thu Aug 18 03:33:51 EDT 2011
Good idea, I guess. However, the module cannot be opened Exclusive since it's partitioned out...

Now, keeping an undeleteable link module in the database wouldn't be a huge problem, if it were empty. But this one contains links, which can't be deleted since the link module is read-only.

Other ideas?
(BTW, in the cleanup process following our migration to 9.2, we have found a project that can't be deleted. I have absolutely no clue why. I have full access and have found no indication of anything that would prevent me from deleting it. It can be moved and converted to folder, but not deleted.)

It appears I'm batting 1000 when I way "I don't know what I'm talking about"!

Perhaps run the Integrity Checker as the Administrator.

On a practice database or restoring the project into a playground, I'd be tempted to check the clock, create a partitian, then look through the database for the partitian file which will be the one just modified. Then rename it and see if the phantom lock is gone. There may also be some file inside the module's file hierchy worth playing with.

-Louie