Problem 

Solutions 

Socket Error 

1. Did you successfully install the server instance on the machine you are trying to connect to?
2. Is the service running on the machine your are trying to connect to?
3. If you have had a network connection failure on the local machine, you may need to restart the service.

 

One of the endpoints (IP number/ports) in my cluster has changed 

To update the IP of a database instance, it is necessary to update the endpoint in the sysinstances table of the system database on each instance individually. Perform the following steps for each instance in the cluster, including the instance with the new endpoint:
1. Shut the server instance down (by stopping the system service)
2. Run the server instance with NET/Mode configuration option set to 1 on the Command Console (cmd.exe) with:
scimoredb -STARTUP/Instance=0 -STARTUP/Console=1 -NET/Mode=1
replacing the instance number with the local instance number to be updated. Note that this may very well be different to the instance id number in the cluster. This will start the server instance in single-instance mode, to ensure the client will always connect to that one instance.
3. Run the Database Manager and update the sysinstances table with the new endpoint with something like:
UPDATE system.sysinstance SET [endpoint]='new-ip:port' WHERE [id]=instance-id
replacing the appropriate values.
4. Back in the Command Console, press Ctrl-C and then y to stop the server.

Once you have done this for all server instances in the cluster, you can restart the system services for all of the instances. 

Queries are running very slowly 

1. Ensure that there are indexes on columns you are matching against in your WHERE clause
2. Ensure that you have run GENERATE STATISTICS recently
3. Database health and monitoring parameters can be accessed via system database memory tables or through the Monitors sections in the tree view of Database Manager.

 

Is your problem not here? 

Contact Scimore support