提供7*24专业Sybase数据库远程及现场技术支持,Sybase ASE及Sybase SQL Anywhere数据库修复服务,
请联系电话: (微信),QQ: 289965371!
We supply technical support for Sybase ASE and Sybase SQL Anywhere, also have many years of experience in recovering data from damanged Sybase devices.
Please contact us:
Phone:
Wechat: 13811580958
QQ: 289965371 联系我们获取数据库技术支持!
Email: 289965371@qq.com
扫描下方微信,联系我们:
扫描雨翰数据恢复官方微信获取专业数据库恢复服务

 

随着Sybase被完全整合到SAP下,Sybase原来的支持网站被SAP Support Portal取代。
只有购买了SAP服务的用户才能使用账号登录SAP Support Portal进行介质下载、补丁升级、报Incident等。
考虑到Sybase数据库的初学者或者没有购买原厂服务的Sybase客户情况,现提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息。
在SAP Support Portal网站或者google上搜索Targeted CR List for ASE,可以看到针对不同版本的CR(CR表示Change Request)简单描述信息列表。
需要注意的是:Targeted CR List for ASE列出的CR虽然绝大多数是BUG,但有一些是更改需求。
以下提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息!

如有问题,请联系我!

QQ :289965371 联系我们获取数据库技术支持!
Email:
不仅仅包括BUG的详细描述信息,还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程;有些BUG还提供了Workaround来临时解决该BUG带来问题。

 

CR:214559
CR Number:   214559
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   7.1.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Sep 2004 Fixed
Description
1. Create a new user and attach it to a group having the Connect RIght.

2. Go to the Rights tab of the User prop sheet. Note that the Connect right has not been added to the user.

We should have a mechanism a checked-grayed box for inherited rights.

It could also be a "show inherited rights" icon like in member tab for a group.



CR:221815
CR Number:   221815
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   7.1.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Aug 2000 Duplicate
Description
7.5.0.715

BUG when creating repository tables. No confirmation message to say "Finished creating tables."

I know that this is not a major issue, but from the customer's perspective, they need to know when a PowerDesigner process has completed.



CR:224873
CR Number:   224873
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   7.1.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
7.5.0.739



During consolidation of large models, PD shell stops responding to Windows (doesn't update display, etc). Need more than just "Saving the local document in the repository..."



1) Import model into PD7 and save it

2) Then consolidate that model into your favorite repository.

3) When it gives you the "Saving the local document..." message, launch the TaskManager and check out the PowerDesigner program.

NOTE: It will be listed as "Not responding".

4) If you have another application open, move its window around in front of the PD GUI.

Notice that it doesn't refresh the display. This is not good.

It takes a long time (anything over a minute or so is too long, but I'm talking 30 minutes and longer here) before it will update the GUI.



What I want to see is more GUI refreshes and some kind of status update in the message window, like what happens when I Reverse Engineer a database. The old MetaWorks gave me more information than this when it was working. Just giving me an hourglass is not acceptable



CR:224982
CR Number:   224982
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   7.1.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
beluga 03 Jan 2001 Fixed
Description
7.5.0.739

When creating the repository dictionary on DB2, there is no way to specify Create Table options that are allowed in DB2. Also, there is no way to obtain a copy of the DDL script for modification before the repository is created.
In PD6, there was a SHOW option in MetaWorks too provide access to the Dictionary creation script.

This functionality needs to added back into PowerDesigner 7.5.x.



CR:225082
CR Number:   225082
Product Name:   Repository
Product Component:   Documentation
Status:   Closed
OS:   all
Original Version:   7.1.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
beluga 01 Dec 2000 Fixed
Description
7.5.0.739

In the PowerDesigner Repository Users Guide Part 1 "Using the Repository" chapter 7 topic "Understanding consolidation conflicts," there is a paragraph that reads as follows:

Updating PowerDesigner models

When you update PowerDesigner models, the merge dialog box
displays differences between models and lets you define merge actions.
In the merge dialog box, the local model is the source model displayed
in the right pane, and the repository model is the target model that will
be modified in the left pane of the merge dialog box.

Where it says that "the local model is the source model displayed in the right pane, and the repository model is the target model that will be modified in the left pane of the merge dialog box" THE OPPOSITE IS TRUE, THE TARGET MODEL WILL ALWAYS BE ON THE RIGHT SIDE AND THE SOURCE ON THE LEFT. [Passing along customer's upper-case emphasis there, that comes from confusion we had working with the Merge dialog in the Betas.]

The doc is wrong and needs to be updated because Source-Target is potentially confusing.



CR:225090
CR Number:   225090
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   7.1.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
beluga 20 Nov 2000 Fixed
Description
7.5.0.781

BUG in Repository Extract, Select Packages dialog box. The list of packages is NOT SORTED. With over 125 in a model, this doesn't work well. Also EXTREMELY SLOW getting just one package.



CR:228693
CR Number:   228693
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   beluga
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
**** Fri Dec 01 15:55:48 EST 2000 *** ahill **** build 137 & 7.5.0.739

Allow the user to build folders by reading a directory and then to consolidate that into the repository, or go the other way.

We have all of our models organized into a fairly complex directory structure on a network server. I want to duplicate the hierarchy of the directories directly in PD. Then I want to duplicate that into the repository. Now, when I extract something from the repository, it should default to the correct folder in the workspace, and from the workspace it should automatically save to the proper directory on the server. This should be a General Option like "Keep all folders in sync".



CR:228859
CR Number:   228859
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   beluga
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Upgrading Repository from 7.5.x to 8.0.132, the output window displays a line for each object in the repository, at least once. Actually, it displays the SQL statement for every command issued in upgrading the repository database.

It would be nice to send that SQL stream to a text LOG file, maybe put messages in the output window such as "Updating PMREFR table..." (one per table) or something to that effect. At the end, put a note that says "The entire SQL stream can be found in the file C:\Program Files\Sybase\PowerDesigner 8\RepositoryUpgrade.LOG" or something like that.

NOTE: The displaying of all of those statements (and I had thousands upon thousands) actually slows down the process significantly. Logging them to a text file could actually make it run faster.



CR:231367
CR Number:   231367
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   beluga
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
**** Fri Jan 12 17:44:51 EST 2001 *** ahill **** build 172

Please provide the user with some guidelines as to how large to make the repository database (at least for starters). There could be recommendations for a small, medium, and large model. And all the disclaimers can still be documented.



CR:232516
CR Number:   232516
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   beluga
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
**** Fri Jan 26 14:46:43 EST 2001 *** ahill **** Build 184

Consolidation of a model into the repsoitory takes a significant time if number of entities is large (> 100). It would be very helpful to see a progress bar showing % of consolidation completed.



CR:234493
CR Number:   234493
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   beluga
Fixed Version Build Resolution Date Closure Code (If Appropriate)
26 Jun 2002 Fixed
Description
**** Mon Feb 26 11:50:01 EST 2001 *** ahill **** build 203

When you look at attributes of an entity in the Repository tree view, they all appear as "Entity Attribute" and their property sheets have Name and Code blank. The tree view should show the Name of the attribute, and the property sheet should have the Name and Code value for the attribute.

To Reporoduce (I used Sybase ASE 12.0 on NT for the Repository and build 203 on NT for PD8):

[ 1] Open PD8 Examples\project.cdm and consolidate into Repository.
[ 2] Tools -> General Options -> Repository check on "Show objects" in Browser group if not on already.
[ 3] In Repository Object Browser, expand model node and Entiities node under that. Node entries are shown for the entities in the model.
[ 4] Pick one -- for example, CUSTOMER and open its node. Open the attributes node under that. For CUSTOMER, there are six items in the tree list that say "Entity Attribute" -- these should show the attribute name.
[ 5] Open the property sheet for these items. They all have the Name and Code fields blank. They should contain the correct values for the Name and Code of the attribute.



CR:234495
CR Number:   234495
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   beluga
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
**** Mon Feb 26 12:00:18 EST 2001 *** ahill **** build 203

There is no icon to open the property sheet of the parent object as you can do when you are in a CDM, PDM or OOM. The Property sheets for shortcuts in the Repository are not connected to the parent objects. For example on a shortcut entity, you cannot get the property sheet of the parent object. You cannot see its data item attributes, and the identification of the object's parent model and package is not clear. This functionality should be added.

Also, the General tab has a field called Location that has a value "Project management" -- the model name, telling you that this shortcut is in the model level of information. On the Attributes tab, there is a line entry also called Location that says "\CUSTOMER MANAGEMENT" -- reflecting the package where the entity resides. This is a little confusing. In the property sheet for shortcuts in the workspace, these fields are called "Target model" and "Target package" which is clearer.

Repro:
[ 1] Open PD8 Examples\project.cdm and convert the two submodel diagrams to packages.
[ 2] Consolidate into Repository (I used Sybase ASE 12.0 on NT, with Build 203 of PD8).
[ 3] Make sure "Show objects" is turned on in Tools -> General Options -> Repository -> Browser groupbox. Look at the tree view of the Repository Object Browser and see the shortcuts for entities at the model (top) level. Open the property sheet for one, for example, CUSTOMER.
[ 4] See that there is no way to get at information about the parent object.



CR:258912
CR Number:   258912
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   neptune
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2001 Presently Not Targeted For Any Future Release Of This Product
Description
**** Mon Sep 10 13:12:05 EDT 2001 *** ahill **** build 373 & 8.0.1.275

The problem appears to only occur when composite primary keys are being used and the first column of the primary key has a distinct value less than 100%.

To reproduce:
1) Create a new PDM
2) Create two tables
3) In table_1, add two columns and make them both part of the primary key.
4) Change the Distinct Values to 40% on the first column of primary key (column_1)
5) In table_2, add two columns and make them both part of the primary key.
6) Change the Distinct Values to 40% on the second column of primary key (column_2)
7) Consolidate the PDM (Note: Do not allow the extraction of the PDM)
8) Compare the PDM in the repository with the PDM in the workspace.
Note: In table_1, the distinct value percentage of column_1 has been changed to 100% in the repository.



