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

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

CR:390214

CR Number:   390214 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 001 09 Sep 2005 Fixed Description RBA not found with DataSharingOption=Single Workaround Description  Use the "none" option in a single member environment. The following combinations work: Log_identifier=DB0X <==== original value DataSharingOption=None <====change here DataSharingMember=DB3X <==== original value OR Log_identifier=DB3x <==== name of DB2 DataSharingOption=None <====change here *DataSharingMember=DB3X <==== comment out

CR:391024

CR Number:   391024 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   5.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.0.01 07 Oct 2005 Fixed 5.1.00 07 Oct 2005 Fixed Description Be sure that the system default charset on the machine on which RepAgent is running is the same as that of the primary database. Sometimes this is insufficient and you need to set it within the RepAgent run script(s): Edit the various RepAgent run scripts to uncomment the line(s) for RA_JAVA_DFLT_CHARSET and set the value to the Java (not Sybase) name of the default charset (note that the charset name is case sensitive). The following examples set the default charset for RepAgent to Cyrillic: Windows (should be all on one line): if %RA_JAVA_DFLT_CHARSET%. == . set RA_JAVA_DFLT_CHARSET=Cp1251 Unix: if [ $RA_JAVA_DFLT_CHARSET. = . ] then RA_JAVA_DFLT_CHARSET=ISO8859_5 export RA_JAVA_DFLT_CHARSET echo " " fi

CR:391236

CR Number:   391236 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 NULL and empty string not supported in where clause on subscription. rs_helpsub displays where clause incorrectly. Workaround Description  None....according to case 10998998, one cannot predicate on NULL value in 11.5.1, 12.0 and 12.5

CR:391658

CR Number:   391658 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Unknown Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Enhancement request to have certain Rep Server Auditing feature

CR:391820

CR Number:   391820 Product Name:   Rep Serv Commands Ref Product Component:   Rep Serv Commands Ref Status:   Closed OS:   all Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 12 Jan 2006 Fixed Description Requirement of a unique identifier for text, image, and rawobject replication, should be emphasized in the text/image areas of the manuals.

CR:392001

CR Number:   392001 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Reader Status:   Closed OS:   Generic Original Version:   5.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.6.02 08 Feb 2008 Fixed Description System log messages regarding transaction log truncation are inaccurate and numerous.

CR:392281

CR Number:   392281 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   LTI Driver Status:   Closed OS:   NA Original Version:   5.1.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.00 31 Oct 2005 Fixed 5.2.00 20 Jan 2006 Fixed Description LTI trace message "LTI received request to start replication" is misspelled.

CR:392336

CR Number:   392336 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.0 12 Jan 2006 Fixed Description Sentence referring to Rep Agent in 6th and 7th bullet under Usage for alter logical connection is incorrect and if kept, refers to the Distributor.

CR:392433

CR Number:   392433 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Reader Status:   Closed OS:   Generic Original Version:   12.5.0.3021P1-ONE_OFF Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.5.0.3022P2-ONE_OFF 08 Jun 2005 Fixed 12.5.0.304P3 04 May 2006 Fixed 21 Feb 2006 Not a Bug Description When the LTI inbound queue is full and a replication error occurs, the LogReader SenderThread does not shut down properly, causing LTL to be sent out of order to RepServer.

CR:392667

CR Number:   392667 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   HP-UX Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Sep 2006 Duplicate Description RS reports "Error from unpacker or parser" when processing trasactions on a MSA connection. If connection is resumed parser will read the transaction OK and no transactions need to be skipped.

CR:392715

CR Number:   392715 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 Mar 2010 Presently Not Targeted For Any Future Release Of This Product Description ASE Message 4966 needs RS errorclass default changed from STOP to IGNORE

CR:392728

CR Number:   392728 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   HP-UX Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Feature request to optimize/speed up queries in rsupgr.sql for upgrading RSSD.

CR:392825

CR Number:   392825 Product Name:   RepAgent for MVS Product Component:   RepAgent for MVS - DOC Status:   Closed OS:   MVS Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 003 07 Jul 2005 Fixed Description When there are a lot of rows in LTMOBJECTS, RA may take a while to start up. This related to the time it takes to load the internal table from LTMOBJECTS, SYSTABLES and SYSCOLUMNS. This is dependent on DB2 performance.

CR:393407

CR Number:   393407 Product Name:   Repository Product Component:   Repository Status:   Open OS:   Windows 2000 Original Version:   chronos Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Tested and reproduced with PD 10.1.0.1169 EBF7 This is a new feature request only: Today, even setting Tools - General options-Repository-Merge Document to false, when customer extracts a model, the Merge Document is still available for checking. Customer would like this option to be disabled since a General Repository option (Merge Document) was changed.

CR:393713

CR Number:   393713 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Linux Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 26 Jul 2005 Fixed 26 Jul 2005 Fixed Description If the tempdb log of the ASE hosting the RSSD is full when Replication Server is starting, Replication Server may core dump.

CR:393861

CR Number:   393861 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   NA Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Feature Request for RS to provide command like ASE's "sp_listener"

CR:394043

CR Number:   394043 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 27 Jun 2005 Fixed 15.0 27 Jun 2005 Fixed 15.0 27 Jun 2005 Failed Description If a replicated target returns Repserver an error message longer than 800 bytes, Repserver may hang or crash due to memory corruption. Workaround Description  Assign the error number to an action of 'ignore'. DSI will be suspended after receiving the error message. Resume DSI with skip transaction.

CR:394345

CR Number:   394345 Product Name:   RepAgent/ASA Product Component:   Replication Agent Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3228 24 Nov 2005 Fixed Description The ASA RepAgent, and SQL Remote for ASE, would have crashed at startup on Red Hat Enterprise Linux versions 3 and 4. This was due to the fact that the Open Server/Open Client libraries, version 12.5 that was shipped with ASA, did not support these distributions. This has been fixed by installing a newer version of the Open Server/Open Client libraries, version 12.5.1, that is certified for Red Hat Enterprise Linux versions 3 and 4.

CR:394601

CR Number:   394601 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 Aug 2006 Fixed 15 Aug 2006 Fixed 15 Aug 2006 Fixed Description "map to" feature in "create replication definition" does not work when mapping to binary datatype.

