Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 10 OCT 2007 05:32:47PM Tinashe Machingarufu wrote:

Hi guys. I got a persistent problem for the past 2 weeks. I got over 10 temporary volumes with the same tables on my drive. However, my system only requires one such temporary volume at a time to be attached depending on what is processing at that time. This means I am supposed to be doing a lot of detaching volumes and attaching tables as need arises. However, when I do a DETACH_VOLUME, the old volume is not detaching and the new volume is not attaching properly. I am not getting any error msg for this. When I inspect @VOLUMES(2), the new volume seems to be attached but I am getting an error when I try to open any one of the tables in the new volume. Please help, I am stranded!


At 10 OCT 2007 05:39PM [email protected] wrote:

Guessing you have a "system" file which won't allow it to be detached. What files are on the volume?

[email protected]

The Sprezzatura Group Web Site

World Leaders in all things RevSoft


At 10 OCT 2007 05:58PM Tinashe Machingarufu wrote:

Nah! These are only temp volumes. They got nothing to do with System files. The System works perfectly well with neither of them attached. I only require one temp volume to be attached when I do a specific task.


At 11 OCT 2007 08:09PM Karen Oland wrote:

Does it here (and at several customer sites as well), UD 3 and 4, as well as stand-alone using UD3.

Leaves the volume attached - in db manager, there is a "blank" icon instead of any files. also, at that point db manager can't release the volume, since there technically are no files attached.

Don't remember seeing this before (and every now and then it does detach a the volumes correctly on my stand along workstation), but is pretty consistent in 7.2.2 – sometimes have couple dozen empty volumes attached at customer sites, when installing updates.


At 12 OCT 2007 04:25PM Richard Bright wrote:

How about adding a flush and garbagecollect between the detach and attach -

* First detach current_Volume to be sure

Set_Status=0 ; * Make sure status clear
Detach_Volume(Current_Volume)
If Get_Status(Status_Code) then

NewVol=Current_Volume

GoSub Error_Processing

Ret= 0

Return

End	
  • Now flush cache - important
Flush
GarbageCollect
  • Now attach selected volume - all tables
Set_Status=0 ; * Make sure status clear
ATTACH_TABLE(Volume,'','MYAPP','')
If Get_Status(Status_Code) then
  NewVol=Volume
  GoSub Error_Processing
  GoSub ResetRepos
  Ret=0
  Return 
End

Richard Bright

BrightIdeas New Zealand

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/215833421959aa3b8525737000765bf5.txt
  • Last modified: 2023/12/28 07:39
  • by 127.0.0.1