 |
|
|
| |
| How can I move a Sablime database to a different location? |
|
|
Applicability: Unix/Linux Sablime
This FAQ is for moving a Sablime database to a different location on the same machine. There is a different FAQ for moving an instance to another machine.
- Turn off the databases, using "dbstop", so that you are working with an unchanging database. If you have more than one product in the Sablime instance you're moving, run the Sablime setup script for a generic in each product, and run "dbstop" for each of the products.
- We recommend you run the audit programs so you can be sure whether problems were introduced by the move or were already in place.
- Move your databases to the new locations. An example of doing this follows. It assumes that both the old and new locations have the four databases located in one parent directory.
mkdir new_sablime_db_dir # if necessary
cd old_sablime_db_dir # location of existing database directory
find adb idb sdb gdb -print | cpio -pdumv new_sablime_db_dir
-
Go to the new Global Database (gdb) PR subdirectory, and modify each file to reflect the new database directories. These are the 6th, 7th, and 8th fields of each "product" record. (Use ssql -help from PR to see the field layout of the PR files).
-
Update your "sablime.sh" and "xsablime.sh" files as necessary to reflect the new database locations (in particular the new GDB location).
Also update the "sabVAR" file(s) that the (x)sablime.sh file references, so that they contain updated paths.
Run sh2x, if necessary, to regenerate your "sablime" and "xsablime" scripts
sh2x sablime.sh sablime
sh2x xsablime.sh xsablime
-
If you have "triggers" (in the $sabLCB "hooks" subdirectory), you'll want to check them also to see if they need updating.
-
Setup and restart at least one product, by running ". sablime some_generic, and then running dbstart. Verify that commands launch properly. Restart the remaining products.
-
If you are using the External MR communications package, you will need to update the ".EMR" file in your Sablime bin with the correct location of the GDB.
Updated 26Apr2006: New
|
|