CR:394730

CR Number:   394730 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 19 Jul 2005 Fixed Description On non-datasharing DB2s, the rollback qid does not match the qid of the command. Workaround Description  None at this time other than do not do transactions that generate rollbacks.

CR:394844

CR Number:   394844 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 01 05 Aug 2009 Fixed Description New command to change API_QID_request_interval. "F RAGENT,C,APIQIDRI=value"

CR:395437

CR Number:   395437 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   LTI Driver Status:   Closed OS:   NA Original Version:   5.1.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.1.00 07 Oct 2005 Fixed Description LTI loads database-level repdefs only the first time a start replication is requested. From that point on, the database-level repdefs are never refreshed, so any new or altered database-level repdefs are ignored until the Replication Agent is stopped and re-started.

CR:395464

CR Number:   395464 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Generic Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Create a mainframe DB2 class that can be inherited and acts the same way as the other heterogeneous function string classes. Workaround Description  If customer is not currently using the rs_db2_function_class, using SQL, change the RSSD so that the class has a parent class of the rs_default_function_class. update rs_classes set parent_classid = 0x0000000001000003 where classname = "rs_db2_function_class" On my RSSD, select * from rs_classes has the following two rows: rs_db2_function_class 0x0000000001000004 F 0 1 0x0000000001000003 rs_default_function_class 0x0000000001000003 F 0 1 0x0000000000000000

CR:395498

CR Number:   395498 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Generic Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description rs_delexceptions to delete a range of entries Workaround Description  delete all from rs_exceptshdr delete all from rs_exceptscmd delete all from rs_exceptslast delete rs_systext where texttype = 'C'

CR:395679

CR Number:   395679 Product Name:   Sybase Replication Server Product Component:   rsmclient Status:   Closed OS:   Microsoft Windows Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 Aug 2009 Presently Not Targeted For Any Future Release Of This Product Description Displaying a subscription that was created on a RS that is not included in the RSM environment, results in closing of Sybase Central window. Workaround Description  Only display subscriptions for a RS where the RS is known to this RSM environment.

CR:395979

CR Number:   395979 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 005 26 Oct 2005 Fixed Description For DB2 6.1, do the following: In RA.LINKLIB, rename LTMINFO to LTMINFO7. Rename LTMINFO6 to LTMINFO. In the PDRBIND job, change the member name from LTMINFO to LTMINFO6 and run the job. Workaround Description  I changed the last 2 bytes of first line from X'D5D2' to X'00C9' in DBRMLIB LTMINFO. I could execute the PDRBIND. [Before] DBRM...~DWILCOX LTMINFO .妥;. Q..B. .....................................1.. NK CCDD000ACECDCDE4DEDCDCD419B509DD10C280000000000000000000000000000000000000F008DD 4294000046933670334956607E6ECFF8102202000000000000000000000000000000000000100052 [After] DBRM...~DWILCOX LTMINFO .妥;. Q..B. .....................................1.. .I CCDD000ACECDCDE4DEDCDCD419B509DD10C280000000000000000000000000000000000000F0080C 4294000046933670334956607E6ECFF8102202000000000000000000000000000000000000100009

CR:396180

CR Number:   396180 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   all Original Version:   chronos Fixed Version Build Resolution Date Closure Code (If Appropriate) 20 Jul 2005 Fixed 09 Sep 2005 Fixed Description Even if an user has only the read permission on a package, it is possible to consolidate an activity diagram with a new sub-object. Steps to reproduce New Activity diagram 2 packages P1 P2 In P1 diagram D1 1 activity : A1 In P2 diagram D2 1 activity A2 decompose the activity in the new diagram D3 add a new activity A3 Consolidate the model as ADMIN In the repository : new User : U1 On P1 : permission add user U1 full permission copy permission to all children on P2 : permission add U1 : read copy permission to all children Disconnect ADMIN and connect U1 Extract the model In P1 add a new activity A11 in P2 D2 add a new activity A22, in D3 (sub-diagram) add a new activity : A33 Consolidate with update got a warning : which is correct Merge windows, have a look it is possible to add A11 which is correct It is not possible to add A22 which is correct But have a look at the diagram D2, it is possible to add A33 which is not correct click OK check the repository : A33 has been added in P2

CR:396183

CR Number:   396183 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   Windows 2000 Original Version:   penelope Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Jul 2005 Fixed 31 Aug 2005 Fixed Description Repository Update script (from v.9.5.2 to 11.1.0) problem. After upgraded repository, the PDM models having views will not consolidate into the updated repository. Get following error consolidating to Ms Sql Server 2000 repository db: [Microsoft][ODBC Driver][Microsoft Sql Server] syntax error converting the varchar value materialized to a column of data type integer. SQLSTATE = 22005. Get the following error consolidating to ASA 9.0.2 repository db: [Sybase][ODBC Driver][Adaptive Server Anywhere]Cannot convert MATERIALIZED to a int SQLSTATE = 07006 note: it appears to be a datatype (int to varchar (254))change on the PMPDMTABL.otyp and PMPDMVIEW.otyp column between the v. 9.5.2 repository creation script and 11.1.0 repository update/creation script.

CR:396842

CR Number:   396842 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 Jul 2006 Fixed 11 Jul 2006 Fixed 11 Jul 2006 Fixed 17 Jul 2006 Fixed 17 Jul 2006 Fixed 17 Jul 2006 Fixed Description Resume distributor command should not raise an error, it should provide an approriate message not a fatal error.

CR:397307

CR Number:   397307 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 Thread dALARM( ) infected with signal 10 when replicating purge process Workaround Description  Start back up the RS

CR:397504

CR Number:   397504 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 Provide trace to show why a transaction was ungrouped.

CR:397618

