Switch to standard view 
  Sybase logo
 
 
 



DocID: DC76342-01-1251-01

Topic

Page

1. Accessing current release bulletin information

2. Product summary

3. Special upgrade instructions

4. Changed functionality in this version

4.1 New command line options for OpenSwitch

4.2 Multithreaded coordination module

4.3 Timeout support in the coordination module

4.4 New configuration options

4.5 New coordination mode

4.6 Warnings of capabilities of TDS level change during failover

4.7 User name and password encryption

4.8 New coordination module APIs

5. Known problems

5.1 Known problems with OpenSwitch 12.5.1

5.2 Known problems with Replication Coordination Module

6. Product compatibilities

7. Documentation updates and clarifications

8. Technical support

9. Other sources of information

9.1 Sybase certifications on the Web

9.2 Sybase EBFs and software maintenance

1. Accessing current release bulletin information

A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the release of the product CD, use the Sybase Technical Library Product Manuals Web site.

Accessing release bulletins at the Technical Library Product Manuals Web site

  1. Go to Product Manuals.

  2. Follow the links to the appropriate Sybase product.

  3. Select the Release Bulletins link.

  4. Select the Sybase product version from the Release Bulletins list.

  5. From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.


2. Product summary

Enclosed is Sybase OpenSwitch Server 12.5.1, which is compatible with the following platform and operating system configurations:

Also enclosed is the Replication Coordination Module (RCM), a coordination module for OpenSwitch Server version 12.5.1, which is compatible with the following platform and operating system configurations:

The RCM application contains the following files:

3. Special upgrade instructions

The internal structure of the coordination module library in OpenSwitch 12.5.1 has changed and some APIs have been added, so after installing OpenSwitch 12.5.1, you must rebuild your existing coordination module applications with the new header files and coordination module library.

See the sample Makefile in $OPENSWITCH/sample for an example of how to modify your Makefile.

See the Installation Guide for upgrade instructions.

4. Changed functionality in this version

4.1 New command line options for OpenSwitch

Some command line options have been added:

For information about command line options, see Chapter 3, “Starting and Stopping OpenSwitch” in the OpenSwitch Administration Guide.

4.2 Multithreaded coordination module

The coordination module library libcm has changed from a single-threaded model to a multithreaded model. When libcm was single-threaded, it monitored all incoming notifications, check message queues, and timer queues for each of the coordination module instances serially. With the single-threaded model, if the coordination module needs to deal with multiple OpenSwitch servers, it could hang in many places because the processing of one coordination module connection could delay the processing of the others.

With the multithreaded model, a thread is created for each coordination module instance within the context to receive and process notifications, messages, and timers from one OpenSwitch server. These threads run independently and are not affected by the processing of callbacks on the other threads. Therefore, the notifications and messages from different OpenSwitch servers are handled simultaneously, and server failures are detected instantaneously without any delays introduced by the coordination module.

4.2.1 Recompiling the coordination module

Check your coordination module source code to ensure that these rules are followed:

After verifying that your coordination module program adheres to these set of rules you must recompile your coordination module with the newest cm.h header file (located in $OPENSWITCH/include on UNIX and %OPENSWITCH%\include on Windows) and link it with the newest libraries.

If you need to modify your coordination module program to adhere to these rules, use the cm1.c program in the $OPENSWITCH/sample directory as a guide.



Note:

When linking the coordination module on Sun Solaris and HP Tru 64 UNIX platforms, you must add -lrt to the link line in your Makefile. As an example, see the OSW_LIBS in the sample Makefile located in $OPENSWITCH/sample


4.3 Timeout support in the coordination module

You can now define timeout values other than the 60-second default for the coordination module applications’ connections to the OpenSwitch server. See the timeval variable in the cml.c sample located in $OPENSWITCH/sample on UNIX and %OPENSWITCH%\sample on Windows for an example of how to set this in your application.

For information about compiling the coordination module, see the Coordination Module Reference Manual.

4.4 New configuration options

There are new configuration options in OpenSwitch 12.5.1. If you are using the configuration file from your previous OpenSwitch installation, add the new configuration options that are applicable to your environment.

The new configuration options and their default settings are:

For a description of the new configuration options, see Chapter 4, “Using the Configuration File” in the OpenSwitch Administration Guide.

4.5 New coordination mode

The coordination mode indicates how Adaptive Server should respond in the presence of a coordination module. OpenSwitch 12.5.1 has a new coordination mode:

ENFORCED – the presence of a coordination module is required. If a coordination module is unavailable when a client makes a request, the request is refused and an informational message is sent back to the client.

ENFORCED is the recommended coordination mode in the configuration of OpenSwitch when using the RCM. the coordination mode ALWAYS still works correctly, but ENFORCED is recommended.

