What s New in Replication Server?

Transcription

1 What s New in Replication Server? Replication Server 12.6

2 DOCUMENT ID: DC LAST REVISED: October 2003 Copyright by Sybase, Inc. All rights reserved. This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. To order additional documents, U.S. and Canadian customers should call Customer Fulfillment at (800) , fax (617) Customers in other countries with a U.S. license agreement may contact Customer Fulfillment via the above fax number. All other international customers should contact their Sybase subsidiary or local distributor. Upgrades are provided only at regularly scheduled software release dates. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Sybase, Inc. Sybase, the Sybase logo, AccelaTrade, ADA Workbench, Adaptable Windowing Environment, Adaptive Component Architecture, Adaptive Server, Adaptive Server Anywhere, Adaptive Server Enterprise, Adaptive Server Enterprise Monitor, Adaptive Server Enterprise Replication, Adaptive Server Everywhere, Adaptive Server IQ, Adaptive Warehouse, Anywhere Studio, Application Manager, AppModeler, APT Workbench, APT-Build, APT-Edit, APT-Execute, APT-FORMS, APT-Translator, APT-Library, AvantGo, AvantGo Application Alerts, AvantGo Mobile Delivery, AvantGo Mobile Document Viewer, AvantGo Mobile Inspection, AvantGo Mobile Marketing Channel, AvantGo Mobile Pharma, AvantGo Mobile Sales, AvantGo Pylon, AvantGo Pylon Application Server, AvantGo Pylon Conduit, AvantGo Pylon PIM Server, AvantGo Pylon Pro, Backup Server, BizTracker, ClearConnect, Client-Library, Client Services, Convoy/DM, Copernicus, Data Pipeline, Data Workbench, DataArchitect, Database Analyzer, DataExpress, DataServer, DataWindow, DB-Library, dbqueue, Developers Workbench, Direct Connect Anywhere, DirectConnect, Distribution Director, e-adk, E-Anywhere, e-biz Integrator, E-Whatever, EC Gateway, ECMAP, ECRTP, efulfillment Accelerator, Embedded SQL, EMS, Enterprise Application Studio, Enterprise Client/Server, Enterprise Connect, Enterprise Data Studio, Enterprise Manager, Enterprise SQL Server Manager, Enterprise Work Architecture, Enterprise Work Designer, Enterprise Work Modeler, eprocurement Accelerator, EWA, Financial Fusion, Financial Fusion Server, Gateway Manager, GlobalFIX, ImpactNow, Industry Warehouse Studio, InfoMaker, Information Anywhere, Information Everywhere, InformationConnect, InternetBuilder, iscript, Jaguar CTS, jconnect for JDBC, Mail Anywhere Studio, MainframeConnect, Maintenance Express, Manage Anywhere Studio, M-Business Channel, M-Business Network, M-Business Server, MDI Access Server, MDI Database Gateway, media.splash, MetaWorks, My AvantGo, My AvantGo Media Channel, My AvantGo Mobile Marketing, MySupport, Net-Gateway, Net-Library, New Era of Networks, ObjectConnect, ObjectCycle, OmniConnect, OmniSQL Access Module, OmniSQL Toolkit, Open Biz, Open Client, Open ClientConnect, Open Client/Server, Open Client/Server Interfaces, Open Gateway, Open Server, Open ServerConnect, Open Solutions, Optima++, PB-Gen, PC APT Execute, PC Net Library, PocketBuilder, Pocket PowerBuilder, Power++, power.stop, PowerAMC, PowerBuilder, PowerBuilder Foundation Class Library, PowerDesigner, PowerDimensions, PowerDynamo, PowerJ, PowerScript, PowerSite, PowerSocket, Powersoft, PowerStage, PowerStudio, PowerTips, Powersoft Portfolio, Powersoft Professional, PowerWare Desktop, PowerWare Enterprise, ProcessAnalyst, Rapport, Report Workbench, Report-Execute, Replication Agent, Replication Driver, Replication Server, Replication Server Manager, Replication Toolkit, Resource Manager, RW-DisplayLib, S-Designor, SDF, Secure SQL Server, Secure SQL Toolset, Security Guardian, SKILS, smart.partners, smart.parts, smart.script, SQL Advantage, SQL Anywhere, SQL Anywhere Studio, SQL Code Checker, SQL Debug, SQL Edit, SQL Edit/TPU, SQL Everywhere, SQL Modeler, SQL Remote, SQL Server, SQL Server Manager, SQL SMART, SQL Toolset, SQL Server/CFT, SQL Server/DBM, SQL Server SNMP SubAgent, SQL Station, SQLJ, STEP, SupportNow, S.W.I.F.T. Message Format Libraries, Sybase Central, Sybase Client/Server Interfaces, Sybase Financial Server, Sybase Gateways, Sybase MPP, Sybase SQL Desktop, Sybase SQL Lifecycle, Sybase SQL Workgroup, Sybase User Workbench, SybaseWare, Syber Financial, SyberAssist, SyBooks, System 10, System 11, System XI (logo), SystemTools, Tabular Data Stream, TradeForce, Transact-SQL, Translation Toolkit, UltraLite.NET, UNIBOM, Unilib, Uninull, Unisep, Unistring, URK Runtime Kit for UniCode, Viewer, Visual Components, VisualSpeller, VisualWriter, VQL, WarehouseArchitect, Warehouse Control Center, Warehouse Studio, Warehouse WORKS, Watcom, Watcom SQL, Watcom SQL Server, Web Deployment Kit, Web.PB, Web.SQL, WebSights, WebViewer, WorkGroup SQL Server, XA-Library, XA-Server and XP Server are trademarks of Sybase, Inc. 03/03 Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. All other company and product names used herein may be trademarks or registered trademarks of their respective companies. Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS for the DOD and as set forth in FAR (a)-(d) for civilian agencies. Sybase, Inc., One Sybase Drive, Dublin, CA

3 Contents About This Book... vii CHAPTER 1 New Features in Replication Server Version Multi-site availability (MSA)... 1 Support for symmetric multiprocessors (SMP)... 2 The embedded RSSD (ERSSD)... 4 Performance enhancements... 4 Better management of empty transactions... 4 Internal commit control for parallel processing... 4 New Replication Server configuration parameters... 5 New database configuration parameters... 5 Changed database configuration parameters... 6 date and time datatypes... 7 Support for sending encrypted passwords... 7 New bulk materialization method... 8 Chinese character set (GB18030) support... 8 CHAPTER 2 System Changes in Replication Server Configuration parameters... 9 Replication Server parameters... 9 Database connection parameters RCL commands System stored procedures Function strings System tables Keywords CHAPTER 3 Introducing Replication Manager Introducing Replication Manager Setting configuration parameters for replication objects Software requirements and compatibilities Installation Understanding the graphical user interface What s New iii

4 Contents The replication environment Database replication support Monitoring a replication environment Preparing to manage a replication environment Before you replicate data Support for multi-site availability (MSA) Mixed version support Using the database replication interface Managing database replication CHAPTER 4 New Features in Replication Server Manager Version Introducing RSM Support for embedded RSSD Backing up the ERSSD from Sybase Central Adding an Adaptive Server Anywhere server Support for date and time datatypes Support for commit control CHAPTER 5 New Features in Replication Server Version Enhanced support for the parallel Data Server Interface (DSI) Extended server limits Using extended limits Mixed-version support Unicode support Support for Secure Sockets Layer (SSL) security Lightweight Directory Access Protocol (LDAP) Direct writes to storage media CHAPTER 6 System Changes in Replication Server New and modified configuration parameters New Replication Server configuration parameters New configuration parameters for database connections New configuration parameters for routes New configuration parameters for RepAgent New configuration parameter for queues Modified configuration parameters New and modified commands Changes to system stored procedures System table changes New keywords CHAPTER 7 New Features in Replication Server Version iv Replication Server