CR Number:   397618 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   all Original Version:   penelope Fixed Version Build Resolution Date Closure Code (If Appropriate) 17 Aug 2005 Fixed 18 Aug 2005 Fixed 31 Aug 2005 Fixed Description Pd 10.1 ebf 11 Unexpected error while executing the following action: Changing value of attribute Source Text Offset of object PD 11 and PD 11.1 ebf 2 Unexpected error while executing the following action: Changing value of attribute Creation Date of object In all versions the error occurs at the same level Delete Class "Stichprobenergebnis" Delete Shortcut of Class "Stichprobenergebnis" Repository : Oracle 8.1.7 ODBC driver used : Datadirect OEM 4.20 Oracle wire protocole, OEM 5., Oracle driver Repro \\neo\CIR\CIRMails\39xxxx\397618 ct is woring in 10.1 version but I also got the problem in 11.1 ebf 2 version When doing the consolidation in 2 steps - consolidation 1 Delete Class "Stichprobenergebnis" Delete Shortcut of Class "Stichprobenergebnis" both unchecked -consolidation 2 Delete Class "Stichprobenergebnis" Delete Shortcut of Class "Stichprobenergebnis" checked It is working When consolidation with "create baseline version" it is working Could not isolate much the problem No ODBC Trace Steps to reproduce Consolidate the server.oom and extract it Merge into server.oom the local.oom Select all actions consolidate with update the repository in merge windows Select all actions Have a look Package 0_Diagramme --> Fachliches Objektmodell classe : shortcut Stichprobenergebnis is going to be deleted Package AM.pro Backend --> 0_Geschftsobjekte Class : Stichprobenergebnis is going to be deleted Error message Unexpected error while executing the following action: Changing value of attribute Creation Date of object If both are unchecked no problem

CR:397637

CR Number:   397637 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   Windows 2000 Original Version:   penelope EBF2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 05 Sep 2005 Fixed Description Add MySQL (open source)dbms to be able to store/install the repository tables.

CR:397648

CR Number:   397648 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 009 09 Sep 2005 Fixed Description Format of LEPHYSTB changed. Sample exit and doc does not reflect the change. Format is now in previous format unless the names are too long for the field. If the names are too long, the first byte will be x'00' and the next for bytes will be a pointer to a varchar name (2 byte length prefix). Workaround Description  None, must modify the user exit

CR:397786

CR Number:   397786 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Generic Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Parameter to limit the size of a queue, or to designate a queue to a specific location. Workaround Description  none except to give enough stable device space and to provide timely monitoring of when stable device or queue has hit threshhold limits via Replication Server Manager Client

CR:398133

CR Number:   398133 Product Name:   Rep Server Configuration Guide Product Component:   Rep Server Configuration Guide Status:   Closed OS:   BSD Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 04 Jan 2006 Fixed Description Provide more correct instructions in entering character set and sort order when using rs_init to build a new Replication Server.

CR:398220

CR Number:   398220 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   all Original Version:   penelope Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Sep 2005 Fixed Description Steps to reproduce the problem PD 11 New PM informix 9 1 table : T1 with column C1 create one view (using Tool create view or not) SQL Query Select case when T1.C1 = ' ' then 1 else 0 end case as C_view from T1 consolidate using datatdirectdriver without extraction upgrade the rep to 11.1 and to 11.1 ebf 4 using Informix driver extract using informix driver Model graphic is empty the objects have been extracted but the view has no columns anymore When you add another column to the table and to the view (new column before and/or after the case expression: no problem anymore But it is a strange behaviour because in the ct model, the views have many columns and I had the problem you will find \\neo\CIR\CIRMails\39xxxx\398220 my_model_1 1 table, 1 view with a case expression in SQL query : broken after extraction FIKS_3_1_small_repro_33 small repro from ct's model : broken after extraction FIKS_3_1_small_repro_33_45 which contains a views with only case expression (from ct model): OK after extraction *** 26 August 2005 14:58:13 *** mtinevez *** PD 11.1 ebf 2 Repository : Informix Driver ODBC used : Informix ODBC driver Steps to reproduce PD 11 - consolidate the model which contains few tables, views and view references - extract : result OK - Upgrade to PD 11.1 and after to PD 11.1 ebf 2 using Informix ODBC driver - extract the model consolidated with PD 11. Have a look in the graphic, nothing, objects are there but they are not visible view references parent and child : nothing View column : no name model used to do the test \\neo\CIR\CIRMails\39xxxx\398220

CR:398309

CR Number:   398309 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Solaris Original Version:   12.5.0.301 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 Jul 2008 Presently Not Targeted For Any Future Release Of This Product Description RAM hangs. Desire flag similar to CR 359566 that was created for Oracle. Workaround Description  None at this time. We don't know the circumstances that causes this problem at this time.

CR:398410

CR Number:   398410 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/MsSQL Status:   Closed OS:   Generic Original Version:   12.5.0.301 Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 Nov 2008 Presently Not Targeted For Any Future Release Of This Product Description Request is to force READ COMMITTED by explicitly setting this in the relevant ra_ procs so that they won't fail if the apps is running under another isolation level

CR:398928

CR Number:   398928 Product Name:   Rep Serv Commands Ref Product Component:   Rep Serv Commands Ref Status:   Closed OS:   NA Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 12 Jan 2006 Fixed Description short ltl keywords is mis-typed as short Itl keywords in the RS Commands Reference Manual.

CR:400099

CR Number:   400099 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.3.03 10 Dec 2006 Fixed 5.4.00 06 Dec 2006 Fixed 5.3.02 06 Mar 2008 Fixed Description ORACLE ONLY: The Replication Agent has been enhanced to allow archived redo logs to be accessed when required data no longer exists in the on-line redo logs. Configuring the Replication Agent to include access to archive logs also removes the requirement that Oracle automatic archiving be disabled. When the Replication Agent configuration is changed to include archive logs, the Replication Agent will no longer issue archive commands to Oracle, requiring that automatic archiving in Oracle be enabled, or that archiving be performed by a mechanism other than Replication Agent. The following three new configuration options can now be used to configure the Replication Agent to include archive log usage, obtaining the archive logs from the location specified and optionally having the Replication Agent remove the archive log files when they are no longer needed for Replication. 1) pdb_include_archives New configuration property pdb_include_archives, when true, indicates that Replication Agent should read Oracle archive log files in addition to on-line redo log files. When false, only on-line redo log files are read, and the Replication Agent expects to control the Oracle archiving process (Oracle automatic archiving must be disabled). Default value: false Allowed values: true: Enables reading of archived Oracle redo log files from the path specified by configuration parameter pdb_archive_path. Configuration of Oracle automatic archiving is supported under this mode. Removal of old archive logs (no longer needed to support replication) may be provided using configuration property pdb_archive_remove. false: Only on-line redo logs files will be read. Oracle automatic archiving must be disabled. The Replication Agent will execute Oracle archive commands to archive the redo logs once they are no longer needed for replication. Comments: Set this configuration to true when use of archive logs in addition to on-line redo logs is preferred or when Oracle must be configured to perform automatic archiving. Set this value to false if accessing only the on-line redo logs is preferred. 2) pdb_archive_path New configuration property pdb_archive_path identifies the directory path where the Replication Agent will expect to find archived Oracle redo log files. Valid only when configuration parameter pdb_include_archives is enabled. Default value: none Allowed values: A valid directory path on the machine hosting the Replication Agent, pointing to a location where Oracle will place archived redo logs. Comments: Setting of the configuration parameter is required and must be set to a valid location before the Replication Agent can be placed in a replicating state when configuration parameter pdb_include_archives is also set to true. 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. Archived log files can be removed from this location by the Replication Agent, if configuration parameter pdb_archive_remove is set to true. WARNING: The Replication Agent process must have access to this directory, and 'read' permissions on the individual archive log files. Access failures will prevent the Replication Agent from maintaining a replicating state. 3) pdb_archive_remove New configuration property pdb_archive_remove, when true, indicates that Replication Agent should remove archived log files from the directory specified by pdb_archive_path during log truncation processing. Valid only when pdb_include_archives is enabled. Default Value: false Allowed Values: true: Enables removal of archived Oracle redo log files from the path specified by pdb_archive_path. Removal occurs based on the execution of command pdb_truncate_xlog, or the timing of automatic truncation based on parameters truncation_type and truncation_interval false: Disables Replication Agent removal of archived Oracle redo log files. Comments: Set this configuration to true when the path specified by pdb_archive_path is established solely for Replication support, and automatic removal of unneeded archived log files is desired. If the path specified by pdb_archive_path is shared by other processes, or the removal of archived log files is expected to be performed by processes other than the Replication Agent, this parameter should be false. Parameters truncation_type and truncation_interval, and command pdb_truncate_xlog have no impact when this configuration parameter is set to false. WARNING: When the pdb_archive_remove parameter is set to TRUE, the Replication Agent process must have UPDATE access to this directory, and 'UPDATE' permissions on the individual archive log files. Failure to provide the necessary permissions will prevent the Replication Agent from removing old archive files. After the three new configuration options have been properly set, Replication Agent command ra_updatedevices should be executed prior to resuming replication. This command will query Oracle to obtain the 'log_archive_format' value from the v$parameter table. This format is required to allow the Replication Agent to recognize the archive log file names. Once ra_updatedevices command has been run and the three new configuration parameters have been set and permissions to the archive log files and directory have been granted, the Replication Agent can be placed in Replicating state and automatic archiving in Oracle can be enabled.

