CA-Alexandria Database Procedures
Article ID: 56245
Updated On:
Products
Issue/Introduction
CA-Alexandria Database Procedures
Environment
Component: ALEX
Resolution
Table of Contents
Moving the CA-Alexandria Database to Another Machine
1. Shut down daemons on all clients and server.
2. If bits are auto mounted to clients:
Change startup scripts to mount to new server. They can still mount from the old server if the bits are not removed, but this may complicate the next update.
3. Copy the Alex home directory from the old server to the new server.
Edit the passwd and groups files to add Alex.
4. Move the Hardware to the new server.
5. On the new server, link executables to /usr/bin - ./alex-install -FS -IB from platform specific directory.
6. In <alexbkup home dir> /Database, re-create the Def, LCK, and Schema files.
a. Execute: mv Dbase.Def Dbase.Def.old
b.Execute: mv Dbase.LCK Dbase.LCK.old
c.Execute: mv Dbase.Schema Dbase.Schema.old
d. Execute: alex-dbase -cd
e. Execute: rm Dbase.Schema
f. Execute: alex-dbase -B
7. Start daemons. CA-Alexandria should now be functional on server.
Note: If any hardware parameters have changed, CA-Alexandria configuration must also be changed.
8. Execute the following on each client machine:
a. alex-remote -c
{new-server-name}
TCP/IP /dev/null 2>&1&1
b. alex-option -u
{Client-Home-Server new-server-name}
/dev/null 2>&1&1
c. alex-device -Us
{lib-name new-server-name,lib-name}
/dev/null 2>&1&1
new-server-name = hostname of the new server.
lib-name = name of the library from Hardware config.
These steps will be complicated unless consistent library names were used.
9. Start client daemons.
10. On the server change the name of the Database Machine to the new Server for all your op-cards. (If you store the database on the server).
Cleaning Up the Four Scheduling Tables
Description:
This procedure is used for cleaning up possible corruption in the tables that are responsible for scheduling and maintaining active CA-Alexandria processes.
Execution/Installation:
1. Make sure there are no active CA-Alexandria processes running
alex-sched -lq
2. Bring down all the CA-Alexandria daemons
alex-install -q -k
3.When all CA-Alexandria daemons are down, list all the CA-Alexandria database tables
alex-dbase -n
4. Delete the tables Process.1, History.1, Sched-Queue.1, and Inform:
alex-dbase -D Process.1
alex-dbase -D History.1
alex-dbase -D Sched-Queue.1
alex-dbase -D Inform
5. Recreate the same four tables:
alex-dbase -ct
6. List all CA-Alexandria tables and make sure the four tables were recreated
alex-dbase -n
7. Start all the CA-Alexandria daemons
alex-install -q -s
Unloading an CA-Alexandria Database Table to Text File
CA-Alexandria Database Tables may be unloaded to text files to fix corruption. This procedure should only be performed by a highly experienced CA-Alexandria Database Administrator or Support Technician who can determine where corruption exists.
Execution/Installation:
1. Check to see if any CA-Alexandria Processes are running. alex-sched -lp
2. With no processes running, bring down all CA-Alexandria daemons. alex-install -q -k
3. Show a list of the CA-Alexandria tables in correct sytax. alex-dbase -n
4. Enter alex-dbase -u {filename} {tablename} 1 1 1 where filename is the absolute path to the file that the table will be dumped to
5. Make a copy of the file just in case any mistakes are made. cp {filename} {filename1}
6. To edit the file, vi {filename}
7. After making modifications to the file and saving them, delete the dumped table in CA-Alexandria. alex-dbase -D {tablename}
8. Load the text file back into the Database. alex -dbase -l filename tablename 1 19. View the list of CA-Alexandria tables and make sure the dumped table is back in the CA-Alexandria database. alex-dbase -n
WARNING: Unrecoverable damage can occur if this procedure is done improperly. Please make sure you are a skilled CA-Alexandria Database Administrator or call CA-Alexandria Customer Support for assistance.
Feedback
