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

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

CR:486616

CR Number:   486616 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) 5.6.02 28 Feb 2008 Fixed 5.5.08 01 Feb 2008 Fixed Description ORACLE_ONLY: Timestamp with time zone value may not be replicated correctly.

CR:486700

CR Number:   486700 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Management Status:   Closed OS:   Microsoft Windows NT Original Version:   15.0.0.5500 Fixed Version Build Resolution Date Closure Code (If Appropriate) 20 Jul 2009 Fixed 29 Jul 2009 Fixed Description Install RAX as a Windows Service. User can create ,remove,start or stop a windows service using this tool Workaround Description  Use Windows resource kit to create a service or run RAX with .bat file. It still does not provide automatic startup of RAX when machine is rebooted.

CR:486770

CR Number:   486770 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 01 10 Aug 2009 Third Party Problem 15.0 ESD#3 07 10 Aug 2009 Third Party Problem Description Replication Agent locks table spaces so CA DB2 utilities cannot use those table spaces even when the table spaces are unrelated to tables that are being replicated.

CR:486981

CR Number:   486981 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   all Original Version:   tyresias Fixed Version Build Resolution Date Closure Code (If Appropriate) 17 Jan 2008 Fixed 31 Jan 2008 Fixed Description A repository user can consolidate objects in a model containing a package on the model root level if he has write/full permission on the package level and read permission on the model root level. This however should not be allowed due to missing permissions. Workaround Description  None

CR:487020

CR Number:   487020 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.10 Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 Nov 2014 Not a Bug Description 0C4 in LTMINFO at offset 00002B42 after inserting many transactions into LTMOBJECTS Workaround Description  Restart RA DB2

CR:487081

CR Number:   487081 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/UDB Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 26 Feb 2008 Fixed 5.5.09 26 Feb 2008 Fixed Description UDB ONLY: When replicating an update for a table created with the value compression clause, extra characters are appended to the end of the last column's data.

CR:487165

CR Number:   487165 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Linux Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description drop connection produces stack Workaround Description  Once RS crashes, issue the drop connection again.

CR:487270

CR Number:   487270 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/UDB Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.8.00 30 Aug 2008 Fixed 5.6.04 07 May 2008 Fixed 5.5.14 28 May 2008 Fixed Description UDB ONLY: Replication Agent for UDB now supports ra_dump command.

CR:487338

CR Number:   487338 Product Name:   Sybase Replication Server Product Component:   RSMJavaPlugin Status:   Closed OS:   NA Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Sep 2009 Presently Not Targeted For Any Future Release Of This Product Description Replication Manager Plug-in: Connection status folder is NOT refreshed manually using the Refresh menus or Icons. Workaround Description  Reduce Monitoring Interval in Properties of the Replication Environment.

CR:487352

CR Number:   487352 Product Name:   RepConnector Product Component:   Misc. Status:   Open OS:   Solaris Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description The customer will now be able to select a different log file for the connection being configured, and have the ability to specify the name and location of the log file.

CR:487403

CR Number:   487403 Product Name:   Rep Serv Rel Bull Product Component:   Rep Serv Rel Bull Status:   Closed OS:   NA Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 02 Jul 2008 Added to user documentation Description Release Bulletin needs to include detailed requirements for Linux versions that have been certified. Workaround Description  Use certification report: http://certification.sybase.com/ucr/platformDetail.do?certId=1951&platformId=117&productId=34

CR:487427

CR Number:   487427 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Solaris Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description modify rs_dump_stats to only get a subset of the available data

CR:487432

CR Number:   487432 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   MRAgent/ASE Status:   Closed OS:   Generic Original Version:   12.6.0.5305P16 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.3.08 13 Oct 2008 Fixed 5.5.17 08 Oct 2008 Fixed Description ASE ONLY: Replication Agent fails to replicate a rollback operation with error "Caught an unexpected fatal exception: Could not get locator for operation to rollback".

CR:487506

CR Number:   487506 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.5.07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 26 Feb 2008 Fixed 5.5.08 01 Feb 2008 Fixed Description ORACLE ONLY: Replication Agent processing causes the Oracle session information in the Replication Agent System Database (RASD) to fill up which will affect the performance of replication. Issuing the 'ra_truncateusers' command will only solve the problem temporarily. Workaround Description  Issue command "ra_truncateusers" periodically to keep the size of the oracleSession table reduced.

CR:487598

CR Number:   487598 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Mar 2008 Fixed Description Memory leak in Replication Server when interfaces file entry for target server does not exist. This is Sybase Connectivity bug (CR 483926) fixed in OCS 15.0 ESD #12. Workaround Description  Suspend the connection or drop the connection to all servers that no longer exist. This way, the RS does not constantly try to retry the connection. Reboot the Rep Server to get the memory back.

CR:487621

CR Number:   487621 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Admin Status:   Closed OS:   Microsoft Windows NT Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 26 Feb 2008 Fixed 5.5.08 01 Feb 2008 Fixed Description WINDOWS ONLY: The pdb_date, ra_date commands return an incorrect month if the OS region is set to Chinese. Workaround Description  set OS regional to English and restart RA.

CR:487732

CR Number:   487732 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Microsoft Windows NT Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed 5.5.10 05 May 2008 Fixed Description ORACLE ONLY: If pdb_execute_sql is used to execute certain SQL commands such as "pdb_execute_sql "create table test(id int)", the following errors is returned "CT-LIBRARY error: ct_results(): protocol specific layer: external error: There is a tds protocol error. An invalid numeric precision was received."

CR:487784

CR Number:   487784 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.5.07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 26 Feb 2008 Fixed 5.5.08 01 Feb 2008 Fixed Description ORACLE ONLY: When RepAgent processes a "truncate table" on a temporary table, it errors with a java.lang.NullPointerException. Workaround Description  use "pdb_skip_op add, <RBA>" to skip the transaction at primary.

CR:487798

CR Number:   487798 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   NA Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Feb 2008 Fixed Description Add unique index on partition id in table rs_diskpartitions.