5 Counters to monitor performance Modules and counters Viewing information provided by counters Partition affinity High availability on Sun Cluster CHAPTER 8 System Changes in Replication Server New configuration parameters New Replication Server configuration parameters New configuration parameters for database connections New configuration parameters for routes New system stored procedures New Transact-SQL commands New system tables Changes to system tables Index What s New v

6 vi Replication Server

7 About This Book Audience How to use this book Related documents This manual is intended for customers who are upgrading to Replication Server version What s New in Replication Server? is an introduction to new Sybase Replication Server version 12.6 features, the commands, system procedures, system tables, and documentation that support them. It also provides an introduction to the new Replication Manager graphics-based administration tool and changes to Replication Server Manager (RSM). This document also discusses the new features added and system changes made in version 12.5 and This information is provided for users who are upgrading to Replication Server version 12.6 from earlier versions. It includes these chapters: Chapter 1, New Features in Replication Server Version 12.6 describes the new Replication Server 12.6 features. Chapter 2, System Changes in Replication Server 12.6 describes new and changed commands, stored procedures, configuration parameters, system tables, keywords, and so on. Chapter 3, Introducing Replication Manager describes the new Replication Manager plug-in to Sybase Central, Java edition. Chapter 4, New Features in Replication Server Manager Version 12.6 describes new features in RSM. Chapter 5, New Features in Replication Server Version 12.5 describes the Replication Server 12.5 features. Chapter 6, System Changes in Replication Server 12.5 describes Replication Server 12.5 system changes. Chapter 7, New Features in Replication Server Version 12.1 describes the Replication Server 12.1 features. Chapter 8, System Changes in Replication Server 12.1 describes Replication Server 12.1 system changes. The Sybase Replication Server documentation set consists of the following: What s New vii

8 The release bulletin for your platform contains last-minute information that was too late to be included in the books. A more recent version of the release bulletin may be available on the Word Wide Web. To check for critical product or document information that was added after the release of the product CD, use the Sybase Technical Library. Installation Guide for your platform describes installation and upgrade procedures for all Replication Server and related products. What s New in Replication Server? describes the new features in Replication Server version 12.6 and the system changes added to support those features. Administration Guide contains an introduction to replication systems. This manual includes information and guidelines for creating and managing a replication system, setting up security, recovering from system failures, and improving performance. Configuration Guide for your platform describes configuration procedures for all Replication Server and related products, and explains how to use the rs_init configuration utility. Design Guide contains information about designing a replication system and integrating heterogeneous data servers into a replication system. Getting Started with Replication Server provides step-by-step instructions for installing and setting up a simple replication system. Heterogeneous Replication Guide describes how to use Replication Server to replicate data between databases supplied by different vendors. Reference Manual contains the syntax and detailed descriptions of Replication Server commands in the Replication Command Language (RCL); Replication Server system functions; Sybase Adaptive Server commands, system procedures, and stored procedures used with Replication Server; Replication Server executable programs; and Replication Server system tables. System Tables Diagram illustrates system tables and their entity relationships in a poster format. Available only in print version. Troubleshooting Guide contains information to aid in diagnosing and correcting problems in the replication system. Replication Server plug-in help, which contains information about using Sybase Central to manage Replication Server. viii Replication Server

9 About This Book Other sources of information Sybase certifications on the Web 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: The Getting Started CD contains release bulletins and installation guides in PDF format, and may also contain other documents or updated information not included on the Technical Library CD. It is included with your software. To read or print documents on the Getting Started CD you need Adobe Acrobat Reader (downloadable at no charge from the Adobe Web site, using a link provided on the CD). The Technical Library CD contains product manuals and is included with your software. The DynaText reader (included on the Technical Library CD) allows you to access technical information about your product in an easy-to-use format. Refer to the Technical Library Installation Guide in your documentation package for instructions on installing and starting the Technical Library. The Technical Library Product Manuals Web site is an HTML version of the Technical Library CD that you can access using a standard Web browser. In addition to product manuals, you will find links to EBFs/Updates, Technical Documents, Case Management, Solved Cases, newsgroups, and the Sybase Developer Network. To access the Technical Library Product Manuals Web site, go to Product Manuals at 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 at 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. What s New ix

10 Sybase EBFs and software maintenance Conventions 1 Point your Web browser to Technical Documents at 2 Click MySybase and create a MySybase profile. Finding the latest information on EBFs and software maintenance 1 Point your Web browser to the Sybase Support Page at 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. The following style conventions are used in this manual: In a sample screen display, commands you should enter exactly as shown are in: this font In a sample screen display, words that you should replace with the appropriate value for your installation are shown in: this font In the regular text of this document, the names of files and directories appear in italics: /usr/u/sybase The names of programs, utilities, procedures, and commands appear in this type: bcp The conventions for syntax statements in this manual are as follows: x Replication Server

11 About This Book Table 1: SQL syntax conventions Key Definition command Command names, command option names, utility names, utility flags, and other keywords are in Arial. variable Variables, or words that stand for values that you fill in, are in italics. { } Curly braces indicate that you choose at least one of the enclosed options. Do not include braces in your option. [ ] Brackets mean choosing one or more of the enclosed options is optional. Do not include brackets in your option. ( ) Parentheses are to be typed as part of the command. The vertical bar means you can select only one of the options shown., The comma means you can choose as many of the options shown as you like, separating your choices with commas to be typed as part of the command. If you need help 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 cannot resolve a problem using the manuals or online help, please have the designated person contact Sybase Technical Support or the Sybase subsidiary in your area. What s New xi

12 xii Replication Server

13 CHAPTER 1 New Features in Replication Server Version 12.6 This chapter describes the new features introduced with Sybase Replication Server version 12.6 and 12.5 EBF. Topic Page Multi-site availability (MSA) 1 Support for symmetric multiprocessors (SMP) 2 The embedded RSSD (ERSSD) 4 Performance enhancements 4 date and time datatypes 7 Support for sending encrypted passwords 7 New bulk materialization method 8 Chinese character set (GB18030) support 8 Multi-site availability (MSA) MSA extends Replication Server replication capabilities and can make the process of setting up a replication system both faster and easier. Some of the features that MSA provides include: A simple replication methodology that requires only one replication definition for the primary database and only one subscription for each subscribing database. A replication filtering strategy that lets you choose whether or not to replicate individual tables, transactions, functions, system stored procedures, and data definition language (DDL). Replication of DDL to any replicate database including non warm standby databases. Replication to multiple replicate sites for standby as well as nonstandby databases. What s New 1

