Date: Thu, 8 Jul 2004 11:08:08 -0400
Reply-To: Cathlene Mc Rae <cathlene_mcrae@HP.COM>
Sender: HP-3000 Systems Discussion <HP3000-L@RAVEN.UTC.EDU>
From: Cathlene Mc Rae <cathlene_mcrae@HP.COM>
Subject: Re: Copying DB with ADAGER with SQLDBE attached.
Copying a image database with an sqldbe attached is not recommended.
The reason: If you copy a image database to another account or group, the
permission on the sqldbe will not be correct. A SQL dbe knows where it
came from and who has access to it. You would not be able to access the
dbe once the imagedb is moved. These notes contain information on how to
move/create/problems with copying an image database attached to sql dbe.
KBRC00000477 & KBRC00002708 & KBRC00002680
It is best to detach the image database from the dbe then copy the image
database to another account, then create a new dbe to attach to the moved
image database. If you are moving the image database to another system
with the same accounting structure, the you must move the image db and all
supporting sqldbe files.
Imagesql will create the 3 AllbaseSql files and 2 ImageSql files.
TC -430 = contains the dbe name(s) the image db is attached
and/or item customization.
CR -431 = contains the imagedb name(s) the dbe is attached.
If the image database is no longer attached to a sqldbe the TC and CR files
will not exist.
dbe -491 = The DBECon file
FL -493 = The DBEFile
LG -497 = The LogFile
Hope this helps.
Cathlene Mc Rae
Sr HP Response Center Engineer
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *