Oracle 19c - Database Gateway SQL Server Users Guide

Oracle® Database Gateway for SQL
Server
User's Guide
19c
F18235-02
January 2021
Oracle Database Gateway for SQL Server User's Guide, 19c
F18235-02
Copyright © 2002, 2021, Oracle and/or its affiliates.
Primary Author: Rhonda Day
Contributing Authors: Vira Goorah, Juan Pablo Ahues-Vasquez, Peter Castro, Charles Benet, Peter Wong,
Govind Lakkoju
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,
any programs embedded, installed or activated on delivered hardware, and modifications of such programs)
and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government
end users are "commercial computer software" or "commercial computer software documentation" pursuant
to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,
the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works,
and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs
embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle
computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the
license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud
services are defined by the applicable contract for such services. No other rights are granted to the U.S.
Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,
and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise
set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not
be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface
Audience xi
Documentation Accessibility xi
Related Documentation xii
Conventions xii
1 Introduction to the Oracle Database Gateway for SQL Server

1.1 Overview of Oracle Database Gateways 1-1
1.2 About Heterogeneous Services Technology 1-1
1.3 About Oracle Database Gateway for SQL Server 1-2
2 SQL Server Gateway Features and Restriction

2.1 Remote Insert Rowsource 2-1
2.2 Using the Pass-Through Feature 2-2
2.3 Executing Stored Procedures and Functions 2-3
2.4 CHAR Semantics 2-3
2.5 Multi-byte Character Sets Ratio Suppression 2-3
2.6 IPv6 Support 2-3
2.7 Gateway Session IDLE Timeout 2-4
2.8 Remote User-defined Function Support 2-4
2.8.1 Return Values and Stored Procedures 2-4
2.8.2 Result Sets and Stored Procedures 2-5
2.8.2.1 OCI Program Fetching from Result Sets in Sequential Mode 2-6
2.8.2.2 PL/SQL Program Fetching from Result Sets in Sequential Mode 2-7
2.9 Database Compatibility Issues for SQL Server 2-8
2.9.1 Implicit Transactions (Chained Mode) 2-9
2.9.2 Column Definitions 2-9
2.9.3 Naming Rules 2-9
2.9.3.1 Rules for Naming Objects 2-9
2.9.3.2 Case Sensitivity 2-9
2.9.4 Data Types 2-10
iii
2.9.4.1 Binary Literal Notation 2-10
2.9.4.2 Bind Variables With LONG Columns 2-10
2.9.4.3 Data Type Conversion 2-11
2.9.5 Queries 2-11
2.9.5.1 Row Selection 2-11
2.9.5.2 Empty Strings 2-11
2.9.5.3 Empty Bind Variables 2-12
2.9.6 Locking 2-12
2.10 Known Restrictions 2-12
2.10.1 Multiple Open Statements 2-13
2.10.2 Transactional Integrity 2-13
2.10.3 Transaction Capability 2-13
2.10.4 COMMIT or ROLLBACK in PL/SQL Cursor Loops Closes Open
Cursors 2-13
2.10.5 Stored Procedures 2-14
2.10.6 Pass-Through Feature 2-14
2.10.7 DDL Statements 2-14
2.10.8 SQL Syntax 2-15
2.10.8.1 WHERE CURRENT OF Clause 2-15
2.10.8.2 CONNECT BY Clause 2-15
2.10.8.3 Functions in Subqueries 2-16
2.10.8.4 Parameters in Subqueries 2-16
2.10.8.5 Data Dictionary Table and Views in UPDATE Statement 2-16
2.10.8.6 ROWID 2-16
2.10.8.7 TO_DATE 2-16
2.10.8.8 EXPLAIN PLAN Statement 2-16
2.10.9 Functions 2-16
2.10.10 SQL*Plus COPY Command with Lowercase Table Names 2-16
2.10.11 Database Links 2-16
2.11 Known Problems 2-17
2.11.1 Encrypted Format Login 2-17
2.11.2 Date Arithmetic 2-17
2.11.3 SQL Server IMAGE, TEXT and NTEXT Data Types 2-17
2.11.4 String Functions 2-18
2.11.5 Schema Names and PL/SQL 2-18
2.11.6 Data Dictionary Views and PL/SQL 2-18
2.11.7 Stored Procedures 2-18
3 Case Studies
3.1 Case Descriptions 3-1
3.2 Installation Media Contents 3-1
iv
3.3 Demonstration Files 3-2
3.4 Demonstration Requirements 3-2
3.5 Creating Demonstration Tables 3-2
3.5.1 Demonstration Table Definitions 3-3
3.5.2 Demonstration Table Contents 3-4
3.6 Case 1: Simple Queries 3-5
3.7 Case 2: A More Complex Query 3-5
3.8 Case 3: Joining SQL Server Tables 3-5
3.9 Case 4: Write Capabilities 3-5
3.9.1 DELETE Statement 3-5
3.9.2 UPDATE Statement 3-5
3.9.3 INSERT Statement 3-6
3.10 Case 5: Data Dictionary Query 3-6
3.11 Case 6: The Pass-Through Feature 3-6
3.11.1 UPDATE Statement 3-6
3.11.2 SELECT Statement 3-6
3.12 Case 7: Executing Stored Procedures 3-6
A Data Type Conversion
B Supported SQL Syntax and Functions

B.1 Supported SQL Statements B-1
B.1.1 DELETE B-1
B.1.2 INSERT B-1
B.1.3 SELECT B-2
B.1.4 UPDATE B-2
B.2 Oracle Functions B-2
B.2.1 Functions Not Supported by SQL Server B-2
B.2.2 Functions Supported by SQL Server B-2
B.2.2.1 Arithmetic Operators B-3
B.2.2.2 Comparison Operators B-3
B.2.2.3 Pattern Matching B-3
B.2.2.4 Group Functions B-3
B.2.2.5 String Functions B-4
B.2.2.6 Other Functions B-4
B.2.3 Functions Supported by the Gateway B-4
C Data Dictionary
C.1 Data Dictionary Support C-1
v
C.1.1 SQL Server System Tables C-1
C.1.2 Accessing the Gateway Data Dictionary C-1
C.1.3 Direct Queries to SQL Server Tables C-2
C.1.4 Supported Views and Tables C-2
C.2 Data Dictionary Mapping C-3
C.2.1 Default Column Values C-4
C.3 Gateway Data Dictionary Descriptions C-4
C.4 ALL_CATALOG C-5
C.5 ALL_COL_COMMENTS C-5
C.6 ALL_CONS_COLUMNS C-5
C.7 ALL_CONSTRAINTS C-6
C.8 ALL_IND_COLUMNS C-6
C.9 ALL_INDEXES C-7
C.10 ALL_OBJECTS C-8
C.11 ALL_TAB_COLUMNS C-9
C.12 ALL_TAB_COMMENTS C-10
C.13 ALL_TABLES C-10
C.14 ALL_USERS C-11
C.15 ALL_VIEWS C-11
C.16 DBA_CATALOG C-12
C.17 DBA_COL_COMMENTS C-12
C.18 DBA_OBJECTS C-12
C.19 DBA_TAB_COLUMNS C-13
C.20 DBA_TAB_COMMENTS C-14
C.21 DBA_TABLES C-14
C.22 DICT_COLUMNS C-15
C.23 DICTIONARY C-16
C.24 DUAL C-16
C.25 TABLE_PRIVILEGES C-16
C.26 USER_CATALOG C-17
C.27 USER_COL_COMMENTS C-17
C.28 USER_CONS_COLUMNS C-17
C.29 USER_CONSTRAINTS C-17
C.30 USER_IND_COLUMNS C-18
C.31 USER_INDEXES C-18
C.32 USER_OBJECTS C-20
C.33 USER_TAB_COLUMNS C-20
C.34 USER_TAB_COMMENTS C-21
C.35 USER_TABLES C-22
C.36 USER_USERS C-23
vi
C.37 USER_VIEWS C-23
D Initialization Parameters
D.1 Initialization Parameter File Syntax D-1
D.2 Oracle Database Gateway for SQL Server Initialization Parameters D-2
D.3 HS_CALL_NAME D-3
D.4 HS_DB_DOMAIN D-4
D.5 HS_DB_INTERNAL_NAME D-4
D.6 HS_DB_NAME D-4
D.7 HS_DESCRIBE_CACHE_HWM D-5
D.8 HS_FDS_ARRAY_EXEC D-5
D.9 HS_FDS_AUTHENTICATE_METHOD D-5
D.10 HS_FDS_CONNECT_INFO D-6
D.11 HS_FDS_DATE_MAPPING D-7
D.12 HS_FDS_ENCRYPT_SESSION D-7
D.13 HS_FDS_FETCH_ROWS D-7
D.14 HS_FDS_PROC_IS_FUNC D-7
D.15 HS_FDS_RECOVERY_ACCOUNT D-8
D.16 HS_FDS_RECOVERY_PWD D-8
D.17 HS_FDS_REMOTE_DB_CHARSET D-8
D.18 HS_FDS_REPORT_REAL_AS_DOUBLE D-9
D.19 HS_FDS_RSET_RETURN_ROWCOUNT D-9
D.20 HS_FDS_RESULTSET_SUPPORT D-9
D.21 HS_FDS_SQLLEN_INTERPRETATION D-10
D.22 HS_FDS_SUPPORT_STATISTICS D-10
D.23 HS_FDS_TIMESTAMP_MAPPING D-10
D.24 HS_FDS_TRACE_LEVEL D-11
D.25 HS_FDS_TRANSACTION_ISOLATION D-11
D.26 HS_FDS_TRANSACTION_LOG D-11
D.27 HS_FDS_TRUSTSTORE_FILE D-12
D.28 HS_FDS_TRUSTSTORE_PASSWORD D-12
D.29 HS_FDS_VALIDATE_SERVER_CERT D-12
D.30 HS_IDLE_TIMEOUT D-13
D.31 HS_KEEP_REMOTE_COLUMN_SIZE D-13
D.32 HS_LANGUAGE D-13
D.32.1 Character Sets D-14
D.32.2 Language D-14
D.32.3 Territory D-14
D.33 HS_LONG_PIECE_TRANSFER_SIZE D-15
D.34 HS_NLS_LENGTH_SEMANTICS D-15
vii
D.35 HS_OPEN_CURSORS D-15
D.36 HS_RPC_FETCH_REBLOCKING D-15
D.37 HS_RPC_FETCH_SIZE D-16
D.38 HS_TIME_ZONE D-16
D.39 HS_TRANSACTION_MODEL D-17
D.40 IFILE D-17
Index
viii
List of Tables
A-1 Data Type Mapping and Restrictions A-1
C-1 Oracle Data Dictionary View Names and SQL Server Equivalents C-3
C-2 ALL_CATALOG C-5
C-3 ALL_COL_COMMENTS C-5
C-4 ALL_CONS_COLUMNS C-5
C-5 ALL_CONSTRAINTS C-6
C-6 ALL_IND_COLUMNS C-6
C-7 ALL_INDEXES C-7
C-8 ALL_OBJECTS C-8
C-9 ALL_TAB_COLUMNS C-9
C-10 ALL_TAB_COMMENTS C-10
C-11 ALL_TABLES C-10
C-12 ALL_USERS C-11
C-13 ALL_VIEWS C-11
C-14 DBA_CATALOG C-12
C-15 DBA_COL_COMMENTS C-12
C-16 DBA_OBJECTS C-12
C-17 DBA_TAB_COLUMNS C-13
C-18 DBA_TAB_COMMENTS C-14
C-19 DBA_TABLES C-14
C-20 DICT_COLUMNS C-15
C-21 DICTIONARY C-16
C-22 DUAL C-16
C-23 TABLE_PRIVILEGES C-16
C-24 USER_CATALOG C-17
C-25 USER_COL_COMMENTS C-17
C-26 USER_CONS_COLUMNS C-17
C-27 USER_CONSTRAINTS C-17
C-28 USER_IND_COLUMNS C-18
C-29 USER_INDEXES C-18
C-30 USER_OBJECTS C-20
C-31 USER_TAB_COLUMNS C-20
C-32 USER_TAB_COMMENTS C-21
C-33 USER_TABLES C-22
C-34 USER_USERS C-23
ix
C-35 USER_VIEWS C-23
x
Preface
This manual describes the Oracle Database Gateway for SQL Server, which enables
Oracle client applications to access SQL Server data through Structured Query
Language (SQL). The gateway, with the Oracle database, creates the appearance
that all data resides on a local Oracle database, even though the data can be widely
distributed.
This preface covers the following topics:
• Audience
• Documentation Accessibility
• Related Documentation
• Conventions
Audience
This manual is intended for Oracle database administrators who perform the following
tasks:
• Installing and configuring the Oracle Database Gateway for SQL Server
• Diagnosing gateway errors
• Using the gateway to access SQL Server data
Note:
You should understand the fundamentals of Oracle Database Gateways
and the Microsoft Windows operating system before using this guide to
install or administer the gateway.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the
Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
Access to Oracle Support

Oracle customers that have purchased support have access to electronic support
through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/
lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs
if you are hearing impaired.
xi
Preface
Related Documentation
For more information, see the following documents:
• Oracle Database New Features Guide
• Oracle Call Interface Programmer's Guide
• Oracle Database Administrator's Guide
• Oracle Database Development Guide
• Oracle Database Concepts
• Oracle Database Performance Tuning Guide
• Oracle Database Error Messages
• Oracle Database Globalization Support Guide
• Oracle Database Reference
• Oracle Database SQL Language Reference
• Oracle Database Net Services Administrator's Guide
• SQL*Plus User's Guide and Reference
• Oracle Database Heterogeneous Connectivity User's Guide
• Oracle Database 2 Day DBA
• Oracle Database Security Guide
Many of the examples in this book use the sample schemas of the seed database,
which is installed by default when you install Oracle. Refer to Oracle Database Sample
Schemas for information on how these schemas were created and how you can use
them yourself.
Printed documentation is available for sale in the Oracle Store at
https://shop.oracle.com/
Conventions
The following text conventions are used in this document:
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code
in examples, text that appears on the screen, or text that you enter.
xii
1
Introduction to the Oracle Database
Gateway for SQL Server
Oracle Database Gateways provide the ability to transparently access data residing in
a non-Oracle system from an Oracle environment. The following sections briefly cover
Heterogeneous Services, the technology that the Oracle Database Gateway for SQL
Server is based on.
To get a good understanding of generic gateway technology, Heterogeneous Services,
and how Oracle Database Gateways fit in the picture, reading Oracle Database
Heterogeneous Connectivity User's Guide first is highly recommended.
Topics:
• Overview of Oracle Database Gateways
• About Heterogeneous Services Technology
• Oracle Database Gateways
1.1 Overview of Oracle Database Gateways

Heterogeneous data access is a problem that affects a lot of companies. A lot of
companies run several different database systems. Each of these systems stores data
and has a set of applications that run against it. Consolidation of this data in one
database system is often hard-in large part because many of the applications that
run against one database may not have an equivalent that runs against another. Until
such time as migration to one consolidated database system is made feasible, it is
necessary for the various heterogeneous database systems to interoperate.
Oracle Database Gateways provide the ability to transparently access data residing
in a non-Oracle system from an Oracle environment. This transparency eliminates the
need for application developers to customize their applications to access data from
different non-Oracle systems, thus decreasing development efforts and increasing the
mobility of the application. Applications can be developed using a consistent Oracle
interface for both Oracle and SQL Server.
Gateway technology is composed of two parts: a component that has the generic
technology to connect to a non-Oracle system, which is common to all the non-Oracle
systems, called Heterogeneous Services, and a component that is specific to the non-
Oracle system that the gateway connects to. Heterogeneous Services, in conjunction
with the Oracle Database Gateway agent, enables transparent access to non-Oracle
systems from an Oracle environment.
1.2 About Heterogeneous Services Technology

