Managing Oracle Metadata

In this section:

When the server accesses a data source, it needs to know how to interpret the data stored there. For each data source the server will access, you create a synonym that describes the structure of the data source and the server mapping of the Oracle data types.


Top of page

x
Creating Synonyms

How to:

Reference:

x

Synonyms define unique names (or aliases) for each Oracle table or view that is accessible from the server. Synonyms are useful because they hide the underlying data source location and identity from client applications. They also provide support for extended metadata features of the server, such as virtual fields and additional security mechanisms.

Using synonyms allows an object to be moved or renamed while allowing client applications to continue functioning without modification. The only modification required is a redefinition of the synonym on the server. The result of creating a synonym is a Master File and an Access File, which represent the server metadata.

Note that creating a synonym for a stored procedure is described with reporting against a stored procedure, in Generating a Synonym for a Stored Procedure.



x
Procedure: How to Create a Synonym

To create a synonym, you must have previously configured the adapter. You can create a synonym from the Applications or Adapters pages of the Web Console.

  1. From the Web Console menu bar, click Applications.

    The Applications page opens.

  2. Click the New button and select Synonym from the drop-down menu.

    The Select adapter to configure or Select connection to create synonym pane opens.

  3. Click a connection for the configured adapter.

    The first of a series of synonym creation panes opens.

  4. Enter values for the parameters required by the adapter as described in the synonym creation parameters reference.
  5. After entering the parameter values, click Create Synonym.

    The Status pane indicates that the synonym was created successfully.

The synonym is created and added under the specified application directory.

Note:



x
Reference: Synonym Creation Parameters for Oracle

The following list describes the synonym creation parameters for which you can supply values.

Restrict Object Type to

Restrict candidates for synonym creation based on the selected object type(s): Tables, Views, External SQL Scripts, and any other supported objects.

Choosing External SQL Scripts from the drop-down list enables you to represent an SQL Query as a synonym for read-only reporting. A Synonym candidate can be any file that contains one (and only one) valid SQL Query and does not contain end-of-statement delimiters (";" or "/") and comments.

Depending on the adapter, you can further restrict your search by choosing check boxes for listed objects.

Filter by Owner/Schema and Object name

Selecting this option adds the Owner/Schema and Object Name parameters to the screen.

  • Owner/Schema. Type a string for filtering the selection, inserting the wildcard character (%) as needed at the beginning and/or end of the string. For example, enter: ABC% to select tables or views whose owner/schema begin with the letters ABC; %ABC to select tables or views whose owner/schema end with the letters ABC; %ABC% to select tables or views whose owner/schema contain the letters ABC at the beginning, middle, or end.
  • Object name. Type a string for filtering the object names, inserting the wildcard character (%) as needed at the beginning and/or end of the string. For example, enter: ABC% to select all objects whose names begin with the letters ABC; %ABC to select all whose names end with the letters ABC; %ABC% to select all whose names contain the letters ABC at the beginning, middle, or end.
Location of External SQL Scripts

xIf you specify External SQL Scripts in the Restrict Object type to field, these additional fields are displayed.

The following standard naming conventions apply for UNIX, IBM i IFS, and z/OS HFS:

  • In the Base Location field, specify the physical directory location of the file that contains the SQL Query. You can type a directory name or click on the ellipsis. This opens the Select Base Location dialogue.
  • In the Document Name field, enter the file name with or without wild card characters.
  • In the Document Extension field, enter the extension of the script files to filter the list of candidates.

On IBM i, you can use alternative IFS naming conventions to access library members. The following entry illustrates this method:

  • In the Base Location field, enter:
    /QSYS.LIB/MYLIBRARY.LIB/MYSRC.FILE
  • The Document Extension is understood to be MBR. You can enter this value explicitly or leave the input box blank.

During synonym generation, the adapter issues native API calls to obtain a list of elements in the select list and builds the Master File with a field for each element. The generated Access File references the location of the SQL script in the DATASET attribute, which contains the full path, including the name and extension of the file containing the SQL Query. For example,

DATASET=/ul/home2/apps/report3.sql

When a WebFOCUS report is created, the SQL Query is used to access data.

Cardinality

Select the Cardinality check box to reflect the current cardinality (number of rows or tuples) in the table during metadata creation. Cardinality is used for equi-joins. The order of retrieval is based on the size (cardinality) of the table. Smaller tables are read first.