CR:487802

CR Number:   487802 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   NA Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Feb 2008 Fixed Description All partitions should be listed in the RS log at startup. Workaround Description  None.

CR:487809

CR Number:   487809 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Solaris Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.08 01 Feb 2008 Fixed 5.6.02 26 Feb 2008 Fixed Description ORACLE ONLY: A rogue rollback command is sent to Replication Server, which causes the Replication Server to fail with error "#9022 DIST Cannot deliver a command from DS.DB since no transaction is open."

CR:487830

CR Number:   487830 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/UDB Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 26 Feb 2008 Fixed 5.5.08 01 Feb 2008 Fixed 5.5.08 01 Feb 2008 Fixed Description UDB ONLY: Replication Agent incorrectly enables the owner mode based on the owner qualified replicate table name.

CR:487870

CR Number:   487870 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Solaris Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.08 01 Feb 2008 Fixed 5.6.02 26 Feb 2008 Fixed 5.5.08 25 Jul 2008 Fixed Description ORACLE ONLY: The Replication Agent fails with error: "java.lang.RuntimeException: Invalid supplemental data format" when a table has been defined with "rowdependencies" enabled.

CR:487944

CR Number:   487944 Product Name:   Sybase Replication Server Product Component:   RMA Status:   Closed OS:   Generic Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 20 Aug 2009 Presently Not Targeted For Any Future Release Of This Product Description RMServices three-tier Replication System management console in Sybase Central does not support users who have the '@' character in the password. Workaround Description  Use users who do NOT have '@' chars in passwords.

CR:487999

CR Number:   487999 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) 5.6.02 28 Dec 2007 Fixed 5.5.08 01 Feb 2008 Fixed Description ORACLE ONLY: Automatic generated replication definitions for tables containing char and varchar2 data types are generated incorrectly if the primary database is double byte character set. The data sent to Replication Server causes the Replication Server to fail with an error "ORA-12899: value too large for column". Workaround Description  delete auto_created repdef, and then create a repdef manually,(change ch column length in repdef to 10), data can be replicated correctly: create replication definition ra$0xc9dd_test1 with primary at oracle10g_ra.or10gpdb with all tables named 'qafuser'.'test1' ( "id" rs_oracle_decimal, "ch" char(10) ) primary key( "id" ) searchable columns( "id" ) send standby all columns replicate minimal columns

CR:488021

CR Number:   488021 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Repository Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.09 26 Feb 2008 Fixed 5.6.03 03 Apr 2008 Fixed Description LINUX ONLY: Command rasd_restore may fail with an error message "Could not stop database <.../repository/myra.db>."

CR:488166

CR Number:   488166 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   NA Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 24 Mar 2008 Fixed Description Change RS code to remove the character case restriction for column named seq in rs_threads. Workaround Description  Redo function strings and calls for rs_threads tables that involve column seq.

CR:488346

CR Number:   488346 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   LTI Driver Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 26 Feb 2008 Fixed 5.5.08 01 Feb 2008 Fixed 5.6.02 22 May 2008 Added to user documentation Description Replication Agent command rs_create_repdef failed to include the owner name in the "with replicate table named" clause.

CR:488347

CR Number:   488347 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) 29 Sep 2009 Fixed 12 Oct 2009 Fixed 12 Oct 2009 Fixed Description UDB ONLY: Replication Agent incorrectly sends the "character for bit data" column in character values to Replication Server.

CR:488391

CR Number:   488391 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.5.10 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 26 Feb 2008 Fixed 5.5.08 01 Feb 2008 Fixed Description ORACLE ONLY: Replication Agent does not process the rollback for an off-row LOB update. The LOB value is applied when it should be rolled back.

CR:488429

CR Number:   488429 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 26 Feb 2008 Fixed 5.5.08 01 Feb 2008 Fixed Description ORACLE ONLY: NULLPointerException on DDL create table and create user command processing causes Replication Agent to go to ADMIN state.

CR:488462

CR Number:   488462 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) 5.6.02 26 Feb 2008 Fixed 5.5.08 01 Feb 2008 Fixed Description ORACLE ONLY: Automatic generated replication definitions for tables containing CLOB data type are generated incorrectly if the primary database is double byte character set.

CR:488531

CR Number:   488531 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.5.07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.08 01 Feb 2008 Fixed Description ORACLE ONLY: If parameter "log_archive_format" of Oracle primary database contains "%T" or "%S%", Replication Agent will fail to find archive log files under "pdb_archive_path" directory. Workaround Description  Do not use upper letter in Oracle parameter "log_archive_format"

CR:488555

CR Number:   488555 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) 5.6.03 03 Apr 2008 Fixed Description ORACLE ONLY: Replication Agent generates an incorrect Log Transfer Language (LTL) for the Data Manipulation Language (DML) command on the Oracle Cluster Table.

CR:488568

CR Number:   488568 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Solaris Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.08 01 Feb 2008 Fixed 5.6.02 26 Feb 2008 Fixed Description ORACLE ONLY: Replication fails with error: "IllegalStateException: No applicable system object found for DDL command".

CR:488681

CR Number:   488681 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   AIX Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.08 01 Feb 2008 Fixed 5.6.03 03 Apr 2008 Fixed Description ORACLE ONLY: Replication Agent fails while processing DDL commands generated during upgrade of Oracle from release 10.2.0.1.0 to 10.2.0.3.0

CR:488701

CR Number:   488701 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Admin Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 26 Feb 2008 Fixed 5.5.09 05 May 2008 Fixed Description MICROSOFT SQL SERVER AND UDB ONLY: pdb_setreptable command output does not display the owner name information in the replicate name column.

CR:488714

CR Number:   488714 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.5.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.08 01 Feb 2008 Fixed 5.6.02 26 Feb 2008 Fixed 5.3.08 30 Aug 2008 Fixed 5.5.08 15 Aug 2008 Fixed Description ORACLE ONLY: Command ra_truncatearticles removes Articles that are still in use.

