Sybase数据库技术,数据库恢复

• 首页
• 关于
• 订阅
• 归档
• 留言
• 标签
• 免费ASE测试环境
• 镜像站
• 恢复工具

CR:564293

CR Number:   564293 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.7.12 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.7.12 07 Apr 2009 Fixed 5.8.01 15 Jul 2009 Fixed Description ORACLE ONLY: After resuming replication, an EndOfLogException during RBA search positioning sends the Replication Agent back to ADMIN state.

CR:564308

CR Number:   564308 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.7.12 01 Apr 2009 Fixed 16 Mar 2009 Fixed 09 May 2010 Fixed Description ORACLE ONLY: The error "OracleRuntimeException: Off-row LOB leaf update contains unexpected values" causes the Replication Agent to suspend replication.

CR:564317

CR Number:   564317 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Linux Original Version:   15.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Oct 2009 Duplicate Description hds_oracle_setup_for_replicate.sql rs_lastcommit needs char(72 byte) for _qid's select origin, origin_qid, secondary_qid from rs_lastcommit E. ... ERROR #5094 DSI(104 oracle_dco.oracle_dco) - /dsioqid.c(1781) The second and third columns returned by the rs_get_lastcommit function should have type 'binary' or 'char'. The one returned from database 'oracle_dco. oracle_dco' for column 2 is not 'binary' or 'char'. It is '2' as defined by CS_LIB. I. ... The DSI thread for database 'oracle_dco.oracle_dco' is shutdown. REHL5.2 (2.6.18-92.el5) x86_64 we need to change the syntax for creating the rs_lastcommit table in hds_oracle_setup_for_replicate.sql should be... create table rs_lastcommit ( origin number(8), origin_qid char(72 byte), secondary_qid char(72 byte), origin_time date, dest_commit_time date ) go Workaround Description  To fix the problem regardless what value NLS_LENGTH_SEMANTICS in oracle has set. we change the rs_lastcommit table to be created in hds_oracle_setup_for_replicate.sql: create table rs_lastcommit ( origin number(8), origin_qid char(72 byte), secondary_qid char(72 byte), origin_time date, dest_commit_time date ) go The table column datatype description of ... char(72 byte) ... semantic will override the server setting.

CR:564438

CR Number:   564438 Product Name:   Common Metadata Repository Product Component:   Web UI Status:   Closed OS:   Windows Original Version:   Jove Fixed Version Build Resolution Date Closure Code (If Appropriate) Jove 21 Jun 2010 Fixed Description Tested and reproduced with PD 15.0 EBF#3 and Repository Web Browser 15.0 and 15.0 EBF#3 When accessing a repository created in SQL Server 2005 via CMR, the following error appear in CMR logs right after starting up CMR service: ERROR Thread-1 2009/03/12 10:29:34 BRT com.sybase.cmr.infra.server.persistence.db.metacommands.LoadMetaModelCmd.execute(LoadMetaModelCmd.java:144) Unrecoverable exception occurred during loading of metamodels from repository java.lang.NullPointerException at java.util.Hashtable.get(Hashtable.java:336) at com.sybase.cmr.infra.server.persistence.db.ExtendedMetaData.getMetaPackageExtendedMetaData(ExtendedMetaData.java:129) at com.sybase.cmr.infra.server.persistence.db.DbMetaPersistenceManagerImpl.createMetaPackages(DbMetaPersistenceManagerImpl.java:589) at com.sybase.cmr.infra.server.persistence.db.metacommands.LoadMetaModelCmd.execute(LoadMetaModelCmd.java:106) at com.sybase.cmr.infra.server.persistence.db.command.CommandWrapper.execute(CommandWrapper.java:107) at com.sybase.cmr.infra.server.persistence.db.command.TxCommand.execute(TxCommand.java:83) at com.sybase.cmr.infra.server.persistence.db.command.CommandStackImpl.execute(CommandStackImpl.java:58) at com.sybase.cmr.infra.server.persistence.db.DbMetaPersistenceManagerImpl.loadAllMetaModels(DbMetaPersistenceManagerImpl.java:342) at com.sybase.cmr.infra.server.persistence.db.DbMetaPersistenceManagerImpl.loadAllMetaModels(DbMetaPersistenceManagerImpl.java:112) at com.sybase.cmr.infra.server.meta.management.MetaModelManagerImpl.loadMetaModels(MetaModelManagerImpl.java:227) at com.sybase.cmr.infra.server.impl.RepositoryImpl.init(RepositoryImpl.java:753) at com.sybase.cmr.infra.server.impl.RepositoryImpl.<init>(RepositoryImpl.java:203) at com.sybase.cmr.infra.server.impl.RepositoryImpl.<clinit>(RepositoryImpl.java:112) at com.sybase.cmr.infra.server.RepositoryFactory.createRepository(RepositoryFactory.java:27) at com.sybase.cmr.webrepository.webapp.servlet.CMRHttpServlet.init(CMRHttpServlet.java:62) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1139) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3956) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4230) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) If the repository is not empty, the following error also occurs when trying to expand Default Treeview within Repository Explorer Tab: ERROR http-3030-Processor25 2009/03/12 10:30:29 BRT org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260) Servlet.service() for servlet Blocking Servlet threw exception java.lang.RuntimeException: Could not find metaclass with the specified id 1106. at com.sybase.cmr.webrepository.webapp.filter.LocaleFilter.doFilterInternal(LocaleFilter.java:112) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:77) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:595)

CR:564563

CR Number:   564563 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Oct 2009 Fixed 5.8.02 19 Oct 2009 Fixed 5.9.00 19 Oct 2009 Fixed Description Replication Agent backup log file names are not generated in sequential order if the log file to be backed up is exclusively locked by other application.

CR:564650

CR Number:   564650 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.1 ESD #1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0.1 07 Apr 2009 Fixed 15.2 28 Apr 2009 Fixed 15.5 17 Jun 2009 Fixed 15.0.1 17 Jun 2009 Fixed 12.6 ESD#10 06 May 2009 Presently Not Targeted For Any Future Release Of This Product Description 'Internal error #23 RSI' will be generated by Replication Server for a route because of a synchronization issue between SQM writer and SQM reader. The RSI thread will report a stack trace in the RS log file when waking up in some circumstances.

CR:564756

CR Number:   564756 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Admin Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 03 Jun 2009 Fixed 5.8.01 26 Jun 2009 Fixed Description The schedule option for 'rasd_trunc_schedule' command has been enhanced to accept two kinds of schedule string. The current support restricted UNIX cron style format and now a full UNIX cron style format to support range and step schedule. The following is a valid schedule string in the full UNIX cron style format: [mm] [HH] [DOM] [MON] [DOW] Note: - Similar to the restricted UNIX cron style schedule, a full UNIX cron style have 5 fields: mm, HH, DOM, MON and DOW, The schedule format consists of 5 fields: - minutes - hours - day of month - month - day of week. - Each of the fields must be separated by a whitespace. The schedule string must be enclosed in double quotation marks. - A list of values, a range of values or a range of stepped values can be specified in each fields so that a series schedule can be specified in one command. - List values in form i,j,k, which means integer values applying to a field are i,j and k. For example, schedule "1,2,8,10 20 * * *" represents 8:01 pm, 8:02 pm, 8:08 pm, 8:10 pm every days. - Range values in form of i-j, which means any integer value from i to j. For example, 0-59 represents values 0,1,2,3,4,5,...58,59; schedule "0-59 20 * * * " represents every minutes in 8 pm. - Step values in form of i-j/n, which means any value from i to j stepped by n. For example, 1-10/4 represents values 1,5,9.; schedule "1-10/4 20 * * *" represents 8:01pm, 8:05 pm and 8:09 pm.

