If you
connected to SPD Server through a SAS connection, verify that both
the SPD Server Name Server (spdsnsrv) and the SPD Server host (sdpsserv)
processes are running. Issue the UNIX
ps command.
You should see processes for spdsnsrv, spdsserv, spdsbase (row level
integrity proxy), and spdssnet as shown in the following example:
PID TTY TIME CMD
24012 pts/26 00:00:00 ksh
24114 pts/26 00:00:00 spdsnsrv
24116 pts/26 00:00:00 spdslog
24117 pts/26 00:00:00 spdsserv
24119 pts/26 00:00:00 spdslog
24120 pts/26 00:00:00 spdssnet
24130 pts/26 00:00:00 spdslog
24136 pts/26 00:00:00 spdsbase
24139 pts/26 00:00:00 ps
If the
spds* processes are not running, check the log for errors. Unless
you change the log file defaults in
rc.spds, the log paths are the following:
-
InstallDir/log/spdsnsrv.log
-
InstallDir/log/spdsnsrv_mmddyyyy_hh:mm:ss.spdslog
-
InstallDir/log/spdsserv.log
-
InstallDir/log/spdsserv_mmddyyyy_hh:mm:ss.spdslog
-
InstallDir/log/spdssnet.log
-
InstallDir/log/spdssnet_mmddyyyy_hh:mm:ss.spdslog
If there
were problems during start-up and any processes failed to initialize,
terminate the remaining SPD Server processes before re-invoking the
rc.spds script. Use the
killspds shell script
in the
\samples directory, or terminate
the process manually using the UNIX
kill command
as shown in the following example:
$ kill 834 831 832 836 835
Upgrade Notice: If you upgrade from SPD Server 3.
x to SPD Server 4.5, when you are satisfied with
your SPD Server installation, you should copy the libnames.parm file
from your SPD Server 3.x location to your SPD Server 4.5 location.
The new libnames.parm file overwrites the temporary file that was
created when you verified your SPD Server 4.5 installation. The new
file provides you with access to all of the SPD Server 3.
x LIBNAME domains from your previous environment.