14 Support for symmetric multiprocessors (SMP) Database replication When the replicate is a warm standby database You can overlay MSA scenarios onto your existing replication structure. The procedures for implementing MSA are similar to those you already use to replicate to warm standby or replicate databases. When you use table and function replication, you describe each piece of data that is to be replicated using individual table and function replication definitions and subscriptions. This methodology allows you to transform data and provides fine-grained control over the information being entered in the replicate database. However, you must mark each table or function to be replicated, create a replication definition for each replicated table or function, and create subscriptions for each replication definition at each replicate database. MSA lets you identify specific database objects: tables, functions, transactions, DDL, and system stored procedures in a single replication definition. You can choose to replicate the entire database; or you can choose to replicate or not replicate specific tables, functions, transactions, DDL, and system stored procedures in that database. If you do not need to replicate partial tables, MSA can provide replication while affording the advantages of simple setup and maintenance. In the non-msa warm standby scenario, changes to the primary database are copied directly to the warm standby database without alteration. This methodology allows replication of DDL. To change or qualify the data sent, you must add table and function replication definitions. Each primary database can have one, and only one, standby database. MSA provides all the features of traditional Sybase warm standby. In addition, MSA: Enables replication to multiple standby databases Provides the option to replicate or not replicate specific database objects MSA supports the use of logical connections. Support for symmetric multiprocessors (SMP) Replication Server 12.6 lets you run Replication Server on either symmetric multiprocessor (SMP) or single-processor platforms. Replication Server s multithreaded architecture supports both hardware configurations. 2 Replication Server

15 CHAPTER 1 New Features in Replication Server Version 12.6 Configuring SMP Monitoring thread status Monitoring performance On a single processor platform, Replication Server threads run serially. On a multiprocessor platform, Replication Server threads can run in parallel, thereby improving performance and efficiency. Replication Server support for multiple processors is based on Open Server support for multiple processors. Both servers use the POSIX thread library on UNIX platforms and the WIN32 thread library on Windows NT platforms. For detailed information about Open Server support for multiple processing machines, see the Open Server Server-Library/C Reference Manual. When Replication Server is in single-processor mode, a server-wide mutual exclusion lock (mutex) enforces serial thread execution. Serial thread execution safeguards global data, server code, and system routines, ensuring that they remain thread-safe. When Replication Server is in multiprocessor mode, the server-wide mutex is disengaged and individual threads use a combination of thread management techniques to ensure that global data, server code, and system routines remain secure. To enable SMP on a multiprocessor machine, use configure replication server with the smp_enable option. For example: configure replication server set smp_enable to on You can verify Replication Server thread status using these commands and procedures: admin who provides information on all Replication Server threads admin who_is_up or admin who_is_down lists Replication Server threads that are running, or not running. sp_help_rep_agent provides information on the RepAgent thread and the RepAgent User thread. This is an Adaptive Server stored procedure. Replication Server provides monitors and counters for monitoring performance. See Chapter 15, Using Counters to Monitor Performance, in the Administration Guide. See the Administration Guide for more information about increasing Replication Server performance using SMP. What s New 3

16 The embedded RSSD (ERSSD) The embedded RSSD (ERSSD) Limitations Replication Server can run either on an Adaptive Server Replication Server System Database (RSSD) or on an embedded RSSD (ERSSD). ERSSD is designed for users who do not want to manage the Replication Server RSSD in Adaptive Server. Replication Server is easier to install and manage with ERSSD. If you select embedded RSSD when you install Replication Server, ERSSD is automatically installed, configured, and started in the background. It is self-maintained. Backup procedures are automatic and pre-configured. Currently, you cannot create a route originating from Replication Server with ERSSD. Nor can you migrate between RSSD and ERSSD. To use the ERSSD, you must select it when you install Replication Server. For more details, see the Replication Server Installation Guide and the Replication Server Administration Guide. Performance enhancements Replication Server 12.6 includes new performance enhancements. See Chapter 16, Performance Tuning, in the Administration Guide for detailed information about these enhancements. Better management of empty transactions Transactions that contain only a begin and a commit statement can degrade the performance of warm standby connections. To enhancement performance, these transactions are now deleted from the inbound queue as they are read. To further enhance performance, Sybase recommends that you also tune your application to eliminate as many of these empty transactions as possible. Internal commit control for parallel processing To resolve conflicting updates when using parallel processing, Replication Server must maintain transaction commit order and resolve commit consistency deadlocks. 4 Replication Server

17 CHAPTER 1 New Features in Replication Server Version 12.6 Replication Server introduces a new method to maintain commit control using the function string rs_dsi_check_thread_lock. Replication Server uses rs_dsi_check_thread_lock to check whether the current DSI executor thread is blocking another replicate database process. This new method handles commit control within Replication Server thus requiring less network I/O than other methods, and may result in the rollback of only one transaction instead of many. New database connection parameters used with internal commit control are: dsi_commit_check_locks_intrvl dsi_commit_check_locks_max dsi_commit_control New Replication Server configuration parameters You can use new Replication Server configuration parameter to fine-tune Replication Server performance. sqt_init_read_delay the amount of time an SQT thread sleeps while waiting for an SQM read before checking for new instructions in its command queue. sqt_max_read_delay the maximum amount of time an SQT thread sleeps while waiting for an SQM read before checking for new instructions in its command queue. New database configuration parameters You can use new database connection configuration parameters to fine-tune Replication Server performance. dsi_commit_check_locks_intrvl specifies the number of milliseconds (ms) the DSI executor thread waits between executions of the rs_dsi_check_thread_lock function string. Used with parallel DSI. dsi_commit_check_locks_max specifies the maximum number of times a DSI executor thread checks whether it is blocking other transactions in the replicate database before rolling back its transaction and retrying it. Used with parallel DSI. What s New 5

18 Performance enhancements dsi_commit_control specifies whether commit control processing is handled internally by Replication Server using internal tables (on) or externally using the rs_threads system table (off). Used with parallel DSI. Changed database configuration parameters The database connection parameters dsi_serialization_method and dsi_partitioning_rule have changed. dsi_serialization_method specifies how and when parallel DSI threads can start. It includes these new or changed options: no_wait specifies that a transaction can start as soon as it is ready without regard to the state of other transactions. wait_for_start specifies that a transaction can start as soon as the transaction scheduled to commit immediately before it has started. Replaces the none option. When used with the origin partitioning parameter, this option replaces the single_transaction_per_origin serialization method. isolation_level_3 is the same as wait_for_start, except that DSIs will specify isolation level 3 when connecting to the replicate database. wait_for_commit specifies that a transaction can start only when the previous transaction is ready to commit. none maintained for backward compatibility. Replaced by wait_for_start. single_transaction_per_origin maintained for backward compatibility. Replaced by dsi_serialization_method set to wait_for_start and dsi_partitioning_rule set to origin. dsi_partitioning_rule specifies the partitioning rules the DSI uses to partition transactions among available parallel DSI threads. It includes these new options: origin specifies that transactions with the same origin must be serialized when applied to the replicate database. origin_sessid specifies that transactions with the same origin and the same process ID (SPID in Adaptive Server) must be serialized when applied to the replicate database. The LTL version must be 600 or later. Sybase recommends that you try setting dsi_partitioning_rule to origin_sessid, time as this setting may provide the most efficient partitioning. 6 Replication Server