If the cardinality of the tables to be used in the application are dynamic, it may not be beneficial to choose this setting.

With foreign key

Select the With foreign key check box to include within this synonym every table related to the current table by a foreign key. The resulting multi-table synonym describes all of the foreign key relationships of this table.

Dynamic columns

To specify that the Master File created for the synonym should not contain column information, select the Dynamic columns check box.

If this option is selected, column data is retrieved dynamically from the data source at the time of the request.

Select Application

Select an application directory. The default value is baseapp.

Prefix/Suffix

If you have tables with identical table names, assign a prefix or a suffix to distinguish them. For example, if you have identically named human resources and payroll tables, assign the prefix HR to distinguish the synonyms for the human resources tables. Note that the resulting synonym name cannot exceed 64 characters.

If all tables and views have unique names, leave the prefix and suffix fields blank.

Customize data type mappings

To change the data type mappings from their default settings, select this check box. The customizable mappings are displayed.

For information about customizable mappings, see Oracle Data Type Support.

Overwrite Existing Synonyms

To specify that this synonym should overwrite any earlier synonym with the same fully qualified name, select the Overwrite existing synonyms check box.

Note: The connected user must have operating system write privileges in order to recreate a synonym.

Default Synonym Name

This column displays the name that will be assigned to each synonym. To assign a different name, replace the displayed value.

Owner/Schema

The user account that created the object or a collection of objects owned by a user.

Type

The object type (Table, View, and so on).

Select tables

Select tables for which you wish to create synonyms:

  • To select all tables in the list, click the Select All button.
  • To select specific tables, select the corresponding check boxes.


Example: Sample Generated Synonym

An Adapter for Oracle synonym comprises a Master File and an Access File. This is a synonym for the table nf29004.

Generated Master File nf29004.mas

FILE=DIVISION, SUFFIX=SQLORA ,$
SEGNAME=SEG1_4, SEGTYPE=S0 ,$
FIELD=DIVISION4,    DIVISION4,    I9,  I4,  MISSING=OFF ,$
FIELD=DIVISION_NA4, DIVISION_NA4, A25, A25, MISSING=ON  ,$
FIELD=DIVISION_HE4, DIVISION_HE4, I9,  I4,  MISSING=ON  ,$

Generated Access File nf29004.acx

SEGNAME=SEG1_4,TABLENAME=EDAQA.NF29004,
CONNECTION=ORA901,KEYS=1, WRITE=YES,$


x
Reference: Mapping Oracle Comments into a Synonym

When you generate a synonym for an Oracle table, the adapter maps each:



x
Reference: Access File Keywords

This chart describes the keywords in the Access File.

Keyword

Description

SEGNAME

Value must be identical to the SEGNAME value in the Master File.

TABLENAME

Identifies the Oracle table. The value assigned to this attribute can include the name of the owner (also known as schema) and the database link name as follows:

TABLENAME=[owner.]table[@databaselink]
CONNECTION

Indicates a previously declared connection. The syntax is:

CONNECTION=connection

CONNECTION=' ' indicates access to the local Oracle database server.

Absence of the CONNECTION attribute indicates access to the default database server.

KEYS

Indicates how many columns constitute the primary key for the table. Range is 0 to 64. Corresponds to the first n fields in the Master File segment.

Note: If the table does not have the primary key, then the first unique index may be taken instead.

WRITE

Specifies whether write operations are allowed against the table.

KEYFLD
IXFLD

Supply the names of the primary key and foreign key fields that implement the relationships established by the multi-table Master File. Together, KEYFLD and IXFLD identify the field shared by a related table pair.

  • KEYFLD is the FIELDNAME of the common column from the parent table.
  • IXFLD is the FIELDNAME of the common column from the related table.

KEYFLD and IXFLD must have the same data type. It is recommended, but not required, that their lengths also be the same.

Note: An RDBMS index on both the KEYFLD and IXFLD columns provides the RDBMS with a greater opportunity to produce efficient joins. The columns must have the same data type. If their length is the same, the RDBMS handles the join more efficiently.



x
Reference: Managing Synonyms

Once you have created a synonym, you can right-click the synonym name in the Adapter navigation pane of either the Web Console or the Data Management Console to access the following options.