Heterogeneous Services provides the generic technology for connecting to non-Oracle
systems. As an integrated component of the database, Heterogeneous Services can
exploit features of the database, such as the powerful SQL parsing and distributed
optimization capabilities.
1-1
Chapter 1
About Oracle Database Gateway for SQL Server
Heterogeneous Services extend the Oracle SQL engine to recognize the SQL and
procedural capabilities of the remote non-Oracle system and the mappings required
to obtain necessary data dictionary information. Heterogeneous Services provides two
types of translations: the ability to translate Oracle SQL into the proper dialect of the
non-Oracle system as well as data dictionary translations that displays the metadata
of the non-Oracle system in the local format. For situations where no translations are
available, native SQL can be issued to the non-Oracle system using the pass-through
feature of Heterogeneous Services.
Heterogeneous Services also maintains the transaction coordination between Oracle
and the remote non-Oracle system, such as providing the two-phase commit protocol
to ensure distributed transaction integrity, even for non-Oracle systems that do not
natively support two-phase commit.
See Also:
Oracle Database Heterogeneous Connectivity User's Guide for more
information about Heterogeneous Services.
1.3 About Oracle Database Gateway for SQL Server

The capabilities, SQL mappings, data type conversions, and interface to the remote
non-Oracle system are contained in the gateway. The gateway interacts with
Heterogeneous Services to provide the transparent connectivity between Oracle and
non-Oracle systems.
The gateway can be installed on any machine independent of the Oracle or non-
Oracle database. It can be the same machine as the Oracle database or on the same
machine as the SQL Server database or on a third machine as a standalone.
1-2
2
SQL Server Gateway Features and
Restriction
After the gateway is installed and configured, you can use the gateway to access
SQL Server data, pass SQL Server commands from applications to the SQL Server
database, perform distributed queries, and copy data.
Topics:
• Remote Insert Rowsource
• Using the Pass-Through Feature
• Executing Stored Procedures and Functions
• CHAR Semantics
• Multi-byte Character Sets Ratio Suppression
• IPv6 Support
• Remote User-defined Function Support
• Database Compatibility Issues for SQL Server
• Known Restrictions
• Known Problems
2.1 Remote Insert Rowsource

A remote insert rowsource feature allows remote insert requiring local Oracle data to
work through the Oracle database and Oracle Database Gateway. This functionality
requires that the Oracle database and the Oracle Database Gateway to be version
12.2 or later.
By Oracle Database design, some distributed statement must be executed at the
database link site. But in certain circumstances, there is data needed to execute
these queries that must be fetched from the originating Oracle Database. Under
homogeneous connections, the remote Oracle database would call back the source
Oracle database for such data. But in heterogeneous connections, this is not viable,
because this means that the Foreign Data Store would have to query call back
functions, or data, that can only be provided by the Oracle instance that issued the
query. In general, these kinds of statements are not something that can be supported
through the Oracle Database Gateway.
The following categories of SQL statements results in a callback:
• Any DML with a sub-select, which refers to a table in Oracle database.
• Any DELETE, INSERT, UPDATE or "SELECT... FOR UPDATE..." SQL statement
containing SQL functions or statements that needs to be executed at the
originating Oracle database.
2-1
Chapter 2
Using the Pass-Through Feature
These SQL functions include USER, USERENV, and SYSDATE; and involve the
selection of data from the originating Oracle database.
• Any SQL statement that involves a table in Oracle database, and a LONG or LOB
column in a remote table.
An example of a remote INSERT statement that can work through the remote insert
rowsource feature is as follows:
INSERT INTO gateway_table@gateway_link select * from local_table;
2.2 Using the Pass-Through Feature

The gateway can pass SQL Server commands or statements from the application to
the SQL Server database using the DBMS_HS_PASSTHROUGH package.
Use the DBMS_HS_PASSTHROUGH package in a PL/SQL block to specify the statement to

be passed to the SQL Server database, as follows:
DECLARE
num_rows INTEGER;
BEGIN
num_rows := DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE@MSQL('command');
END;
/
Where command cannot be one of the following:

• BEGIN TRANSACTION
• COMMIT
• ROLLBACK
• SAVE
• SHUTDOWN
• RELEASE
• SAVEPOINT
• CONNECT
• SQL Server tool commands
The DBMS_HS_PASSTHROUGH package supports passing bind values and executing
SELECT statements.
Note:
TRUNCATE cannot be used in a pass-through statement.
2-2
Chapter 2
Executing Stored Procedures and Functions
See Also:
Oracle Database PL/SQL Packages and Types Reference and Chapter
3, Features of Oracle Database Gateways, of Oracle Database
Heterogeneous Connectivity User's Guide for more information about the
DBMS_HS_PASSTHROUGH package.
2.3 Executing Stored Procedures and Functions

Using the procedural feature, the gateway can execute stored procedures that are
defined in the SQL Server database. It is not necessary to relink the gateway or
define the procedure to the gateway, but the procedure's access privileges must permit
access by the user that the gateway is logging in as.
Standard PL/SQL statements are used to execute a stored procedure.
The gateway supports stored procedures in three mutually exclusive modes:
• Normal mode: Have access to IN/OUT arguments only
• Return value mode: Have a return value for all stored procedures
• Resultset mode: Out values are available as last result set
2.4 CHAR Semantics

This feature allows the gateway to optionally run in CHAR Semantics mode. Rather than
always describing SQL Server CHAR columns as CHAR(n BYTE), this feature describes
them as CHAR(n CHAR) and VARCHAR(n CHAR). The concept is similar to Oracle
database CHAR Semantics. You need to specify HS_NLS_LENGTH_SEMANTICS=CHAR
gateway parameter to activate this option. Refer to Initialization Parameters for more
detail.
2.5 Multi-byte Character Sets Ratio Suppression

This feature optionally suppresses the ratio expansion from SQL Server database
to Oracle database involving multi-byte character set. By default, Oracle gateways
assume the worst ratio to prevent data being truncated or insufficient buffer size
situation. However, if you have specific knowledge of your SQL Server database and
do not want the expansion to occur, you can specify HS_KEEP_REMOTE_COLUMN_SIZE
parameter to suppress the expansion. Refer to Initialization Parameters for more
detail.
2.6 IPv6 Support

Besides full IPv6 support between Oracle databases and the gateway, IPv6 is
also supported between this gateway and SQL Server database. Refer to the
HS_FDS_CONNECT_INFO parameter in Initialization Parameters for more detail.
2-3
Chapter 2
Gateway Session IDLE Timeout
2.7 Gateway Session IDLE Timeout

You can optionally choose to terminate long idle gateway sessions automatically with
the gateway parameter HS_IDLE_TIMEOUT. Specifically, when a gateway session is idle
for more than the specified time limit, the gateway session is terminated with any
pending update rolled back. Refer to the HS_IDLE_TIMEOUT parameter in Initialization
Parameters for more detail.
2.8 Remote User-defined Function Support

User-defined functions in a remote non-Oracle database can be used in SQL
statements.
See Also:
Oracle Database Heterogeneous Connectivity User's Guide for more
information about executing user-defined functions on a non-Oracle
database.
2.8.1 Return Values and Stored Procedures

By default, all stored procedures and functions do not return a return value to the user.
To enable return values, set the HS_FDS_PROC_IS_FUNC parameter value to TRUE.
See Also:
Initialization Parameters for information about both editing the initialization
parameter file and the HS_FDS_PROC_IS_FUNC parameter.
Note:
If you set the HS_FDS_PROC_IS_FUNC gateway initialization parameter to TRUE,
you must change the syntax of the procedure execute statement for all
existing stored procedures.
In the following example, the employee name JOHN SMYTHE is passed to the SQL
Server stored procedure REVISE_SALARY. The stored procedure retrieves the salary
value from the SQL Server database to calculate a new yearly salary for JOHN SMYTHE.
The revised salary returned in RESULT is used to update EMP in a table of an Oracle
database:
DECLARE
INPUT VARCHAR2(15);
RESULT NUMBER(8,2);
BEGIN
2-4
Chapter 2
Remote User-defined Function Support
INPUT := 'JOHN SMYTHE';

RESULT := REVISE_SALARY@MSQL(INPUT);
UPDATE EMP SET SAL = RESULT WHERE ENAME =: INPUT;
END;
/
The procedural feature automatically converts non-Oracle data types to and from
PL/SQL data types.
2.8.2 Result Sets and Stored Procedures

The Oracle Database Gateway for SQL Server provides support for stored procedures
which return result sets.
By default, all stored procedures and functions do not return a result set to the user. To
enable result sets, set the HS_FDS_RESULTSET_SUPPORT parameter value to TRUE.
See Also:
Initialization Parameters for information about both editing the initialization
parameter file and the HS_FDS_RESULTSET_SUPPORT parameter. For further
information about Oracle support for result sets in non-Oracle databases see
Oracle Database Heterogeneous Connectivity User's Guide.
Note:
If you set the HS_FDS_RESULTSET_SUPPORT gateway initialization parameter to
TRUE, then you must change the syntax of the procedure execute statement
for all existing stored procedures, else errors will occur.
When accessing stored procedures with result sets through the Oracle Database
Gateway for SQL Server, you will be in the sequential mode of Heterogeneous
Services.
The Oracle Database Gateway for SQL Server returns the following information to
Heterogeneous Services during procedure description:
• All the input arguments of the remote stored procedure
• None of the output arguments
• One out argument of type ref cursor (corresponding to the first result set returned
by the stored procedure)
Client programs have to use the virtual package function
DBMS_HS_RESULT_SET.GET_NEXT_RESULT_SET to get the ref cursor for subsequent result
sets. The last result set returned is the out argument from the procedure.
The limitations of accessing result sets are the following:
• Result sets returned by a remote stored procedure have to be retrieved in the
order in which they were placed on the wire
2-5
Chapter 2
• On execution of a stored procedure, all result sets returned by a previously

executed stored procedure will be closed (regardless of whether the data has
been completely retrieved or not)
In the following example, the SQL Server stored procedure is executed to fetch the
contents of the emp and dept tables from SQL Server:
create procedure REFCURPROC (@arg1 varchar(255), @arg2 varchar(255) output)
as
select @arg2 = @arg1
select * from EMP
select * from DEPT
go
This stored procedure assigns the input parameter arg1 to the output parameter arg2,
opens the query SELECT * FROM EMP in ref cursor rc1, and opens the query SELECT *
FROM DEPT in ref cursor rc2.
2.8.2.1 OCI Program Fetching from Result Sets in Sequential Mode

The following example shows OCI program fetching from result sets in sequential
mode:
OCIEnv *ENVH;
OCISvcCtx *SVCH;
OCIStmt *STMH;
OCIError *ERRH;
OCIBind *BNDH[3];
OraText arg1[20];
OraText arg2[255];
OCIResult *rset;
OCIStmt *rstmt;
ub2 rcode[3];
ub2 rlens[3];
sb2 inds[3];
OraText *stmt = (OraText *) "begin refcurproc@MSQL(:1,:2,:3); end;";
OraText *n_rs_stm = (OraText *)
"begin :ret := DBMS_HS_RESULT_SET.GET_NEXT_RESULT_SET@MSQL; end;";
/* Prepare procedure call statement */
/* Handle Initialization code skipped */

OCIStmtPrepare(STMH, ERRH, stmt, strlen(stmt), OCI_NTV_SYNTAX, OCI_DEFAULT);
/* Bind procedure arguments */

inds[0] = 0;
strcpy((char *) arg1, "Hello World");
rlens[0] = strlen(arg1);
OCIBindByPos(STMH, &BNDH[0], ERRH, 1, (dvoid *) arg1, 20, SQLT_CHR,
(dvoid *) &(inds[0]), &(rlens[0]), &(rcode[0]), 0, (ub4 *) 0,
OCI_DEFAULT);
inds[1] = -1;
OCIBindByPos(STMH, &BNDH[1], ERRH, 1, (dvoid *) arg2, 20, SQLT_CHR,
(dvoid *) &(inds[1]), &(rlens[1]), &(rcode[1]), 0, (ub4 *) 0,
OCI_DEFAULT);
inds[2] = 0;
rlens[2] = 0;
OCIDescriptorAlloc(ENVH, (dvoid **) &rset, OCI_DTYPE_RSET, 0, (dvoid **) 0);
2-6
Chapter 2
OCIBindByPos(STMH, &BNDH[2], ERRH, 2, (dvoid *) rset, 0, SQLT_RSET,

(dvoid *) &(inds[2]), &(rlens[2]), &(rcode[2]),
0, (ub4 *) 0, OCI_DEFAULT);
/* Execute procedure */
OCIStmtExecute(SVCH, STMH, ERRH, 1, 0, (CONST OCISnapshot *) 0,
(OCISnapshot *) 0, OCI_DEFAULT);
/* Convert result set to statement handle */

OCIResultSetToStmt(rset, ERRH);
rstmt = (OCIStmt *) rset;
/* After this the user can fetch from rstmt */

/* Issue get_next_result_set call to get handle to next_result set */
/* Prepare Get next result set procedure call */
OCIStmtPrepare(STMH, ERRH, n_rs_stm, strlen(n_rs_stm), OCI_NTV_SYNTAX,

OCI_DEFAULT);
/* Bind return value */

OCIBindByPos(STMH, &BNDH[1], ERRH, 1, (dvoid *) rset, 0, SQLT_RSET,
(dvoid *) &(inds[1]), &(rlens[1]), &(rcode[1]),
0, (ub4 *) 0, OCI_DEFAULT);
/* Execute statement to get next result set*/

OCIStmtExecute(SVCH, STMH, ERRH, 1, 0, (CONST OCISnapshot *) 0,
(OCISnapshot *) 0, OCI_DEFAULT);
/* Convert next result set to statement handle */

OCIResultSetToStmt(rset, ERRH);
rstmt = (OCIStmt *) rset;
/* Now rstmt will point to the second result set returned by the
remote stored procedure */
/* Repeat execution of get_next_result_set to get the output arguments */
2.8.2.2 PL/SQL Program Fetching from Result Sets in Sequential Mode

Assume that the table loc_emp is a local table exactly like the SQL Server emp
table. The same assumption applies for loc_dept. The table outargs has columns
corresponding to the out arguments of the SQL Server stored procedure.
create table outargs (outarg varchar2(255), retval number);
create or replace package rcpackage is

type RCTYPE is ref cursor;
end rcpackage;
/
declare
rc1 rcpackage.rctype;
rec1 loc_emp%rowtype;
rec2 loc_dept%rowtype;
rec3 outargs%rowtype;
out_arg varchar2(255);
begin
2-7
Chapter 2
Database Compatibility Issues for SQL Server
-- Execute procedure
out_arg := null;
refcurproc@MSQL('Hello World', out_arg, rc1);
-- Fetch 20 rows from the remote emp table and insert them into loc_emp
for i in 1 .. 20 loop
fetch rc1 into rec1;
insert into loc_emp (rec1.empno, rec1.ename, rec1.job,
rec1.mgr, rec1.hiredate, rec1.sal, rec1.comm, rec1.deptno);
end loop;
-- Close ref cursor

close rc1;
-- Get the next result set returned by the stored procedure

rc2 := dbms_hs_result_set.get_next_result_set@MSQL;
-- Fetch 5 rows from the remote dept table and insert them into loc_dept
for i in 1 .. 5 loop
insert into loc_dept values (rec2.deptno, rec2.dname, rec2.loc);
end loop;
--Close ref cursor

close rc2;
-- Get the output arguments from the remote stored procedure

-- Since we are in sequential mode, they will be returned in the
-- form of a result set
rc3 := dbms_hs_result_set.get_next_result_set@MSQL;
-- Fetch them and insert them into the outargs table