CR:400316

CR Number:   400316 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.06 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 015 26 Oct 2005 Fixed Description LEX0005 message is not clear enough.

CR:400595

CR Number:   400595 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Jun 2006 Fixed Description RS may stack trace when "dataserver" does not have a corresponding entry in the interfaces file and the "drop connection" command is executed.

CR:400889

CR Number:   400889 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   LTI Driver Status:   Closed OS:   NA Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.1.01 07 Oct 2005 Fixed Description Incorrect LTL is generated for rs_dump procedure execution.

CR:400958

CR Number:   400958 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 In a warm standby setup, when a stored procedure is marked for replication at the active (with sp_setrepproc), only its execution is replicated at the standby. Therefore, triggers associated with inserts/deletes on the tables that the procedure touches will not fire at the standby. This may cause inconsistencies in the data at active and standby and can be worked around by using 'set triggers' code in the body of the replicated stored procedure. Workaround Description  Including set triggers code in the replicated stored procedures seems to properly address the situation, however, any user executing the stored procedure needs to have replication_role.

CR:401777

CR Number:   401777 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 06 Sep 2005 Fixed 12.6 06 Sep 2005 Fixed Description Block database subscriptions in mixed version environment Target Version  12.6

CR:401955

CR Number:   401955 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 024 14 Dec 2005 Fixed Description LTMEXT abends with 0C7 - data exception due to DB2 log rec compresson/expansion

CR:401974

CR Number:   401974 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.00 31 Oct 2005 Fixed 5.2.00 06 Mar 2008 Fixed Description When configuring the log directory (ra_config log_directory, xxx) where "xxx" is an invalid directory name, no error is returned.

CR:401975

CR Number:   401975 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.00 31 Oct 2005 Fixed 5.0.00 22 May 2008 Added to user documentation 5.2.00 06 Mar 2008 Fixed Description When using ra_config command to set log_directory property to the default value, the resulting path does not include the instance name.

CR:402069

CR Number:   402069 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 015 26 Oct 2005 Fixed Description Expansion routine crashes with 0C4 in LTMINFO when many tables are marked for replication. Workaround Description  Reduce the number of tables marked for replication.

CR:402221

CR Number:   402221 Product Name:   Repository Product Component:   Repository Status:   Open OS:   all Original Version:   ulysses Fixed Version Build Resolution Date Closure Code (If Appropriate) Description During the repository installation, PD could create pre-defined repository user groups ("Administrators", "Developers", "Business users" - as PD help suggests) associated with reasonable access rights. Benefit: A repository creator can customize or delete these more easily.

CR:402228

CR Number:   402228 Product Name:   Repository Product Component:   Repository Status:   Open OS:   all Original Version:   ulysses Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Nov 2005 Fixed Description The customer has submitted the following request: The repository setup scripts could contain a few lines of metadata, similar to a "generate database as script" generation option. Some explanations what to do next or in case of failure or incomplete setup could also be placed in the SQL comment. In an effort to clarify this request the customer was assked the following questions: What specifically are you looking for? Other metadata such as date created, created by user, a general description of the purpose of repository database, suggestions for a naming convention, security issues (database level), size recommendations.... What do you want for 'what to do next'? In case of a successful rep setup, Perhaps a hint for the username and password that must be used to connect the repository. In case of an unsuccessful setup: Hints what to do besides the three choices (ignore - ignore all - abort). Explanations what "ignore", "ignore all" "abort" mean, respectively. What are alternatives (e.g., retry) and consequences In what scenario are you encountering an incomplete repository setup? In the general scenario. Clicking on Powerdesigner menus and dialog boxes. Sometimes the rep setup script is 13000 lines long, sometimes it has 19000 lines (for no apparent reason) Submitting the dialog box with the setup script to the server with the repository database. Creates above mentioned cryptic error dialogs. The repository setup process is pretty awkward. A *general* redesign (perhaps by means of a wizard) would be appropriate, IMHO.