CR:564900

CR Number:   564900 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   MRAgent/ASE Status:   Closed OS:   AIX Original Version:   15.0.0.5522P8 Fixed Version Build Resolution Date Closure Code (If Appropriate) 01 Jul 2009 Fixed 30 Jun 2009 Fixed 01 Jul 2009 Fixed Description ASE ONLY: Issuing 'resume' command prior to performing migration causes Mirror Replication Agent to fail with NullPointerException.

CR:564908

CR Number:   564908 Product Name:   Rep Serv Commands Ref Product Component:   Rep Serv Commands Ref Status:   Closed OS:   all Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.5 21 Mar 2010 Fixed Description dsi_quoted_identifier is written up as dsi_quoted_identifiers in the manuals. Workaround Description  remove the 's' in the parameter. It is dsi_quoted_identifier

CR:564947

CR Number:   564947 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   MRAgent/ASE Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Jun 2009 Fixed 22 Jun 2009 Fixed Description ASE ONLY: Marked stored procedure is still marked after Mirror Replication Agent is re-initialized.

CR:564954

CR Number:   564954 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Utilities Status:   Closed OS:   Microsoft Windows NT Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.7.15 19 May 2009 Fixed 16 Jun 2009 Fixed 5.8.00 23 Mar 2009 Fixed Description Replication Agent ADMIN utility (ra_admin or ma_admin) with the " -u <instance_dir>" option is unable to upgrade the instance if the specified source instance directory is a relative path with no file separator. Workaround Description  use ra_admin -u all C:\sybase\RAX-15_1>bin\ra_admin -u all Upgrading instances from <C:\sybase\RAX-15_1> directory. Upgrading instance <rao1> in directory <C:\sybase\RAX-15_1>. Successfully upgraded instances: [rao1]. The log file for this session is: C:\sybase\RAX-15_1\admin_logs\admin3182009_133 34.log

CR:565081

CR Number:   565081 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   15.0 ESD#3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 ESD#3 22 05 Aug 2009 Fixed Description The apostrophe in this char string must be sent as two apostrophes '' so that the Rep server does not get an error. @"DS_DOMICILIO"='Calle Baltasar D'Espanya 00002 Bajo',

CR:565127

CR Number:   565127 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 24 Apr 2009 Fixed 18 May 2009 Fixed 03 Jun 2009 Fixed 18 Jan 2010 Fixed Description Quoted keywords in replication definitions do not carry to primary key and do not work on text/image columns. User will see DSI threads shutdown likely reporting illegal syntax, inspection of the RS log file will include misquoted object names. Workaround Description  For the repdef, use the "as" clause to rename the column to something more acceptable. On the target, replicate into a view.

CR:565132

CR Number:   565132 Product Name:   Rep Serv Commands Ref Product Component:   Rep Serv Commands Ref Status:   Closed OS:   all Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.5 26 Mar 2010 Added to user documentation 12 Mar 2010 Fixed Description If using subscription materialization, the primary DSI connection must be altered to use quoted identifiers.

CR:565142

CR Number:   565142 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 May 2009 Fixed 18 May 2009 Fixed Description Quoted identifiers failed in subscription materialization even with the connections set to use quoted identifiers. The changes for this CR support quoted identifiers for subscription materialization. Custom function strings with a quoted constant in the select cannot be used with quoted identifiers and subscription materialization. Target Version   Workaround Description  you have to start the subscription all over or create the subscription without materialization. Here are the steps to start the subscription over: 1. sysadmin dump_queue, q#, subscription materialization queue 2. Shutdown the RS 3. manually delete the subscription 4. delete the row for the replicate connection if this is the last subscription for the replicate connection 5. Start up Replication Server <assuming here that the connection to the primary database now allows quoted identifiers> 6. Re-create the subscription

CR:565430

CR Number:   565430 Product Name:   Repository Product Component:   Repository Status:   Open OS:   all Original Version:   closluce Fixed Version Build Resolution Date Closure Code (If Appropriate) Description PDes does not update the shortcut (name+code) in the target model in the repository with new name/code: the local document and the repository document are identical. The check in has been canceled. The display in the repository explorer is now confusing: new name is displayed in local browser, old name is displayed in repository browser.

CR:565536

CR Number:   565536 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 24 Sep 2009 Fixed 26 Mar 2009 Not a Bug Description ORACLE ONLY: java.lang.IllegalStateException with message like "No entry found in oracleLob with the LOB Column <BLOB_COL> in table <RAUSER>.<TAB>" is thrown when checking whether the object is in encrypted tablespace or not.

CR:565548

CR Number:   565548 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Sep 2009 Fixed 13 Dec 2009 Fixed 22 Sep 2009 Fixed Description ORACLE ONLY: "pdb_xlog init" fails against a supported Oracle version with message "version ... is not supported" after Replication Agent attempts to initialize against an unsupported Oracle version. Workaround Description  remove the old ra instance, and create a new on, then pdb_xlog init can be done on oracle 10g.

CR:565564

CR Number:   565564 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Jun 2009 Fixed 22 May 2009 Fixed Description ORACLE ONLY: Marking a table with partition defined in encrypted tablespace is successful when it should not be allowed.

CR:565661

CR Number:   565661 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.7.12 07 Apr 2009 Fixed Description ORACLE RAC ONLY: A LocatorComparisonException sends the Replication Agent to ADMIN state.

CR:565694

CR Number:   565694 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   MRAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.7.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Mar 2009 Fixed Description ORACLE ONLY: The "pdb_archive_path" configuration property now provides the option to include the Oracle unique database name with the ASM disk group name in order to identify the location in ASM that archived log files are stored. pdb_archive_path This parameter is available only for Oracle. Identifies the directory path where the Replication Agent expects to find archived redo log files (for Oracle). When archived redo log files or archived transaction log files are stored in the file system, the configuration parameter is set to a file system path. Default <not configured> Values For Oracle, a valid directory path on the machine hosting the Replication Agent that points to a location where Oracle places the archived redo log files. For example, ORACLE_HOME\oradata\orcl\archive For Oracle, when archived redo log files are stored in Oracle ASM, the configuration parameter must be set to the name of the ASM disk group where the archived redo log files are stored. The disk group name must be preceded with a plus + sign to specify the archive redo log path as an ASM disk group. For example, +dgroup_01 For Oracle, when archived redo log files are stored in Oracle ASM and the Oracle database name and unique database name are different, the configuration parameter must be set to the name of the ASM disk group and database name where the archived redo log files are stored. The disk group name must be preceded with a plus + sign to specify the archive redo log path as an ASM disk group followed by a path separator "/" and database name. For example, +dgroup_01/XDMQALDA Comments Setting of the configuration parameter is required when configuration property pdb_include_archives is set to true, and must be set to a valid location before the Replication Agent can be placed in a replicating state. If the Replication Agent cannot find an expected log record in the Oracle online redo logs, the Replication Agent will search this directory for the archived log file containing the required record. See also pdb_archive_remove and pdb_include_archives.

