Sagent Data Flow Solution


This readme is designed to help you find resolved issues, known issues, and compatibility information more efficiently. The features of this format are:

  • Use the navigation links on the left for quick access to each section of the readme without scrolling through dozens of pages of information.
  • Use the Tabs to access the current release and legacy information. The Sagent Data Flow Solution Version 6.8 tab contain details for version 6.8 GA and subsequent patch releases. The Legacy Known Issues tab contain known issues from previous Sagent Data Flow versions.
  • You can filter data for resolved issues, pre-requisites, enhancements, internationalization/localization, and known issues. Each table now includes a list button and text boxes in each column so that you can filter by patch or perform a full-text search of the table you are viewing.
  • The text search now support filter as you type and search string highlighting.

    The current format has filters based on various criteria. For example,
  • Server - Select the relevant type from the drop down list and the relevant issues are filtered and displayed.
  • Description - Type a string and the relevant issues are automatically filtered and displayed, with the search string highlighted. For example, if you type “transform” in the Description column text box of the Known Issues table, you will automatically get a list of all known issues related to transforms.

2009-2013 Pitney Bowes Software Inc. All rights reserved.

Copyright Notice

Best viewed in Internet Explorer 7.0 and above

Updates in this Patch Set

This section gives a brief summary of the updates made in the current patch set.

Readme Section Updated Update Summary
Before you Start Added seven General information and one Pre-requisite item.
Automation Updater Updated to the latest.
AIX 7.1 Installation Updated to the latest.
Resolved Issues Added one resolved issue.
New Features, Enhancements and Platform Certifications Added one Enhancement and four New Platform Certifications.
Known Issues Added two Known issues.
QA Environment Section updated with the latest QA matrix.
Cab File Version Cab File Version updated to the latest.

The following documents were also updated:

  • Transforms Reference Guide version 6.8
  • Sagent Install Guide version 6.8
  • Automation Updater Guide version 6.8

You can download the latest copy of these documents from:

Automation Updater

A new release of Automation Updater for Opalis 4 is now available with 6.8.3 patch. Please contact technical support for more information.

Known Issues: Generic

This section lists the Generic known issues in Sagent Data Flow version 6.8.

S. No Description

Advanced XML Source Transform does not support recursive and inline XML schema files.


Irrespective of user rights, sequences or caches created using the Primary Key Generator are visible to every user of the system.


In Advanced XML source Transform, de-selecting Preserve relationship between different Entities removes the schema relationships between the entities and flattens the XML view in the Entity Tree. Selecting it again recreates the relationships but the surrogate keys in the Attribute Details Grid remain de-selected.

Workaround: In the Entity Tree, de-select and again select the associated entities.


In Advanced XML Sink Transform, if the following characters appears in an XML or XML schema (XSD) tag name, they will be replaced by an _ (underscore):

<Space>  <  >  &  \  "  '  ,  /  ?  ;  |  {  }  [  ]   +   =   (   )   *   ^   %   $   #   @   !   ~   `   \t  

Schedule a task (to execute a plan) using the Windows AT command. Once the plan is executed, clicking Cleanup Repository tab in Sagent Admin results in the following error:

Unspecified Error

Workaround: After the plan executes, remove the scheduled task from Windows Task Scheduler library.


A plan is created using the Advanced XML Sink Transform and a source transform. Now if an additional Advanced XML Source Transform is added to the existing plan, the hierarchy mappings from the new Advance XML Source Transform will not be reflected in Advanced XML Sink.

Workaround: Delete and add the Advanced XML Sink and create the plan again.


Even if a query is able to fetch data from Oh-Pa, both Oracle and the Oh-Pa Service should be up and running, else the plans will fail.


In Oh-Pa, existing baseviews, metaviews and plans will not work. You will have to recreate new baseviews, metaviews and plans.


In Oh-Pa, for columns with an integer or float data type, the value of NULL is treated as 0.


Schemas in both the Oracle and Oh-Pa databases should be compatible for Oh-Pa to work. The following conditions must be fulfilled:

  1. The order of columns in the tables should be same for both Oracle and Oh-Pa databases.
  2. Basic data types of corresponding columns should be same. The only exception in this case is that a column defined as String in Oh-Pa can be defined as Date in Oracle.
  3. Sagent treats decimal and float data types as double for an Oh-Pa database even if the data is fetched from Oracle through query redirection.

In Oh-Pa, query redirection will not happen if Oh-Pa returns even a single record. For example the following types of queries are not supported:

SELECT DATA from TABLE where MM = JAN(Oh-Pa) or MM = AUG(Oracle)

If the length of data defined in ohpa.env is less than the actual length of data in the CSV file, Oh-Pa would truncate the data to the length in the ohpa.env file before loading it.


In Oh-Pa, queries of the following form will not work:


You must provide a specific element to be fetched. For example:


Advanced XML Source Transform does not support XML schema files (XSDs) that uses the Redefine element tag to edit element in an included or imported schema file.

Workaround: Edit the included or imported schema file to change the required schema definitions.


In Advanced XML Sink Transform, selecting a different parent entity using the Entity Details dialog and then trying to revert back the change will result in an error.

Workaround: Click Cancel and start over again.

16 If Typed In is selected from the User Input dropdown during prompt creation, then plan prompt BLANK is not displayed on Weblink client.
17 The Red Brick Batch Loader TMU files are now stored in a folder TMU in the system TEMP folder. These files are sometimes not deleted after the plan execution as they ideally should be.

Workaround: You must delete these files manually from the system TEMP folder.
18 If a linked component plan contains steps that were copied from the plan using it and the copied steps exist in both the main plan and the linked component plan then it can cause issues and the plan output may not be as expected.
19 If you create a plan with copies of a linked component in one flow and pass custom plan properties to the copies, you may not get the correct output.

Workaround: Move other copies of the same linked plan in the SubPlan (using the Move Into new Subplan option) residing under one flow.
20 If Sagent Admin and Data Flow Server are installed on different machines (with the Data Flow server on Windows 2008), the Error 5 error message is displayed while trying to register the Data Flow Server in Sagent Admin.

