dlangschied
Member
All,
I have an issue where I need to refresh my QAD test environment. I am running out of space, but I do have another file system that I can use.
With QAD2014SE, I have a great number of scripts that refer to the database directory as /db/env. I cannot create any new databases there, so I want to put the test databases in /db2/env without changing a lot of code. The simple answer is to use Linux symbolic links. The problem is that I can't with a multi-volume database. Is there a way to do this?
I was specifically thinking of putting the *.db files in /db/env and the extents in /db2/env. Is this a doable option?
Regards,
David Langschied
I have an issue where I need to refresh my QAD test environment. I am running out of space, but I do have another file system that I can use.
With QAD2014SE, I have a great number of scripts that refer to the database directory as /db/env. I cannot create any new databases there, so I want to put the test databases in /db2/env without changing a lot of code. The simple answer is to use Linux symbolic links. The problem is that I can't with a multi-volume database. Is there a way to do this?
I was specifically thinking of putting the *.db files in /db/env and the extents in /db2/env. Is this a doable option?
Regards,
David Langschied