Hello all,
first of all, a little background information on how we use :
Our ASP provider uses a windows 2003 db server, where +- 300 sybase 9 (Adaptive Server Anywhere 9.2) engines were running (the process for sybase 9 is dbsrv9.exe).
Last year we start migrating towards sybase 16, but for us it's impossible to migrate evrything at once, so we are migrating one by one.
The current situation is 200 sybase 9 engines and +- 100 sybase 16 engine on the db server.
Our ASP provider informed us, that since windows 2003 was ending, they wanted to migrate to a windows 2012 db server.
We did this migration 2 weeks ago.
All the sybase 16 engines were migrated without any problem, and we could start them just fine.
With the sybase 9 engines we encountered a very weird problem :
as said we have 200 engines left, that we wanted to start, but for some reason, we could only start 175 engines.
The other 25 engines refused to start, the only error they gave was "Could not start DB server"
That was the only error we received, nothing more. in the event log, in the sybase log, everywhere we got "could not start db server"
At that time we started to change serverports, we started to use different admin db's the service uses, started to remove db's out of the service, but nothing helped.
We even tried to raising the number of sybase 9 licences with the dblic command, but same error.
What we then noticed was the following : when we stopped service nr 170, we could start a service (that refused to start with the "could not start db server" error) just fine, but service nr 170 refused to start now ...
That's how we started to play around with services, when we stopped a service, we could start another one just fine ... so it seems that there is a cap on simaltaneous engines.
The questions we have now :
Is the cap a problem of sybase 9? (allthough we had it running just fine on a windows 2003 server).
Is this a windows 2012 problem? (my idea is that this is a windows 2012 problem, but can't be sure at the moment)
Are we going to have the same problem with sybase 16?
Biggest problem right now, is the 175 cap on services, cause we can't start some of our services.
We are converting them as fast we can towards sybase 16, but as of now there are clients of us that can't work.
So if anyone can give us some tips or advice, we would be very obliged
Regards,
Stephen