Oracle7 Getting Started for Windows NT

Library

Product

Contents

Index

Post-installation Tasks

The Starter Database
Configuring SQL*Net
Configuring Oracle Enterprise Manager
Configuring Oracle7 Spatial Data Option
Configuring ConText Option
Configuring Advanced Replication Option
Configuring Oracle Client Software Manager (OCSM)
Compiling and Linking Oracle XA Library
Implementing Multiple Oracle Homes (Windows 3.1 Only)

The Starter Database

During the installation process, you have the option of installing a starter database (default name ORCL) that is fully configured and ready for use after installation. There are two types of starter database you can choose to install:

Starter Database Type Provides You With...
Standard

A fully configured and ready-to-use database. The standard starter database provides read-only snapshot capabilities. A read-only snapshot is a full copy of a table, or a subset of a table, that reflects a recent state of a database.

Replication

A database with symmetric, update-anywhere replication capabilities (also referred to as updatable snapshots). All copies of data can potentially be updated, and ultimately all sites can have access to the same data. After installation, configure your database for this feature. See the section "Configuring Advanced Replication Option" for details.

If you wish to create your own database, refer to the chapter "Creating a New Database".

What Does Your Starter Database Include?

The Standard and Replication starter databases both contain:

Three User Accounts
Four Tablespaces
Four Data Files
One Initialization Parameter File
Two Redo Log Files
Two Control Files

Data Dictionary

Note The Replication starter database can take up to one hour to install and configure. Its SYSTEM tablespace is much larger than that of the Standard starter database as it contains a number of replication tables.

Additional Information See the appendix "Initialization Parameter Files" of this Getting Started. This appendix lists the Oracle7 Server for Windows NT-specific initialization parameters and their default values. For further information on initialization parameters see Oracle7 Server Reference Manual.

Redo Log Files

The starter database contains two redo log files located in the ORANT\DATABASE directory

Database Files Description
LOG1ORCL.ORA
LOG2ORCL.ORA

Redo log files hold a record of all changes made to data in the database buffer cache. If an instance failure occurs, the redo log files are used to recover the modified data that was in memory.

.

Additional Information See the chapters "Managing the Online Redo Log" and "Recovering a Database" of Oracle7 Server Administrator's Guide.

Control Files

The starter database contains two control files located in the ORANT\DATABASE directory.

Control Files Description
CTL1ORCL.ORA
CTL2ORCL.ORA

An administrative file that is required to start and run the database. The control file records the physical structure of the database. For example, a control file contains the database name, names and locations of the database's data files and redo log files.

Note Oracle Corporation recommends that you keep multiple control files (on separate physical drives) for each database and set the CONTROL_FILES initialization parameter to list each control file. See the chapter "Managing Control Files" of Oracle7 Server Administrator's Guide for information on setting this initialization parameter value.

Data Dictionary

The data dictionary is a read-only collection of tables and views containing reference information about the database, its structures, and its users. The data stored in the dictionary include:

Names of the Oracle7 Server users
Privileges and roles each user has been granted
Names and definitions of schema objects (tables, views, snapshots, indexes, clusters, synonyms, sequences, procedures, functions, packages and so on)
Integrity constraints
Space allocation for database objects
Auditing information, such as who accessed or updated various objects

Additional Information The chapter "The Data Dictionary" of Oracle7 Server Concepts Manual.

Configuring SQL*Net

Two configuration tools enable you to configure SQL*Net version 2.3 client and server database connections and create server and client configuration files. The tool you use depends upon the size and complexity of the network.

Configuration Tool Use for...
SQL*Net Easy Configuration

Simple database connections.
SQL*Net Easy Configuration is automatically installed when you select the Oracle7 Server Products, Oracle7 Client Products installation options or SQL*Net Server and SQL*Net Client from the Custom Installation option.

Oracle Network Manager

Complex networks, and advanced SQL*Net features such as Oracle Names and Advanced Networking Option.
Oracle Network Manager is a Windows 16-bit application that can be run on Windows NT, Windows 95 and Windows 3.1. You must install Oracle Network Manager using the Windows 3.1 Oracle Installer and not the SETUP.EXE file at the root of the CD-ROM disc.

Review the following guidelines before choosing either SQL*Net Easy Configuration or Oracle Network Manager:

Use either SQL*Net Easy Configuration or Oracle Network Manager; you cannot use both together.

Oracle Corporation strongly recommends that every machine in the workgroup network be configured with one, and only one, of the configuration utilities.

Additional Information See the chapters "Configuring the Network using SQL*Net" and "Understanding the Contents of the Configuration Files" of Oracle Network Products Getting Started for Windows Platforms.

Configuring Oracle Enterprise Manager

Additional Information Refer to Oracle Enterprise Manager Installation Guide for installation requirements and information on how to install Oracle Enterprise Manager.

The Oracle Enterprise Manager works with the Oracle Intelligent Agent to perform distributed database administration from a single console computer. The Oracle Enterprise Manager is installed on a console workstation, typically a Windows NT client. The Oracle Intelligent Agent is installed on each computer with an Oracle7 Server for Windows NT database to be managed. The Oracle Intelligent Agent is responsible for managing and completing tasks requested from the console workstation by the Oracle Enterprise Manager. Once installed, the Oracle Intelligent Agent:

listens for and responds to job requests initiated by the Oracle Enterprise Manager console workstation
schedules job requests (requests can include detecting and correcting abnormal conditions, performing standard database administration procedures, and monitoring events)
executes the job request

Configuration Tasks

Perform the following configuration tasks after installing the Oracle Enterprise Manager on a Windows NT client and the Oracle Intelligent Agent on your Windows NT server:

Each of these configuration tasks is described in the following sections.

Verify Oracle Services Are Started

Before configuring Oracle Enterprise Manager, ensure that the Oracle7 database services OracleServicesid and OracleStartsid are started on the client and server. Refer to the section "Managing Oracle Database Services" in the chapter "Administering a Database" of this Getting Started for information.

Start the Oracle Intelligent Agent

In order to use the Oracle Enterprise Manager, the Oracle Intelligent Agent must be started on your Windows NT server. The Oracle Intelligent Agent automatically locates the services on the computer where it resides and passes this information to the Oracle Enterprise Manager console.

Start the Oracle Intelligent Agent on the Windows NT server in either of two ways.

From the icon:

In the Control Panel window, choose the Services icon.
The Services dialog box appears. Look for the OracleAgent service. A blank in the Status column indicates that the service is not running.
Select the OracleAgent service and choose Start.
The agent is started.
Choose the Close button.

From the command line, enter:

net start OracleAgent

Create a Repository User Account

You need to have a user account with DBA (Database Administrator) privileges set up on the database where you want to create a repository. Oracle Enterprise Manager places its repository in the default tablespace of the user account to which you are connected when creating the repository. Because of this, Oracle Corporation recommends that you create a new user account so that the repository can be created in its own tablespace. It is also recommended that you create a new tablespace and the newly-created user be customized to use this tablespace as its default tablespace.

To create a repository user account on the Windows NT server:

Start Server Manager and connect to the Oracle7 database.
```
C:\> SVRMGR23
```
```
SVRMGR> CONNECT SYSTEM/MANAGER
```
Create a special tablespace for the Oracle Enterprise Manager repository.
```
SVRMGR> CREATE TABLESPACE reposit_tablespace DATAFILE 'datafile' SIZE x M;
```
where x is the tablespace size in megabytes.

Create a user account where the user's default tablespace is the newly-created tablespace:

SVRMGR> CREATE USER username IDENTIFIED BY password

SVRMGR> DEFAULT TABLESPACE reposit_tablespace;

Grant the SYSTEM privileges to this user account.

SVRMGR> GRANT DBA to username IDENTIFIED BY password;

When done, enter:
```
SVRMGR> EXIT
```
Exiting Server Manager closes the database connection.
Follow Steps 1-5 for additional repository user accounts.

Create an NT User Account

After a repository user account is created, an NT user account with the same user name as the repository user account must be created.

To create a user account on the Windows NT server:

Start the User Manager application:

If Using... Select the...
Windows NT 3.51

Accessories icon from the Windows NT Program Manager, then choose User Manager.

Windows NT 4.0

Administrative Tools folder from the Start icon in the Taskbar, then choose User Manager.

Choose New User from the User menu.
Enter the appropriate information in the dialog box:

a. Enter a user name that is the same as the one you entered in "Create a Repository User Account" in Username.

