[Contents] [Index] [Info] [Previous] [Next]

Preface

The purpose of this guide is to explain how to configure and use SQL*Net 2.3.3 for OpenVMS, including the following components:

• TNS Listener

• Oracle Names

• Oracle Intelligent Agent and SNMP Support

• Oracle Advanced Networking Option and SNMP Support

The configuration and use of the protocols: DECnet, TCP/IP, and OpenVMS Mailboxes are detailed in this guide.

The following topics are covered in this Preface:

• Audience

• How this guide is organized

• Conventions used in this guide

• Related publications

• Customer support information

• Your comments are welcome

Audience

This guide assumes that the user has a fundamental knowledge of the OpenVMS operating system; it does not document any features of OpenVMS except when they affect or are affected by SQL*Net.

Only those SQL*Net features that are specific to the OpenVMS environment are documented in this guide. For general, non-platform-specific information about SQL*Net 2.3.3, refer to the documents listed in the section "Related Publications" later in this chapter.

How This Guide is Organized

Chapter 1: Introduction

This chapter provides general conceptual information about SQL*Net Version 2.3.3 in the OpenVMS environment. It presents a configuration overview, describes the possible SQL*Net installations, and explains the role of the Transparent Network Substrate.

Chapter 2: SQL*Net Configuration with Network Manager

This chapter explains how to use the Network Manager to configure SQL*Net in the OpenVMS environment. It tells how to start Network Manager, tells what to enter in the port-specific fields, and describes how to save and distribute configuration information.

Chapter 3: The Protocol Adapters

This chapter provides information about the Mailbox, DECnet, TCP/IP, and bequeath protocol adapters on OpenVMS.

Chapter 4: The TNS Listener

This chapter provides information about the TNS listener on OpenVMS.

Chapter 5: Oracle Names

This chapter provides OpenVMS-specific information about Oracle Names. It describes the requirements and tells how to start Oracle Names from the DCL prompt.

Chapter 6: Oracle Intelligent Agent and SNMP Support

This chapter provides OpenVMS-specific information about installing and running the Oracle Intelligent Agent and information about Single Network Management Protocol (SNMP) Support.

Chapter 7: Advanced Networking Option

This chapter provides OpenVMS-specific information about installing the Advanced Networking Option (ANO).

Appendix A: Major Changes and Enhancements from Previous Versions of SQL*Net

This appendix lists the major changes from previous versions of SQL*Net to SQL*Net 2.3.3.

Appendix B: Sample ORASRV_NETV2 Command Procedure

This appendix shows the contents of the ORASRV_NETV2_COM.SAMPLE file.

Appendix C: Sample ORASRV_BEQ_<sid> Command Procedure

This appendix shows the contents of the ORASRV_BEQ_COM.SAMPLE file.

Appendix D: SQL*Net Configuration for OpenVMS Clusters

This appendix describes how to configure SQL*Net for easy operation in OpenVMS Clusters/shared disk configurations.

Conventions Used in this Guide

Syntax

monospaced font	Monospaced font is used to represent information displayed or entered on terminals. For example, menu screens that are displayed during the Oracle7 installation procedure are represented in this guide with monospaced font.
UPPERCASE	UPPERCASE in monospaced font represents a command name. Enter the text exactly as shown.
UPPERCASE	UPPERCASE words within the text refer to command names or file names.
<variable>	<lowercase italicized words> in monospaced font enclosed by angle brackets represent a variable on the command line. Substitute an appropriate value.
<variable>	<lowercase italicized words> enclosed by angle brackets within the text refer to variable names.

Basic Terms Used in this Guide

Oracle	Generally refers to the company, Oracle Corporation, that develops and distributes the Oracle7 Server, SQL*Net, and related products.
Oracle7 Server	Refers to a single Oracle product, the Oracle7 Server, that stores, manages, and manipulates data. It is sometimes referred to as the kernel, the RDBMS, or simply Oracle7. The product name includes such subproducts as Server Manager and SQL*Loader.
Oracle7 System	Refers to all the Oracle products installed at a site, including the Oracle7 Server and any optional tools such as Oracle Forms or SQL*Net, and to the structures created in shared OpenVMS memory when Oracle7 is running.
Database	In this guide, the reference is only to the physical data files that contain data stored by the Oracle7 Server.

