Oracle® Database Installation and Administration Guide 11g Release 2 (11.
Oracle Database Installation and Administration Guide, 11g Release 2 (11.2) for Fujitsu BS2000/OSD E27508-03 Copyright © 2007, 2014, Oracle and/or its affiliates. All rights reserved. Primary Author: Bharathi Jayathirtha 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 ................................................................................................................................................................. xi Audience....................................................................................................................................................... xi Using Oracle Database Documentation ...................................................................................................
2 Architecture and Implementation 2.1 2.1.1 2.1.2 2.1.3 2.2 2.2.1 2.2.2 2.2.2.1 2.2.2.2 2.2.2.3 2.2.2.4 2.2.2.5 2.2.3 2.2.4 2.3 2.4 2.4.1 2.5 2.5.1 2.5.2 2.5.3 2.5.4 2.6 2.7 2.8 2.8.1 2.8.1.1 2.8.1.2 2.8.2 2.8.2.1 2.8.2.2 2.8.3 2.8.3.1 3 Operating System Environment ............................................................................................... 2-1 File Systems ..........................................................................................................................
3.3.2.3 3.3.2.4 3.3.2.5 3.3.2.6 3.3.3 3.3.3.1 3.3.3.2 3.3.3.3 3.3.3.4 3.3.3.5 3.3.4 3.3.4.1 3.3.4.2 3.3.4.3 3.3.4.4 3.3.5 3.3.5.1 3.3.5.2 3.3.5.3 3.3.6 3.3.6.1 3.3.6.2 3.4 3.5 3.6 3.7 4 Package Requirements................................................................................................. 3-6 Additional BS2000 Software Components................................................................ 3-7 Compiler and CRTE Requirements for Oracle Database Applications................
4.2.1 4.2.2 4.2.3 5 Administering Oracle Database 5.1 5.1.1 5.1.2 5.1.3 5.1.4 5.1.5 5.1.6 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.3 5.4 5.4.1 5.4.2 5.5 6 Backing Up an Oracle Database................................................................................................ Using BS2000 Utilities to Back Up an Oracle Database.................................................. Online Backup ......................................................................................................................
8.5 Troubleshooting .......................................................................................................................... 8-8 8.5.1 Trace Files ............................................................................................................................. 8-8 8.5.1.1 Trace File Examples...................................................................................................... 8-8 8.5.2 Debugging ...................................................................
14 Oracle Management Agent 14.1 14.2 14.3 14.4 14.5 Preinstallation Issues ............................................................................................................... Running the Installation Script .............................................................................................. Running the Agent................................................................................................................... Restrictions....................................................
B.4.3 BGJPRC_UID / BGJPRC_SID ........................................................................................... B.4.4 BGJ_LOG_JOBSTART ........................................................................................................ B.4.5 sid_BGJPAR ......................................................................................................................... B.4.6 sid_USER.............................................................................................................
E File Types and Names Used by Oracle x
Preface This manual and Oracle Database User's Guide for Fujitsu BS2000/OSD, form a system-specific set of manuals that provide installation, maintenance, and usage information about Oracle Database and related products.
Type Meaning/Usage Generic This is the primary Oracle Database documentation, which describes how the product works and how it is used. Use this type of documentation to learn about product functions and how to use any Oracle Database product or utility. System Specific This documentation provides the information required to use the product under a specific operating system. Use this type of documentation to determine whether there are any system-specific deviations from the generic documentation.
Convention Meaning 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. Command Syntax Item Syntax Commands This font identifies text which must be entered exactly as shown: set echo off Variables Variables appear in italics.
xiv
1 1 Release Notes This chapter describes the features of Oracle Database on Fujitsu BS2000/OSD. The following topics are covered in this chapter: ■ Oracle Database Editions for BS2000/OSD ■ Options Not Supported ■ Features not Supported ■ Known Restrictions, Problems, and Workarounds 1.
Features not Supported ■ Oracle RAC One Node ■ Oracle Real Application Clusters (Oracle RAC) 1.
Known Restrictions, Problems, and Workarounds ■ Oracle Data Pump Import and Oracle Data Pump Export ■ Globalization Support ■ Oracle Call Interface ■ ADRCI ■ Connecting from Oracle Database 10g clients ■ Utilities in the POSIX environment ■ Oracle Net Services ■ Oracle Net BEQ Protocol ■ Oracle Protocol Support for TCP/IP ■ POSIX Subsystem 1.4.1 General Notes The German characters ä, ö, ü and ß, cannot be used in the names of tables, columns, fields, synonyms, and so on.
Known Restrictions, Problems, and Workarounds 1.4.7 Oracle Scheduler External Jobs are not supported. 1.4.8 INIT.ORA Parameters A few initialization parameters in the INIT.ORA file, described in the generic documentation are not supported by Oracle Database 11g Release 2 for BS2000/OSD. Refer to Appendix C, "Initialization Parameters and the Parameter File" for more information. 1.4.9 Archiving to Tape Archiving to tape is not supported; archive log files must always be created as disk files.
Known Restrictions, Problems, and Workarounds ■ ■ ■ ■ If you use the SQL*Plus -s option, then it must be the first option entered at the prompt. The internal message buffer is limited to 76 characters, therefore, certain messages are truncated. This typically occurs if a message includes a second message. In such cases, you usually refer to the message number part of the second message.
Known Restrictions, Problems, and Workarounds ■ Dynamic, or Private Ports, or both, from 49152 through 65535 Fujitsu documentation for TCP/IP on BS2000 recommends setting the privileged port to 2050. However, using a registered Oracle port number may cause conflicts (see http://www.iana.org/assignments/port-numbers).
2 2 Architecture and Implementation This chapter describes the Oracle Database system architecture for Fujitsu BS2000/OSD. The chapter includes the following topics: ■ Operating System Environment ■ Basic Structures ■ Two-Task Mode ■ Address Space Planning ■ Oracle Database Environment Definition File ■ The ORALOAD Library ■ The ORAMESG library ■ User ID Requirements 2.1 Operating System Environment Oracle Database 11g Release 2 runs on the BS2000/OSD operating system.
Basic Structures Therefore, Oracle Database 11g Release 2 for BS2000/OSD requires the POSIX file system. While in Oracle Database 10g the use of the POSIX file system was optional, it is mandatory in Oracle Database 11g Release 2. During the installation of the Oracle Database software executables, libraries and other files are installed both in the BS2000 DMS and in the POSIX file system. You must provide access to the POSIX file system.
Basic Structures Note: Both the BS2000/OSD operating system and Oracle Database perform input and output efficiently in units called blocks. A block is the basic unit of data storage. An Oracle Database block can be in one of the following formats: ■ 2K, 4K, 6K, 8K, 16K, 32K when using BS2000 2K pubset format ■ 4K, 8K, 16K, 32K when using BS2000 4K pubset format Oracle Database and redo log files are BS2000 PAM files, and Oracle Database uses UPAM to access them. 2.2.
Basic Structures 2.2.3 Oracle-Managed Files The following is a list of the INIT.ORA parameters for oracle-managed files: ■ DB_CREATE_FILE_DEST for data files, temp files, and block change tracking files ■ DB_CREATE_ONLINE_LOG_DEST_n for redo log files and control files ■ DB_RECOVERY_FILE_DEST for backups, archive log files, and flashback log files On BS2000, these parameters are used as a prefix for file names. Oracle tablespace names can be up to 30 characters long.
Address Space Planning Refer to "Using Oracle Managed Files" in Oracle Database Administrator's Guide for more information about file name formats See Also: 2.2.4 Bigfile Tablespaces Oracle Database 11g Release 2 on BS2000/OSD supports bigfile tablespaces.
Oracle Database Environment Definition File Figure 2–1 Placement of Data Areas in Background, Server and User Tasks The xxx_BASE values must be compatible with the BS2000/OSD value SYSBASE (defined by BS2000/OSD generation and delimiting the user’s address space). Starting with Oracle Database 10g, user programs use a separate shared code pool for common services such as Core, Globalization Support, and Net Services.
Oracle Database Environment Definition File 2.5.2 Oracle Environment Variables Appendix B, "Oracle Environment Variables" contains a list of Oracle environment variables that the database administrator can use. Most users only need to set a few of these variables. Any DBA-specific variables that are placed in a user's ORAENV file are ignored. 2.5.
Oracle Database Environment Definition File The Oracle variable BGJPAR is not set after running the .profile.oracle. If you do not set this variable, then the default value, BGJPAR=START=IMME,CPU-LIMIT=NO,LOGGING=*NO, is used by Oracle utilities. Note: You can change the default value of a variable by setting this variable in the POSIX environment. For example: $ NLS_LANG=German_Germany.
User ID Requirements 2.6 The ORALOAD Library The ORALOAD library ($ORAC1120.ORALOAD.LIB by default) is required to run any Oracle Database 11g Release 2 program. The Oracle Database uses this library to load executables and subroutines dynamically when required. The link name ORALOAD must identify the ORALOAD library before calling any Oracle Database program. If the link name is missing, then you get a BLS (BS2000/OSD loader) error message.
User ID Requirements ■ You must not use the BS2000/OSD System Administrator user ID TSOS as an Oracle Database installation user ID. ■ The ORAUID does not require any specific user attributes or privileges. ■ Only the installation phase requires a BS2000 LOGIN under this user ID. ■ During installation all files are created with the file attributes: USER-ACC=ALL-USERS, ACCESS=READ ■ ■ You do not need to define write access for any file after installation.
User ID Requirements USER-ACC=OWNER-ONLY, ACCESS=WRITE ■ the POSIX user for the DBA user ID must be initialized with a unique user number and group number. 2.8.2.2 Default Name There is no default name for the DBA user ID. 2.8.3 User IDs for Oracle users An Oracle user accesses and uses the database through Oracle utilities, such as SQL*Plus, and through the precompiler application programs. The user can connect to Oracle Database through Oracle Net Services facilities.
User ID Requirements 2-12 Oracle Database Installation and Administration Guide
3 3 Oracle Database Installation and Deinstallation This chapter describes preinstallation requirements, postinstallation tasks, and the installation and deinstallation of Oracle Database 11g Release 2 on BS2000/OSD.
Oracle Database Preinstallation Requirements See Also: Oracle Database Licensing Information for more licensing information 3. Complete preinstallation tasks: "Oracle Database Preinstallation Requirements" describes preinstallation tasks that you must complete before installing the product. 4. Install the software: "Installing the Oracle Database Software" describes how to use the Oracle installation procedure for BS2000/OSD to install Oracle Database 11g Release 2. 5.
Oracle Database Preinstallation Requirements ■ To determine the user address space limit, log in to the desired user ID and enter the following command: /SHOW-USER-ATTRIBUTES If the user address space is less than the required size, then ask your BS2000 system administrator to increase the Address Space Limit by using the command: /MODIFY-USER-ATTRIBUTES USER-IDENTIFICATION=user-id,ADRESS-SPACE-LIMIT={512|1024} 3.3.1.
Oracle Database Preinstallation Requirements ■ BS2000 file system: Item Disk Space Software 1.000.000 PAM pages Staging library 820.000 PAM pages Recommended (in total) 2.000.000 PAM pages ■ POSIX file system: Requirement Disk Space Minimum 400 MB Recommended 1 GB Note: The diagnostic data of the Automatic Diagnostic Repository (ADR) reside in the POSIX file system.
Oracle Database Preinstallation Requirements 3.3.2.1 Operating System and Communication System Requirements The following operating system and communication system versions or higher, are required for Oracle Database 11g Release 2: ■ BS2000/OSD V7.0 ■ openNet Server V3.3 This includes BCAM V20.0 and Sockets V2.4. Oracle recommends that you regularly install the most current correction packages for BS2000/OSD.
Oracle Database Preinstallation Requirements Recommended Value Parameter Name Description NOSTTY Maximum number of 512 sttys DBLSTATE Initial state of POSIX loader DBLPOOL Size of pool in MB for 30 POSIX loader 1 The POSIX administrator or BS2000 system administrator can check the values in the file $TSOS.SYSSSI.POSIX-BC.version, for example, version = 070|080|090.
Oracle Database Preinstallation Requirements 3.3.2.4 Additional BS2000 Software Components The following additional software is required by Oracle Database 11g Release 2. Install the required or higher versions: ■ CRTE-BASYS V1.7F or CRTE-BASYS V1.8E or CRTE-BASYS V1.9A ■ SDF V4.7 ■ SDF-P V2.5 ■ SDF-A V4.1 ■ EDT V17.0A ■ LMS V3.4 ■ openSM2 V7.0 ■ PTHREADS V1.3 ■ ORACLE-TOOLS V1.
Oracle Database Preinstallation Requirements ■ CRTE V2.8E ■ CRTE V2.9 3.3.2.6 Additional Software Requirements openUTM V6.0 or higher is required if you want to use Oracle Database in configurations with the transaction monitor openUTM. 3.3.3 Checking Network Setup Typically, the computer on which you want to install Oracle Database is connected to the network as a member of a network domain. Besides the BCAM host name, the host should have a full qualified name (hostname.
Oracle Database Preinstallation Requirements 3.3.3.4 Checking Loopback Address Check if the file $TSOS.SYSDAT.BCAM.ETC.HOSTS contains an entry for the loopback address. For example: 127.0.0.1 localhost loopback # local address 3.3.3.5 Checking the Configuration Files in the POSIX File System Check the network configuration files /etc/hosts and /etc/resolv.conf. These files must have the same contents as the corresponding files in the BS2000 administrator user ID TSOS.
Oracle Database Preinstallation Requirements The inst_group parameter shows the group name of your former Oracle Database installation, here oracle. ■ To determine if this group is defined with a unique group-id, enter the following command: $ grep 'oracle' /etc/group If the output shows the group name and a group-id greater than 100, then the group exists. If the group-id is 100, then you must change the id to a distinct value greater than 100, for example, 104.
Oracle Database Preinstallation Requirements /SHOW-POSIX-USER-ATTRIBUTES If the output shows default values and the directory is /home/gast, then initialize the POSIX user with the following BS2000 command: /ADD-POSIX-USER The POSIX user attributes of an initialized POSIX user can be modified with the following BS2000 command: /MODIFY-POSIX-USER-ATTRIBUTES Finally, add the user to the Oracle installation group in the file /etc/group.
Oracle Database Preinstallation Requirements Note: ■ ■ The installation user ID and the installation group must have read, write and execute permissions to the subdirectory app. During Oracle Database software installation, you are prompted for a valid Oracle base directory. You can accept the default value or enter a new path. The installation procedure creates the Oracle base directory if possible. You can use the same Oracle base directory for the installation of the Oracle Management Agent.
Oracle Database Preinstallation Requirements 3.3.5.3 Oracle Home Directory The Oracle home directory is the directory where you install the software for a particular Oracle product. When you run the Oracle installation procedure, it prompts you to specify the path of this directory. You can accept the recommended path or enter a new path. The directory that you specify must be a subdirectory of the Oracle base directory.
Oracle Database Preinstallation Requirements The directory paths specified on each line identify Oracle home directories. Directory paths that end with the user name of the Oracle software owner are existing Oracle base directories. For the installation of Oracle Database 11g Release 2, you can choose the subdirectory /u01/app as root for your Oracle base directory.
Installing the Oracle Database Software # chown -R oracle_sw_owner:oracle_installation_group /mount_point/app/oracle_sw_ owner # chmod -R 775 /mount_point/app/oracle_sw_owner For example: # mkdir -p /u01/app/orac1120 # chown -R orac1120:oracle /u01/app/orac1120 # chmod -R 775 /u01/app/orac1120 3.4 Installing the Oracle Database Software The Oracle Database 11g Release 2 software is available in a zipped LMS library. Complete the following steps to install the Oracle Database software: 1.
Installing the Oracle Database Software If you have stored the staging library in a different BS2000 user ID, then call the Oracle installation procedure as follows: /CALL-PROCEDURE (staging_ userid.ORA11202.S390.LIB,ORAINST.PRC),(INSTUID=staging_userid) For example: /CALL-PROCEDURE ($FOO.ORA11202.S390.LIB,ORAINST.
Oracle Database Postinstallation Tasks Parameter Value Description ORACLE-HOME *DIALOG|oracle_home The Oracle home directory is required for the installation of Oracle Database 11g Release 2 in the POSIX file system. The default value *DIALOG indicates the prompting for an Oracle home directory. default: *DIALOG DEBUG Debug the installation procedures.
Installing Multiple Oracle Systems ■ Creates the file /var/opt/oracle/oraInst.loc ■ Creates an empty file /var/opt/ortacle/oratab ■ If the product APACHE is installed, then it creates a link in the lib directory of the APACHE installation to the Oracle Client shared library in the Oracle home lib directory. 3.6 Installing Multiple Oracle Systems You can also install multiple Oracle systems, based on the same or different versions of Oracle software.
4 4 Creating and Upgrading a Database This chapter describes how to create a new 11.2 database or upgrade an existing database to release 11.2. It contains the following topics: ■ Creating a Database ■ Upgrading a Database Creating a Java enabled database is not part of this chapter. For more information about creating a Java enabled database, refer to Chapter 12, "Java in the Database". Note: 4.1 Creating a Database You can create a database either automatically or manually.
Creating a Database Note: 3. The value of ADDRSPACE must be at least 512 MB. Oracle recommends that the BS2000 System Administrator should define a separate job class for the background tasks. This job class should have the following characteristics: TP-ALLOWED=YES NO-CPU-LIMIT=YES JOB-TYPE=BATCH 4.1.2 Creating a Database Automatically Complete the following steps to create a database automatically: 1. Log in using the DBA user ID. 2. To start the automatic creation procedure, INSTALL.P.
Creating a Database Parameter Value JAVA Enter NO if you do not need a Java enabled database (thus saving memory, CPU and disk space resources). For more information refer to Chapter 12, "Java in the Database". DBSIZE Enter the size of the system tablespace files in bytes, kilobytes or megabytes. The value you enter can have one of the following forms: ■ 44M for 44 megabytes ■ 44000K for 44000 kilobytes ■ 10000000 for 10000000 bytes The default is 250M.
Creating a Database ■ ■ Creates the system and sysaux tablespace Creates the default permanent tablespace, temporary tablespace, and undo tablespace ■ Creates the log files ■ Initializes the database ■ Runs CATALOG.SQL ■ Runs CATPROC.SQL ■ Installs the SQL Help tables ■ Installs the DEMO tables ■ Changes the system passwords if necessary ■ Calls the verification procedure When $ORAC1120.INSTALL.P.
Creating a Database /CALL-PROCEDURE $ORAC1120.INSTALL.P.DBA This procedure prompts you for the following information: Parameter Value DBASID Enter the 1 - 4 character system ID of the database you are installing. JOBCLASS Enter the BS2000 jobclass to be used for background and server tasks. You can also modify the following keyword parameters when invoking this procedure: Parameter Value LOG Enter WRITE-TEXT (the BS2000 command name) if you want to have install actions listed.
Creating a Database Database block size given in the init.ora parameter DB_BLOCK_SIZE, refer to Appendix C, "Initialization Parameters and the Parameter File". For example, if you want to create a 2 MB database file, then you must specify 1024 plus 1 PAM pages extra Oracle Database block as the value of file size in the FILE command. device specifies the device to be used to store the file. volser specifies the volume to be used to store the file.
Creating a Database 4.1.3.3 Installing Data Dictionary Views Data dictionary views provide easy access to dictionary information. If you want to use dictionary views, then you must install them by running SQL*Plus, by issuing the CONNECT / AS SYSDBA command, and entering the following commands: SQL> SPOOL filename SQL> SET TERMOUT OFF SQL> @$ORAC1120.RDBMS.ADMIN.CATALOG.SQL Data dictionary views required for Export or Import are also installed in this sequence. 4.1.3.
Upgrading a Database 4.1.3.9 Installing Oracle Text Usage and installation of Oracle Text is summarized in the "Oracle Text" chapter of this book. 4.1.3.10 Installing Java Using and installing of Java is summarized in the chapter "Java in the Database" in this book. 4.2 Upgrading a Database This section contains information about upgrading your Oracle database that are described in the following: ■ Upgrade from Version 9 ■ Upgrade from Version 10 ■ Postupgrade Activities 4.2.
Upgrading a Database 4. Enter the following command to create an Oracle Database 11g Release 2 init.ora and an Oracle Database 11g Release 2 ORAENV file and save the original files under the suffix .OLD. /CALL-PROCEDURE $ORAC1120.INSTALL.P.DBA, (sid, jobclass, UPDATE=YES) 5. Modify the newly created files according to your special requirements (for instance PROCESSES, DB_CACHE_SIZE, and so on) and set the parameters in the INIT.ORA file as recommended in the spoolfile.
Upgrading a Database Re-compilation of C and COBOL Programmatic Interface Programs All C and COBOL programs developed prior to release 11.2 must be precompiled using the new version of the precompilers and recompiled. Re-Linking Programmatic Interface Programs All user-written precompiler or Oracle Call Interface applications must be re-linked using the new Oracle Database libraries. Rebuilding Oracle Database (openUTM) Applications openUTM applications must be rebuilt.
5 5 Administering Oracle Database This chapter describes how to administer Oracle Database 11g Release 2 for BS2000/OSD. Common administration tasks are described in the following sections: ■ Using the SQL*Plus Utility ■ Startup and Parameter Files ■ Remote Startup of a Database Instance ■ Automatic Diagnostic Repository ■ Checking the Integrity of the Physical Data Structure 5.
Using the SQL*Plus Utility 5.1.2 Calling SQL*Plus from a Procedure Set Task Switch 1 to on (/MODIFY-JOB-SWITCHES ON=1). This forces SQL*Plus to read in data from the procedure, rather than prompt you at the terminal. 5.1.3 Using SQL*Plus in the POSIX shell Before starting SQL*Plus in the POSIX shell, you must set the environment variable ORACLE_HOME and extend the POSIX variable PATH by the path to the Oracle bin directory $ORACLE_HOME/bin.
Startup and Parameter Files 5.1.5 Using an Editor in SQL*Plus Start a text editor in SQL*Plus with the EDIT command, if you want to edit an SQL statement. If you run SQL*Plus in the native BS2000 environment, then the only editor supported is BS2000 EDT. If you run SQL*Plus in a POSIX shell, then the default editor depends on the terminal connected with your POSIX session. If the POSIX shell is started on a blockmode terminal, then the default editor in SQL*Plus is set to edtu.
Startup and Parameter Files ■ The Server Parameter File SPFILE ■ Using the Correct Initialization File 5.2.1 The Environment Definition File ORAENV The ORAENV file is identified by sid.P.ORAENV, where SID is the database identifier. The same ORAENV file must be used by SQL*Plus in BS2000 and by all background jobs. This is ensured by the installation procedures, which create the basic ORAENV file.
Remote Startup of a Database Instance with no PFILE clause, Oracle locates the initialization parameter file by examining file names in the following order: 1. sid.DBS.SPFILE.ORA 2. DBS.SPFILE.ORA 3. sid.DBS.INIT.ORA If you want to use some other initialization file, then use the argument PFILE. For example, to bring up a previously created database using an initialization file called TEST.INIT.ORA, enter the following: /START-PROGRAM $ORAC1120.
Automatic Diagnostic Repository 5. Execute SQL*Plus on the remote computer and connect as user sys to a server of the instance you want to startup. In the following example, which shows the commands for SQL*Plus on a UNIX client, we use the net service name orcl_on_ bs2000 to address the remote instance on the BS2000 computer: sqlplus /nolog SQL> connect sys@orcl_on_bs2000 as sysdba Enter password: password Connected SQL> startup ... 5.
Automatic Diagnostic Repository Within ADR base, there can be multiple ADR homes, where each ADR home is the root directory for all diagnostic data, such as traces, dumps, the alert log, and so on, for a particular instance of a particular Oracle product or component. Oracle Net Services also store diagnostic data in the ADR. The location for diagnostic information for Oracle Net Services is set by the parameters ADR_BASE and ADR_BASE_ listener_name.
Checking the Integrity of the Physical Data Structure You can either select the preferred text editor by setting the environment variable EDITOR before starting ADRCI or specify your preferred text editor within ADRCI with the ADRCI set editor command. Note: The editor vi does not work on blockmode terminals and the editor edtu does not work on xterm terminals.
6 6 Backing Up and Recovering a Database This chapter supplements the generic Oracle Database documentation set with information about backup and recovery. Refer to the following Oracle manuals for detailed information about database backup and recovery: ■ Oracle Database Concepts ■ Oracle Database Administrator's Guide ■ Oracle Database Backup and Recovery User's Guide You can choose among many methods and Oracle tools for backup and recovery.
Recovering Databases 2. To ensure that all Oracle database files are synchronized at the time of the backup, shut down Oracle database using SQL*Plus. 3. Back up all database files and log files using the BS2000 ARCHIVE utility or the BS2000 /COPY-FILE command. You should always back up all files at the same time. 4. Restart Oracle Database using SQL*Plus. 6.1.
Recovery Manager While Oracle database is running, the names of all files which it comprises can be determined by querying the table V$DATAFILE. Enter the following command when the SQL prompt is displayed: SQL> select file#,name FROM V$DATAFILE; The following is an example of the result that is displayed: FILE#NAME ------------------------------1 :pvs:$dbauserid.sid.DBS.DATABASE1.DBF 2 :pvs:$dbauserid.sid.DBS.DATABASE2.DBF 2 ROWS SELECTED.
Recovery Manager 6-4 Oracle Database Installation and Administration Guide
7 7 Tuning Oracle Database Careful tuning can dramatically increase the speed of an Oracle database. This chapter describes how you can monitor and tune the system for optimal performance of Oracle database. For a general discussion of performance and tuning issues, refer to Oracle Database Administrator's Guide and Oracle Database Performance Tuning Guide. This chapter covers BS2000 specific tuning parameters. You should always tune Oracle database.
BS2000/OSD-Specific Parameters 7-2 Oracle Database Installation and Administration Guide
8 8 openUTM Product Set This chapter describes how to use the BS2000/OSD transaction monitor openUTM for coordinated interoperation with Oracle Database 11g Release 2 (11.2). The following areas are covered: ■ Operation of Oracle Database Using openUTM Programs ■ Distributed openUTM Files ■ Installing ■ Developing an Oracle Database/openUTM Application ■ Troubleshooting 8.
Installing ■ The following files provide examples of procedures and programs: UTM.DEMO.P.COMPILE.C UTM.DEMO.P.COMPILE.COBOL UTM.DEMO.P.KDCDEF UTM.DEMO.P.KDCROOT UTM.DEMO.P.PROBIND UTM.DEMO.P.PROSTRT UTM.DEMO.CSELEMP.PC UTM.DEMO.SELDEP.PCO UTM.DEMO.SELEMP.PCO UTM.DEMO.UPDEMP.PCO UTM.DEMO.ERRSQL.C UTM.DEMO.ERRTXT.C 8.
Developing an Oracle Database/openUTM Application An Oracle Database/openUTM application requires the following information for execution: ■ Information about the application ■ Username/password with access protection ■ Information about the terminal and communication partners ■ Information about the transaction codes These properties collectively form the configuration, which is stored in the KDCFILE file. The configuration definition is carried out by the KDCDEF utility.
Developing an Oracle Database/openUTM Application corresponding programming language compilers. See the example procedure UTM.DEMO.P.KDCROOT for the compilation of the KDCROOT table module. 4. Linking the openUTM application program: The openUTM application program is produced by linking the KDCROOT table module with the openUTM program units. You must include the stub module XAOSTUB: INC-MOD LIB=ORAUID.XAO.
Developing an Oracle Database/openUTM Application Notes: Remember the following: ■ ■ ■ You can enter the required fields and optional fields in any order when constructing the open string. All field names are case-insensitive, although their values may or may not be case-sensitive depending on the system. You may not use the "+" character as part of the actual open string. 8.4.1.1 Required Fields The required fields for the open string are: Item Meaning Acc Specifies user access information.
Developing an Oracle Database/openUTM Application For more information about precompilers, specifically Pro*C, refer to the section Using Precompilers with openUTM later in this chapter. Item Meaning MaxCur Specifies the number of cursors to be allocated when the database is opened. It serves the same purpose as the precompiler option maxopencursors. maximum_no_of_open_cursors Indicates the number of open cursors. The default is 10.
Developing an Oracle Database/openUTM Application 8.4.2 Using Precompilers with openUTM You can choose from two options when interfacing with precompilers: ■ Using precompilers with the default database ■ Using precompilers with a named database You should run all precompiler programs with the option release_cursor set to no. Precompiler programs may be written in C or COBOL. In the following examples, the precompiler Pro*C is used. 8.4.2.
Troubleshooting You can use a character host variable in the AT clause, as the following example shows: EXEC SQL BEGIN DECLARE SECTION; db_name1 CHARACTER(10); db_name2 CHARACTER(10) EXEC SQL END DECLARE SECTION; . . set db_name1 = 'PAYROLL' set db_name2 = 'MANAGERS' . . EXEC SQL AT :db_name1 UPDATE... EXEC SQL AT :db_name2 UPDATE... For more information, refer to the respective sections in the Pro*COBOL Programmer's Guide and Pro*C/C++ Programmer's Guide that discusses concurrent logons.
Troubleshooting The following example shows a trace file for an application's task '1234' that was opened on April 2nd 1999. The DB field for this application was not specified in the open string when the resource manager was opened ORAXALOG.1234-NULL-990402.TRC The following example shows a trace file that was created on December 15th 1998 by task 5678. The DB field was specified as FINANCE in the open string when the resource manager was opened. ORAXALOG.5678-FINANCE-981215.
Troubleshooting ■ V$GLOBAL_TRANSACTION Note: For detailed information about how to use these tables, refer to the sections in the Oracle Database Administrator's Guide that discuss failures during two-phase commit and manually overriding in-doubt transactions. For transactions generated by Oracle Database/openUTM applications, the following column information applies specifically to the DBA_2PC_NEIGHBORS table: ■ The DBID column is always xa_orcl. ■ The DBUSER_OWNER column is always db_namexa.oracle.
9 9 Oracle Net Services This chapter describes Oracle Net Services and it’s implementation in the BS2000/OSD environment. It supplements the Oracle Database Net Services Administrator's Guide with BS2000/OSD-specific information about the following topics: ■ Introducing Oracle Net Services ■ Shared Server Architecture ■ Oracle Advanced Security ■ Configuring the Network ■ Troubleshooting Oracle Net Services 9.
Introducing Oracle Net Services 9.1.1.2 Using the IPC Protocol The IPC protocol allows applications to integrate with the Inter Process Communication method on a local host. The following is the syntax for using IPC protocol: (ADDRESS= (PROTOCOL=IPC) (KEY=alphanumeric) ) where PROTOCOL specifies the supported protocol. For IPC, the value is "IPC". KEY specifies the listen endpoint. A string of at most 32 characters: [a...z], [A...Z], [0...9], '.
Introducing Oracle Net Services 9.1.3 Using the TCP/IP Protocol The TCP/IP protocol support implements a standard interface that is used to resolve the equivalent communication functions between the TCP/IP protocol and Oracle's Net Foundation Layer. After the TCP/IP protocol is installed for the particular system, you can use the TCP/IP–specific parameters with the TNS connect descriptors to identify nodes within a TCP/IP-based community.
Shared Server Architecture ■ ■ Is used for local connections where an Oracle Database client application, such as SQL*Plus, communicates with an Oracle Database instance running on the same computer. Only works in Dedicated Server mode. It cannot be used in a Shared Server mode. Note: If clients are running under a user ID different from the DBA user ID, then Oracle recommends using a net service name to connect through a listener to the destination database. 9.
Oracle Advanced Security information in the following shared server dynamic tables to help you arrive at your decision: ■ V$DISPATCHER ■ V$QUEUE ■ V$SHARED_SERVERS ■ V$SHARED_SERVER_MONITOR For more information about these tables, refer to the Oracle Database Administrator's Guide. 9.3 Oracle Advanced Security With this release the data integrity and the cryptographic services of Oracle Advanced Security are supported. The Secure Sockets Layer (SSL) protocol is also supported.
Configuring the Network The value of each of these parameters can be either a list of algorithm names in parenthesis separated by commas or a single algorithm name. The default crypto checksum type is MD5, while the encryption defaults to all the algorithms. Type Values Crypto checksum types SHA1, MD5 Encryption types AES256, RC4_256, AES192, 3DES168, AES128, RC4_128, 3DES112, RC4_56, DES, RC4_40, DES40 Use the parameter SQLNET.
Configuring the Network ■ Testing the Configuration on the Client 9.4.1 Using Easy Connect Naming Method The Easy Connect naming method, can be used to connect to a database without the need to configure service names in the TNSNAMES.ORA configuration file. For using the Easy Connect naming method, ensure that EZCONNECT is listed in the client's configuration file parameter for naming adaptors names.directory_path. Easy Connect naming is only suitable in small and simple environments.
Configuring the Network Parameter Meaning sid_BGJPAR parameters for ENTER jobs identified by SID sid_USER the user ID under which the job should run user_ACCOUNT Account of the target user ID user_PASSWORD Password of the target user ID The following example of an ORAENV file configured for a central listener process shows how the parameters work. The listener can share this ORAENV file with an instance, which runs under the same user ID.
Troubleshooting Oracle Net Services 9.4.5 Configuration on the Client Configuration of network clients involves adding or editing parameters in the client configuration file SQLNET.ORA and dependent on the used naming method, the configuration file LDAP.ORA or TNSNAMES.ORA. For more information about the configuration parameters, refer to Oracle Database Net Services Reference. 9.4.
Troubleshooting Oracle Net Services ■ ■ ■ 4. If you do not want to use the BCAM host name of the computer in the TCP/IP network, then define a sockets-host-name as described in the BCAM documentation and register this name in the name service. Ensure that the BCAM Leight Weight Resolver LWRESD is properly configured and running. A client reports ORA-12535 ■ 5. Check the naming service if the host name returned by the listener is well known in the TCP/IP network.
10 10 Oracle Text This chapter describes how to install and run Oracle Text and the restrictions of this option on BS2000/OSD. 10.1 Installing Oracle Text When you follow the procedures explained in chapter 4 about creating an Oracle Database 11g Release 2 database the result is not Oracle Text enabled. If you want to install Oracle Text, then complete the following steps: 1. Start SQL*Plus.
Restrictions of Oracle Text on BS2000/OSD 10.3 Restrictions of Oracle Text on BS2000/OSD Due to ASCII-EBCDIC and other dependencies, the following restrictions are inherent: ■ ■ No index themes, that is CTX_DDL.
11 External Procedures 11 This chapter describes how to create an environment on BS2000/OSD, where external procedure calls can operate. It complements the chapter about External Routines in the Fundamentals section of Oracle Database Advanced Application Developer's Guide. 11.1 Loading External Procedures This section complements the corresponding part in Oracle Database Advanced Application Developer's Guide. Follow these steps to load external procedures: 1. Set up the environment.
Loading External Procedures The external C routine has to be compiled and the generated LLM has to be stored in the LMS library. If you set the MODULE-PROPERTIES option LOWER-CASE-NAMES=*NO, then all lowercase letters in the entry names are converted to uppercase. Furthermore, if you set the MODULE-PROPERTIES option SPECIAL-CHARACTERS=*CONVERT-TO-DOLLAR, then all underscores (_) in entry names are converted to dollar signs ($), which must be considered when publishing the external procedure. 3.
12 Java in the Database 12 This chapter describes BS2000-specific features for Java in the database. This chapter includes: ■ Installation of a Java Enabled Database ■ Database character sets and Java Encodings ■ Java Demonstration Files For more information, refer to the Oracle Java documentation set. 12.1 Installation of a Java Enabled Database When you call $ORAC1120.INSTALL.P.
Database character sets and Java Encodings Default encoding Encoding modification Statement or API File type Place CREATE JAVA SOURCE USING BFILE .java, .sqlj BS2000 PAM DB charset file or POSIX Execute dbms_ java. set_ compiler_ option (' ', 'encoding', 'ISO8859-1') CREATE JAVA SOURCE AS .sql Part of statement Session character set specified in NLS_LANG NLS_LANG CALL DBMS_ JAVA.LOADJAVA *, .jar, .zip POSIX DB charset Option encoding in loadjava call java.
Java Demonstration Files An example with database connection using the server-side internal driver is shipped under: $ORAC1120.JAVAVM.DEMO.
Java Demonstration Files 12-4 Oracle Database Installation and Administration Guide
13 XML 13 This chapter describes BS2000 specific topics of XML such as installation, features, and restrictions. For more information refer to Oracle XML Developer's Kit Programmer's Guide, Oracle XML DB Developer's Guide, Oracle Database XML C API Reference, Oracle Database XML C++ API Reference, and Oracle Database XML Java API Reference. 13.1 Installation of Xdk The Oracle XML Developer's Kit (Xdk) is not part of the Oracle Database Product Set.
Features and Restrictions ■ ■ PL/SQL File output is written to POSIX with ASCII-Data Format. For INSERT/UPDATE/DELETE operations the XML document must not contain . When using the JAVA-interfaces you must ensure the right charset of the data. For more information, refer to the encoding considerations listed in Chapter 12, "Java in the Database".
14 Oracle Management Agent 14 This chapter describes the Oracle Management Agent for BS2000/OSD and provides installation and configuration information. The reader is supposed to be familiar with Oracle Enterprise Manager. The Oracle Management Agent for BS2000/OSD is responsible for monitoring all components on the host computer. Once installed, the Oracle Management Agent knows how to monitor default target types, such as the Oracle Database.
Running the Installation Script The following table describes the parameters in the format: Parameter Description ORACLE_SID system identifier of the database ORACLE_HOME Oracle home directory under POSIX ORACLE_DATA user ID where the database files are stored Each database that should be monitored needs an entry in the oratab file.
Running the Agent Parameter Description EM-OMS-HOST The host name of the Oracle Management Server EM-OMS-HTTP-PORT The port of the Oracle Management Server To finalize the EM Agent installation login as root and execute the following script: $EMDROOT/root.sh The installation of the Management Agent, can also be operated by a background process.
Restrictions 14.4 Restrictions The following is a list of issues that might affect Oracle Enterprise Manager Agent ■ ■ ■ ■ ■ ■ Oracle Management Agent for BS2000/OSD can monitor servers that are running Oracle Database 10g or Oracle Database 11g. The Oracle Management Agent for BS2000/OSD does not support the SNMP framework. That means, the agent is not integrated within the EMANATE master agent for BS2000/OSD. The agent does not accept any SNMP requests and does not send any SNMP trap.
Troubleshooting Here you find the TSNs of the tasks involved in the PTHREADS application. You can connect to the PTHREADS application when you choose the TSN of the ORIG task as the input for the parameter TSN of the ITH-START procedure in the following format: /CALL-PROCEDURE $TSOS.SYSPRC.PTHREADS.013(ITH-START),(TSN=1MYQ) When you see the double slash prompt you can type CANCEL-THREADED-PROGRAM to cancel the PTHREADS application.
Troubleshooting 14-6 Oracle Database Installation and Administration Guide
15 Oracle on SQ Server 15 This chapter describes features, which are specific to Oracle Database for BS2000/OSD SQ Server: ■ Concepts ■ Definitions ■ Product Set ■ Hardware Requirements ■ Software Requirements ■ Address Space Limit ■ Installing Oracle Database Software ■ Database Creation ■ Upgrade and Migration ■ Administration ■ Oracle application programs ■ openUTM Product Set 15.
Definitions 15.2 Definitions Because there are two Oracle editions for BS2000, that is, one for the /390 series and one for the SQ series, the following definitions are introduced to avoid confusion: Oracle edition Meaning Oracle for BS2000/390: BS2000 line of Oracle, which is running on systems with /390 CPU's (S Servers). This Oracle line can also run on SQ Server, but only in the slower /390 mode, also called compatibility mode.
Oracle application programs Component Requirement Compilers Though not required to run the Oracle Database, if high-level languages, such as C or COBOL, are used to interface to the Oracle Database, then the following compilers are supported: COBOL85 V2.3 CCOBOL2000 V1.5 and higher CPP as of V3.1 openUTM openUTM V6.0 and higher CRTE CRTE V2.8 and higher 15.6 Address Space Limit A user's address space should not be less than 512 MB.
openUTM Product Set Application programs, which have been developed on /390 systems can run on SQ Servers without any changes. 15.12 openUTM Product Set The openUTM product set of Oracle Database 11g Release 2 (11.2) for SQ Server requires openUTM V6.0 and higher. There are no differences in developing Oracle Database/openUTM applications in comparison with the /390 edition of Oracle (refer to chapter "Using the Oracle Database under openUTM" in the Oracle Database User's Guide for Fujitsu BS2000/OSD).
A A Oracle Error Messages for BS2000/OSD This appendix lists Oracle Database 11g Release 2 for Fujitsu BS2000/OSD messages 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 detected the problem, and can include internal status codes, BS2000 system macro return codes, or both.
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 and the corresponding ILCS routine returned the error. Action: Ensure 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 the Oracle Support Services Representative.
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 block sizes. This may indicate an internal error and should not normally occur. Action: If you cannot identify the cause of the problem, then contact the Oracle Support Services Representative. ORA-05015: text file open failed Cause: An Oracle Database text or command file cannot be opened.
Cause: An attempt was made to read a block of an Oracle Database file that does not exist. For example, block number < 1 or > file size. This is an internal error and should not normally occur. Action: Contact the Oracle Support Services Representative. ORA-05023: file close failed Cause: The attempt to close an Oracle Database file failed. This is an internal error and should not normally occur. Action: Contact the Oracle Support Services Representative. ORA-05025: sfccf:file mismatch.
Action: Ensure that the ORAENV variable assignments are correct. If you cannot identify the cause of the problem, then contact the Oracle Support Services Representative. ORA-05033: bad environment values Cause: One or more of the values specified in the ORAENV file are invalid. Action: Ensure that you specified legal values in the ORAENV file, refer to the Appendix B, "Oracle Environment Variables" in this guide or Oracle Database User's Guide for Fujitsu BS2000/OSD for further information.
Cause: The archiver process was unexpectedly interrupted. Action: If you cannot identify the cause of the problem, then contact the Oracle Support Services Representative. ORA-05042: soarch: Buffer overflow Cause: The archiver process detected an internal buffer overflow. Action: If you cannot identify the cause of the problem, then contact the Oracle Support Services Representative. ORA-05043: Archive control string too long Cause: The archive control string is too long.
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 need to change the default value for the PGA_SIZE environment variable. Action: Use the default value for the PGA_SIZE environment variable. If this does not solve the problem, then contact the Oracle Support Services Representative.
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 run the STARTUP command. ORA-05064: cannot allocate SGA Cause: After creating the memory pool, the REQMP to allocate the space failed. This might be an operating system error. Action: If you cannot identify the cause of the problem, then contact the Oracle Support Services Representative.
ORA-05072: cannot enable post/wait item Cause: Probable operating system error. Action: Contact the Oracle Support Services Representative. ORA-05073: error in post Cause: An inter-process communication operation failed. Action: Check that the database and all required background tasks are running correctly. If you cannot identify the cause of the problem, then contact the Oracle Support Services Representative. ORA-05074: error in wait Cause: An inter-process communication operation failed.
Action: Re-link the UTM application. If the error persists, then contact the Oracle Support Services Representative. ORA-05103: generated TSKM too short Cause: The TSKM area was overwritten by the Oracle Database. Action: Change the parameter LTHTSKM in the KDCDB / KDCDBO macro. ORA-05104: generated TAM too short Cause: The TAM area was overwritten by the Oracle Database. Action: Change the parameter LTHTAM in the KDCDB / KDCDBO macro.
Action: Ensure that the ORALOAD link name identifies the correct ORALOAD library. Then restart the program. If you cannot identify the cause of the problem, then contact the Oracle Support Services Representative. ORA-05117: cannot attach to socket subsystem Cause: An application could not be bound to the sockets subsystem. Generally this message is preceded by a BLS-nnnn message from the operating system. Action: Contact the Oracle Support Services Representative.
Cause: In the start parameters there must be at least one open string for the Oracle Database. Action: Refer to Chapter 8, "openUTM Product Set" of this guide and correct the start parameters. ORA-05134: DBSTAT secondary opcode inconsistent Cause: System error. Action: Contact the Oracle Support Services Representative. ORA-05135: Error x Recover PTC-list, Instance y Cause: System error.
ORA-05143: Mismatch in TA for User(s) z Cause: In the UTM warmstart there is a mismatch between openUTM, and the Oracle Database instance(s), or both. Action: Clear the Oracle Database instance(s), create a new KDCDEF for openUTM and restart the openUTM application. ORA-05144: Error x at Prepare Transaction for User z, Instance y Cause: The preparation for committing a transaction in instance y is invalid. Action: Restart the UTM transaction.
Cause: In the start parameters for the Oracle Database there is a syntax error. Action: Refer to Chapter 8, "openUTM Product Set"and correct the start parameters. ORA-05155: Internal Error: malloc in dbstpa Cause: This error message indicates a system error. One of the possible reasons for this issue is that the system is out of memory. Action: Contact the Oracle Support Services Representative. ORA-05156: Internal Error: realloc in dbstpa Cause: This error message indicates a system error.
Action: You should not normally need to specify this variable, as the default value is correct. Contact the 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. Correct the value and restart the database.
Cause: The user-side stub module could not load the PRO/OCI module. In this case, the message is usually preceded by a BS2000 BLS-nnnn message, or the loaded module is incompatible with the version of the stub module. Action: Ensure that the ORALOAD link name exists and points to the current ORALOAD library. Re-link the application with the current link libraries. ORA-05191: symbol translation error for kernel memory pool Cause: The logical name translation for the kernel memory pool failed.
Action: If you cannot identify the cause of the problem, then contact the Oracle Support Services Representative.
A-18 Oracle Database Installation and Administration 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: PRINTPAR=print-options Classification: USER B.3.10 SQLPATH This variable specifies a path where SQL*Plus looks for command files. Elements of the path are separated by semicolons (;). For example: SQLPATH=PRIVATE;$ORAC1120 This assignment causes SQL*Plus to look for filename.SQL, then for PRIVATE.filename.SQL, and finally for $ORAC1120.filename.SQL. Format: SQLPATH=search-path Classification: USER, DBA B.3.
DBA Startup Variables B.4.2 BGJPAR This variable specifies the parameters for the ENTER-PROCEDURE command used when starting background jobs. The ENTER-PROCEDURE command is used to submit jobs as follows: .jobname ENTER-PROCEDURE jobfile, &BGJPAR Format: BGJPAR=parameters Classification: DBA Note: The BGJPAR variable is set up by the installation procedure. B.4.3 BGJPRC_UID / BGJPRC_SID These variables specify the user ID and orasid of the file for the background enter jobs.
DBA Startup Variables Syntax: sid is a string of at the most 4 alphanumeric characters userid is a string of at most 8 alphanumeric characters which follows the rules of a BS2000/OSD USER-ID Classification: DBA,USER, NET B.4.7 user_ACCOUNT/ user_PASSWORD user_ACCOUNT or user_PASSWORD define credentials of a USER-ID, which are used by the ENTER-PROCEDURE command to start a process.
DBA Startup Variables Classification: DBA Default: KNL_BASE=72M B.4.12 ORACLE_HOME The Oracle home directory is the directory in the POSIX file system which contains the installation of the software for a particular Oracle product. Format: ORACLE_HOME=/path-name Classification: DBA, USER B.4.13 PGA_BASE This variable specifies the base address of the fixed part of the PGA. The PGA is task-specific, but must be located at a fixed memory address so that the kernel can access it.
Oracle Net Services Variables B.4.16 SGA_BASE This variable gives the address where the SGA is mapped into memory, and must represent a megabyte-boundary. Format: SGA_BASE=address Classification: DBA Default: SGA_BASE=190M The value of SGA_BASE is read from the kernel if the shared kernel is already loaded. There is no corresponding SGA_SIZE variable; the size of the SGA memory pool is calculated when the database is started. Note: B.
Oracle Net Services Variables 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.
C C Initialization Parameters and the Parameter File Every time SQL*Plus starts an Oracle Database instance, it uses a set of parameters which specify the characteristics of the instance's operation. These parameters are kept in a file, typically named sid.DBS.INIT.ORA. This appendix lists unsupported parameters, and lists other parameters that you may need to change to customize the Oracle Database for the system.
Additional Notes on Initialization Parameters value for this parameter is the current BS2000 user ID of the Oracle background processes. You can specify a prefix for the trace and alert files in the following format: BACKGROUND_DUMP_DEST=BDD You can also specify a POSIX directory for this parameter, if you have enabled the POSIX subsystem.
Additional Notes on Initialization Parameters C.3.6 DB_FILES If you plan to create a large database, then you must set this value to the maximum of 2044 before creating the database. C.3.7 LOCK_SGA This parameter is ignored on Oracle Database 11g for BS2000/OSD. Buffers in the SGA are page fixed only during I/O operations. Otherwise, the SGA on BS2000 is pageable. C.3.8 SGA_MAX_SIZE This parameter should not be specified on Oracle Database 11g for BS2000/OSD.
Additional Notes on Initialization Parameters C-4 Oracle Database Installation and Administration Guide
D D Troubleshooting This section describes problems that you may encounter when using the Oracle Database 11g Release 2 on BS2000, and provides you with information about how to diagnose and overcome such problems. To solve a problem, identify the type of the problem and locate the relevant information in this appendix. Examine each of the listed points to find the cause of the problem. Carry out the suggested solution, and try again.
Problems Accessing the Database ■ Did you get an ORA-05032 error with no extra information? When you attempt to start a database and the startup fails, you sometimes get an ORA-05032 message and not much other information. This indicates that a problem occurred in a very early stage of the startup, when Oracle Database 11g error stack and backtracking mechanism was not yet active.
Problems Accessing the Database ■ Does the file exist? ■ Is the file accessible to the program which is trying to open it? ■ Is there a hardware problem? ■ Did you specify the correct block size? If you specified the ORAENV environment variable, SF_PBLKSIZE, at database creation, then you must continue to use the same specification whenever you run an ALTER DATABASE statement. D.3.
Problems Accessing the Database D-4 Oracle Database Installation and Administration Guide
E File Types and Names Used by Oracle E The following is a list of file types and names used by Oracle. sid.DBS.xxx.DBF Database files such as sid.DBS.CONTROL.DBF, sid.DBS.DATABASE1.DBF, or sid.DBS.LOG1.DBF contain the entire Oracle database including data dictionary, user tables, log files, and so on. sid.DBS.INIT.ORA Parameter file used when instance is started. sid.P.ORAENV Environment file containing user environment. Always to be run before start of an instance or an application: /DO sid.P.ORAENV. S.
L.sid.xxx.LOG To be removed after successful installation, for example, L.sid.CATALOG.LOG. ORAXALOG.tsn-NULL-YYMMDD.TRC This file is used to trace errors when openUTM is used with Oracle. This file is created only when an error occurs. NULL can be replaced by a db_name when specified in the open string.
Index A E Address Space, 2-5 administration utility SQL*Plus, 5-1 Architecture Oracle Server, 2-1 Archiving, 1-4 AUDIT_FILE_DEST, C-2 EE8BS2000, 12-2 Environment Definition File, 2-6 Environment variables BGJPAR, 7-1, B-6 CLN_BASE, B-3 CLN_MPID, B-3 DEFAULT_CONNECTION, B-3 EXP_CLIB_FILE_IO, B-3 IMP_CLIB_FILE_IO, B-4 JOBID, B-7 KNL_BASE, B-7 LOGNAME, B-2 NLS_LANG, B-4 OPS_JID, B-4 ORAUID, B-2 PGA_BASE, B-8 PGA_SIZE, B-8 PGM, B-2 PRINTPAR, B-4 SF_PBLKSIZE, B-8 SGA_BASE, B-9 SQLPATH, B-5 SSSIDPWF, B-5 TERM,
G MAX_SHARED_SERVERS, 9-4 Messages, A-1 Modifying INIT.ORA, 4-6 Globalization Support, 1-4 GLOGIN.SQL, 5-3 N H NLS_LANG, HOST, 5-2 O I IMP_CLIB_FILE_IO, B-4 Import, 1-4 Initialization parameters CIRCUITS, 9-4 DB_FILE_MULTIBLOCK_READ_COUNT, C-2 DB_FILES, C-3 DISPATCHERS, 9-4 INIT.ORA file, C-1 LOCAL_LISTENER, 9-4 MAX_DISPATCHERS, 9-4 MAX_SHARED_SERVERS, 9-4 SHARED_SERVER_SESSIONS, 9-4 SHARED_SERVERS, 9-4 INIT.
S.E.tsn.YYYY-MM-DD.hh.mm.ss, E-1 SF_PBLKSIZE, B-8 SGA_BASE, B-9 SGA_MAX_SIZE, C-3 shared code pool, B-7 SHARED_SERVER_SESSIONS, 9-4 SHARED_SERVERS, 9-4 sid_BGJPAR, B-6 SID_LIST_LISTENER, 5-5 sid_USER, B-6 sid.DBS.INIT.ORA, E-1 sid.DBS.xxx.DBF, E-1 sid.P.ORAENV, E-1 S.OUT.tsn.YYYY-MM-DD.hhmmss, E-1 SPFILE, 2-3, 5-4 SQ130, 15-1 SQL*Net TCP/IP, 1-5 SQL*Plus, 1-4, 5-1 and INIT.
Index-4