19 CHAPTER 1 New Features in Replication Server Version 12.6 date and time datatypes There are two new datatypes, date and time, in Replication Server. These datatypes extend the existing datetime and smalldatetime datatypes, providing date and time columns to replicate and standby databases. Both are fixed-width 4-byte datatypes that support rs_subcmp, and mixed-version environments. Replication Server version 12.6 with date and time datatype support is backward-compatible with earlier versions of Adaptive Server. However, earlier versions of Adaptive Server do not recognize date and time, and thus can send only datetime and smalldatetime data. The new columns generated by date and time datatypes allow you to replicate date and time data to both standby and replicate databases. These columns can be part of the primary key in a replication definition, and are searchable columns in a replication definition. You can use date and time columns in the where clause of define subscription, create subscription, or create article. In the same way, the date and time columns are searchable parameters in a function replication definition, again used in the where clause of define subscription, create subscription, or create article. Table 1-1: Range and storage needs for date/time datatypes Datatype Range Storage needed date January 1, 0001 to 4 December 31, 9999 time 12:00:00 AM to 11:59: PM smalldatetime January 1, 1900 to June 6, 2079; 12:00:00AM to 11:59:59:999 PM datetime January 1, 1753 to December 31, 9999; 12:00:00AM to 11:59: PM Support for sending encrypted passwords Replication Server 12.6 supports the -X option in isql that sends encrypted passwords through the network when making a client connection. What s New 7

20 New bulk materialization method To ensure that all Replication Server client connections except the first connection to the RSSD send encrypted passwords, set the Replication Server configuration parameter send_enc_password to on. For example, enter: configure replication server set send_enc_password to on To ensure that all Replication Server client connections, including the first connection to the RSSD, send encrypted passwords, set the configuration parameter RS_enc_pw to on in the rs_name.cfg file using a text editor. If RS_enc_pw is on, all Replication Server connections to the RSSD send encrypted passwords, even if send_enc_password is off. New bulk materialization method Replication Server 12.6 supports a new bulk materialization method for copying or moving a database from a source Adaptive Server to a destination Adaptive Server without shutting down the source Adaptive Server. The Adaptive Server quiesce database... to manifest_file and mount commands let you quiesce the server and copy or move the database. To use this bulk materialization method, both the source and destination database servers must be Adaptive Server version or later. You can use quiesce database... to manifest_file to generate all the data storage information and then use mount to mount the data to a new database see Chapter 10, Managing Subscriptions, in the Replication Server Administration Guide. You can use quiesce database... to manifest_file and mount when you add a warm standby database see Chapter 13, Managing Warm Standby, in the Replication Server Administration Guide. For information about mount and unmount, see Chapter 22, Database Mount and Unmount, in the Adaptive Server System Administration Guide. Chinese character set (GB18030) support Replication Server supports all character sets supported by Adaptive Server Enterprise. Accordingly, Replication Server 12.6 supports the Chinese character set (GB18030). 8 Replication Server

21 CHAPTER 2 System Changes in Replication Server 12.6 This chapter describes system changes introduced with Sybase Replication Server version 12.6 and 12.5 EBF. Topic Configuration parameters RCL commands 11 System stored procedures 12 Function strings 12 System tables 13 Keywords 13 Page 9 Configuration parameters This section summarizes new and changed configuration parameters for Replication Server Replication Server parameters Table 2-1 describes new Replication Server configuration parameters stored in the rs_config system table. Table 2-1: New Replication Server parameters for rs_config table Parameter Description smp_enable Enables SMP on Replication Server on a multiprocessor machine. send_enc_password Enables encrypted password to be sent through the network for all Replication Server client connections, except the first connection to the RSSD. What s New 9

22 Configuration parameters Parameter sqt_init_read_delay sqt_max_read_delay Description The length of time an SQT thread sleeps while waiting for an SQM read before chicking to see if it has been given new instructions in its command queue. With each expiration, if the command queue is empty, SQT doubles its sleep time up to the value set for sqt_max_read_delay. Default: 2000 ms The maximum length of time an SQT thread sleeps while waiting for an SQM read before chcking to see if it has been given new instructions in its command queue. Table 2-2 describes new Replication Server configuration parameters stored in the rs_name.cfg file. Table 2-2: New Replication Server parameters for rs_name.cfg file Parameter RS_enc_pw Description Enables encrypted password to be sent through the network for all Replication Server client connections, including the first connection to the RSSD. Database connection parameters Table 2-3 describes the new database connection configuration parameters. Table 2-3: New configuration parameters Parameter Description dsi_commit_check_locks_intrv l dsi_commit_check_locks_max The number of milliseconds (ms) the DSI executor thread waits between executions of the rs_dsi_check_thread_lock function string. Default: 1000ms (1 second) Minimum: 0 Maximum: 86,400,000 ms (24 hours) The maximum number of times a DSI executor thread checks whether it is blocking other transactions in the replicate database before rolling back its transaction and retrying it. Used with parallel DSI. Default: 200 Minimum: 1 Maximum: 1,000, Replication Server

23 CHAPTER 2 System Changes in Replication Server 12.6 Parameter dsi_commit_control rep_as_standby Description Specifies whether commit control processing is handled internally by Replication Server using internal tables (on) or externally using the rs_threads system table (off). Default: off When rep_as_standby is on, table subscriptions replicate tables marked by sp_reptostandby. For rep_as_standby on to succeed, the RepAgent parameters send maint xacts to replicate must be false and send warm standby xacts must be true. Default: off Table 2-4 describes changed configuration parameters. Table 2-4: Changed database configuration parameters Parameter dsi_partitioning_rule dsi_serialization_method Description of enhancements Provides new options: origin specifies that transactions with the same origin must be serialized when applied to the replicate database. origin_sessid specifies that transactions with the same origin and the same process ID must be serialized when applied to the replicate database Provides new options: no_wait specifies that a transaction can start as soon as it is ready. Replaces the none option. wait_for_start specifies that a transaction can start as soon as the transaction sceduled to commit immediately before has started RCL commands This section summarizes new and changed RCL commands for Replication Server Table 2-5 describes new commands. Table 2-5: New Transact-SQL commands Command Description alter database replication definition Changes a database replication definition What s New 11

24 System stored procedures Command create database replication definition drop database replication definition Description Creates a replication definition that describes a database or database objects for replication Deletes a database replication definition Table 2-6 describes changed commands. Table 2-6: Changed commands Command activate subscription check subscription create subscription define subscription drop subscription validate subscription Description of enhancements Starts the distribution of updates from the primary to the replicate database and sets the database subscription status to ACTIVE Checks the materialization status of a subscription to a database replication definition Creates a subscription for a database replication definition Defines a subscription for a database replication definition Drops a subscription for a database replication definition Sets the status of a database subscription to VALID System stored procedures Table 2-7 describes new stored procedures. Table 2-7: New system stored procedures System procedure Description rs_helpdbrep Displays information about database replication definitions associated with the current Replication Server rs_helpdbsub Displays information about database subscriptions associated with the replicate Replication Server Function strings Table 2-8 describes new function strings. 12 Replication Server

25 CHAPTER 2 System Changes in Replication Server 12.6 Table 2-8: New function strings Function string Description rs_dsi_check_thread_lock Checks whether the current DSI executor thread is blocking another replicate database process. Used during parallel processing System tables Table 2-9 describes new system tables. Table 2-9: New system tables System table Description rs_dbreps Stores all information about database replication definitions except name sets. It is replicated to all sites with a version number of 12.6 or later. rs_dbsubsets Stores the name sets for database replication definitions. It is replicated to all sites with a version number of 12.6 or later. Keywords There are three new keywords in Replication Server 12.6: functions osid procedures transactions What s New 13

26 Keywords 14 Replication Server