CR:488734

CR Number:   488734 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   unknown Original Version:   12.6.0.5306P9 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 26 Feb 2008 Fixed 5.3.08 30 Aug 2008 Fixed 5.5.08 01 Feb 2008 Fixed Description ORACLE ONLY: Replication Agent sends an empty LTL to Replication Server for an insert into a table containing more than 128 columns.

CR:488751

CR Number:   488751 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   AIX Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.09 26 Feb 2008 Fixed 5.6.03 03 Apr 2008 Bundled Request Description ORACLE ONLY: The Replication Agent stops replicating while processing a DDL command for a new user defined type. The error is similar to: "IllegalStateException: Could not find data type with TOID".

CR:488752

CR Number:   488752 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   AIX Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.10 05 May 2008 Fixed 5.6.03 03 Apr 2008 Fixed Description ORACLE ONLY: Replication Agent fails with the following errors while attempting to process a DDL command for a type object: "Failed to create a user defined data type." "SybSQLException: ASA Error -195: Column 'objectName' in table 'oracleObject' cannot be NULL"

CR:488768

CR Number:   488768 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Admin Status:   Closed OS:   Generic Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Jan 2009 Fixed Description ORACLE ONLY: New immediate option for marking tables: "pdb_setreptable tablename, mark, immediate", Marked objects with immediate option may have the capability of being replicated prior to truncation point. But the schema of the objects to be marked with immediate option must not be changed from replication start point to now. Old marked information would be removed, which could result in previoulsy unreplicated records being replicated. Only curent schema is used for all records. Only existing marked objects can be changed to 'immediate'.

CR:488770

CR Number:   488770 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Solaris Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.08 01 Feb 2008 Fixed 5.6.03 03 Apr 2008 Fixed Description ORACLE ONLY: Replication Agent failed with UnsupportedOperationException error while trace flag RASDTRC was enabled.

CR:488829

CR Number:   488829 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Solaris Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description RS 12.6 may occasionally crash showing stack-trace with ex_disconnect_handler() -> _sync_drop_element() -> ll_del(). Workaround Description  None known.

CR:488871

CR Number:   488871 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Solaris Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.08 01 Feb 2008 Fixed 5.6.03 03 Apr 2008 Fixed Description ORACLE ONLY: Maintenance user transactions are not filtered because the user assigned to the transactions is the 'SYS' user.

CR:489010

CR Number:   489010 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.5.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.7.01 27 Oct 2008 Fixed 5.8.00 27 Oct 2008 Fixed 5.5.23 06 Jan 2009 Fixed Description ORACLE ONLY: Replication Server ignores the error: "ORA-04043: object xxx does not exist for replicate database." The script to create error class oracle_error_class has been updated to correctly stop replication when this error occurs. If the error class oracle_error_class already exists, you can issue the following commands in Replication Server to apply the same modification: assign action stop_replication for oracle_error_class to 4043 go

CR:489105

CR Number:   489105 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed Description MICROSOFT SQL SERVER ONLY: A NullPointerException error is thrown when replicating DDL transaction whose name size is not multiple of 4 bytes. For example: begin transaction a create user/table commit

CR:489114

CR Number:   489114 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.5.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.09 26 Feb 2008 Fixed Description ORACLE ONLY: Command pdb_date fails with an exception when the OS locale is set to Chinese.

CR:489206

CR Number:   489206 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/UDB Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed Description UDB ONLY: pdb_xlog remove command generates an incorrect error message if a stored procedure not created by Replication Agent but owned by the pds_username exists in the database: Replication Agent Stored Procedures { names } in schema { pds_username } have not been dropped from the database. Please drop the procedures,and rerun the pdb_xlog remove command.

CR:489254

CR Number:   489254 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 01 Jan 2009 Duplicate Description Monitor & Counter information cannot be collected to RSSD Workaround Description  do not use RSSD option

CR:489322

CR Number:   489322 Product Name:   Rep Serv Commands Ref Product Component:   Rep Serv Commands Ref Status:   Closed OS:   NA Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 13 May 2008 Fixed Description Table 3-23 and 3-24 are identical.

CR:489368

CR Number:   489368 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Admin Status:   Closed OS:   Generic Original Version:   5.6.03 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed 5.5.10 05 May 2008 Fixed Description MICROSOFT SQL SERVER AND UDB ONLY: Replication Definition Not Found Exception will be thrown when a table with a case sensitive name is marked for replication.

CR:489422

CR Number:   489422 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   AIX Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.09 26 Feb 2008 Fixed 5.6.03 03 Apr 2008 Fixed Description ORACLE ONLY: The Replication Agent stops replicating after reporting error: "TransactionException: Transaction context not found for commit operation".

CR:489521

CR Number:   489521 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   all Original Version:   tyresias Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Jan 2008 Duplicate Description From documentation "When you delete a version from a configuration you do not delete the document version from the repository, you detach it from the configuration." It does delete the document version in the repository if the document version you removed in configuration is the current version in the repository.

CR:489557

CR Number:   489557 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 17 May 2010 Fixed Description stack with i386_lock and sqm_get_queue_handle Workaround Description  Start back up the Rep Server and drop the conneciton again. This time, the RS should stay up and not report an error.

CR:489726

CR Number:   489726 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) 5.6.02 11 Feb 2008 Fixed 5.5.09 26 Feb 2008 Fixed Description ORACLE ONLY: When attempting to verify or create an instance using a response file against Oracle 10g, Replication Agent response file verification will fail with "ERROR: Automatic archiving of redo logs is not enabled." if the "log_archive_start" parameter in the primary database is set to false. Workaround Description  SQL> show parameter log_archive_start NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ log_archive_start boolean FALSE If the result is 'false', try this to set it to true. SQL> alter system set log_archive_start=true scope=spfile; Then restart the database.

CR:489780

CR Number:   489780 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Solaris Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.09 26 Feb 2008 Fixed 5.6.03 03 Apr 2008 Fixed 13 Feb 2008 Duplicate Description ORACLE ONLY: Replication Agent fails with error: "TransactionException: Could not set article for operation" for a table that contains a VARRAY column.

