Technical article 100113

ARCserve or ARCserve database keeps shutting down, or a database is unreadable.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

SCO ARCserve is exhibiting one of the three problems listed below:

1. The ARCserve database keeps on shutting down and one of the logs may return the error message:

e1004 failed connect to client agent on 19240.15 connection refused.

A tape record was not added to the database.

2. When booting up, I get the following error message:

RAIMA data manager systems error 904, unable to allocate sufficient memory errno=0: unknown error

3. When attempting to start arc (astart) it seems to start, and then dies.

Cause

It is probable that the ARCserve database files are corrupt.

Solution

To check ARCserve database integrity, take these steps:

To find the databases, use these commands;

# cd /usr/lib/ARCserve/dbase
# find . -name "*.dbd" -print

To check a database use this command:

# ./dbcheck <directory_path/file_name(without .dbd extension)>
     for every file found

Any databases identified as corrupt will have to be restored from backup or restored from ./emptydb and initialized.

An example is provided below:
**************** BEGINNING OF EXAMPLE  **********************

First, follow these steps to find the database files:

# cd /usr/lib/ARCserve/dbase
# find . -name "*.dbd" -print
./FTS/fts.dbd
./FTS/query/db_query.dbd
./SETUP/setup.dbd

Then, follow these steps to check database file integrity:

# ./dbcheck ./FTS/query/db_query
Raima Data Manager Version 3.21A
Database Consistency Check Utility
Copyright (C) 1985-1992 Raima Corporation, All Rights Reserved
----------------------------------------------------------------
Processing key file: ......
Database consistency check completed
0 errors were encountered in 0 records/nodes
# ./dbcheck ./FTS/fts
Raima Data Manager Version 3.21A
Database Consistency Check Utility
Copyright (C) 1985-1992 Raima Corporation, All Rights
Reserved
----------------------------------------------------------------
Processing key file: ......
Database consistency check completed
0 errors were encountered in 0 records/nodes
# ./dbcheck ./SETUP/setup
Raima Data Manager Version 3.21A
Database Consistency Check Utility
Copyright (C) 1985-1992 Raima Corporation, All Rights Reserved
----------------------------------------------------------------
Processing key file: ......
Database consistency check completed
0 errors were encountered in 0 records/nodes
****************** END OF EXAMPLE  *************************
NOTE:     Do not use .. as part of the path in any of these commands,
           even if it seems like it should work.  Due to the use of
           symbolic links, you may not be in the directory you think
           you should be after typing 'cd ..'
Databases that are found to be corrupt may be removed and
restored from backup.  If after restoring databases, errors
still occur, one or more databases may need to be restored
from the ./emptydb directory and then be initialized.

As an example, use the following to remove ./dbase/FTS and replace it with the ./FTS template found in ./emptydb/FTS.

# cd /usr/lib/ARCserve
# rm -r dbase/FTS
# mkdir dbase/FTS
# cp -r emptydb/FTS dbase/FTS

Any database that is removed and replaced will need to be initialized with the appropriate script shown below and will be empty of data.

NOTE:     Use the following to clear or initialize databases.

If FTS/fts database is corrupt or needs to be initialized, enter the following:

# cd /usr/lib/ARCserve/dbase
# ./initdb -y ./FTS/fts >/dev/null 2>&1
# chmod 664 ./FTS/*
# chmod 775 ./FTS/query
# chmod 775 ./FTS/log
# chown bin ./FTS/*

If FTS/query/db_query database is corrupt or needs to be initialized, enter the following:

# cd /usr/lib/ARCserve/dbase
# ./initdb -y ./FTS/query/db_query >/dev/null 2>&1
# chmod 664 ./FTS/query/*
# chown bin ./FTS/query/*

If SETUP/setup database is corrupt or needs to be initialized, enter the following:

# cd /usr/lib/ARCserve/dbase
# ./initdb -y ./SETUP/setup >/dev/null 2>&1
# chmod 664 ./SETUP/*
# chmod 775 ./SETUP/log
# chown bin ./SETUP/*

From the Xinuos technical article database, record 100113. Reproduced with permission. The original is at www.sco.com/ta/100113, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.