insert into outargs (rec3.outarg, rec3.retval);
-- Close ref cursor

close rc3;
end;
/
2.9 Database Compatibility Issues for SQL Server

SQL Server and Oracle databases function differently in some areas, causing
compatibility problems. The compatibility issues are described in the following links:
• Implicit Transactions (Chained Mode)
• Column Definitions
• Naming Rules
• Data Types
• Queries
• Locking
2-8
Chapter 2
2.9.1 Implicit Transactions (Chained Mode)

The gateway supports the ANSI-standard implicit transactions. SQL Server stored
procedures must be written for this mode. Running implicit transactions allows the
gateway to extend the Oracle two-phase commit protection to transactions updating
Oracle and SQL Server databases.
2.9.2 Column Definitions

By default, a SQL Server table column cannot contain null values unless NULL is
specified in the column definition. SQL Server assumes all columns cannot contain
null values unless you set a SQL Server option to override this default.
For an Oracle table, null values are allowed in a column unless NOT NULL is specified
in the column definition.
2.9.3 Naming Rules

Naming rule issues include the following:
• Rules for Naming Objects
• Case Sensitivity
2.9.3.1 Rules for Naming Objects

Oracle and SQL Server use different database object naming rules. For example,
the maximum number of characters allowed for each object name can be different.
Also, the use of single and double quotation marks, case sensitivity, and the use of
alphanumeric characters can all be different.
See Also:
Oracle Database Reference and SQL Server documentation.
2.9.3.2 Case Sensitivity

The Oracle database defaults to uppercase unless you surround identifiers with double
quote characters. For example, to refer to the SQL Server table called emp, enter the
name with double quote characters, as follows:
SQL> SELECT * FROM "emp"@MSQL;
However, to refer to the SQL Server table called emp owned by Scott from an Oracle
application, enter the following:
SQL> SELECT * FROM "Scott"."emp"@MSQL;
If the SQL Server table called emp is owned by SCOTT, a table owner name in
uppercase letters, you can enter the owner name without double quote characters,
as follows:
2-9
Chapter 2
SQL> SELECT * FROM SCOTT."emp"@MSQL;
or
SQL> SELECT * FROM scott."emp"@MSQL;
Oracle recommends that you surround all SQL Server object names with double quote
characters and use the exact letter case for the object names as they appear in the
SQL Server data dictionary. This convention is not required when referring to the
supported Oracle data dictionary tables or views listed in Data Dictionary.
If existing applications cannot be changed according to these conventions, create
views in Oracle to associate SQL Server names to the correct letter case. For
example, to refer to the SQL Server table emp from an existing Oracle application
by using only uppercase names, define the following view:
SQL> CREATE VIEW EMP (EMPNO, ENAME, SAL, HIREDATE)
AS SELECT "empno", "ename", "sal", "hiredate"
FROM "emp"@MSQL;
With this view, the application can issue statements such as the following:
SQL> SELECT EMPNO, ENAME FROM EMP;
Using views is a workaround solution that duplicates data dictionary information

originating in the SQL Server data dictionary. You must be prepared to update the
Oracle view definitions whenever the data definitions for the corresponding tables are
changed in the SQL Server database.
2.9.4 Data Types

Data type issues include the following:
• Binary Literal Notation
• Bind Variables With LONG Columns
• Data Type Conversion
2.9.4.1 Binary Literal Notation

Oracle SQL uses hexadecimal digits surrounded by single quotes to express literal
values being compared or inserted into columns defined as data type RAW.
This notation is not converted to syntax compatible with the SQL Server VARBINARY
and BINARY data types (a 0x followed by hexadecimal digits, surrounded by single
quotes).
For example, the following statement is not supported:
SQL> INSERT INTO BINARY_TAB@MSQL VALUES ('0xff')
Where BINARY_TAB contains a column of data type VARBINARY or BINARY. Use bind
variables when inserting into or updating VARBINARY and BINARY data types.
2.9.4.2 Bind Variables With LONG Columns

The gateway does not support using bind variables to update columns of data type
LONG.
2-10
Chapter 2
2.9.4.3 Data Type Conversion

SQL Server does not support implicit date conversions. Such conversions must be
explicit.
For example, the gateway issues an error for the following SELECT statement:
SELECT DATE_COL FROM TEST@MSQL WHERE DATE_COL = "1-JAN-2004";
To avoid problems with implicit conversions, add explicit conversions, as in the

following:
SELECT DATE_COL FROM TEST@MSQL WHERE DATE_COL = TO_DATE("1-JAN-2004")
See Also:
Data Type Conversion for more information about restrictions on data types.
2.9.5 Queries
Query issues include the following:
• Row Selection
• Empty Strings
• Empty Bind Variables
2.9.5.1 Row Selection

SQL Server evaluates a query condition for all selected rows before returning any of
the rows. If there is an error in the evaluation process for one or more rows, no rows
are returned even though the remaining rows satisfy the condition.
Oracle evaluates the query condition row-by-row and returns a row when the
evaluation is successful. Rows are returned until a row fails the evaluation.
2.9.5.2 Empty Strings

Oracle processes an empty string in a SQL statement as a null value. SQL Server
processes an empty string as an empty string.
When comparing an empty string the gateway passes literal empty strings to the SQL
Server database without any conversion. If you intended an empty string to represent
a null value, SQL Server does not process the statement that way; it uses the empty
string.
You can avoid this problem by using NULL or IS NULL in the SQL statement instead of
the empty string syntax, as in the following example:
SELECT * from "emp"@MSQL where "ename" IS NULL;
To select an empty string:
2-11
Chapter 2
Known Restrictions
• For VARCHAR columns, the gateway returns an empty string to the Oracle database
as NULL value.
• For CHAR columns, the gateway returns the full size of the column with each
character as empty space (' ').
2.9.5.3 Empty Bind Variables

For VARCHAR bind variables, the gateway passes empty bind variables to the SQL
Server database as a NULL value.
2.9.6 Locking
The locking model for an SQL Server database differs significantly from the Oracle
model. The gateway depends on the underlying SQL Server behavior, so the following
possible scenarios can affect Oracle applications that access SQL Server through the
gateway:
• Read access might block write access
• Write access might block read access
• Statement-level read consistency is not guaranteed
See Also:
SQL Server documentation for information about the SQL Server locking
model.
2.10 Known Restrictions

If you encounter incompatibility problems not listed in this section or in "Known
Problems", contact Oracle Support Services. The following section describes the
known restrictions and includes suggestions for dealing with them when possible:
• Multiple Open Statements
• Transactional Integrity
• Transaction Capability
• COMMIT or ROLLBACK in PL/SQL Cursor Loops Closes Open Cursors
• Stored Procedures
• Pass-Through Feature
• DDL Statements
• SQL Syntax
• Functions
• SQL*Plus COPY Command with Lowercase Table Names
• Database Links
2-12
Chapter 2
Known Restrictions
Note:
If you have any questions or concerns about the restrictions, contact Oracle
Support Services.
2.10.1 Multiple Open Statements

Accessing SQL Server has the limitation that one open statement or cursor is allowed
for each connection. If a second statement or cursor needs to open in the same
transaction to access SQL Server, it requires a new connection.
Because of this limitation multiple open statements or cursors within the same
transaction can lock each other because they use different connections to SQL Server.
To avoid this restriction, issue a commit, or modify the logic, or both.
2.10.2 Transactional Integrity

The gateway cannot guarantee transactional integrity in the following cases:
• When a statement that is processed by the gateway causes an implicit commit in
the target database
• When the target database is configured to work in Autocommit Mode
Note:
Oracle strongly recommends the following:
– If you know that executing a particular statement causes an implicit
commit in the target database, then ensure that this statement is
executed in its own transaction.
The gateway sets Autocommit Mode to Off when a connection is established to the
SQL Server database.
2.10.3 Transaction Capability

The gateway does not support savepoints. If a distributed update transaction is under
way involving the gateway, and a user attempts to create a savepoint, the following
error occurs:
ORA-02070: database dblink does not support savepoint in this context
By default, the gateway is configured as COMMIT_CONFIRM.
2.10.4 COMMIT or ROLLBACK in PL/SQL Cursor Loops Closes Open

Cursors
Any COMMIT or ROLLBACK issued in a PL/SQL cursor loop closes all open cursors, which
can result in the following error:
2-13
Chapter 2
Known Restrictions
ORA-1002: fetch out of sequence
To prevent this error, move the COMMIT or ROLLBACK statement outside the cursor loop.
2.10.5 Stored Procedures

The Oracle transaction manager or Oracle COMMIT or ROLLBACK commands cannot
contril changes issued through stored procedures that embed commits or rollbacks
When accessing stored procedures with result sets through the Oracle Database
Gateway for SQL Server, you must work in the sequential mode of Heterogeneous
Services.
When accessing stored procedures with multiple result sets through the Oracle
Database Gateway for SQL Server, you must read all the result sets before continuing.
Output parameters of stored procedures must be initialized to an empty string.
2.10.6 Pass-Through Feature

If the SQL statements being passed through the gateway result in an implicit commit
at the SQL Server database, the Oracle transaction manager is unaware of the commit
and an Oracle ROLLBACK command cannot be used to roll back the transaction.
2.10.7 DDL Statements

SQL Server requires some DDL statements to be executed in their own transaction,
and only one DDL statement can be executed in a given transaction.
If you use these DDL statements in a SQL Server stored procedure and you execute
the stored procedure through the gateway using the procedural feature, or, if you
execute the DDL statements through the gateway using the pass-through feature,
an error condition might result. This is because the procedural feature and the
pass-through feature of the gateway cannot guarantee that the DDL statements are
executed in their own separate transaction.
The following SQL Server DDL statements can cause an error condition if you attempt
to pass them with the gateway pass-through feature, or if you execute a SQL Server
stored procedure that contains them:
• ALTER DATABASE
• CREATE DATABASE
• CREATE INDEX
• CREATE PROCEDURE
• CREATE TABLE
• CREATE VIEW
• DISK INIT
• DROP <object>
• DUMP TRANSACTION
• GRANT
2-14
Chapter 2
Known Restrictions
• LOAD DATABASE
• LOAD TRANSACTION
• RECONFIGURE
• REVOKE
• SELECT INTO
• TRUNCATE TABLE
• UPDATE STATISTICS
See Also:
SQL Server documentation for more information about DDL statements.
2.10.8 SQL Syntax

This section lists restrictions on the following SQL syntax:
• WHERE CURRENT OF Clause
• CONNECT BY Clause
• Functions in Subqueries
• Parameters in Subqueries
• Data Dictionary Table and Views in UPDATE Statement
• ROWID
• TO_DATE
• EXPLAIN PLAN Statement
See Also:
Supported SQL Syntax and Functions for more information about restrictions
on SQL syntax.
2.10.8.1 WHERE CURRENT OF Clause

UPDATE and DELETE statements with the WHERE CURRENT OF clause are not supported
by the gateway because they rely on the Oracle ROWID implementation. To update or
delete a specific row through the gateway, a condition style WHERE clause must be
used.
2.10.8.2 CONNECT BY Clause

The gateway does not support the CONNECT BY clause in a SELECT statement.
2-15
Chapter 2
Known Restrictions
2.10.8.3 Functions in Subqueries

Bind variables and expressions are not supported as operands in string functions or
mathematical functions, when part of subquery in an INSERT, UPDATE, or DELETE SQL
statement.
2.10.8.4 Parameters in Subqueries

Due to a limitation in SQL Server, you cannot use parameters in subqueries.
2.10.8.5 Data Dictionary Table and Views in UPDATE Statement

Data dictionary tables and views in the SET clause of an UPDATE statement are not
supported.
2.10.8.6 ROWID
The Oracle ROWID implementation is not supported.
2.10.8.7 TO_DATE
TO_DATE is a reserved word and cannot be used as a database identifier name.
2.10.8.8 EXPLAIN PLAN Statement

The EXPLAIN PLAN statement is not supported.
2.10.9 Functions
The following restrictions apply to using functions:
• Unsupported functions cannot be used in statements that refer to LONG columns.
• When negative numbers are used as the second parameter in a SUBSTR function,
incorrect results are returned. This is due to incompatibility between the Oracle
SUBSTR function and the equivalent in SQL Server.
2.10.10 SQL*Plus COPY Command with Lowercase Table Names

You need to wrap lower case table names in double quotes.
For example:
copy from tkhouser/tkhouser@inst1 insert loc_tkhodept using select * from
"tkhodept"@holink2;
2.10.11 Database Links

The gateway is not multithreaded and cannot support shared database links. Each
gateway session spawns a separate gateway process and connections cannot be
shared.
2-16
Chapter 2
Known Problems
2.11 Known Problems

This section describes known problems and includes suggestions for correcting them
when possible. If you have any questions or concerns about the problems, contact
Oracle Support Services. A current list of problems is available online. Contact your
local Oracle office for information about accessing the list.
The following known problems are described in this section:
• Encrypted Format Login
• Date Arithmetic
• SQL Server IMAGE_ TEXT and NTEXT Data Types
• String Functions
• Schema Names and PL/SQL
• Data Dictionary Views and PL/SQL
• Stored Procedures
2.11.1 Encrypted Format Login

The Oracle9i database (Release 9.2 and earlier) supported an Oracle initialization
parameter, DBLINK_ENCRYPT_LOGIN. When this parameter is set to TRUE, the password
for the login user ID is not sent over the network.
If this parameter is set to TRUE in the initialization parameter file used by the Oracle9i
database, you must change the setting to FALSE, the default setting, to allow Oracle9i
to communicate with the gateway.
In the current release, the DBLINK_ENCRYPT_LOGIN initialization parameter is obsolete,
so you do not need to check it.
2.11.2 Date Arithmetic

The following SQL expressions do not function correctly with the gateway:
date + number
number + date
date - number
date1 - date2
Statements with the preceding expressions are sent to the SQL Server database
without any translation. Since SQL Server does not support these date arithmetic
functions, the statements return an error.
2.11.3 SQL Server IMAGE, TEXT and NTEXT Data Types

The following restrictions apply when using IMAGE, TEXT, and NTEXT data types:
• An unsupported SQL function cannot be used in a SQL statement that accesses a

column defined as SQL Server data type IMAGE, TEXT, or NTEXT.
• You cannot use SQL*Plus to select data from a column defined as SQL Server
data type IMAGE, TEXT, or NTEXT when the data is greater than 80 characters in
2-17
Chapter 2
Known Problems
length. Oracle recommends using Pro*C or Oracle Call Interface to access such
data in a SQL Server database.
• IMAGE, TEXT, and NTEXT data cannot be read through pass-through queries.
• If a SQL statement is accessing a table including an IMAGE, TEXT, or NTEXT column,
the statement will be sent to SQL Server as two separate statements. One
statement to access the IMAGE, TEXT or NTEXT column, and a second statement
for the other columns in the original statement.
The gateway does not support the PL/SQL function COLUMN_VALUE_LONG of the
DBMS_SQL package.
See Also:
Supported SQL Syntax and Functions for more information about restrictions
on SQL syntax.
2.11.4 String Functions

If you concatenate numeric literals using the "||" or CONCAT operator when using the
gateway to query a SQL Server database, the result is an arithmetic addition. For
example, the result of the following statement is 18:
SQL> SELECT 9 || 9 FROM DUAL@MSQL;
The result is 99 when using Oracle to query an Oracle database.
2.11.5 Schema Names and PL/SQL

If you do not prefix a SQL Server database object with its schema name in a SQL
statement within a PL/SQL block, the following error message occurs:
ORA-6550 PLS-201 Identifier table_name must be declared.
Change the SQL statement to include the schema name of the object.
2.11.6 Data Dictionary Views and PL/SQL

