tmart
03-13-2010, 09:29 AM
Is there a particular reason why we cannot do a "vol copy" into the volcache?
For example: I was working on an instantiated catalog component (prior to branching) and while the app was running I just wanted to start over... so I did a "vol destroy" on the volcache version of that component's boot volume and then expected that I could just copy the boot vol back out of the catalog object into the volcache. But this was the error message:
Destination volume must be a global or application user or singleton class volume.
Of course when I restarted the app, AppLogic recreated the missing volume; however, I really didn't want to have to reboot the entire (very large) app. I know that this isn't commonplace functionality... and in general I wouldn't need to be tinkering with a boot volume on an unbranched class... but is there any good reason why I shouldn't be able to effectively "clean" a volume on a running app? Is there another way without restarting the app?
Thanks.
For example: I was working on an instantiated catalog component (prior to branching) and while the app was running I just wanted to start over... so I did a "vol destroy" on the volcache version of that component's boot volume and then expected that I could just copy the boot vol back out of the catalog object into the volcache. But this was the error message:
Destination volume must be a global or application user or singleton class volume.
Of course when I restarted the app, AppLogic recreated the missing volume; however, I really didn't want to have to reboot the entire (very large) app. I know that this isn't commonplace functionality... and in general I wouldn't need to be tinkering with a boot volume on an unbranched class... but is there any good reason why I shouldn't be able to effectively "clean" a volume on a running app? Is there another way without restarting the app?
Thanks.