HP 3000 Manuals HP 3000 Manuals
Establishing the Databases and Logging
When establishing databases and logging for your system, ensure that:
* Each database on the primary system is actively logging to the
logfile specified in the configuration file.
* Each database on the secondary system(s) is available for access but
is not enabled for logging.
The steps to follow to establish databases and logging are defined below:
1. Notify all active users to log off the database.
2. On the primary system log onto the user.account,group where the
database resides and disable the database for access:
:HELLO user.account,group/pass
:RUN DBUTIL.PUB.SYS
>>DISABLE dbname FOR ACCESS
>>EXIT
3. The status of TurboIMAGE logging on your system determines your
next step:
a. If TurboIMAGE logging is not active on your system, build a
logfile and enable logging:
:BUILD logfl.group.account;CODE=LOG;DISC=10000,10,10
:GETLOG logproc;LOG=logfl.group.account,DISC; AUTO
The parameters specified for the DISC= keyword of the :BUILD
command vary by system. The values specified depend upon the
rate at which transactions are applied to the database and the
frequency of log cycles.
If automatic logging is active on your system, specify the
AUTO keyword of the :GETLOG command to maintain AUTO
CHANGELOG. If this is not specified, the default (AUTO
CHANGELOG OFF) is in effect.
b. If TurboIMAGE logging is active on your system, turn it off,
alter the log procedure declaration, and ensure it resides in
the same group and account as the database:
:LOG logprocedurename, STOP
:ALTLOG logprocedurename;LOG=logfl.group.account,DISC
FCOPY, or fully qualify, the existing logfile to the
group.account where the database resides.
4. Store all the files in group.account to tape:
:FILE T;DEV=TAPE
:STORE database,logfiles,configfile;*T;SHOW
This copies the database, logfiles, and configuration file to tape
for use when setting up the secondary system.
5. Start logging (for an existing logfile use the RESTART option):
:LOG logproc, START
6. Enable the database on the primary system for access and logging:
:RUN DBUTIL.PUB.SYS
>>SET dbname LOGID=logproc
>>ENABLE dbname FOR ACCESS
>>ENABLE dbname FOR LOGGING
>>EXIT
If the error message Logging is being enabled when no preceding
DBSTORE was done is displayed, ignore it. The MPE :STORE command
used in Step 4 accomplished the database store.
7. At the secondary system System Console, logon to the same
group.account used on the primary system, and restore the files
from the tape created in Step 4. If the group.account stored to
tape from the primary system does not exist on the secondary
system, create it. The group.account and its capabilities,
passwords, and other features must be identical on both systems:
:HELLO user.account,group/pass
:FILE T;DEV=TAPE
:RESTORE *T;@.@;SHOW
This restores the database, configuration file, and logfile from
tape to the specified group.account.
8. Enable the secondary database for access and disable it for
logging:
:RUN DBUTIL.PUB.SYS
>>ENABLE dbname FOR ACCESS
>>DISABLE dbname FOR LOGGING
>>EXIT
9. If you are duplicating more than one database, ensure that the
Recovery Process (RP) on the secondary system can write to each
database not in the group.account. There are two ways to do this:
* Assign the user of group.account System Manager (SM)
capability, or,
* Use DBUTIL on the secondary system to release each database
not residing in group.account. The DBUTIL >RELEASE command
maintains normal TurboIMAGE security.