Re: Moving database to separate dbspace
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I had a similar issue to resolve, developers and test (Q&A) in the
same database
<br>or dbspace. Splitting your users between dbspaces will not help you
with <i>ontape</i>
<br>which is instance oriented. You cannot isolate a dbspace or database
using ontape.
<br>I resolved the problem by creating a second instance so each group
has complete
<br>isolation. You can look this up in the sysadmin guide under <i>multiple-residency.</i>
<br>Hope this helps.<i></i>
<p>have a nice day.
<p>Honda75 wrote:
<blockquote TYPE=CITE>We have 2 databases, train and live, both in the
same dbspace. We use ontape
<br>for backups and have found that we cannot restore to the train side
only,
<br>because train is in dbs0, along with live. If train were in a separate
dbspace,
<br>we could restore to it only and not overwrite live. Need help with
moving train
<br>to a separate dbspace. I know how to create a new dbspace, but what
are the
<br>next steps? Do we need to remove the old version of train first? Can
we just do
<br>a onunload/unload to the new train dbspace?
<br>Thanks so much
<br>CKG</blockquote>
</html>