CR:565702

CR Number:   565702 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Solaris Original Version:   15.0.0.5519P8a-ONE_OFF Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Jun 2009 Fixed 21 Jun 2009 Fixed 17 Jun 2009 Fixed 17 Jun 2009 Fixed Description ORACLE ONLY: Replication Agent 'suspend' command may take a long time to complete.

CR:565705

CR Number:   565705 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   15.0 ESD#2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 Nov 2014 Fixed Description Configuration property, retry, does not change length between retries. When RS is in hibernate mode after the RS was replicating, the configuration property, Maximum_connect_retries, does not shutdown the RA DB2 after Maximum_connect_retries is reached. Workaround Description  Make Maximum_connect_retries larger. It appears that retry is hardcoded to 10 seconds.

CR:565724

CR Number:   565724 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.7.15 19 May 2009 Fixed 5.8.00 26 Mar 2009 Fixed Description ORACLE ONLY: The byte order of double byte CLOB data in LTL is not consistent with the value for lr_ntext_byte_order setting.

CR:565745

CR Number:   565745 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Mar 2009 Fixed 15 Apr 2009 Fixed 5.7.12 21 Apr 2009 Fixed 21 Apr 2009 Fixed Description ORACLE ONLY: Replication Agent fails on a rollback transaction on a multi-block undo enabled Oracle database.

CR:566000

CR Number:   566000 Product Name:   Repository Product Component:   Repository Status:   Open OS:   all Original Version:   closluce Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Feature Request: PDes shall be able to continue to response to users action while it is waiting for the repository connection and PDes shall allow users to browse other models in the workspace while it is checking in/out another document.

CR:566068

CR Number:   566068 Product Name:   Replication Management Product Component:   Agent Plugins Status:   Closed OS:   Generic Original Version:   3.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 Jul 2009 Fixed Description Replication: If the associated Rep Server was authenticated first, you may get the following exception in the SCC (UAF) console when you authenticate an ASEMAP ASE: [ASEMAP:][ERROR] [btpool1-3] Exception invoking method getRelatedManagedObjects javax.management.RuntimeOperationsException: Exception invoking method getRelatedManagedObjects. If you continue and schedule collections for all servers, the collection jobs appear to run successfully - no errors are thrown as the collections are running. When you launch the ASE Monitor for the ASEMAP ASE you may get a pop-up error: The ASEMO does not contain all the child MO(s). Click OK, and the ASE Monitor displays, but no data will be displayed on the Rep Agent screen Workaround Description  In the Resource Explorer, unregister the Rep Server and ASE involved. Note that this will remove the resources from all perspectives, delete any collection jobs that have been created and you will not be able to access any previously gathered statistics once the servers are re-registered. Re-register both Rep Server and ASE, then follow the integration steps to authenticate the resources in the required order. The above workaround could also be followed for the case where the user has been monitoring a Rep Server then later decides to add an ASE (with a RepAgent thread) that is part of the replication environment.

CR:566070

CR Number:   566070 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   SunOS Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Apr 2009 Fixed 14 May 2009 Fixed Description When Replication Server drops a route, it might produce core dump when deleting the segment. When multiple routes are created concurrently, deadlock might happen.

CR:566080

CR Number:   566080 Product Name:   Mirror Replication Agent Product Component:   MRAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Mar 2009 Added to user documentation Description When using Mirror Replication Agent version 15.1 GA and communicating with Replication Server 15.2 or later, the Mirror Replication Agent query against the Replication Server System Database to obtain replication definition information fails to return the appropriate rows. This failure causes the Mirror Replication Agent to fail with a 'replication definition not found' error.

CR:566099

CR Number:   566099 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   15.0 ESD#3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 Nov 2014 Fixed Description Trace statements show up in SYSPRINT in build 22. Workaround Description  Ignore the trace statements

CR:566117

CR Number:   566117 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   AIX Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 21 May 2009 Fixed 21 May 2009 Fixed 06 Jul 2009 Fixed Description ORACLE ONLY: Replication Agent initialization may fail to locate the Oracle timezone file even though the ORACLE_HOME environment setting is defined correctly. Workaround Description  Set the correct timezone file location to Rep Agent by "ra_config pdb_timezone_file, <path>". For example, "ra_config pdb_timezone_file, /work/ora102/oracore/zoneinfo/timezone.dat". Try "pdb_xlog init" again.

CR:566139

CR Number:   566139 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.8.00 26 Mar 2009 Fixed 5.7.15 19 May 2009 Fixed Description MICROSOFT SQL SERVER ONLY: Replication Agent instance can not start up after upgrading from pre-15.1 to current release version.

CR:566225

CR Number:   566225 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 26 Mar 2009 Not a Bug Description There are three new options to the -u parameter in the ra_admin utility for upgrading Replication Agent instances. SYNTAX: ma_admin -u <upgrade_option> PARAMETERS -u <src_instance_dir> Upgrade one instance of Replication Agent in the specified source instance directory to the product installation directory -u <instance_name> | instance=<instance_name> Upgrades only the specified instance of Replication Agent in the current product installation directory -u all Upgrade all instances of Replication Agent within the current product installation directory. EXAMPLE: To upgrade an individual instance in a specified source instance directory to the product installation directory. ma_admin -u /opt/sybase/MA-15_0/my_inst To upgrade all the instances in the current product installation. ma_admin -u all To upgrade a specific instance in the current product installation directory. ma_admin instance=my_inst OR ma_admin my_inst NOTE: - The -u <src_instance_dir> provides the ability to upgrade an individal instance from a previous major release to the current release. - The 'all' or '<inst_name>' or 'instance=<inst_name>' upgrade options performs an upgrade of instance(s) in the current product release. All upgrades are performed directly on the instance to be upgraded. The Replication Agent instance configuration file is backed before the upgrade for use in error recovery, if required. If an error occurs, the upgrade is rolled back. This option is intended for performing upgrade of instances between release to release in the same major release such as a patch update.

CR:566309

CR Number:   566309 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description 5185 message can be misleading. Workaround Description  Use SQL Statement Replication -- or -- set message 5185 (and possibly 5187) to ignore so that the message doesn't print in the RS log. To change it to ignore for the default action: update rs_erroractions set action = 1 where errorclassid = 0x000000000100001a and ds_errorid = 5185

CR:566422

CR Number:   566422 Product Name:   Replication Management Product Component:   Agent Plugins Status:   Closed OS:   Generic Original Version:   3.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 May 2009 Fixed Description Replication: A set of stored procedures is loaded into the RSSD when a Replication Server is added to SCC. In the previous release the content of the script was written to the SCC log file. This has been changed to exclude the script's content, but to add an informational message to the log that identifies the name of the script.

CR:566480

CR Number:   566480 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Reader Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.8.00 30 Mar 2009 Fixed Description ASE ONLY: For internal use only(QA found the issue before release): Table or procedure can not be marked/unmark/ enable/disabled by using "pdb_setreptable" or "pdb_setrepproc" due to "null" error.

CR:566579

CR Number:   566579 Product Name:   Repository Product Component:   Repository Status:   Open OS:   all Original Version:   closluce Fixed Version Build Resolution Date Closure Code (If Appropriate) Description State icon for both project and document does not reflect the current status in the local browser. Sometimes, icon is not displayed at all and you have to click the model/project to see it or have it updated. Workaround Description  Refresh and always check out after check in.