CR:264254
CR Number:   264254
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   neptune
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Within PowerDesigner various SQL errors are not visible to the end user. This could be possible for all actions (consolidation, create/modify/delete branch,/config etc...).



CR:265511
CR Number:   265511
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   neptune
Fixed Version Build Resolution Date Closure Code (If Appropriate)
26 Jun 2002 Fixed
Description
**** Mon Nov 19 17:23:56 EST 2001 *** ahill **** build 436


Enhancement Request: In the Merge window pane (upon consolidation): you must uncheck each specific Sybmol's checkbox, this could take alot of effort... Somehow offer the user the ability to be able to "DESELECT ALL SYMBOLS" for each diagram. And then go to a specific diagram and select all the sybmols within that Branch. Or have a Select All/Unselect all symbol objects in the Symbols branch. But, it would be nicer to be able to go to a diagram node under symbols and be able to select all/de-select all the symbol nodes in a specific diagram.

To reproduce the behavior:

a) User1 extracts the current version of the model to their workspace.
b) User2 extracts the current version of the model to their workspace.
c) User1 changes the fill color of entity1 symbol on diagram1 from white to blue.
d) User2 changes the fill color of entity2 symbol on diagram2 from white to red.
e) User1 consolidates their workspace to the repository. The repository recommends (by prefilling in the check box) that the local change for entity1 be applied. The extracted model reflects the new color of blue for entity1. Entity2 is (still) white.
f1) User2 consolidates their workspace to the repository. The repository recommends (by prefilling in the check box)that the local copy for entity2 be applied. The extracted model reflects the new color of blue for entity1.
f2) BUT the repository also recommends (by prefilling in the check box)that the local copy of entity1 be applied - even though user2 has never made any change to diagram1 or entity1. The extracted model reflects the old color of white for entity1.

Per Product Development:

In PD 8.x, currently, the changes to symbol's attributes (fill color, line style, background color, font style, font style etc...) are not updated by a modification date in the Version info tab on that object. The Modification Date only concerns the object itself (adding/deleting a column, change a data type, add in description, comments etc..). So merge during the consolidation does not know when the change has been done on the symbol and cannot propose a correct check box. So when you make a change on the symbol, merge proposes a default checked check box but it can be turned on to be the wrong result. The best way to solve this issue would be to manage a modification date on all symbols. Although, it will be memory consuming...



CR:265915
CR Number:   265915
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   theseus
Fixed Version Build Resolution Date Closure Code (If Appropriate)
atlas 26 Apr 2002 Fixed
Description
When you modify Database properties in a PDM Name, comments ..., nothing is updated in the repository

Repository Database : Informix 8 and 9

I reproduced on Informix 9 and ASA 7

======================================================

Steps to reproduce

- new pdm - 1 table

- consolidate and extract

- modify the PDM like that

Models --> Modeles properties --> Database --> New

add few properties : Database name, Comments, notes

- consolidate with update

- extract again, all Database properties still like before nothing has been updated.



Reproduced with PD 7.5, 8.01 build 289 and 9 build 437



CR:268242
CR Number:   268242
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   8.0.1 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Jul 2002 Fixed
27 Aug 2002 Fixed
Description
PD version : 8.01 and 9

Repository : ASA 7

Error message:

" Unexpected error while executing the following action:

Changing value of attribute Alias of object Query Column Object

The consolidation of the document has been canceled."



After modify a view in a pdm by adding a new alias or adding a column from a new table and then consolidating the model using update, results in an error:



Unexpected error while executing the following action:

Changing value of attribute Alias of object Query Column Object



CR:268679
CR Number:   268679
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   neptune
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 May 2002 Fixed
Description
**** Thu Dec 20 16:27:38 EST 2001 *** ahill **** 9.0.0.438 & 8.0.1.292

There is no way to update the repository with a change made to the order of an object, send backwards or bring forwards. If this change is made, consolidating the model does not show any differences. If an object is modified so that the consolidation occurs, the change in object order is not updated to the repository.

Steps to repro;

1) create a new CDM
2) create 2 entities (entity_1 & entity_2)
3) position the symbols in such a way that entity_2 is overlapping entity_1 in a cascading fashion
4) consolidate the model (I used Oracle 8.1.7 rep using Merant 3.70 ODBC) using all the default settings
5) extract the model (do not update model in workspace, create a new model). You now have two models in your workspace with the same name
6) right-click on entity_1 >Order>Bring to front. Now it wil be overlapping entity_2. If you try to consolidate it at this point, no consolidation will occur becuase PD shows no differences between the local copy and the repository copy.
6a) You will need to make some other type of change to get the consolidation to complete. I changed entity_1's name & code to entity_10.
7) consolidate the model using all the default settings (update)
8) Extract the model and again do not update the workspace model. This will create a 3rd model in the workspace all having the same name.

NOTE:The name & code change remains intact however entity_2 is now in front of entity_10. The change made to the symbol was not recorded in the repository. PD is ignoring the object "order" information.



CR:271770
CR Number:   271770
Product Name:   Repository
Product Component:   Documentation
Status:   Closed
OS:   all
Original Version:   neptune
Fixed Version Build Resolution Date Closure Code (If Appropriate)
atlas 20 Feb 2002 Fixed
Description
"Repository User's Guide>Ch.5>Using Folders in the Repository" needs to explain the naming of new folders better.

One of the bullets in this section states the following:

The Name of the folder. This name must be unique in a hierarchy of folders.

