1 Getting Started

1.1.1 Generating the Environment-Definition File

You must generate an ORAENV file prior to using Oracle Database for the first time. Perform the following steps to generate an ORAENV file:

1. Call the INSTALL.P.USER procedure by entering the following command:

   /CALL-PROCEDURE $ORAC1020.INSTALL.P.USER
   

   where $ORAC1020 is the name of Oracle Database 10g release 2 (10.2) installation user ID.

   You are prompted for the database system identifier, known as the sid.

2. Enter the sid. If you do not know what the sid is, consult the database administrator.

1.1.2 Calling the Environment-Definition File

Call the ORAENV file supplied (sid.P.ORAENV) by entering the CALL-PROCEDURE command on the ORAENV file. For example, to call the example ORAENV file for the database DEMO, enter the following command:

/CALL-PROCEDURE DEMO.P.ORAENV

1.1.3 Specifying the Environment Variables

The following is the content of the ORAENV file available with Oracle Database:

/SET-PROC-OPT DATA-ESCAPE=*STD                                    
/DECL-PAR (SYSCMD(INI-VAL='DEMO.P.ORAENV'))
/       REMARK * SYSCMD must be name of this file
/       WRITE-TEXT '                                            '
/       WRITE-TEXT ' +----------------------------------------+ '
/       WRITE-TEXT ' I  Oracle Database 10g Release 2 (10.2)  I '
/       WRITE-TEXT ' I           environment setup            I '
/       WRITE-TEXT ' +----------------------------------------+ '
/       WRITE-TEXT '                                            '
/       SET-FILE-LINK ORAENV,&SYSCMD
/       SET-FILE-LINK ORALOAD,$ORAC1020.ORALOAD.LIB
/       SET-FILE-LINK ORAMESG,$ORAC1020.ORAMESG.LIB
/&*     MOD-SDF $ORAC1020.SYSSDF.ORACLE.USER
/&*     *** if SYSOUT protocol is desired set BGJOUT='KEEP' ***
/&*     SET-VAR BGJOUT='DEL'
/       EXIT-PROCEDURE
**  parameters for users:
*
ORAUID=/BS2/$ORAC1020
ORASID=DEMO
NLS_LANG=German_Germany.D8BS2000
* PRINTPAR=
/END-PROCEDURE

If you wish, you can change Oracle Database 10g release 2 (10.2) working environment by editing the user variables in this file. The Appendix B, "ORAENV Variables" contains a list of the variables you can specify in the ORAENV file. The values you assign to user variables are specific to your task only. The database administrator can also set other variables that affect the whole database instance. If you try to set values for the DBA-specific variables in the ORAENV file, then they are ignored.

1.5.1 Default Connections

If you do not specify a connection string, then the environment variable DEFAULT_CONNECTION, if set, is used to establish the Oracle database connection. Refer to Appendix B, "ORAENV Variables" for more information on the ORAENV file and the DEFAULT_CONNECTION environment variable.

1.5.2 Connecting to the Oracle Database

Access to a local or remote database is done through Oracle Net Services. Use the Oracle Net Services logon string to identify the following for accessing a local or remote database:

• Protocol to be used

• Database you want to access

• Type of server (whether dedicated or shared) you want to use

The Oracle Net Services logon string has the following structure:

/START-PROGRAM $ORAC1020.SQLPLUS
* userid/password@service_name

where:

service_name specifies a service name entered in the TNSNAMES.ORA file that identifies the TNS connect descriptor for the desired database. If you are not sure of what you should enter here, then contact the database administrator.

The following example logon string that connects to a database defined in the TNSNAMES.ORA file as SERVERX:

HR/HR@SERVERX

For information on connecting to the Oracle Database using the Bequeath adapter, refer to the "Oracle Net Services" chapter in Oracle Database Installation and Administration Guide for Fujitsu Siemens BS2000/OSD.

1.6.1 Text Files

Textual data is usually stored in SAM or ISAM files; each record is taken to be one text line. Examples are the SQL script files used by SQL*Plus and spool output files.

SQL*Loader input data is provided as SAM or ISAM files. These files may also contain non-printable data, such as packed decimal or binary integer values. For ISAM files, the key at the beginning of the record is generally ignored.

1.6.2 Binary Files

Binary data is usually stored in PAM files.

1.6.3 Generic Oracle Database File Name Syntax

The convention used in generic Oracle Database documentation represents file names as two parts separated by a period, as in LOGIN.SQL. This syntax is correct for BS2000. However, as there is no "current directory" concept in BS2000, you have to add a prefix to the generic example names to get a full BS2000 file name.

1.6.4 Default File Name Extensions

Under BS2000/OSD, the Oracle Database utilities add default extensions to file names only when the last component of the specified file name is longer than three characters, or when only one component is specified, as shown in the following table.

This is similar to the file naming conventions used with Oracle Database on a UNIX system.

1.6.5 Using Link Names

Instead of specifying a file name, in special cases, you can also refer to the LINKNAME of a previously issued BS2000 /FILE command by using the syntax link=linkname in places where a file name is requested. In this way, you can override default file attributes, preallocate file space, and so on. There are a few exceptions where the link=linkname notation cannot be used.

1.6.6 Fixed Link Names

Oracle Database 10g release 2 (10.2) for BS2000/OSD also assumes fixed link names for certain files whose names cannot be specified.

The most important of these are as follows:

Typically, you set these link names by running the ORAENV procedure.