Skip Headers

Oracle8i Server Installation and Database Administration Guide
Release 3 (8.1.7) for Fujitsu Siemens Computers BS2000/OSD

Part Number A95466-01
Go To Table Of Contents
Go To Index

Go to previous page Go to next page

Oracle Server on SR2000

This chapter describes those features, which are specific for Oracle on Business Server SR2000.

The topics described include:


With Oracle Server Release Oracle supports the BS2000 RISC Hardware "Business Server SR2000" and the BS2000 Operating System "OSD-Server Value
Package " (= OSD-SVP)

Oracle for SR2000 is running completely in native RISC mode.
Programs running in this mode provide much better performance than programs running in /390 mode (= compatibility mode).

Oracle for SR2000 is very flexible regarding the run mode of Oracle applications. You can run your database applications in /390 mode or native RISC mode.
There are no differences in handling and administration compared to the "conventional" Oracle for BS2000 (on /390 machines).
So the migration from conventional Oracle for BS2000 to Oracle for SR2000 is very simple.

All products you know from the /390 port of Oracle (e.g. Net8, SQL*Plus, Precompilers) are available in RISC mode for the SR2000.


Because there are two Oracle ports for BS2000 (i.e. one for the /390 series and one for the RISC series), we will introduce some definitions in order to avoid confusion:

Oracle port Meaning

Oracle for BS2000/390:

BS2000 port of Oracle, which is running on machines with /390 CPU's.
This Oracle port can also run on SR2000, but only in the slower /390 mode ("compatibility mode").


"/390 port of Oracle(BS2000)"

Oracle for BS2000/RISC:

BS2000 port of Oracle, which is running in native RISC mode on machines with RISC CPU's.
This Oracle port can't run on /390 CPU's.


"RISC port of Oracle(BS2000)"
"Oracle for Business Server SR2000"
"Oracle for SR2000"

Product Set

All products which are available with the /390 port of Oracle (BS2000) are also available with Oracle for SR2000. (see product list in Chapter 1). There are no differences in functionality and production status between the products of these two Oracle/BS2000 ports.

The release numbers of the products of the two Oracle/BS2000 ports are identical with the exception of the last digit:

".10":   Oracle /390 port
".15": Oracle RISC port

for example:

Oracle8i Release 3 Server (/390 port):
Oracle8i Release 3 Server (RISC port):

Hardware requirements

Business Server SR2000

Main memory: at least 128 MB

Disk Space:

Database Space

Software requirements

Component Requirement

Operating System

OSD-Server Value Package V3.0,
Korrekturpaket 2/00 (incl. REP A0446872 and SINIX-2000 807);
OSD-Server Value Package V4.0,
(OSD-Server Value Package includes SDF, EDT, LMS, CRTE,
HSMS with ARCHIVE, DCAM with Sockets, ...)


Though not required to run the Oracle Server, if high-level languages (such as C or COBOL) are used to interface to the Oracle Server, the following compilers are supported:


V2.2, V2.3




V2.2C, V3.0


V2.2C, V3.0



V4.0, V5.0, V5.1






Communication System

openNet Server V2 including BCAM V16 and Sockets V2.

Address Space Limit

A user's address space should not be less than 128MB.

We recommend to load the RISC version of BS2000 DSSM "CRTE-BASYS"
(= CRTEBASR) to reduce memory requirements.

Installing Oracle Server Software

There are almost no differences in installing the Oracle Server Software compared to the /390 port of Oracle:

  1. The BS2000 System Administrator needs to create the Oracle installation userid, the userid under which you want the Oracle Server 8.1.7 software to reside. Throughout these release notes we refer to this userid as "$ORACL817". This userid does not require any special BS2000 privileges and should have at least 250 000 PAM pages free.

  2. LOGON under your installation userid ($ORACL817).

  3. Oracle for SR2000 is distributed on CD-ROM. Use ARCHIVE to load the contents of the CD-ROM:

    FILES NAME=($O817RISC.,RENAME=$userid.)

    "volser" is the Volume Serial Number of the CD-ROM (="ORACL1").
    CD-ROM drive has device type "T9G".

    The "RENAME=$userid" parameter is used to specify the installation userid ($ORACL817).

  4. Review the .DOC files transferred from the installation CD-ROM, especially the README.DOC file. These text files serve as an online supplement to the printed documentation and provide up-to-date information on this release.

  5. Execute the install procedure as follows:


where $userid is your current installation userid.

This procedure applies the necessary changes to a number of command files. If any problems occur, you should inspect the log file and perform any relevant actions.

Database Creation

The creation of a database works exactly as described in the Chapter 4, "Creating/Migrating a Database". You may create a database automatically (by BS2000 procedure INSTALL.P.SUPER) or manually.

There are no differences to the /390 port of Oracle for BS2000.


see Chapter 4, "Creating/Migrating a Database"


There are no differences in administration to the /390 port of Oracle Server.

Oracle application programs

Oracle for SR2000 supports the same programming languages for Oracle application programs as the /390 port of Oracle. There are Precompilers for C/C++ and Cobol.

Oracle application programs can run on SR2000 in /390 mode or RISC mode.

Your Oracle application programs must run in two-task mode.

/390 mode applications

Application programs running in /390 mode have to be linked as described in the "User's Guide".

C application programs which have been developed on /390 machines can run on SR2000 without any changes (in /390 mode). But application programs written in Cobol must be re-linked with "Oracle on SR2000" libraries, when you migrate from BS2000 /390 machines to SR2000.

RISC mode applications

BS2000 compilers CPP-R 2.2C and CPP-R 3.0 are able to generate RISC code.

So application programs written in C/C++ can also run in native RISC mode.

C application programs, which should run in native RISC mode have to be linked as described in the "User's Guide", but using the Oracle RISC libraries ORASQL.LIB.RISC and PRO.C.LIB.RISC in your installation userid ($ORACL817).

For linking RISC mode applications you need IRS library V1.7.

UTM Product Set

The UTM product set of Oracle on SR2000 requires openUTM V4.0,
openUTM V5.0 or openUTM V5.1.

There are no differences in developing Oracle/UTM applications in comparison with the /390 port of Oracle (see chapter "Using the Oracle Server under openUTM" in the Oracle8i for Fujitsu Siemens BS2000/OSD User's Guide).

You have to re-link Oracle/UTM application programs, when you migrate from /390 machines to SR2000. Oracle/UTM application programs have to be linked with CRTE V2.3.

Your Oracle/UTM application must run in two-task mode.

Go to previous page Go to next page
Copyright © 2001 Oracle Corporation.

All Rights Reserved.
Go To Table Of Contents
Go To Index