However, when actually naming the folders, the name must only be unique at each level of a hierarchy. For example, I can create a hierarchy of folder_1>folder_1>folder_1. (This makes the above bullet incorrect.) However, if I try to create a second folder_1 at the root level, I will receive a message stating that this name already exists.

A suggested description could be ....

The Name of the folder. This name must be unique at each level in a hierarchy of folders.
The title of the CR should read....
Please clarify the Using Folders section of the repository documentation.



CR:272284
CR Number:   272284
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   Windows 2000
Original Version:   atlas
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Customer has consolidated a PDM. On the Attributes tab of a stored procedure, the customer is trying to review the text of the stored procedure. This is very difficult to do because the entire procedure text is written on one line. The customer would like the ability to open an expanded view to see the entire text of the stored procedure.



background information:

User is trying to perform a visual comparison between a consolidated procedure and one in the local model. Based on this comparison, they would then like to copy sections of the consolidate procedure and paste them into the local procedure. (The way to accomplish the customer's comparison issue is to compare the two models, but the customer does not prefer the option.)



CR:278643
CR Number:   278643
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   neptune
Fixed Version Build Resolution Date Closure Code (If Appropriate)
13 May 2002 Presently Not Targeted For Any Future Release Of This Product
Description
In the browser in the repository only the latest version is displayed. Customer wants to see all the versions in a tree view structure without right clicking on the name and then on versions tab.



CR:279936
CR Number:   279936
Product Name:   Rep Server Tests
Product Component:   Rep Server Tests
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 Jun 2002 Fixed
25 Jun 2002 Fixed
Description
The Replication Server installation script 'rs_install_systables.sql'

('rsinssys.sql' on Windows NT) contains the non-localized date value

'Jan 1, 4000' (and is used to represent a maximum date value). When the

ASE hosting the RSSD is using a non-English default language such as

Chinese, the date value is considered an illegal value and prevents the

proper initialization of the RSSD. To work around this issue, edit the

installation script and replace 'Jan 1, 4000' with '01/01/4000'.



CR:286066
CR Number:   286066
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Jun 2002 Fixed
Description
When attempting to replicate 'unichar' and 'univarchar' values which are

greater than 127 unichars (or 254 bytes) in length, the Replication

Server terminates with the following messages in the error log followed

by a stack trace:



N. 2002/05/22 15:08:19. INTERNAL ERROR #20020 DSI EXEC(103(1)

PDS.pubs2_rep) - (7958) The packer failed to pack a command.



F. 2002/05/22 15:08:19. FATAL ERROR #1029 DSI EXEC(103(1)

PDS.pubs2_rep) - (7958) CS-Library error: Error: 33816868,

Severity 1 -- 'cs_convert: cslib user api layer: common library

error: The result is truncated because the conversion/operation

resulted in overflow.'.



To work around this issue, limit the length of a 'unichar' or

'univarchar' column to 127 unichars (or 254 bytes).



CR:286584
CR Number:   286584
Product Name:   Other - Docs: Rep Server
Product Component:   Other - Docs: Rep Server
Status:   Closed
OS:   NA
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
29 Jun 2004 Fixed
Description
Preparing to upgrade servers with

replicated databases



dbcc gettrunc can return two different column headings. One is ltm_trunc_state, as the doc mentions, and the other is secondary trunc state. If the value is 1 under either heading, then replication is enabled for that database.



Regarding subscriptions, the paragraph is confusing. Using the check subscription is a good idea for checking for "valid" subscriptions. Explaining about "create subscription" is confusing.



In the bold note in the first part of this section, we state that it is NOT sufficient to have data in the inbound queue of Replication Server. Yet, if the customer follows the instructions in this order, suspending the DSI connections before ensuring the transaction logs have been drained will put data in the inbound queue. The section for suspending the DSI connections should be after the section on draining the transaction logs.



Also, formatting wise, some of the 2>go commands appear on the same line as >1



Status: Reviewed Sep 2002. Fix targeted (but not commited) for the 12.6 release.



CR:286778
CR Number:   286778
Product Name:   RepAgent/ASA
Product Component:   Replication Agent
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   7.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.2 3456 13 Jun 2002 Fixed
8.0.1 3011 13 Jun 2002 Fixed
8.0.0 2310 13 Jun 2002 Fixed
7.0.4 3343 13 Jun 2002 Fixed
7.0.3 2142 13 Jun 2002 Fixed
7.0.2 1596 13 Jun 2002 Fixed
6.0.04 3801 13 Jun 2002 Fixed
Description
The RepAgent was not have replicating stored procedure calls, if the procedures were executed by triggers. Procedures called by triggers are now replicated.



CR:286934
CR Number:   286934
Product Name:   Sybase Replication Server
Product Component:   rsmsrvr
Status:   Closed
OS:   Generic
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 27 Jun 2002 Fixed
Description
Missing parameters in stored procedure rsm_where_list causes Replication Server Plug-In to suspend indefinitely when adding a 12.0 or 12.1 Replication Server.
Workaround Description
 Using the rsm1250.sql script, for stored procedure rsm_where_list, copy the parameters from @byteswap to the end of the parameter list and add them to the parameter list in the rsm1200.sql and rsm1210.sql scripts.



CR:287170
CR Number:   287170
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Jun 2002 Fixed
Description
If the Replication Server and the replicate ASE are both configured with

differing character sets, the Replication Server relies on the replicate

ASE to perform the necessary character set conversion on the replicate

data.



If the replicate ASE is configured to always use Unilib character set

conversion (the 'enable unicode conversion' configuration value is set

to '2') but configured with an insufficient 'size of unilib cache'

value, the ASE will issue the following warning and will not perform any

subsequent character set conversion.



Msg 2420, Level 17, State 1: Unable to load Unicode-based

character set conversion table 'sjis' - Unicode conversion cache

is full. Please notify your system administrator to add mode

unicode buffers.



The Replication Server ignores this ASE warning message, which results

in replicate data not undergoing the proper character set conversion.



To work around this issue, configure the ASE with a larger 'size of

unilib cache' configuration value. Validate that the new configuration

value is sufficient by confirming that the above-mentioned error message

does not appear when contacting the ASE using the 'isql'. Be sure to

invoke 'isql' with the appropriate '-J<charset>' parameters so that

'isql' uses the same character set as the Replication Server.
Workaround Description
 Increase the "size of unilib cache" in replicate ASE so that when you isql into the ASE with -J <RRS's character set>, it does not generate the error message about being unable to load the Unicode-based
character set conversion table.



CR:287366
CR Number:   287366
Product Name:   Sybase Replication Server
Product Component:   rsmclient
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Aug 2009 Presently Not Targeted For Any Future Release Of This Product
Description
Feature request to filter out error message "Failed to find table object with name..." and generate DDL of repdef that exists in RS,

but primary table does

not exist in database.



Status: Reviewed Sep 2002. Fix targeted (but not commited) for a release beyond the 12.6 release.



CR:287415
CR Number:   287415
Product Name:   Sybase Replication Server
Product Component:   rs_init
Status:   Open
OS:   Microsoft Windows
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
TITLE: The Installer will not install critical files if the user choses

"No to All" when the Installer asks about installing over existing

files.



If the Installer attempts to install a new file over an existing file,

the Installer will ask the user how to handle the conflict. If the user

choses "No to All", critical files will not get installed.



When the user attempts to start 'rs_init', 'rs_init' will terminate with

the a message similar to the following:



INTERNAL ERROR: Unable to load messages for product 'rs' using

language 'english' and character set 'cp850: could not locate

the localization file

'c:\sybase\locales\english\cp850\sybinit\rs.loc'.



To avoid this issue, install the Replication Server in a separate

directory.



CR:287775
CR Number:   287775
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Microsoft Windows
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
TITLE: The Replication Server will not start if installed in the same

directory as an older version of the Replication Server



If the Replication Server is installed in the same directory as an older