27 CHAPTER 3 Introducing Replication Manager Replication Manager, a plug-in to Sybase Central, Java edition, is a new component in Replication Server version Replication Manager functionality is a subset of the existing Replication Server plug-in functionality, and is designed to provide complete management support for both multi-site availability (MSA) and standard warm standby environments. Name Page Introducing Replication Manager 15 Understanding the graphical user interface 17 The replication environment 19 Database replication support 19 Monitoring a replication environment 20 Preparing to manage a replication environment 21 Support for multi-site availability (MSA) 27 Introducing Replication Manager Replication Manager is separate from Replication Server Manager (RSM). RSM includes the Replication Server plug-in and Replication Server Manager Server (RSM Server). Replication Manager has a similar look-and-feel as the Replication Server plug-in, but runs within the Sybase Central, Java edition, framework. In addition, Replication Manager does not require RSM Server to manage servers in a replication environment. It communicates directly with Replication Server and Adaptive Server Enterprise servers. Feature Replication Server plug-in Replication Manager Uses a graphical user interface X X Allows you to manage, monitor, and troubleshoot all replication system X components Provides some monitoring capabilities X What s New 15

28 Introducing Replication Manager Feature Contains extensive help that provides a quick reference for Replication X Server concepts and tasks Manages a warm standby environment X X Supports Multi-Site Availability (MSA) X Supports the Embedded RSSD X Runs within the same Sybase Central framework as Adaptive Server X Enterprise plug-in to Sybase Central, Java edition Provides a two-tier solution, which does not require Replication Server X Manager (RSM) Server Runs on MicroSoft Windows platforms as well as all UNIX platforms X supported by Replication Server Provides a server-centric view of the replication environment. X X Manages a Replication Server, including all configuration parameters, and the Adaptive Server Enterprise Replication Agent thread (RepAgent) X X Enables you to create, alter, and delete: Physical and logical connections Replication Server users Replication Server plug-in Enables you to create, alter, and delete table replication definitions X Enables you to create, alter, and delete Replication Server partitions X and queues, and Routes Uses the switch active logical connection process X X Displays connection status X X Provides logging and tracing of server commands X X X Replication Manager X Setting configuration parameters for replication objects Using Replication Manager, you can set configuration parameters for the following objects: Replication Server Database connections Replication agent thread 16 Replication Server

29 CHAPTER 3 Introducing Replication Manager Software requirements and compatibilities Replication Manager requires the following software: Java JRE version Sybase Central, Java edition, version jconnect for JDBC version 5.5 Replication Manager can run in the same instance of Sybase Central as the Adaptive Server Enterprise plug-in to Sybase Central, Java edition, version Installation Replication Server 12.6 uses a new installer, called InstallShield, for the installation process. You can install Replication Manager at the same time you install Replication Server using InstallShield. If you choose Typical or Full installation when you install Replication Server 12.6, InstallShield automatically installs Sybase Central and Replication Manager, registers Replication Manager in Sybase Central, then, if you choose, starts Sybase Central when installation is complete. Understanding the graphical user interface Sybase Central, Java edition, provides the same basic framework to display and manage items in a hierarchy as Sybase Central on Windows platforms, as shown in Figure 3-1. What s New 17

30 Understanding the graphical user interface Figure 3-1: The Replication Manager main window Main window The Sybase Central main window is split into two panes: The left pane shows the object tree, a hierarchical view of objects, such as Replication Servers and data servers. These objects are containers of other objects. The right pane shows the contents of the currently selected container in the object tree on the left. For example, the left pane may show a Database Replication Definition folder, but the database replication definitions themselves are shown in the right pane. The object tree is also illustrated in Figure 3-1. The root object in the hierarchy represents Replication Manager. The object below that represents a replication environment called Tokyo. An environment consists of all the Adaptive Server Enterprise servers and Replication Servers that participate in replication, along with the databases and the data contained within the databases. For more information about the replication environment, see The replication environment on page Replication Server

31 CHAPTER 3 Introducing Replication Manager Logical and physical views Wizards and dialog boxes The data servers contain databases, which, in turn, contain tables, definitions, and subscriptions. Replication Servers contain all the objects required for their use, such as connections. In addition, the Replication Manager main window lets you select multiple objects before executing commands. Replication Manager displays both a logical view and a physical view of the replication environment. The logical view, which you display by selecting database objects in the left pane, manages databases and all data-specific information. For example, the logical view displays connections, tables, replication definitions, and subscriptions. The physical view displays servers and manages information specific to Replication Server, such as users and connections. You display this view by double-clicking a Replication Server object. Replication Manager provides wizards and dialog boxes to aid you in replication environment management tasks. The replication environment The replication environment represents the set of data servers and databases, and one or more Replication Servers, that you are managing through Replication Manager. The environment also contains these servers and gives you access to the database replication definitions and subscriptions for each database in that environment. You can view and, in some cases, change replication objects within that environment. To view and edit the properties of an existing replication environment, right-click the environment object, and select Properties. The Environment Properties dialog box opens. Database replication support The purpose of the Replication Manager is to support the replication of entire databases; therefore, it does not support replicating individual table or stored procedure objects. What s New 19

32 Monitoring a replication environment Warm standby replication MSA replication There are two different ways to replicate entire databases: Standard warm standby replication MSA replication In the standard warm standby solution, you can use Replication Manager to identify the two Adaptive Server Enterprise databases that will be the active and standby databases, and to create both physical connections and logical connections. All warm standby features in the current Replication Server plugin are provided in Replication Manager. In the new MSA solution, you can use Replication Manager to create database connections, database replication definitions, and database subscriptions. The Replication Manager supports the capabilities of new features such as filtering replication definitions by excluding individual tables, functions, and transactions. See Support for multi-site availability (MSA) on page 27 for more information. Monitoring a replication environment Replication Manager monitors the state of a replication environment and lets you troubleshoot problems in that environment. This capability is a subset of the monitoring capability that exists in the Replication Server plug-in. To help you monitor the environment, Replication Manager: Controls data flow you can suspend and resume RepAgent and DSI threads. Switches a logical connection and monitors the warm standby environment you can issue the switch active command in a warm standby environment, monitor the switching process, and report any errors. 20 Replication Server

33 CHAPTER 3 Introducing Replication Manager Manages connections you can configure the Replication Server and database connections. Note Replication Manager does not provide the ability to read the Replication Server error log file because it does not access the RSM Server. Instead, consider using the Replication Server plug-in, which does access the RSM Server if you want to troubleshoot Replication Server. Tune replication performance Replication Manager lets you fine-tune server performance by changing configuration parameters affecting servers and database connections. Preparing to manage a replication environment InstallShield automatically registers Replication Manager after installation, so the first step in configuring and setting up Replication Manager is to create a replication environment. Note If, after installation, Replication Manager is not registered, you need to manually register it. For instructions, see the Replication Server Installation Guide for your platform. Before you can use Replication Manager to manage a replication environment, you must: Create an object within Replication Manager to represent that environment Configure replication for the environment Creating a replication environment object To create an environment that reflects the replication environment you plan to manage: 1 Start Sybase Central. 2 Click the Replication Manager icon in the left pane of the Replication Manager window. 3 Double-click the Add Replication Environment icon in the right pane. What s New 21

34 Preparing to manage a replication environment The Add Replication Environment wizard starts, as shown: 4 Enter the name of your environment and click Next. 5 Enter a user name and password that will let you access the environment in a secure manner. Click Next. 6 Click the servers that you want to add to your environment from the list, then add a user name and password for each. If you are adding a Replication Server, enter a user name and password for the RSSD. When adding servers, you must provide a user name and password that have been granted certain permissions: Replication Server sa permissions Adaptive Server Enterprise the sa_role and the sso_role See the Replication Server Administration Guide for more information about granting user permissions. 7 Click Next. 8 Check the summary page to make sure you have added all the servers you need, then click Finish. The new environment object displays in the left pane under the Replication Manager object with the name you gave it in the wizard. 22 Replication Server