Workaround: Access the Data Flow server machine once from the machine on which Sagent Admin is installed. Once you are authenticated, the Data Flow server will be successfully registered in Sagent Admin.
21 If multiple Transforms are connected to the same Base View in a plan and the Base View connection parameters are changed, you will need to modify/change the BaseView connection parameters for every Transform separately.
22 On UNIX, while executing a plan using SARUN to generate a columnar report, Data Flow server crashes if the path provided for saving the columnar report is invalid (non-existent).
23 When a baseview is exported from a source repository and imported in a target repository without exporting and importing the linked metaview/s, the plans using these baseviews will not execute.
24 While creating baseview for Directlink, the following error occurs:
Invalid Columns This is because some lines in the Directlink DAT file contains commas within columns due to which they are not parsed.
25 On Windows 7 with UAC enabled:
  • If you execute a partial or full export using SARPUTIL with administrator privileges, the exported CSV file is created.
  • If you execute the export as a standard user, no exported file is created.
This is a known issue for a standard user. You can use any of these workarounds to fix the issue for a standard user:
  • Use a directory where the user has write permissions e.g. My Documents, Desktop, etc
  • Explicitly choose run as administrator
  • Disable UAC (On choosing this option the user will get proper error messages)
26 VB ScriptSource and Sink transforms are not supported on the Windows Server 2008 platform.
27 Using SARUN, multiple plans can be executed in parallel if the base view properties (Database, Server, TableOwner, Login and Password) are set at runtime, with the following limitations:
  1. TableOwner property can be set to BLANK at runtime using SARUN command.
  2. In case of plans containing SQL Query Transform and having a simple query (query formed using a single table) created using drag and drop:
    • All the baseview properties (Server, TableOwner, Database, LoginID and Password) can be set at runtime when using SQL Server and Sybase.
    • Only Server, TableOwner, LoginID and Password can be set at runtime when Databases like DB2 and Oracle are used in reference to the query created from BaseViews.
  3. In case of plans having handwritten queries, both simple and complex (query formed using two or more tables):
    • Only Server, LoginID and Password can be set at runtime.
  4. In case of plans having a complex query created using drag and drop, Step property cannot be set at runtime using SARUN.
  5. Plans created using Sybase baseview and containing two or more SQL Query Transforms connected with a union might not execute, if Step property is set at runtime using SARUN.
28 If the Data Flow Server is installed on a Windows 2008 machine (32-bit or 64-bit) with UAC (User Account Control) enabled, and Sagent Admin is installed on a Windows XP machine with Service Pack 2, the Data Flow Server cannot be started or stopped using the Sagent Admin.
29 Plans containing Advanced Matcher Transforms returns the following error when run in parallel:
Error while processing the data for the step 'Advanced Matcher'
30 Centrus transforms are not loaded in the Tools bin of Sagent Design Studio after installing the 32-bit client (from the 32-bit installation package) with a 64- bit server.

Workaround: Install the 32-bit server (from the 32-bit installation package) and not the client setup on the 32-bit client machine to be used with the 64-bit server setup.
31 For Centrus Transforms, the transform DLLs registered under 64-bit installation will not be automatically unregistered on uninstalling the respective Centrus Transform.
32 For Centrus Transforms, if a 32-bit client is installed on a 64-bit machine already having a 64-bit server, the installation entry for the 64-bit server under Control Panel > Add/Remove Programs will be overwritten by the client install. Uninstalling from the Control Panel will only remove the 32-bit client installation and not the 64-bit server components.

The same is true for the other case where 32-bit client components are installed first and then 64-bit server installation is done. In this case, uninstall will only remove the 64-bit server components and not the 32-bit client.
33 In WebLink, while working with two analysis plans, the WebLink client gets terminated when one plan is executed using the drill through link of the other and the Analysis column is clicked.

