file: /controls/database/diagnostic_help.txt

0. Try console access to the databases...
On a console start D81 to check accdb.
If D81 fails to stage or load, there are other (non database) problems.
If D81 displays a list of users, then the database is accessible, and the
problem is either a resource lock (see the help for the Blk column in D81),
or the database may be very busy resulting in programs getting timeouts
(Clicking on re-display several times may help you catch the likely task,
 as the display by default is sorted to put active tasks on top.)
If D81 fails to finish initializing (yellow background chars in upper left),
then the ADBS/CDBS server on gravastar.fnal.gov is unreachable from this consol
(It will actually time out, finish init, and report SQL_NOTAVAIL after a
minute or two.)  If D81 displays an error message, that message pertains to
the ADBS/CDBS server on gravastar.fnal.gov.  Proceed to step 1.

On a console start D82 to check appdb.
If D82 fails to stage or load there are other (non database) problems.
If D82 displays a list of users, then the database is accessible, and the
problem is either a resource lock (see the help for the Blk column in D82),
or the database may be very busy resulting in programs getting timeouts
(Clicking on re-display several times may help you catch the likely task,
 as the display by default is sorted to put active tasks on top.)
If D82 fails to finish initializing (yellow background chars in upper left),
then the ADBS/CDBS server on gravastar.fnal.gov is unreachable from this consol
(It will actually time out, finish init, and report SQL_NOTAVAIL after a
minute or two.)  If D82 displays an error message, that message pertains to
the ADBS/CDBS server on gravastar.fnal.gov.  Proceed to step 1.

On a console start D83 to check srdb.
If D83 fails to stage or load there are other (non database) problems.
If D83 displays a list of users, then the database is accessible, and the
problem is either a resource lock (see the help for the Blk column in D83),
or the database may be very busy resulting in programs getting timeouts
(Clicking on re-display several times may help you catch the likely task,
 as the display by default is sorted to put active tasks on top.)
If D83 fails to finish initializing (yellow background chars in upper left),
then the BDBS server on binary.fnal.gov is unreachable from this console.
(It will actually time out, finish init, and report SQL_NOTAVAIL after a
minute or two.)  If D83 displays an error message, that message pertains to
the BDBS server on binary.fnal.gov.  Proceed to step 1.


1. Check to see that the nameserver is working...
On any machine:
 $ nslookup gravastar.fnal.gov
 $ nslookup binary.fnal.gov
each should result in a response similar to this:
 Server:   131.225.121.4
 Address:  131.225.121.4#53

 Name:   gravastar.fnal.gov
 Address:  131.225.121.36
If not, contact Jim Smedinghoff.

2. Check network connectivity...
On any machine:
 $ ping -c 3 gravastar.fnal.gov
 $ ping -c 3 binary.fnal.gov
each should result in a response similar to this:
 PING gravastar.fnal.gov (131.225.121.36): 56(84) data bytes
 64 bytes from gravastar.fnal.gov (131.225.121.36): icmp_seq=0 ttl=254 time=0.219 ms
 64 bytes from gravastar.fnal.gov (131.225.121.36): icmp_seq=1 ttl=254 time=0.236 ms
 64 bytes from gravastar.fnal.gov (131.225.121.36): icmp_seq=2 ttl=254 time=0.207 ms
 --- gravastar.fnal.gov ping statistics ---
 3 packets transmitted, 3 packets received, 0% packet loss, time 2001ms
 rtt min/avg/max/mdev = 0.200/0.232/0.264/0.032 ms, pipe 2
If not, contact the networking group.

3. Make sure sybase interface file is intact and not recently changed...
On a machine that cannot talk to the database (ie. a console):
 $dir/date=mod sybase:interfaces
should result in a response similar to this:
 Directory SYS$SYSDEVICE:[XCONSOLE]
 INTERFACES.;59        1-DEC-2000 01:34:11.87
 INTERFACES.;58       30-NOV-2000 17:23:59.81
If file is recently changed, try renaming the newest file out of the way and
then do a CNSRUN. (ie. $rename INTERFACES.;59 NEW_INTERFACES.)
If file is missing copy from DWIN_DISK:[DWIN.DOWNLOAD.XCONSOLE]INTERFACES.

4. Check database connectivity...
On a machine that cannot talk to the database (ie. a console):
 $isql -S ADBS -U "nobody" -P "nobody"
should result in a response similar to this:
 1>
at the 1> prompt type:
 quit
should result in the command line prompt returning.
If you get an error instead of the 1> prompt, the database may be broken.
If you hang or timeout, the database may be temporarily locked, real busy or
hung up in some bad condition.

AND/OR

 run acnet$exe:wait4accdb.exe
 run acnet$exe:wait4appdb.exe
These will return to the VAX prompt if they find the database, otherwise they
will wait (hang) until it is available...

5. Follow the separately published document explaining the procedure for
   performing a software reboot of the database server in question.