CR:402340

CR Number:   402340 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.09 14 Feb 2006 Fixed Description S0C4 in LTMEXT at OFFSET=00004220 with compression Workaround Description  Problem is in decompressing a DB2 log. Fix to be included in 12.6.8. No workaround except to replicate using RA DB2 12.0 or 12.5

CR:402421

CR Number:   402421 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   NA Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Use of NULL on where clause should throw syntax error.

CR:402424

CR Number:   402424 Product Name:   RepAgent/ASA Product Component:   Replication Agent Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.0 1820 09 Sep 2005 Fixed Description The SQL Anywhere RepAgent now supports long table names, column names, procedure names, function names, and parameter names. The maximum length for these names is 128 bytes and that is identical to the maximum length of identifiers in SQL Anywhere. In order to use this new feature, the Rep Server and the Open Server/Open Client must be equal to or greater than version 15.0. Versions earlier than 15.0 still support these objects using the old maximum identifier length of only 30 bytes.

CR:402443

CR Number:   402443 Product Name:   Repository Product Component:   Documentation Status:   Closed OS:   all Original Version:   Minerva Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 Nov 2005 Presently Not Targeted For Any Future Release Of This Product Description ENH: Offer a more streamlined document displaying how the repository meta-tables and their columns are linked. Customer's comments: Current need: Reporting of high level objects and information against the models in the Repository like, "How many CDMs, PDMs, OOMs are in the repository?", "What models are in which folder?" "What is the repository version number of each model?". ENHANCEMENT: ---------------------------- A user could (with some effort) certainly derive the desired meta-data out of the existing sample models and documentation that PowerDesigner Development has to offer to produce queries. However, it would be more beneficial to the end users if you could provide a more simplistic form showing the mapping (linking) of these tables and columns to each other, or maybe a hierarchical document that shows how one could 'mine the data' of an object in a model type. This hierarchical document would show the descending levels of metadata. A white paper of sorts. Additionally, when maintenance updates are provided and it affects the repository (new tables, new columns, new datatypes etc...) then provide what has changed in the 'What's New' documentation. (ie) Adding the dragging of models and folders feature to the repository browser was a big change but, no mention in the 'What's New' documentation of what changes were specifically made to which repository tables. As an end user, while I understand that structure changes need to be made to a repository structure to enable enhancement, I have a couple of concerns: 1. Is the MetaModel in the examples directory updated with the latest changes? 2. Will my reports (queries) still work and if not will I have to redo all of the initial discovery work with the model to determine how to modify my report (queries) to work again? Please, give the end user a heads up (document changes) which can curb time and effort in addition to building trust in the tool set. 11/04/2005 This enhancement has been reviewed and will not implemented. Per engineering, the repository metamodel.pdm in Example directory must be used to understand repository structure.

CR:402645

CR Number:   402645 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.00 31 Oct 2005 Fixed 5.2.00 06 Mar 2008 Fixed Description When configuring the log directory (ra_config log_directory, xxx) where "xxx" is either an empty string or a space, the RepAgent will hang on startup.

CR:402702

CR Number:   402702 Product Name:   Sybase Replication Server Product Component:   RSMJavaPlugin Status:   Closed OS:   Microsoft Windows Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Sep 2009 Presently Not Targeted For Any Future Release Of This Product Description When status changes for connections in a warm standby environment, the active and standby logical connection columns for logical connections are not being updated, but the logical connection icon does update. This means that a user needs to do a manual refresh for those two columns to update.

CR:402867

CR Number:   402867 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   12.5.0.303P2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.5.0.308P9 25 Feb 2008 Fixed Description ORACLE ONLY: The shadow table columns created by the Replication Agent may have insufficient size to accommodate a primary table column defined as type number without explicit precision. The fix provided in this ESD affects only newly created shadow tables (created when an object is marked for replication). For shadow tables that already exist, the column size will only be corrected if the object is un-marked and re-marked. Note that un-marking and re-marking should only be performed if all data from the affected tables has been replicated. To manually perform the modification, without un-marking and re-marking, the size of the shadow table columns may be increased by altering each column so that the shadow table columns size is increased to varchar2(40). Example: ALTER TABLE <my_tab> MODIFY (colx varchar2(40)); Note that this modification is necessary only if the existing shadow table column size is less than 40 for a primary table column defined as NUMBER without any precision. Workaround Description  Manually modify the field in the shadow table to varchar2(40) or drop and recreate the shadow table with varchar2(40).

CR:402905

CR Number:   402905 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 018 09 Sep 2005 Fixed Description Trace command stops replication. Workaround Description  Do not issue trace= command from console

CR:403008

CR Number:   403008 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Generic Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description rsupgr.sql is inefficient and does not use indexes in join Workaround Description  See description of problem for proposed changes

CR:403519

CR Number:   403519 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 High CPU and low latency Workaround Description  drop partitions and start from fresh partitions. We don't know if the size of the backlog of the partition is the problem.

CR:403643

CR Number:   403643 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.0 23 Mar 2006 Fixed Description Document that IPV6 certification is available as of 12.6 ESD #5.

CR:403687

CR Number:   403687 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   LTI Driver Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.1.01 07 Oct 2005 Fixed 5.0.00 22 May 2008 Added to user documentation Description Change in behavior: Before you can start replication, you must set the configuration property rs_charset to match the character set at RepServer. If rs_charset does not match RepServer's character set, then RepServer will do character set conversion on the complete LTL commands it receives which will corrupt the origin QIDs and transaction IDs.

CR:403736

CR Number:   403736 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.09 16 Feb 2006 Fixed Description RA DB2 terminates without providing adequate information on why it shutdown. Restart is successful.

