Skip Headers

Oracle® Database Heterogeneous Connectivity Administrator's Guide
10g Release 1 (10.1)

Part Numb er B10764-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents< /font>
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previo
us page
Previous
Go to next page
Next
View PDF


Preface

This manual describes Oracle's ap proach for information integration in a heterogeneous environment. Specifically, it describes Oracle Transparent Gateways and Generic Connectivity and is meant to be an administrator's guide for these Oracle products.

This pr eface contains these topics:

Audience

Oracle Database Heterogeneous Connectivity Administrator's Guide is intended for the following users:

To use this document, you should be familiar with the following information:

Organization

This document contai ns:

Chapter 1, "Introduction"

This chapter describes the challenges of operating in a heterogen eous environment. Oracle recognizes these challenges and offers both synchronous and asynchronous solutions that enable companies to easily operate in such an environment. The two synchronous solutions, Oracle Transparent Gateways and Generic Connectivity, are discu ssed this book.

Cha pter 2, "The Role of the Heterogeneous Services Component"

Oracle's synchro nous solutions for operating in a heterogeneous environment are Oracle Transparent Gateways and Generic Connectivity. The common comp onent of the Oracle database server for supporting these solutions is Heterogeneous Services. This chapter describes the architecture and functionality of the Heterogeneous Services component and its interaction with Oracle Transparent Gateways and Generic Connectiv ity.

Chapter  3, "Features of Oracle Transparent Gateways and Generic Connectivity"

This chapt er describes the major features provided by Oracle Transparent Gateways and Generic Connectivity.

Chapter 4, "Using Heterogeneous Services Agents"

This chapter explains how to use Heterogeneous Services agents.

Chapter 5, "Multithreaded Age nts"

This chapter explains what multithreaded agents are, how they contribute to the overall efficiency of a distributed database system, and how to administer multithreaded agents.

Chapter 6, "Performance Tips"

This chapter explains how to optimize distributed SQL statements, how to use partition views w ith Oracle Transparent Gateways, and how to optimize the performance of distributed queries.

Chapter 7, "Generic Connectivity"

This chapter describes the configuration and usage of generic connectivity agents.

Appendix A, "Heterogeneous Services Initialization Parameters"

This appendix lists heterogeneous services initializ ation parameters and provides instructions on how to set them.

Appendix B, "Datatype Mapping"

The tables in this appendix show how Oracle maps ANSI datatypes through ODBC and OLE DB interfaces to supported Oracle datatypes when it is retrieving data from a non-Oracle system.

Appendix C, "Data Dictionary Translation Support"

Thi s appendix documents data dictionary translation support. It explains how to access non-Oracle data dictionaries, lists heterogeneous services data dictionary views, describes how to use supported views and tables, and explains data dictionary mapping.

Related Documentation

For more information, see these Oracle resources:

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 u se them yourself.

Printed documentation is available for sale in the Oracle Store at

http://oraclestore.oracle.com/ < /pre>

To download free release notes, installation documentation, white papers, or other collate ral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be don e at

http://otn.oracle.com/membership/
index.html

If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at

http://otn.oracle.com/documentation/index.html

Conventions

This section describes t he conventions used in the text and code examples of this documentation set. It describes:

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

< /tbody>
Convention Meaning Example

Bold

Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.

When you specify this clause, you create an index-organized tab le.

Italics

Italic typeface indicates book tit les or emphasis.

Oracle Database Concepts

Ensure that the recovery catalog and target database do not reside on the same disk.

UPPERCASE monospace (fixed-width) font

Uppercase m onospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and struc tures, usernames, and roles.

You can specify this clause only for a NUMBER column.

You can back up the database by using the BACKUP c ommand.

Query the TABLE_NAME column in the USER_TABLES data diction ary view.

Use the DBMS_STATS.GENERATE_STATS procedure.

lowercase monospace (fixed-width) font

Lowercase monospace typeface indicates executables, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net se rvice names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, u sernames and roles, program units, and parameter values.

Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.

Enter sqlplus to open SQL*Plus.

The password i s specified in the orapwd file.

Back up the datafiles and control files in the < code>/disk1/oracle/dbs directory.

The department_id, department_nam e, and location_id columns are in the hr.departments table.

Set the QUERY_REWRITE_ENABLED initialization parameter to true.

Con nect as oe user.

The JRepUtil class implements these methods.

lowercas e italic monospace (fixed-width) font

Lowercase italic monospace font represents placeholders or variables.

You can spec ify the parallel_clause.

Run Uold_release .SQL where old_release refers to the release you installed prior to upgrading.

Conventions in Code Examples< /h4>

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention Meaning Example
[ ]