version of the Replication Server, critical files (e.g. 'libunic.dll')

will not be updated.



Without these updated critical files, the Replication Server will fail

to start and issue a message similar to the following:



Cannot find Procedure entry point unisort_DataCompare in Dynamic

link library libunic.dll.



To avoid this issue, install the Replication Server in a separate

directory from other existing Sybase products.



Additionally, it may be necessary to update the 'libunic.dll' file

manually.



To do this, copy the file ...



%SYBASE%\SYSDLL\WindowsNT\WinNT\system32\libunic.dll



... to the following location ...



%SYBASE%\REP-12_5\bin\libunic.dll



If this does not resolve the issue, copy the file ...



%SYBASE%\SYSDLL\WindowsNT\WinNT\system32\libunic.dll



... to the following location ...



%SystemRoot%\system32\libunic.dll



CR:287959
CR Number:   287959
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Jul 2002 Fixed
Description
Turning on repserver trace "CM,GENERAL_1", "FSTR, GENERAL_1", etc will cause repserver to coredump.



CR:288036
CR Number:   288036
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   Dolphin
Fixed Version Build Resolution Date Closure Code (If Appropriate)
09 Mar 2004 Not reproducible with latest version of the product available as of Resolution Date
Description
S130 & S138 abend



CR:288371
CR Number:   288371
Product Name:   Sybase Replication Server
Product Component:   rsmclient
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Sep 2009 EOL'd version. Not to be Fixed.
Description
An earlier screen claims that RSM will add the maint_user login for you. This is only

true if dump/load option is not selected.



Final screen of "add standby database wizard" should include following information:



If you choose to Initialize standby database using dump and load option, RSM will

not create the maint_user for you. See RS Admin Guide, "Adding the Standby Database

Maintenance User"



Status: Reviewed Sep 2002. Fix targeted (but not commited) for the 12.6 release.



CR:288460
CR Number:   288460
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Informix
Status:   Closed
OS:   Generic
Original Version:   12.1.0.214P1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
4.0.0 06 May 2003 Fixed
12.1.0.215P2 04 Oct 2002 Fixed
12.5.0.302P1 04 Oct 2002 Fixed
5.0.00 02 Aug 2007 Presently Not Targeted For Any Future Release Of This Product
5.0.00 02 Aug 2007 Presently Not Targeted For Any Future Release Of This Product
4.0.1 20 Nov 2002 Fixed
Description
INFORMIX ONLY: Transaction ids are sometimes

negative. To fix this required changing the

schema of the XLog.



If you are creating an XLog, the new schema

will be used.



If you have an existing XLog with the new

schema (12.1.0.xxx where xxx >= 215 or

12.5.0.yyy where yyy >= 302), you need do

nothing special.



If you have an existing XLog without the new

schema (12.0 or 12.1.0.xxx where xxx < 215 or

12.5.0.yyy where yyy < 302), you must do the

following to migrate the schema:



1 - login to the RepAgent and verify that

scripts run automatically:



ra_config pdb_auto_run_scripts, true



3 - shut down the RepAgent and apply this EBF

3 - start the RepAgent in ADMIN mode

4 - lock the primary database to prevent the

marked primary tables and/or the marked primary

procedures from calling the ra_get_tx_info_

procedure

6 - at the RepAgent login, issue the pdb_xlog

command with no parameters

7 - unlock the primary database

8 - resume replication



The migration adds the ra_txid_seq_ table that

maps Informix transaction-id-related

information into a sequence number,

drops/re-creates the ra_get_tx_info_ procedure

to use the new table, and increments the

database generation id. Some additional

housekeeping entries are added to the

ra_xlog_system_ table, and, for Informix 7, the

tran-id rollover procedure (ra_txid_rollover_)

is created.



This new schema uses the following global

variables:



ra_begstamp_ (new)

ra_connected_ (new)

ra_opid_hi_

ra_opid_lo_

ra_pid_ (new)

ra_tstamp_

ra_txid_

ra_txid_hi_ (new)

ra_txid_lo_ (new)



Note that this fix does NOT migrate an XLog

created on Informix 7 to the appropriate schema

for Informix 9.



CR:288594
CR Number:   288594
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Linux
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Jan 2006 Fixed
Description
Cannot create LDAP connections to Repserver 12.5 on Linux



CR:288843
CR Number:   288843
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.5.0.301
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5.0.302P1 04 Oct 2002 Fixed
4.0.0 13 Aug 2004 Fixed
Description
RepAgent crashes when it tries to wrap system.log

on start up.



CR:289054
CR Number:   289054
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   12.5.0.301
Fixed Version Build Resolution Date Closure Code (If Appropriate)
4.0.4 08 Jul 2004 Fixed
12.5.0.303P2 08 Jul 2004 Fixed
12.5.0.303P2 02 Aug 2004 Fixed
5.0.00 12 Jul 2005 Fixed
4.0.4 08 Jul 2004 Presently Not Targeted For Any Future Release Of This Product
Description
ORACLE ONLY: Oracle JDBC driver 9.2.0.1.0

causes a ClassCastException. This fix changes

the schema of the XLog and requires migrating

the XLog (see below). This fix also certifies

RepAgent 12.5 against Oracle 9.2, and supports

the Oracle TIMESTAMP and INTERVAL data types.



IMPORTANT: It is NOT recommended that you use

the Oracle 9.2 JDBC driver against Oracle 8i

because it causes the loss of time precision

from DATE columns in the XLog tables. Instead,

for Oracle 8i, use the Oracle 9.0 JDBC driver.

The following drivers have been certified:



for Oracle 8i, use

9.0.1.4 JDBC thin driver for

JDK 1.2 & 1.3 (classes12.zip)



for Oracle 9i (optionally for 8i), use

9.2.0.5 JDBC thin driver for

JDK 1.2 & 1.3 (classes12.zip)



MIGRATING the XLog:

If you are creating an XLog, the new schema

will be used.



If you have an existing XLog, you must do the

following to migrate the schema:



1 - login to the RepAgent and verify that

scripts run automatically:



ra_config pdb_auto_run_scripts, true



2 - shut down the RepAgent and apply this EBF

3 - if replicating out of Oracle 9i, upgrade

your JDBC driver to 9.2.0.5

4 - start the RepAgent in ADMIN mode

5 - login to the RepAgent and issue the

pdb_xlog command with no parameters



When the command returns successfully,

migration will have been completed and you may

resume replication.



Note that, regardless of how many fixes in this

release require migration, you need migrate a

given RepAgent instance only once.



CR:289444
CR Number:   289444
Product Name:   Sybase Replication Server
Product Component:   rs_init
Status:   Closed
OS:   NA
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Jul 2002 Fixed
Description
When using a resource file (i.e. "batch" mode) to add a database to a

replication envionment, 'rs_init' reports the following OCS errors ...



CONNECTIVITY ERROR: CT-Library error: 'ct_connect(): directory

service layer: internal directory control layer error:

Requested server name not found.'.



CONNECTIVITY ERROR: Login attempt failed: server = ''.



Despite this error, the database appears to be correctly added to the

replication environment.



CR:289692
CR Number:   289692
Product Name:   Sybase Replication Server
Product Component:   rsmsrvr
Status:   Closed
OS:   HP-UX
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Aug 2009 Presently Not Targeted For Any Future Release Of This Product
Description
12.1 RSM, If you enable an event for a database, the RSM upon restart issues ERROR #49056 repserver failed to find connection: ds.db (where ds.db is your dataserver.database)



CR:290153
CR Number:   290153
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Informix
Status:   Closed
OS:   Generic
Original Version:   12.1.0.213
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.1.0.215P2 04 Oct 2002 Fixed
4.0.0 06 May 2003 Fixed
12.5.0.302P1 04 Oct 2002 Fixed
Description
INFORMIX ONLY: On Informix 9, truncation of