Option

Description

Edit

Opens the Master File for viewing and editing using a graphical interface. If an Access file is used it will be also available.

Edit as Text

Enables you to view and manually edit the Master File synonym.

Note: To update the synonym, it is strongly recommended that you use the graphical interface provided by the Edit option, rather than manually editing the Master File.

Edit Access File as Text

Enables you to view and manually edit the Access File synonym.

Note: This option is available only when an Access File is created as part of the synonym.

Sample Data

Retrieves up to 20 rows from the associated data source.

Data Profiling

Data Profiling provides the data characteristics for synonym columns.

Alphanumeric columns provide the count of distinct values, total count, maximum, minimum, average length, and number of nulls.

Numeric columns provide the count of distinct values, total count, maximum, minimum, average value, and number of nulls.

Refresh Synonym (if applicable)

Regenerates the synonym. Use this option if the underlying object has been altered.

Data Management

Followed by these options, if applicable:

Recreate DBMS Table. Recreates the data source table. You are asked to confirm this selection before the table is regenerated. (Note that the table will be dropped and recreated. During the process, data may be lost.)

Delete All Data. Deletes all existing data. You are asked to confirm this selection before the data is deleted.

Insert Sample Data. Inserts specified number of sample records, populating all fields with counter values.

Impact Analysis

Generates reports on procedures, synonyms, and columns that provide information on the flows/stored procedures available on a particular server, and the synonyms and columns they use. These reports enable you to evaluate changes before they are made by showing which components will be affected. See the Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual for details about Impact Analysis Reports.

Copy

Copies the synonym to clipboard.

Delete

Deletes the synonym. You are asked to confirm this selection before the synonym is deleted.

Cut

Deletes the synonym and places it in clipboard.

Properties

Displays the properties of the synonym, including physical location, last modified date, and description.



x
Accessing Multiple Database Servers in One SQL Request

To access a remote Oracle table using DATABASE LINKs, the following conditions must exist:

Once you have met the above conditions, all requests for the table will be processed on the remote Oracle database server specified using the DATABASE LINK name. Using this method is another way to access multiple remote servers in one SQL request.


Top of page

x
Oracle Data Type Support

Reference:

x

The following tables describe how the server maps Oracle data types.

 

Oracle Data Type

Server Data Type

 

Remarks

USAGE

ACTUAL

Date-Time Data Types

DATE

HYYMDS

HYYMDS

Stores point-in-time values (dates and times) ranging from January 1, 4712 BCE through December 31, 9999 CE.

TIMESTAMP (fractional_seconds_precision) WITH LOCAL TIME ZONE

HYYMDS

HYYMDs

HYYMDm

HYYMDS

HYYMDs

HYYMDm

fractional_seconds_precision in (0,1,2).

fractional_seconds_precision in (3,4,5).

fractional_seconds_precision in (6,7,8,9).

The Server supports TIMESTAMP without the TIME ZONE portion.

INTERVAL YEAR (year_precision) TO MONTH

Not supported

Not supported

Stores a period of time in years and months, where year_precision is the number of digits in the YEAR datetime field. Accepted values are 0 to 9. The default is 2.

INTERVAL DAY (day_precision) TO SECOND (fractional_seconds_precision)

Not supported

Not supported

Stores a period of time in days, hours, minutes, and seconds.

Numeric Data Types

NUMBER (p, s)

Pp,s

P1,...,8

p is an integer between 1 and 31.

s is an integer between 0 and p.

Note: If the MISSING=ON attribute is present in the Master File, the ACTUAL attribute must be P8 or longer. If MISSING=OFF, the ACTUAL attribute will be generated with the length equal to the precision of a NUMERIC field in an Oracle table.

Pp,s

P9,...,16

p is an integer between 16 and 31.

s is an integer between 0 and p.

D20.2

D8

p is an integer between 32 and 37.

s is an integer between 0 and p.

I11

I4

p is 38. This value is the Oracle default.

s is an integer between 0 and p.

INTEGER

See Number

See Number

Oracle converts and stores this type as NUMBER.

DECIMAL

See Number

See Number

Oracle converts and stores this type as NUMBER.

FLOAT

D20.2

D8

An approximate numeric type.

BINARY_DOUBLE

D20.2

D8

