on 2017 Feb 16 7:23 AM
Hi.
Is there any limitations in number of services in SQL Anywhere Sybase Central? Currently we have 89 services defined in Sybase Central, but we are only able to start 87. The last 2 services gets the status "Pending" in Windows Services when we try to start it in Sybase Central. Most of these services are tiny databases used in small web applications, so resources are no issue. There are lots of memory, CPU and diskspace available.
We can copy the definition of the service and start dbsrv16.exe with the same parameters without any problems. But the service will not start.
We are currently running SQL Anywhere 16.0.0.2158.
Regards,
Bjarne Anker Maritech Systems AS Norway
Request clarification before answering.
Hi Bjarne,
I doubt that there's a limitation inside SybaseCentral. Can you start the services using the Windows Control Panel / the dbsvc utility / the net start OS command? Can you start the last two services alright when two others aren't running yet? Does the Windows event log show any indications for problems? Do these services have an output protocol file (-o cmd line option)? If so, what's written there?
Cheers,
Volker DB-TecKnowledgy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bjarne,
on the dbsrv16 command line, in the server options part, which is before / left of the first database file name, specify "-o filename" without the quotes. You may have to quote the filename if it contains special characters, just like you do with file names in the cmd shell. Absolute path is recommended, the directory must exist, and it has to be a different filename for each service.
In the SybaseCentral Service setup dialog, it should be the 2nd tab ("Setup"? - I currently only have the German labels in place) with the multi line editor ("Parameters"?). It'll be safe to put the -o and the filename just before your existing options.
BTW, using -o is generally considered good practice, especially when there is no output window to observe the server output.
HTH
Volker
Note, you can manage SQL Anywhere services outside of Sybase Central with the help of the DBSVC command line utility, which supports its own -o parameter, so you can log its output, as well, such as
dbsvc -o C:\\MyLogs\\MyDbSvc.txt -u MySaSvc139
That would start the according service and log the output accordingly.
It seems the log contents is identical to the command line output of the DBSVC utility - but like the server's console log, contents gets added to the end, so you can use the same log for different SA services and service operations (which might be very helpful in your case with very many services on the same box.)
Hi.
During friday afternoon, we suddenly managed to start all services without having to stop any of the other running services. So now, all 89 services are running as normal. My colleague says that he did nothing at all thursday afternoon/evening, and "it just worked" on friday. Strange! Perhaps it was Windows Server that rejected the startup due to lack of resources? However, the server has plenty of RAM and CPU, so don't think that's the reason.
BTW: Adding the -o to the service did not generate any log when trying to start the services on thursday when the problems was occuring.
Anyways, it looks good now. In any case, this could be a good reason to add a second DB-server and offloading some databases to that.
Thanks for all the good suggestions and tips.
Regards,
Bjarne
User | Count |
---|---|
60 | |
10 | |
8 | |
8 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.