Workaround: In global.asa, change the value of Session("TargetFrame") from:
Session("TargetFrame") ="_blank"
Session("TargetFrame") ="_self"
34 On Windows Server 2008, Weblink does not work when run on Netscape 8 and 9. It works fine on Netscape 8 if the following settings are made in the browser configuration:
  1. Open Netscape browser; go to Tools > Options > Site controls.
  2. If the required WebLink URL already exists under my settings window then remove that URL, as the required options might not have been set properly for this existing URL when it was added initially.
  3. Add the WebLink URL (for example: to my settings with the “Initial trust settings” option set to "I trust this site".
  4. For the added URL set the “Rendering engine” option to Internet explorer.
  5. Select the options for:
    • Enable Java
    • Enable JavaScript/VBscript
    • Enable ActiveX
    • Allow site to run programs
    • Allow unrequested pop-up windows
    • Open requested pop-ups in new tab
    • Allow images to be displayed
  6. Set these options also for the WebLink URL appearing under plus sign in my settings panel.
  7. Save the new settings and close the Netscape browser. This is very important as the new settings won’t come into effect without closing the old browser.
  8. Open a new browser and execute the plans; plans should run successfully after following the above steps.
35 On Windows 2008 Server, you can install Sagent Data Flow Solution with UAC (User Account Control) enabled but there are issues with starting/stopping and registering DFS and WebLink services:
  1. 32-bit Windows 2008 Server with UAC enabled:
    - No problems were observed during installation of GA and patch
    - Sagent WebLink service does not get started automatically
    - Data Flow Server cannot be started and stopped from Sagent Admin
    - User has to start DFS and WebLink service manually from Services Manager
  2. 32-bit Windows 2008 Server with UAC disabled – the following changes are observed:
    - Sagent WebLink service starts automatically
    - Data Flow Server can be started and stopped from Sagent Admin
  3. 64-bit Windows 2008 Server with UAC enabled:
    - No problems were observed during installation of GA and patch
    - DFS cannot be registered in Sagent Admin on any other machine
  4. 64-bit Windows 2008 Server with UAC disabled:
    - Same user is able to register the DFS in Sagent Admin
36 To run utilities on Windows 2008 Server, you need to either disable the UAC (User Account Control) or manually permit them to run for the first time.
37 On Windows 2008 Server, UAC (User Account Control) is enabled by default and it prevents SARPUTIL from working. To make SARPUTIL work, you have to either disable UAC or manually grant permission to SARPUTIL.

To grant permission to SARPUTIL:
  1. Open sarpcmd.exe in the Sagent installation folder.
  2. Click Allow when prompted for permissions.
38 On Windows 2008 Server, UAC (User Account Control) prevents SARPUTIL help from working.
39 On Windows 2008 Server, if the thin clients are set to ON and you execute a plan containing reports, the results would be displayed as continuous text along with the following warning message
Ask your administrator to setup the weblink server for thin clients
Whereas with the same settings on Windows 2003 server it displays the results in a tabular format.
40Microsoft Excel 2007 supports XLS and XLSX file types. You cannot convert/save an XLS type file to XLSX or vice versa using the Excel Sink Transform.
41In the Excel Sink Transform, the New, Open, and Save buttons on the MS Excel 2007 toolbar are enabled but not functional.
42A plan containing a macro enabled MS Excel 2007 excel sheet is created using the Excel Sink Transform. If you right click on the Excel Sink Transform and click Settings twice in a row, the following errors messages are displayed: Cannot rename file. Cannot read from source file or disk. Excel Sink: Failed while saving the File. File has wrong format or hidden macro in the file.
43In the French environment, the Add column transform doesn't generate the correct output value for a decimal column, containing a default data with proper precision and scale. Example: Precision=7, Scale=2, Default value=10334.56. Output displays nothing.

Known Issues: 64-bit Specific

This section lists the 64-bit specific known issues in Sagent Data Flow version 6.8.

S. No. Description
1 In the French environment, IgnoreSystemLocale does not work properly when the Data Flow Server is running on Solaris.
2 On upgrading from Sagent v4.5, the WebLink server was crashing for users other than sa. The workaround here is to manually change the data type of the column attribute_number in the sarp_obj_attr repository table from smallint to int.
3 The Use Existing feature in Add Columns transforms is non-functional.
4 In Flat File Source, a signed negative Decimal data having precision 38 doesn't get processed. However, the same data gets processed through Delimited File Source, successfully.
5 In Add Column transform, an improper error message is displayed: Invalid length. Maximum field lengths can be overridden through a registry entry. This happens when a string column of length 0 is added. The same error message is displayed when the string length crosses the upper limit.
6 When Add Column transform is used to add a Decimal data type column and the initial value provided is such that it is larger than the precision value and also precision value is equal to the scale then incorrect data is found in the output. Similarly, if the initial value is smaller, then the precision and scale values are the same the output data is incorrect. For example, if 3 is selected as scale and precision value and the initial value of 1212.121213 or -.1 is provided.
7 In Analytical Calculator transform, a logical expression true XOR false does not return 0 all the time and on repetitive execution may return 1.To overcome this issue, please use either 0 or 1 instead of false and true.
8 In Analysis transform, when null data of Long data type is organized as a row then it is displayed as 0 instead of blank or null.
9 A plan having Column Select and Excel transforms, displays incorrect output in specific scenarios as mentioned below:
Scenario 1: Create the plan such that the data in the Column Select transform contains a column of date-time data type followed by an integer/ unsigned integer/long data type. Now, remove the date-time column using Column Select and execute the plan. Excel will contain incorrect output in the integer/unsigned integer/long column.
Scenario 2: Use the same plan with more columns in the Column Select but ensure the order of an integer /unsigned integer/long column should be after the date-time column. Now, remove the first column of the Column Select transform and execute the plan. Excel will contain incorrect data in the integer/unsigned integer/long column, which is next to the date-time column. Please note, these scenarios will only be replicated with Excel as a Sink transform and the data in the date-time column should have a proper date with time. Workaround: Change the Columns in the Column select Transform first. Then delete the existing Excel and drag a new Excel. It will solve the problem.
10 In Concatenation transform, if a column of data type Unsigned Int contains a value greater than the max range of int i.e., 2,147,483,647 and if any string is concatenated with this column, then incorrect output is displayed.
11 In DTFS source transform, an empty column value is taken as an empty string and not as NULL. For using NULL check related functionality, Flat File Source can be used.
12 In Conditional Splitter transform, the value field is allowed data up to 6 decimal places. Inserting data more than that length rounds the value.
13 In transforms like Filter and Filtered Splitter, when Regular Expression is checked with String type input, the operator list changes to is equal to and is not equal to. However, when the input column is changed to integer type, the operator list doesn't get refreshed properly and remains the same.
14 In Flat File Source transform, if there is an input column of date data type with format MM/DD/YYYY and in the Processing tab, the Date Conversion Mask drop-down is selected as DDMMYYYY, displays the following error: Invalid Date Processed. But if the YYYYMMDD format is selected, the plan gets executed fine without any error.
15 When using the Use Existing Field feature of Moving Average transform, the moving average for negative integer data does not get calculated correctly. It is incremented by 1 and the rest gets calculated accordingly.
16 For Time Lookup transform, the input column should be date-time data type. However, it allows string data type as well.
17 When using the create a new excel workbook option in Excel transform, and the Overwrite the existing file when the plan is saved option in the Excel Property dialog, with the Include data check box checked after specifying the file path of an existing Excel file for Excel transform and executing the plan may not generate data in the Excel Workbook.
18 Disk Sort may not sort data correctly above the following ranges:
  • Integer range: -1000000000 to +1000000000
  • Unsigned Integer range: 2000000000
19 In Expression Calculator transform, every String column added using Add Columns transform of length 1, shows a default length 2.
20 When using IsDecimal () method of Expression Calculator on a column having '+ or'/ '- or' / '.or' or directly using '+', '-', '.', '+', '-', '.' with the function in Expression Calculator produces '1' as the output.
21 In Expression Calculator, an expression like, "" returns a length of 199 in the Property dialog.
22 In Expression Calculator transform, if an expression created with PadRight () / PadLeft () is used, the length returned is incorrect. The problem occurs when fixed length is used and the length returned is not that of the fixed length but the complete string length.
23 In Expression Calculator transform, for TrimLeft () function returns the length inclusive of the trimmed space characters.
24 Memory sort may not sort data correctly above the following ranges:
  • Integer range : -1000000000 to +1000000000
  • Unsigned Integer range : 2000000000
25 When using the Use Existing Field feature of Running Average transform, the running average for negative integer data is not calculated correctly. It is incremented by 1 and the rest calculated accordingly.
26 Repository creation in Sybase database, in French and Japanese locale, fails generating the following error: Error converting characters into server's characters. Some characters could not be converted.
27 In SQL Query transform, on opening the SQL Editor dialog and clicking OK, reduces the length of the String data type columns by 1. The reduced length can be viewed in the SQL Editor when it is opened again. This happens every time this operation is performed. However, this does not result in loss of data.
28 In Delimited Text File Source and Flat File Source transform, removing columns from first or middle misaligns the data. However, it works fine when columns are deleted from the end.
29 In case of default error value in Key Lookup transform, if the value is set from Custom Plan Property dialog, the default value will be set for the first column mapping and not for the rest of the mappings. Moreover, it will not be displayed in the List of column mappings in the Properties dialog of Key Lookup transform.
30 When a plan is exported from one repository and imported onto another repository where the BaseView used in the exported plan is not present, the plan runs as long as the Key Lookup dialog is not opened until the user presses OK. This is because the BaseView information is saved in the plan and is only verified again if the user opens the dialog of the Key Lookup step. The behavior exists in earlier versions too and is a documentation entry only.
31 Performing the followings steps creates a plan folder automatically:
  1. Create a Private ‘PV1’plan folder and a Public ‘PU1’ plan folder in the Design Studio - Plan bin.
  2. In the Private folder ‘PV1’, create another Private folder ‘PV2’, and in the Public folder ‘PU1’, create another Public folder ‘PU2’.
  3. Now move the inner most Private folder '‘PV2’ to Public folder ‘PU1’. Then move it back into the Private folder '‘PV1’.
  4. A new folder is automatically created in the Public plan folder ‘PU1’. However, operating it vice-versa does not create any new folder automatically.
32 In SAINRP, if the View Log button is clicked, an error message is generated if the software Active Perl is not installed in the client system.
33 Using invalid value in the Use existing schema option of Delimited Text File Sink transform does not generate any error. The plan is completed successfully.
34 In Expression Calculator transform, using a Right() function and creating an expression like, Right( InitCaps (Concat ('EXPRESSION', Added_Column), 0), 7) where, Added_Column is a string column added through Add Column transform, which has the initial value Sagent results in Sagent as output instead of NSagent.

The workaround is to break this expression into a smaller expression like use an InitCaps (Concat ('EXPRESSION', Added_Column), 0) and then use a new Expression calculator transform later in the flow to create an expression with Right () function to get the desired result.
35 Using invalid value in the Use existing schema option of Fixed Width File Sink transform does not cause any error. The plan is completed successfully.
36 In Expression Calculator transform using the function dtIsFormattedDate and creating expressions like the following result in the output being displayed as 1 which is incorrect:
  • dtIsFormattedDate (‘02/29/08","DD/MM/YY’)
  • dtIsFormattedDate (‘29022008","YYYYMMDD’)
  • dtIsFormattedDate (‘29-02-2008","D-M-YY’)
  • dtIsFormattedDate (‘29/02/2008","M/D/YY’)
The output should ideally be 0. This issue basically occurs for invalid dates and formats.
37 In Excel Transform, in the Data Transfer tab of the Properties dialog, entering an invalid value for 'starting location' like A0, A-5 or A2147483648 displays COleDispatchException and not a comprehensible error message.
38 In Excel Transform, in the Data Transfer tab of the Properties dialog, entering an invalid value like 3A or 5B or any negative number for Maximum Number of Rows to Transfer, doesn't generate any error message instead the plan executes successfully. Basically, if the entered value is an alphanumeric value, beginning with a numeric value, the rest of the string data is stripped and the numeric value is used for processing. And if the alphanumeric value has a string at the beginning, it generates an error.
39 In Expression Calculator transform using the function dtDateFromString and creating expressions like the following results in these expression getting parsed properly and displaying incorrect dates rather than the default error date:
  • dtDateFromString ('12/31/2009' ,' DD/MM/YYYY')
  • dtDateFromString ('15/12/06','MM/DD/YY')
  • dtDateFromString ('12-22-06','DD-MM-YY')
  • dtDateFromString ('12-16-2008','DD-MM-YYYY')
  • dtDateFromString ('2-22-2008','D-M-YY')
  • dtDateFromString ('1312006','MMDDYYYY')
  • dtDateFromString ('13106','MMDDYY')
  • dtDateFromString ('11206','DDMMYY')
  • dtDateFromString ('11211969','DDMMYYYY')
  • dtDateFromString ('20001310','YYYYMMDD')
  • dtDateFromString ('202209','YYMMDD')
40 In Expression Calculator transform, using the dtDateFromPStr () function to create an expression like, dtDateFromPStr ("13122008", 1) results in the output to be displayed as 12/13/2008 0:00:00 AM instead of a default error date.
41 In Expression Calculator transform, using the Right () or Left () function to create expression like, Right ("Expression",-5) or, Left ("Expression",-5), results in the output length of the expression to be displayed as 19 9.
42 In Analysis transform, using the Column Organizer option by right-clicking the transform may not work.

The workaround here would be to switch between the various tabs or by opening the Presentation tab and then using Column Organizer.
43 In SQL Query transform, if a plan is executed when a Decimal or Double data type column having data outside the range of Integer is changed to Integer data type using SQL Editor, may either result in an incorrect error or may result in Internal Error: Access Violation.
44 Plan file name is not visible in plan strip if a single character for plan file name is provided. For example, on saving a plan file with the name "A"; "A" is not visible in plan strip. This occurs due to a Prof-UI limitation where tabs can't display names consisting of single character.
45 The bottom scroll bar disappears some times in Grid if we adjust columns or rows. This is because of an inherent limitation of the way in which Prof-UI implements tab windows.
46 The Grid intermittently goes out of the presentation area on the right side with no Horizontal or, Vertical Scroll bar to control it.
47 On Sybase Repository, while using SAINRP when a wrong database name is entered and Check Connectivity is clicked, then a message:
Successful Login is displayed.

However, subsequent repository operations cannot be performed.
48 Repository Upgrade (including BaseView Upgrade) for large repositories, takes significantly longer time as compared to the previous versions of Sagent.
49 After upgrade, Leaving Plans open while closing Design Studio may cause the same plans to behave erratically in the next session.
50 Inconsistent use of redo and undo with Group Summary may result in sporadic display issues.
51 In Key Lookup transform, the Pre-loaded partial cache option should not be used for large number of input records exceeding 100K due to the fact that for this caching mode, all the input records are held by DFS in memory till the end of execution of the Key Lookup step for comparison with each lookup subset. Memory utilization will go up with larger input records. This mode is only useful for scenarios where the number of look up records is much greater than the number of input records. The execution time is higher than that of Whole cache because of the number of iterations involved.
52 In Key Lookup transform, for Lookup conditions like <, >, and so on, the execution time is higher than in =. This is because multiple comparisons are made with the look up data, which could return multiple records. Also, a direct look up in cache is not possible for the caching modes for conditions other than ‘=’.
53 In Key Lookup transform, All matched rows execution option utilizes considerable memory. Because, in this case, all the matched records from look up table are joined with the input and the output records increase considerably with the volume of the input and look up table size. As a result, an out-of-memory state could possibly arise. This option should be used in case of Cache whole table and Pre-loaded partial cache with less number of records in both input and lookup tables.
54 In Key Lookup transform, the All matched rows execution option should specifically be avoided with Cache as found option, as it is a time-consuming activity; the memory consumption rises with the matched look up records fetched from lookup table; and the increasing number of input records to be processed as output are stored in the memory.
55 In Key Lookup transform, the result for returned lookup columns is different in the Cache Whole Table and Pre-loaded Partial Cache options. This is because of the different caching mechanisms involved.
56 In Key Lookup transform, the First matched row execution option returns the matched record, which is first retrieved from the cache and this may not be in the same order as it occurs in the lookup table.
57 While using the Open existing workbook option in the Excel transform, errors such as COleException with status code 0x80010105 and Access Violation are thrown. This occurs sporadically.
58 The OLEDB Source transform for Sybase OLEDB Provider generates the following error:
Provider 'Sybase OLEDB Provider' not found.
59 In a Flat File source, if the input file with date column is given and in the Processing tab, the date conversion dropdown format is selected as 19YYMMDD, this should give an error as the input date does not match the date type. Instead, it executes by rounding off all the years in the date to 2000. The above-mentioned scenario is specific to the input data. If the DateTime column is after an integer column, an error gets generated. But if the DateTime column is after string column, the changed behavior is observed.
60 In the Flat file source, if the input file is ANSI but if the character set in the Attributes tab is selected as OEM/EBCDIC, then on executing the plan, an Access Violation error is likely to occur.
61 Export or Import of repository with all the plans and security display the wrong creator. It has two work around solutions: 1. Give manually access to the imported plans to that particular user. OR 2. Import the plan after importing the security settings instead of doing it together.
62 In a plan having Analysis as sink, if the input is such that a column of type date with year as 1600 or less than 1600 is specified, the output generates a blank entry. But the date is displayed properly in the grid.
63 When the data type of input column used in Enter moving total field of Moving Total transform changed to string from integer, and then opening the Moving total transform dialog would display the following error: Incorrect parameter used. Clicking OK would show a slightly different dialog of Moving total.
64 Login fails using the Ask while running script option for Tombstone in SARPUTIL for DB2.
65 In XML Source transform, even if a different schema file is specified for an XML file, the plan gets updated but without any records in the output.
66 When the BaseViews or MetaViews are created with names as long as 255 characters, then renaming them truncates the name to 80 characters.
67 In Delimited Text File Source transform, when the Add button is used to add a new column in DTFSource and not initialize it; the column value will be displayed in the wrong place (the value of next column will be evaluated to the new column) and that of respective columns gets shifted to one place left depending upon the data type compatibility of the columns.
68 In SaConfig.exe, if a wrong name is provided for the Database Alias, then it throws an error with Save To File option. Saving it as a 'Text File' stores it without any extension. To open the file, it has to be converted manually to .txt type.
69 In Query Iterator transform on DB2, if the input file has an integer column having NULL values for some rows and Non-NULL values for some other rows, the following error is encountered:
“NULL” is not valid in the context where it is used "NULL" is not valid in the context where it is used.
70 With DB2 Batch Loader in a plan trying to insert data in a table having a hyphen (-) in its column name will result in an error message. The same behavior is observed with Microsoft Batch Loader transform in SQL repository.
71 In Sagent Admin utility, the server type is not validated hence registering a new server with a valid server credentials and invalid 'OS Type' will show the server registered without generating any error message. Now, clicking the Status tab will also show the current client session and corresponding user name.
72 In Sagent Admin utility, the Agent Port is not validated hence registering a new server with a valid server credentials and invalid 'Agent Port' having any arbitrary value doesn't give any error and the server gets registered successfully.
73 In the UI of Disk Sort Transform, the Max Blocks in Memory field when entered manually with keyboard gives correct results. But when the scroll button is used, it generates an error for values above 999.
74 In the DB2 Batch Loader Transform, in the Property dialog, when OK is clicked without selecting a BaseView, an error message is displayed. Clicking the OK button in the error message, however, closes the Property dialog.
75 In Sybase Batch Loader, if a negative batch size value is provided and the plan the executed then no error message is generated and it executes properly.
76 The Design Studio crashes while performing the following steps:
  1. Take two SQL Query transforms, Sorted Union and Grid. Execute the plan.
  2. Remove the two inputs and double-click on Sorted Union. The following error is displayed: An invalid input ID was used.
  3. Double-click on Sorted Union transform.
77 In Fixed Width File Sink transform, column name is truncated when the length of the column name is longer than the content of this column.
78 Sybase Batch Loader fails to load data into the database with high precision data Decimal data. Please follow the steps to replicate the issue:
  1. Create a string field str (say) with 38 size and having the data -.123456789012345678901234567890123456.
  2. The following expression is created in Expression Calculator by using: ToDecimal(PadRight ( str, "2",1 ) ,38,38 ) *-1.
  3. Sybase Batch Loader is used to load the data in a Sybase database table.
79 In Analytical Calculator transform, an expression False AND False and False ISNOT False does not return 1 all the time. Its repetitive execution may return even 0. To overcome the issue, please use either 0 or 1 instead of false and true.
80 Hyperbolic and Inverse functions cannot be given using the keypad in Analytical Calculator.
81 On clicking the Attributes box in Analytical Calculator, the tab which opens has a title "Column Attribes".
82 In Sarputil, performing Export / Import operation on Sybase repository, prints many empty lines in the output window of Sarputil.
83 In Add Column transform, if a new column of double data type is created with an invalid initial value such as 12..36, it doesn't throw an error during plan execution and displays incorrect value in the output.
84 A plan with two input sources (Time Generation transforms), a Comparison transform and two sinks (Grid transforms) executes properly. However, adding a Splitter and Grid transform to one of the Time Generation transforms leads to the following error: Step Comparison with unconnected output.
85 The error messages generated from the server side are displayed in English for Key Lookup transform and not in the corresponding localized language when the Data Flow Server and the client are installed in two different machines.
86 If a Sybase repository having plans having VBA components incorporated is upgraded from v6.5, it may give VBA related errors while plan execution. In such scenarios, first restart the Design Studio. If this does not work, then re-create the VBA component for the corresponding plan.
87 Plans containing both Command Line Sink and DB2 Batch Loader, generates the following error when a column with the Date data type is used in the data flow: Invalid internal date string processed. This issue doesn’t occur when these sinks are used independently or when a third sink is used in the plan.
88 On performing certain operations on SQL Query transform in the Oracle repository, the scale length of the column in database object explorer is shown as -2147483647. This is different from the length -127 shown in the Columns in Statement area. Also, the value gets truncated to the first 12 significant digits, which is reflected in the DB. The operations on SQL Query transform in the Oracle repository are:
  1. Create a table having a column with Float (38) data type in Oracle.
  2. Insert values with precision 38 into the column using Oracle Batch Loader.
  3. Insert values with precision 38 into the column using Oracle Batch Loader.
  4. Create a MetaView with that table and open the SQL Editor on the table.
89 Upgraded plans using Key Lookup transform are found to be running 10 percent slower than previous version.
90 In Analytical Calculator transform, expressions greater than 255 character length are not supported. If such expressions are used it leads to Internal Error: Access Violation. On subsequent execution, it is likely to cause a DFS crash.
91 All number data types (Double and Decimal) with high values of precision and scale values tend to lose the original value slightly during processing within Sagent. At times, the data is either rounded off, lost or altered. For example, a Double data type value such as 9999988888.77777 becomes 9999988888.77776910 during processing. When these altered values pass into subsequent downstream transforms for further processing, they return unexpected results. Basically, this behavior is designed as such. It is how the computer represents floating point in binary. CPU uses binary to represent floating point decimal number. So, precision loss is inevitable. As explained above, the issue is not language-specific. This has been confirmed by Microsoft.
92 In Columnar Report or Form Report transforms, displaying data of Double or Decimal data type with length greater than 15, results in incorrect output where zeroes get appended with the data.
93 In DB2, when TIME data type is used to create BaseView, executing a Plan with the BaseView displays invalid output values. For example, a Time data type value like, 10:10:59 AM, gets displayed as, 1/1/2001 10:10:59 AM, in the output. The reason is TIME data type in DB2 gets converted to duration in Sagent. During processing, it gets converted to DateTime data type. As TIME data type represents time value, it appends the default date value of 1/1/2001 to the output.
94 No strict validation exists in the BaseView Editor for manual changes that can be done by the user to a particular column of a table existing in BaseView Editor (validation such as scale should be less than precision). Hence, such changes reflect in the MetaView and the data flow as well.
95 The BaseView Editor encounters Access Violation error while creating a BaseView with a wrong database name but valid Sybase credentials. Sybase does not validate the database name while adding the tables. Yet generates an error while creating the BaseView.
96 A plan containing a lot of client sinks (around 15 to 20) result in flickering Design Studio.
97 Microsoft Batch Loader and Oracle Batch Loader share the same dialog. Thus, if there is a particular functionality for any of them, the same get reflected in the user interface. For example, "Truncate string to be loaded in Database" option is used in Oracle. But the same option is visible in Microsoft Batch Loader. However, it is operative for the intended transform and disabled in other transforms.
98 In Oracle, the username for Design Studio is case sensitive. It is not case sensitive in SQL Server.
99 In the case of Constant Values in subset, no validation for time is performed. Only the Date field has been validated. This is due to the constraint in Microsoft-provided COLEDateTime.
100 In the Constant Comparison option in Key Lookup transform, if the user enters a numeric value, which is the same as that of a column name, (say, the column name is ‘123’ and the constant is also 123), then the column name would take precedence over the constant value.
101 Saving plans inside the Plan bin may display two names of the same plan at a time. This is only a display issue and occurs because the Plan bin automatically does not get refreshed. This is the limitation in the design of the product and the workaround here would be to select an option from the dropdown such as, List all the plan that I can Access. This refreshes the Plan bin and, thus, a single instance of the plan will be displayed thereafter.
102 The sizes of the output columns in Grid sink do not get re-adjusted appropriately during the display. This is a due to a design issue wherein the refresh does not occur in the desired manner with the new UI implementation in V6.5. Click the columns of the Grid sink along with either clicking the sink tab or switch between the various tabs. This would re-adjust the grid display correctly.
103 In DB2 Batch Loader, if data of data type Unsigned Integer is used, then invalid data is loaded into the database. This is because the there is no data type such as, Unsigned Integer in DB2. Thus, it internally converts the data type into Integer. This conversion leads to invalid data getting loaded into the database.
104 More than one Component plans having the same name can be saved in the root folder.
105 In Key Lookup transform, if the subset is done on a numeric field then the user must be provided a numeric constant value. If the constant value provided is same as one of the column names in the lookup table, then the subsets will be done based on the column values instead of the constant value. For example, if the subset constant value '123' is given and a column named '123' is present in the lookup table, then the subsets will be generated based on the values of column '123' and not on '123' as a value.
106 Altibase is not supported with Sagent 64-bit Non-Unicode release.
107 For creating a repository on DB2 and Sybase ASE, page size must be set to 16 KB.
108 Clicking on links in the Content pane of the Design Studio and New Features online help returns a page not found error. Use the expanding/collapsing Navigation pane to view help topics. The Index and Search features work correctly and are not affected by this problem.
109 When wrong credentials, particularly wrong repository name is given when logging into Design Studio, using a Sybase repository, the following error is encountered:
Repository Connection Failure : This software is not compatible with the Repository - Current Repository version : 6.5 ; Required Repository version:6.5. This is due to the limitation of Sybase CT-LIB APIs.
110 In Key Lookup transform with the Whole or Preloaded Partial Caching option, the more the number of resource mappings, the more would be the chance of getting a composite key error. This is because of the fact that the distinct row selection is done based on the number of columns referenced in the lookup table. Hence, it could be possible that the user finds that the Cache as found option is not resulting in a composite key error unlike the other two caching options.
111 In Key Lookup transform, for Integer fields, Input or Lookup value should be less than INT_MAX.
112 When fetching data of Date data type from Sybase database, with incorrect date format (a value that cannot be interpreted by Sybase), results in incorrect date conversion error. At times ct_fetch () error message is also encountered. This is due to the limitation of the CT-LIB API's of Sybase.
113 In DB2 with Save To Table transform, if the table name is specified in single quotes such as 'db_table', the table gets created in the database in single quotes like, 'db_table’.
  • Take a backup of the table SARP_VFL_STEP_PROP on the DB2 Sagent repository.
  • Drop the table and recreate it with the same specifications as earlier, except for the column VAL_BLOB.
  • Increase the size of the column VAL_BLOB, which has a default size of 180000 bytes. Consult your Database Administrator [DBA] before resizing.
114 The result sets in output for Key Lookup transform vary for limiting precision data, when processed using the different caching options. This is an existing limitation because of differences in float data handled by Databases and MFC functions.
115 In SQL Query with Sybase database, the length of the columns with data types such as, Text and Binary are displayed as 2M. On clicking GetColumns in SQL Query Editor, the value changes to 32768.
116 If Data Flow Server and WebLink server are on different machines, and IT\SaConnectionMax (on the WebLink server) is greater than DC\MaxClients (on DFS machine), WebLink will set the internal value, it uses for IT\SaConnectionMax to be 5 less than DC\MaxClients. Set DC\MaxClients (on DFS machine) to 5 greater than IT\SaConnectionMax (on WebLink server) to allow for other clients such as SAAD. (SG16785)
117 In Analysis, if you rename Parts in a MetaView, the corresponding field names in Analysis do not reflect the changes. The SQL query is correct and the Plan works. If you want Analysis to have the changed names, delete the Analysis Transform and then add it back. (SG11057)
118 Joins in BaseViews: If you delete a join in the BaseView, Plans will return indeterminate amounts of data. Adding the join back does not fix the problem. The Plan needs to be forced to recompile by adding a Part to the SQL Query step and then delete it, which forces the code to recompile the Plan and regenerate the joins. (SG13434)
119 WebLink: Clicking the Back button after a prompt selection has been made, takes the user back to the previous Plan, not the prompt list. To get back to the prompt list, click Refresh. (SG13890)
120 Key Lookup Transform: A cached key lookup can differ from an un-cached key lookup. The reason is that during un-cached lookups the Key Lookup Transform relies upon the DBMS to perform the lookup of key values. The DBMS uses its own methods for doing data type conversions such as between a floating point number (double) and a NUMBER (4, 9) column. For cached operations, the transform requires an exact key match. This difference can, in some instances, lead to differences in finding lookup entries. (SG14110)
121 Use of Join Groups: Creating BaseViews with many tables that contain complex groups of tables with joins can degrade performance when trying to pull Parts from a MetaView into a SQL query. To significantly speed up performance, use join groups. This allows several joins to be contained in a group, which optimizes the query. (SG14202)
122 Field Definitions in Transforms: There are differences in the behavior of NULLS in field definitions for column names on Transforms in English and Japanese. There will be different behavior if you use NULL for column names. (SG14922)
123 WebLink Registry Setting: If you set SaConnectionMAX to -1, which is an illegal value, a Plan run in WebLink never completes. Use valid positive values for this setting. Repository Error: If you create a new Repository and then run Repository cleanup using sarpdel with the /snaptables option, an error is produced. Since this is a new Repository, there is no snap table information in a newly created Repository. This error has no effect. (SG14855)
124 BaseView Editor: When renaming tables in the properties part of the BaseView Editor, the changes are not picked up in some of the transforms (Query Iterator, SQL Command and MS Batch Loader) in an existing Plan. To ensure that the name change is picked up, change the first part of the name. For example, if you change "pubs" to "new_pubs" the change will be picked up. If you change it to "pubs1" the change will not be reflected in these transforms. (SG14877)
125 iWay: Intermittent Access violations on repeated updating after manipulating transforms after each run. No known workaround. (SG15286)
126 Using Comma in Expression Calculator when locale is German: All operations in Expression Calculator use the period as the decimal point. Operations on strings using the comma can be output as periods as the decimal point. It is best to use the Sagent Standard Format when doing all calculations in the Expression calculator. (SG16228)
127 Design Studio with Query Iterator Transform Stops Responding: When you rename a MetaView Part in the Query Iterator transform, Design Studio can stop responding. (SG16497)
128 Trusted security and WebLink: Using Trusted security logon, a Microsoft SQL Server feature) is not supported in WebLink. (SG16825)
129 When using the Drop or Create option for the Save To Table Transform, if the ODBC Data Source Configuration does not have the appropriate data source names, you encounter an error or the service does not run. Create ODBC data source names for each database you are using. (SG11258)
130 No columns are displayed after creating a BaseView against SQL Server 7 with an ODBC driver. Database name in the BaseView Editor should be the same as the database name that was selected during configuration of an ODBC Data Source name in ODBC Administrator. (SG11344)
131 When you install Sagent samples, some sample Plans come pre-installed with Design Studio and Information Studio. The sample Plans include Populate Fact Table, which can be accessed when you are logged in as jsmith. To update Populate Fact Table successfully, the following Plans need to be updated first:
  • Populate Account Dimension
  • Populate Card Product Dimension
  • Populate Day Dimension
  • Populate Household Dimension
  • Populate Status Dimension, and
  • Populate transaction type dimension
