We also test with the JDBC drivers for SAP SQL Anywhere (Sybase SQL Anywhere) listed on this page. Buy Pro Version. DbVisualizer is tested with the major databases and JDBC drivers. For databases more commonly used in the industry we. Connecting to Sybase ASE (SybaseToSQL); 3 minutes to read +1; In this article. To migrate Sybase Adaptive Server Enterprise (ASE) databases to SQL Server or SQL Azure, you must connect to the Adaptive Server that contains the databases that you want to migrate.

Appendix A Setting Up the Adaptive Server Anywhere Database Server as a Service

The following section explains the requiredsteps for setting up an Adaptive Server Anywhere database serverto run as an NT service. They are:

1. Start the Adaptive ServerAnywhere server as a service.
2. Set up the ODBCSystem DSN.
3. Set up the Connection Profile.
4. Connect to PowerDynamo.

Start the Adaptive Server Anywhere server as a service

Configure the Adaptive Server Anywhere serveras an NT service by opening the Services folder in the Sybase Central,then clicking Add Service in the right pane.

Follow the instructions in the wizard to definethe new service.

The path you specify in the wizard should pointto dbsrv50.exe for 5.5.04 or earlier versionsof SQL Anywhere. For versions 6.0 or later, the path should pointto dbsrv6.exe.

You must also specify the server name and thedatabase to which PowerDynamo will be connecting.

For more information on services, see the SybaseAdaptive Server Anywhere User's Guide.

Set up the ODBC System DSN

You must next create an ODBC System DSN, whichstores information about how to connect to a data provider. By defininga System DSN rather than a User DSN, the information is accessibleto any user on the local machine.

To create an ODBC System Data Source Name:

1. Start the ODBC Administrator.
2. Select the System DSN tab. The SystemData Source window will open. Click Add.
3. In the Create New Data Source window,select the appropriate ODBC driver and click OK.
4. In the SQL Anywhere ODBC configurationwindow, enter the data source name, the server name, and the databasename. Click OK.

Start-up options for SQL Anywhere 5.5.04 or earlier

If you are using SQL Anywhere 5.5.04 or earlier,you should set some start-up commands in the ODBC configurationwindow, as shown in Figure 12-1.

If you are using Adaptive Server Anywhere 6.0or later, you do not need to set these start-up commands.

Click Options from the SQL Anywhere ODBC configurationwindow. Over and over again and again god is faithful mp3 download full.

Figure 12-1 illustrates how your start-up optionsshould be set if you are using SQL Anywhere 5.5.04 or lower.

Figure 12-1: Startup Options window

If you are connecting to a remote databaseserver, specify this start command:

If you are connecting to a database serveron the same machine as the Web server, and DBCLIENT hasbeen specified, the Agent should be Not Specified. This does notstart the DBCLIENT application, but allowsaccess to the database server.

Selecting Client as the Agent would cause the DBCLIENT applicationto start unnecessarily, causing the local connection to be madethrough the network which would cause a decline in performance.Select Client as the Agent only if the databaseserver is running on a different machine than the Web server.

Set up the Connection Profile

To connect to the appropriate database, createa PowerDynamo connection profile that calls the appropriate ODBCdata source name.

1. In SybaseCentral, select Tools Connection Profiles.
2. Click New.
3. Enter a connection name and selectPowerDynamo as the profile type from the drop-down list. Click OK.
4. Select the appropriate ODBC datasource from the drop-down list.
5. Enter your user ID and password.Click OK.

Connect to PowerDynamo

Once you have completed your connection profile,you can connect to PowerDynamo.

1. In SybaseCentral, select Tools Connection Profiles.
2. Select the connection profile youwant to connect with and click Connect.

Copyright © 2001 Sybase, Inc. All rights reserved.

Troubleshooting

Problem

This technote explains troubleshooting tips for 'unable to connect to database' errors when using Sybase SQL Anywhere IBM® Rational® ClearQuest®.

Symptom

This error appears when attempting to connect to a ClearQuest client to a SQL Anywhere server that is on a different subnet from the server or when using a dial-up connection to the network.

