This chapter exists for the purpose of steering you in the right direction in
case of trouble. By the time you’ve reached this chapter, you should be able to
handle any problem that comes up that doesn’t need direct aid from Sybase
So, based on some typical problems that you as a DBA need to solve,
where would you look first? This chapter is useful for review. Read the ques-
tion first, think about how you might solve it, and then look at our suggested
The Server Will Not Come Up
Where do you look first? What needs to be up?
First, check the system errorlog (or event log on NT). Usually there will be an
explicit clue there. Most typically, something has happened to either file per
missions or system memory, and you will discern this from the errorlog.
Other things to check:
Is the network up?
Are there enough resources available (e.g., memory) for the server to
Have you examined all operating system logs?
Are you signed in as the sybase user or an OS system admin? (A common
mistake; you should be signed in as the sybase user to start the server.)
Is the server already started?
Are the environment variables set up correctly? On Solaris, if a file such
as SYBASE.csh is not sourced, the environment variables are not set up
and the server may not start.
Have the file or partition permissions changed?