CR:489820

CR Number:   489820 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed 5.6.03 03 Apr 2008 Fixed 5.6.03 03 Apr 2008 Fixed 07 Oct 2008 Fixed Description MICROSOFT SQL SERVER ONLY: Sybfilter fails to start up on 64-bit Windows Vista with error "ERROR: Could not connect to filter: 0x80070002". Workaround Description  Reboot machine, press F8 and select 8.Disable Driver signature Enforcement. Or enter system under debug mode.

CR:490235

CR Number:   490235 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) 5.8.00 05 Mar 2009 Fixed Description ORACLE ONLY: When the Replication Agent has been configured to get Oracle or Automatic Storage Management (ASM) connection information from a tnsnames.ora file, the pdb_xlog init may fail with an error indicating the Oracle instance name cannot be found.

CR:490295

CR Number:   490295 Product Name:   Repository Product Component:   Repository Status:   Open OS:   all Original Version:   tyresias Fixed Version Build Resolution Date Closure Code (If Appropriate) Description During consolidation using branch mode, the version number is based on the latest frozen version, not the version you extracted.

CR:490338

CR Number:   490338 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.7.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.7.00 03 Jul 2008 Fixed 5.6.07 06 Jul 2008 Fixed 5.5.17 06 Jul 2008 Fixed Description ORACLE ONLY: During processing of a resource file, Replication Agent lists only the values of parameters that are invalid. The names of the parameters that are invalid are missing.

CR:490344

CR Number:   490344 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Installation Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.8.00 09 Mar 2009 Fixed 5.7.15 26 May 2009 Fixed Description When using a response file to create, start and initialize an instance, the error messages are not clear about how to restart.

CR:490346

CR Number:   490346 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Installation Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 30 Jan 2008 Duplicate Description RAX checks log_archive_start in Oracle 10g even though the parameter is obsolete and Oracle does not have the correct setting. Workaround Description  Verify that log_archive_start = true by the following: SQL> show parameter log_archive_start NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ log_archive_start boolean FALSE If the result is 'false', try this to set it to true. SQL> alter system set log_archive_start=true scope=spfile; Also see Quick Start Guide "To verify Oracle 10g flashback feature is disabled"

CR:490361

CR Number:   490361 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed Description MICROSOFT SQL SERVER ONLY: Replication Agent does not replicate an ntext column in the correct byte order when ltl_big_endian_unitext parameter is set to true and lr_ntext_byte_order is set to little. The ntext column is incorrectly sent in little endian byte order to Replication Server. Workaround Description  Set ltl_big_endian_unitext to false and lr_ntext_byte_order to 'big' will make the ntext column sent out in byteOrder big endian

CR:490704