operations from shadow tables and tranlog table

will fail where opid_lo > 2147483647.



CR:290247
CR Number:   290247
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   Management
Status:   Closed
OS:   Generic
Original Version:   12.1.0.215P2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.1.0.215P2 04 Oct 2002 Fixed
12.5.0.302P1 04 Oct 2002 Fixed
4.0.0 06 May 2003 Fixed
Description
INFORMIX ONLY: Update-statistics parameters

(pdb_update_stats_type and pdb_update_stats_count)

are reset to default values at quiesce.



CR:290389
CR Number:   290389
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Informix
Status:   Closed
OS:   Generic
Original Version:   12.1.0.215P2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.1.0.215P2 04 Oct 2002 Fixed
12.5.0.302P1 04 Oct 2002 Fixed
4.0.0 06 May 2003 Fixed
Description
INFORMIX ONLY: Truncation appears to be stuck on

the ra_txid_seq_ table if it's busy.



CR:290674
CR Number:   290674
Product Name:   Rep Server Configuration Guide
Product Component:   Rep Server Configuration Guide
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Sep 2003 Fixed
Description
RS12.5 configuration guide Chapt 3 "Mixed-version replication systems" clarification.

Request to change topic "No RSM Client, no new features at source Replication Server"
to "No RSM Client, new features not yet implimented at source Replication Server"

Current wording could be misinterpreted that no new features were ever going to be used.



CR:292606
CR Number:   292606
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Digital UNIX
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
After appying ebf 10156 (which includes fix for CR 269228) customer still receives

_dsi_qm_free_cmd -> exc_unlink_ele



Status: Reviewed Nov 2002. Fix to be targeted (but not committed) to the 12.5.1 release.
Workaround Description
 Same as CR 269228:



Needs dsi_sqt_max_cache_size bigger enough to host all processing trans.

Options:

1. Increase dsi_sqt_max_cache_size

2. Turn off parallel DSI

3. Reduce numbers of parallel DSI threads

4. Set dsi_num_large_xact_threads to 0

5. I



CR:293092
CR Number:   293092
Product Name:   RepAgent/ASA
Product Component:   Replication Agent
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.2 3535 29 Aug 2002 Fixed
8.0.1 3035 29 Aug 2002 Fixed
8.0.0 2341 29 Aug 2002 Fixed
7.0.4 3365 29 Aug 2002 Fixed
Description
DBLTM may have sent a "use database_name" command to RepServer and RepServer would have responded with "Error 2057: Line 1, character 1: Incorrect syntax with the keyword 'use'", if the environment variable SQLCONNECT contained the key word "dbn=database_name". This problem is fixed now.
Workaround Description
 As a temporary fix, remove the environment variable of "sqlconnect"



CR:293128
CR Number:   293128
Product Name:   RepAgent/ASA
Product Component:   Replication Agent
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4505 21 Oct 2002 Fixed
8.0.2 4076 21 Oct 2002 Fixed
8.0.1 3061 21 Oct 2002 Fixed
8.0.0 2350 21 Oct 2002 Fixed
7.0.4 3381 21 Oct 2002 Fixed
Description
The ASA Replication Agent, DBLTM, was not able to replicate tables with BLOB columns that were not included in the replication definition. For replication of tables that contained BLOB columns, DBLTM would send RepServer the LTL of rs_datarow_for_writetext to describe the details of the BLOB columns. But if the BLOB columns were not defined in the replication definition, RepServer could complain "Function 'rs_datarow_for_writetext' is not defined for table 'table_name'" and then shut down the DSI thread. This problem is fixed. Now, DBLTM uses rs_insert, rs_update, or rs_delete to send non-BLOB columns, as well as to describe the details of the BLOB columns and then it uses rs_writetext to send the BLOB data.
Workaround Description
 There is none.



CR:293255
CR Number:   293255
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Solaris
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Creation repdef or subscription may take a long time due to reloading system tables into sts_cache every time a new repdef/sub is created.



CR:293856
CR Number:   293856
Product Name:   RepAgent/ASA
Product Component:   Replication Agent
Status:   Closed
OS:   Novell NetWare
Original Version:   8.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.1 3062 28 Oct 2002 Fixed
8.0.0 2351 28 Oct 2002 Fixed
7.0.4 3382 28 Oct 2002 Fixed
Description
The ASA RepAgent on NetWare (dbltm.nlm) works as expected, but when it was shut down, it would have hung forever. This then required the NetWare server to be restarted. This has been fixed , dbltm will now shut down.



CR:294146
CR Number:   294146
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
create route ... set save_interval to 'xxx' does not work.
The route create command does not update twosave column of rs_queues.
Workaround Description
 use alter route command:
alter route xxx set save_interval to 'xxx'



CR:294755
CR Number:   294755
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
21 Oct 2002 Fixed
Description
Repserver core dumps at starting time or RSI connection retry time if
Open Server or Open client tries to report errors.



CR:295856
CR Number:   295856
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   atlas
Fixed Version Build Resolution Date Closure Code (If Appropriate)
30 Sep 2002 Not a Bug
Description
Collection information is not resolved for various PDM objects. Per the online help, an example is provided for the CDM of adding a business rule to an entity. After consolidating the model, the business rule is displayed on the collections tab of the entity in the repository. If the same is done for a table, pk or fk index, then the collection is not shown. If the rule is added to a non pk or fk index or a column then the collection information is displayed.



CR:295868
CR Number:   295868
Product Name:   Sybase Replication Server
Product Component:   rs_init
Status:   Open
OS:   IRIX
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
rs_init fails to recognize raw partition on XLV or XVM devices under SGI 6.5.Recieved more information on this issue from an SGI engineer on site.



CR:295886
CR Number:   295886
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.6 06 Aug 2003 Fixed
23 Aug 2003 Fixed
Description
ASE tables modified with the ASE command ...



set identity_update <table name> on



... will not replicate properly when the table's identity column is

updated with the T-SQL UPDATE command ...



update <table name> set <identity column> = <identity value>



Under these circumstances, the Replication Server will ignore any change

to the identity column.
Workaround Description
 Please see 'Description'.



Work-around description is too large for this field.



CR:295891
CR Number:   295891
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   atlas
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Oct 2002 Fixed
EBF2 10 Oct 2002 Fixed
Description
After upgrading from PD 9.0 to 9.5, extracting, modifying and then consolidating a PDM fails to consolidate. This problem only happens when the PDM is already in the repository when the upgrade is done.



Version: PD 9.5 DBMS is Oracle 8i2, DB2 and ASA8 (This has been reproduce on each DBMS)

Steps to reproduce:

1. In PD 9.0 consolidate a PDM into the repository. (I used project.pdm)

2. Upgrade to PD 9.5 (using the web download)

3. Connect to the repository and run the update tables script. (connecting with ADMIN and DBA rights)

4. Extract the PDM model in the repository into PD 9.5

5. Make a change and consolidate it. (I changed the data type of a domain and added a table)

6. The following error message will occur:

Unexpected error while executing the following action:

Changing value of attribute Creation Date of object Group 'PUBLIC'

The consolidation of the document has been



CR:295944
CR Number:   295944
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   atlas
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
In the Repository Browser, selecting any object, you see a Versions(1.1, 1.2, 2.1) and Version Info tabs. The customer is asking to have this information combined and displayed on one tab.



CR:296164
CR Number:   296164
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Solaris
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Allow use of integer only component on a numeric datatype in a where clause (e.g. a=1 should be allowed versus a=1.0)
Workaround Description
 where clause needs to include the full decimal value: e.g. 1.0, 2.0



CR:297042
CR Number:   297042
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   NA
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Oct 2002 Fixed
23 Oct 2002 Fixed
07 Feb 2003 Fixed
07 Feb 2003 Fixed
Description
If a TEXT/IMAGE column is modified at the primary ASE via the