CR:566663

CR Number:   566663 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   15.0 ESD#3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 ESD#3 10 Aug 2009 Fixed Description Error during FREEMAIN, SYS CODE = 378-0C, for memory not allocated. Workaround Description  The user who is assigned to RA DB2, must have trace authority. Give user trace authority

CR:566670

CR Number:   566670 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Reader Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Jun 2009 Fixed 01 Jul 2009 Fixed 26 Apr 2010 Fixed Description MICROSOFT SQL SERVER ONLY: Replication Agent provides two new API command, ra_deviceoffset and ra_helpdeviceoffset to set the raw device offset and provide help on the raw device offset setting

CR:566715

CR Number:   566715 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 27 Apr 2009 Fixed 15.5 17 Jun 2009 Fixed Description Replication Server command "admin stats, status" returns error, single quoting the "status" value will avoid the problem but internal and external management tools require this keywork status without single quotes.

CR:566829

CR Number:   566829 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   all Original Version:   tyresias Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 Feb 2010 Fixed Description *** Tuesday, March 31, 2009 1:17:13 PM *** ahill *** 12.5 & 15.0 BUG: PD 12.5.0.2361(esd#19) consolidate 'metamodel.oom' to ASE 1501 esd#1 using the Sybase ASE ODBC driver 15.00.00.xxx causes loss of metadata. This issue appears to be due to the size specified in the 'text size' parameter of the ODBC DSN. The default value is 32678. The consensus from a consult is that the 'text size' attribute needs to be increased to resolve this issue. Changing this value from 32678 to 10,000,000 should have no performance related issues when working with a repository installed on ASE. This value can be increased to a maximum of 2G if necessary. Another issue that occurred was some text characters being extracted incorrectly. Using metamodel.oom, 'ellipsis' in a comment was extracted as a '.' period. This is due to the character set of the server. However, this issue can be addressed by changing the 'character set' attribute on the ODBC driver. ASE TSE has provided the following: The ellipsis (...) character is properly processed (consolidate/extract/compare from repository) when PD 125 client has MaxBytesPerChar set and the ODBC driver setting 'User Specified' = utf8 is set... //////////////////// ASE: I have an ASE 1501 ESD#1 server. It's charset = iso_1, sort = bin_iso_1. --- ODBC driver: If I set the <<User Specified>> = utf8 in the Character Set groupbox and the <<Client Default>> > Code Page Type = ANSI (it's greyed out). --- PD 12.5 client: The regkey: HKLM\Software\Sybase\PowerDesigner 12\Repository\MaxBytesPerChar =3 The ellipsis character (a unicode character) is properly mananged in the db.

CR:566833

CR Number:   566833 Product Name:   Repository Product Component:   Documentation Status:   Closed OS:   all Original Version:   tyresias Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Sep 2010 Fixed Description ENH: For Sybase ASE, it would be very helpful to offer mandatory database configuration settings that are required to accept the PD repository script and the consolidation/extraction of any/all of the example models...

CR:566854

CR Number:   566854 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.1 ESD #1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 01 Jun 2009 Fixed 01 Jun 2009 Fixed 16 Jun 2009 Fixed Description When Replication Server can not connect to replicate database and continues to retry the connection, memory leak will happen. Workaround Description  Suspend the connection. However the memory is not freed.

CR:566944

CR Number:   566944 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.9.00 20 May 2009 Fixed 5.8.00 20 May 2009 Fixed 5.7.15 20 May 2009 Fixed Description ORACLE ONLY: The system tables for Oracle user 'WK_TEST' and 'FLOWS_FILES' are now being filtered out for replication by default.

CR:566946

CR Number:   566946 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Admin Status:   Closed OS:   Generic Original Version:   5.8.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Jun 2009 Fixed 01 Jul 2009 Fixed 01 Jul 2009 Fixed Description When the transaction log does not exist in the primary database or the RASD is not yet initialized, "pdb_setrepcol" with no argument returns "0 rows affected" instead of returning an error.

CR:566987

CR Number:   566987 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 27 Apr 2009 Fixed 15.5 04 May 2009 Fixed Description Replication Server 15.2 Upgrade script has a typo when adding a new function string "rs_get_errormode". User may see erroneously reporting of warning message #13110.

CR:567006

CR Number:   567006 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 Apr 2009 Fixed Description 'create error class <class>' where <class> is a Replication Server class, returns message about system table being corrupt when it is not. The correct command for creating a Replicaton Server error classes is: create replication server error class rs_repserver_error_class Workaround Description  Nothing is wrong with the rs_classes table. To set the primary Rep Server id to this rep server error class, use the following command: create replication server error class <classname> for instance: create replication server error class rs_repserver_error_class

CR:567192

CR Number:   567192 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.7.12 07 Apr 2009 Fixed 5.8.01 30 Jul 2009 Bundled Request 5.9.00 30 Jul 2009 Bundled Request Description ORACLE RAC ONLY: Oracle RAC replication performance is slow.

CR:567241

CR Number:   567241 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Mar 2010 Insufficient priority to fix Description RS 15.1 and 15.2 use considerable more memory at bootup than RS 15.0.1 for the same number of connections. Workaround Description  None, however, the effect is that memory_limit should be increased to allow for variation when the connections are used.

CR:567247

CR Number:   567247 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Apr 2009 Fixed 15 Apr 2009 Fixed 24 Apr 2009 Fixed Description Error message #5185 messages is not supressed when the corresponding error action is set to 'ignore'. The error will continue to be reported in the Replication Server error log causing the log to fill very quickly if the source and target databases are out of sync. Workaround Description  None at this time.

CR:567376

CR Number:   567376 Product Name:   Replication Management Product Component:   Access Library Status:   Open OS:   Generic Original Version:   3.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 May 2009 Fixed Description Replication: The following error may appear in the Sybase Control Center agent.log: Attempt to locate entry in sysdatabases for database 'database_name' by name failed - no entry found under that name. Make sure that name is entered properly.

CR:567436

CR Number:   567436 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.5 ESD #2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Jun 2010 Fixed 19 Jan 2011 Fixed Description 5185, 5186, 5187 should identify the table that is producing the message. Workaround Description  change error to stop_replication, do a dsi_buf_dump, then examine/rerun the function to identify the culprit.

CR:567480

CR Number:   567480 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Linux Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 May 2009 Fixed Description When the Replication Server replicates text data containing multi-byte characters and the length of text data is longer than 4KB, the Replication Server may fall down with a 7035 error (additional allocation would exceed the memory_limit). This can occur if the ASE and the Replication Server are both configured with multi-byte character sets.

CR:567610

CR Number:   567610 Product Name:   Replication Management Product Component:   Web UI Status:   Closed OS:   Generic Original Version:   3.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Jun 2009 Fixed Description When parameters "Change in Activity (commands)" and/or "Latency(sec) are zero, the Path dashboard does not display the queues chart.

CR:567614

CR Number:   567614 Product Name:   Replication Management Product Component:   Web UI Status:   Closed OS:   Generic Original Version:   3.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Jun 2009 Fixed Description Only the top 10 queues are being displayed in the Replication Server dashboard Queues view.

CR:567682

CR Number:   567682 Product Name:   Sybase Replication Server Product Component:   RMA Status:   Closed OS:   AIX Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 05 Aug 2009 Presently Not Targeted For Any Future Release Of This Product Description RMS agent: If the RMS agent, on IX, is unable to login to the RepServer (due to login failure) then the network may fill with unclosed connections eventually preventing further connections to RS. Workaround Description  Shutdown UA process.

CR:567729

CR Number:   567729 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 14 Jul 2009 Fixed 14 Jul 2009 Fixed 14 Jul 2009 Fixed Description ORACLE ONLY: Replication Agent goes to ADMIN state with error "Too many open files". Workaround Description  *** Wednesday, April 08, 2009 9:36:05 AM *** blopez *** If the operating system has the ability to increase the number of file that can be open at a time, increase the allowed number of open files to ensure the number of disks required to read all redo logs can be open at the same time.

CR:567760

CR Number:   567760 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.0.1 ESD#3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0.1 05 May 2009 Fixed 15.2 03 May 2009 Fixed 15.1 07 May 2009 Fixed 12.6 ESD#10 24 Jul 2009 Fixed Description When multiple threads update the 'rs_databases' system table twice in one transaction, then the STS cache will be corrupted.

CR:567814

CR Number:   567814 Product Name:   Replication Management Product Component:   Agent Plugins Status:   Open OS:   Solaris Original Version:   3.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 May 2009 Fixed Description Replication: The Replication Topology view may not display correctly if a server is unregistered from Sybase Control Center and a different server is registered under the same name.

CR:567821

CR Number:   567821 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 14 Jul 2009 Fixed 5.8.01 09 Jul 2009 Fixed 14 Jul 2009 Fixed Description ORACLE ONLY: Low scan_sleep_max configuration may stop replication. There is a new Replication Agent configuration log_scan_eol_threshold for determining when to flush sorted records that have not been checkpointed. And in Oracle RAC environment, for helping to determine when a node in a cluster is no longer active. log_scan_eol_threshold The threshold used to determine when to flush sorted records that have not been checkpointed. Default 300 Values An integer from 300 to 2147483647. Comments - The value of the log_scan_eol_threshold parameter is the maximum number of seconds that can elapse before the Log Scanner component flush sorted records that have not been checkpointed. Notes - For Oracle RAC, log_scan_eol_threshold configuration is used in determining whether a node in the cluster is active. Since a node may go down at any point during replication, Replication Agent has to determine when a node is no longer active, and the log_scan_eol_threshold configuration is used for this purpose. If Replication Agent is reading at the end of the node's redo log thread and there are no checkpointed records in the queue, Replication Agent will treat a node as inactive after the number of seconds specified by the log_scan_eol_threshold configuration pass. The log_scan_eol_threshold configuration can not be set too low, otherwise Replication Agent treating a node as inactive when it is actually still active. Workaround Description  Increase the scan_sleep_max configuration value.

CR:567926

CR Number:   567926 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description bulk insert doesn't do bulk insert on nullable text column, replicate_if_changed and ASE 12.5.4. Workaround Description  Use ASE 15.x OR change the text column to always_replicate (and also change the replication definition to match the text definition) OR make the text column not allow NULLS.

CR:567946

CR Number:   567946 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Apr 2009 Fixed Description Stack upon startup with quoted identifiers on. Workaround Description  probably purge the queue.

CR:567970

CR Number:   567970 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 Apr 2009 Fixed 27 Aug 2009 Fixed Description Self-join queries do not be replicated as SQL statement correctly. The Replication Server applies the SQL statement as the maintenance user and the target ASE does not process is correctly. The Replication Server should use the owner name associated with the table in the replication definition and apply the SQL with the prefix owners name included in the target table.

CR:568078

CR Number:   568078 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.7.02 08 May 2009 Fixed 15.2 ESD #1 25 May 2009 Fixed 28 Jul 2009 Fixed 15.2 ESD #1 28 Jul 2009 Fixed Description ORACLE ONLY: Transaction user is not sent correctly when using "Oracle Identity Manager 10.1.4". There is a new Replication Agent command to support use of Oracle Identity Manager. Command: pdb_send_osuser_list Description: Add or remove database user id to/from osuser list. If the database user is in the osuser list, then any transactions for that database user will be sent as the relative operating system user for that transaction user. This list is a list of 'database' users that will need to be replaced with the 'operating system' user name. This is NOT a list of 'operating system' users. This command also returns a list of the database users in the osuser list. Syntax: pdb_send_osuser_list pdb_send_osuser_list [[add | remove],[user | all]] Parameters: add The add keyword add user into osuser list, whose transaction will be sent to Replication Server as its relative operating system user. remove The remove keyword removes database user from osuser list. user The name of the database user that need be converted to operating system user. The user name is case insensitive. all All database users will be converted to operating system user if they have a valid operating system user. Examples: Example 1 pdb_send_osuser_list This command lists database users who will be converted to osuser. Assuming a person logs into their operating system as joeuser, and subsequently logs into Oracle as user_a: Example 2 pdb_send_osuser_list add, user_a This command adds database 'user_a' into osuser list. The transaction of 'user_a; will be sent as operating system user joeuser Example 3 pdb_send_osuser_list remove, user_a This command removes database 'user_a' from osuser list. The transaction of database 'user_a' will no longer be converted to the operating system user 'joseuser'. Example 4 pdb_send_osuser_list add, all The transaction of all database users will be sent as operating system user Usage: - When pdb_send_osuser_list is invoked, its function is determined by the keywords and options you specify. When multiple keywords and options are specified, each must be separated by a comma. Blank space before or after a comma is optional. - Only session login later then pdb_send_osuser_list will be converted as osuser. The session by user which is earlier than pdb_send_osuser_list setting will not change. For example: pdb_send_osuser_list add, user - The pdb_send_osuser_list command is valid only when the Replication Agent instance is in ADMIN state. - If command without parameters to list only, then it valid for any status.

CR:568104

CR Number:   568104 Product Name:   Rep Serv Admin Guide Product Component:   Rep Serv Admin Guide Status:   Closed OS:   all Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.5 21 Mar 2010 Fixed Description Documentation clarification: cannot change the declared datatype if the column is used in a where clause.

CR:568145

CR Number:   568145 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.9.00 07 Jul 2009 Fixed 5.9.00 09 Jul 2009 Fixed 5.8.01 08 Jul 2009 Fixed Description ORACLE ONLY: Replication Agent may fail with Filechannel Map failed Exception when user initializes Replication Agent and then re-initializes it on HPIA platform. Workaround Description  pdb_xlog init shutdown replication agent pdb_xlog init,force

CR:568248

CR Number:   568248 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 03 May 2009 Fixed 26 Aug 2009 Fixed Description Dynamic SQL will not be used when a table has a timestamp data type and a database replication definition and table replication definition are used. Workaround Description  Either just use the repdef or just use the msa, do not use both.

CR:568254

CR Number:   568254 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Nov 2009 Fixed 15 Sep 2009 Fixed 25 Nov 2009 Fixed 10 Dec 2009 Fixed Description Dynamic SQL procedures that are automatically generated, should have a name that identifies the target table and the operation (insert, update, delete)

CR:568271

CR Number:   568271 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   LTM Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.5 17 Nov 2009 Fixed 15.2 ESD #2 17 Nov 2009 Fixed Description Replication Agent will now log the Java VM maximum, total, and free memory amounts (in bytes) in the log file during initialization and when ra_version_all is invoked.

CR:568452

CR Number:   568452 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/UDB Status:   Closed OS:   Solaris Original Version:   5.8.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Jul 2009 Fixed 15.5 14 Jul 2009 Fixed Description UDB ONLY: Multi-record updates are not handled correctly when the primary database is IBM UDB 9.5.

CR:568476

CR Number:   568476 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.7.12 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.7.12 24 Apr 2009 Fixed 5.8.00 27 Apr 2009 Fixed Description ORACLE ONLY: The primary and replicate databases are out of synch.

CR:568493

CR Number:   568493 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 28 Apr 2009 Fixed 15.5 04 May 2009 Fixed Description The order of new column rs_errorclassid is wrong in Replication Server 15.2 upgrade/downgrade scripts, which should follow the schema of rs_databases in rs_install_systable_as[a|e].sql script file. Workaround Description  akirkpat for annie shan - Dec 2, 2009 Here are my steps to fix rs_errorclassid. To simplify: - back up the RSSD - alter table rs_databases drop rs_errorclassid - alter table rs_databases add rs_errorclassid rs_id default 0x000000000100001a however, there are two triggers on rs_databases. I am not sure if it is required to rebuild these two triggers, but i did it. - Annie ---------- 1> use rrs1_rssd126 2> go 1> select * from rs_databases 2> go dsname dbname dbid dist_status src_status attributes errorclassid rs_errorclassid funcclassid prsid rowtype sorto_status ltype ptype ldbid enable_seq ------------------------------ ------------------------------ ----------- ----------- ---------- ---------- ------------------ ------------------ ------------------ ----------- ------- ------------ ----- ----- ----------- ----------- LDS LDB 219 1 1 0 0x0000000000000000 0x000000000100001a 0x0000000000000000 16777322 1 0 L L 219 0 REL1251_SHAN route1 208 1 1 0 0x0000000001000002 0x000000000100001a 0x0000000001000001 16777322 1 0 P A 208 0 REL1251_SHAN rrs1_rssd126 206 1 1 0 0x0000000001000002 0x000000000100001a 0x0000000001000001 16777322 0 0 P A 206 0 dco10gss dco150 226 3 0 0 0x0000000001000016 0x000000000100001a 0x0000000001000007 16777322 1 0 P A 226 0 (4 rows affected) alter table rs_databases drop rs_errorclassid 1> alter table rs_databases add rs_errorclassid rs_id default 0x000000000100001a 2> go Non-clustered index (index id = 3) is being rebuilt. Non-clustered index (index id = 4) is being rebuilt. Non-clustered index (index id = 5) is being rebuilt. Non-clustered index (index id = 6) is being rebuilt. Warning: The schema for table 'rs_databases' has changed. Drop and re-create each trigger on this table that uses the 'if update(column_name)' clause. 1> select * from rs_databases 2> go dsname dbname dbid dist_status src_status attributes errorclassid funcclassid prsid rowtype sorto_status ltype ptype ldbid enable_seq rs_errorclassid ------------------------------ ------------------------------ ----------- ----------- ---------- ---------- ------------------ ------------------ ----------- ------- ------------ ----- ----- ----------- ----------- ------------------ LDS LDB 219 1 1 0 0x0000000000000000 0x0000000000000000 16777322 1 0 L L 219 0 0x000000000100001a REL1251_SHAN route1 208 1 1 0 0x0000000001000002 0x0000000001000001 16777322 1 0 P A 208 0 0x000000000100001a REL1251_SHAN rrs1_rssd126 206 1 1 0 0x0000000001000002 0x0000000001000001 16777322 0 0 P A 206 0 0x000000000100001a dco10gss dco150 226 3 0 0 0x0000000001000016 0x0000000001000007 16777322 1 0 P A 226 0 0x000000000100001a 1> select object_name(681050431) 2> go ------------------------------ rs_databases_ins (1 row affected) 1> select object_name(697050488) 2> go ------------------------------ rs_databases_upd drop trigger rs_databases_ins drop trigger rs_database_upd create trigger rs_databases_ins on rs_databases for insert as begin update rs_databases /* This upgrades rs_databases rows from pre 11.0 replication ** servers by setting src_status = 3 where it was 2. */ set src_status = 3 where ldbid = 0 and ptype = 'A' and dbid in (select inserted.dbid from inserted where src_status = 2) update rs_databases /* This upgrades rs_databases rows from pre 11.0 replication ** servers by setting dist_status = 3 where it was 2. */ set dist_status = 3 where ldbid = 0 and ptype = 'A' and dbid in ( select inserted.dbid from inserted where dist_status = 2) update rs_databases /* This upgrades rs_databases rows from pre 11.0 replication ** servers by setting ldbid = pdbid. */ set ldbid = dbid where ldbid = 0 and ptype = 'A' and dbid in (select inserted.dbid from inserted) if (select count(*) from inserted where inserted.ptype = 'K') > 0 begin update rs_subscriptions /* reset status Q_COMPLETE when subscription is atomic and Q_COMPLETE and */ /* not VALID and from the right primary */ set status = (status & (~2)), recovering = 1 from rs_subscriptions, rs_objects, inserted where /* it is a primary switch */ inserted.ptype = 'K' and /* subscription is materializing */ materializing = 1 and /* primary is the ldbid */ rs_subscriptions.objid = rs_objects.objid and rs_objects.dbid = inserted.ldbid and /* subscription is atomic */ (method & 1 = 1) and /* subscription is in Q_COMPLETE but not VALID state */ (status & 2 = 2) and (status & 16 = 0) update rs_subscriptions /* set status to SUSPECT when subscription is nonatomic and */ /* not VALID and from the right primary */ /* #33554432=0x2000000 */ set status = (status | (33554432)), recovering = 1 from rs_subscriptions, rs_objects, inserted where /* it is a primary switch */ inserted.ptype = 'K' and /* subscription is materializing */ materializing = 1 and /* primary is the ldbid */ rs_subscriptions.objid = rs_objects.objid and rs_objects.dbid = inserted.ldbid and /* subscription is nonatomic */ (method & 16 = 16) and /* subscription is not in VALID state */ (status & 16 = 0) end end te trigger rs_databases_upd on rs_databases for update as begin if (select count(*) from inserted where inserted.ptype = 'K') > 0 begin update rs_subscriptions /* reset status Q_COMPLETE when subscription is atomic and Q_COMPLET E and */ /* not VALID and from the right primary */ set status = (status & (~2)), recovering = 1 from rs_subscriptions, rs_objects, inserted where /* it is a primary switch */ inserted.ptype = 'K' and /* subscription is materializing */ materializing = 1 and /* primary is the ldbid */ rs_subscriptions.objid = rs_objects.objid and rs_objects.dbid = inserted.ldbid and /* subscription is atomic */ (method & 1 = 1) and /* subscription is in Q_COMPLETE but not VALID state */ (status & 2 = 2) and (status & 16 = 0) update rs_subscriptions /* set status to SUSPECT when subscription is nonatomic and */ /* not VALID and from the right primary */ /* #33554432=0x2000000 */ set status = (status | (33554432)), recovering = 1 from rs_subscriptions, rs_objects, inserted where /* it is a primary switch */ inserted.ptype = 'K' and /* subscription is materializing */ materializing = 1 and /* primary is the ldbid */ rs_subscriptions.objid = rs_objects.objid and rs_objects.dbid = inserted.ldbid and /* subscription is nonatomic */ (method & 16 = 16) and /* subscription is not in VALID state */ (status & 16 = 0) end end

CR:568670

CR Number:   568670 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.7.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Sep 2009 Fixed 22 Jul 2009 Fixed 23 Sep 2009 Fixed Description ORACLE ONLY: Replication Agent appears to be hung after a 'resume' command if there are a lot of archive logs stored in Oracle ASM.

CR:568684

CR Number:   568684 Product Name:   Replication Management Product Component:   Access Library Status:   Closed OS:   Generic Original Version:   3.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 May 2009 Fixed Description The following error may be displayed in the Sybase Control Center agent.log: Collection task failed and will be skipped. Message=null

CR:568982

CR Number:   568982 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Generic Original Version:   15.1.0.5700 Fixed Version Build Resolution Date Closure Code (If Appropriate) 14 Jun 2009 Fixed 09 Jun 2009 Fixed 14 Jun 2009 Fixed Description MICROSOFT SQL SERVER ONLY: If Microsoft SQL Server is upgraded to SP3, some Replication Agent system objects are overwritten. Please use ra_migrate command to restore these missing objects. Workaround Description  There are two workaround here. #1) Re-generate server xlog objects in Microsoft SQL Server system resource database. a) Download a sql script from the "Attach" tab of this CR or copy the sql content below, the sql script is mssqlsystemresource_setup.sql, and put it under %RAX-15_1%\scripts\mssql\ directory. b) Restart Microsoft SQL Server in single user mode by opening a new command window and executing this command: "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe" -m -sserverName\instanceName Here, instanceName is the name of the Microsoft SQL Server instance. c) Log on to Microsoft SQL Server as system administrator by using Dedicated Admin Connection and run mssqlsystemresource_setup script. "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\sqlcmd.exe" -UuserName -Ppassword -SserverName\instanceName -A -i%RAX-15_1%\scripts\mssql\mssqlsystemresource_setup.sql d) Restart Microsoft SQL Server in multiple user mode. ============The content of script mssqlsystemresource_setup.sql=================== USE mssqlsystemresource GO Alter database mssqlsystemresource set Read_Write GO if object_id('sp_SybSetLogforReplTable') is not null begin drop procedure sp_SybSetLogforReplTable end GO -- -- null -- CREATE PROCEDURE sys.sp_SybSetLogforReplTable @tabid int ,@mark int AS SET NOCOUNT ON BEGIN if (@mark = 1) EXEC %%Relation(ID = @tabid).SetReplicated(Value = 1) else EXEC %%Relation(ID = @tabid).SetReplicated(Value = 0) EXEC sys.sp_SybSetLogforLOBCol @tabid,@mark return 0 END GO GO Update sys.sysschobjs set status =0 where name = 'sp_SybSetLogforReplTable' GO Grant exec on sp_SybSetLogforReplTable to public GO if object_id('sp_SybSetLogforLOBCol') is not null begin drop procedure sp_SybSetLogforLOBCol end GO -- -- null -- CREATE PROCEDURE sys.sp_SybSetLogforLOBCol @tabid int ,@mark int AS SET NOCOUNT ON BEGIN set nocount on DECLARE @colname sysname,@source_table sysname DECLARE #lobcol CURSOR LOCAL FAST_FORWARD FOR SELECT name FROM sys.columns where object_id = @tabid and is_replicated != @mark and (system_type_id in (34, 35, 99) or user_type_id in (34, 35, 99)) -- image, text, ntext DECLARE @is_replicated tinyint SELECT @is_replicated = is_replicated from sys.tables where object_id = @tabid OPEN #lobcol FETCH #lobcol INTO @colname WHILE (@@fetch_status <> -1) BEGIN IF (@mark = 1) and (@is_replicated = 1) EXEC %%ColumnEx(ObjectID = @tabid, Name = @colname).SetReplicated(Value = 1) ELSE IF (@mark = 0) EXEC %%ColumnEx(ObjectID = @tabid, Name = @colname).SetReplicated(Value = 0) IF @@ERROR <> 0 BEGIN SELECT @source_table = object_name(@tabid) RAISERROR(15165, -1, -1, @source_table) RETURN 1 END FETCH #lobcol INTO @colname END --WHILE CLOSE #lobcol DEALLOCATE #lobcol END GO GO Update sys.sysschobjs set status =0 where name = 'sp_SybSetLogforLOBCol' GO Grant exec on sp_SybSetLogforLOBCol to public GO if object_id('sp_SybSetLogforReplProc') is not null begin drop procedure sp_SybSetLogforReplProc end GO -- -- null -- CREATE PROCEDURE sys.sp_SybSetLogforReplProc @procid int ,@mark int AS SET NOCOUNT ON BEGIN if (@mark = 1) EXEC %%Module(ID = @procid).SetProcReplicated(Value = 1) ELSE EXEC %%Module(ID = @procid).SetProcReplicated(Value = 0) END GO GO Update sys.sysschobjs set status =0 where name = 'sp_SybSetLogforReplProc' GO Alter database mssqlsystemresource set Read_Only GO #2) Another recovery is to run pdb_xlog remove and then pdb_xlog init and remark tables and procedures to be replicated.

CR:569140

CR Number:   569140 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.8.00 19 May 2009 Bundled Request 5.7.12 19 May 2009 Bundled Request 5.5.23 08 Dec 2009 Fixed Description ORACLE ONLY: The primary and replicate databases are out of synch and the Replication Agent system log contains a warning message indicating that the log sequence number for the second block in the log does not match the log header sequence number.

CR:569230

CR Number:   569230 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Apr 2009 Fixed 28 Apr 2009 Fixed 16 Jun 2009 Fixed Description When primary Replication Server can not connect to replicate Replication Server and continues to retry the connection, memory leak will happen.

CR:569283

CR Number:   569283 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   LTI Driver Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.8.00 21 Apr 2009 Fixed 5.7.15 11 Oct 2009 Fixed Description Replication Agent fails to resume with error "LTI start replication failed to initialize connections", after Replication Server is upgraded to 15.2. Workaround Description  a) Shutdown Rep Server b) Log on to RSSD(ASE), and execute the following sql script. alter table rs_databases drop rs_errorclassid go alter table rs_databases add rs_errorclassid rs_id default 0x000000000100001A go c) Start Rep Server