A 32-bit, single-precision floating-point approximate numeric type.

BINARY_FLOAT

D20.2

D8

A 64-bit, double-precision floating-point approximate numeric type.

LOB Data Types

BLOB

BLOB

BLOB

Server supports BLOB through the OCI interface, with ora_oci=y set in edaserve.cfg.

CLOB

TX50

TX

Server supports CLOB through the OCI interface, with ora_oci=y set in edaserve.cfg.

NCLOB

TX50

TX

Server supports NCLOB through the OCI interface, with ora_oci=y set in edaserve.cfg.

LONG

TX50

TX

Character data of variable length up to 2 gigabytes, or 231 – 1 bytes. Provided for backward compatibility.

The LONG field must be the last position in the report. This field is the subject of all limitations as documented by Oracle.

As of Oracle 8i, this data type is deprecated. You can migrate to CLOB whenever possible.

LONG RAW

BLOB

BLOB

As of Oracle 8i, this data type is deprecated. You can migrate to BLOB whenever possible.

BFILE

Not supported

Not supported

Stores unstructured binary data in operating system files outside the database.

Other Data Types

ROWID

A18

A18

The pseudo-column data types that store the physical address of a row.

UROWID

Not supported

Not supported

The pseudo-column data types that store both the physical and logical address of a row.

MLSLABEL

Not supported

Not supported

Stores variable-length, binary operating system labels.

The following table lists how the non-Unicode server maps Character data types. This mapping can be changed based on the value of LONGCHAR. The default value is ALPHA.

Oracle Data Type

 

Remarks

LONGCHAR ALPHA

LONGCHAR TEXT

USAGE

ACTUAL

USAGE

ACTUAL

CHAR (n)

n is an integer between 1 and 256.

An

An

An

An

n is an integer between 257 and 2000.

An

An

TX50

TX

NCHAR (n)

n is an integer between 1 and 256.

An

An

An

An

n is an integer between 257 and 2000.

An

An

TX50

TX

VARCHAR2 (n)

or

VARCHAR (n)

n is an integer between 1 and 256.

AnV

AnV

AnV

AnV

n is an integer between 257 and 4000.

AnV

AnV

TX50

TX

NVARCHAR2 (n)

n is an integer between 1 and 256.

An

An

An

An

n is an integer between 257 and 4000.

An

An

TX50

TX

RAW (n)

n is an integer between 1 and 128, m = 2 * n

Am

Am

Am

Am

 

n is an integer between 129 and 2000, m = 2 * n

Am

Am

TX50

TX

Note: The main purpose of the LONGCHAR setting is to provide compatibility with previous releases of the server. This SET parameter was designed to control processing of DBMS Character data types and was never intended for DBMS LOB.



x
Reference: Data Type Support for Unicode

The following table describes how the Unicode server maps Character data types. The server operates in character semantic when configured for Unicode. The LONGCHAR does not affect mapping in this case.

 

Oracle Data Type

Server Data Type

 

Remarks

USAGE

ACTUAL

CHAR (n)

AnV

AnB

n is an integer between 1 and 2000.

The column stores n bytes (specified by the ACTUAL attribute) which represent up to n characters (specified by the USAGE attribute).

CHAR (n CHAR)

An

An

n is the number of characters, and is an integer between 1 and 2000.

CHAR (n BYTE)

AnV

AnB

n is an integer between 1 and 2000.

The column stores n bytes (specified by the ACTUAL attribute) which represent up to n characters (specified by the USAGE attribute).

VARCHAR2 (n)

or

VARCHAR (n)

AnV

AnVB

n is an integer between 1 and 4000.

The column stores up to n bytes (specified by the ACTUAL attribute) which represent up to n characters (specified by the USAGE attribute).

VARCHAR2 (n CHAR)

AnV

AnV

n is the number of characters, and is an integer between 1 and 4000.

VARCHAR2 (n BYTE)

AnV

AnVB

n is an integer between 1 and 4000.

The column stores up to n bytes (specified by the ACTUAL attribute) which represent up to n characters (specified by the USAGE attribute).



x
Controlling the Mapping of Large Character Data Types

How to:

The SET parameter CONVERSION LONGCHAR controls the mapping of supported Oracle data types listed below. By default, the server maps these data types as alphanumeric (A). The server data type A supports a maximum of 4096 characters for TABLE/MODIFY and 32768 characters for API applications.