b. Enter the same password you entered in "Create a Repository User Account" in both Password and Confirm Password.
Click OK.
The user is added.
Select the newly created user and choose User Rights from the Policies menu.
The User Rights Policy dialog box appears.
Click the Show Advanced User Rights check box and select Log on as a batch job from the Right drop-down list box.
Select Users from the Grant To list box and click OK.
If Users does not exist, create it:

a. Choose Add.
The Add Users and Groups dialog box appears.

b. Select the names of the local host machine from the List Names From drop-down list box.

c. Choose User from the Names list box and choose Add.

d. Click OK.
Users appears in the Grant To list box.
Click OK.
Choose Exit from the User menu.
Repeat Steps 1-9 for any other repository user accounts you created.

Create TNSNAMES.ORA and TOPOLOGY.ORA

The TNSNAMES.ORA file (TOPOLOGY.ORA is optional) is required by Oracle Enterprise Manager:

TOPOLOGY.ORA

Includes configuration information used with Oracle Intelligent Agent versions to populate the Oracle Enterprise Manger Console Navigator tree.

TNSNAMES.ORA

Includes a list of service names (or databases aliases) of network databases mapped to connect descriptors.

SQL*Net Easy Configuration or Oracle Network Manager generates a TNSNAMES.ORA file and the Network Topology Generator generates or modifies the TOPOLOGY.ORA file.

To configure these files on the Windows NT client:

Ensure that the TNSNAMES.ORA file exists in the %ORACLE_HOME%\NETWORK\ADMIN directory on the console.
If not, create TNSNAMES.ORA using SQL*Net Easy Configuration or Oracle Network Manager. For this release of Oracle Enterprise Manager, the host name of the server in TNSNAMES.ORA must be entered in all uppercase letters in order for Oracle Enterprise Manager to recognize the host name.

Additional Information See the Oracle Network Products Getting Started for Windows Platforms for complete information on creating the TNSNAMES.ORA file.

Start the Network Topology Generator application:

If Using... Select the...
Windows NT 3.51

Network Topology Generator icon from the Oracle for Windows NT Program Group.

Windows NT 4.0

Oracle Enterprise Manager folder from the Start icon in the Taskbar, then choose Network Topology Generator.

The Oracle Network Topology Generator window appears.

Select TNSNAMES.ORA and click OK.
The SQL*Net Service Name List dialog box appears.
Click Write File to generate the TOPOLOGY.ORA file.
The Save As dialog box appears.
Ensure the directory is ORACLE_HOME\NETWORK\ADMIN and click OK.
Choose Exit from the SQL*Net Service Name List box to exit the Oracle Network Topology Generator.

Access Oracle Enterprise Manager and Create the Repository

Before you can use Oracle Enterprise Manager, you need a repository. The repository is a set of base tables in a database that contains status and environment information for your managed databases. A separate repository must be created for each user wanting to use Oracle Enterprise Manager. Create the Enterprise Manager repository in the same user account and database.

To create a repository on the Windows NT client:

Start Oracle Enterprise Manager:

If Using... Select the...
Windows NT 3.51

Oracle Enterprise Manager icon from the Oracle for Windows NT Program Group.

Windows NT 4.0

Oracle Enterprise Manager folder from the Start icon in the Taskbar, then choose Enterprise Manager.

The Oracle Enterprise Manager Repository Login Information dialog box appears.

Enter the following appropriate information and choose OK:
The Oracle Repository Manager and Oracle Enterprise Manager windows appear.

Discovering Network Services

The Oracle Enterprise Manager Console must discover network services, such as databases, listeners, and nodes, to populate the Oracle Enterprise Manager Navigator tree. In addition to discovery, the Oracle Enterprise Manager must also be able to manage these services for the Job Scheduling and Event Management systems. This can be achieved with the Discovery Wizard.

When the agent starts up and is explicitly requested by the Oracle Enterprise Manager with the Navigator Discovery feature, the agent passes information from the Oracle Enterprise Manager console to populate the Navigator tree.

To discover services:

Select Discovery -> Wizard from the Navigator menu.
The Auto Discovery Wizard appears.
Select Discover services immediately and choose Next.
Enter the server host name in the Node/IP field and choose Add.
The host name is added to the Selected list box.
Select Finish.
The Auto Discovery Status window appears. It changes from Pending to Discovered and the blue colored boxes changes to green, indicating the services are accessible from the Navigator Tree.
Select Close.
The Navigator Tree's object can now be viewed.

Stop the Oracle Intelligent Agent

Stop the Oracle Intelligent Agent on the Windows NT server in either of two ways.

From the icon:

In the Control Panel window, choose the Services icon.
The Services dialog box appears. Look for the OracleAgent service. A blank in the Status column indicates that the service is not running.
Select the OracleAgent service and choose Stop.
The agent is stopped.
Choose the Close button.

From the command line, enter:

net stop OracleAgent

Configuring Oracle7 Spatial Data Option

Perform these configuration tasks before using Oracle7 Spatial Data Option:

Start Server Manager at the command prompt:
```
C:\> SVRMGR23
```

Create an MDSYS user. For example,

SVRMGR> create user MDSYS identified by manager;

Connect to the database as SYSTEM/MANAGER:
```
SVRMGR> CONNECT SYSTEM/MANAGER
```

Grant the following privileges to the MDSYS user:

SVRMGR> grant all privileges to MDSYS identified by manager with admin option;

SVRMGR> alter user MDSYS quota unlimited on SYSTEM;

Use SQL*Plus to connect to the database as MDSYS/MANAGER.

Note You cannot use Server Manager to run CATMD.SQL.
Run the CATMD.SQL script. For example,
```
SQL> @C:\ORANT\RDBMS73\ADMIN\CATMD.SQL
```
This script creates the following:

Configuring ConText Option

Perform these configuration tasks before using ConText Option:

Start Server Manager at the command prompt:
```
C:\> SVRMGR23
```

Connect to the database as INTERNAL:

connect internal/password@connect string

Create a tablespace called DRSYS with size of at least 5 MB for the ConText Option objects. For example, using Server Manager as SYSTEM/MANAGER execute the following command.
```
SVRMGR> create tablespace DRSYS datafile 'c:\orant\database\drorcl.ora'

2> size 30M;
```
Exit Server Manager.
Go to the %ORACLE_HOME%\CTX73\ADMIN directory, start SQL*Plus and execute DRCRSYST.SQL.
```
SQL> @drcrsyst ctxsys ctxsys drsys drsys
```
This script creates the CTXSYS user with password CTXSYS and default tablespace of DRSYS. It also creates the CTXADMIN, CTXAPP and CTXUSER roles.
Execute the DR0INST.SQL script to load the data dictionary.
```
SQL> CTXSYS/CTXSYS @dr0inst
```
This loads the data dictionary and packages into user CTXSYS/CTXSYS.
Import the CTXSET.DMP file to import data into the data dictionary:
```
imp73 CTXSYS/CTXSYS file=ctxset.dmp full=y ignore=y
```
This imports data used by the linguistics services into CTXSYS/CTXSYS.
Execute the DRSYS.SQL script to install the patch for Oracle7 Server 7.3.2.
```
SQL> sys/your_sys_password @drsys
```
Add or check for the following line in your INITsid.ORA file if you want to use one-step queries in ConText Option.
```
TEXT_ENABLE = TRUE
```
Set the SHARED_POOL_SIZE initialization parameter to at least 9 MB when using the ConText Option.
Restart your database.

Additional Information See Oracle ConText Option QuickStart, Oracle ConText Option Administrator's Guide and Oracle ConText Option Messages.

ConText Option Demos

ConText Option demos are provided for the following products:

Product ConText Option Demos
SQL*Plus

Installed under %CTX73%\DEMO\CTXPLUS. Contains a README.TXT file and .SQL scripts for one-step, two-step, and other queries from SQL*PLUS.

Oracle Forms

Installed under %CTX73%\DEMO\CTXFORM. Contains a README.TXT file and .SQL scripts for one-step, two-step, and other queries from Oracle Forms.

Linguistics

Installed under %CTX73%\DEMO\CTXLING.

Additional Information Refer to the Oracle ConText Option Application Developer's Guide for further information on setting up and executing the demos applications.

Note The ConText Option Web Sample Application is not provided on Windows NT.

User Defined Filters

This section describes information specific to using user defined filters on Windows NT.