CR:403825

CR Number:   403825 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 025 14 Dec 2005 Fixed Description QIDs are not ascending message resulting from incorrect calculation for RBA when a logical log record spanned physical log data areas. Workaround Description  Customer went back to older version. However, once we know what causes the issue, other alternatives might be possible.

CR:403929

CR Number:   403929 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 020 11 Oct 2005 Fixed Description Replication Agents for DB2 UDB (RAD) for OS/390 terminates after one of the DB2 members is stopped and LOGINFO command is issued.

CR:404037

CR Number:   404037 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 10 Oct 2005 Fixed 12.6 22 Nov 2005 Fixed Description MSA with table replication definition and minimal columns does not behavior the same as warm standby. Workaround Description  add warm standby replication definition if want to use minimal columns

CR:404131

CR Number:   404131 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 024 26 Oct 2005 Fixed Description After an invalid console command has been entered and ignored, RAD 12.6.8 beta would abend with S0C4 within module LTMMMGR when it is subsequently terminated using the correct console STOP command: > 290 SYSTEM COMPLETION CODE=0C4 REASON CODE=00000004 > 290 ACTIVE LOAD MODULE ADDRESS=0E800390 OFFSET=00040AFA > 290 NAME=LTMMGR

CR:404196

CR Number:   404196 Product Name:   Sybase Replication Server Product Component:   RSMJavaPlugin Status:   Closed OS:   NA Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Oct 2009 Presently Not Targeted For Any Future Release Of This Product Description The ASE RepAgent Thread requires the ASE to be properly named with the 'sp_addserver' system procedure. If the ASE is not properly named, an attempt to start an ASE RepAgent Thread will result in an error. Replication Manager needs to check if sp_addserver has been run, and if not, run it before starting the ASE RepAgent Thread.

CR:404249

CR Number:   404249 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.09 05 16 Feb 2006 Fixed Description 0C7 after DB2 LOAD REPLACE with DD DUMMY

CR:404274

CR Number:   404274 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.09 05 14 Feb 2006 Fixed Description The Rep Agent sends the LEX0044 message after a shutown was requested.

CR:404401

CR Number:   404401 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Jul 2006 Fixed Description <set ciphertext on> session property is not recognised by IQ (ie 125) and DSI is in limbo state. The function string for this connection will require adjustments to support IQ. Workaround Description  Alter the rs_set_ciphertext function string in order to nullify the command send ie: create function string class <..> set parent to rs_asa_function_class go create function string rs_set_ciphertext for <..> output language '' go alter connection to <..> set funtion string class to <..> go

CR:404559

CR Number:   404559 Product Name:   RepAgent/ASA Product Component:   Replication Agent Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3195 23 Sep 2005 Fixed 9.0.1 2072 23 Sep 2005 Fixed 8.0.3 5303 23 Sep 2005 Fixed Description Updating a non-BLOB column of a table in a primary database would have caused the data of nullable BLOB columns to be lost in the replicated database. These nullable BLOB columns of the updated rows in the replicated database could have a NULL value after the update. This problem has been fixed.

CR:404673

CR Number:   404673 Product Name:   Rep Serv Commands Ref Product Component:   Rep Serv Commands Ref Status:   Closed OS:   NA Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 12 Jan 2006 Fixed Description rs_config table has column named comments instead of comment.

CR:404758

CR Number:   404758 Product Name:   Repository Product Component:   Repository Status:   Open OS:   Windows 2000 Original Version:   Minerva Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Tested and reproduced with: PD 11.0, 11.1, 11.1 EBF#5 Today, when deleting an object from a model directly in repository, customer would like a warning to be displayed telling that there are respective shortcuts in other models in repository that also need to be deleted.

CR:404984

CR Number:   404984 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.00 31 Oct 2005 Fixed 5.0.00 22 May 2008 Added to user documentation 5.0.00 22 May 2008 Added to user documentation 5.0.00 02 Apr 2010 Presently Not Targeted For Any Future Release Of This Product 5.3.00 25 Aug 2006 Fixed Description ORACLE ONLY: Oracle datatype TIMESTAMP WITH TIMEZONE is replicated without including the time zone displacement value. In order to support inclusion of the time zone displacement, new configuration parameter pdb_timezone_file has been added to allow the customer to specify the exact location of the Oracle timezone file to be used. This configuration parameter must be set to $ORACLE_HOME/oracore/zoneinto/timezone.dat or timezlrg.dat, depending on which timezone file the Oracle server has been configured to use.

CR:405076

CR Number:   405076 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.00 31 Oct 2005 Fixed 5.2.00 06 Mar 2008 Presently Not Targeted For Any Future Release Of This Product Description ORACLE ONLY:After executing "trace" command, the error message "Could not find Resource Bundle containing index: xxx" is shown on the console for LOGRECDBG and ORACLETYPMAPDBG debug flags.

CR:405227

CR Number:   405227 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Utilities Status:   Closed OS:   NA Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.4.00 04 Dec 2006 Fixed Description Three parameters "log_wrap", "log_backup_files" and "log_append_existing" are supported in exclusive debug logs.

CR:405228

CR Number:   405228 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.1.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.00 31 Oct 2005 Fixed 5.0.00 22 May 2008 Added to user documentation Description ORACLE ONLY: Replication fails if the last attribute of a user defined object type is null and the object type is the last column of a table.

CR:405382

CR Number:   405382 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 Mar 2010 Fixed Description Upgrade script does not mark rs_dbreps and rs_dbsubsets as replicated tables.

CR:405562

CR Number:   405562 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Solaris Original Version:   12.6 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Oct 2005 Fixed 27 Oct 2005 Fixed Description When distributor is resumed, rs_writetext causes 7034 (unable to obtain system memory). Workaround Description  None, problem does not seem to happen with iso_1, however, we don't know if that would cause problems with the data. The problem can be bypassed by purging the queue. Zapping the begin of the transaction does NOT get around the problem.

CR:405968

CR Number:   405968 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   Windows 2000 Original Version:   atlas Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Oct 2005 Fixed Description Reproduced in PD 11.1 EBF#6 When consolidating OOM model into repository for the 2nd time with "Freeze after consolidation" set, actor, message and objects are moved down improperly inside diagram. Other objects like rectangle are kept in correct place.