CR:569335

CR Number:   569335 Product Name:   Rep Serv Admin Guide Product Component:   Rep Serv Admin Guide Status:   Closed OS:   all Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.5 22 Mar 2010 Not a Bug Description Provide more details on setting up SSL in RepServer

CR:569519

CR Number:   569519 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.7.12 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 Apr 2009 Fixed 28 Apr 2009 Fixed Description ORACLE ONLY: The primary and replicate databases are out of synch or an open transaction prevents the truncation point from moving and also results in the Replication Server stable queue filling up.

CR:569549

CR Number:   569549 Product Name:   Replication Management Product Component:   Agent Plugins Status:   Closed OS:   Generic Original Version:   3.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 May 2009 Fixed Description Replication: SCC now supports Replication Agent and Mirror Replication Agent version 15.2.

CR:569585

CR Number:   569585 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Generic Original Version:   15.1.0.5700 Fixed Version Build Resolution Date Closure Code (If Appropriate) 24 Jun 2009 Workaround 24 Jun 2009 Workaround 11 Oct 2009 Presently Not Targeted For Any Future Release Of This Product Description MICROSOFT SQL SERVER ONLY: This is a limitation for Replication Agent. The workaround is that zero the locator of RASD by Replication Agent command 'ra_locator zero' and zero the locator of Replication Server by Replication Server command 'rs_zeroltm <data_server>, <database>'. Before doing this, please make sure that all the data have finished replication. Then resume Replication Agent again.