You cannot refer to data dictionary views in SQL statements that are inside a PL/SQL
block.
2.11.7 Stored Procedures

Return values of stored procedures that return result sets are incorrect.
2-18
3
Case Studies
The following case studies for SQL Server demonstrate some of the features of the
Oracle Database Gateway. You can verify that the gateway is installed and operating
correctly by using the demonstration files included in the distribution media.
The demonstration files are automatically copied to disk when the gateway is installed.
Topics:
• Case Descriptions
• Installation Media Contents
• Demonstration Files
• Demonstration Requirements
• Creating Demonstration Tables
• Case 1: Simple Queries
• Case 2: A More Complex Query
• Case 3: Joining SQL Server Tables
• Case 4: Write Capabilities
• Case 5: Data Dictionary Query
• Case 6: The Pass-Through Feature
• Case 7: Executing Stored Procedures
3.1 Case Descriptions

The cases illustrate:
• A simple query (Case 1)
• A more complex query (Case 2)
• Joining SQL Server tables (Case 3)
• Write capabilities (Case 4)
• A data dictionary query (Case 5)
• The pass-through feature (Case 6)
• Executing stored procedures (Case 7)
3.2 Installation Media Contents

The installation media contains the following:
• Demonstration files
3-1
Chapter 3
Demonstration Files
• One SQL script file that creates the demonstration tables and stored procedures in
the SQL Server database
• One SQL script file that drops the demonstration tables and stored procedures
from the SQL Server database
3.3 Demonstration Files

After a successful gateway installation, use the demonstration files stored in the
directory ORACLE_HOME\dg4msql\demo where ORACLE_HOME is the directory under which
the gateway is installed. The directory contains the following demonstration files:
• bldmsql.sql
• case1.sql
• case2.sql
• case3.sql
• case4a.sql
• case4b.sql
• case4c.sql
• case5.sql
• case6a.sql
• case6b.sql
• case7.sql
• dropmsql.sql
3.4 Demonstration Requirements

The case studies assume these requirements have been met:
• The gateway demonstration tables and stored procedures are installed in the SQL
Server database
• The Oracle database has an account named SCOTT with a password of TIGER
• The Oracle database has a database link called GTWLINK (set up as public or
private to the user SCOTT) which connects the gateway to a SQL Server database
as SCOTT with password TIGER2
For example, you can create the database link as follows:
SQL> CREATE DATABASE LINK GTWLINK CONNECT TO SCOTT
2 IDENTIFIED BY TIGER2 USING 'GTWSID';
• Oracle Net Services is configured correctly and running
3.5 Creating Demonstration Tables

The case studies are based on the GTW_EMP, GTW_DEPT, and GTW_SALGRADE tables and
the stored procedures InsertDept and GetDept. If the demonstration tables and stored
procedures have not been created in the SQL Server database, use the bldmsql.sql
script to create them. Enter the following:
3-2
Chapter 3
Creating Demonstration Tables
> isql -USCOTT -PTIGER2 -ibldmsql.sql
The script creates the demonstration tables and stored procedures in the SQL Server
database accordingly:
CREATE TABLE GTW_EMP (
EMPNO SMALLINT NOT NULL
ENAME VARCHAR(10),
JOB VARCHAR(9),
MGR SMALLINT,
HIREDATE DATETIME,
SAL NUMERIC(7,2),
COMM NUMERIC(7,2),
DEPTNO SMALLINT)
go
CREATE TABLE GTW_DEPT (

DEPTNO SMALLINT NOT NULL,
DNAME VARCHAR(14),
LOC VARCHAR(13))
go
CREATE TABLE GTW_SALGRADE (

GRADE MONEY,
LOSAL NUMERIC(9,4),
HISAL NUMERIC(9,4))
go
DROP PROCEDURE InsertDept

go
CREATE PROCEDURE InsertDept (@dno INTEGER,

@dname VARCHAR(14), @loc VARCHAR(13))
AS INSERT INTO GTW_DEPT VALUES (@dno, @dname, @loc)
go
DROP PROCEDURE GetDept

go
CREATE PROCEDURE GetDept (@dno INTEGER, @dname VARCHAR(14) OUTPUT)

AS SELECT @dname=DNAME FROM GTW_DEPT WHERE DEPTNO=@dno
go
3.5.1 Demonstration Table Definitions

The following table definitions use information retrieved by the SQL*PLUS DESCRIBE
command:
GTW_EMP
Name Null? Type
------------------------------- -------- ----
EMPNO NOT NULL NUMBER(5)
ENAME VARCHAR2(10)
JOB VARCHAR2(9)
MGR NUMBER(5)
HIREDATE DATE
SAL NUMBER(7,2)
COMM NUMBER(7,2)
DEPTNO NUMBER(5)
3-3
Chapter 3
Creating Demonstration Tables
GTW_DEPT
Name Null? Type
------------------------------- -------- ----
DEPTNO NOT NULL NUMBER(5)
DNAME VARCHAR2(14)
LOC VARCHAR2(13)
GTW_SALGRADE
Name Null? Type
------------------------------- -------- ----
GRADE NUMBER(19,4)
LOSAL NUMBER(9,4)
HISAL NUMBER(9,4)
3.5.2 Demonstration Table Contents

The contents of the SQL Server tables are:
GTW_EMP
EMPNO ENAME JOB MGR HIREDATE SAL COMM DEPTNO
----- ----- --- --- -------- --- ---- ------
7369 SMITH CLERK 7902 17-DEC-80 800 20
7499 ALLEN SALESMAN 7698 20-FEB-81 1600 300 30
7521 WARD SALESMAN 7698 22-FEB-81 1250 500 30
7566 JONES MANAGER 7839 02-APR-81 2975 20
7654 MARTIN SALESMAN 7698 28-SEP-81 1250 1400 30
7698 BLAKE MANAGER 7839 01-MAY-81 2850 30
7782 CLARK MANAGER 7839 09-JUN-81 2450 10
7788 SCOTT ANALYST 7566 09-DEC-82 3000 20
7839 KING PRESIDENT 17-NOV-81 5000 10
7844 TURNER SALESMAN 7698 08-SEP-81 1500 0 30
7876 ADAMS CLERK 7788 12-JAN-83 1100 20
7900 JAMES CLERK 7698 03-DEC-81 950 30
7902 FORD ANALYST 7566 03-DEC-81 3000 20
7934 MILLER CLERK 7782 23-JAN-82 1300 10
GTW_DEPT
DEPTNO DNAME LOC
----- -------------- --------
10 ACCOUNTING NEW YORK
20 RESEARCH DALLAS
30 SALES CHICAGO
40 OPERATIONS BOSTON
GTW_SALGRADE
GRADE LOSAL HISAL
------ ------ -----
1 700 1200
2 1201 1400
3 1401 2000
4 2001 3000
5 3001 9999
3-4
Chapter 3
Case 1: Simple Queries
3.6 Case 1: Simple Queries

Case 1 demonstrates the following:
• A simple query
• A simple query retrieving full date information
The first query retrieves all the data from GTW_DEPT and confirms that the gateway is
working correctly. The second query retrieves all the data from GTW_EMP including the
time portion of the hire date because the default date format was set to DD-MON-YY
HH24:MM:SS for the session by an ALTER SESSION command.
3.7 Case 2: A More Complex Query

• The functions SUM(expression) and NVL(expr1, expr2) in the SELECT list
• The GROUP BY and HAVING clauses
This query retrieves the departments from GTW_EMP whose total monthly expenses are
higher than $10,000.
3.8 Case 3: Joining SQL Server Tables

• Joins between SQL Server tables
• Subselects
The query retrieves information from three SQL Server tables and relates the
employees to their department name and salary grade, but only for those employees
earning more than the average salary.
3.9 Case 4: Write Capabilities

Case 4 is split into three cases and demonstrates the following:
• DELETE Statement
• UPDATE Statement
• INSERT Statement
3.9.1 DELETE Statement

Case 4a demonstrates bind values and subselect. All employees in department 20 and
one employee, WARD, in department 30 are deleted.
3.9.2 UPDATE Statement

Case 4b provides an example of a simple UPDATE statement. In this example,
employees are given a $100 a month salary increase.
3-5
Chapter 3
Case 5: Data Dictionary Query
3.9.3 INSERT Statement

Case 4c is an example of a simple insert statement that does not provide information
for all columns.
3.10 Case 5: Data Dictionary Query

Case 5 demonstrates data dictionary mapping. It retrieves all the tables and views that
exist in the SQL Server database that begin with GTW.
3.11 Case 6: The Pass-Through Feature

Case 6 demonstrates the gateway pass-through feature which allows an application to
send commands or statements to SQL Server.
This case demonstrates:
• A pass-through UPDATE statement using bind variables
• A pass-through SELECT statement
3.11.1 UPDATE Statement

Case 6a provides an example of a pass-through UPDATE statement with bind variables.
In this example, the salary for EMPNO 7934 is set to 4000.
3.11.2 SELECT Statement

Case 6b provides an example of a pass-through SELECT statement. The data that
is returned from the SELECT statement is inserted into a local table at the Oracle
database.
3.12 Case 7: Executing Stored Procedures

Case 7 demonstrates the gateway executing a stored procedure in the SQL Server
database.
3-6
A
Data Type Conversion
The gateway converts SQL Server data types to Oracle data types as follows:
Table A-1 Data Type Mapping and Restrictions
SQL Server Oracle Comment If Oracle uses large varchar

(32k)
BIGINT NUMBER(20)
BIGINT IDENTITY NUMBER(20)
BINARY RAW -
BIT NUMBER(3) -
CHAR CHAR -
DATETIME DATE Fractional parts of a second are
truncated
DECIMAL NUMBER(p[,s]) -
DECIMAL IDENTITY NUMBER(p[,s])
FLOAT FLOAT(53) -
IMAGE LONG RAW -
INT NUMBER(10)
INT IDENTITY NUMBER(10)
MONEY NUMBER(19,4) -
NCHAR NCHAR if the size is 1000 or less. If
the size is more than 1000,
then it will be mapped to LONG
Oracle Database Character Set
= Unicode, otherwise, it is not
supported.
NTEXT LONG if Oracle DB Character Set =
Unicode. Otherwise, it is not
supported
NVARCHAR NVARCHAR -
NVARCHAR(MAX) LONG 4000 < N 32767 < N
if Oracle DB Character Set =
Unicode. Otherwise, it is not
supported.
NUMERIC NUMBER(p[,s]) -
NUMERIC IDENTITY NUMBER(p[,s])
REAL FLOAT(24) -
SMALLDATETIME DATE -
SMALLMONEY NUMBER(10,4) -
A-1
Appendix A
Table A-1 (Cont.) Data Type Mapping and Restrictions
SQL Server Oracle Comment If Oracle uses large varchar

(32k)
SMALLINT NUMBER(5) -
SMALLINT IDENTITY NUMBER(5)
SYSNAME NVARCHAR -
TEXT LONG
TIMESTAMP RAW -
TINYINT NUMBER(3) -
TINYINT IDENTITY NUMBER(3)
VARBINARY RAW 1 N 2000 1 <= N <= 32767
VARBINARY(MAX) LONG RAW 2000 < N N < 32767
VARCHAR VARCHAR2 N 4000 N <= 32767
VARCHAR(MAX) LONG 4000 < N 32767 < N
XML LONG if Oracle Database Character Set
= Unicode. Otherwise, it is not
supported.
A-2
B
Supported SQL Syntax and Functions
The following topics describe supported SQL Syntax and Functions:
• Supported SQL Statements
• Oracle Functions
B.1 Supported SQL Statements

With a few exceptions, the gateway provides full support for Oracle DELETE, INSERT,
SELECT, and UPDATE statements.
The gateway does not support Oracle data definition language (DDL) statements.
No form of the Oracle ALTER, CREATE, DROP, GRANT, or TRUNCATE statements can be
used. Instead, use the pass-through feature of the gateway if you need to use DDL
statements against the SQL Server database.
Note:
TRUNCATE cannot be used in a pass-through statement.
See Also:
Oracle Database Reference for detailed descriptions of keywords,
parameters, and options.
B.1.1 DELETE
The DELETE statement is fully supported. However, only Oracle functions supported by
SQL Server can be used.
See Also:
"Functions Supported by SQL Server" for a list of supported functions.
B.1.2 INSERT
The INSERT statement is fully supported. However, only Oracle functions supported by
B-1
Appendix B
Oracle Functions
See Also:
B.1.3 SELECT
The SELECT statement is fully supported, with these exceptions:
• CONNECT BY condition
• NOWAIT
• START WITH condition
• WHERE CURRENT OF
B.1.4 UPDATE
The UPDATE statement is fully supported. However, only Oracle functions supported by
See Also:
B.2 Oracle Functions

All functions are evaluated by the SQL Server database after the gateway has
converted them to SQL Server SQL equivalents. The exception is the TO_DATE
function, which is evaluated by the gateway.
B.2.1 Functions Not Supported by SQL Server

Oracle SQL functions with no equivalent function in SQL Server are not supported
in DELETE, INSERT, or UPDATE statements, but are evaluated by the Oracle database
if the statement is a SELECT statement. That is, the Oracle database performs post-
processing of SELECT statements sent to the gateway.
If an unsupported function is used in a DELETE, INSERT, or UPDATE, statement, the

following Oracle error occurs:
ORA-02070: database db_link_name does not support function in this context
B.2.2 Functions Supported by SQL Server

The gateway translates the following Oracle database functions in SQL statements to
their equivalent SQL Server functions:
• Arithmetic Operators
B-2
Appendix B
Oracle Functions
• Comparison Operators
• Pattern Matching
• Group Functions
• String Functions
• Other Functions
B.2.2.1 Arithmetic Operators
Oracle SQL Server

+ +
- -
* *
/ /
B.2.2.2 Comparison Operators
Oracle SQL Server

= =
> >
< <
>= >=
<= <=
<>, !=, ^= <>
IS NOT NULL IS NOT NULL
IS NULL IS NULL
B.2.2.3 Pattern Matching
Oracle SQL Server

LIKE LIKE
NOT LIKE NOT LIKE
B.2.2.4 Group Functions
Oracle SQL Server

AVG AVG
COUNT COUNT
MAX MAX
MIN MIN
SUM SUM
B-3
Appendix B
Oracle Functions
B.2.2.5 String Functions
Oracle SQL Server

||, CONCAT + (expression1 + expression2)
ASCII ASCII
CHR CHAR
INSTR (with two arguments) CHARINDEX
LENGTH () LEN ()
LENGTHB () DATALENGTH ()
LENGTHC () LEN ()
LOWER LOWER
LTRIM LTRIM
RTRIM RTRIM
SUBSTR (second argument cannot be a SUBSTRING
negative number)
UPPER UPPER
B.2.2.6 Other Functions
Oracle SQL Server

ABS ABS
CEIL CEILING
COS COS
EXP EXP
FLOOR FLOOR
LN LOG
LOG LOG10
MOD %
NOT NVL IS NOT NULL
NVL IS NULL
POWER POWER
ROUND ROUND
SIN SIN
SQRT SQRT
TAN TAN
B.2.3 Functions Supported by the Gateway

If an Oracle function has no equivalent function in SQL Server, the Oracle function
is not translated into the SQL statement and must be post-processed if the SQL
statement is a SELECT.
B-4
Appendix B
Oracle Functions
The gateway, however, does support the TO_DATE function equivalent in SQL Server,
as follows:
TO_DATE(date_string | date_column)
where:
• date_string is converted to a string with the following format:
yyyy-mm-dd hh:mi:ss.fff
Note:
Supply the date string with the same format as the result (that is, yyyyy-
mm-dd hh:mi:ss.fff).
• date_column is a column with a date data type. It is converted to a parameter with