'writetext' command, and the TEXT/IMAGE column does not appear in any

replication definition at the Replication Server, the Replication Server

DSI will suspend with Error #32021 ("Function 'rs_datarow_for_writetext'

is not defined for table '<table>'").



CR:297048
CR Number:   297048
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   NA
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Oct 2002 Fixed
23 Oct 2002 Fixed
Description
A stack trace may occur after issuing the Replication Server command

'resume connection ... skip transaction' to skip a transaction that

contains modifications to TEXT/IMAGE columns. If a stack trace does

occur, the stack trace will contain the routine name

'_dsi_gen_textptr_init_output_cmds'.



CR:297680
CR Number:   297680
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Solaris
Original Version:   12.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Customer has many tables in a database. Some are uni-directional and some are bi-directional. Customer would like an easier way to override default action on individual tables since function strings work on entire databases.



For example, as an extension to autocorrection, per a replication definition, eliminate the command rather than delete/insert the update.



CR:297742
CR Number:   297742
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Solaris
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Provide an easy mechanism (e.g. maintenance user id, sessions setting, etc.) that would allow a customer to make massive change to the active database without it replicating to the standby database.
Workaround Description
 Currently, only way to do this is to give the user replication_role so that the user can modify the session to "set replication off"



CR:297752
CR Number:   297752
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   NA
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Provide consistent flag information between "send warm standby xacts" and "send maint commands to replicate" for warm standby listing on sp_help_rep_agent.



CR:298253
CR Number:   298253
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   HP-UX
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 23 Jan 2003 Fixed
23 Jan 2003 Fixed
Description
When there are multiple replication definitions with searchable columns for a same table and there is
where clause for subscriptions of the related replication definition, an update may not replicate at all even
though incoming data match the condition of the where clause of the subscription.



CR:298789
CR Number:   298789
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 May 2009 Presently Not Targeted For Any Future Release Of This Product
Description
With increased security, more customers are now changing their passwords on a regular basis. However, for most user changes, it requires that the Rep Server be quiesced. This request is to make it easier to change passwords on a rep server.



CR:298790
CR Number:   298790
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 11 Aug 2005 Fixed
04 Feb 2007 Presently Not Targeted For Any Future Release Of This Product
22 Dec 2005 Fixed
12.6 04 Feb 2007 Fixed
12.6 11 Apr 2008 Fixed
12.6 15 May 2008 Fixed
12.6 15 May 2008 Fixed
Description
When a Replication Server's connection

to an ASE is broken unexpectedly, the

Replication Server will attempt to

report the event. However, due to a

defect in the Replication Server, the

event is not properly processed and the

Replication Server will terminate

unexpectedly with internal error #12025.
Workaround Description
 Repserver is trying to report a CTLIB error. Restart Repserver most likely

will be OK.



CR:299074
CR Number:   299074
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   HP-UX
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Replication Server 12.5 may require increase of max_threads_proc.
Workaround Description
 Here is what one customer found:



Rep server uses 42 threads with all connections suspended. A primary connection uses 6 threads, a replicate connection used 7 (parallel DSI will make a difference), a rep agent used 4, and it took one thread to login



CR:299248
CR Number:   299248
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Digital UNIX
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Need OCS CR 212652 fixed in RS 12.1



CR:299427
CR Number:   299427
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Solaris
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.1 21 Nov 2002 Fixed
12.6 29 Jul 2003 Fixed
12.6 16 Sep 2003 Fixed
12.6 04 Sep 2003 Fixed
Description
Repserver accepts in-coming connections with encrypted passwords, i.e., isql -X.

Repserver can be configured to send encrypted passwords for out-going connections.



CR:299878
CR Number:   299878
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   NA
Original Version:   12.5.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
RS enhancement request to allow Class Level Translations to be inherited. Currently, a child function class does not inherit class level translations from the parent function class.



CR:299904
CR Number:   299904
Product Name:   Sybase Replication Server
Product Component:   rs_init
Status:   Closed
OS:   NA
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 Jan 2003 Fixed
28 Mar 2003 Fixed
Description
The Replication Serve Installation program, 'rs_init', will fail to
install a Replication Server or add a primary or replicate database to
the Replication Server if the Replication Server's RSSD, primary
database or replicate database is located on a 12.5.0.3 ASE configured
with a logical page size greater than 2KB.
Workaround Description
 Please see 'Description'.

Work-around description is too large for this field.



CR:300087
CR Number:   300087
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   12.1.0.215P2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
4.0.4 02 Aug 2004 Fixed
12.5.0.303P2 02 Aug 2004 Fixed
Description
ORACLE ONLY: Column PRIMARY_NAME in table

RA_PROCACTIVE_ is varchar(30) should be 61.

This fix changes the schema of the XLog and

requires migrating the XLog.



MIGRATING the XLog:

If you are creating an XLog, the new schema

will be used.



If you have an existing XLog, you must do the

following to migrate the schema:



1 - login to the RepAgent and verify that

scripts run automatically:



ra_config pdb_auto_run_scripts, true



2 - shut down the RepAgent and apply this EBF

3 - start the RepAgent in ADMIN mode

4 - login to the RepAgent and issue the

pdb_xlog command with no parameters



When the command returns successfully,

migration will have been completed and you may

resume replication.



Note that, regardless of how many fixes in this

release require migration, you need migrate a

given RepAgent instance only once.
Workaround Description
 drop and redefine ra_procactive_ table with column primary_name varchar(61)



CR:300169
CR Number:   300169
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 09 Mar 2004 Fixed
Description
The PINGRS utility is giving erroneous "success" messages when it has actually failed.



CR:300239
CR Number:   300239
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   Dolphin
Fixed Version Build Resolution Date Closure Code (If Appropriate)
09 Mar 2004 Not reproducible with latest version of the product available as of Resolution Date
Description
If a site's UACC for their BATCH profile of their DSNR class resource is

set to NONE, SETUP00 must contain SYSADM parameter.



CR:300673
CR Number:   300673
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   Dolphin
Fixed Version Build Resolution Date Closure Code (If Appropriate)
09 Mar 2004 Not reproducible with latest version of the product available as of Resolution Date
Description
DRL@LGGX of size 000155D0 uses high CPU



CR:300677
CR Number:   300677
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   Dolphin
Fixed Version Build Resolution Date Closure Code (If Appropriate)
09 Mar 2004 Not reproducible with latest version of the product available as of Resolution Date
Description
PREV QID is after CURR QID



CR:300849
CR Number:   300849
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   LTI Driver
Status:   Closed
OS:   Generic
Original Version:   12.5.0.302P1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5.0.303P2 08 Jul 2004 Fixed
4.0.1 06 May 2003 Fixed
4.0.1 08 Jul 2004 Fixed
5.0.00 13 Jul 2005 Fixed
5.0.00 12 Oct 2005 Fixed
Description
Request override capability for charsets. The

ability already exists in RepAgent to set the

various connections' charsets except for

RepServer's. So, rs_charset has been added as

a configurable property.



NOTE that, just because RepAgent provides a

pds_charset property, it does not mean that the

charset will actually be set at the vendor's

JDBC driver. Most vendor JDBC drivers provide

no way of setting the charset.



CR:300910
CR Number:   300910
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
modification of save interval on a warm standby logical connection only affects outbound queue of logical connection
Workaround Description
 update twosave value of rs_queues table. Should only update the value

for Warm Standby inbound queues. The value is measured in seconds.



CR:300912
CR Number:   300912
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
21 Nov 2002 Fixed
Description
Attempting to turn on STS,GENERAL_1 trace may produced a stack trace.



CR:300966
CR Number:   300966
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   NA
Original Version:   12.5.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
21 Jul 2008 Third Party Problem
Description
RS hangs if RSSD log is full; when RSSD_prim stuck due to "Log Suspend"