35 CHAPTER 3 Introducing Replication Manager Configuring replication After you have created the replication environment, you must use the Configure Replication wizard to create the necessary connections, database replication definitions, and subscriptions. To configure replication: 1 Select the environment object you created in the previous procedure. 2 In the right pane, double-click Configure Replication. 3 On the Configure Replication wizard page that opens, click the button next to the type of environment you want to create: If you choose Create a Standard Replication Server Warm Standby Environment, go to Configuring a standard warm standby environment on page 23. If you choose Create an Environment Where the Primary Database is Replicated to Several Replicate Sites, go to Configuring an environment with one primary and multiple replicates on page 24. If you choose Create a Bidirectional Replication Environment, go to Creating a bidirectional replication environment on page 26. Configuring a standard warm standby environment Note When selecting a server, if the server does not appear in the list, click Add Server to open the Add Server wizard. Follow the procedure to add servers in Creating a replication environment object on page Select the active server and active database. 2 Select the Replication Server that will manage the database connections. 3 Select the standby server and standby database. 4 Enter the name of the logical connection. When using an existing connection to create a warm standby logical connection, you must use the existing data_server and database names of the active database for the logical connection name. See the Replication Server Administration Guide, Volume 2 for more information. 5 Enter the user name and password of the maintenance user. If the maintenance user does not exist, the wizard creates one for you, and gives it a default name and password. Accept the defaults, or enter your own values. What s New 23

36 Preparing to manage a replication environment 6 Select the user name and password that the RepAgent will use to connect to Replication Server. If the RepAgent user does not exist, the wizard creates one for you, and gives it a default name and password. Accept the defaults, or enter your own values. 7 Select the materialization method. 8 Review the summary information about the replication environment. 9 Click Finish. 10 If everything looks correct, click Finish. Otherwise, click Back to return to an earlier page in the wizard and change the replication environment information. Then, return to the final wizard page and click Finish. Replication Manager creates the following replication objects: Logical connections Physical connections Maintenance user in both Adaptive Server Enterprise servers. Configuring an environment with one primary and multiple replicates This procedure can be used for setting up warm standby environment where data is replicated from one site to many replicate sites using MSA. Note When selecting a server, if the server does not appear in the list, click Add Server to open the Add Server wizard. Follow the procedure to add servers in Creating a replication environment object on page Select the primary server and the primary database. 2 Click Next. 3 Select the Replication Server that will manage the database connections. 4 Click Next. 5 Select a replicate server, then a corresponding database, and click Add. The corresponding server.database connection displays in the Connections list. Repeat this step for each replicate server and replicate database pair you need in your environment. 6 Click Next. 24 Replication Server

37 CHAPTER 3 Introducing Replication Manager 7 Enter the user name and password of the maintenance user. If the maintenance user does not exist, the wizard creates one for you, and gives it a default name and password. Accept the defaults, or enter your own values. All selected connections will use this maintenance user login. 8 Click Next. 9 Select the user name and password that the RepAgent will use to connect to Replication Server. If the RepAgent user does not exist, the wizard creates one for you, and gives it a default name and password. Accept the defaults, or enter your own values. All connections will use this RepAgent login. 10 Click Next. 11 Specify how replicated tables will be materialized. Choose one of the following options: Create Subscription Without Materialization Define Subscription for Bulk Materialization 12 If you chose Define Subscription for Bulk Materialization in the previous step, click Use Dump Marker in Transaction Log if you want to use dump and load coordination. For more information about materialization, see Subscription materialization methods in the Replication Server Administration Guide, Volume Click Next. 14 Review the summary of the replication environment. 15 If everything looks correct, click Finish. Otherwise, click Back to return to an earlier page in the wizard and change the replication environment information. Then, return to the final wizard page and click Finish. Replication Manager creates the following replication objects: Physical connections A database replication definition for the primary database One or more database subscriptions for each of the replicate databases Maintenance user in both Adaptive Server Enterprise servers What s New 25

38 Preparing to manage a replication environment Creating a bidirectional replication environment Using this procedure, you can define an environment where data is updated at multiple locations and replicated to each site. Note Conflict resolution is the responsibility of the site. Sybase does not provide automatic conflict resolution. 1 Identify the servers and databases that will be part of the bidirectional replication environment. 2 Follow steps 5 through 15 in the previous procedure. Adding connections and users After you have configured your replication environment, you can add additional database and logical connections, as well as users, using the wizards available within the folders in the right pane. The following procedure describes the process for adding these objects: 1 In the left pane, open the replication server object to which you want to add database or logical connections or users. 2 Open the folder for the object you want to add. For example, open the Connections folder to add a database connection. In the right pane, a shortcut icon for the appropriate wizard displays. 3 Double-click the shortcut. For example, double-click Add Connection to add a database connection. 4 Follow the wizard steps to add the object to your environment. For example, if you are adding a database connection, you must enter user names and passwords for the maintenance user and for RepAgent, if the database is both a primary and replicate. 5 Click Finish to complete the wizard and return to the Replication Manager object tree. For more information about adding connections and users, see the Replication Server plug-in help, which describes similar procedures using the existing Replication Server plug-in to Sybase Central. 26 Replication Server

39 CHAPTER 3 Introducing Replication Manager Before you replicate data Before you can replicate data, you must create replication definitions and subscriptions. See Managing database replication on page 35 for more information. Support for multi-site availability (MSA) Replication Manager supports the MSA feature of Replication Server Using Replication Manager, you can set up database replication definitions for the primary database and database subscriptions for each subscribing database. You can also use Replication Manager to filter out or specifically include individual tables, transactions, functions, system stored procedures, and data definition language (DDL). Using Replication Manager and MSA, you can set up a simple system with multiple targets. MSA provides all the features of the warm standby application described, such as DDL replication, but supports logical connections as only targets of replication. For more information, see: Multi-site availability (MSA) on page 1 for more information about MSA. See Chapter 13, Managing Warm Standby Applications, in the Replication Server Administration Guide, Volume 1 for more information about warm standby environments. The Replication Manager includes the following features to support MSA: Ability to define and alter database replication definitions through the Add Database Replication Definition dialog box and the Database Replication Definition Properties dialog box, respectively Database Replication Definition filters for data exclusion or inclusion, which you control from the Add Database Replication Definition dialog box or the Database Replication Definition Properties dialog box Ability to define and view database subscriptions through the Add Database Subscription dialog box and the Database Subscription Properties dialog box, respectively See Multi-site availability (MSA) on page 1 for more information about MSA. What s New 27

40 Support for multi-site availability (MSA) Mixed version support In versions 12.6 and later, Replication Server and Replication Manager support MSA. If you use an earlier version of Replication Server, database-level replication is not supported. If the replication environment contains more than one Replication Server, all Replication Servers must have site versions of 12.6 or later if you plan to use database replication. Also, route versions must be upgraded to 12.6 or later in the controlling Replication Server. Replication Servers between the controlling Replication Servers can be versions earlier than Note To upgrade routes, you must use the existing Replication Manager plugin to Sybase Central, or the Replication Server command line. For more information, see Concepts for upgrading routes in the Replication Server plug-in help, or see admin show_route_versions in Chapter 3, Replication Server Commands, in the Replication Server Reference Manual. Using the database replication interface Database replication definitions Database subscriptions Replication Manager lets you manage database replication. To access existing or create new database replication definitions, select the Database Replication Definition folder in the left pane of the tree view, under the Definitions folder. The right pane displays existing database replication definition objects and the Add Database Replication Definition shortcut icon. To access existing or create new database subscriptions, select the Database Subscriptions folder in the left pane of the tree view. The right pane displays existing database subscriptions and the Add Database Subscriptions shortcut icon. See Figure 3-1 on page 18 for an illustration of the object tree. See Managing database replication on page 35 for information about how to access existing or create new database replication definitions and subscriptions. 28 Replication Server

