Oracle® Database User's Guide 11g Release 2 (11.
Oracle Database User's Guide, 11g Release 2 (11.2) for Fujitsu BS2000/OSD E27507-02 Copyright © 2007, 2012, Oracle and/or its affiliates. All rights reserved. Primary Author: Tanvee Ravi Contributing Author: Janelle Simmons This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.
Contents Preface ................................................................................................................................................................. ix Audience....................................................................................................................................................... Documentation Accessibility .....................................................................................................................
2.2.2.2 2.3 2.3.1 2.3.2 2.3.2.1 2.3.2.2 2.3.2.3 2.4 2.4.1 2.5 2.5.1 2.6 3 Running SQL*Plus ...................................................................................................................... SQL*Plus User Profiles........................................................................................................ The GLOGIN.SQL Global Startup File ...................................................................... The LOGIN.SQL User Startup File ...................................
.2.2.2 5.2.2.3 5.2.3 5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.4 5.4.1 5.4.2 5.4.3 5.4.4 5.4.5 5.5 5.5.1 5.5.2 5.6 5.6.1 5.6.2 6 Using the Oracle Database Under openUTM 6.1 6.1.1 6.1.2 6.1.3 6.1.4 6.1.5 6.1.6 6.1.7 6.1.8 6.2 6.2.1 6.2.2 6.2.3 6.2.4 7 User-Specific Configuration Files............................................................................... 5-4 Input, Output, and List-files .......................................................................................
7.5 7.6 Location of Message Files .......................................................................................................... 7-4 Linguistic Definitions ................................................................................................................. 7-4 A Oracle Error Messages for BS2000/OSD B Oracle Environment Variables B.1 B.2 B.2.1 B.2.2 B.2.3 B.2.4 B.2.5 B.3 B.3.1 B.3.2 B.3.3 B.3.4 B.3.5 B.3.6 B.3.7 B.3.8 B.3.9 B.3.10 B.3.11 B.3.12 B.4 B.4.1 B.4.2 B.4.3 B.4.4 B.4.
B.5.4 TNS_UPDATE_IPNODE ...............................................................................................
viii
Preface This manual, with the Oracle Database Installation and Administration Guide for Fujitsu BS2000/OSD, forms the system-specific component of a set of manuals which document installation, maintenance, and use of the Oracle Database 11g Release 2 (11.2). General information about the Oracle Database for all operating systems is contained in the Oracle Database documentation set.
Using Oracle Database Documentation The Oracle Database products that run under BS2000/OSD are identical, in the way in which they are supported, to the Oracle Database products that run under any other operating system. However, because of the diversity of operating systems, the use of applications may differ slightly between different operating systems.
Typographic Conventions The following text conventions are used in this manual: 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 Name Symbol single quotation mark '
1 1 Getting Started This chapter provides the BS2000/OSD-specific information that you must use with Oracle Database 11g Release 2 (11.2) for Fujitsu BS2000/OSD.
The Oracle Database Environment-Definition File /CALL-PROCEDURE $ORAC1120.INSTALL.P.USER where $ORAC1120 is the name of Oracle Database 11g Release 2 (11.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, then consult the database administrator. 1.1.2 Calling the Environment-Definition File Call the ORAENV file (sid.P.ORAENV) by entering the CALL-PROCEDURE command on the ORAENV file.
Starting Oracle Utilities with BS2000 SDF commands You can create an individual ORAENV file for each database with which you work. To set the environment variables, call the ORAENV file containing the environment variables for the database you want to use. Note: 1.2 The ORALOAD Library The ORALOAD library ($ORAC1120.ORALOAD.LIB by default) is required for starting Oracle Database 11g Release 2 (11.2) programs. Oracle Database uses this library to dynamically load executables when required.
Starting Oracle Utilities in UNIX-Style /START-EXECUTABLE ($ORAC1120.ORALOAD.LIB,program_name) For example, if you want to start SQL*Plus, then enter the command: /START-EXECUTABLE ($ORAC1120.ORALOAD.LIB,SQLPLUS) 1.
Starting Oracle Utilities in the POSIX environment Set the variable ORACLE_SID to start an Oracle utility for a specific Oracle instance. Additional instance-specific parameters that are defined in the related BS2000 ORAENV file, may be set in the POSIX environment or by accessing the BS2000 ORAENV file. Utilities running in the POSIX shell provide the opportunity to read instance-specific variables from the ORAENV file in the BS2000 file system.
Connecting to an Oracle Instance $ SQL> connect / as sysdba 1.
Using BS2000 Files for Input and Output 1.7 Using BS2000 Files for Input and Output In most cases, Oracle Database for BS2000/OSD programs use the functions of the C-BS2000 run-time system to access their input and output files. Oracle Database programs can read and write SAM, ISAM, and PAM files. 1.7.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.
Using BS2000 Files for Input and Output Note: When using the link=linkname notation, default file name extensions do not work. As a result, file name defaults derived from such notation are not valid, and you have to provide explicit names in such cases. For example, when working with SQL*Loader, if you specify link=linkname for the SQL*Loader control file, then you must provide explicit names for the BAD, LOG, and DISCARD file names.
2 2 Oracle Database Utilities This chapter describes how you start the following Oracle Database utilities: ■ SQL*Loader ■ The Export Utility ■ The Import Utility ■ The Data Pump Export Utility ■ The Data Pump Import Utility ■ Oracle Text Loader For a more detailed discussion of these utilities, refer to Oracle Database Utilities. 2.1 SQL*Loader SQL*Loader is a tool used for moving data from an external file (or files) into the tables of an Oracle database.
The Export Utility START-PROGRAM $ORAC1120.SQLPLUS * SCOTT/password SQL> START $ORAC1120.RDBMS.DEMO.ULCASE1 This example sets up the table for the user SCOTT to run the demonstrations. Note: 2. Start SQL*Loader to run the demonstration by entering the following command: /START-PROGRAM $ORAC1120.SQLLDR * SCOTT/password $ORAC1120.RDBMS.DEMO.ULCASE1 ULCASE1 ULCASE1 2.2 The Export Utility The Export utility is used to write data from an Oracle Database into the BS2000 system files.
The Import Utility When exporting a large volume of data, the default disk-space allocation for the output file will be inappropriate, and the program will spend a significant amount of time allocating secondary extents of disk space. If the maximum number of extents exceeds the number that the catalog entry can hold, then an output-file error will occur. As a counter-measure, you should always preallocate the EXP output file with the BS2000 /FILE command, prior to starting the Export utility.
The Data Pump Export Utility 2.3.1 Starting the Import Utility To start the Import utility, IMP, enter the following command: /START-PROGRAM $ORAC1120.IMP * SCOTT/password [options] If you omit the SCOTT/password parameters, then you are prompted for them. 2.3.2 Importing from Foreign Systems This section gives you some guidelines on importing data from non-BS2000 systems. 2.3.2.
Oracle Text Loader /START-PROGRAM $ORAC1120.EXPDP * username/password [options] Data Pump Export dump files are created by EXPDP as PAM files with BLKSIZE=(STD,2). When you try to use an export file from BS2000 as an import file on an ASCII platform, use as transfer utility FTP on BS2000 side and indicate the parameter binary. Note: If you start EXPDP in UNIX-Style and use interactive-command mode [K2] key, then the parameters must be specified when you are prompted for them and not on the command line.
Oracle Text Loader 2-6 Oracle Database User's Guide
3 3 SQL*Plus SQL*Plus is a general purpose utility used for running SQL commands and PL/SQL blocks, perform database administration, and so on. This chapter describes how you use SQL*Plus under BS2000/OSD. It supplements the SQL*Plus User's Guide and Reference with information about the following topics: ■ Running SQL*Plus ■ Specifying the Search Path for SQL*Plus Command Files ■ Sample Schemas and SQL*Plus ■ SQL*Plus Limits ■ Using SQL*Plus in the POSIX environment 3.
Running SQL*Plus 3.1.1.1 The GLOGIN.SQL Global Startup File The global startup file GLOGIN.SQL begins whenever any user starts SQL*Plus. This file can contain SQL statements or SQL*Plus commands to be run at the beginning of the SQL*Plus session. The GLOGIN.SQL file is located under the $ORAC1120 user ID, and its name is $ORAC1120.SQLPLUS.ADMIN.GLOGIN.SQL. The database administrator may customize the GLOGIN.SQL file if required. The GLOGIN.SQL file will be run regardless of the current user ID. 3.1.1.
Running SQL*Plus When you press the INTERRUPT key [K2], the Oracle Database stops retrieving rows and returns you to the SQL*Plus command level. If you issue an INTERRUPT when input is requested, then you must answer this request before the processing can be interrupted. However, this answer will be ignored. Note: 3.1.4 Issuing BS2000 Commands from SQL*Plus The SQL*Plus HOST command and the $ command enable you to enter a BS2000 command while you are logged on to SQL*Plus.
Specifying the Search Path for SQL*Plus Command Files You can also use the EDIT command to edit a SQL file by specifying the SQL file in the EDIT command. For example, if you enter the following command, then the editor EDT is called to edit the LOGIN.SQL file. Note that you can omit the default file name extension .SQL. SQL> EDIT login[.SQL] Refer to the SQL*Plus User's Guide and Reference for more details about the SQL EDIT command. 3.1.
Using SQL*Plus in the POSIX environment SQL> START filename If this file cannot be found, then SQL*Plus searches the paths specified by the ORAENV environment variable SQLPATH. This variable is used to specify one or more file name prefixes separated by a semicolon (;), which should be applied when searching for the command file.
Using SQL*Plus in the POSIX environment ■ Running Shell Commands From SQL*Plus ■ Using an Editor in SQL*plus 3.5.1 Starting SQL*Plus You can start SQL*Plus in the POSIX shell. Refer to "Starting Oracle Utilities in the POSIX environment" for more information about running SQL*Plus in the POSIX shell. 3.5.2 Running Shell Commands From SQL*Plus The SQL*Plus HOST command enables you to enter a POSIX shell command, while you are logged on to SQL*Plus.
4 4 PL/SQL PL/SQL is an extension to the SQL language and is used to create, store, modify, retrieve, and manage information in an Oracle database. This chapter supplements the Oracle Database PL/SQL Language Reference, with operating system-specific information about the PL/SQL demonstrations. See your database administrator if the PL/SQL demonstrations have not already been loaded. 4.1 PL/SQL Demonstrations The PL/SQL demo scripts do not specify fully qualified file names when including other scripts.
PL/SQL Demonstrations To run these demos, you must first build the demo tables with PLSQL.DEMO.PLS-EXAMPBLD.SQL and load them with PLSQL.DEMO.PLS-EXAMPLOD.SQL (under any user ID). The following example shows how to do this and run PLS-SAMPLE1: /START-PROGRAM $ORAC1120.SQLPLUS * user/password SQL> @PLS-EXAMPBLD SQL> @PLS-EXAMPLOD SQL> @PLS-SAMPLE1 4.1.2 PL/SQL Demos for Precompilers The demos for the precompilers are as follows: PLSQL.DEMO.PLS-EXAMP9.PC PLSQL.DEMO.PLS-EXAMP10.PC PLSQL.DEMO.PLS-SAMPLE5.
5 5 Programmatic Interfaces This chapter provides BS2000/OSD-specific information that supplements the documentation for the individual precompilers (such as Pro*C), and host language calls (Oracle Call Interface). It includes information about the following topics: ■ Overview ■ Building and Running a Programmatic Interface Application ■ Pro*C/C++ ■ Pro*COBOL ■ The Oracle Call Interface ■ The Object Type Translator 5.
Building and Running a Programmatic Interface Application ■ Pro*COBOL (COBOL85 and COBOL2000) OCI C and OCI COBOL programs cannot be combined together; any attempt to do so results in execution errors. The entries into the Oracle Database used by OCI C and OCI COBOL (for example, OLOGON) have identical names but different argument lists (for OCI COBOL, all arguments are by reference, that is, the parameter list contains all pointers, whereas for OCI C, the numeric arguments are by value).
Building and Running a Programmatic Interface Application 7. You can find sample files in the installation user ID: $ORAC1120.P.PROC, $ORAC1120.P.PROCOB and $ORAC1120.P.PROLNK . Figure 5–1 illustrates the sequence of events outlined in the preceding numbered list and how the programmatic interfaces make use of the program libraries. Figure 5–1 Usage of Program Libraries by Programmatic Interfaces 5.2.1 Existing Applications Existing Applications must be pre-processed, compiled and linked anew. 5.2.
Building and Running a Programmatic Interface Application When you use LMS library elements, the element name you specify must be the full element name including the suffix. Pro* does not append the suffix to the element name. 5.2.2.1 Include Files All standard include files are shipped in the LMS library, $ORAC1120.PRO.INCLUDE.LIB. You must enter either this library or a user-defined include library for EXEC SQL INCLUDE statements using the INCLUDE precompiler option as follows: * INCLUDE=$ORAC1120.PRO.
Pro*C/C++ You must use brackets when specifying the appropriate element. Note: In the following example, Pro*C generates a BS2000-ISAM-output file called SAMPLE.C as the ONAME option has been omitted: * INAME=INPUT.LIB[SAMPLE.PC] \ * LNAME=LIST.LIB[SAMPLE.LST] 5.2.3 Additional Remarks The following are additional remarks on this release of Oracle Database 11g Release 2 (11.2) for Fujitsu BS2000/OSD. ■ ■ ■ Only compilers and compiler versions supporting the ILCS Standard Linkage are supported.
Pro*COBOL $ORAC1120.C.DEMO.*.PC $ORAC1120.UTM.DEMO.*.PC $ORAC1120.CONFIG.PCSCFG.CFG An example of a compilation and precompilation procedure is included in the Oracle Database Software under the name $ORAC1120.P.PROC. 5.3.3 SQLLIB Calls If you want to code explicit C calls to SQLLIB functions, then you must call SQ2XXX instead of SQLXXX. For example, call SQ2CEX instead of SQLCEX. 5.3.4 Linking Pro*C To link a Pro*C program, you need: ■ ■ The Common Run-Time Environment, CRTE.
Pro*COBOL Before precompiling After precompiling COB-LABEL1. COB-LABEL1 . . . . EXEC SQL.... SQL-LABEL1. . . . . COB-LABEL2. COB-LABEL2. Before precompiling, the statement PERFORM COB-LABEL1 runs the code in paragraph COB-LABEL1 until the COB-LABEL2 heading is reached. However, the precompiler generates a paragraph heading, SQL-LABEL1, for the code generated from the EXEC SQL statement.
The Oracle Call Interface Note: The PROCOB option MAXLITERAL defaults to 180, not 256, as shown in the Pro*COBOL Programmer's Guide. The option FORMAT=TERMINAL is not supported. 5.4.2 Pro*COBOL Include, System Configuration, and Demo Files The Pro*COBOL include files, demo files, and system configuration file are shipped under: $ORAC1120.PRO.INCLUDE.LIB $ORAC1120.COBOL.DEMO.*.PCO $ORAC1120.UTM.DEMO.*.PCO $ORAC1120.CONFIG.PCBCFG.
The Oracle Call Interface COBOL programming languages. OCI calls are fully described in the Oracle Call Interface Programmer's Guide. For restrictions refer to "Known Problems, Restrictions and Workarounds" in Oracle Database Installation and Administration Guide for Fujitsu BS2000/OSD. The precompiler products from Oracle offer a higher level interface to the Oracle Database. One precompiler call is translated to several OCI calls.
The Object Type Translator 5.6 The Object Type Translator This section discusses port-specific notes for using the Object Type Translator. 5.6.1 Starting Ott As the Object Type Translator is based on Java it can only be started in the POSIX environment. You must use the JDBC Thin driver to connect to the database.
6 6 Using the Oracle Database Under openUTM This chapter describes the Oracle Database-specific points that you should consider when using Oracle Database 11g Release 2 (11.2) for BS2000/OSD under openUTM (Universal Transaction Monitor). The following topics are discussed in this chapter: ■ SQL Operations ■ UTM Operations 6.1 SQL Operations UTM application program units must use embedded SQL. Calls to the Oracle Call Interface (OCI) are not allowed. 6.1.
UTM Operations which will wait until input comes from the terminal, or to assign the same TACCLASS to subsequent programs after a PEND PA or PR. 6.1.6 Dynamic SQL You may use dynamic SQL as described in Oracle Database Programmer's Guide to the Oracle Precompilers. 6.1.7 PL/SQL COMMIT, ROLLBACK, CONNECT, and SAVEPOINT statements are not allowed in PL/SQL programs running under UTM. 6.1.
7 7 Globalization Support This chapter describes the globalization support available with Oracle Database 11g Release 2 (11.
Supported Language Conventions 7.1.2 Other Oracle Database Products For the supported Oracle Database products, you can choose a language, territory, and character set from within BS2000/OSD by setting the value of the ORAENV variable NLS_ LANG. Set this environment variable as follows: NLS_LANG = language_territory.characterset Where, language is any supported language territory is any supported territory characterset is the character set required by your terminal For example: NLS_LANG=German_Germany.
Supported Character Sets ■ Denmark: denmark ■ Finland: finland ■ France: france ■ Germany: germany ■ Hungary: hungary ■ Italy: italy ■ The Netherlands: the netherlands ■ Norway: norway ■ Poland: poland ■ Portugal: portugal ■ Spain: spain ■ Sweden: sweden ■ CIS: CIS ■ Slovakia: slovakia ■ Turkey: turkey ■ United Kingdom: united kingdom 7.4 Supported Character Sets Oracle Database 11g Release 2 (11.
Location of Message Files Name Description Usage CE8BS2000 Siemens Central European (= EBCDIC.DF.04-2 8-bit ISO 8859/2) WE8BS2000E Siemens EBCDIC.DF.04-F 8-bit West European with Euro symbol (= ISO 8859/15) The character sets WE8BS2000, CL8BS2000, WE8BS2000L5, EE8BS2000, CE8BS2000, and WE8BS2000E are the recommended database character sets. The other character sets should only be used as client character sets.
A A Oracle Error Messages for BS2000/OSD This appendix lists the messages of Oracle Database 11g Release 2 (11.2) for Fujitsu BS2000/OSD together with possible causes and suggested actions. The messages shown in this chapter may be accompanied by additional text when displayed on screen. This text identifies the function that detects the problem, and can include internal status codes, or BS2000 system macro return codes, or both.
Action: Make sure that your application program runs in ILCS mode. Some programming languages (for example, FOR1, PL/I) require specific options for ILCS. Refer to the Fujitsu documentation for further information. ORA-05004: Fatal error: stack overflow, extension failed Cause: A call to a function required an extension of the current call stack segment. This extension failed (the corresponding ILCS routine returned the error).
ORA-05013: bad filename parse Cause: A file name being analysed is not well-formed for Oracle Database purposes. Action: Correct the file name and re-run the program. ORA-05014: sfcopy: non-matching block size Cause: In a partial database file copy, source and target file have different blocksizes. This may indicate an internal error and should not normally occur. Action: If you cannot identify the cause of the problem, then contact your Oracle Support Services Representative.
Action: If the error cannot be identified as one caused by a disk malfunction, then either contact the System Administrator, or contact your Oracle Support Services Representative. ORA-05022: read block outside of file Cause: An attempt was made to read a block of an Oracle Database file that does not exist (block number < 1 or > file size). This is an internal error and should not normally occur. Action: Contact your Oracle Support Services Representative.
Action: Ensure that the ORASID definition is correct and re-run the program. ORA-05032: bad name parse Cause: The translation of a file name, or other name containing variable parts, failed. The error may be caused by a wrong specification in the ORAENV file. Action: Ensure that the ORAENV variable assignments are correct. If you cannot identify the cause of the problem, then contact your Oracle Support Services Representative.
Action: Make sure that the user address space is large enough (in the JOIN entry) and that there is no temporary memory saturation. Then re-run the program. If you need further help, then contact your Oracle Support Services Representative. ORA-05041: Interrupt in soarch Cause: The archiver process was unexpectedly interrupted. Action: If you cannot identify the cause of the problem, then contact your Oracle Support Services Representative.
ORA-05053: invalid or missing PGA_BASE Cause: An invalid value for the PGA_BASE parameter has been specified in the DBA ORAENV file. Action: Specify a correct value. ORA-05054: invalid or missing PGA_SIZE Cause: An invalid value for the PGA_SIZE environment variable has been specified in the DBA ORAENV file. You should never change the default value for the PGA_ SIZE environment variable. Action: Use the default value for the PGA_SIZE environment variable.
Action: Verify that it is not one of the preceding causes (check with your database administrator). Otherwise, contact your Oracle Support Services Representative. ORA-05063: SGA base invalid Cause: An invalid value has been specified for the SGA_BASE parameter in the ORAENV file. Action: This value is not normally needed. If specified, it must be a hexadecimal value giving the full virtual address for the SGA memory pool. Correct the value and re-issue the STARTUP command.
Cause: Probable operating system error. Action: Contact your Oracle Support Services Representative. ORA-05071: cannot ENQ on TPA ser.item Cause: Probable operating system error. Action: Contact your Oracle Support Services Representative. ORA-05072: cannot enable post/wait item Cause: Probable operating system error. Action: Contact your Oracle Support Services Representative. ORA-05073: error in post Cause: An interprocess communication operation failed.
different from $ORAC1120 and that the installation procedure has not executed correctly. Action: Ensure that the ORAUID definition in the ORAENV file is correct. Otherwise, contact your Oracle Support Services Representative. ORA-05102: module verification failure: ORADBCN@ Cause: The UTM application has probably been link-edited with an Oracle Database version different from the Oracle Database version used at execution. Action: Re-link the UTM application.
Action: If this value is specified, then it must be a hexadecimal value giving the full virtual address for the base address of a memory pool. Correct the value and restart the database. ORA-05116: cannot load shared code into pool Cause: Shared code could not be loaded into the specified memory pool. Generally, this message will be preceded by a BLS-nnnn message from the operating system. Action: Make sure that the ORALOAD link name identifies the correct ORALOAD library. Then restart the program.
ORA-05132: TA for User x is committed by the Resource-Manager Cause: Transaction has been committed before failing. Action: None. ORA-05133: No Connect-String in Startparams found Cause: In the start parameters there must be at least one open string for the Oracle Database. Action: Refer to the chapter "UTM Product Set" in the Oracle Database Installation and Administration Guide for Fujitsu BS2000/OSD and correct the start parameters. ORA-05134: DBSTAT secondary opcode inconsistent Cause: System error.
ORA-05142: Error x at End Transaction for User z, Instance y Cause: The end of a transaction in instance y is invalid. Action: Restart the UTM transaction. If the error persists, then shut down the UTM application and do a restart. ORA-05143: Mismatch in TA for User(s) z Cause: In the UTM warmstart there is a mismatch between openUTM, or between the Oracle Database instance(s), or both. Action: Clear the Oracle Database instance(s), create new KDCDEF for UTM and restart the UTM application.
ORA-05153: xa_switch definition not found for specified Resource-Manager: s Cause: System error. Action: Contact your Oracle Support Services Representative. ORA-05154: Syntax error in start parameters for Resource-Manager: s Cause: In the start parameters for the Oracle Database there is a syntax error. Action: Refer to the chapter "UTM Product Set" in your Oracle Database Installation and Administration Guide for Fujitsu BS2000/OSD and correct the start parameters.
Cause: An invalid value for the KNL_SIZE parameter has been specified in the ORAENV file. Action: You should not normally specify this variable, as the default value will be correct. Contact your Oracle Support Services Representative. ORA-05174: bad kernel base Cause: An invalid value for the KNL_BASE parameter has been specified in the ORAENV file. Action: If this value is specified, then it must be a hexadecimal value giving the full virtual address for the kernel memory pool.
ORA-05181: load/init problem with PRO/OCI interface Cause: The user-side stub module could not load the PRO/OCI module (in this case, the message will normally be preceded by a BS2000 BLS-nnnn message), or the loaded module is incompatible with the version of the stub module. Action: Make sure the ORALOAD link name exists and points to the current ORALOAD library. Re-link your application with the current link libraries.
Action: If you cannot identify the cause of the problem, then contact your Oracle Support Services Representative.
A-18 Oracle Database User's Guide
B B Oracle Environment Variables This appendix describes variables that can be specified in the ORAENV file or the POSIX shell. Oracle parameters, such as ORACLE_SID and NLS_LANG, may be specified in the ORAENV file or POSIX shell. If you use a ORAENV file, then you must follow the ORAENV rules for specifying environment variables as described in the following sections. In the POSIX shell, you must follow the UNIX rules to set and export the environment variables.
Built-in Variables ■ When variable assignments refer to other variables, BS2000 command file substitution syntax applies. Substitution takes place when a variable is actually used, not when it is read from the ORAENV file. For example: ORAUID=$ORAC1120 SQLPATH=&ORAUID..RDBMS.ADMIN assigns the value $ORAC1120.RDBMS.ADMIN to the variable SQLPATH. If ORAUID is changed, then SQLPATH automatically reflects the new value. ■ ■ The sequence of items in the ORAENV file is not generally significant.
General Variables B.3.1 CLN_BASE This variable specifies the address of the shared code pool of customer written database applications for CORE, NLS, and NET. Format: CLN_BASE=address Classification: USER Default: CLN_BASE=37M B.3.2 CLN_MPID This variable specifies the identification of the shared code pool of customer written database applications for CORE, NLS, and NET. Format: CLN_MPID=sid Classification: USER Default: CLN_MPID=&ORASID B.3.
General Variables Format: EXP_CLIB_FILE_IO=FALSE Classification: USER Default: EXP_CLIB_FILE_IO=TRUE B.3.5 IMP_CLIB_FILE_IO This variable should be set to FALSE when you use the Import utility to overcome a problem with the C library functions when an import file is read from tape. Format: IMP_CLIB_FILE_IO=FALSE Classification: USER Default: IMP_CLIB_FILE_IO=TRUE B.3.6 NLS_LANG This variable specifies the default language and character set. For example: NLS_LANG=GERMAN_GERMANY.
DBA Startup Variables Format: ORASID=sid (sid is a characterstring where 1 <= length <= 4) Classification: USER, DBA Note: Oracle recommends that you use the ORACLE_SID variable. B.3.10 PRINTPAR This variable specifies optional variables for the /PRINT command issued for SPOOL OUT spool files. Using this variable, the user can modify the spooled job, and, for example, route the job to a remote printer, add print options for laser printers, and so on.
DBA Startup Variables ■ ■ ■ A number with no modifiers is interpreted as a decimal number A number followed by K or M is interpreted as a decimal number multiplied by 1024 or 1048576 (1024*1024) respectively A number enclosed in single quotation marks and preceded by the letter X is interpreted as a hexadecimal number For example, the following all set the KNL_BASE variable to 8M: KNL_BASE=8M KNL_BASE=8388608 KNL_BASE=X'800000' B.4.
DBA Startup Variables Format: sid_BGJPAR=parameters Syntax: sid is a string of at the most 4 alphanumeric characters parameters is the parameters for the ENTER-PROCEDURE command as described in the BS2000/OSD commands Classification: DBA,USER, NET B.4.6 sid_USER This variable specifies the USER-ID where the instance assigned by SID resides.
DBA Startup Variables B.4.10 JOBID This variable is used internally in identifying the background tasks and generating task-specific names. You see it in some places, but you should never specify it yourself. Classification: DBA B.4.11 KNL_BASE This variable gives the base address where the shared memory pool is mapped in memory. This must be an integral number of megabytes. Format: KNL_BASE=address Classification: DBA Default: KNL_BASE=72M B.4.
Oracle Net Services Variables Format: SF_PBLKSIZE=2K|4K Classification: DBA Default: 2K Note: This variable cannot be changed after database creation. Once you specify a value different from the default, you must specify it in all future calls. B.4.16 SGA_BASE This variable gives the address where the SGA is mapped into memory, and must represent a megabyte-boundary.
Oracle Net Services Variables B.5.3 TNS_BEQ_TIMEOUT This variable specifies the time after which a connection between a parent and a child process is closed if there is no communication between them. Format: TNS_BEQ_TIMEOUT=lifetime (in seconds) Classification: NET Default: TNS_BEQ_TIMEOUT=180 B.5.4 TNS_UPDATE_IPNODE This variable forces the Oracle Net software to change always the server's IP-Node name to an IP-Node address.
Index Symbols $ command, 3-3 A ASCII function, 3-4 B BGJ_LOG_JOBSTART, B-6 BGJPAR, B-6 BS2000 commands from SQL*Plus, 3-3 BS2000 editor starting, 3-3 C Call Interface, 5-8 Character sets supported, 7-3 CLN_BASE, B-3 CLN_MPID, B-3 COM_BASE, B-7 Commands $, 3-3 DEFINE_EDITOR, 3-3 EDIT, 3-3 HOST, 3-3 RESUME, 3-3 SPOOL, 3-4 Connecting to the Oracle Database, 1-6 D DEFAULT_CONNECTION, B-3 DEFINE_EDITOR command, 3-3 Demonstration files PL/SQL, 4-1 SQL*Loader, 2-1 CLN_BASE, B-3 CLN_MPID, B-3 DEFAULT_CONNECTIO
R Interrupting SQL*Plus, 3-2 RESUME, 3-3 RSET call (UTM), J JOBID, B-8 S K KNL_BASE, B-8 L Languages specifying, 7-1 supported, 7-2 Linguistic definitions, 7-4 LOGNAME, B-2 M Messages, A-1 N National language support, NLS_LANG, B-4 7-1 O OCI, 5-8 linking, 5-9 OPS_JID, B-4 Oracle Call Interface, 5-8 Oracle Database precompilers, 5-1 programmatic interfaces, 5-1 utilities, 2-1 ORACLE_HOME, B-8 ORADUMP, B-4 ORAENV, B-1 ORALOAD, 1-3 ORAUID, B-2 P PEND call (UTM), 6-2 PGA, B-8 PGA_BASE, B-8 PGA_SIZE,