Feature request to return message if RSSD log full to RS.log to help diagnose RS hang problems.



CR:301141
CR Number:   301141
Product Name:   Sybase Replication Server
Product Component:   rs_init
Status:   Open
OS:   NA
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Feature Request to embed RS version string within all scripts.
(ie. on $SYBASE_REP/scripts)



CR:302193
CR Number:   302193
Product Name:   Sybase Replication Server
Product Component:   rs_init
Status:   Closed
OS:   Linux
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
08 May 2003 Fixed
Description
Repserver does not support raw partitions with the "add partition" command. Raw partitions are also not supported by rs_init: the raw partition name entered into the partition-name field of rs_init is summarily rejected by rs_init. rs_init waits for you to input another value but no value is accepted.



CR:302309
CR Number:   302309
Product Name:   RepConnector
Product Component:   Misc.
Status:   Closed
OS:   Generic
Original Version:   2.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2.0 18 Dec 2002 Not a Bug
Description
After the first tibco CM message is sent the the queue, the repconnector transaction hangs.



CR:302546
CR Number:   302546
Product Name:   Sybase Replication Server
Product Component:   rsmsrvr
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
08 May 2003 Fixed
Description
RSM 12.5 dies when an event script is triggered

ERROR #44048 dSERVICE( ) - /sysproc.c(189)
Error occurred while waiting for a child process.
Exiting due to a fatal error



CR:302911
CR Number:   302911
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   all
Original Version:   Mercury
Fixed Version Build Resolution Date Closure Code (If Appropriate)
26 Feb 2003 Fixed
Description
Consolidation attempt of the attached *.oom to the 9.5.0 repository installed on DB2 v. 7.2 fails with [IBM][CLI Driver]CLI0120E Memory allocation error using DB2 driver OR fails with [Merant][ODBC DB2 driver][DB2] X396 Literals are not supported as stored procedure parameters;using Data Direct 3.7.0 driver.



Using the Data Direct 4.1 DB2 Wire Protocol driver in 9.5.1 fails with the following error:

[DataDirect][ODBC DB2 Wire Protocol driver][DB2]L964 SQLSTATE = S1000



CR:303094
CR Number:   303094
Product Name:   RepAgent/ASA
Product Component:   Replication Agent
Status:   Closed
OS:   Generic
Original Version:   5.5.05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4552 12 Dec 2002 Fixed
8.0.2 4095 12 Dec 2002 Fixed
8.0.1 3087 12 Dec 2002 Fixed
8.0.0 2358 12 Dec 2002 Fixed
Description
If a shutdown request came in after DBLTM has completely scanned the active transaction log, DBLTM could complain "Shutdown caused by fatal error". However the shutdown was actually requested by the user. This has been fixed.



CR:303451
CR Number:   303451
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Unknown
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 Jan 2003 Fixed
28 Mar 2003 Fixed
Description
When Replication Server DSI applies the following new 12.5.0.3 ASE T-SQL

command to a 12.5.0.3 ASE ...



set identity_insert ...



... the 12.5.0.3 ASE returns the following new informational (i.e.

severity 10) message to the Replication Server DSI ...



Message: 11065, State 1, Severity 10

''SET IDENTITY_INSERT' is ON for table '<table>'.



The Replication Server DSI will stop when encountering this

informational message because, by default, 12.5 Replication Server (as

well as earlier versions) does not define an error action for this new

informational message. If no error action is defined for any message,

informational or otherwise, the default action for the Replication

Server DSI is to stop.
Workaround Description
 Apply the following commands to the RS which is applying commands to the 12.5.0.3 ASE:

create error class rs_sqlserver_error_class

assign action ignore for rs_sqlserver_err

Once this is done, RS will ignore the 11065 message.



CR:303462
CR Number:   303462
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   Dolphin
Fixed Version Build Resolution Date Closure Code (If Appropriate)
EBF112P3 17 May 2005 Fixed
Description
Rep Agent self-initiates a "normal" shutdown sequence on it's own.



CR:303468
CR Number:   303468
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 09 Mar 2004 Fixed
Description
If Codepage is specified as CP500,force,utf8 and replication is done from the DB2 CHAR/VARCHAR to ASE UTF8 CHAR/VARCHAR , and DB2 string has unprintable chars, then replication won't happen.

Workaround (prior to EBF 10867) is to substitute unprintable chars for X'40' (space) or any other printable symbols.



CR:304308
CR Number:   304308
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   NA
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
03 Dec 2008 Fixed
Description
Replication of 'create table' fails if that warm-standby table has a reserved word... because 'set quoted_identifier on' is not replicated. Therefor, standby unable to create table due to error.



This is also problem for any/all reserved words replicated by RS: insert, update, delete... Not just 'create table'



CR:304315
CR Number:   304315
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   NA
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Default behavior of warmstandby is to use all columns of table to generate
where clause. This is bad if timestamp is one of those columns. In that case, because timestamp value different at standby database than active, where clause for update and delete commands fail to effect any rows.

Workaround is to create repdef for standby table do not include timestamp as part of primary key set



CR:304551
CR Number:   304551
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   NA
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
rs_helprep lists replication definition twice when logical connection name and physical connection name are the same.



CR:304733
CR Number:   304733
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   Log Reader
Status:   Closed
OS:   Generic
Original Version:   4.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
4.0.1 05 Oct 2004 Fixed
12.5.0.303P2 22 Nov 2004 Fixed
Description
Varchar primary key on primary table breaks LOB

replication with a syntax error.



CR:304998
CR Number:   304998
Product Name:   Sybase Replication Server
Product Component:   rsmclient
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Aug 2009 EOL'd version. Not to be Fixed.
Description
subscriptions displayed in RSM client that have a period in the name will shutdown Sybase Central.
Workaround Description
 Do it all in isql



CR:305419
CR Number:   305419
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   NA
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
admin stats_intrusive_counter, { 'on' | 'off' } is RS 12.5, and plural (admin stats_intrusive_counters, { 'on' | 'off' } ) in RS 12.1.
Workaround Description
 For RS 12.1, the command is admin stats_intrusive_counters, { 'on' | 'off' }. For RS 12.5, the command is admin stats_intrusive_counter, { 'on' | 'off' }



CR:305420
CR Number:   305420
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   NA
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Jan 2003 Duplicate
Description
admin stats_intrusive_counter, { 'on' | 'off' } is RS 12.5, and plural (admin stats_intrusive_counters, { 'on' | 'off' } ) in RS 12.1.
Workaround Description
 For RS 12.1, the command is admin stats_intrusive_counters, { 'on' | 'off' }. For RS 12.5, the command is admin stats_intrusive_counter, { 'on' | 'off' }



CR:305550
CR Number:   305550
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   neptune
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Oracle replication is incompatible with some datatypes used in two tables of the repository installation script

Table PMLBIN and Table PMXFIL

Datatype Long Raw

So to be able to replicate all columns datatype, long raw has to be replace by : LOBs (CLOBs).



CR:306800
CR Number:   306800
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Solaris
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.1 25 Mar 2003 Fixed
10 Aug 2005 Fixed
12.6 14 Aug 2003 Fixed
Description
Install RS an attention event handler. If a Rep Agent orRSI User

tries to break its connection while Repserver waits for the

completion of some tasks, an attention event can bring Repserver

back to handler the disconnection event. This may prevent Rep

Agent or RSI thread hang.
Workaround Description
 If network is setting correctly, recycle Repserver should

make Rep Agent stop.



CR:306842
CR Number:   306842
Product Name:   Sybase Replication Server
Product Component:   rsmsrvr
Status:   Closed
OS:   HP-UX
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 May 2003 Fixed
05 Apr 2004 Fixed
Description
The use of RSM events to trigger user-defined actions does not work correctly in RSM 12.5 on the HP platform and causes RSM to hang or unexpectedly terminate.