41 CHAPTER 3 Introducing Replication Manager Database replication definition filters Replication Server lets you apply filters when you create or alter a database replication definition to remove or specifically include data from the replication definition. You can manipulate filters through a combination of check boxes and selection lists in the Add Database Replication Definition dialog box and the Database Replication Definition Properties dialog box. See Database Replication Definition dialog box on page 29 for more information. Database replication definition context menu When you right-click a database replication object, the Database Replication Definition context menu displays, showing the following selections: Delete removes the database replication definition from the environment. Properties opens the Database Replication Definition Properties dialog box. See Figure 3-2 on page 30 for an illustration. Database Replication Definition dialog box When you select Properties from the Database Replication Definition Context menu, the Database Replication Definition Properties dialog box opens, displaying the several tabs. What s New 29

42 Support for multi-site availability (MSA) Figure 3-2: Database Replication Definition Properties dialog box The General tab The General tab displays information about the database replication definition and the database itself, some of which you can edit. The name of the database replication definition displays at the top of the tab. You can select the following check boxes: Replicate All DDL lets you set the replication definition to replicate all data definition language (DDL). If you leave the box unchecked, you replicate no DDL. Suspend DSI When Altering Database Replication Definition lets you automatically suspend the Data Server Interface (DSI) thread when you alter this specific replication definition. You cannot edit this name or the following information: Server the server name for the selected database. Database the database name for the selected database. Replication Server the name of the governing Replication Server. 30 Replication Server

43 CHAPTER 3 Introducing Replication Manager Filter tabs Minimum Version the minimal version of the table replication definition. See the Replication Server Administration Guide, Volume 1, for more information. Each Filter tab lets you either replicate all, replicate none, or filter replication for tables, functions, transactions, and system procedures. For example, selecting Replicate All Tables on the Table Filters tab replicates all tables in the database; selecting No Tables Replicated replicates no tables. The following list describes each Filter tab: Table Filters lists all tables in the database. You can select tables to exclude from replication or to specifically include in replication. An edit box lets you enter the names of tables manually. For example, you can use the owner.tablename form, or use the asterisk (*) wildcard character to designate all tables that belong to a certain owner (owner.*), or all tables of a given name belonging to any owner (*.tablename). You can also use a space( ) to designate null or no owner (.name), or to designate null or no name (owner. ). If you want to designate all the tables that have a name publisher, regardless of who owns them, designate *.publisher. Function Filters lists all stored procedures in the database. You can select the procedures you want to exclude from replication, or those you want to specifically include in replication. Transaction Filters lets you enter the exact SQL transaction names that you want to exclude from replication or those you want to specifically include in replication. For example, if you want to designate all the transactions that have no or a null name and were executed by maintuser, designate maintuser.. If you want to designate a transaction named my_tran from any user, designate my_tran or *.my_tran. To designate a transaction named my_tran from a user named usera, designate usera.my_tran To designate any transaction from a user named usera, designate usera.*. System Procedure Filters lists all Adaptive Server Enterprise system procedures that are supported by Replication Server. You can select the procedures you want to exclude from replication or those you want to specifically include in replication. What s New 31

44 Support for multi-site availability (MSA) Add Database Replication Definition dialog box The General tab Filter tabs When you double-click Add Database Replication Definition from the right pane of the object tree, the Add Database Replication Definition dialog box opens displaying the following tabs: The General tab on the Add Database Replication Definition dialog box is almost the same as the General tab on the Database Replication Definition Properties dialog box. The name of the server, database, and Replication Server are displayed; however, there is no Suspend DSI When Altering Database Replication Definition field, and you must enter the name of the database replication in the text box at the top of the dialog box. The filter tabs on the Add Database Replication Definition dialog box are the same as those on the Database Replication Definition Properties dialog box. See Database Replication Definition dialog box on page 29 for more information. Database Subscriptions Properties dialog box When you select Properties from the Database Subscription context menu, the Database Subscription Properties dialog box opens, as shown in Figure 3-3. Note You cannot edit the information on the Database Subscription Properties dialog box. Database Subscription context menu When you right-click a database subscription in the right pane, the Database Subscriptions context menu displays showing the following selections: Activate activates a subscription. This menu item is active only when you have indicated you are using bulk materialization to materialize the database. Validate validates a subscription.this menu item is active only when you have indicated you are using bulk materialization to materialize the database. Delete removes the database subscription from the environment. Properties opens the Database Subscription Properties dialog box, which is similar to the properties dialog box for database replication definitions, as shown in Figure Replication Server

45 CHAPTER 3 Introducing Replication Manager See the Replication Administration Guide, Volume 1, for more information about materialization methods. Figure 3-3: Database Subscription Properties dialog box The General tab The Database Subscription Properties dialog box displays the following two tabs: The General tab displays information about the database subscription, including the database subscription name at the top, and the following fields and buttons: Database displays the database name for the replicate (subscribing) database. Subscription Method displays the subscription method the subscription uses: Bulk bulk materialization method Bulk Create no materialization method Use Dump Marker bulk materialization with dump and load coordination methods See Add Database Subscription dialog box on page 34 for more information. What s New 33

46 Support for multi-site availability (MSA) Status Subscribe to Truncate Table displays Yes if this subscription subscribes to the truncate table command and No if it does not. Primary Database displays the primary database whose data the subscription subscribes to. Database Replication Definition displays the database replication definition name. The Status tab displays the status of the primary and the replicate databases. Add Database Subscription dialog box The Add Database Subscription dialog box is similar to the Database Subscription Properties dialog box, except that you add information about a new subscription to create it. When you double-click Add Database Subscription from the right pane of the object tree, the Add Database Subscription dialog box opens displaying the following fields: Subscription Name text box enter the name you want to give the subscription. Primary Server choose the name of primary server from the drop-down list. Primary Database choose the name of the primary database from the drop-down list. Database Replication Definition choose the name of the database replication definition you want to subscribe to. Replicate Database displays the name of the replicate database. This field is filled in when you choose the primary server. Subscribe to Truncate Table selected by default. If you want to subscribe to the truncate table command, leave the check box selected; otherwise, clear the check box. Subscription Method choose the subscription method you want to use from the drop-down list: Bulk sets the subscription method to bulk materialization. Use this method if you need to initialize the replicate database outside the replication system. 34 Replication Server

