Multi-tier Product V3.2
Release Notes
Bugs Fixed
Postgres95 | Progress | Sybase | Unify 2000
General |
|
PTR:1000339 |
Logging to file doesn't work in NT Broker CVSID 42 |
| Systems | General Database, on Windows NT (Intel) 4.0 Platform, to General Client |
| Notes | Start the CVS00042 archive broker with the options: -dvL
<filename> The Broker creates the log file but does not write any Trace output to the File. Status: Fixed
|
PTR:1000378 |
Allow customers to do a silent installation of our clients software on Windows or NT |
| Systems | General Database, on General Platform, to Windows 95 Client |
| Notes | The new version of install shield has an option that
does a silent install & uses all defaults. Status: Fixed
|
PTR:1000381 |
SQLGetInfo(SQL_QUOTED_IDENTIFIER_CASE) returns an invalid value |
| Systems | General Database, on General Platform, to Windows 95 Client |
| Notes | This problem appears to be a general one across all
database as the same error was returned when tested against Oracle, OpenIngres &
Progress. Below is the output from an ODBCTest session against OpenIngres Successfully connected to DSN 'oig2'. SQLGetInfo: In: ConnectionHandle = 0x007F0BD8, InfoType = SQL_QUOTED_IDENTIFIER_CASE=93, InfoValuePtr = 0x004B2048, BufferLength = 300, StringLengthPtr = 0x004B2018, Information Value Type = SQL_C_SLONG=-16 Return: SQL_SUCCESS=0 Out: *InfoValuePtr = -892731389 TST0006: The value -892731389 was not a valid named constant for SQL_QUOTED_IDENTIFIER_CASE. *StringLengthPtr = 2 Status: Fixed
|
PTR:1000386 |
Add routine to handle LIKE escape sequence |
| Systems | General Database, on General Platform, to Windows 95 Client |
| Notes | When a select statement is parsed, the like escape
sequence is not currently handelled. Status: Fixed
|
PTR:1000403 |
{fn now( )} not supported on scrollable cursors |
| Systems | General Database, on General Platform, to Windows 95 Client |
| Notes | Scrollable cursor parser rejects "select {fn now()}
from emp" - It doesn't recognize {fn now()} clause. Status: Fixed
|
PTR:1000424 |
Open Agent API Completion |
| Systems | General Database, on General Platform, to General Client |
| Notes | The Open Agent API is a key element in our Agent
Development process as it process a better abstraction between our Agent and the Comms
Layer. Status: Complete
|
PTR:1000436 |
Build NT ODBC agent installer |
| Systems | General Database, on Windows NT (Intel) Platform, to General Client |
| Notes | This installer will effectively just install the Broker
and Service agent ie: ODBC, JDBC & Proxy agents to enable users to use desktop ODBC
Driver like Dbase, FoxPro etc to access these tools via our drivers. Status: Complete
|
PTR:1000441 |
Add oplshut -s functionality to the web configurator |
| Systems | General Database, on General Platform, to General Client |
| Notes | The functionality has been added to the web configurator
code and has been merged with New Web Configurator wizard code. The functionality of oplshut -s is already present in the Web Configurator. Need a script to expose it. Status: Fixed
|
PTR:1000446 |
Using JDBC agent to retrieve Null values from a Text Column results in the JDBC agent crashing in NT and Segmentation Violation on Unix |
| Systems | General Database, on General Platform, to Java Client |
| Notes | Bug fetching NULLs in the JDBC agent. Status: Fixed
|
PTR:1000476 |
WWW_SV fails to run on CVS 45 |
| Systems | General Database, on Windows NT (Intel) 4.0 Platform, to General Client |
| Notes | WWW_SV fails to run when there is a space in the
installed path. Status: Fixed
|
PTR:970389 |
Install.sh Problems |
| Systems | General Database, on General Platform, to General Client |
| Notes | Install.sh has a line of code that potentially breaks
installations. The script has now been extensively modified for better functionality. Status: Fixed |
TOPInformix |
|
PTR:1000380 |
Informix agent strips trailing spaces from CHAR columns when fetching |
| Systems | Informix Database, on General Platform, to Windows 95 Client |
| Notes | Our Informix agent wrongly strips off trailing spaces
when fetching from Informix CHAR columns. Status: Fixed
|
PTR:1000479 |
Informix agent instance only supports 1 DBMS session |
| Systems | Informix Database, on General Platform, to General Client |
| Notes | At present, each Informix agent instance can only
support one database connection. If a re-use rule is specified it must be 'ifsame
database, 'ifsame user'. (This rule was presumably enforced by PMN because ESQL/C
automatically includes a single, global sqlca.) Informix 7.2 supports 'SET CONNECTION ...' to make the current connection dormant, or a dormant connection current. So, it appears to have the facility to support more than one connection. This facility needs testing and if feasible, the Informix agent should be modified to support > 1 database session per instance. Status: Fixed
|
PTR:1000509 |
Different column names are returned to SQLTables if a parameter is supplied. |
| Systems | Informix 7 Database, on General Platform, to General Client |
| Notes | Different column names are returned if all parameters
are null, than when one parameter is specified (such as 'TABLE'). The same column names
should be returned in both instances. This behavioral difference is causing problems with
programs that use the stated catalog function. If you look at the names of the columns, they have changed from "table_qualifier", "table_owner", "table_name", "table_type", "remarks" when there is no parameter to "(constant)", "owner", "tabname", "tabtype", "(constant)" when the parameters are supplied. This confuses the development tool which is probably interrogating the resultset metatdata, or simply looking for the column in a row named "table_name". When one parameter is specified: SQLTables: In: StatementHandle = 0x00A31878, CatalogName = SQL_NULL_HANDLE, NameLength1 = 0, SchemaName = SQL_NULL_HANDLE, NameLength2 = 0, TableName = SQL_NULL_HANDLE, NameLength3 = 0, TableType = "TABLE", NameLength4 = 5 Return: SQL_SUCCESS=0 Get Data All: "(constant)", "owner", "tabname", "tabtype", "(constant)" <Null>, "informix", "Tt", "TABLE", "" <Null>, "informix", "account", "TABLE", "" ... When all parameters are null: Get Data All: "table_qualifier", "table_owner", "table_name", "table_type", "remarks" <Null>, "informix", "Tt", "TABLE", "" <Null>, "informix", "account", "TABLE", "" <Null>, "informix", "branch", "TABLE", "" <Null>, "informix", "call_type", "TABLE", "" … Status: Fixed
|
PTR:1000392 |
Adding to tables with datetime fields using the JDBC Scrollable Cursor demo |
| Systems | Informix Possibly all agent Databases, on DGUX (Intel) Possibly all OS Platforms, to Java JDK 1.1 Client |
| Notes | When you try to Add a row using the scrollable cursor
demo, the database complains about the 'ts' escape. The file (udbc.out) demonstrates it in
full, but the database message: '{ts '1996-02-12 00:0' shows the problem. See below for more: Replicated the behavior on Informix DG-UX Intel. The customer was using Ingres 6.4 on Solaris. SQLExtendedFetch hStmt=DBD0003 fFetchType=1 irow=1 pcrow=DFFFF004 rgfRowStatus=5B6A0 ConvertCHAR: retBufferLength(41) to SQL_C_CHAR ConvertCHAR: retBufferLength(21) to SQL_C_CHAR ConvertTIMESTAMP: precision,scale (20,0) to SQL_C_CHAR ConvertTIMESTAMP temBuf string = %04u-%02u-%02u %02u:%02u:%02u ConvertTIMESTAMP: precision,scale (20,0) to SQL_C_CHAR ConvertTIMESTAMP temBuf string = %04u-%02u-%02u %02u:%02u:%02u ConvertTIMESTAMP: precision,scale (20,0) to SQL_C_CHAR ConvertTIMESTAMP temBuf string = %04u-%02u-%02u %02u:%02u:%02u ConvertCHAR: retBufferLength(23) to SQL_C_CHAR ConvertCHAR: retBufferLength(2) to SQL_C_CHAR ConvertCHAR: retBufferLength(6) to SQL_C_CHAR ConvertCHAR: retBufferLength(41) to SQL_C_CHAR ConvertCHAR: retBufferLength(101) to SQL_C_CHAR SQLExtendedFetch: returning SQL_SUCCESS SQLSetPos hStmt=DBD0003 irow=1 fOption=4 fLock=0 SQLSetPos: returning SQL_ERROR SQLError: szErrorMsg=DFFFEB94 cbErrorMsgMax=256, pcbErrorMsg=0 szSqlState=DFFFEC94 pfNativeError=DFFFEF94 Returning [Ingres Server]Error in row SQLError: szErrorMsg=DFFFEB94 cbErrorMsgMax=256, pcbErrorMsg=0 szSqlState=DFFFEC94 pfNativeError=DFFFEF94 Returning [Ingres Server]E_US10D4 bad character found in date string beginning with '{ts '1996-02-12 00:0'. (-40206) This problem has been recreated against Ingres 6.4 on SCO 4 using the method described above with the JDBC ScrollDemo program by attempting to update or insert a row with a datetime field in it. Have also recreated this problem with MSSQLServer although it does not occur with Oracle. On further investigation it is apparent that inserts o datatypes are passed to the JDBC agent using the ODBC escape syntax for dates ie {ts <timestamp>} and is thus dependant on the Database agent being able to convert these to native Datbase format before being presented to the database. For paramertised queries only Oracle has support for converting from the escape syntax to native database syntax Status: Fixed |
TOPIngres |
|
PTR:1000514 |
VAX VMS Broker crashes when a single quote ( ' ) is placed at the end of the username |
| Systems | Ingres Database, on VAX VMS 5.5-2 Platform, to General Client |
| Notes | Status: Fixed
|
PTR:1000510 |
oplrqb.exe leaves one handle unrelinquished per agent in NT |
| Systems | Ingres 2.0 Database, on Windows NT (Intel) NT 4 Service Pack 3 Platform, to General Client |
| Notes | With ReUse=never, connect to a request broker on NT,
while monitoring the number of handles open in the task monitor. For 10 connections & disconnections from udbctest, the number of handles used by oplrqb.exe increases by 10, i.e. the handles are not being closed. The loop used is: zsh, oplfbsd 3:51PM examples > repeat 10 ./udbctest <<EOF dsn=ing7 EOF zsh, oplfbsd 3:56PM examples > This is independent of ReUse (Never or 'upto 2'). Also, it is not related to the 2 minute TIME_WAIT socket problem - we waited until all the sockets had died on the client and server, and the handles are still in use. There are also leaks in the NT system files. Status: Fixed
|
PTR:1000519 |
SQLTables() against Ingres gives blank list of tables in MS Query |
| Systems | Ingres 6.4 Database, on VAX VMS Platform, to Windows NT (Intel) NT4 SP3 Client |
| Notes | Using MS Query, under Data / Get external Data, select
'create new query'. Create a new File DSN using the dialog Query presents. Fill in points
1, 2 and 3 (selecting a driver for the connection and attempting to connect). Once the
connection is established, Query calls SQLTables() with a % in the owner field to make a
list of tables in the datasource. This list comes over as blank. On Vax, there is also a 'syntax error or access' at this point. Client-side debug trace follows: SQLTables hStmt=DBD0003 szTableQualifier=823060 cbTableQualifier=0 szTableOwner=823070 cbTableOwner=-3 szTableName=823080 cbTableName=0 szTableType=823090 cbTableType=0 Qualifier='' Owner='%' Name='' Type='' SQLTables: returning SQL_SUCCESS SQLBindCol hStmt=DBD0003 icol=2 fCType=1 rgbValue=3D894 cbValueMax=65 pcbValue=3DE08 SQLBindCol: returning SQL_SUCCESS SQLFetch hStmt=DBD0003 SQLFetch: returning SQL_NO_DATA_FOUND This is reported on Vax, confirmed on HP9 and Sequent. The problem lies in the SQLTables() call where instead of using NULL pointers to strings, it uses NULL strings. (This is reproduced in ODBCTest / Gator by specifying empty string instead of null string in a call to SQLTables().) Status: Fixed
|
PTR:970225 |
Unable to connect as many users when VMS Broker is running in detached mode as opposed to non-detached mode |
| Systems | Ingres Database, on General VAX VMS Platform, to Windows NT (Intel) Client |
| Notes | The Broker running in detached mode does not appear to
be inheriting the process Quotas it inherits when running in non-detached mode. The errors
typically received when the Broker fails to start an agent session are: oplrqb: cannot
create internal connection: RPC: Remote system error - Error 65535 (3506252) oplrqb:
cannot create internal connection: RPC: Remote system error - Error 65535 (28) oplrqb:
File "OPENLINK_ROOT:[BIN]ing6_sv.exe" not found (status = 114730) Status: Fixed |
TOPMS SQL Server |
|
PTR:1000358 |
DB-Lib Agents - Share DBPROCESS between sibling HSTMTs |
| Systems | MS SQL Server Database, on General Platform, to General Client |
| Notes | Re-architecting of DB-Library agents was required to
avoid potential deadlock when performing batch updates across several hstmt's with
autocommit off. Status: Fixed
|
PTR:1000431 |
JUDBC agent dies retrieving a null text field |
| Systems | MS SQL Server 6.5 Database, on Windows NT (Intel) 4.0 Platform, to Java 1.1 Client |
| Notes | There was a bug in transferring NULLs in the JDBC agent.
With a type-3 judbc connection to MS SQLServer 6.5 the judbc agent dies retrieving a null text field. There is no problem retrieving a null varchar, nor a text field if it contains data. Status: Fixed
|
PTR:1000371 |
MS SQL Server Stored Procedure Support |
| Systems | MS SQL Server All Database, on Windows NT (Intel) Platform, to Windows NT (Intel) Client |
| Notes | DBLIB Agent does not handle OUTPUT or MIXED Parameters
Correctly Status: Fixed |
TOPOpenIngres |
|
PTR:1000393 |
DG/UX (Intel) release 1.5.5 OpenIngres agent archive is corrupt on the WEB |
| Systems | OpenIngres Database, on DGUX (Intel) Platform, to Windows 95 Client |
| Notes | Status: Fixed |
TOPOracle |
|
PTR:970220 |
Timestamp Type Handling Problems (INSERTS) & Parameter Binding |
| Systems | Oracle Database, on General Platform, to Windows 95 Client |
| Notes | If the insert statement has an ODBC date-time escape
sequence ({ts ...}) it works fine, or if it is coded a "to_date(...)" the insert
statement works. When a parameter is used instead of a hard coded date then it doesn't
work. Support for ODBC escape syntax handling for parameters has been added. Status: Fixed
|
PTR:1000433 |
OPTIONS field in our OpenLink DSN Config Utility should hold the SQL*NetAlias name for Oracle sessions |
| Systems | Oracle Database, on General Platform, to General Client |
| Notes | A sqlnet alias can now be specified in the multitier
options dialog. However, there is still a problem with making two connections to different
aliases from a single application(ptr1000480). The OPTIONS field in our OpenLink DSN Config Utility should hold the SQL*Net Alias name for Oracle sessions. Status: Fixed
|
PTR:1000471 |
Oracle Lite DLL crashed when runing against a Multithreaded application |
| Systems | Oracle Database, on General Platform, to Windows NT (Intel) Client |
| Notes | Our Oracle Lite and MT Generic client crash when running
against an application running multiple threads continuosly in a loop. Status: Fixed
|
PTR:1000473 |
Oracle Lite crashes after 16 connections on the same handle |
| Systems | Oracle Database, on General Platform, to General Client |
| Notes | Modified source so the lite drivers could be built
without the MULTIPLEX LDA feature. The Oracle Lite driver was being built with the define MULTIPLEXLDA which is a feature not supported with the lite driver. As a consequence it was crashing after 16 connections on the same connection handle. Status: Fixed
|
PTR:1000448 |
Blob failure in Oracle using ASP |
| Systems | Oracle 7.2 Database, on Windows NT (Intel) 4.0 Platform, to Windows NT (Intel) 4.0 Client |
| Notes | using ADO in Active server page in IIS 4.0 when trying
to connect to Oracle database using cursor, if the table contains BLOB fields an error is
returned. Status: Fixed |
TOPPostgres95 |
|
PTR:1000466 |
SQLDescribeCol returns SQL_CHAR instead of SQL_DATE or SQL_TYPE_DATE for date columns |
| Systems | Postgres95 6.3.2 Database, on Linux/Elf Platform, to Linux/Elf Client |
| Notes | Returns SQL_CHAR for postgres 'date' table columns. SQLDescribeCol() should return SQL_DATE or SQL_TYPE_DATE. The postgres agent fetches all data as character data and currently relies on the client to do all conversions. The time and data datatypes are not converted. The data set containing the character representation of the data will be re-written on the server before being sent to the client. This work is required for the cursor library . Status: Fixed |
TOPProgress |
|
PTR:1000477 |
3 Issues with Progress Lite data source setup box |
| Systems | Progress Database, on General Platform, to Windows NT (Intel) Client |
| Notes | Issue 1. password text box in DSN setup: In addition to the User ID text box, can we add a Password text field as well. Issue 2 In ODBC Admin when configuring a DSN, the box where you enter the TABLEVIEW parameter is restricted to 35 characters, where as the other two are restricted to 255. Can the size of this also be increased to 255? Issue 3 The tab Order at present is incorrectly set. It currently moves from Session options to Tableview and then to Database options Status: Fixed
|
PTR:1000502 |
Registering Progress Lite Large with a Large key still shows 'Software has expired' |
| Systems | Progress Database, on General Platform, to Windows NT (Intel) Client |
| Notes | In the past, when trying to register progress large with
a large key, it showed a successful registration but when a connection was attempted, a
dialog box appeared showing that the software had expired. Status: Fixed
|
PTR:1000545 |
Progress 8.2c Lite Driver does not return high-byte characters (², ³, etc.). |
| Systems | Progress Database, on General Platform, to Windows NT (Intel) 4 Client |
| Notes | Unable to replicate this problem using a cvs48 lite
driver connecting to Progress on NT and on oplusdgint. In both cases the high byte
characters were returned correctly. When using the 3.2 (csv48) drivers, the Progress 8.2c Lite Driver does not return high-byte characters (², ³, etc.). The Multi-Tier driver returns these characters properly. Status: Fixed
|
PTR:1000511 |
Cannot drop table using Progress 7 agent |
| Systems | Progress 7 Database, on General Platform, to General Client |
| Notes | Removed the -NL connection parameter and reverted to
appending "FOR READ ONLY" to select statements so drop statements now work.
Errors when selecting "FOR READ ONLY" from views are trapped and "FOR READ
ONLY" is removed. When parsing sql in the Progress agent we append "FOR READ ONLY" to select statements. However, in some versions of Progress 7 we cannot use "FOR READ ONLY" with views so we use the -NL connection parameter as a workaround in all Progress 7 agents. Connecting with the -NL parameter means that when Progress translates the DROP TABLE code into 4GL, it leaves the lock requested as No-Lock and the statement fails. Status: Fixed
|
PTR:970385 |
Agent dies after any simple select statement is issued. |
| Systems | Progress 8.2 Database, on Dec Unix OSF/1 OSF1 V4.0 564 alpha Platform, to Windows 95 Client |
| Notes | Status: Fixed
|
PTR:1000414 |
Installation and Portation of Progress 8.2C on NT Alpha |
| Systems | Progress 8.2C Database, on Windows NT (Alpha) 4.0 Platform, to General Client |
| Notes | Status: Complete
|
PTR:1000382 |
Character Space Padding Problems |
| Systems | Progress All Database, on General Platform, to Windows 95 Client |
| Notes | This was the old problem about the length returned for
an expression. The customer wanted the first 3 characters but the applications was sizing the columns to 2k. The environment variable created for ptr981080 can be used to reduce this size from 2k. SQL column display size from Openlink is a lot wider (containing blanks?) than Progress'. This is giving some ODBC & JDBC Applications Dynamic Sizing problems. Note: similar to PTR100380 Status: Fixed |
TOPSybase |
|
PTR:1000494 |
Problems with Sybase/SQLServer stored procedure support |
| Systems | Sybase Database, on General Platform, to General Client |
| Notes | Sybase dblib, ctlib and SQLServer drivers crash when
fetching row results from a stored procedure containing timestamp data (only when
parameter markers are used) Stored procedures containg the Transact SQL print command generate an error that stops any more results being fetched.(dblib only) Status: Fixed
|
PTR:1000559 |
Sybase /SQLServer do not allow duplicate fields in an orderby clause |
| Systems | Sybase Database, on General Platform, to General Client |
| Notes | This has been seen working with Sybase and is a bug in
the cursor library as the cursor library appends an order by clause to the query
internally which results in the query sent to Sybase being of the form: 'SELECT id,datecreated,... FROM info ORDER by id, id assuming a key field named 'id'. Problem is that Sybase / SQLServer do not allow duplicate fields in an order by clause whereas every other database tested against does not complain. The fix required is thus to scan the query to check whether key columns are already present in the original order by, and if so don't attempt to add them to the end of the ordering list. Status: Fixed |
TOPUnify 2000 |
|
PTR:1000383 |
Portation of Unify DataServer 6 on Sequent at customer Site |
| Systems | Unify 2000 Database, on Dynix/Ptx Platform, to Windows 95 Client |
| Notes | Status: Complete
|
PTR:970259 |
Unify ORDER BY clauses from Access |
| Systems | Unify 2000 Database, on General Platform, to Windows 95 Client |
| Notes | Fails with a syntax error (-2131) or a "Invalid
ORDER BY specification (-2042) based on the mode and query that is run. Status: Fixed |
| |