CR:307456
CR Number:   307456
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Solaris
Original Version:   12.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
If regular replication is set up first and the identity is mapped to numeric, the warm standby replication definition is not used.
Workaround Description
 Build a warmstandby replication definition first, then build replication definition for regular replication.



CR:308078
CR Number:   308078
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
Rep Server stacks when replicating text to char or varchar.
Workaround Description
 Change the datatype of the offending column at the target to something that is compatible with text and then bring up the Rep Server (no change to replication definition or subscription in this case).



or Suspend dsi and purge/skip trasaction inthe que





--------------------------------------华丽的分割线-------------------------------------------------------------------------

Sybase SQL Anywhere数据库恢复工具ReadASADB:

之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具: ReadASADB。
此工具支持ASA v5.0, v6.0, v7.0, v8.0, v9.0, v10.0, v11.0, v12.0, v16.0, v17.0等版本。
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具。
恢复Sybase SQL Anywhere的工具在国内处于领先水平。

Sybase SQL Anywhere数据库恢复工具ReadASADB功能
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具
  1. 适用于所有的SQL Anywhere版本    包括:5.x,6.x,7.x,8.x,9.x,10.x,11.x,12.x,16.x,17.x
  2. 适用于所有的UltraLite版本
  3. 能够恢复出来表结构和数据
  4. 能够恢复自定义数据类型
  5. 能够恢复存储过程等对象的语法
  6. 能够导出到目标数据库
  7. 能够导出到SQL文件并生成导入脚本
  8. 支持多种字符集,包括:cp850、cp936、gb18030、utf8等
  9. 能够恢复未加密或者简单加密类型的数据
  10. 简单易用
  11. 限制:不支持AES加密的数据文件
请参考:研发成功了从Sybase SQL Anywhere的DB文件上恢复数据的工具
            SQL Anywhere数据库非常规恢复工具ReadASADB使用介绍

Sybase SQL Anywhere数据库恢复工具ReadASADB适用场景

各种误操作:

  1. 误截断表(truncate table)
  2. 误删除表(drop table)
  3. 错误的where条件误删数据
  4. 误删除db或log文件
  5. 误删除表中的字段

Sybase SQL Anywhere数据库恢复工具ReadASADB的应用场景:

1.因为物理磁盘故障、操作系统、系统软件方面或者掉电等等原因导致的Sybase SQL Anywhere数据库无法打开的情况;
2.误操作,包括truncate table,drop table,不正确的where条件导致的误删除等;
Sybase SQL Anywhere无法打开时,比较常见的错误是:Assertion failed。
如:
1、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Checkpoint log: invalid bitmap page -- transaction rolled back
2、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Page number on page does not match page requested -- transaction rolled back
3、Internal database error *** ERROR *** Assertion failed:200502 (9.0.2.2451) Checksum failure on page 23 -- transaction rolled back
4、File is shorter than expected
5、Internal database error *** ERROR *** Assertion failed: 201116 Invalid free list index page found while processing checkpoint log -- transaction rolled back
6、*** ERROR *** Assertion failed: 51901 Page for requested record not a table page or record not present on page
7、*** ERROR *** Assertion failed: 201417 (7.0.4.3541) Invalid count or free space offset detected on a table page
8、Internal database error *** ERROR *** Assertion failed: 201425 (8.0.3.5594) Invalid count or free space offset detected on a free list page -- transaction rolled back.
9、Internal database error *** ERROR *** Assertion failed: 100702 (8.0.1.2600) Unable to modify indexes for a row referenced in rollback log -- transaction rolled back


-------------------------------------------------------------------------------------------

Sybase ASE数据库恢复工具READSYBDEVICE:

一个不依赖数据库管理系统、直接从Sybase数据库设备文件上提取数据的业内领先的恢复工具!
能够从损坏的Sybase ASE设备文件(.dat)上提取数据的非常规恢复工具。

Sybase ASE数据库恢复工具READSYBDEVICE的主要功能:

  1. 被勒索病毒加密数据文件及备份文件情况下的恢复;
  2. 系统崩溃只剩下数据文件的情况下的恢复,甚至数据库文件不存在而只有损坏的备份文件情况下的恢复;
  3. 因断电、硬盘坏道等造成数据库文件损坏情况下的恢复;
  4. delete数据恢复、误update数据恢复、误删除表(drop)恢复、误truncate表恢复 等;
  5. 各种Sybase内部系统表损坏、索引错误的修复;
  6. master数据库损坏而无法正常运行情况下的恢复;
  7. Sybase数据库被标记为可疑,不可用等情况的恢复;
  8. Sybase数据库中数据文件内部出现坏块情况下的恢复;
  9. Sybase数据库无数据文件但有日志文件的情况下的恢复;
  10. Sybase数据库只有数据文件无任何日志文件的情况下的恢复;
  11. Sybase数据文件被误删除情况下的碎片提取恢复;
  12. 磁盘阵列上的Sybase数据库被误格式化情况下的数据库恢复;
  13. 数据库sysobjects等系统表损坏无法正常应用情况下的恢复;
  14. Sybase数据库还原数据库出现失败情况下的恢复;
  15. Sybase数据库只剩下损坏的备份文件情况下的恢复。

Sybase ASE数据库恢复工具READSYBDEVICE支持的版本:

Sybase ASE 11.0.x,11.5.x,11.9.x,12.0.x,12.5.x,15.0.x,15.5.x,15.7.x,16.0.x


-------------------------------------------------------------------------------------------

SQL Server数据库恢复工具SQLRescue:

一个不依赖数据库管理系统、直接从SQL Server数据库文件上提取数据的业内领先的恢复工具!
能够从损坏的SQL Server数据库文件(.mdf)上提取数据的非常规恢复工具。

SQL Server数据库恢复工具SQLRescue的主要功能:

  1. 系统崩溃只剩下数据文件的情况下的恢复,即无日志文件或者日志文件损坏情况下的恢复;
  2. 断电导致数据库文件损坏情况下的恢复;
  3. 硬盘坏道造成数据库损坏情况下的恢复;
  4. 数据文件内部存在坏页情况下的恢复;
  5. 企业管理器误删除数据表记录,管理软件误删除数据表记录的恢复;
  6. 并闩锁错误、格式化、误删除后导致软件不能使用的情况;
  7. 无法读取并闩锁页sysindexes失败情况下的修复;
  8. 数据文件被误删除情况下的碎片提取恢复;
  9. 系统表损坏、索引错误、误删除数据库表、删除记录的数据找回;
  10. master数据库损坏而无法正常运行情况下的恢复;
  11. 数据文件无法附加情况下的数据恢复;
  12. 数据库被标记为可疑,质疑,不可用等情况的恢复;
  13. 数据库sysobjects等系统表损坏情况下的恢复;
  14. 数据被误(drop、delete、truncate)删除表数据的恢复,误update后的数据恢复等;
  15. 还原时报一致性错误,错误823等情况下的数据恢复,各种错误提示的数据库文件修复;
  16. 数据库被误格式化等情况下的数据库恢复;
  17. 日志收缩造成数据库损坏情况下的恢复;
  18. 仅剩损坏的备份文件情况下的恢复。

SQL Server数据库恢复工具SQLRescue技术特点:

只要SQL Server数据库的数据文件存在,我们就有办法帮您从数据文件中找回重要数据。
  1. 从数据文件中直接恢复数据
  2. 不能附加时直接恢复数据并生成新的数据库
  3. 系统表损坏的数据库修复
  4. 快速修复SQL 823错误、连接中断错误

SQL Server数据库恢复工具SQLRescue支持的版本:

Microsoft SQL Server 7.0, 2000, 2005, 2008, 2008R2, 2012, 2014, 2016, 2017,2019。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------