a timestamp data type.
B-5
C
Data Dictionary
The Oracle Database Gateway for SQL Server translates a query that refers to an
Oracle database data dictionary table into a query that retrieves the data from SQL
Server system tables. You perform queries on data dictionary tables over the database
link in the same way you query data dictionary tables in the Oracle database.
The gateway data dictionary is similar to the Oracle database data dictionary in
appearance and use.
Topics:
• Data Dictionary Support
• Data Dictionary Mapping
• Gateway Data Dictionary Descriptions
C.1 Data Dictionary Support

The following paragraphs describe the Oracle Database Gateway for SQL Server data
dictionary support.
C.1.1 SQL Server System Tables

SQL Server data dictionary information is stored in the SQL Server database as SQL
Server system tables. All SQL Server system tables have names prefixed with "sys".
The SQL Server system tables define the structure of a database. When you change
data definitions, SQL Server reads and modifies the SQL Server system tables to add
information about the user tables.
C.1.2 Accessing the Gateway Data Dictionary

Accessing a gateway data dictionary table or view is identical to accessing a data
dictionary in an Oracle database. You issue a SQL SELECT statement specifying a
database link. The Oracle database data dictionary view and column names are used
to access the gateway data dictionary in an Oracle database. Synonyms of supported
views are also acceptable. For example, the following statement queries the data
dictionary table ALL_CATALOG to retrieve all table names in the SQL Server database:
SQL> SELECT * FROM "ALL_CATALOG"@MSQL;
When a data dictionary access query is issued, the gateway:

1. Maps the requested table, view, or synonym to one or more SQL Server system
table names. The gateway translates all data dictionary column names to their
corresponding SQL Server column names within the query. If the mapping
involves one SQL Server system table, the gateway translates the requested table
name to its corresponding SQL Server system table name within the query. If the
mapping involves multiple SQL Server system tables, the gateway constructs a
join in the query using the translated SQL Server system table names.
C-1
Appendix C
Data Dictionary Support
2. Sends the translated query to SQL Server.

3. Might convert the retrieved SQL Server data to give it the appearance of the
Oracle database data dictionary table.
4. Passes the data dictionary information from the translated SQL Server system
table to the Oracle database.
Note:
The values returned when querying the gateway data dictionary might
not be the same as the ones returned by the Oracle SQL*Plus DESCRIBE
command.
C.1.3 Direct Queries to SQL Server Tables

Queries issued directly to individual SQL Server system tables are allowed but they
return different results because the SQL Server system table column names differ from
those of the data dictionary view. Also, certain columns in an SQL Server system table
cannot be used in data dictionary processing.
C.1.4 Supported Views and Tables

The gateway supports the following views and tables:
ALL_CATALOG ALL_COL_COMMENTS
ALL_CONS_COLUMNS ALL_CONSTRAINTS
ALL_IND_COLUMNS ALL_INDEXES
ALL_OBJECTS ALL_TAB_COLUMNS
ALL_TAB_COMMENTS ALL_TABLES
ALL_USERS ALL_VIEWS
DBA_CATALOG DBA_COL_COMMENTS
DBA_OBJECTS DBA_TAB_COLUMNS
DBA_TAB_COMMENTS DBA_TABLES
DICT_COLUMNS DICTIONARY
DUAL TABLE_PRIVILEGES
C-2
Appendix C
Data Dictionary Mapping
USER_CATALOG USER_COL_COMMENTS
USER_CONS_COLUMNS USER_CONSTRAINTS
USER_IND_COLUMNS USER_INDEXES
USER_OBJECTS USER_TAB_COLUMNS
USER_TAB_COMMENTS USER_TABLES
USER_USERS USER_VIEWS
No other Oracle database data dictionary tables or views are supported. If you use a
view not on the list, you will receive the Oracle database error code for no more rows
available.
Queries through the gateway of any data dictionary table or view beginning with ALL_
can return rows from the SQL Server database even when access privileges for those
SQL Server objects have not been granted. When querying an Oracle database with
the Oracle data dictionary, rows are returned only for those objects you are permitted
to access.
C.2 Data Dictionary Mapping

The tables in this section list Oracle data dictionary view names and the equivalent
SQL Server system tables used. A plus sign (+) indicates that a join operation is
involved.
Table C-1 Oracle Data Dictionary View Names and SQL Server Equivalents
View Name SQL Server System Table Name

ALL_CATALOG sysusers + sysobjects
ALL_COL_COMMENTS sysusers + sysobjects + syscolumns
ALL_CONS_COLUMNS sp_pkeys + sp_fkeys
ALL_CONSTRAINTS sysusers + sysobjects + sysindexes +
sysconstraints + sysreferences
ALL_IND_COLUMNS sysusers + sysindexes + syscolumns
ALL_INDEXES sysusers + sysindexes + sysobjects
ALL_OBJECTS sysusers + sysobjects + sysindexes
ALL_TAB_COLUMNS sysusers + sysobjects + syscolumns
ALL_TAB_COMMENTS sysusers + sysobjects
ALL_TABLES sysusers + sysobjects
ALL_USERS sysusers
ALL_VIEWS sysusers + sysobjects + syscomments
DBA_CATALOG sysusers + sysobjects
C-3
Appendix C
Gateway Data Dictionary Descriptions
Table C-1 (Cont.) Oracle Data Dictionary View Names and SQL Server
Equivalents
View Name SQL Server System Table Name

DBA_COL_COMMENTS sysusers + sysobjects + syscolumns
DBA_OBJECTS sysusers + sysobjects + sysindexes
DBA_TABLES sysusers + sysobjects
DBA_TAB_COLUMNS sysusers + sysobjects + syscolumns
DBA_TAB_COMMENTS sysusers + sysobjects
DICT_COLUMNS sysobjects + syscolumns
DICTIONARY sysobjects
DUAL sysusers
TABLE_PRIVILEGES sysprotects + sysusers + sysobjects
USER_CATALOG sysusers + sysobjects
USER_COL_COMMENTS sysusers + sysobjects + syscolumns
USER_CONS_COLUMNS sp_pkeys + sp_fkeys
USER_CONSTRAINTS sysusers + sysobjects + sysindexes +
sysconstraints + sysreferences
USER_IND_COLUMNS sysusers + sysindexes + syscolumns
USER_INDEXES sysusers + sysindexes + sysobjects
USER_OBJECTS sysusers + sysobjects + sysindexes
USER_TAB_COLUMNS sysusers + sysobjects + syscolumns
USER_TAB_COMMENTS sysusers + sysobjects
USER_TABLES sysusers + sysobjects
USER_USERS sysusers
USER_VIEWS sysusers + sysobjects + syscomments
C.2.1 Default Column Values

There is a minor difference between the gateway data dictionary and a typical Oracle
database data dictionary. The Oracle database columns that are missing in an SQL
Server system table are filled with zeros, spaces, null values, not-applicable values
(N.A.), or default values, depending on the column type.
C.3 Gateway Data Dictionary Descriptions

The gateway data dictionary tables and views provide the following information:
• Name, data type, and width of each column
• The contents of columns with fixed values
They are described here with information retrieved by an Oracle SQL*Plus DESCRIBE
command. The values in the Null? column might differ from the Oracle database data
C-4
Appendix C
ALL_CATALOG
dictionary tables and views. Any default value is shown to the right of an item, but this
is not information returned by DESCRIBE.
Note:
The column width of some columns in the translated data dictionary tables
would be different when the gateway connects to a SQL Server Version 7.0
database.
C.4 ALL_CATALOG
Table C-2 ALL_CATALOG
Name Type Value

OWNER VARCHAR2(256) -
TABLE_NAME VARCHAR2(256) -
TABLE_TYPE VARCHAR2(5) "TABLE" or "VIEW"
C.5 ALL_COL_COMMENTS
Table C-3 ALL_COL_COMMENTS
Name Type Value

COLUMN_NAME VARCHAR2(256) -
COMMENTS VARCHAR2(1) -
C.6 ALL_CONS_COLUMNS
Table C-4 ALL_CONS_COLUMNS
Name Type Value

CONSTRAINT_NAME VARCHAR2(256) -
POSITION NUMBER(5) -
C-5
Appendix C
ALL_CONSTRAINTS
C.7 ALL_CONSTRAINTS
Table C-5 ALL_CONSTRAINTS
Name Type Value

CONSTRAINT_TYPE VARCHAR2(1) "C" or "P" or "R" or
" U"
SEARCH_CONDITION VARCHAR2(1) NULL
R_OWNER VARCHAR2(256) -
R_CONSTRAINT_NAME VARCHAR2(256) -
DELETE_RULE VARCHAR2(1) NULL
STATUS VARCHAR2(1) NULL
DEFERRABLE VARCHAR2(1) NULL
DEFERRED VARCHAR2(1) NULL
VALIDATED VARCHAR2(1) NULL
GENERATED VARCHAR2(1) NULL
BAD VARCHAR2(1) NULL
RELY VARCHAR2(1) NULL
LAST_CHANGE DATE -
C.8 ALL_IND_COLUMNS
Table C-6 ALL_IND_COLUMNS
Name Type Value

INDEX_OWNER VARCHAR2(256) -
INDEX_NAME VARCHAR2(256) -
TABLE_OWNER VARCHAR2(256) -
COLUMN_POSITION NUMBER(3) -
COLUMN_LENGTH NUMBER -
Char_LENGTH NUMBER -
DESCEND VARCHAR2(4) -
C-6
Appendix C
ALL_INDEXES
C.9 ALL_INDEXES
Table C-7 ALL_INDEXES
Name Type Value

INDEX_TYPE VARCHAR2(1) NULL
TABLE_TYPE VARCHAR(7) "TABLE" or
"CLUSTER"
UNIQUENESS VARCHAR2(1) NULL
COMPRESSION VARCHAR2(1) NULL
PREFIX_LENGTH NUMBER 0
TABLESPACE_NAME VARCHAR2(1) NULL
INI_TRANS NUMBER 0
MAX_TRANS NUMBER 0
INITIAL_EXTENT NUMBER 0
NEXT_EXTENT NUMBER 0
MIN_EXTENTS NUMBER 0
MAX_EXTENTS NUMBER 0
PCT_INCREASE NUMBER 0
PCT_THRESHOLD NUMBER 0
INCLUDE_COLUMN NUMBER 0
FREELISTS NUMBER 0
FREELIST_GROUPS NUMBER 0
PCT_FREE NUMBER 0
LOGGING VARCHAR2(1) NULL
BLEVEL NUMBER 0
LEAF_BLOCKS NUMBER 0
DISTINCT_KEYS NUMBER 0
AVG_LEAF_BLOCKS_PER_KEY NUMBER 0
AVG_DATA_BLOCKS_PER_KEY NUMBER 0
CLUSTERING_FACTOR NUMBER 0
NUM_ROWS NUMBER 0
SAMPLE_SIZE NUMBER 0
LAST_ANALYZED DATE NULL
DEGREE VARCHAR2(1) NULL
C-7
Appendix C
ALL_OBJECTS
Table C-7 (Cont.) ALL_INDEXES
Name Type Value

INSTANCES VARCHAR2(1) NULL
PARTITIONED VARCHAR2(1) NULL
TEMPORARY VARCHAR2(1) NULL
SECONDARY VARCHAR2(1) NULL
BUFFER_POOL VARCHAR2(1) NULL
USER_STATS VARCHAR2(1) NULL
DURATION VARCHAR2(1) NULL
PCT_DIRECT_ACCESS NUMBER 0
ITYP_OWNER VARCHAR2(1) NULL
ITYP_NAME VARCHAR2(1) NULL
PARAMETERS VARCHAR2(1) NULL
GLOBAL_STATS VARCHAR2(1) NULL
DOMIDX_STATUS VARCHAR2(1) NULL
DOMIDX_OPSTATUS VARCHAR2(1) NULL
FUNCIDX_STATUS VARCHAR2(1) NULL
C.10 ALL_OBJECTS
Table C-8 ALL_OBJECTS
Name Type Value

OBJECT_NAME VARCHAR2(256) -
SUBOBJECT_NAME VARCHAR2(1) NULL
OBJECT_ID NUMBER -
DATA_OBJECT_ID NUMBER 0
OBJECT_TYPE VARCHAR2(9) "TABLE" or "VIEW"
or "INDEX" or
"PROCEDURE"
CREATED DATE -
LAST_DDL_TIME DATE -
TIMESTAMP VARCHAR2(1) NULL
STATUS VARCHAR2(5) "VALID"
C-8
Appendix C
ALL_TAB_COLUMNS
C.11 ALL_TAB_COLUMNS
Table C-9 ALL_TAB_COLUMNS
Name Type Value

DATA_TYPE VARCHAR2(9) -
DATA_TYPE_MOD VARCHAR2(1) NULL
DATA_TYPE_OWNER VARCHAR2(1) NULL
DATA_LENGTH NUMBER -
DATA_PRECISION NUMBER -
DATA_SCALE NUMBER -
NULLABLE VARCHAR2(1) "Y" or "N"
COLUMN_ID NUMBER(5) -
DEFAULT_LENGTH NUMBER 0
DATA_DEFAULT VARCHAR2(1) NULL
NUM_DISTINCT NUMBER 0
LOW_VALUE NUMBER 0
HIGH_VALUE NUMBER 0
DENSITY NUMBER 0
NUM_NULLS NUMBER 0
NUM_BUCKETS NUMBER 0
CHARACTER_SET_NAME VARCHAR2(1) NULL
CHAR_COL_DEC_LENGTH NUMBER 0
AVG_COL_LEN NUMBER 0
CHAR_LENGTH NUMBER
CHAR_USED VARCHAR2(1)
V80_FMT_IMAGE VARCHAR2(1)
DATA_UPGRADED VARCHAR2(1)
HISTOGRAM VARCHAR2(1)
C-9
Appendix C
ALL_TAB_COMMENTS
C.12 ALL_TAB_COMMENTS
Table C-10 ALL_TAB_COMMENTS
Name Type Value

COMMENTS VARCHAR2(1) NULL
C.13 ALL_TABLES
Table C-11 ALL_TABLES
Name Type Value

CLUSTER_NAME VARCHAR2(1) NULL
IOT_NAME VARCHAR2(1) NULL
PCT_FREE NUMBER 0
PCT_USED NUMBER 0
INI_TRANS NUMBER 0
MAX_TRANS NUMBER 0
FREELISTS NUMBER 0
BACKED_UP VARCHAR2(1) NULL
NUM_ROWS NUMBER 0
BLOCKS NUMBER 0
EMPTY_BLOCKS NUMBER 0
AVG_SPACE NUMBER 0
CHAIN_CNT NUMBER 0
AVG_ROW_LEN NUMBER 0
C-10
Appendix C
ALL_USERS
Table C-11 (Cont.) ALL_TABLES
Name Type Value

AVG_SPACE_FREELIST_BLOCKS NUMBER 0
NUM_FREELIST_BLOCKS NUMBER 0
CACHE VARCHAR2(1) NULL
TABLE_LOCK VARCHAR2(1) NULL
IOT_TYPE VARCHAR2(1) NULL
TEMPORARY VARHCAR2(1) NULL
NESTED VARCHAR2(1) NULL
ROW_MOVEMENT VARCHAR2(1) NULL
DURATION VARHCAR2(1) NULL
SKIP_CORRUPT VARCHAR2(1) NULL
MONITORING VARCHAR2(1) NULL
C.14 ALL_USERS
Table C-12 ALL_USERS
Name Type Value

USERNAME VARCHAR2(256) -
USER_ID NUMBER(10) -
CREATED DATE -
C.15 ALL_VIEWS
Table C-13 ALL_VIEWS
Name Type Value

VIEW_NAME VARCHAR2(256) -
C-11
Appendix C
DBA_CATALOG
Table C-13 (Cont.) ALL_VIEWS
Name Type Value