CR:406038

CR Number:   406038 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   NA Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.01 23 Jan 2006 Fixed 5.0.00 22 May 2008 Added to user documentation Description ORACLE ONLY: The DDL replication configuration setting (the 'pdb_setrepddl' command) is reset after invoking the 'pdb_xlog init, force' command. Workaround Description  Execute "pdb_setrepddl enable" after re-initializing.

CR:406052

CR Number:   406052 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Open OS:   Solaris Original Version:   12.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description admin statistics, repagent, bytesxferred shows negative value for BytesXferred. Workaround Description  Do not rely on this counter. It is possible that flushing this counter to RSSD will have a retain its positive value. However, RS 12.6 found that the counter does not track bytes correctly. It would be better to get similar information from SQM counter such as: 6004 SQM: Bytes written to queue, Total bytes written to a stable queue by an SQM thread.

CR:406165

CR Number:   406165 Product Name:   Sybase Replication Server Product Component:   repserver Status:   Closed OS:   Generic Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Oct 2009 Duplicate Description Request for RepServer to allow more than 2gb of memory, removing the 2gb limit on setting memory_limit.

CR:406275

CR Number:   406275 Product Name:   Repository Product Component:   Repository Status:   Open OS:   all Original Version:   Minerva Fixed Version Build Resolution Date Closure Code (If Appropriate) Description The customer has executed 'Find Objects' in the repository. They then try to copy/paste the result set, but they are unable to do so. However, if the execute Find Objects on an open model, the result set can be copied and pasted. The customer is requesting the same functionality for the result set of the Repository find objects.

CR:406620

CR Number:   406620 Product Name:   Sybase Replication Server Product Component:   RMA Status:   Closed OS:   Generic Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Nov 2005 Not reproducible with latest version of the product available as of Resolution Date 15.0 200 08 Mar 2006 Fixed 05 Mar 2006 Workaround Description Event triggers that you create are executed by RMS on startup, which should not happen.

CR:406876

CR Number:   406876 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   12.6.0.5101 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.00 31 Oct 2005 Fixed 5.2.00 22 May 2008 Added to user documentation 5.2.00 20 Jan 2006 Fixed Description ORACLE ONLY: If CREATE SEQUENCE privilege is not granted to pds_username, "pdb_xlog init" fails resulting in the following error message in the log: Work is being rolled back because of problems executing script: ORA-01031: insufficient privileges.

CR:406888

CR Number:   406888 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.2.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.00 31 Oct 2005 Fixed 5.0.00 22 May 2008 Added to user documentation Description ORACLE ONLY: Initialization of the RepAgent instance fails in some Oracle environments with a NumericOverflow error.

CR:407133

CR Number:   407133 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.01 23 Jan 2006 Fixed 5.3.00 19 May 2008 Fixed Description ORACLE ONLY: Replication of a large LOB value fails with a BufferUnderflowException.

CR:407377

CR Number:   407377 Product Name:   Repository Product Component:   Repository Status:   Closed OS:   Windows 2000 Original Version:   Minerva Fixed Version Build Resolution Date Closure Code (If Appropriate) 14 Jun 2006 Fixed Description Tested and reproduced with PD 11.0 and PD 11.1 EBF#6. A model in repository has package1 and package2. Package1 has a shortcut dependency from Package2. if we uncheck "Extract Dependencies" and extract Package, obligatorially PowerDesigner displays: "Your package selection has been automatically extended to include target packages referenced by internal shortcuts". According to PD help, no shortcut dependencies should be included in package extraction.

CR:407434

CR Number:   407434 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   Log Admin Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.01 23 Jan 2006 Fixed 5.2.00 19 May 2008 Fixed 5.3.00 25 Aug 2006 Fixed Description ORACLE ONLY: When a table is marked with a different replication name with the command "pdb_setreptable <priName>,<repName>,mark" or "pdb_setreptable <priName>,<repName>,mark,owner", replication fails because RepAgent does not use the replicate name. This fix requires Replication Agent migration. ALL PRIMARY DATABASES: How you specify the owner of the table in a replication definition has changed from that described in the Reference Manual. Now, you must always use the "owner" keyword if you want to enable the SEND OWNER mode. When marking, if you do not specify the replicate owner, it will default to the primary owner. In the following examples, the leading letter indicates either primary (p) or replicate (r): Example 1: pdb_setreptable ptable, rtable, mark, owner the table in the replication definition will be: powner.rtable Example 2: pdb_setreptable ptable, rowner.rtable, mark,owner the table in the replication definition will be: rowner.rtable Example 3: pdb_setreptable ptable, rowner.rtable, mark the table in the replication definition will not be owner-qualified: rtable Workaround Description  *** Thursday, August 17, 2006 11:06:18 AM *** wliao *** Can set primary table name the same as the replicate table name in create replication definition command.

CR:407527

CR Number:   407527 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.08 024 26 Oct 2005 Fixed Description RAD 12.6.8 beta reports setting ERROR_CODE (in LTMOBJECTS) to 16 instead of the documented 12 when, before RAD job startup, the DB2 DATA CAPTURE CHANGE was set to NONE for a DB2 table marked for replication: > 14.57.37 STC01191 LTMINFO Replication stopped for TWCLRFXD because data capture changes none > 14.57.37 STC01191 LTMINFO: TABLE LOAD COMPLETE ... > 14.57.38 STC01191 LEX0068 Replication updated for table JEDB21 .TWCLRFXD > 14.57.38 STC01191 LEX0070 Column ERROR_CODE changed to 16

CR:407547

CR Number:   407547 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.01 23 Jan 2006 Fixed 5.2.01 23 Jan 2006 Fixed Description ORACLE ONLY: The 'ra_locator zero' command fails to clear the stored locator value.

CR:407549