Oracle7 Server generic documentation states that user defined filters should be placed within the subdirectory /BIN under %ORACLE_HOME%\CTX. On Windows NT, user defined filters must be placed in the directory %ORACLE_HOME%\BIN.
On UNIX operating systems, Perl scripts and UNIX shell scripts can be executed as user defined filters. On Windows NT only .EXEs, .CMDs, and .BATs are executed as user defined filters.
To implement a filter on Windows NT, for example, to run a Perl script FOO.PL, associate files with a .PL extension with CCPERL.EXE (if you have a Perl compiler). When the ConText Option server process executes your FOO.PL user defined filter, it calls CCPERL.EXE FOO.PL input file output file.

Running ConText Option Server Processes on Windows NT

ConText Option servers can be started from the command prompt or the ConText Option control utility.

From the command prompt:

C:\> start CTXSRV73 -user CTXSYS <passwd for CTXSYS>@<conn string> -personality . . .

Using the ConText Option control utility:

C:\> CTXCTL73

command> start 1 [dml | ddl | load | ling | query]

ConText Option server processes started from the command prompt are killed by Windows NT when the logged on console user logs off the Windows NT console.

To help ConText Option servers survive Windows NT console logoffs, use the ConText Option control utility CTXCTL73.EXE to start, stop and view the ConText Option servers running on the Windows NT server/workstation.

The ConText Option control utility interacts with a Windows NT service for the ConText option. It is this service that manages the various ConText Option server processes on that Windows NT server/workstation. The service is called OracleConTextService73 and must be started prior to using the ConText Option control utility. By default the service starttype is AUTO.

The ConText Option control utility cannot list or kill ConText Option servers started directly by executing CTXSRV73.EXE or CTXSRX73.EXE. It can only manage ConText Option servers through the OracleConTextService73 Windows NT service.

Configuring Advanced Replication Option

Refer to the Oracle7 Server for Windows NT CD-Insert for Advanced Replication Option installation requirements.

Additional Information There are many configuration and usage possibilities with the Advanced Replication Option. For more information about advanced replication, see:

Oracle7 Server Distributed Systems, Volume I: Distributed Systems
Oracle7 Server Distributed Systems, Volume II: Replicated Data
Oracle7 Server Concepts
Oracle7 Server Administrator's Guide

Tablespace Requirements

These are the recommended tablespace requirements for the Advanced Replication Option:

Tablespace Requirement
SYSTEM

At least 20 MB of free space is required for replication packages. Replication triggers and procedures are stored here.

ROLLBACK SEGMENTS

Rollback Initial Extent = 50 KB

Rollback Next Extent = 50 KB

ROLLBACK

At least 5 MB of free space.

TEMPORARY

At least 10 MB of free space.

USER

User specific.

Initialization Parameters

The following initialization parameters must be set or added to the INITsid.ORA file (recommended values are included).

Note These parameters are already set if you choose to install the Replication starter database.

Master Site

Add these initialization parameters to the master site.

Parameter Name Recommended Value
SHARED_POOL_SIZE

At least 10 MB

DISTRIBUTED_LOCK_TIMEOUT

300 seconds

DISTRIBUTED_TRANSACTIONS

5

GLOBAL_NAMES

TRUE

OPEN_LINKS

4

PROCESSES

Add 9 to current value

JOB_QUEUE_PROCESSES

2 (depends on number of n-way sites)

JOB_QUEUE_INTERVAL

10 seconds

JOB_QUEUE_KEEP_CONNECTIONS

FALSE

Snapshot Site

Add these initialization parameters for snapshot sites.

Parameter Name Recommended Value
SNAPSHOT_REFRESH_PROCESSES

2

SNAPSHOT_REFRESH_INTERVAL

60 seconds

SNAPSHOT_REFRESH_KEEP_CONNECTIONS

FALSE

Configuration Tasks

Note If you have installed the Replication starter database there is no need to perform the following configuration tasks.

Perform these configuration tasks before using Advanced Replication Option:

Start Server Manager at the command prompt:
```
C:\> SVRMGR23
```
Connect to the database as INTERNAL/password.
Execute the script CATREP.SQL once the database has started.
This script is found in the %ORACLE_HOME%\RDBMS73\ADMIN directory. It takes approximately one hour to run. A good idea is to spool output to a log file first before running CATREP.SQL.
a. Enter the following command:
```
SVRMGR> SPOOL output
```
This creates a file called OUTPUT.LOG to which to output all on-screen activity while the SPOOL session is open.
b. Close the SPOOL command by entering OFF when the script completes running:
```
SVRMGR> SPOOL OFF
```
OUTPUT.LOG is placed in the directory from which Server Manager was invoked.
Confirm that CATREP.SQL ran correctly by running a query on ALL_OBJECTS where STATUS = 'INVALID'. For example,
```
SVRMGR> SELECT * FROM ALL_OBJECTS WHERE STATUS = 'INVALID';
```
If you find that any of the package bodies compiled incorrectly, recompile them manually.
```
SVRMGR> ALTER PACKAGE <package name> COMPILE BODY;
```
If CATREP.SQL has run successfully, a number of replication tables are created in the SYSTEM tablespace. The database is now set up for advanced replication.
Refer to the generic documentation for details on setting up:

Data Dictionary Tables

The practical limit as to the number of master sites an environment may have is 10. The SNP0 to SNP9 processes each handle one destination master at a time.

If you use the Advanced Replication Option and intend to set up a large number of replicated objects, monitor the following data dictionary tables with the SQL SELECT command:

SOURCE$
IDL_UB1$
IDL_UB2$
I_SOURCE1I
ARGUMENT$
I_ARGUMENT1
IDL_SB4$
IDL_CHAR$
TRIGGER$

If necessary, increase the storage parameters to accommodate the storage requirements of large numbers of replicated objects.

Configuring Oracle Client Software Manager (OCSM)

OCSM is bundled in the Oracle Windows Installer. It enables System Administrators to install and configure Oracle products on a server for access by multiple client workstations. Installation is centralized, and updates to software on client workstations are automatic.

OCSM is a 16-bit application that manages Windows 3.1 products. You can run OCSM on Windows NT and Windows 95 to manage Windows 3.1 products, however, it does not manage 32-bit products.

Oracle Installer for Windows provides the basic services for setting up the OCSM directory and loading the following software on the server:

Oracle Client Software Administrator--allows a System Administrator to configure users' access to Oracle software.

Oracle Client Software Agent--loaded on clients, the agent monitors the server for changes and automatically configures the clients to reflect these changes.

Note This release of OCSM has been tested with Microsoft networks, Windows 3.1, Windows 95, Windows NT 3.51 or 4.0 (Workstation and Server), NetWare Server versions 3.x and 4.x, and NetWare Client Requestors versions 3.12, 3.32, and 4.0.

Note The included versions of Oracle Objects for OLE and the Oracle ODBC Driver are not OCSM-compliant. If you want to take advantage of the shared-installation feature of Oracle Installer, do not attempt to share-install Oracle Objects for OLE or the Oracle ODBC Driver.

Note On Windows NT version 4.0, the Oracle ODBC Driver 32-Bit ODBC Release Notes item in the Oracle for Windows NT program group may not launch correctly on some Windows NT 4.0 systems. This is because in some cases the correct location for the WRITE.EXE program is not specified in the item shortcut. If you have this problem, change the properties for the 32-Bit ODBC Release Notes item so that the shortcut points to the correct location for the WRITE.EXE program.

Configuration Options

Client personal computers can be configured to run Oracle client software installed in shared directories with several options. These options are configured within each of the user configurations and are applied to all the users in the configuration. The options are:

Configuration Option Description
Available products

Users are assigned to configurations, each with a set of associated products. Users can access the products associated with their configurations.

Allow users to choose products

Users are not required to use all products in the product configuration determined by the System Administrator.

Decide executable location

A client may use a shared product as:

Shared--shared pool of products runs directly off the server.

EXE/DLL Download--executables and DLLs of the shared product are downloaded to the client machine in order to improve performance.

Full Download--complete installation of the shared product on the client machine. A client can use shared products even if the network server connection is terminated.

Conflict resolution

Tells the administration utility and client agents how to resolve parameter conflicts that can occur when a user is in two different configurations.

Additional Information See the Oracle7 Server for Windows NT CD-ROM Insert for information on OCSM system requirements and installation instructions.

Compiling and Linking Oracle XA Library