TEXT_LENGTH NUMBER 0
TEXT VARCHAR2(1) -
TYPE_TEXT_LENGTH NUMBER 0
TYPE_TEXT VARCHAR2(1) -
OID_TEXT_LENGTH NUMBER 0
OID_TEXT VARCHAR2(1) -
VIEW_TYPE_OWNER VARCHAR2(1) -
VIEW_TYPE VARCHAR2(1) -
C.16 DBA_CATALOG
Table C-14 DBA_CATALOG
Name Type Value

C.17 DBA_COL_COMMENTS
Table C-15 DBA_COL_COMMENTS
Name Type Value

C.18 DBA_OBJECTS
Table C-16 DBA_OBJECTS
Name Type Value

OBJECT_ID NUMBER -
C-12
Appendix C
DBA_TAB_COLUMNS
Table C-16 (Cont.) DBA_OBJECTS
Name Type Value

or "INDEX" or
"PROCEDURE"
CREATED DATE -
C.19 DBA_TAB_COLUMNS
Table C-17 DBA_TAB_COLUMNS
Name Type Value

DATA_SCALE NUMBER -
LOW_VALUE NUMBER 0
HIGH_VALUE NUMBER 0
DENSITY NUMBER 0
NUM_NULLS NUMBER 0
C-13
Appendix C
DBA_TAB_COMMENTS
Table C-17 (Cont.) DBA_TAB_COLUMNS
Name Type Value

CHAR_COL_DEC_LENGTH NUMBER 0
C.20 DBA_TAB_COMMENTS
Table C-18 DBA_TAB_COMMENTS
Name Type Value

C.21 DBA_TABLES
Table C-19 DBA_TABLES
Name Type Value

PCT_FREE NUMBER 0
PCT_USED NUMBER 0
INI_TRANS NUMBER 0
MAX_TRANS NUMBER 0
FREELISTS NUMBER 0
C-14
Appendix C
DICT_COLUMNS
Table C-19 (Cont.) DBA_TABLES
Name Type Value

NUM_ROWS NUMBER 0
BLOCKS NUMBER 0
AVG_SPACE NUMBER 0
CHAIN_CNT NUMBER 0
C.22 DICT_COLUMNS
Table C-20 DICT_COLUMNS
Name Type Value

C-15
Appendix C
DICTIONARY
Table C-20 (Cont.) DICT_COLUMNS
Name Type Value

C.23 DICTIONARY
Table C-21 DICTIONARY
Name Type Value

COMMENTS VARCHAR2(1) -
C.24 DUAL
Table C-22 DUAL
Name Type Value

DUMMY VARCHAR2(1) "X"
C.25 TABLE_PRIVILEGES
Table C-23 TABLE_PRIVILEGES
Name Type Value

GRANTEE VARCHAR2(256) -
GRANTOR VARCHAR2(256) -
SELECT_PRIV VARCHAR2(1) "Y"
INSERT_PRIV VARCHAR2(1) "A"
DELETE_PRIV VARCHAR2(1) "Y"
UPDATE_PRIV VARCHAR2(1) "A"
REFERENCES_PRIV VARCHAR2(1) "A"
ALTER_PRIV VARCHAR2(1) "Y"
INDEX_PRIV VARCHAR2(1) "Y"
CREATED DATE -
C-16
Appendix C
USER_CATALOG
C.26 USER_CATALOG
Table C-24 USER_CATALOG
Name Type Value

C.27 USER_COL_COMMENTS
Table C-25 USER_COL_COMMENTS
Name Type Value

C.28 USER_CONS_COLUMNS
Table C-26 USER_CONS_COLUMNS
Name Type Value

POSITION NUMBER(5) -
C.29 USER_CONSTRAINTS
Table C-27 USER_CONSTRAINTS
Name Type Value

CONSTRAINT_TYPE VARCHAR2(1) "R" or "P" or "U" or
" C"
SEARCH_CONDITION VARCHAR2(1) NULL
R_OWNER VARCHAR2(256) -
C-17
Appendix C
USER_IND_COLUMNS
Table C-27 (Cont.) USER_CONSTRAINTS
Name Type Value

R_CONSTRAINT_NAME VARCHAR2(256) -
DELETE_RULE VARCHAR2(1) NULL
DEFERRABLE VARCHAR2(1) NULL
DEFERRED VARCHAR2(1) NULL
VALIDATED VARCHAR2(1) NULL
BAD VARCHAR2(1) NULL
RELY VARCHAR2(1) NULL
LAST_CHANGE DATE -
C.30 USER_IND_COLUMNS
Table C-28 USER_IND_COLUMNS
Name Type Value

COLUMN_POSITION NUMBER(3) -
COLUMN_LENGTH NUMBER -
CHAR_LENGTH NUMBER -
DESCEND VARCHAR2(4) -
C.31 USER_INDEXES
Table C-29 USER_INDEXES
Name Type Value

INDEX_TYPE VARCHAR2(1) NULL
TABLE_TYPE VARCHAR2(7) "TABLE" or
"CLUSTER"
UNIQUENESS VARCHAR2(1) NULL
COMPRESSION VARCHAR2(1) NULL
C-18
Appendix C
USER_INDEXES
Table C-29 (Cont.) USER_INDEXES
Name Type Value

PREFIX_LENGTH NUMBER 0
INI_TRANS NUMBER 0
MAX_TRANS NUMBER 0
PCT_THRESHOLD NUMBER 0
INCLUDE_COLUMN NUMBER 0
FREELISTS NUMBER 0
PCT_FREE NUMBER 0
BLEVEL NUMBER 0
LEAF_BLOCKS NUMBER 0
DISTINCT_KEYS NUMBER 0
AVG_LEAF_BLOCKS_PER_KEY NUMBER 0
AVG_DATA_BLOCKS_PER_KEY NUMBER 0
CLUSTERING_FACTOR NUMBER 0
NUM_ROWS NUMBER 0
PCT_DIRECT_ACCESS NUMBER 0
ITYP_OWNER VARCHAR2(1) NULL
ITYP_NAME VARCHAR2(1) NULL
C-19
Appendix C
USER_OBJECTS
Table C-29 (Cont.) USER_INDEXES
Name Type Value

PARAMETERS VARCHAR2(1) NULL
DOMIDX_STATUS VARCHAR2(1) NULL
DOMIDX_OPSTATUS VARCHAR2(1) NULL
FUNCIDX_STATUS VARCHAR2(1) NULL
C.32 USER_OBJECTS
Table C-30 USER_OBJECTS
Name Type Value

OBJECT_ID NUMBER -
or "INDEX" or
"PROCEDURE"
CREATED DATE -
STATUS VARCHAR2(5) "VALID"
C.33 USER_TAB_COLUMNS
Table C-31 USER_TAB_COLUMNS
Name Type Value

C-20
Appendix C
USER_TAB_COMMENTS
Table C-31 (Cont.) USER_TAB_COLUMNS
Name Type Value

DATA_SCALE NUMBER -
LOW_VALUE NUMBER 0
HIGH_VALUE NUMBER 0
DENSITY NUMBER 0
NUM_NULLS NUMBER 0
CHAR_COL_DECL_LENGTH NUMBER 0
CHAR_LENGTH NUMBER 0
CHAR_USED VARCHAR2(1)
V80_FMT_IMAGE VARCHAR2(1)
DATA_UPGRADED VARCHAR2(1)
HISTOGRAM VARCHAR2(1)
C.34 USER_TAB_COMMENTS
Table C-32 USER_TAB_COMMENTS
Name Type Value

C-21
Appendix C
USER_TABLES
C.35 USER_TABLES
Table C-33 USER_TABLES
Name Type Value

PCT_FREE NUMBER 0
PCT_USED NUMBER 0
INI_TRANS NUMBER 0
MAX_TRANS NUMBER 0
FREELISTS NUMBER 0
NUM_ROWS NUMBER 0
BLOCKS NUMBER 0
AVG_SPACE NUMBER 0
CHAIN_CNT NUMBER 0
C-22
Appendix C
USER_USERS
Table C-33 (Cont.) USER_TABLES
Name Type Value

DURATION VARCHAR2(1) NULL
C.36 USER_USERS
Table C-34 USER_USERS
Name Type Value

USERNAME VARCHAR2(256) -
USER_ID NUMBER(5) -
ACCOUNT_STATUS VARCHAR2(4) "OPEN"
LOCK_DATE DATE NULL
EXPIRY_DATE DATE NULL
DEFAULT_TABLESPACE VARCHAR2(1) NULL
TEMPORARY_TABLESPACE VARCHAR2(1) NULL
CREATED DATE -
INITIAL_RSRC_CONSUMER_GROUP VARCHAR2(1) NULL
EXTERNAL_NAME VARCHAR2(1) NULL
C.37 USER_VIEWS
Table C-35 USER_VIEWS
Name Type Value

VIEW_NAME VARCHAR2(256) -
TEXT_LENGTH NUMBER 0
TEXT VARCHAR2(1) -
TYPE_TEXT_LENGTH NUMBER 0
TYPE_TEXT VARCHAR2(1) NULL
OID_TEXT_LENGTH NUMBER 0
C-23
Appendix C
USER_VIEWS
Table C-35 (Cont.) USER_VIEWS
Name Type Value

OID_TEXT VARCHAR2(1) NULL
VIEW_TYPE_OWNER VARCHAR2(1) NULL
VIEW_TYPE VARCHAR2(1) NULL
C-24
D
Initialization Parameters
The Oracle database initialization parameters in the init.ora file are distinct from
gateway initialization parameters. Set the gateway parameters in the initialization
parameter file using an agent-specific mechanism, or set them in the Oracle data
dictionary using the DBMS_HS package. The gateway initialization parameter file must
be available when the gateway is started.
The following topics contain a list of the gateway initialization parameters that can be
set for each gateway and their description. The topics also describe the initialization
parameter file syntax.
• Initialization Parameter File Syntax
• Oracle Database Gateway for SQL Server Initialization Parameters
D.1 Initialization Parameter File Syntax

