Kbase 13955: TOP Questions to ask when troubleshooting Sybase DS Installs
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
TOP Questions to ask when troubleshooting Sybase DS Installs
Top issues surrounding installing a Progress Sybase DataServer
1) Make sure that you have the proper Progress products installed.
** If you have a local unix client, you need to have the Sybase
DataServer product installed
** If you have a local windows client, you must have Sybase's NETLIB
product installed
** If you are doing a remote unix client, you need the Progress
Sybase DataServer on the host and Progress Networking where
appropriate
To run our Sybase DataServer product you need SQL Server and
Sybase's Open Call Interface (this gives the DBLIB interface).
Where the product needs to be is highly dependent on the
configuration.
Remote PC to Unix with Progress Networking:
Sybase SQL Server on the unix machine
Sybase OCI on the PC
Remote PC to Unix with Sybase Networking
Sybase SQL Server on the unix machine
NETLIB on the PC
Remote Unix to Unix host
Sybase SQL Server on the host
Sybase OCI on the client side
Local Unix
Sybase SQL Server
** Note at this time Sybase SQL Server bundles OCI in it.
2) Make sure the Sybase SQL Server is running. On Unix you can
issue a variant of the ps command to see the Sybase process
3) Do you need to run PROBUILD ? If so, have you done this ?
The DataServer guide for Sybase gives a helpful chart in the
probuild chapter. It lists what you need to build based on your
configuration. Please refer to it and be sure all link scripts
were generated and run to produce the new executables.
** Before running PROBUILD, make sure the following environment
variables are set:
DLC set to where you installed PROGRESS
PROLOAD = $DLC/probuild
DLCLOAD = $DLC/probuild
PATH should have $DLC/bin, $DLC, $DLCLOAD/eucapp added to it
PROTERMCAP = $DLC/protermcap
PROCFG=$DLC/progress.cfg
PROMSGS=$DLC/promsgs
PROEXE=$DLC/bin (NOTE in item 4 this may change after probuild
is executed)
PROPATH needs $DLC, $DLC/bin, $DLC/src/prodict/syb
4) After running probuild, be sure to set your PROEXE to the new
client executable you generated and if you are doing remote clients
with PROGRESS Networking, make sure you have DTRSRV (Sybase 10) or
SYBSRV (Sybase 4) set prior to starting the DataServer Broker.
Set the following environment variables necessary to
communicate with Sybase
DSQUERY, SYBASE, SYBLIB and have $SYBASE/bin in your PATH
5) If you go into PROGRESS, Sybase DataServer utilities in the
dictionary and no options are available, you must be connected to
a PROGRESS db to get these options (the PROGRESS db can be an
already existing schema holder that you are adding to or an empty
one).
6) If you are using PROGRESS Networking, be sure to use -H -S and
-N on your client connection. -S needs to be the service name
you started the DataServer Broker with. When starting the BROKER,
the Sybase DataServer guide lists $PROBRKR -S servicename. You
should also use -H and -N on this startup.
7) Use the -Dsrc "prgrs_idbuf,1000" client startup connection to
help with communication over the network with Sybase (see kbase
entry under DataServer/Sybase).
Progress Software Technical Support Note # 13955