SQL Anywhere service started and then stopped
Modified on: Tue, 8 Sep, 2020 at 11:05 AM [Sybase][ODBC Driver][SQL Anywhere]Internal database error *** ERROR ***Assertion failed: 200114 ( SQLSTATE=HY000
ReasonSQLA Bug Fix ( QTS 790977 - Under very rare timing dependent condition an index that has long hash values could throw assertions 200114 (cannot find values) or invalid page assertion. This has been fixed. ):Assertion 200114, Can't find values for row ... in index .. How to resolve
There are 3 possible workarounds to this issue: workaround1: A possible solution is to rebuild the index using:
workaround2: Drop and recreate the index :
DROP INDEX IF EXISTS "dba"."CMS_InfoObjects7"."ObjName_I7"; CREATE INDEX "ObjName_I7" ON "dba"."CMS_InfoObjects7" ( "ObjName" ASC ) IN "system"; workaround 3: Rebuild corrupted database please follow steps below:
Did you find it helpful? Yes No Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback. Mel,
It could be that the server that was running got hung. Use Task Manger to
teminiate all DBSRV11.EXE (or DB Eng...etc). If you are unable to terminate
the hung service via task manger then download PSTOOL and use PSKILL
ServiceName.
Hope this help...
Rachan Terrell
If you start a service, it keeps running until you stop it. Closing Sybase Central or logging off does not stop the service. Stopping a database server service closes all connections to the database and stops the database server. For other applications, the program shuts down.
This Technote addresses an issue where the SQL Anywhere database service will not start from IBM® Rational® Administrator or Services in Control Panel.
The version of SQL Anywhere that ships with IBM Rational ClearQuest® 2001 and 2002 is 5.5.05 Build 2509. SQL Anywhere 5.5.05 is supported by Sybase for Windows 2000 but only if it is Build 2785 or later. Some setups with Build 2509 have the problem that the service will not start. Go to http://www.sybase.com/downloads to download Build 2785 or later. Sometimes installing this later build does not solve the problem either. If the 5.5.05 server is allowed to broadcast during start-up to ensure its name is unique (the default behavior), it will fail to start on Windows 2000. The error is "unable to initialize requested communications links". A work-around to the problem is to use DoBroadcast=no when specifying the TCPIP parameter on the server start line. To add this line click:
[{"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Database Configuration\/Connectivity - SQL Anywhere","Platform":[{"code":"PF033","label":"Windows"}],"Version":"2001a.04.00;2002.05.00;2002.05.20","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
|