The following table lists data type mappings based on the value of LONGCHAR.

Oracle Data Type

 

Remarks

LONGCHAR ALPHA or BLOB

LONGCHAR TEXT

USAGE

ACTUAL

USAGE

ACTUAL

CHAR (n)

n is an integer between 1 and 2000

An

An

TX50

TX

VARCHAR (n)

n is an integer between 1 and 4000

AnV

AnV

TX50

TX

VARCHAR2 (n)

n is an integer between 1 and 4000

AnV

AnV

TX50

TX

RAW (n)

n is an integer between 1 and 2000m = 2 * n

Am

Am

TX50

TX



x
Syntax: How to Control the Mapping of Large Character Data Types
x
ENGINE SQLORA SET CONVERSION LONGCHAR {ALPHA|TEXT|BLOB}

where:

SQLORA

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

ALPHA

Maps the Oracle data types CHAR, NCHAR, VARCHAR, VARCHAR2, NVARCHAR2, and RAW as alphanumeric (A). ALPHA is the default value.

TEXT

Maps the Oracle data types CHAR, NCHAR, VARCHAR, VARCHAR2, NVARCHAR2, and RAW as text (TX). Use this value for WebFOCUS applications.

BLOB

For UNIX, Windows, OpenVMS, and IBM i, is identical to ALPHA. That is, it maps the Oracle data types CHAR, NCHAR, VARCHAR, VARCHAR2, NVARCHAR2, and RAW as alphanumeric (A).

For z/OS, maps the Oracle data types CHAR, NCHAR, VARCHAR, VARCHAR2, NVARCHAR2, and RAW as binary large object (BLOB).


Top of page

x
Controlling the Mapping of Variable-Length Data Types

How to:

The SET parameter VARCHAR controls the mapping of the Oracle data types VARCHAR, VARCHAR2, and NVARCHAR2. By default, the server maps these data types as variable character (AnV).

The following table lists data type mappings based on the value of VARCHAR:

Oracle Data Type

 

Remarks

VARCHAR ON

VARCHAR OFF

USAGE

ACTUAL

USAGE

ACTUAL

VARCHAR (n)

n is an integer between 1 and 4000

AnV

AnV

An

An

VARCHAR2 (n)

n is an integer between 1 and 4000

AnV

AnV

An

An

NVARCHAR2 (n)

n is an integer between 1 and 4000

AmV

AmV

Am

Am



x
Syntax: How to Control the Mapping of Variable-Length Data Types
ENGINE SQLORA SET VARCHAR {ON|OFF}

where:

SQLORA

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

ON

Maps the Oracle data types VARCHAR, VARCHAR2, and NVARCHAR2 as variable-length alphanumeric (AnV). This is required for Unicode environments. ON is the default value.

OFF

Maps the Oracle data types VARCHAR, VARCHAR2, and NVARCHAR2 as alphanumeric (A). ON is the default value.


Top of page

x
Considerations for the CHAR and VARCHAR2 Data Types

How to:

Special attention must be paid to CHAR and VARCHAR2 data types. When you compare a CHAR data type column to a VARCHAR2 data type column, where the only difference is additional trailing spaces in the CHAR data type column, Oracle treats the column values as different.

The SET parameter lets you specify which of the two data types will be used for inserting, updating, and retrieving data.

If you create the tables outside of the server, we recommend that you use either CHAR or VARCHAR2 data types, but not both. If you create a table with both data types, you might not be able to retrieve the data you inserted due to Oracle's comparison mechanism. When inserting data into VARCHAR2 columns outside of the server, do not insert any trailing spaces.

If you use the server to generate Oracle tables and retrieve data, you will not encounter this problem, since the data type being used will be either CHAR or VARCHAR2, depending upon the ORACHAR setting.



x
Syntax: How to Set ORACHAR
ENGINE SQLORA SET ORACHAR {FIX|VAR}

where:

SQLORA

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

FIX

Uses the CHAR data type. This is the default value.

VAR

Uses the VARCHAR2 data type.


Top of page

x
Trailing Blanks in SQL Expressions

The new SQL Expression generator in the TABLE Adapter by default preserves literal contents, including trailing blanks in string literals and the fractional part and exponential notation in numeric literals. This allows greater control over the generated SQL.