CR:569869

CR Number:   569869 Product Name:   Repository Product Component:   Repository Status:   Open OS:   all Original Version:   closluce Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Unfreeze feature is not available if user has Write permission on the document.

CR:569956

CR Number:   569956 Product Name:   RepConnector Product Component:   Run-time Engine Status:   Open OS:   Solaris Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) Fixed Fixed Fixed Fixed Description Enhancement for latency checking from RepServer to RepConnector.

CR:570001

CR Number:   570001 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   15.2 ESD #1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 29 Apr 2009 Fixed Description Replication Server may report a unique constraint error in an Oracle-to-Oracle environment due to incorrectg usage of the begin and end transaction markers (DSIC_XACG_END_M/DSIC_XACT_BEGIN_M).

CR:570015

CR Number:   570015 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   15.2 ESD #1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Apr 2009 Fixed 27 Apr 2009 Fixed 14 May 2009 Fixed Description In the SMP implementation, the SQM_RS_SEGMENTS_MUTEX_C is mistakenly acquired instead of the sqm_segs_sync element, this can cause a deadlock in the SQT and SQM write theads.

CR:570206

CR Number:   570206 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   Windows XP Original Version:   closluce EBF6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 19 May 2009 Fixed Description reproduce: 1.install repository on ASA10 by JDBC , after executing scripts a few time, it pops up an error window says that "SQLSTATE = 23502 SQL Anywhere Error -195: Column 'CMMT' in table 'PMUSER' cannot be NULL". This issue only happens when using PD EBF6 to install repository directly, if the repository is installed by some older versions and use PD BEF6 to upgrade, it works fine. And if install by ODBC directly, it works fine too.

