SAP R/3在UNIX系统上安装指南与Oracle数据库集成

需积分: 9 197 浏览量更新于2024-07-31 收藏 1.46MB PDF 举报

本资源是一份名为《SAP® AG神经特斯特拉.16，D-69190沃尔夫拉德 R/3在UNIX上的安装指南》的文档，由SAP AG于2001年4月发布。这份安装指南专注于R/3（SAP企业资源规划系统）在基于Oracle数据库的UNIX环境下的安装过程，适用于Oracle Database Release 4.6 CSR2版本。它详细地阐述了如何在UNIX操作系统环境下进行SAP R/3的部署，包括软件配置、依赖项安装以及可能遇到的问题解决方案。版权方面，所有权利归SAP AG所有，未经其明确许可，不得复制或以任何形式传播该文档。同时，指南中提到的部分软件产品如Microsoft的Windows、NT、Excel、Word和SQL Server，IBM的DB2、OS/2等都是各自公司的注册商标。文档强调，某些SAP AG及其分销商提供的软件产品包含来自其他软件供应商的专有软件组件，如Oracle的Oracle Database和Informix的特定技术。此外，还提到了与UNIX相关的术语，如UNIX、X/Open、OSF/1和Motif，这些都是The Open Group的注册商标，以及用于SAP集成的HTML、DHTML、XML和XHTML等Web技术。这份安装指南旨在为用户提供一个清晰、全面的指导，帮助用户在UNIX平台上顺利进行SAP R/3的安装和配置。它可能包括了系统需求分析、安装步骤、数据库连接设置、用户权限管理、系统配置参数调整等内容，确保了在遵循版权法律的前提下，提供了实用的技术支持和最佳实践。对于IT专业人员和希望部署SAP R/3的组织来说，这份文档是不可或缺的参考资料。

Standard SAP System Installation SAP AG

16 April 2001

• Configuring the domain controller in the Transport Management System (TMS)

• Calling the System Administration Assistant transaction (SSAA)

• Configuring the instance profiles after the installation

• Performing a full backup of the installation

− Optional Tasks

• Performing operating system adjustments

• Performing file and directory adjustments

• Performing application-specific actions

• Installing the SAP Internet Solution

For more information, see Post-Installation Activities [page 113].

SAP AG 1 Installation Planning

1.1 System Configuration

April 2001 17

1 Installation Planning

Purpose

Before you begin with the practical installation tasks, it is essential to have a planning phase.

in which you make a number of fundamental decisions that influence the subsequent

installation procedure. Careful planning is a prerequisite for the successful installation of the

system.

Process Flow

When you plan the installation you have to:

• Decide on the optimal configuration for the system

• Work out how the software components must be distributed to disks

• Make sure that you can meet the hardware and software requirements specified by SAP

SAP specifies minimal hardware and software requirements for different system

configurations to make sure that a newly installed system performs well. These

requirements are summarized in the hardware and software requirements checklists.

In your planning stage, it is essential to consult the Hardware and Software

Requirements Check [page 27] to find out the requirements and to make sure that they

can be met.

Read the installation notes before beginning the installation. These notes

contain the most recent information regarding the installation, as well as

corrections to the installation documentation. See the table of installation

notes [page 9].

1.1 System Configuration

The configuration of the system is generally planned well in advance of the installation

together with the hardware vendor. Configuration planning involves deciding whether a

central system or standalone database system is to be installed, and how many dialog

instances are required.

The configuration is worked out with the hardware partner on the basis of sizing information

that reflects the system workload. Details such as the set of applications that are to be

deployed, how intensively these are to be used, and the number of users enable the

hardware vendor to recommend a configuration that performs well.

An SAP System consists of a database server, (optional) additional application servers, and a

number of frontend computers. The graphic below shows a typical distribution of the

instances of an SAP System over several computers.

The database server is the computer on which the database is installed. It is named

DBSERVER in the graphic. This server can also accommodate the central instance (the SAP

instance that includes the message server and enqueue server processes). If the central

instance is installed on a separate application server, the database server is called a

standalone database server.

Additional dialog instances (SAP instances including only dialog, batch, spool, or update

processes) are installed on application servers. These servers are named D1 and D2 in the

graphic.

SAP AG 1 Installation Planning

1.2 Distribution of Components to Disks

April 2001 19

1.2 Distribution of Components to Disks