The sample Plans include New Populate Fact Table, which can be accessed when you are logged in as advuser. To update New Populate Fact Table successfully, the following Plans need to be updated first:
  • New Populate Account Dimension
  • New Populate Card Product Dimension
  • New Populate Day Dimension
  • New Populate Household Dimension
  • New Populate Status Dimension, and
  • New Populate transaction type dimension
132 In the StarView Wizard, when the user is prompted with Try to fill the new StarView? message, clicking the Yes button creates a StarView view and attempts to fill it. Whereas, clicking the No button creates an empty StarView. (SG10155)
133 If you use an Alias Dimension Table in StarView, the SQL statement in the Populate Plan function does not recognize the table name related to the Alias. To work around this problem, edit the SQL statement manually to account for the Alias. (SG11412)
134 The Sagent Samples install does not drop and create the sample data tables causing data to be duplicated in existing sample tables. The sample tables must be dropped manually before installing Sagent Samples. (SG12617)
135 If you create a drill-through link that includes the _self parameter in a Report and run the Plan in WebLink using Netscape 6.0 or greater, WebLink ignores the _self parameter and the result is displayed in a new window. (SG16027)
136 In Expression Calculator when the source database is Oracle, field names must be in uppercase in order for Expression Calculator to recognize the field names. (SG16255)
137 The Scheduler shows only Post-Meridian times when the Time Style of the Regional Settings is set to H:mm:ss or HH:mm:ss. To show Anti-Meridian times in the Scheduler, change the Time Style option to hh:mm:ss tt.
138 The XML Source Transform does not support the use of single-byte Katakana characters in XML source files because the XML Parser does not support single-byte Katakana.
139 Sometimes illegible characters or fonts display in the international English version on Asian Windows OS. (SG11453)
140 Using a backslash (\) as a Date format separator from the Control Panel displays unexpected output for dates in Plans. (SG12489)
141 In Chinese environment, the error of composite keys with respect to Key Lookup transform (i.e., “More than one row was returned from the lookup Composite key") is displayed in English when the Data Flow Server and the client are installed in two different machines.
142 In all the localized environments, when a plan say, 'pln1' execution is scheduled using the scheduler where, Save Plan as Snap is also used, then the snap is saved as an English name like, Snap of 'pln1' instead of getting saved in the corresponding localized language. This happens when the Data Flow Server and the client are installed in two different machines.
143 A plan with XML Source is created in the localized environment with wrong data and the 'Abort on Error' option selected, and a valid path as input in the validate frame of the Document Source tab. The 'Error converting XML value' error message is displayed in English and not in the corresponding localized language. This happens when the Data Flow Server and the client are installed in two different machines.
144 In all the localized environments, when a plan having Oracle SQL* Loader is used to load data into an existing populated table using the update method, the following error message is displayed in the English locale and not in the corresponding localized language:
Oracle SQL * Loader: Process exited before connect to pipe. Check log file for specific error.

This happens when the Data Flow Server and the client are installed in two different machines.
145 In the Korean environment, the semantics of copy-pasted expressions have a minor inconsistency with respect to the Korean operating system. For example, when an expression called "test" is copied and pasted twice, it is displayed as "Copy (2) of test" instead of "Copy of test (2)".
146 In the Korean environment, on exporting a report into the PDF format, occasionally results in garbage characters getting displayed in the generated PDF document.
147 In the Korean environment, an occasional error "Transform Specifications Invalid" is displayed, while running a Plan with Multi-Condition Filter or, Analytical Calculator.
148 In the Japanese environment, the Sagent version description string in the Multiple Design Studio utility occasionally shows a garbage value.
149 In the German locale, the DateTime format in the Log file is different in Oracle Sql*Loader and Oracle Batch Loader. In the Log file, the DateTime generated by Oracle Sql*Loader is displayed as "Mi Feb 25 ", but in the Oracle Batch Loader, it is displayed as "Wed Feb 25".
150 The dialog properties of the Log Viewer utility are not localized. Moreover, the Tip dialog which pops up when Log Viewer utility is used, is also not localized.
151 In the Chinese locale, the Query Iterator transform generates garbage characters when the Selected Part or Dataflow Field in query generation includes null values for the column.
152 Executing a plan with Microsoft 6.x Batch Loader, generates an error indicating that the transform is not supported. However, the error message is displayed in English and not in the corresponding localized language. This happens when the Data Flow Server and the client are installed on two different machines.
153 In transforms such as Delimited Text File Sink, Fixed Width File Sink and XML Sink and Oracle Batch Loader, while generating a new file with a non-existing folder, the following error message is displayed: Can't create or open file. However, the error message is shown in English and not in the corresponding localized language. This happens when the Data Flow Server and the client are installed on two different machines.
154 Sybase repository is not supported in Japanese and French locale.
155 If you developed custom Transforms using the Sagent Transform SDK and added new properties, the Transform and new properties must be updated. If you run an old Plan without updating them, the new properties are not assigned the correct default values. To update the Transform, open each Plan that uses the Transform and open the Transform dialog in the Data Flow. Then save the Plan in the Plan Bin. You can also edit the Transform code and recompile. When you add new properties to a custom Transform, be sure to change the following in the Transform code:
  • In the constructor, increment the version number of the Transform.
  • In GetPropertySheetValues, check if the Transform is the old version, then assign a default value for the new property.
156 Decimal truncation for Add Column may propagate to transforms using this feature.
157 The Oracle Batch Loader does not load data into a destination table with a public synonym. (SG12337)
158 If you have the Crystal Reports add-in product installed and used an Excel Transform in a Plan, the Excel Toolbar displays a button for Crystal Reports. This button is inoperable and is a function of how Microsoft displays Excel Add-ins. There is no interoperability between the Excel Transform and the Crystal Reports Transform.
159 If you build a StarView aggregate table with an average measure and use that StarView in Analysis, the query uses the base fact table instead of the aggregate table. (SG10058)
160 The double data type has a limit of 15 digits of accuracy. The Grid display formats decimal field types as decimals. Other sinks convert decimal field types to doubles in order to format them correctly. The least significant digits beyond the fifteenth digit will be inaccurate.