SQL*Net Terms Used in this Guide

TNS-based product	A product based on the Transparent Network Substrate (TNS) refers to software that directly calls or uses TNS. An example would be SQL*Net 2.3.3.
TNS community	A TNS community corresponds to what is typically called a network. It consists of several clients or nodes that fulfill the following conditions:

• Connected and can communicate using one common network transport protocol (regardless of media or distance)

• Run TNS-based products, such as SQL*Net 2.3.3

	Communities are given names, but because they are based on a single protocol they may also be referred to using phrases such as the TCP/IP community or the DECnet community.
TNS network/ application network	A TNS network (also called an application network) is a network that consists of one or more TNS communities running TNS-based products. A simple example is one TNS community in which two nodes are running SQL*Net Version 2.3.3. In the TNS networks, several protocol communities are connected by MultiProtocol Interchanges.
TNS client	A TNS client is an application that is a member of a TNS community and that is running TNS-based software such as SQL*Net Version 2.3.3. A TNS client may be either a requestor or a provider of a service.
Initiator	An initiator is a TNS client application that requests a connection to another client in a TNS network. Every TNS connection is originated by an initiator. An example is an Oracle Forms application that accesses an Oracle7 database using SQL*Net Version 2.3.3.
TNS connection	A TNS connection is an application-level connection between two TNS clients on the same TNS network. The initiator and destination can belong to the same TNS community or to different TNS communities. A TNS connection between two clients in the same community requires neither navigation nor an Interchange. A TNS connection that spans multiple communities requires an Interchange to navigate and establish the connection path. Figure 1 shows a logical TNS connection that spans three different transport protocol communities.
	Note: Multiprotocol Interchanges are not available on OpenVMS. However, TNS connections with OpenVMS at one or both ends may involve a Multiprotocol Interchange on a non-OpenVMS system.

Figure 1. TNS Connection

Connect descriptor	An initiator requests a TNS connection using a connect descriptor, which identifies the destination application and usually contains initial application connection information (such as a database system ID). Usually the connect descriptor is identified by a service name, a short alias for the connect descriptor. The connect descriptors and their corresponding service names are stored in the Oracle Names server for the network (if one exists) or in the TNSNAMES.ORA file.
Path	A path is the series of nodes traversed by a connection, beginning with the start point (the initiator) to the end point (the destination).

Related Publications

OpenVMS Publications

Product-Specific Publications

Customer Support Information

For Oracle Worldwide Customer Support Services (WCSS), contact your local number. (The hours are detailed in your support contract.) ___________________________________

Please prepare the following information before you call, using this page as a checklist:

• Your Customer Support Identification number (CSI) if applicable, or full contact details, including any special project information ____________________________

• The complete version numbers of the Oracle7 Server and associated products (for example, Oracle7 Server version 7.3.3 or Oracle Forms version 4.5.6.3.2) Note: The version numbers for products can be obtained from the file ORA_UTIL:PRODUCTS.TXT ____________________

• The hardware type on which the problem occurs (for example, Digital VAX) ______________

• The operating system name and version number (for example, OpenVMS 7.0) _______________

• Details of error codes and associated descriptions. Please write these down as they occur, since they are critical in helping WCSS to quickly resolve your problem. _________________________

• A full description of the issue, including:

• What - What happened? For example, the command used and result obtained.

• When - When did it happen? For example, time of day, or after a certain command, or after an O/S upgrade.

• Where - Where did it happen? For example, on a particular system or within a certain procedure or table.

• Extent - What is the extent of the problem? For example, production system unavailable, or moderate impact but increasing with time, or minimal impact and stable.

• Keep copies of any trace files, core dumps, and redo log files recorded at or near the time of the incident, since WCSS will need these to further investigate your problem.

• Error returned by the installation procedure and/or OpenVMS __________________________

Your Comments Are Welcome

[Contents] [Index] [Info] [Previous] [Next]