Brackets enclose one or more optional items. Do not en ter the brackets.

DECIMAL (digits [ , precision ])
{ }

Braces enclose two or more item s, one of which is required. Do not enter the braces.

{ENABLE |
DISABLE}
|

A vertical bar represents a choice of two or more options w ithin brackets or braces. Enter one of the options. Do not enter the vertical bar.

{ENABLE | DISABLE}
[COMPRESS | NOCOMPRESS]
...

< /a>

Horizontal ellipsis points indicate either:

  • T hat we have omitted parts of the code that are not directly related to the example
  • That you can repeat a portion of the code

CREATE TABLE ... AS subquery;

SELECT 
col1, col2, ... , coln FROM employees;
 .
 .

 .

Vertical ellipsis points indicate that we have omitted sever al lines of code not directly related to the example.

SQL> SE
LECT NAME FROM V$DATAFILE;
NAME
------------------------------------
/
fsl/dbs/tbs_01.dbf
/fs1/dbs/tbs_02.dbf
.
.
.
/fsl/dbs/tbs_09.dbf
9 rows selected.

Other notation

You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown.

acctbal NUMBER(11,2);
acct    CONSTANT NUMBER(4) := 3;
Italics

Italicized text indicates placeholders or varia bles for which you must supply particular values.

CONNECT SYSTEM
/system_password
DB_NAME = database_name

UPPERCASE

Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with th e spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase.

SELECT last_name, employee_id FROM employees;
SELECT * FROM USER_TABLES;

DROP TABLE hr.employees;
lowercase

Lowercase ty peface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files.

Note: Some programmatic elements use a mixture of UPPERCASE and lowerca se. Enter these elements as shown.

SELECT last_name, employee_id
 FROM employees;
sqlplus hr/hr
CREATE USER mjones IDENTIFIED BY ty3MU9;

Conventions for Windows Operating Syst ems

The following table describes conventions for Windows operating systems and prov ides examples of their use.

Convention Me aning Example

Choose Start >

How to start a program.

To start the Database Configuration Ass istant, choose Start > Programs > Oracle - HOME_NAME > Configuration and Migration Tools > Databa se Configuration Assistant.

File and directory names

File and directory names a re not case sensitive. The following special characters are not allowed: left angle bracket (<), right angle bracket (>), colon (:), double quotation marks ("), slash (/), pipe (|), and dash (-). The special character backslash (\) is treated as an element sep arator, even when it appears in quotes. If the file name begins with \\, then Windows assumes it uses the Universal Naming Convention .

c:\winnt"\"system32 is the same as 
C:\WINNT\SYSTEM32
< /td>

C:\>

Represents the Windows command prompt of the current hard disk drive. The escape character in a command prompt is the caret (^). Your prompt reflects the subdirectory in which you are working. Ref erred to as the command prompt in this manual.

C:\oracle\oradata>

Special characters

The backslash (\) special ch aracter is sometimes required as an escape character for the double quotation mark (") special character at the Windows command promp t. Parentheses and the single quotation mark (') do not require an escape character. Refer to your Windows operating system documenta tion for more information on escape and special characters.

C:\&
gt;exp scott/tiger TABLES=emp QUERY=\"WHERE 
job='SALESMAN' and sal<1600\"
C:\>imp SYSTEM/password FROMUSER=scott 
TABLES=(emp, dept)
HOME_NAME

Represents the Oracle home name. The home name can be up to 16 alphanumeric characters. The only special character a llowed in the home name is the underscore.

C:\> net start Ora
cleHOME_NAMETNSListener

ORACLE_HOME and ORACLE_BASE

In releases prior to Oracle8i release 8.1.3, when you installed O racle components, all subdirectories were located under a top level ORACLE_HOME directory. For Windows NT, the default location was C:\orant for Windows NT.

This release complies with Optimal Flexible Architecture (OFA) guidelines. All subdirectories are not under a top level ORACLE_HOME directory. Th ere is a top level directory called ORACLE_BASE that by default is C:\oracle. If you install the l atest Oracle release on a computer with no other Oracle software installed, then the default setting for the first Oracle home direct ory is C:\oracle\orann, where nn is the latest release number. The Oracle ho me directory is located directly under ORACLE_BASE.

All directory path examples in this guide follow OFA conventions.

Refer to Oracle Database Pl atform Guide for Windows for additional information about OFA compliances and for information about installing Oracle products i n non-OFA compliant directories.

Go to the ORACLE_BASE\ORACLE_HOME\rdbms\admin directory.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the di sabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will co ntinue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacle s so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Pro gram Web site at

http://www.oracle.com/access
ibility/

Accessibil ity of Code Examples in Documentation

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an o therwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations tha t Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sit es.