CR:570505

CR Number:   570505 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Open OS:   Microsoft Windows NT Original Version:   15.1.0.5602 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Mar 2010 Fixed 22 Oct 2009 Fixed Description Restriction: varchar(max) can only be replicated to MS SQL targets. Workaround Description  None known at this time. The varchar(max) will always send to RS, the LTL used in partial LOB update. Since this capability is not available on other DBMSs, these columns cannot be replicated to anything other than the DMBS where they came from, in this case, MS SQL.

CR:570511

CR Number:   570511 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Open OS:   Microsoft Windows NT Original Version:   15.1.0.5602 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Allow varchar(max) to replicate to non-MS SQL targets Workaround Description  None currently

CR:570520

CR Number:   570520 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Generic Original Version:   15.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Design capability in RS to use appropriate process in DSI to update a column values when the source column value has to be handled in two or more different methods.

CR:570668

CR Number:   570668 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   LTI Driver Status:   Closed OS:   Generic Original Version:   5.8.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 02 Jun 2009 Fixed 01 Jun 2009 Fixed Description Increase rs_packet_size maximum to 64K.

CR:570748

CR Number:   570748 Product Name:   Repository Product Component:   Repository Status:   Open OS:   all Original Version:   closluce Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Allow objects within resource files to be viewable via the CMR application. Specifically, the customer would like to view the extended attributes associated with objects. The customer uses extended attributes extensively throughout their models. With the introduction of CMR, they would like to the extended attributes exposed. The lack of this exposure limits the effectiveness of the CMR application for their company. Their intention is to use CMR to allow 300+ users to view metadata associated with their models. Without the extended attribute a large portion of this information is missing.

