3.3

Maintaining the Database
55
Starting the day before, allows time for the system to complete this process, which may
take several hours, before you run dbvisit.
n
To check the database structure for errors, dbvisit must perform a cursory check of stories in
the database, including those in the Dead queue. You can shorten the time it takes dbvisit to
examine the database by using dbserver to empty the Dead queue first.
The dbserver command initiates a day-long operation and should be done one day ahead of
the next steps in this procedure. Your system remains online during the operation.
After the dbserver operation is completed, you are ready to clean up the database
offline, by doing the following:
1. Shutdown the system, by completing the following steps:
n
For more details on the procedure for shutting down the system, see the Avid iNEWS
Newsroom Computer System Setup and Configuration Guide.
a. Select all servers.
b. Take the system offline.
c. Log out all users.
The dbvisit command cannot examine stories being edited. You must log out
everyone on the system and stop all news programs on the servers before running
dbvisit.
d. Run the stop all console command on all servers to stop all workstations, wires, and
other devices from making further changes to the database.
After using the stop all command, wait a few seconds for the prompt to reappear. When
it does, proceed to the next step.
c
Ensure system is offline and that you have stopped all network devices. If you do not do
this before cleaning your database, you may corrupt the data when you perform the
cleanup.
2. Start the database cleanup by doing the following:
a. Select only the master computer (typically server A).
b. Enter superuser mode.
c. Type:
dbvisit -d
A message similar to the following appears:
09:31:45 opening database
09:31:45 traversing roots