Progress
Version 9
Product Update Bulletin


Progress Version 9.1D DataServer For ORACLE

The Progress Version 9.1D DataServer for ORACLE contains the following enhancements over previous versions:

Collation Table Support For ORACLE

Version 9.1D of the Progress DataServer for Oracle now supports the user specifying the collation table that should be used through the Create/Modify Database Record for DataServer Schema. You can access the Collation option through the Data Administration tool, and select DataServer Oracle Utilities Create DataServer Schema. The dialog box shown in Figure A–1 opens.

Figure A–1: Create/Modify Database Record For DataServer Schema Dialog Box

The collation table that the user specifies must be defined in the convmap.dat file or the user will receive an error message stating that the combination between the code page and the table does not exist.

The user can also specify the Collation table when performing the PROGRESS DB to Oracle Conversion. To access this utility, choose DataServer ORACLE Utilities Schema Migration Tools Progress DB to ORACLE. The dialog box shown in Figure A–2 opens.

Figure A–2: PROGRESS DB To Oracle Conversion Dialog Box

For more information on collation tables, see the Progress Internationalization Guide .

Include Default Option For ORACLE

In Progress Version 9.1D, there is also an additional option in the ProtoOra Utility called the Include Default option. Selecting the Include Default option causes the conversion to include the default values for fields in the Oracle schema. The code uses the Progress initial value for varchar and numbers. Additionally, if the Progress date field has TODAY as the initial value, the default value in Oracle will be SYSDATE. The LOGICAL data type has either 1 or 0 depending on whether the initial value is set to TRUE or FALSE. The utility only supports True/False or Yes/No for LOGICAL initial values.

The new Include Default option is also available in the Delta df to Oracle Conversion utility. To access this utility, choose DataServer Oracle Utilities Schema Migration Tools Generate Delta.slq Progress to Oracle. The dialog box shown in Figure A–3 opens.

Figure A–3: Delta df To Oracle Conversion Dialog Box

Alternative No NameServer Support For ORACLE

In prior versions of the DataServer for Oracle, you can connect through the Progress Explorer without using the NameServer by providing a special value of “none” to the -DataService connection parameter. Now, in Progress Version 9.1D, to indicate that the NameServer should not be used, the DataServer for Oracle can use the -DirectConnect connection parameter. If the -DirectConnect connection parameter is specified, then the -H and -S parameters are interpreted as the host and port of the broker. However, unlike connecting directly to the broker with the -DataService connection parameter, using the -DirectConnect parameter makes the -H and -S parameters optional. If -H is not provided, it defaults to “localhost”. If -S is not specified, it defaults to 4445. If -DirectConnect is specified, the -DataService is ignored.

Dynamic Find Feature For ORACLE

The Progress DataServer for Oracle in Version 9.1D will execute Dynamic Find statements like a FOR FIRST or FOR LAST statement. This should give much better performance than a typical FIND FIRST or FIND LAST statement. In particular, the NO-LOCK and SHARE-LOCK Dynamic Find statements will be executed using a single sql SELECT statement, instead of the two sql SELECT statements used for a typical FIND statement.

QUOTER 4GL Function For ORACLE

The QUOTER 4GL function can be useful for quoting values or handling embedded quotes when building SQL statements that will be passed into the send-sql-statement stored procedure. For more information on the QUOTER function, see "Progress 4GL Language Reference" in this bulletin and the Progress Programming Handbook .


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095