In some rare cases when trailing blanks are not needed, the following syntax

ENGINE SQLORA SET TRIM_LITERALS ON

is available to ensure backward compatibility.


Top of page

x
Changing the Precision and Scale of Numeric Columns

How to:

You can alter the length and scale of numeric columns returned by a SELECT request to the server by creating different specifications in your login profile or in a stored procedure. The conversion settings are reflected in the Master File in the USAGE and ACTUAL formats of the fields generated by CREATE SYNONYM. This affects how the fields are processed and formatted by the server.

Tip: You can change this setting manually or from the Web Console.



x
Syntax: How to Override the Default Precision and Scale
x
ENGINE SQLORA SET CONVERSION RESET
ENGINE SQLORA SET CONVERSION format RESET
ENGINE SQLORA SET CONVERSION format [PRECISION precision [scale]]
ENGINE SQLORA SET CONVERSION format [PRECISION MAX]

where:

SQLORA

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

RESET

Returns any previously specified precision and scale values to the adapter defaults. If you specify RESET immediately following the SET CONVERSION command, all data types return to the defaults. If you specify RESET following a particular data type, only columns of that data type are reset.

format

Is any valid format supported by the data source. Possible values are:

INTEGER which indicates that the command applies only to INTEGER columns.

DECIMAL which indicates that the command applies only to DECIMAL columns.

REAL which indicates that the command applies only to single-precision floating-point columns. Note: Only applies to DB2, CA-IDMS/SQL, Microsoft SQL Server, and Sybase.

FLOAT which indicates that the command applies only to double-precision floating-point columns.

precision

Is the precision. Must be greater than 1 and less than or equal to the maximum allowable value for the data type (see the description of MAX).

scale

Is the scale. This is valid with DECIMAL, FLOAT and REAL data types. If you do not specify a value for scale, the current scale setting remains in effect. The default scale value is 2.

If the scale is not required, you must set the scale to 0 (zero).

MAX

Sets the precision to the maximum allowable value for the indicated data type:

Data Type

MAX Precision

INTEGER

11

DECIMAL

33

REAL

9

FLOAT

20

Note: When issuing the CREATE SYNONYM command while the CONVERSION command is active in the profile, the Master File reflects the scale and length that is set by the CONVERSION command.

However, when issuing a SELECT statement, the answer set description does not use the information in the Master File. The length and scale used for the answer set description depends on whether a CONVERSION command is in effect.

If a CONVERSION command is in effect, the answer set description uses the length and scale that is set by the CONVERSION command.

If a CONVERSION command is not in effect, the answer set description uses the actual length and scale of the data.



Example: Setting the Precision and Scale Attributes

The following example shows how to set the precision attribute for all INTEGER and SMALLINT fields to 7:

ENGINE SQLORA SET CONVERSION INTEGER PRECISION 7

The following example shows how to set the precision attribute for all DOUBLE PRECISION fields to 14 and the scale attribute to 3:

ENGINE SQLORA SET CONVERSION FLOAT PRECISION 14 3

The following example shows how to set the precision attribute for all INTEGER and SMALLINT fields to the default:

ENGINE SQLORA SET CONVERSION INTEGER RESET

The following example shows how to set the precision and scale attributes for all fields to the defaults:

ENGINE SQLORA SET CONVERSION RESET

Top of page

x
Considerations for the NUMBER Data Type

How to:

When working with the NUMBER data type, where the precision is between 32 and 37, by default the NUMBER data type is mapped to the server data type double float (D), with a precision of 20 and a scale of 2.

When working with the NUMBER data type, where the precision is 38, by default the NUMBER data type is mapped to the server data type Integer (I), with a display length of 11.

To override the precision of the NUMBER data type, where the precision is between 32 and 38, use the ORANUMBER setting.



x
Syntax: How to Set ORANUMBER
ENGINE SQLORA SET ORANUMBER {COMPAT|DECIMAL}

where:

SQLORA

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

COMPAT

Indicates that the NUMBER data type will be mapped to the server data type double float (D), with a precision of 20 and a scale of 2. COMPAT is the default value.

DECIMAL

Indicates that the NUMBER data type will be mapped to the server data type decimal (P), with a precision of 33.


iWay Software