Purpose

The way files are distributed to disk significantly affects system throughput and data security,

and must therefore be carefully planned. The best distribution depends on your specific

environment and must take into consideration factors such as the size of the components

involved, security requirements and the expected workload. A good distribution of files to

disks ensures that:

• Enough free space is available for system growth

• The data is secure

• Performance is good

When you work out the assignment of components to disks, you first need to get an overview

of the main components and their corresponding directories. Then, on the basis of sample

configurations and the recommendations provided in this documentation, you can decide

which assignment is best for your particular system.

• Customer Database Copy

If your own database export instead of the standard SAP database export

from CD-ROM will be used for the database load, refer to the

documentation R/3 Homogeneous System Copy.

• Very Large Database (VLDB)

See Database Modifications for Very Large Databases [page 142] first if

you expect one of the following:

- A large amount of data (> 40 GB)

- A large number of users ( > 300 users)

- A large number of daily log files (> 1 GB)

- A large number of transactions per hour (> 100,000)

Contact a certified installation organization or a basis consultant if you

expect to use a very large database.

Process Flow

There is no single solution or any definite rules for the file distribution. To help you work out a

good solution that suits your particular environment, the following topics cover important

issues concerning Oracle file system configuration.

Oracle Redo Log Files

There are four groups of Oracle transaction log files (redo log files). By default, each group

contains one original and one mirrored redo log file. If you choose mirroring by UNIX, each

group will consist of one original redo log file only.

1 Installation Planning SAP AG

1.2 Distribution of Components to Disks

20 April 2001

Group Redo Log File

Group 101 (redo1)

/oracle/<SAPSID>/origlogA/log_g101m1.dbf

/oracle/<SAPSID>/mirrlogA/log_g101m2.dbf

Group 102 (redo2)

/oracle/<SAPSID>/origlogB/log_g102m1.dbf

/oracle/<SAPSID>/mirrlogB/log_g102m2.dbf

Group 103 (redo3)

/oracle/<SAPSID>/origlogA/log_g103m1.dbf

/oracle/<SAPSID>/mirrlogA/log_g103m2.dbf

Group 104 (redo4)

/oracle/<SAPSID>/origlogB/log_g104m1.dbf

/oracle/<SAPSID>/mirrlogB/log_g104m2.dbf

The log files are periodically written from redo log log_g101m?.dbf to redo log

log_tg104m?.dbf and are archived if the file reaches its maximum size (20 MB), provided

the database is running in archive log mode.

If you consider the sets of Oracle transaction log files

• Set A: /oracle/<SAPSID>/*logA/log*

• Set B: /oracle/<SAPSID>/*logB/log*

the redo log that is archived and the redo log that is written always belong to different sets.

For better performance, the following file systems should be located on different disks:

/oracle/<SAPSID>/origlogA

/oracle/<SAPSID>/mirrlogA

/oracle/<SAPSID>/origlogB

/oracle/<SAPSID>/mirrlogB

Security Issues

• For data security reasons, the redo logs should be mirrored on different disks. This can

be achieved either by Oracle, by the hardware, or by the operating system.

• A production system must run in archive log mode.

• If a test system does not run in archive log mode, data written since the last complete

backup will be lost after a system crash.

Performance Issues

• Store database files and redo logs on different disks, and arrange the redo log files as

described above. Since the redo logs are written synchronously, they cause more I/O

activity than any other database files.

• It is possible to store the redo logs on the same disk as /sapmnt or /oracle/stage.

• Use the file systems /oracle/<SAPSID>/sapdata<n> exclusively for data files of the

database.

• The block size of the file system must be less than or equal to the Oracle block size,

which is 8 KB.

剩余224页未读，继续阅读

w32508

粉丝: 1
资源: 7

SAP R/3在UNIX系统上安装指南与Oracle数据库集成

SAP-IDES4.7中文虚拟机下载地址和详细配置信息图文

最新SAP IDES ECC6.0(服务器+客户端+语言包)完整下载全系统安装包种子下载

sap ides install

IDES SAP SEM 4.0SAP BW 3.50 install_guide

SAP IDES安装

学习SAP IDES的IDES模型介绍

SAP IDES中SPFLI表中生成数据.rar_SAP IDES中SPFLI表中生成数据_SAPSPFLI

SAP IDES的手册

sap ides安装手册

SAP IDES模型资料

最新资源