4.6 Warnings of capabilities of TDS level change during failover

During a failover, OpenSwitch verifies that the capabilities and tabular data stream (TDS) level of the new Adaptive Server Enterprise match those of the Adaptive Server the connection was originally established with. If they do not match, a warning is written to the log file. If an application has problems because of this difference, terminate, then restart, the application.

4.7 User name and password encryption

You can configure OpenSwitch to use encrypted user names and passwords for the user name and password entries in the OpenSwitch configuration file. See Chapter 4, “Using the Configuration File” in the OpenSwitch Administration Guide.

4.8 New coordination module APIs

There are six new coordination module APIs:

See the Coordination Module Reference Manual for more information.

4.9 Starting OpenSwitch as a service on Windows

In OpenSwitch 12.5.1, you can start OpenSwitch as a service on Windows. See “Starting OpenSwitch” in the Installation Guide for instructions on how to start OpenSwitch as a service on Windows.

5. Known problems

5.1 Known problems with OpenSwitch 12.5.1

This section describes known problems in OpenSwitch 12.5.1.

5.1.1 Error in configuring the sample Replication Server when Replication Server is installed in the same SYBASE location as ASE and OpenSwitch

[CR #355040] If ASE, OpenSwitch, and Replication Server are installed in the same SYBASE location, Replication Server throws an error in configuring its sample Replication Server. This happens only when OpenSwitch is configured to use the ASE that already has an entry in the interfaces file on UNIX and sql.ini file on Windows.

Workaround: Before installing Replication Server in the same installation location as OpenSwitch, check the $SYBASE/interfaces file on UNIX and %SYBASE%\ini\sql.ini on Windows and remove any duplicate server name entries if they exist.

5.1.2 Client connects to OpenSwitch even if invalid CMON user name is specified

[CR #352059] The client connects to OpenSwitch as a normal user (connected to the primary Adaptive Server) even if an invalid CMON user name is specified in the OpenSwitch configuration file. This leaves the client in an undefined state when OpenSwitch is configured for HAFailover mode and a failover occurs to the secondary Adaptive Server.

Workaround: Specify a valid CMON user name in the OpenSwitch configuration file. The CMON user name is valid if that user is a valid Adaptive Server user.

5.1.3 CMON_USER and CMON_PASSWORD not configurable

[CR #314085] Currently, CMON_USER/CMON_PASSWORD are configurable at the OpenSwitch level ([CONFIG] section), which applies to all servers, and are not configurable in the [SERVER] section, which applies to the server only. This functionality is scheduled to be in a future release.

5.2 Known problems with Replication Coordination Module

5.2.1 On HP platforms, RCM may hang after execution of a user-defined executable/script

[CR #353088] The RCM allows execution of user-defined executables/scripts when certain major events occur. For example, a user can specify that an e-mail be sent if the RCM loses its connection to OpenSwitch. RCM may hang after execution of this user-defined script.

When running on an HP platform and detecting an RCM event, RCM correctly runs the specified user-defined executable/script and continues processing the tasks pertaining to the event, but then RCM fails to detect any subsequent events.

Workaround: Do not run a user-defined executable/script when encountering RCM events.

6. Product compatibilities

OpenSwitch 12.5.1 is compatible with:

The RCM 12.5.1 is compatible with:

7. Documentation updates and clarifications

This section discusses documentation updates and clarifications.

7.1 Administration Guide

7.1.1 Pool connection caching, Maintaining properties, options, and database context in cached connections

The connection’s server name, user name, and password are fixed when the cache is established. However, you can change other connection properties dynamically when the connection is opened. For example:

.Follow these guidelines to avoid problems with inconsistent connection state:

8. Technical support

Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.

9. Other sources of information

Use the Sybase Getting Started CD, the Sybase Technical Library CD, and the Technical Library Product Manuals Web site to learn more about your product:

9.1 Sybase certifications on the Web

Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on product certifications

  1. Point your Web browser to Technical Documents.

  2. Select Products from the navigation bar on the left.

  3. Select a product name from the product list and click Go.

  4. Select the Certification Report filter, specify a time frame, and click Go.

  5. Click a Certification Report title to display the report.


Creating a personalized view of the Sybase Web site (including support pages)

Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.

  1. Point your Web browser to Technical Documents.

  2. Click MySybase and create a MySybase profile.


9.2 Sybase EBFs and software maintenance

Finding the latest information on EBFs and software maintenance

  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. Enter user name and password information, if prompted (for existing Web accounts) or create a new account (a free service).

  3. Select a product.

  4. Specify a time frame and click Go.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.




Back to Top
© Copyright 2010, Sybase Inc.