CR Number:   490704 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.5.07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.09 26 Feb 2008 Fixed 5.6.03 03 Apr 2008 Fixed Description ORACLE ONLY: The Replication Agent sends data in an incorrect order, causing Replication Server to ignore some operations. Workaround Description  *** Monday, February 04, 2008 12:57:33 *** sshepher *** The current sort buffer used by RAO to handle these ordering issues is controlled by hidden configuration parameter lr_sort_buffer_size, whose default size is 20. In order to resolve the case presented here, the value of lr_sort_buffer_size needs to be increased to 4000. (nearly 4,000 records reported by trace OPSCANDBG between logging of OQID: 000000000004c61e000f and OQID: 000000000004c61e0001. To be more certain for this customer, I would recommend setting lr_sort_buffer_size to 5000, to provide more insurance that we are likely to order these items correctly.

CR:490742

CR Number:   490742 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.5.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.09 26 Feb 2008 Fixed 5.6.03 03 Apr 2008 Fixed Description ORACLE ONLY: Replication Agent stops replicating after logging an error similar to: "Error. Index offset calculation produced a negative value."

CR:490961

CR Number:   490961 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Solaris Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.09 26 Feb 2008 Fixed 5.6.03 03 Apr 2008 Fixed Description ORACLE ONLY: A CLOB value whose default value is EMPTY_CLOB() is incorrectly replicated as a null value.

CR:491159

CR Number:   491159 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   12.5.0.306P7 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.5.0.308P9 25 Feb 2008 Fixed Description ORACLE ONLY: Replication Agent fails with a SQL "numeric overflow error" when restarting replication and the transaction id value is greater than the maximum allowed in an integer.

CR:491319

CR Number:   491319 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   5.6.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed 5.5.11 05 May 2008 Fixed Description Command pdb_date failed with exception "Could not find Resource Bundle containing index: INVALID_DATE_TIME_STRING".

CR:491430

CR Number:   491430 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed 5.6.03 03 Apr 2008 Fixed Description ORACLE ONLY: Oracle cluster database (RAC) replication performance degrades significantly if one or more cluster database instances is down.

CR:491541

CR Number:   491541 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Solaris Original Version:   15.0.0.5507P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.17 24 Jul 2008 Fixed 5.6.07 25 Jul 2008 Fixed 5.7.00 25 Jul 2008 Fixed 5.6.07 28 Jul 2008 Fixed 5.7.00 28 Jul 2008 Fixed Description ORACLE ONLY: A table can not be marked for replication if any of the columns has a datatype that can not be replicated. Replication Agent command pdb_setreptable has been changed to allow marking of tables that contain column datatypes that are not supported for replication. This change allows the supported column data to be replicated, instead of excluding the entire table from replication. The "force" keyword option can be added to the command syntax for any pdb_setreptable command "mark" request to force the Replication Agent to mark the table for replication. When a table has been marked for replication using the pdb_setreptable command "mark" and "force" keywords, only columns with supported datatypes will be replicated. Any column with an unsupported datatype will be excluded (no data for those columns with unsupported datatypes will be sent to Replication Server). Changes to command pdb_setreptable: Syntax changes: To mark a specified table: pdb_setreptable tablename, mark[, owner][, force] To mark a specified table for replication with a replicated name: pdb_setreptable tablename, repname, mark[, owner] [, force] Parameter changes: force A keyword that refers to either a mark or unmark operation. Note: The combination of the "mark" and "force" keywords with the pdb_setreptable command is only valid for Oracle. When the "force" keyword follows the "mark" keyword, the pdb_setreptable command will allow a table that contains one or more columns with unsupported datatypes to be marked for replication. No data for the unsupported columns will be sent to Replication Server. As a result, any replicate table must have a suitable default value defined for the unsupported columns, as no data will be received by the replicate database for inserts into those unsupported columns. The force keyword can not be used in combination with the "all" and "mark" keywords. Tables with unsupported datatypes must be individually marked using the pdb_setreptable command and the "force" keyword. In addition, tables with unsupported datatypes are not automatically marked when configuration property "pdb_automark_tables" is true. Tables with unsupported datatypes must be individually marked using the pdb_setreptable command and the "force" keyword. Note: If a replication definition is created using command rs_create_repdef, for a table that was marked using the "force" keyword, only columns with supported datatypes will be listed in the replication definition. Any column with an unsupported datatype will be excluded from the replication definition. Usage changes: Oracle Only: If a table contains a column with a datatype that can not be supported for replication, the pdb_setreptable command using the "mark" keyword may fail with an error similar to: Command <pdb_setreptable> failed - Table <MYTABLE> could not be marked because: The table contains an unsupported data type. To force the table to be marked, excluding the unsupported datatype columns from replication, add the "force" keyword to the pdb_setreptable command.

CR:491669

CR Number:   491669 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Open OS:   MVS Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Enhance RA DB2 so that latency of transactions from the mainframe can be measured.

CR:491693

CR Number:   491693 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Admin Status:   Closed OS:   Generic Original Version:   5.6.03 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed Description MICROSOFT SQL SERVER AND ORACLE ONLY: When a table is marked for replication, then dropped and recreated, the Replication Agent incorrectly displays the deleted table's mark status.

CR:491883

CR Number:   491883 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   all Original Version:   tyresias Fixed Version Build Resolution Date Closure Code (If Appropriate) 17 Mar 2008 Fixed 31 Mar 2008 Fixed Description Delete mapping between CDM Entity attribute and OOM Class attribute, repository update fails: "The consolidation of the document has been cancelled." Delete mapping between CDM Entity and OOM Class, repository update ends up with: "Unexpected error while executing the following action: Removing Link between object External Inheritance Attribute Mapping and object External Inheritance Mapping '..Mapping_1' The consolidation of the document has been cancelled."

CR:492046

CR Number:   492046 Product Name:   Mirror Replication Agent Product Component:   MRAgent/ASE Status:   Closed OS:   AIX 5.2 Original Version:   15.0.0.5507P4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.10 05 May 2008 Fixed 5.7.00 30 Aug 2008 Fixed Description ASE ONLY: The Replication Agent fails to process a drop table command for ASE release 12.5.4 when running on an AIX platform, with error "ArrayIndexOutOfBoundsException: 0"

CR:492048

CR Number:   492048 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed 5.5.11 05 May 2008 Fixed Description ORACLE ONLY: The Replication agent system log has warning messages describing operations that are skipped because either a session id or matching transaction context was not found and primary database changes are not getting replicated. Workaround Description  If the Replication Agent truncation mode is configured to "locator_update" or "interval", session repository truncation occurs at the same time as log truncation. To work around this problem, change the truncate mode to "command." Please note that re-materialization of the replicate database may be necessary in order to bring the replicate database into a consistent state with the primary.

CR:492088

CR Number:   492088 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.6.03 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed 5.5.10 05 May 2008 Fixed 5.6.03 03 Apr 2008 Fixed 5.5.10 05 May 2008 Fixed Description ORACLE ONLY: Replication Agent fails to create a replication definition if the primary key column in a table contains an Oracle NUMBER data type without any precision and scale. The automatic generated replication definition will omit the primary key for the "NUMBER" column. Workaround Description  For this table, repdef can be created: create table qaf_CR491130 ("SNAP_ID" NUMBER , "DBID" INT NOT NULL ENABLE , "TS#" NUMBER , "OBJ#" INT NOT NULL ENABLE , "DATAOBJ#" INT, "OWNER" VARCHAR2(30) NOT NULL ENABLE, "OBJECT_NAME" VARCHAR2(30) NOT NULL ENABLE, "SUBOBJECT_NAME" VARCHAR2(30) , "PARTITION_TYPE" VARCHAR2(8) , "OBJECT_TYPE" VARCHAR2(18) , "TABLESPACE_NAME" VARCHAR2(30) NOT NULL ENABLE, "INDEX_TYPE" VARCHAR2(27), "BASE_OBJ#" NUMBER , "BASE_OBJECT_NAME" VARCHAR2(30) , "BASE_OBJECT_OWNER" VARCHAR2(30) , CONSTRAINT "CR490742_PK" PRIMARY KEY ("DBID", "OBJ#", "DATAOBJ#") )

CR:492154

CR Number:   492154 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.5.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.10 05 May 2008 Fixed 5.6.03 03 Apr 2008 Fixed Description ORACLE ONLY: The Replication Agent fails with a NullPointerException, with a reference to LTLFormatter.compareFields.

CR:492186

CR Number:   492186 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Reader Status:   Closed OS:   Generic Original Version:   15.0.0.5508P5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.9.00 12 Aug 2009 Fixed Description ORACLE ONLY: Two new Replication Agent commands have been added that allow the user to obtain detailed information about database operations and database operations in a transaction in order to provide additional trouble shooting information. Command ra_helpop Description: Command ra_helpop displays database and Replication Agent information for a specified operation in order to help trouble shoot a failed operation, or transaction. The time the operation executed, the user that executed the operation, the object name and id, operation type (i.e. insert, update, or delete), if the object is marked for replication, and other database specific information is displayed. If the Oracle script $ORACLE_HOME/rdbms/admin/dbmslm.sql has not been installed at the primary database, an error will be reported indicating it must be installed in order for the ra_helpop command to properly operate. If the new permissions that must be granted to the "pds_username" are not granted at the time ra_helpop is executed, an error will be reported indicating the following permission's must be granted before the ra_helpop command will properly work: EXECUTE_CATALOG_ROLE TO PDS$USER; SELECT ON V$LOGMNR_CONTENTS TO PDS$USER; SELECT ON V$LOGMNR_LOGS TO PDS$USER; SELECT ANY TRANSACTION TO PDS$USER; Syntax: ra_helpop "opid | locator" Opid - The Replication Agent operation id for a database operation Locator - The Replication Agent locator for a database operation Example 1: ra_helpop 0x0000.01542e48.0001:0001.000002dc.00000004.0010 This command returns operation information for an operation ID. Example 2: ra_helpop 0000000001544ada00060001000002de00000008001000000 000000000000000 This command returns operation information for a locator. Usage: The ra_helpop command returns the following information for the operation specified by a locator or operatin ID: - The Replication Agent operation id in the format: wrap.scn.subscn.thread.lsn.block.offset - The Oracle SCN for the operation as logged in a redo log file - The Oracle thread that executed the operation - The name of the user that executed the operation - The date and time the operation executed - The Oracle database id for the object - The Oracle object name - The operation type, i.e. INSERT, UPDATE, DELETE - YES if the object in the operation is marked for replication by the Replication Agent - The Oracle id for the transaction the operation is part of - The Oracle SQL that can be used to replay the operation - The Oracle SQL that will undo the operation - The Replication Agent command that will cause the operation to be skipped by the Replication Agent while replicating Command ra_dumptran Description: Command ra_dumptran dumps all operations for a specified transaction to an exclusive log file in order to help trouble shoot a failed operation, or transaction. The time the transaction was executed, the user that executed the transaction, the name of the log the transaction was dumped to, and additional database specific information is displayed as a result set. If the Oracle script $ORACLE_HOME/rdbms/admin/dbmslm.sql has not been installed at the primary database, an error will be reported indicating it must be installed in order for the ra_ dumptran command to properly operate. If the new permissions that must be granted to the "pds_username" are not granted at the time ra_ dumptran is executed, an error will be reported indicating the following permission's must be granted before the ra_ dumptran command will properly work: EXECUTE_CATALOG_ROLE TO PDS$USER; SELECT ON V$LOGMNR_CONTENTS TO PDS$USER; SELECT ON V$LOGMNR_LOGS TO PDS$USER; SELECT ANY TRANSACTION TO PDS$USER; Syntax: ra_dumptran "opid | locator" Opid - The Replication Agent operation id for a database operation Locator - The Replication Agent locator for a database operation Example 1: ra_dumptran 0x0000.01542e48.0001:0001.000002dc.00000004.0010 This command returns information for the begin operation in the transaction specified by an operation ID. Information for every operation in the transaction is written to a file in the Replication Agent log directory. The file is named with the prefix "XID" followed by the transaction ID and ".log". Example: $RAX_DIR/<INSTANCE_NAME>/log/ XID0005.002c.0000002c.log Example 2: ra_dumptran 0000000001544ada00060001000002de00000008001000000 000000000000000 This command returns information for the begin operation in the transaction specified by an locator. Usage: The ra_dumptran command returns the following information for the begin operation specified by a locator or operatin ID: - The Replication Agent operation id for the transactions begin operation in the format: wrap.scn.subscn.thread.lsn.block.offset - The Oracle SCN for the transactions begin operation as logged in a redo log file - The Oracle id for the transactions begin operation - The name of the user that executed the transaction - The date and time the transaction executed - The Oracle thread that transaction was executed on - The Replication Agent command that will cause the transaction to be skipped by the Replication Agent while replicating - The name of the file the transaction is written to The ra_dumptran command wtites the following information for for all operations in the transaction specified by a locator or operation ID: - The Oracle SCN for the operation as logged in a redo log file - The Oracle thread that operation was executed on - The Replication Agent operation id for the transaction begin operation in the format: wrap.scn.subscn.thread.lsn.block.offset - The Oracle id for the object the operation affected - The Oracle name of the object the operation affected - YES if the object in the operation is marked for replication by the Replication Agent, No if it is not marked for replication - The operation type, i.e. INSERT, UPDATE, DELETE - The Oracle SQL statement for the operation

CR:492210

CR Number:   492210 Product Name:   Sybase Replication Server Product Component:   RMA Status:   Closed OS:   Solaris Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 400 07 Apr 2008 Fixed 15.1 400 06 May 2008 Fixed Description Event trigger parameters are not being parsed by the RMS correctly. Parameters with embedded spaces are being separated and passed to the execution script as multiple arguments.

CR:492340

CR Number:   492340 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Generic Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed Description MICROSOFT SQL SERVER ONLY: pdb_get_columns command returns the column data type for varchar(max), nvarchar(max) and varbinary(max) incorrectly as text, ntext and image.

CR:492467

CR Number:   492467 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Generic Original Version:   5.6.03 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed 5.6.03 21 Nov 2008 Added to user documentation Description MICROSOFT SQL SERVER ONLY: Automatic generated replication definitions for tables containing ntext data type are incorrectly mapped to text data type.

CR:492671

CR Number:   492671 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.6.03 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.15 10 Jun 2008 Fixed 5.6.05 10 Jun 2008 Fixed 5.7.00 30 Aug 2008 Fixed Description ORACLE ONLY: Replication Agent fails with an error similar to "IllegalStateException: Could not concatenate chained operation because: Error processing record with supplemental data whose column index duplicates other data".

CR:492682

CR Number:   492682 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed 5.5.11 05 May 2008 Fixed Description ORACLE ONLY: IllegalStateException during log scanner log record sort comparison sends the Replication Agent to ADMIN state. Workaround Description  In some cases, resuming the Replication Agent may be sufficient. However, in those cases it is likely that the Replication Agent will hit the problem again in the future.

CR:492817

CR Number:   492817 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Microsoft Windows NT Original Version:   5.6.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed Description MICROSOFT SQL SERVER ONLY: Replication Agent throws a java.lang.NullPointerException error when replicating update text column value to NULL.

CR:493013

CR Number:   493013 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Generic Original Version:   5.6.03 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed Description MICROSOFT SQL SERVER ONLY: Replication Agent defines an incorrect 'XXXcheckobjects' table name in the Replication Agent system stored procedure 'XXXmark_'. Replication Agent defines the 'XXXcheckobjects' table using default xlog prefix value (ra_) instead using the value defined by the pdb_xlog_prefix parameter.

CR:493098

CR Number:   493098 Product Name:   Sybase Replication Server Product Component:   rs_init Status:   Open OS:   Linux Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description rs_init can change the local server name after creating Replication Agent. Workaround Description  Once the RA is set up, the alias name no longer has to be the local server. Do sp_config_rep_agent dname,'connect dataserver','realname' to allow both aliased names and regular server names to start up automatcally when the ASE server is started. Therefore, after the RA has been set up, do sp_helpserver. The local servername can be the real ASE servername. I would keep the alias name in the sysservers just as documentation.

CR:493103

CR Number:   493103 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.12 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.12 04 06 Aug 2008 Fixed Description Added two new commands, QUIESCE and RESUME.

CR:493353

CR Number:   493353 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.6.03 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.03 03 Apr 2008 Fixed 5.6.04 07 Apr 2008 Fixed Description ORACLE ONLY: Replication Agent doesn't return information for tables, procedures, functions, or sequences when using 'pdb_setreptable', 'pdb_setreproc', or 'pdb_setrepsequence' admin commands if the requested object has been dropped and re-created.

CR:493445

CR Number:   493445 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   NA Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.5 06 Jan 2010 Fixed 15.5 29 Dec 2009 Fixed Description Change RSSD to prevent locking on high volume RSs and cases where monitoring (RMA) is done. Workaround Description  Here is script done by customer to eliminate the full table scans: if exists(select name from sysobjects where name = 'rma_queue' and type = 'P') begin drop proc rma_queue end go create procedure rma_queue (@servername varchar(30) ) as set nocount on create table #subs (rawid binary(8), intid int) /* ** If this a byte-swap machine, swap the order of the last ** four bytes of the subid */ if (convert(int, 0x00000100) = 65536) insert #subs select rawid = subid, intid = substring(subid, 8, 1) + substring(subid, 7, 1) + substring(subid, 6, 1) + substring(subid, 5, 1) from rs_subscriptions else insert #subs select rawid = subid, intid = substring(subid, 5, 4) from rs_subscriptions create table #queues ( name varchar(255), q_number int, q_type int, q_state int, size int, saved int, detect_loss int, ignore_loss int, first_seg int, q_objid binary(8), q_objid_temp binary(8), xnl_large_msg varchar(9) NULL ) insert #queues select distinct dsname + '.' + dbname + '(Inbound)', number, 1, q.state, 0, 0, 0, 0, 0, 0, 0, '' from rs_queues q, rs_databases d where number = d.dbid and type=1 insert #queues select distinct isnull(convert(varchar(61), name), dsname+'.'+dbname)+'(Outbound)', number, 0, q.state, 0, 0, 0, 0, 0, 0, 0, '' from rs_queues q, rs_databases, rs_sites where number *= dbid and number *= id and type=0 insert #queues select distinct d.dsname+'.'+d.dbname+'(Materialization-'+sub.subname+')', number, q.type, q.state, 0, 0, 0, 0, 0, 0, 0, '' from rs_queues q, rs_subscriptions sub, rs_databases d, #subs where d.dbid=number and sub.dbid=d.dbid and #subs.rawid = sub.subid and #subs.intid = q.type and materializing=1 insert #queues select distinct d.dsname+'.'+d.dbname+'(Dematerialization-'+sub.subname+')', number, q.type, q.state, 0, 0, 0, 0, 0, 0, 0, '' from rs_queues q, rs_subscriptions sub, rs_databases d, #subs where d.dbid=number and sub.dbid=d.dbid and #subs.rawid = sub.subid and #subs.intid = q.type and dematerializing=1 /* 3/10/2008 - Mark Parsons RMS is causing deadlocks with RepServer while both processes are trying to access rs_segments. Also, there is no usable index on rs_segments for the queries in this stored proc. Changing rs_segments to datarows locking, and adding an index on rs_segments(q_number, q_type [,used_flag]), may help eliminate the deadlocks. But these steps should be tested/verified/implemented by Sybase as a long-term solution. In the meantime we'll put in a kludge to get us around the majority of deadlock possibilities. Let's pull a copy of rs_segments into a #temp table to help minimize chances of deadlocking with the RepServer. Also, go ahead and add an index to help with follow-on queries. */ -- minimize time required to pull data from rs_segments by -- creating #segments separately select q_number, q_type, logical_seg, used_flag into #segments from rs_segments where 1=0 insert #segments select q_number, q_type, logical_seg, used_flag from rs_segments create clustered index idx1 on #segments (q_number, q_type) with allow_dup_row update #queues set size = (select count(*) from #segments where #queues.q_number = #segments.q_number and #queues.q_type = #segments.q_type and used_flag > 0) update #queues set saved = (select count(*) from #segments where #queues.q_number = #segments.q_number and #queues.q_type = #segments.q_type and used_flag > 1) update #queues set detect_loss = detect_loss + (select count(*) from rs_oqid where #queues.q_number = rs_oqid.q_number and #queues.q_type = rs_oqid.q_type and valid = 1), ignore_loss = ignore_loss + (select count(*) from rs_oqid where #queues.q_number = rs_oqid.q_number and #queues.q_type = rs_oqid.q_type and valid = 2) update #queues set detect_loss = detect_loss + (select count(*) from rs_exceptslast where #queues.q_number = error_db and status = 1), ignore_loss = ignore_loss + (select count(*) from rs_exceptslast where #queues.q_number = error_db and status = 2) update #queues set first_seg = (select isnull(min(logical_seg),0) from #segments where #queues.q_number = #segments.q_number and #queues.q_type = #segments.q_type) /* Build the queue objid number to search for wide message flag in rs_config */ update #queues set q_objid = convert ( binary(4), q_number ) + convert ( binary(4), q_type ) /* Store a copy of the queue objid in case the bytes need to be reversed */ update #queues set q_objid_temp = convert ( binary(4), q_number ) + convert ( binary(4), q_type ) /* If this a byte-swap machine, reverse the objid */ if (convert(int, 0x00000100) = 65536) update #queues set q_objid = substring ( q_objid_temp, 8, 1 ) + substring ( q_objid_temp, 7, 1 ) + substring ( q_objid_temp, 6, 1 ) + substring ( q_objid_temp, 5, 1 ) + substring ( q_objid_temp, 4, 1 ) + substring ( q_objid_temp, 3, 1 ) + substring ( q_objid_temp, 2, 1 ) + substring ( q_objid_temp, 1, 1 ) update #queues set xnl_large_msg = (select charvalue from rs_config where rs_config.objid = #queues.q_objid and rs_config.optionname = 'sqm_xact_with_large_msg' ) update #queues set xnl_large_msg = 'shutdown' where xnl_large_msg = NULL select @servername, name, q_number, q_type, size, saved, convert(char(40), getdate(), 109), detect_loss, ignore_loss, first_seg, "DOWN", xnl_large_msg from #queues where q_number != 0 and q_state != 1 union all select @servername, name, q_number, q_type, size, saved, convert(char(40), getdate(), 109), detect_loss, ignore_loss, first_seg, "UP", xnl_large_msg from #queues where q_number != 0 and q_state = 1 /* Cleanup */ truncate table #queues truncate table #subs truncate table #segments drop table #queues drop table #subs drop table #segments go grant execute on rma_queue to rs_systabgroup

CR:493447

CR Number:   493447 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   NA Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Enhancement Request to make the presence of faded out message and reconnect message configurable.

CR:493452

CR Number:   493452 Product Name:   Sybase Replication Server Product Component:   InstallShield Status:   Closed OS:   Solaris Original Version:   15.0.1 ESD#3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 24 Jun 2010 Presently Not Targeted For Any Future Release Of This Product Description When installing Replication server ESDs over an existing installation, all modules are installed even if they were NOT selected for the original installation. Workaround Description  Delete unwanted files - dangerous and difficult.

CR:493530

CR Number:   493530 Product Name:   Repository Product Component:   Repository Status:   Open OS:   Windows XP Original Version:   telemaque Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Customer suggests to provide an option in interface Consolidation , the option allow to clean up local copy in the Workspace. Though PowerDesigner provides option - "Extract After consolidation", it is different to clean up the local copy.

CR:493594

CR Number:   493594 Product Name:   Repository Product Component:   Repository Status:   Open OS:   all Original Version:   tyresias Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Customer would like the ability to update a model in the repository in real time without the need of having to consolidate the model. Customer's text: Currently, we are working in a "disconnected" mode in PowerDesigner. We make our updates locally and consolidate with the respository. We would like the additional ability to work in a connected mode with the repository, thus enabling us to update the requirements in real-time when connected to the respository. This may require that we actually lock the requirement, update it and unlock it. In this connected mode, we would not need to consolidate since our updates would be applied directly to the model in the repository.

CR:493622

CR Number:   493622 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   HP-UX Original Version:   15.0.1 ESD#3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Apr 2008 Fixed 27 Mar 2008 Fixed 25 Jul 2008 Fixed Description The Replication Server may fail to shutdown after being issued the 'shutdown' command. This can occur if the Replication Server fails to terminate an associated 'dbltm' process. An associated 'dbltm' process is created when the Replication Server is configured to use an embedded RSSD and a route exists to a target Replication Server.

CR:493719

CR Number:   493719 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   NA Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 20 Mar 2008 Fixed Description Change RSSD scripts to make all binary columns that rely on the full length of the binary (e.g. rs_locater.qid, rs_lastcommit, etc.) be explicitly declared as 'not null' Workaround Description  alter the column qid in the table rs_locater, to 'not null'

CR:493723

CR Number:   493723 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   NA Original Version:   15.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Provide trace or configuration parameter that would allow DIST to skip commands automatically if "bad data" cannot be translated correctly by the DIST.

CR:493735

CR Number:   493735 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   NA Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6 ESD#10 03 Dec 2008 Fixed 15.1 ESD #1 17 Oct 2008 Fixed 15.1 ESD #1 23 Oct 2008 Duplicate 15.0.1 ESD #4 03 Dec 2008 Fixed Description When the Replication Server is sent corrupt data (e.g. when BCP is incorrectly used at the primary database), the Distributor thread successfully detects the corruption and terminates while the warm standby DSI thread fails to detect the corruption and replicates the corrupt data. Workaround Description  None at this time.

CR:493748

CR Number:   493748 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   15.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Mar 2008 Fixed 12 Jun 2008 Fixed Description The SySAM warning message that reports that Replication Server functionality will be disabled on a certain date is too vague. Specifically, the Replication Server functionality that will be disabled is not clearly defined. The SySAM warning message should explicitly state that the entire Replication Server will be disabled.

CR:494064

CR Number:   494064 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.5.17 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.5.17 16 Oct 2008 Fixed 5.7.01 16 Oct 2008 Fixed 5.7.00 03 Sep 2008 Presently Not Targeted For Any Future Release Of This Product 5.8.00 29 Oct 2008 Fixed Description ORACLE ONLY: Replication Agent generates replication definition containing incorrect column length for columns whose datatype is nchar, nvarchar or nvarchar2.