The syntax for the initialization parameter file is as follows:
• The file is a sequence of commands.
• Each command should start on a separate line.
• End of line is considered a command terminator (unless escaped with a
backslash).
• If there is a syntax error in an initialization parameter file, none of the settings take
effect.
• Set the parameter values as follows:
[SET][PRIVATE] parameter=value
where:
parameter is an initialization parameter name. It is a string of characters starting
with a letter and consisting of letters, digits and underscores. Initialization
parameter names are case sensitive.
value is the initialization parameter value. It is case sensitive. An initialization
parameter value is either:
– A string of characters that does not contain any backslashes, white space or
double quotation marks (")
– A quoted string beginning with a double quotation mark and ending with a
double quotation mark. The following can be used inside a quoted string:
* backslash (\) is the escape character
* \n inserts a new line
* \t inserts a tab
* \" inserts a double quotation mark
D-1
Appendix D
Oracle Database Gateway for SQL Server Initialization Parameters
* \\ inserts a backslash
A backslash at the end of the line continues the string on the next line. If a
backslash precedes any other character then the backslash is ignored.
For example, to enable tracing for an agent, set the HS_FDS_TRACE_LEVEL
initialization parameter as follows:
HS_FDS_TRACE_LEVEL=ON
SET and PRIVATE are optional keywords. You cannot use either as an initialization
parameter name. Most parameters are needed only as initialization parameters, so
you usually do not need to use the SET or PRIVATE keywords. If you do not specify
either SET or PRIVATE, the parameter is used only as an initialization parameter for
the agent.
SET specifies that, in addition to being used as an initialization parameter, the
parameter value is set as an environment variable for the agent process. Use SET
for parameter values that the drivers or non-Oracle system need as environment
variables.
PRIVATE specifies that the initialization parameter should be private to the agent
and should not be uploaded to the Oracle database. Most initialization parameters
should not be private. If, however, you are storing sensitive information like a
password in the initialization parameter file, then you may not want it uploaded
to the server because the initialization parameters and values are not encrypted
when uploaded. Making the initialization parameters private prevents the upload
from happening and they do not appear in dynamic performance views. Use
PRIVATE for the initialization parameters only if the parameter value includes
sensitive information such as a user name or password.
SET PRIVATE specifies that the parameter value is set as an environment variable
for the agent process and is also private (not transferred to the Oracle database,
not appearing in dynamic performance views or graphical user interfaces).
D.2 Oracle Database Gateway for SQL Server Initialization

Parameters
The initialization file parameters that can be set for the Oracle Database Gateway for
SQL Server are as follows:
• HS_CALL_NAME
• HS_DB_DOMAIN
• HS_DB_INTERNAL_NAME
• HS_DB_NAME
• HS_DESCRIBE_CACHE_HWM
• HS_LANGUAGE
• HS_LONG_PIECE_TRANSFER_SIZE
• HS_OPEN_CURSORS
• HS_RPC_FETCH_REBLOCKING
• HS_RPC_FETCH_SIZE
D-2
Appendix D
HS_CALL_NAME
• HS_TIME_ZONE
• HS_FDS_TRANSACTION_ISOLATION
• HS_FDS_ENCRYPT_SESSION
• HS_FDS_VALIDATE_SERVER_CERT
• HS_FDS_TRUSTSTORE_FILE
• HS_FDS_TRUSTSTORE_PASSWORD
• HS_TRANSACTION_MODEL
• IFILE
• HS_FDS_TIMESTAMP_MAPPING
• HS_FDS_DATE_MAPPING
• HS_FDS_CONNECT_INFO
• HS_FDS_PROC_IS_FUNC
• HS_FDS_RECOVERY_ACCOUNT
• HS_FDS_RECOVERY_PWD
• HS_FDS_REPORT_REAL_AS_DOUBLE
• HS_FDS_RESULTSET_SUPPORT
• HS_FDS_TRACE_LEVEL
• HS_FDS_TRANSACTION_LOG
• HS_FDS_FETCH_ROWS
• HS_IDLE_TIMEOUT
• HS_NLS_LENGTH_SEMANTICS
• HS_KEEP_REMOTE_COLUMN_SIZE
• HS_FDS_REMOTE_DB_CHARSET
• HS_FDS_SUPPORT_STATISTICS
• HS_FDS_RSET_RETURN_ROWCOUNT
• HS_FDS_SQLLEN_INTERPRETATION
• HS_FDS_ARRAY_EXEC
D.3 HS_CALL_NAME
Property Description
Default value None
Range of values Not applicable
Specifies the remote functions that can be referenced in SQL statements. The value is
a list of remote functions and their owners, separated by semicolons, in the following
format:
owner_name.function_name
D-3
Appendix D
HS_DB_DOMAIN
For example:
owner1.A1;owner2.A2;owner3.A3
If an owner name is not specified for a remote function, the default owner name
becomes the user name used to connect to the remote database (specified when the
Heterogeneous Services database link is created or taken from user session if not
specified in the DB link).
The entries for the owner names and the function names are case sensitive.
D.4 HS_DB_DOMAIN
Default value WORLD
Range of values 1 to 199 characters
Specifies a unique network sub-address for a non-Oracle system. The HS_DB_DOMAIN

initialization parameter is similar to the DB_DOMAIN initialization parameter, described in
the Oracle Database Reference. The HS_DB_DOMAIN initialization parameter is required
if you use the Oracle Names server. The HS_DB_NAME and HS_DB_DOMAIN initialization
parameters define the global name of the non-Oracle system.
Note:
The HS_DB_NAME and HS_DB_DOMAIN initialization parameters must combine to
form a unique address in a cooperative server environment.
D.5 HS_DB_INTERNAL_NAME
Default value 01010101
Range of values 1 to 16 hexadecimal characters
Specifies a unique hexadecimal number identifying the instance to which the

Heterogeneous Services agent is connected. This parameter's value is used as part
of a transaction ID when global name services are activated. Specifying a nonunique
number can cause problems when two-phase commit recovery actions are necessary
for a transaction.
D.6 HS_DB_NAME
Default value HO
Range of values 1 to 8 characters
D-4
Appendix D
HS_DESCRIBE_CACHE_HWM
Specifies a unique alphanumeric name for the data store given to the non-Oracle
system. This name identifies the non-Oracle system within the cooperative server
environment. The HS_DB_NAME and HS_DB_DOMAIN initialization parameters define the
global name of the non-Oracle system.
D.7 HS_DESCRIBE_CACHE_HWM
Default value 100
Range of values 1 to 4000
Specifies the maximum number of entries in the describe cache used by

Heterogeneous Services. This limit is known as the describe cache high water mark.
The cache contains descriptions of the mapped tables that Heterogeneous Services
reuses so that it does not have to re-access the non-Oracle data store.
If you are accessing many mapped tables, increase the high water mark to improve
performance. Increasing the high water mark improves performance at the cost of
memory usage.
D.8 HS_FDS_ARRAY_EXEC
Default Value TRUE
Range of values {TRUE|FALSE}
Syntax HS_FDS_ARRAY_EXEC= {TRUE|FALSE}
If set to TRUE, the gateway will use array operations for insert, update, delete
statements containing binds against the remote data source. The array size is
determined by the value of the HS_FDS_FETCH_ROWS init parameter.
If set to FALSE, the gateway will not use array operations for insert, update, and delete
statements. Instead, a single statement will be issued for every value.
D.9 HS_FDS_AUTHENTICATE_METHOD
HS_FDS_AUTHENTICATE_METHOD initialization parameter for Oracle Database Gateway
for SQL Server.
Default Value CLEARTEXT
Range of values {CLEARTEXT | ENCRYPT | ENCRYPT_BOTH | CLIENT}
Syntax HS_FDS_AUTHENTICATE_METHOD= {CLEARTEXT | ENCRYPT |
ENCRYPT_BOTH | CLIENT}
Specifies the way in which user ID and password are sent to the remote DB2 server
and authenticated. Valid values are:
D-5
Appendix D
HS_FDS_CONNECT_INFO
• CLEARTEXT : user ID and password are sent in clear text to server (default).
• ENCRYPT : password is sent encrypted to server.
• ENCRYPT_BOTH : user ID and password are sent encrypted to server.
• CLIENT : user ID is validated on the client side instead of by the server.
D.10 HS_FDS_CONNECT_INFO
Default Value None
Range of Values Not applicable
HS_FDS_CONNECT_INFO that describes the connection to the non-Oracle system.
The default initialization parameter file already has an entry for this parameter. The
syntax for HS_FDS_CONNECT_INFO for the gateway is as follows:
For UNIX:
HS_FDS_CONNECT_INFO=host_name[[:port_number]|/[instance_name]][/database_name]
where, host_name is the host name or IP address of the machine hosting the SQL
Server database, port_number is the port number of the SQL Server, instance_name
is the instance of SQL Server running on the machine, and database_name is the SQL
Server database name.
Either of the variables port_number or instance_name can be used, but not both
together. Optionally, they both can be omitted. The variable database_name is always
optional. The slash (/) is required when a particular value is omitted. For example, all
of the following entries are valid:
HS_FDS_CONNECT_INFO=host_name/instance_name/database_name
HS_FDS_CONNECT_INFO=host_name//database_name
HS_FDS_CONNECT_INFO=host_name:port_name//database_name
HS_FDS_CONNECT_INFO=host_name/instance_name
HS_FDS_CONNECT_INFO=host_name
For Windows:
HS_FDS_CONNECT_INFO= host_name/[instance_name][/database_name]
where, host_name is the host name or IP address of the machine hosting the SQL
Server database, instance_name is the instance of SQL Server running on the
machine, and database_name is the SQL Server database name.
Both instance_name and database_name are optional. If instance_name is omitted and

database_name is provided, the slash (/) is required. This can be shown as follows:
HS_FDS_CONNECT_INFO= host_name//database_name
This release supports IPv6 format, so you can enter IPv6 format in place of hostname,
but you need to wrap square brackets around the IPv6 specification.
For example:
HS_FDS_CONNECT_INFO=[2001:0db8:20c:f1ff:fec6:38af]:port_number/…
D-6
Appendix D
HS_FDS_DATE_MAPPING
D.11 HS_FDS_DATE_MAPPING
Default Value DATE
Range of Values DATE|CHAR
Syntax HS_FDS_DATE_MAPPING={DATE|CHAR}
If set to CHAR, then non-oracle target date would be mapped to CHAR(10). If set to DATE,
then non-Oracle target date would be mapped to Oracle date.
D.12 HS_FDS_ENCRYPT_SESSION
Default Value NONE
Range of values {NONE|SSL|NOTRUST_SSL}
Syntax HS_FDS_ENCRYPT_SESSION = {NONE|SSL|NOTRUST_SSL}
Specifies the way the session to SQL Server is encrypted. Valid values are:
• NONE : data transmitted between the gateway and SQL Server is not encrypted.
(default).
• SSL : data transmitted between the gateway and SQL Server is encrypted using
SSL.
• NOTRUST_SSL: This option is equivalent to the SSL setting, with initialization
parameter HS_FDS_VALIDATE_SERVER_CERT = DISABLED
D.13 HS_FDS_FETCH_ROWS
Default Value 100
Range of Values Any integer between 1 and 1000
Syntax HS_FDS_FETCH_ROWS=num
HS_FDS_FETCH_ROWS specifies the fetch array size. This is the number of rows
to be fetched from the non-Oracle database and to return to Oracle database
at one time. This parameter will be affected by the HS_RPC_FETCH_SIZE and
HS_RPC_FETCH_REBLOCKING parameters.
D.14 HS_FDS_PROC_IS_FUNC
Default Value FALSE
D-7
Appendix D
HS_FDS_RECOVERY_ACCOUNT
Range of Values TRUE, FALSE
Enables return values from functions. By default, all stored procedures and functions
do not return a return value to the user.
Note:
If you set this initialization parameter, you must change the syntax of the
procedure execute statement for all existing stored procedures to handle
return values.
D.15 HS_FDS_RECOVERY_ACCOUNT
Default Value RECOVER
Range of values Any valid user ID
Specifies the name of the recovery account used for the commit-confirm transaction
model. An account with user name and password must be set up at the non-
Oracle system. For more information about the commit-confirm model, see the
HS_TRANSACTION_MODEL parameter.
The name of the recovery account is case sensitive.
D.16 HS_FDS_RECOVERY_PWD
Default Value RECOVER
Range of values Any valid password
Specifies the password of the recovery account used for the commit-confirm
transaction model set up at the non-Oracle system. For more information about the
commit-confirm model, see the HS_TRANSACTION_MODEL parameter.
The name of the password of the recovery account is case sensitive.
D.17 HS_FDS_REMOTE_DB_CHARSET
Default Value None
Range of values Not applicable
Syntax HS_FDS_REMOTE_DB_CHARSET
D-8
Appendix D
HS_FDS_REPORT_REAL_AS_DOUBLE
This parameter is valid only when HS_LANGUAGE is set to AL32UTF8 and the gateway
runs on Windows. As more Oracle databases and non-Oracle databases use
Unicode as database character sets, it is preferable to also run the gateway in
Unicode character set. To do so, you must set HS_LANGUAGE=AL32UTF8. However,
when the gateway runs on Windows, the Microsoft ODBC Driver Manager
interface can exchange data only in the double-byte character set, UCS2.
This results in extra ratio expansion of described buffer and column sizes. To
compensate, the gateway can re-adjust the column size if HS_FDS_REMOTE_DB_CHARSET
is set to the corresponding non-Oracle database character set. For example,
HS_FDS_REMOTE_DB_CHARSET=KO16KSC5601.
D.18 HS_FDS_REPORT_REAL_AS_DOUBLE
Default Value FALSE
Enables Oracle Database Gateway for SQL Server to treat SINGLE FLOAT PRECISION
fields as DOUBLE FLOAT PPRECISION fields.
D.19 HS_FDS_RSET_RETURN_ROWCOUNT
Default Value FALSE
Syntax HS_FDS_RSET_RETURN_ROWCOUNT= {TRUE|FALSE}
When set to TRUE, the gateway returns the row counts of DML statements that are
executed inside a stored procedure. The row count is returned as a single row, single
column result set of type signed integer.
When set to FALSE, the gateway skips the row counts of DML statements that are
executed inside a stored procedure. This is the default behavior, and it is the behavior
of 11.1 and older gateways.
D.20 HS_FDS_RESULTSET_SUPPORT
Default Value FALSE
Enables result sets to be returned from stored procedures. By default, all stored
procedures do not return a result set to the user.
D-9
Appendix D
HS_FDS_SQLLEN_INTERPRETATION
Note:
If you set this initialization parameter, you must do the following:
• Change the syntax of the procedure execute statement for all existing
stored procedures, to handle result sets
• Work in the sequential mode of Heterogeneous Services
D.21 HS_FDS_SQLLEN_INTERPRETATION
Default Value 64
Range of values {64|32}
Syntax HS_FDS_SQLLEN_INTERPRETATION= {64|32}
This parameter is only valid for 64 bit platforms. ODBC standard specifies SQLLEN
(of internal ODBC construct) being 64 bit on 64 bit platforms, but some ODBC
driver managers and drivers violate this convention, and implement it as 32 bit.
In order for the gateway to compensate their behavior, you need to specify
HS_FDS_SQLLEN_INTERPRETATION=32 if you use these types of driver managers and
driver.
D.22 HS_FDS_SUPPORT_STATISTICS
Default Value TRUE
Syntax HS_FDS_SUPPORT_STATISTICS= {TRUE|FALSE}
We gather statistics from the non-Oracle database by default. You can

choose to disable the gathering of remote database statistics by setting the
HS_FDS_SUPPORT_STATISTICS parameter to FALSE.
D.23 HS_FDS_TIMESTAMP_MAPPING
Default Value DATE
Range of Values CHAR|DATE|TIMESTAMP
Syntax HS_FDS_TIMESTAMP_MAPPING={CHAR|DATE|TIMESTAMP}
If set to CHAR , then non-Oracle target timestamp would be mapped to CHAR(26). If set
to DATE (default), then non-Oracle target timestamp would be mapped to Oracle DATE.
D-10
Appendix D
HS_FDS_TRACE_LEVEL
If set to TIMESTAMP, then non-Oracle target timestamp would be mapped to Oracle

TIMESTAMP.
D.24 HS_FDS_TRACE_LEVEL
Default Value OFF
Range of values OFF, ON, DEBUG
Specifies whether error tracing is turned on or off for gateway connectivity.

The following values are valid:
• OFF disables the tracing of error messages.
• ON enables the tracing of error messages that occur when you encounter
problems. The results are written by default to a gateway log file in LOG directory
where the gateway is installed.
• DEBUG enables the tracing of detailed error messages that can be used for
debugging.
D.25 HS_FDS_TRANSACTION_ISOLATION
Default Value READ_COMMITTED
Range of Values {READ_UNCOMMITTED|READ_COMMITTED|REPEATABLE_READ|
SERIALIZABLE}
Syntax HS_FDS_ISOLATION_LEVEL={{READ_UNCOMMITTED|
READ_COMMITTED|REPEATABLE_READ|SERIALIZABLE}
HS_FDS_TRANSACTION_ISOLATION specifies the isolation level that is used for the

transaction that the gateway opens on the non-Oracle database.
The isolation levels of READ_UNCOMMITTED, READ_COMMITTED, REPEATABLE_READ, and
SERIALIZABLE are the four isolation levels defined in the SQL standard and adopted
by both ANSI and ISO/IEC. For additional information regarding them, see Oracle
Database Concepts.
Use caution when specifying an isolation level lower than the Oracle transaction
isolation level being used, as the gateway transaction will have different Preventable
Read Phenomena from what will occur in the Oracle database transaction.
D.26 HS_FDS_TRANSACTION_LOG
Default Value HS_TRANSACTION_LOG
Range of Values Any valid table name
D-11
Appendix D
HS_FDS_TRUSTSTORE_FILE
Specifies the name of the table created in the non-Oracle system for logging
transactions. For more information about the transaction model, see the
HS_TRANSACTION_MODEL parameter.
D.27 HS_FDS_TRUSTSTORE_FILE
Default Value none
Range of values path to truststore file
Syntax HS_FDS_TRUSTSTORE_FILE = path to truststore file
Specifies the path that specifies the location of the truststore file. The truststore file
contains a list of the valid Certificate Authorities (CAs) that are trusted by the client
machine for SSL server authentication.
D.28 HS_FDS_TRUSTSTORE_PASSWORD
Default Value none
Range of values password
Syntax HS_FDS_TRUSTSTORE_PASSWORD= password
Specifies the password required to access the truststore.
D.29 HS_FDS_VALIDATE_SERVER_CERT
Default Value ENABLED
Range of values {ENABLED|DISABLED}
Syntax HS_FDS_VALIDATE_SERVER_CERT = {ENABLED|DISABLED}
Specifies whether the driver validates the certificate that is sent by the database server
when SSL encryption is enabled through HS_FDS_ENCRYPT_SESSION. When using SSL
server authentication, any certificate sent by the server must be issued by a trusted
Certificate Authority. Valid values are:
• ENABLED : the gateway validates the certificate that is sent by the database
server. Any certificate from the server must be issued by a trusted Certificate
Authority in the truststore file. The truststore information is specified using
the HS_FDS_TRUSTSTORE_FILE and HS_FDS_TRUSTSTORE_PASSWORD initialization
parameters.
• DISABLED : the gateway does not validate the certificate that is sent by the
database server.
D-12
Appendix D
HS_IDLE_TIMEOUT
D.30 HS_IDLE_TIMEOUT
Default Value 0 (no timeout)
Range of Values 0-9999 (minutes)
Syntax HS_IDLE_TIMEOUT=num
This feature is only available for Oracle Net TCP protocol. When there is no activity for
a connected gateway session for this specified time period, the gateway session would
be terminated automatically with pending update (if any) rolled back.
D.31 HS_KEEP_REMOTE_COLUMN_SIZE
Default Value OFF
Range of Values OFF | LOCAL | REMOTE | ALL
Syntax HS_KEEP_REMOTE_COLUMN_SIZE = OFF | LOCAL |
REMOTE | ALL
Parameter type String
HS_KEEP_REMOTE_COLUMN_SIZE specifies whether to suppress ratio expansion when

computing the length of (VAR)CHAR datatypes during data conversion from the non-
Oracle database to the gateway, and then to the Oracle database. When it is set
to REMOTE, the expansion is suppressed between the non-Oracle database and the
gateway. When it is set to LOCAL, the expansion is suppressed between the gateway
and the Oracle database. When it is set to ALL, the expansion is suppressed from the
non-Oracle database to the Oracle database.
When the parameter is set, the expansion is suppressed when reporting the
remote column size, calculating the implicit resulting buffer size, and instantiating
in the local Oracle database. This has effect only for remote column size from
non-Oracle database to Oracle database. If the gateway runs on Windows and
HS_LANGUAGE=AL32UTF8, then you must not specify this parameter, as it would influence
other ratio related parameter operation. It has no effect for calculating ratio for data
moving from Oracle database to non-Oracle database through gateway during INSERT,
UPDATE, or DELETE.
D.32 HS_LANGUAGE
Default value System-specific
Range of values Any valid language name (up to 255 characters)
Provides Heterogeneous Services with character set, language, and territory

information of the non-Oracle data source. The value must use the following format:
D-13
Appendix D
HS_LANGUAGE
language[_territory.character_set]
Note:
The globalization support initialization parameters affect error messages, the
data for the SQL Service, and parameters in distributed external procedures.
D.32.1 Character Sets

Ideally, the character sets of the Oracle database and the non-Oracle data source are
the same. In almost all cases, HS_LANGUAGE should be set exactly the same as Oracle
database character set for optimal character set mapping and performance. If they are
not the same, Heterogeneous Services attempts to translate the character set of the
non-Oracle data source to the Oracle database character set, and back again. The
translation can degrade performance. In some cases, Heterogeneous Services cannot
translate a character from one character set to another.
Note:
The specified character set must be a superset of the operating system
character set on the platform where the agent is installed.
As more Oracle databases and non-Oracle databases use Unicode as database

character sets, it is preferable to also run the gateway in Unicode character set. To
do so, you must set HS_LANGUAGE=AL32UTF8. However, when the gateway runs on
Windows, the Microsoft ODBC Driver Manager interface can exchange data only in
the double-byte character set, UCS2. This results in extra ratio expansion of described
buffer and column sizes. Refer to HS_FDS_REMOTE_DB_CHARSET for instruction
on how to adjust to correct sizes.
D.32.2 Language
The language component of the HS_LANGUAGE initialization parameter determines:
• Day and month names of dates

• AD, BC, PM, and AM symbols for date and time
• Default sorting mechanism
Note that Oracle does not determine the language for error messages for the
generic Heterogeneous Services messages (ORA-25000 through ORA-28000). These
are controlled by the session settings in the Oracle database.
D.32.3 Territory
The territory clause specifies the conventions for day and week numbering, default
date format, decimal character and group separator, and ISO and local currency
symbols. Note that the level of globalization support between the Oracle database
and the non-Oracle data source depends on how the gateway is implemented.
D-14
Appendix D
HS_LONG_PIECE_TRANSFER_SIZE
D.33 HS_LONG_PIECE_TRANSFER_SIZE
Default value 64 KB
Range of values Any value up to 2 GB
Sets the size of the piece of LONG data being transferred. A smaller piece size means
less memory requirement, but more round-trips to fetch all the data. A larger piece size
means fewer round-trips, but more of a memory requirement to store the intermediate
pieces internally. Thus, the initialization parameter can be used to tune a system
for the best performance, with the best trade-off between round-trips and memory
requirements, and network latency or response time.
D.34 HS_NLS_LENGTH_SEMANTICS
Default Value BYTE
Range of Values BYTE | CHAR
Syntax HS_NLS_LENGTH_SEMANTICS = { BYTE | CHAR }
This release of gateway has Character Semantics functionality equivalent to

the Oracle Database Character Semantics, that is, NLS_LENGTH_SEMANTICS. When
HS_NLS_LENGTH_SEMANTICS is set to CHAR, the (VAR)CHAR columns of SQL Server
database are to be interpreted as having CHAR semantics. The only situation the
gateway does not honor the HS_NLS_LENGTH_SEMANTICS=CHAR setting is when both
Oracle database and the gateway are on the same multi-byte character set
D.35 HS_OPEN_CURSORS
Default value 50
Range of values 1 to the value of Oracle's OPEN_CURSORS initialization parameter
Defines the maximum number of cursors that can be open on one connection to a
non-Oracle system instance.
The value never exceeds the number of open cursors in the Oracle database.
Therefore, setting the same value as the OPEN_CURSORS initialization parameter in the
Oracle database is recommended.
D.36 HS_RPC_FETCH_REBLOCKING
Default value ON
D-15
Appendix D
HS_RPC_FETCH_SIZE
Range of values OFF or ON
Controls whether Heterogeneous Services attempts to optimize performance of

data transfer between the Oracle database and the Heterogeneous Services agent
connected to the non-Oracle data store.
The following values are possible:
• OFF disables reblocking of fetched data so that data is immediately sent from agent
to server.
• ON enables reblocking, which means that data fetched from the non-Oracle system
is buffered in the agent and is not sent to the Oracle database until the amount
of fetched data is equal to or higher than the value of HS_RPC_FETCH_SIZE
initialization parameter. However, any buffered data is returned immediately when
a fetch indicates that no more data exists or when the non-Oracle system reports
an error.
D.37 HS_RPC_FETCH_SIZE
Default value 50000
Range of values 1 to 10000000
Tunes internal data buffering to optimize the data transfer rate between the server and
the agent process.
Increasing the value can reduce the number of network round-trips needed to transfer
a given amount of data, but also tends to increase data bandwidth and to reduce
latency as measured between issuing a query and completion of all fetches for the
query. Nevertheless, increasing the fetch size can increase latency for the initial fetch
results of a query, because the first fetch results are not transmitted until additional
data is available.
D.38 HS_TIME_ZONE
Default value for Derived from the NLS_TERRITORY initialization parameter
'[+|-]hh:mm'
Range of values for Any valid datetime format mask
'[+|-]hh:mm'
Specifies the default local time zone displacement for the current SQL session. The
format mask, [+|-]hh:mm, is specified to indicate the hours and minutes before or after
UTC (Coordinated Universal Time—formerly Greenwich Mean Time). For example:
HS_TIME_ZONE = [+ | -] hh:mm
D-16
Appendix D
HS_TRANSACTION_MODEL
D.39 HS_TRANSACTION_MODEL
Default Value COMMIT_CONFIRM
Range of Values COMMIT_CONFIRM, READ_ONLY, SINGLE_SITE,
READ_ONLY_AUTOCOMMIT, SINGLE_SITE_AUTOCOMMIT
Specifies the type of transaction model that is used when the non-Oracle database is
updated by a transaction.
The following values are possible:
• COMMIT_CONFIRM provides read and write access to the non-Oracle database and
allows the gateway to be part of a distributed update. To use the commit-confirm
model, the following items must be created in the non-Oracle database:
– Transaction log table. The default table name is HS_TRANSACTION_LOG. A
different name can be set using the HS_FDS_TRANSACTION_LOG parameter. The
transaction log table must be granted SELECT, DELETE, and INSERT privileges
set to public.
– Recovery account. The account name is assigned with the
HS_FDS_RECOVERY_ACCOUNT parameter.
– Recovery account password. The password is assigned with the
HS_FDS_RECOVERY_PWD parameter.
• READ_ONLY provides read access to the non-Oracle database.
• SINGLE_SITE provides read and write access to the non-Oracle database.
However, the gateway cannot participate in distributed updates.
• READ_ONLY_AUTOCOMMIT provides read only access to the non-Oracle database that
does not use logging.
• SINGLE_SITE_AUTOCOMMIT provides read and write access to the non-Oracle
database without logging. The gateway cannot participate in distributed updates.
Moreover, any update to the non-Oracle database is committed immediately.
D.40 IFILE
Default value None
Range of values Valid parameter file names
Use the IFILE initialization parameter to embed another initialization file within the
current initialization file. The value should be an absolute path and should not contain
environment variables. The three levels of nesting limit do not apply.
D-17
Appendix D
IFILE
See Also:
Oracle Database Reference
D-18
Index
A Data type (continued)
IMAGE, A-1
ALTER statement, B-1 LONG RAW, A-1
Arithmetic operators, B-3 MONEY, A-1
NCHAR, A-1
NUMBER, A-1
B NUMERIC, A-1
BIGINT data type, A-1 NVARCHAR, A-1
BINARY data type, A-1 RAW, A-1
BIT data type, A-1 REAL, A-1
SMALL DATETIME, A-1
SMALL MONEY, A-1
C SMALLINT, A-2
Case rules, 2-9 TIMESTAMP, A-2
Case studies, 3-1 TINYINT, A-2
Chained mode, 2-9 VARBINARY, 2-17, A-2
CHAR data type, A-1 VARCHAR, A-2
character sets DATE data type, A-1
Heterogeneous Services, D-14 DATETIME data type, A-1
COMMIT DECIMAL data type, A-1
restrictions, 2-13 DELETE statement, 3-5, B-1, B-2
Comparison operators, B-3 demonstration build SQL script, 3-2
CONCAT operator, 2-18 Demonstration files, 3-2
CONNECT BY clause, 2-15 Demonstration tables, 3-2
COPY command, 2-16 Demonstration tables build SQL script, 3-2
CREATE statement, B-1 describe cache high water mark
Cursor loops definition, D-5
restrictions, 2-13 DROP statement, B-1
D E
Data definition language, B-1 Encrypted format login, 2-17
Data dictionary Error messages
views, C-2 error tracing, D-11
Data type Errors
BIGINT, A-1 ORA-02070, 2-13
BINARY, A-1 Executing Stored Procedures, 3-6
BIT, A-1
CHAR, A-1 F
conversion, 2-11
DATE, A-1 fetch array size, with HS_FDS_FETCH_ROWS,
DATETIME, A-1 D-7
DECIMAL, A-1 FLOAT data type, A-1
FLOAT, A-1 Functions in SQL, 2-3
Index-1
Index
G HS_RPC_FETCH_REBLOCKING initialization
parameter, D-15
Gateway HS_RPC_FETCH_SIZE initialization parameter,
case studies, 3-1 D-16
data dictionary tables, C-1 HS_TIME_ZONE initialization parameter, D-16
pass-through feature, 2-2, 2-14
supported functions, B-1
supported SQL syntax, B-1
I
globalization support IFILE initialization parameter, D-17
Heterogeneous Services, D-13 IMAGE data type, A-1
GRANT statement, B-1 Initialization parameter file
Group functions, B-3 customizing, D-1
INSERT statement, 3-6, B-1, B-2
H isolation level,
HS_FDS_TRANSACTION_ISOLATION,
Heterogeneous Services D-11
defining maximum number of open cursors,
D-15
optimizing data transfer, D-15
K
setting global name, D-5 Known restrictions, 2-12
specifying cache high water mark, D-5
tuning internal data buffering, D-16
tuning LONG data transfer, D-15 L
Hexadecimal notation, 2-10 Locking, database, 2-12
HS_CALL_NAME initialization parameter, D-3 LONG RAW data type, A-1
HS_DB_NAME initialization parameter, D-5
HS_DESCRIBE_CACHE_HWM initialization
parameter, D-5 M
HS_FDS_CONNECT_INFO, D-6
MONEY data type, A-1
HS_FDS_FETCH_ROWS parameter, D-7
HS_FDS_PROC_IS_FUNC initialization
parameter, D-7 N
HS_FDS_RECOVERY_PWD initialization
parameter, D-9 NCHAR data type, A-1
HS_FDS_RESULTSET_SUPPORT initialization NULL values, 2-9
parameter, D-9 NUMBER data type, A-1
HS_FDS_TRACE_LEVEL initialization NUMERIC data type, A-1
parameter, D-11 NVARCHAR data type, A-1
enabling agent tracing, D-2 NVL function, 3-5
HS_FDS_TRANSACTION_ISOLATIONparamete
r, D-11 O
HS_FDS_TRANSACTION_LOG initialization
parameter, D-11 Objects, naming rules, 2-9
HS_IDLE_TIMEOUT initialization parameter, ORA-02070, 2-13
D-13
HS_KEEP_REMOTE_COLUMN_SIZE
initialization parameter, D-13
P
HS_LANGUAGE initialization parameter, D-13 parameters
HS_LONG_PIECE_TRANSFER_SIZE gateway initialization file
initialization parameter, D-15 HS_FDS_FETCH_ROWS, D-7
HS_NLS_LENGTH_SEMANTICS initialization HS_FDS_TRANSACTION_ISOLATION,
parameter, D-15 D-11
HS_OPEN_CURSORS initialization parameter, Pass-Through Feature, 3-6
D-15 Passing commands to database, 2-14
Pattern Matching, B-3
Index-2
Index
PL/SQL, 2-18 String functions, B-4

SUM function, 3-5
R
T
RAW data type, A-1
REAL data type, A-1 TIMESTAMP data type, A-2
remote TINYINT data type, A-2
HS_FDS_TRANSACTION_ISOLATION, D-11 Transaction modes, 2-9
remote functions transactional capability, 2-13
referenced in SQL statements, D-3 transactional integrity, 2-13
ROLLBACK TRUNCATE statement, B-1
restrictions, 2-13 Two-phase commit, 2-13
ROWID, 2-15, 2-16
U
S
UPDATE statement, 2-16, 3-5, 3-6, B-2
savepoint support, 2-13
SELECT statement, 3-6, B-2, C-1
SMALL DATETIME data type, A-1
V
SMALLINT data type, A-2 VARBINARY data type, 2-17, A-2
SQL VARCHAR data type, A-2
statements,
HS_FDS_TRANSACTION_ISOLATION,
D-11 W
Stored procedures, 2-14, 2-18 WHERE CURRENT OF clause, 2-15
running in chained mode, 2-9
Stored procedures in SQL Server, 2-3
Index-3

Oracle 19c - Database Gateway SQL Server Users Guide

Uploaded by

Copyright:

Available Formats

Oracle 19c - Database Gateway SQL Server Users Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle 19c - Database Gateway SQL Server Users Guide

Uploaded by

Copyright:

Available Formats

Oracle® Database Gateway for SQL

Copyright © 2002, 2021, Oracle and/or its affiliates.

Primary Author: Rhonda Day

1 Introduction to the Oracle Database Gateway for SQL Server

2 SQL Server Gateway Features and Restriction

A Data Type Conversion

B Supported SQL Syntax and Functions

Access to Oracle Support

1.1 Overview of Oracle Database Gateways

1.2 About Heterogeneous Services Technology

1.3 About Oracle Database Gateway for SQL Server

2.1 Remote Insert Rowsource

2.2 Using the Pass-Through Feature

Use the DBMS_HS_PASSTHROUGH package in a PL/SQL block to specify the statement to

Where command cannot be one of the following:

2.3 Executing Stored Procedures and Functions

2.4 CHAR Semantics

2.5 Multi-byte Character Sets Ratio Suppression

2.6 IPv6 Support

2.7 Gateway Session IDLE Timeout

2.8 Remote User-defined Function Support

2.8.1 Return Values and Stored Procedures

INPUT := 'JOHN SMYTHE';

2.8.2 Result Sets and Stored Procedures

• On execution of a stored procedure, all result sets returned by a previously

2.8.2.1 OCI Program Fetching from Result Sets in Sequential Mode

/* Prepare procedure call statement */

/* Handle Initialization code skipped */

/* Bind procedure arguments */

OCIBindByPos(STMH, &BNDH[2], ERRH, 2, (dvoid *) rset, 0, SQLT_RSET,

/* Convert result set to statement handle */

/* After this the user can fetch from rstmt */

OCIStmtPrepare(STMH, ERRH, n_rs_stm, strlen(n_rs_stm), OCI_NTV_SYNTAX,

/* Bind return value */

/* Execute statement to get next result set*/

/* Convert next result set to statement handle */

/* Repeat execution of get_next_result_set to get the output arguments */

2.8.2.2 PL/SQL Program Fetching from Result Sets in Sequential Mode

create or replace package rcpackage is

-- Close ref cursor

-- Get the next result set returned by the stored procedure

--Close ref cursor

-- Get the output arguments from the remote stored procedure

-- Fetch them and insert them into the outargs table

-- Close ref cursor

2.9 Database Compatibility Issues for SQL Server

2.9.1 Implicit Transactions (Chained Mode)

2.9.2 Column Definitions

2.9.3 Naming Rules

2.9.3.1 Rules for Naming Objects

2.9.3.2 Case Sensitivity

SQL> SELECT * FROM SCOTT."emp"@MSQL;

Using views is a workaround solution that duplicates data dictionary information

2.9.4 Data Types

2.9.4.1 Binary Literal Notation

2.9.4.2 Bind Variables With LONG Columns

2.9.4.3 Data Type Conversion

To avoid problems with implicit conversions, add explicit conversions, as in the

2.9.5.1 Row Selection

2.9.5.2 Empty Strings