SQLDriverConnect : RETCODE= -1, State=08001, Native Error = 82
SQL Anywhere - Unable to connect to database server: Unable to start specified database.

Cause

Both the SQL Anywhere server and the client send broadcast packets over the network by default when they are started. These packets either get lost or misdirected when they have to pass through a network router which is connecting one or more subnets. Since the client cannot receive the server's broadcast, the client thinks that server does not exist.

Resolving The Problem

There are several levels of troubleshooting to correct this problem.

Test the connection after each step below and don't delete any settings during the process. Once a connection is established, there is no need to implement any further steps.

Level 1 - Add the IP adders or the hostname of the database server to the maintenance tool connection parameters.

Specifying the IP address of the SQL_Anywhere server in the Host entry field when you try to connect to the schema through the ClearQuest Maintenance Tool.

OR

Verify that the cqdbinfo.ini for each database (master and user), located in the directory on the database server where the physical database resides has the QDBConnectHosts= parameter set to the servers host name or IP address. If not add the SQL Anywhere server name or IP address and restart the server.
Level 2 - Turn off the broadcast on the Server

1. On the machine hosting SQL Anywhere, select:
   Start > Programs > Sybase SQL Anywhere Database Server 5.5.05 > Sybase Centralthen Select the Services folder.
2. The Service name that was created to run with ClearQuest should appear in the right window. Right mouse click on the service and select STOP.
3. Right mouse click it again, and go into the properties of the service.
4. On the configuration tab, in the 'parameters for executable' window, add the {dobroadcast=no;host=dbservermachinename} to the TCPIP parameter.
   For example, if the database server name is 'george' then the full command line will look like this:
   
-n cqsqlany -c 2040 -tl 0 -ti 7200 -x TCPIP{dobroadcast=no;host=george}


   The IP address can also be applied instead of the hostname as long as the database server utilizes a static IP address and not DHCP.
5. Test the connection.
   

Level 3 - Turn off the broadcast on the client side
The server connection can be tested by using the Sybase dbclient program located in the rational/sqlany50/win32 directory.
If this connection fails, then a ClearQuest connection will also fail.
The client connection assumes the Sybase defaults so as to mimic what ClearQuest would be using by supplying the service name to the dbclient.

This is illustrated in the following example where the Sql Anywhere service is called cqsqlany:
C:program filesrationalsqlany50win32> dbclient cqsqlany
If that fails, add the nobroadcast and as follows:
..win32> dbclient cqsqlany -x tcpip{dobroadcast=no;host=george}

If the dbclientnow connects, try connecting using the ClearQuest client (leaving the dbclientwindow open).
If this works, then the environment variable can be set on each client that includes the client connection parameters so that it isn't necessary to run the dbclient manually. The value of this environment variable is appended to the dbclientcommand for starting a client connection and overrides the protocols and hosts configuration set in CQ database properties.
Specifically, to turn off broadcasting for TCPIP:

set CQ_SA_OPTIONS=-x TCPIP{dobroadcast=no;host=<host_name>}

Where <host-name>is the network host name of the machine where SQL Anywhere server is running; it can also be an IP address.
Note: Turning off the Broadcast on the Sql Anywhere Server side (Level 2) can also help if the Sql Anywhere Service will not start.

Level 4 - Reset the connection information

By deleting the asasrv.ini file, the SQL Anywhere Service will create a new asasrv.ini file containing the information you specify in the connection string. The asasrv.ini file is normally located in your SQL Anywhere executable directory. For example, the default directory for SQL Anywhere 8 is C:Program FilesRationalSqlAnywhere8win32. This file may also exist in the Windows and Windows System directories as well.

BACKING UP FILES

Company of heroes great war mod. Always make new database back-ups of your schema repository and user databases prior to making schema changes and performing database upgrades. Failure to create back-up copies can limit your ability to recover from a an upgrade failure, design change issues or other unforeseen failures.

Related URL

Document Information

Modified date:
16 June 2018