The Oracle XA Library is automatically installed as part of the Oracle7 Server Products installation option. The following components are created in your Oracle Home directory:

Component Location
XA73.DLL

%ORACLE_HOME%\BIN

XA73.LIB

%ORACLE_HOME%\RDBMS73\XA

XA.H

%ORACLE_HOME%\RDBMS73\XA

The XA Application Program Interface (API) is typically used to enable an Oracle Relational Database Management System (RDBMS) to interact with a transaction processing monitor (TP monitor), such as BEA Tuxedo, IBM Transarc Encina, or IBM CICS. You can also use TP monitor statements in your client programs. The use of the XA API is also supported both from Pro*C and from Oracle Call Interface (OCI). In either case, the XA73.DLL must be contained in the execution path of the caller.

To compile and link a Pro*C program:

Pre-compile PROGRAM.PC using Pro*C to generate PROGRAM.C.
Compile PROGRAM.C, making sure to include %ORACLE_HOME%\XA73 in your path.
Link PROGRAM.OBJ with the following libraries:
Run PROGRAM.EXE. (XA73.LIB will make the function calls to XA73.DLL)

To compile and link an OCI program:

Compile PROGRAM.C by using MS VC++, making sure to include %ORACLE_HOME%\XA73 in your path.
Link PROGRAM.OBJ with the following libraries:
- XA73.LIB
- ORA73.LIB

Run PROGRAM.EXE.

Additional Information For general information about XA and TP monitors please see:

Distributed Transaction Processing: The XA Specification published by X/Open, (now part of OpenGroup). Visit: http://www.rdg.opengroup.org/public/pubs/catalog/full_lst.htm
Transaction Processing XPG4 X/Open CAE Specification XO/CAE/91/300 or C193 2/92
Your specific TP monitor documentation

Additional Information For more information about the Oracle XA Library, see the appendix "Operating System Dependencies" of Oracle7 Server Distributed Systems, Volume I: Distributed Systems.

Implementing Multiple Oracle Homes (Windows 3.1 Only)

The Oracle Installer version included on your CD-ROM disc allows you to maintain more than one Oracle Home on a single machine and to switch between Oracle Homes. When you install the Oracle7 Server for Windows NT, a top-level directory called Oracle Home is created on your hard disk. By default, the Oracle Home directory for:

Oracle 32-bit Windows NT products is \ORANT
Oracle 32-bit Windows 95 products is \ORAWIN95

Oracle 16-bit Windows 3.1 products is \ORAWIN

Note The capability of switching between Oracle Homes is currently supported on Windows 3.1 but not on Windows 95 or Windows NT.

Note Before you create another Oracle Home ensure you have installed Oracle Installer version 3.1.4.1.3 into an existing Oracle Home if it is not already installed. All of your Oracle Homes must have this version of the Oracle Installer or you will not be able to switch between Oracle Homes successfully.

WARNING Do not use the 32-bit Switch Homes because it can render all Oracle 32-bit installations unusable.

Create Another Oracle Home

To create an additional Oracle Home directory, follow these steps:

Run the Oracle Installer from the CD-ROM disc.
Enter a different directory path for the additional Oracle Home in the Oracle Installation Settings dialog box.
Each time you create another Oracle Home, you are prompted by the Oracle Installer to update the PATH variable in your AUTOEXEC.BAT file. You also need to restart Windows 3.1.
Install Oracle Installer version 3.1.4.1.3 and any other products you wish to install into this new Oracle Home.
Your machine will be configured to use this new Oracle Home.

Switch Between Oracle Homes

To switch between Oracle Home directories, follow these steps:

Run the Oracle Installer from the CD-ROM disc.
Select the Switch Homes icon from the Oracle for Windows Program Group.
Select the Oracle Home you want to use from the Oracle Home Selection dialog box.

When the Oracle Installer completes switching Oracle Homes, the Software Asset Manager appears, displaying a list of products installed in your Oracle Home.

Each time you switch between Oracle Homes, the Oracle Installer updates the PATH in your AUTOEXEC.BAT file and you will need to restart Windows 3.1.

Note Only one Oracle Home is active at a time, therefore, if you install one product into one Oracle Home and another into a different Oracle Home, you will not be able to use both of these products at the same time.

Prev Next