CR:570754

CR Number:   570754 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   15.0 ESD#3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 ESD#3 23 05 Aug 2009 Fixed Description Abend S23E after monitoring turned off.

CR:570757

CR Number:   570757 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   15.0 ESD#3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 ESD#3 23 05 Aug 2009 Fixed Description After an F REPJOB,C,MONITOR=1 command the monitor display shows when a minute has elapsed but never displays again.

CR:570762

CR Number:   570762 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   15.0 ESD#3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 ESD#4 06 08 Jun 2010 Fixed Description The Rep Agent abends with an 878 trying to getmain storage when the reason code indicates there is none available.

CR:570763

CR Number:   570763 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   15.0 ESD#3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 ESD#3 26 05 Aug 2009 Fixed Description The Rep Agent gets an S0C4 abend when the Rep Server queues fill up and the Rep Server refuses connections.

CR:570766

CR Number:   570766 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   15.0 ESD#3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 ESD#3 10 Aug 2009 Not a Bug Description The Rep Agent job abends on time out with an SEC6 instead of the normal S322 (timeout cancel).

CR:570775

CR Number:   570775 Product Name:   Replication Server Product Component:   Other Status:   Closed OS:   Generic Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 01 May 2009 Not a Bug Description Sybase Replication Server 15.2 is a completely new version. As a result, there are no fixed bugs to list in this section.

CR:570934

CR Number:   570934 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.7.13 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 ESD #1 29 Jul 2009 Fixed 15.5 28 Jul 2009 Fixed Description ORACLE RAC ONLY: There is a new Replication Agent configuration for scanning the primary database redo log threads in parallel. Configuration Parameter Name lr_parallel_scan Description The lr_parallel_scan configuration property is applicable to Oracle RAC only and determines whether the redo log threads for all nodes in a clustered database are scanned in parallel or whether a single serial scan is used. Default false Values true, false Comments - When true, the Replication Agent will start a redo log scan thread for each redo log thread in the clustered database. - When false, the Replication Agent will do redo log thread reads for each redo log thread in the clustered database serially.

CR:570942

CR Number:   570942 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.5.17 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 May 2009 Presently Not Targeted For Any Future Release Of This Product 5.8.01 20 May 2009 Fixed 5.9.00 24 Jul 2009 Fixed 5.8.01 24 Jul 2009 Fixed 30 Jun 2009 Fixed 07 Jul 2009 Fixed 10 Jul 2009 Fixed 15 Jul 2009 Fixed 26 Jul 2009 Fixed 21 Jul 2009 Fixed Description ORACLE ONLY: New commit generation feature has been added to improve RAC replication latency. The feature is configured and monitored using the following API commands and properties. Configuration property: pdb_commit_generation Values: true or false Default: false Description: If pdb_commit_generation is set to true, Replication Agent will generate committed transactions in the primary database at a configured interval. Configuration property: pdb_commit_interval Valid values: 1 to 5 seconds Default: 1 second Description: pdb_commit_interval is the interval, in seconds, at which the committed transactions are generated in the primary database. Command: pdb_commit_generation_status Description: The command returns the status for all primary database commit generation threads. Command: pdb_commit_generation_filter <action>,<inst> Values: action is the keyword 'add' or remove', inst is the valid Oracle instance name, or the keyword 'all' Description: If the keyword 'add' is passed as an argument, Replication Agent will add the instance to the filter list, disabling the commit generation for the instance. If the keyword 'remove' is passed as an argument, Replication Agent will remove the instance from the filter list and enable the commit generation for the instance. When the command is called without any arguments, then the names of all filtered instances are displayed.