47 CHAPTER 3 Introducing Replication Manager Bulk Create sets the subscription method to no materialization method (which means you use create subscription with the without materialization clause). Use this method if you want to create a database subscription when the primary and replicate databases have been synchronized prior to subscription, or if activities at the primary database can be suspended. Use Dump Marker sets the subscription method to bulk materialization with dump and load coordination. Use this method if the primary will be in use before bulk materialization is complete. See Multi-site availability (MSA) on page 1 for more information. Managing database replication Creating database replication definitions To create a database replication definition: 1 In the left pane of the object tree, select the server, then the database to which you want to add a replication definition. 2 In the right pane, double-click the Add Database Replication Definition icon to open the Database Replication Definition dialog box. 3 On the Database tab, enter the server name and database name. 4 Select the DDL check box to replicate all DDL. Clear it to not replicate any DDL. 5 Go to the filter tab for the object you want to filter. 6 Select Replicate All to replicate all of those objects, or Replicate None to replicate none of those objects. 7 For tables, functions, and system procedures only, select Exclude Selected Tables (Functions, System Procedures) from Replication if you want to individually select objects to exclude in replication; or, select Replicate Only Those Tables (Functions, System Procedures) Selected if you want to individually select objects to include in replication. 8 If you selected to exclude the selected objects from replication, click the specific objects you want to exclude from replication. If you selected to replicate only the selected objects, click the specific objects you want to replicate. What s New 35

48 Support for multi-site availability (MSA) 9 If you are filtering tables and want to add filtering criteria by hand, enter that information in the text box at the bottom of the filter tab. If you are filtering transactions, you must enter the filtering criteria by hand. 10 Choose OK. See Preparing to manage a replication environment on page 21 for more information about using Replication Manager wizards. Altering database replication definitions To alter or review an existing database replication definition: 1 In the left pane of the object tree, select the server, then the database whose replication definition you want to alter. 2 Select the Replication Definitions folder. 3 In the right pane, right-click the database replication definition. 4 Select Properties. The Database Replication Definition Properties dialog box opens, displaying the current settings for that database replication definition, as shown in Figure 3-2 on page Edit the information on the dialog box, following the same steps as for creating a replication definition in the previous procedure. 6 Choose OK. Creating database subscriptions To create database subscriptions: 1 In the left pane of the object tree, select the server, then the database to which you want to add a database subscription. 2 Select the Subscriptions folder. 3 In the right pane, double-click the Add Database Subscriptions icon to open the Add Database Subscription dialog box. The Add Database Subscription dialog box opens, as shown in Figure 3-3 on page 33, displaying by default the name of the primary server and primary database, as well as the name of the replicate database. See Add Database Replication Definition dialog box on page 32 for more information. 36 Replication Server

49 CHAPTER 3 Introducing Replication Manager 4 At the top of the dialog box, enter a name for the database subscription. 5 In the Primary Server drop-down list, accept the default primary server, or choose another server, if appropriate. If you choose a new primary database name, the database replication definitions defined for that database are displayed in the Database Replication Definition drop-down list. 6 In the Primary Database drop-down list, accept the default primary database, or choose another database, if appropriate. If you choose a new primary server name, the databases on that server display in the Primary Database drop-down list. 7 In the Database Replication Definition drop-down list, accept the default replication definition, or choose another database replication definition, if appropriate. 8 Select Subscribe to Truncate Table if you want to subscribe to the truncate table command. 9 From the Subscription Method drop-down list, choose a subscription method. Your choices are Bulk, Bulk Create, or Use Dump Marker. See Add Database Subscription dialog box on page 34 for more information. 10 Choose OK. What s New 37

50 Support for multi-site availability (MSA) 38 Replication Server

51 CHAPTER 4 New Features in Replication Server Manager Version 12.6 Replication Server Manager (RSM) includes: The Replication Server plug-in: a Sybase Central plug-in that lets you monitor, diagnose, and manage your replication system. An RSM Server: an Open Server application that translates and communicates requests from the Replication Server plug-in. The RSM Server also monitors and responds to replication system events. Name Page Introducing RSM Support for embedded RSSD 40 Support for date and time datatypes 42 Support for commit control 46 Introducing RSM 12.6 RSM 12.6 supports the following new features of Sybase Replication Server 12.6: Embedded RSSD (Replication Server System Database) date and time datatype Commit control What s New 39

52 Support for embedded RSSD Support for embedded RSSD In both RSM (the Replication Server plug-in and RSM Server) and Replication Manager, you can retrieve, display, and analyze data from either the traditional RSSD (based on Adaptive Server) or the new embedded RSSD (ERSSD) to manage the replication environment. For more information about the ERSSD, see Chapter 1, New Features in Replication Server Version Note The Replication Manager, a plug-in to Sybase Central, Java edition, is a new component in Replication Manager See Introducing Replication Manager on page 15 for more information. The ERSSD is maintenance-free. Backups are done automatically. Note A Replication Server with an ERSSD does not support routes in version You can have a route going into a Replication Server with an ERSSD, but it must originate at a Replication Server with an RSSD. To see whether Replication Server is using an RSSD or ERSSD, using the existing Replication Server plug-in, go to the Replication Server Properties dialog box, as illustrated in Figure Replication Server

53 CHAPTER 4 New Features in Replication Server Manager Version 12.6 Figure 4-1: ERSSD information on Replication Server Properties dialog box Backing up the ERSSD from Sybase Central Using the Backup ERSSD option, you can back up the ERSSD from the Replication Server plug-in. To access this option, right-click the Replication Server icon and select Backup ERSSD. (This option is active only if the Replication Server is using an ERSSD.) You can select multiple Replication Server icons if you want to back up several ERSSD databases. A confirmation message displays: Backup the Embedded RSSD for the selected Replication Server(s)? Select Yes or No. If you select Yes, the ERSSD for each Replication Server you selected is backed up. What s New 41

54 Support for date and time datatypes Adding an Adaptive Server Anywhere server When you install Replication Server 12.6, you can choose the ERSSD or the RSSD option. If you choose to install the ERSSD, you must add the Adaptive Server Anywhere server that manages the ERSSD before you add the Replication Server to your replication environment in Sybase Central. To add an Adaptive Server Anywhere server, you must use the Add Server wizard. To access the Add Server wizard in Sybase Central, double-click the Add Server icon in the right pane. Follow the wizard steps. Support for date and time datatypes Changes to dialog boxes RSM 12.6 supports the two new datatypes being introduced with Replication Server 12.6, date and time. These fixed-width, 4-byte datatypes extend the existing datetime and smalldatetime datatypes, providing date and time columns to replicate and standby databases. For more information about date and time datatypes, see Chapter 1, New Features in Replication Server Version All dialog boxes that present datatypes now support date and time in the Replication Server plug-in. For example, Figure 4-2 shows changes to the Data tab on the Datatype Class Properties dialog box. The following dialog boxes are updated to support these new datatypes: Table Properties The Columns tab displays the new datatypes in the Type column. To access the Table Properties dialog box: a Select the Adaptive Server Enterprise. b Select the database. c Open the Tables folder. d Right-click a table icon. e Select Properties. Datatype Class Properties The Data tab includes a new datatype mask and default size for date and time. The General Boundaries and Delimiter tabs display the correct minimum/maximum values, delimiters, and delimiter length associated with date and time. 42 Replication Server

55 CHAPTER 4 New Features in Replication Server Manager Version 12.6 See Figure 4-2 for an illustration of the Data tab. Figure 4-2: The Data tab on the Datatype Class Properties dialog box To access the Datatype Class Properties dialog box: a Select the Replication Server. b Open the Datatype Classes folder. c Open a class folder. d Right-click a class icon. e Select Properties. Stored Procedure Properties The Parameters tab displays the new datatypes in the Type column. To access the Stored Procedure Properties dialog box: a Select the Adaptive Server Enterprise. b Select the database. c Open the Stored Procedures folder. What s New 43