CR Number:   407549 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.3.00 07 Mar 2006 Fixed 5.3.00 19 May 2008 Fixed 5.3.00 25 Aug 2006 Fixed 5.3.00 07 Mar 2006 Fixed 5.3.00 07 Mar 2006 Fixed 5.3.00 07 Mar 2006 Fixed Description ORACLE ONLY: has a new feature for creating and removing replication definitions at RepServer. This feature is included not only as a command, but replication definitions can also be automatically created when tables, or procedures are marked, and removed when they are unmarked. New command "rs_create_repdef" creates replication definition at the configured RepServer. Description: Creates a replication definition at RepServer for a marked table/procedure, or all marked tables/procedures. Syntax: rs_create_repdef <ALL> rs_create_repdef <TABLE_NAME> Usage: - When rs_create_repdef is invoked and the parameter "all" or "ALL" is entered, a replication definition is created for all tables and procedures that are marked for replication. - When rs_create_repdef is invoked and the name of a table or procedure that is marked for replication is entered, a Replication Definition is created for that table or procedure. - A result set is returned for each table or procedure that a replication definition create is attempted. The result set contains the replication definition name and status of the create. If the replication definition was created, the status will be "Created". If an error occured, the error message from RepServer will be returned for the status. - The character case of the object names in the replication definition will be set according to the "ltl_character_case" setting. - Replication definition names for tables always begin with the prefix "ra$", and end with the suffix "_rd" and use the replicate table name (possibly modified) in between. All non-alphanumeric characters except the underscore, and period are removed from the replicate table name. The period ("." ) is converted to an underscore, and the resulting name is truncated, if necessary, to 24 characters (repdef names are limited to 30 characters). For example, for a replicate name of "My Table", the resulting repdef name is "ra$mytable_rd". For an owner-qualified replicate name of "wbeck.MyTable", the resulting repdef name is "ra$wbeck_mytable_rd". For an especially long replicate name of "mytable89012345678901234567890" (30 characters), the resulting repdef name is "ra$mytable89012345678901234_rd". - Replication definition names for procedures are the same name as the procedure. New command "rs_drop_repdef" drops a replication definition at the configured RepServer. Description: Drops a replication definition at RepServer for a table/procedure. Syntax: rs_drop_repdef <TABLE_NAME> Usage: - When rs_drop_repdef is invoked a replication definition for that table is dropped at replication server. - A result set is returned for the table or procedure that a replication definition is dropped. The result set contains the table name and status of the drop. If the replication definition was dropped, the status will be "Dropped". If an error occured, the error message from RepServer will be returned for the status. - The character case of the object names in the replication definition will be set according to the "ltl_character_case" setting. - Replication definition names for tables always begin with the prefix "ra$", and end with the suffix "_rd" and use the replicate table name (possibly modified) in between. All non-alphanumeric characters except the underscore, and period are removed from the replicate table name. The period ("." ) is converted to an underscore, and the resulting name is truncated, if necessary, to 24 characters (repdef names are limited to 30 characters). For example, for a replicate name of "My Table", the resulting repdef name is "ra$mytable_rd". For an owner-qualified replicate name of "wbeck.MyTable", the resulting repdef name is "ra$wbeck_mytable_rd". For an especially long replicate name of "mytable89012345678901234567890" (30 characters), the resulting repdef name is "ra$mytable89012345678901234_rd". A new property "pdb_auto_create_repdefs" allows replication definitions to be automatically created and dropped at RepServer for tables and procedures when they are marked and unmarked for replication. Description: If set to true, when tables and procedures are marked for replication, a replication definition is automatically created at RepServer for that table or procedure. Syntax: ra_config pdb_auto_create_repdefs,true ra_config pdb_auto_create_repdefs,false Usage: - When pdb_setreptable is invoked to mark a table or tables, a replication definition will be created at RepServer for each table that gets marked for replication if this property is set to "true". - When pdb_setrepproc is invoked to mark a procedure or procedures, a replication definition will be created at RepServer for each procedure that gets marked for replication if this property is set to "true". - When pdb_setreptable is invoked to unmark a table or tables, the replication definition will be dropped at RepServer for each table that gets unmarked for replication if this property is set to "true". - When pdb_setrepproc is invoked to unmark a procedure or procedures, a replication definition will be dropped at RepServer for each procedure that gets unmarked for replication if this property is set to "true". - When pdb_xlog is initialized and table auto marking is enabled, a replication definition is created for each table that is marked for replication if this property is set to "true". - The character case of the object names in the replication definition will be set according to the "ltl_character_case" setting. - Replication definition names for tables always begin with the prefix "ra$", and end with the suffix "_rd" and use the replicate table name (possibly modified) in between. All non-alphanumeric characters except the underscore, and period are removed from the replicate table name. The period ("." ) is converted to an underscore, and the resulting name is truncated, if necessary, to 24 characters (repdef names are limited to 30 characters). For example, for a replicate name of "My Table", the resulting repdef name is "ra$mytable_rd". For an owner-qualified replicate name of "wbeck.MyTable", the resulting repdef name is "ra$wbeck_mytable_rd". For an especially long replicate name of "mytable89012345678901234567890" (30 characters), the resulting repdef name is "ra$mytable89012345678901234_rd". - Replication definition names for procedures are the same name as the procedure.

CR:407896

CR Number:   407896 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.09 05 19 Jan 2006 Fixed Description When a member of a DB2 data sharing group is taken down, incorrect DB2 log DSN information for the inactive member is displayed in response to the console LOGINFO command.

CR:407913

CR Number:   407913 Product Name:   RepAgent for MVS Product Component:   DB2 Status:   Closed OS:   MVS Original Version:   12.6.08 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.6.09 07 17 Feb 2006 Fixed Description RA DB2 terminates after restarting a DB2 member involved in multi-member datasharing.

CR:407926

CR Number:   407926 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   LTI Driver Status:   Closed OS:   NA Original Version:   12.5.0.303P2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.5.0.304P3 04 May 2006 Fixed Description LTI statistics that are dependent on the LTL command-size calculation are invalid. The invalid LTI statistics are: Total bytes sent Avg LTL command size Avg Bytes/second during transmission Avg 16k LTM buffer utilization (%) Avg LTL commands/buffer

CR:407940

CR Number:   407940 Product Name:   Sybase Replication Agents for Unix and Windows Product Component:   RepAgent/Oracle Status:   Closed OS:   Generic Original Version:   5.1.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 5.2.00 31 Oct 2005 Fixed Description ORACLE ONLY: Redo log is not archived because oldest open section of locator value does not change.