当前位置：文档之家 › SAP Oracle 11g升级文档(整理版)

SAP Oracle 11g升级文档(整理版)

  • 格式：doc
  • 大小：2.24 MB
  • 文档页数：39

SAP Oracle 11g升级文档1.操作系统检查 (2)1.1检查操作系统版本 (2)1.2检查安装包 (2)1.3检查C++运行环境 (2)1.4其他操作系统检查 (2)1.5检查当前数据库版本 (3)2.安装前准备 (3)2.1 用户,组等权限检查 (3)2.2 创建目录并解压ORACLE介质 (3)2.3 更新安装脚本 (4)2.4 检查脚本 (4)3 安装Oracle软件 (5)3.1 设置环境变量，进行软件安装 (5)3.2 安装Opatch (15)3.3 更新Listener和tnsnames文件 (16)3.4 执行升级前脚本检查 (17)4.正式开始数据库升级 (18)4.1停止数据库 (18)4.2修改文件/etc/oratab (18)4.3启动DBUA进行升级 (19)5.升级后后续操作 (27)5.1 修改orabid用户环境变量 (27)5.2检查升级后的数据库 (28)5.3进行数据字典和系统表空间状态更新 (29)5.4数据参数修改 (29)5.5数据库状态更新 (31)5.6运行Post UPGRADE 脚本 (31)5.7创建数据共享包之间的连接 (31)5.8启动数据库Listener (31)5.9备份原有的oracle bin 目录 (32)5.10修改ORACLE_HOME目录给bidadm用户的权限 (32)5.11更新Oracle Client (32)5.12修改orabid以及bidadm用户下的Oracle client相关信息 (33)5.13更新JDBC驱动程序路径 (34)6.启动SAP系统 (39)1.操作系统检查1.1检查操作系统版本(Oracle 11g要求操作系统版本高于6100-02-05)执行命令: oslevel -s1.2检查安装包执行以下命令检查安装包:‘lslpp –l |grep bos.adt.base‘lslpp –l |grep bos.adt.lib‘lslpp –l |grep bos.adt.libm‘lslpp –l |grep bos.perf.libperfstat‘lslpp –l |grep bos.perf.perfstat‘lslpp –l |grep bos.perf.proctools1.3检查C++运行环境执行命令:’ lslpp –l |grep xlC.aix (版本要求大于等于: 10.1.0.0)1.4其他操作系统检查内存检查，需要大于1G,执行命令: lsattr –El mem0/tmp文件系统需要有大于1G空余空间,执行命令: df –g /tmp检查swap空间,执行命令: lsps –a ，要求交换页空间至少大于20GB 检查ORACLE_HOME,应该有剩余15G空间,命令: df –g /oracle/BID1.5检查当前数据库版本执行语句: ‘select version from v$instance;2.安装前准备2.1 用户,组等权限检查检查写入权限，执行以下语句:‘cd $ORACLE_BASE‘touch $ORACLE_HOME/write_test‘rm $ORACLE_HOME/write_test设置umask2.2 创建目录并解压ORACLE介质创建目录解压目录: mkdir /oracle/stage/11202检查/oracle/stage空间,执行df –g /oracle/stage ,要求空间至少有10GB的空余空间扩充空间，执行命令: chfs –a size=+6G /oracle/stage解压Oracle介质执行命令:’SAPCAR –xvf /setupcd/BW_OPT_CD/51040503_ORACLE_RDBMS11G202/OR111264.SAR ’SAPCAR –xvf /setupcd/BW_OPT_CD/51040503_ORACLE_RDBMS11G202/OR211264.SAR ’SAPCAR –xvf /setupcd/BW_OPT_CD/51040503_ORACLE_RDBMS11G202/OR311264.SAR ’SAPCAR –xvf /setupcd/BW_OPT_CD/51040503_ORACLE_RDBMS11G202/OR411264.SAR ’SAPCAR –xvf /setupcd/BW_OPT_CD/51040503_ORACLE_RDBMS11G202/OR511264.SAR检查Inventtory文件,执行命令cd /etc , more oraInst.loc2.3 更新安装脚本2.4 检查脚本使用root用户登陆,切换到目录:/oracle/stage/11202/database, 执行脚本rootpre.sh:使用orabid登陆,进行安装前检查，切换到目录cd /oracle/stage/11202/database,执行脚本./runInstaller -executeSysPrereqs设置DISPLAY环境变量，运行./RUNINSTALLER_CHECK3 安装Oracle软件3.1 设置环境变量，进行软件安装设置以下环境变量:unsetenv TWO_TASKunsetenv ORA_NLSunsetenv ORA_MLS32unsetenv ORA_NLS32unsetenv ORA_NLS33unsetenv ORA_NLS10umask 022setenv DISPLAY XX.XX.XX.XX:1.0setenv ORACLE_HOME_SRC /oracle/BWQ/112_64setenv ORACLE_HOME_TGT /oracle/BWQ/11203setenv LIBPATH $ORACLE_HOME/lib:$LIBPATHxclock备份文件切换到目录cd /oracle/stage/11202/database/SAP, 准备开始数据库软件安装:启动RUNINSTALLER进行安装cd /oracle/stage/11202/database/SAPxclock./RUNINSTALLER报错：检查日志:参照Note: 1431796 ，执行以下语句重新启动安装软件: ./RUNINSTALLER -nocheck 启动界面开始:保持默认，点击”Next”点击”Yes”保持默认，点击”Next”保持默认，点击”Next”保持默认，点击”Next”保持默认，点击”Next”保持默认，设置Software Location: /oracle/BID/11202,点击”Next”保持默认，点击”Next”保持默认，点击”Install”查看安装进度重新打开窗口以root用户登陆执行脚本:点击Close退出3.2 安装Opatch更新opatch脚本:注意设置环境变量: setenv ORACLE_HOME /oracle/BWQ/11203 -----------省略以下步骤：------检查包安装先决条件--------------------省略-------------------------以root用户登陆,执行slibclean使用用户orabid登陆,切换到目录: /oracle/BID/11202/MOPatch执行以下命令: /oracle/BID/11202/MOPatch/mopatch.sh -v -s /setupcd/BW_OPT_CD/SAP_112023_201108_AIX.zip查看命令执行结果,到目录:/oracle/BID/11202/cfgtoollogs/mopatch 查看日志文件3.3 更新Listener和tnsnames文件拷贝admin下的文件到新目录:‘cd /oracle/BID/102_64/network/admin‘cp –rp * /oracle/BID/11202/network/admin修改listener.ora中的ORACLE_HOME添加语句ADR_BASE_LISTENER = /oracle/BWD/saptrace3.4 执行升级前脚本检查切换到用户orabid, 切换到目录:cd /setupcd/BW_OPT_CD/SAP_112023_201108/9584028/files/sap/ora_upgrade/pre_upgrade运行脚本: @pre_upgrade_status.sql,脚本路径:/setupcd/BW_OPT_CD/SAP_112023_201108/9584028/files/sap/ora_upgrade/pre_upgrade执行脚本pre_upgrade_tasks.sql执行: @/setupcd/BW_OPT_CD/SAP_112023_201108/9584028/files/sap/ora_upgrade/pre_upgrade/pre _upgrade_tasks.sql4.正式开始数据库升级4.1停止数据库执行命令: shutdown immediate;停止listener, 执行命令：lsnrctl stop4.2修改文件/etc/oratab在文件中添加以下行:‘vi /etc/oratab‘BID:/oracle/BID/102_64:N4.3启动DBUA进行升级设置环境变量:‘setenv ORACLE_HOME_SRC /oracle/BWQ/112_64‘setenv ORACLE_HOME_TGT /oracle/BWQ/11203‘setenv DISPLAY XX.XX.XX.XX:1.0直接执行以下脚本:‘sh/setupcd/BW_OPT_CD/SAP_112023_201108/9584028/files/sap/ora_upgrade/post_upgra de/dbua.sap.sh点击”Next”点击”Next”点击”Next”点击”Next”取消勾选”Specify Fast Recovery Area”，点击”Next”取消勾选”Configure the database with Enterprise Manager”，点击”Next”确认信息，点击”Finish”开始进行数据库升级点击”OK”点击”Close”5.升级后后续操作5.1修改orabid用户环境变量切换到目录: /oracle/BID,执行命令：‘cp .dbenv_libbid.csh .dbenv_libbid.csh.10g‘cp .dbenv_libbid.sh .dbenv_libbid.sh.10g修改.dbenv_lgbbid.csh修改文件.dbenv_lgbbid.sh5.2检查升级后的数据库启动数据库,执行以下脚本:/setupcd/BW_OPT_CD/SAP_112023_201108/9584028/files/sap/ora_upgrade/post_u pgrade/post_upgrade_checks.sql重点关注以下输出信息:查看Compatible参数:5.3进行数据字典和系统表空间状态更新执行语句:‘brconnect –u / -c –f stats –t system_stats‘brconnect –u / -c –f stats –t oradict_stats 5.4数据参数修改参照Note 1431798alter system reset BACKGROUND_DUMP_DEST scope = spfile sid = '*';alter system reset OPTIMIZER_INDEX_CACHING scope = spfile sid = '*';alter system reset OPTIMIZER_INDEX_COST_ADJ scope = spfile sid = '*';alter system reset OPTIMIZER_MODE scope = spfile sid = '*';alter system reset USER_DUMP_DEST scope = spfile sid = '*'alter system reset COMMIT_LOGGING scope = spfile sid = '*';alter system reset COMMIT_WAIT scope = spfile sid = '*';alter system reset COMMIT_WRITE scope = spfile sid = '*';alter system reset NLS_LENGTH_SEMANTICS scope = spfile sid = '*';alter system reset NLS_LENGTH_SEMANTICS scope = spfile sid = '*';alter system reset DB_FILE_MULTIBLOCK_READ_COUNT scope = spfile sid = '*';alter system reset CORE_DUMP_DEST scope = spfile sid = '*';alter system set AUDIT_FILE_DEST='/oracle/BID/11202/saptrace/audit' scope = spfile;alter system set DB_BLOCK_SIZE =8192 scope = spfile;alter system set DIAGNOSTIC_DEST ='/oracle/BID/11202/saptrace' scope = spfile;alter system set DB_NAME ='BID' scope = spfile;alter system set FILESYSTEMIO_OPTIONS ='SETALL' scope = spfile;alter system set LOG_ARCHIVE_DEST_1='/oracle/BID/oraarch/BIDarch' scope = spfile;alter system set LOG_ARCHIVE_FORMAT ='%t_%s_%r.dbf' scope = spfile;alter system set LOG_CHECKPOINTS_TO_ALERT=true scope = spfile;alter system set MAX_DUMP_FILE_SIZE=20000 scope = spfile;alter system set OPEN_CURSORS=800 scope = spfile;alter system set OPTIMIZER_DYNAMIC_SAMPLING=6 scope = spfile;alter system set CONTROL_FILE_RECORD_KEEP_TIME=30 scope = spfile;alter system set PARALLEL_EXECUTION_MESSAGE_SIZE=16384 scope = spfile;alter system set PARALLEL_MAX_SERVERS=40 scope = spfile;alter system set PARALLEL_THREADS_PER_CPU=1 scope = spfile;alter system set PROCESSES = 300 scope = spfile;alter system set SESSIONS = 600 scope = spfile;alter system set QUERY_REWRITE_ENABLED=FALSE scope = spfile;alter system set RECYCLEBIN =OFF scope = spfile;alter system set REMOTE_OS_AUTHENT = TRUE scope = spfile;alter system set REPLICATION_DEPENDENCY_TRACKING=FALSE scope = spfile;alter system set STAR_TRANSFORMATION_ENABLED = TRUE scope = spfile;alter system set "_B_TREE_BITMAP_PLANS"=FALSE scope = spfile;alter system set "_FIRST_SPARE_PARAMETER"=1 scope = spfile;alter system set "_MUTEX_WAIT_TIME"=10 scope = spfile;alter system set "_MUTEX_WAIT_SCHEME"=1 scope = spfile;alter system set "_OPTIM_PEEK_USER_BINDS"=FALSE scope = spfile;alter system set "_OPTIMIZER_ADAPTIVE_CURSOR_SHARING"=FALSE scope = spfile;alter system set "_OPTIMIZER_EXTENDED_CURSOR_SHARING_REL"=NONE scope = spfile;alter system set "_OPTIMIZER_USE_FEEDBACK"=FALSE scope = spfile;5.5数据库状态更新‘brconnect –c –u / -f stats –t all –f collect –p 45.6运行Post UPGRADE 脚本执行以下脚本：/setupcd/BW_OPT_CD/SAP_112023_201108/9584028/files/sap/ora_upgrade/post_u pgrade/post_upgrade_status.sql5.7创建数据共享包之间的连接切换到用户orabid, 切换到目录: /oracle/BID/11202/lib,执行以下命令:‘cd /oracle/BID/11202/lib‘ln –s libnnz11.so libnnz10.so5.8启动数据库Listener执行命令: lsnrctl start5.9备份原有的oracle bin 目录‘cd /oracle/BID/102_64‘mv /oracle/BID/102_64/bin /oracle/BID/102_64/bin-old5.10修改ORACLE_HOME目录给bidadm用户的权限‘chmod 755 $ORACLE_HOME5.11更新Oracle Client创建Client存放目录,路径:’cd /oracle/client‘mkdir 11x_64切换到新建目录并接压文件‘cd /oracle/client/11x_64‘SAPCAR –xvf /setupcd/11GCLIENT/OCL_AIX_PPC64/OCL11264.SAR创建Link‘ln –s /oracle/client/11x_64/instantclient_11202 instantclient‘ls –alrt5.12修改orabid以及bidadm用户下的Oracle client相关信息升级完成oracle client以后,修改orabid环境变量,修改文件/oracle/BID .dbenv_lgbbid.sh, .dbenv_lgbbid.csh下的ORACLE_CLIENT路径修改bidadm用户的环境变量备份环境变量，切换到目录: /home/bidadm‘ cp .dbenv_ligbbid.sh .dbenv_lgbbid.sh.10g‘ cp .dbenv_ligbbid.csh .dbenv_lgbbid.csh.10g修改/home/bidadm 下的.dbenv_lgbbid.sh中的ORACLE_HOME 和ORACLE_CLIENT 修改/home/bidadm 下的.dbenv_lgbbid.sh同时修改bidadm用户/home/bidadm 下的文件: .dbenv_lgbbid.sh , .dbenv_lgbbid.csh下的ORACLE_CLIENT路径5.13更新JDBC驱动程序路径修改Configtool中的JDBC路径：修改config.properites中的rdbms.driverLocation路径启动configtool.sh点击” Switch to configuration editor mode”修改cluster_data/dispatcher/IDXXXX/kernel/propertysheet.ConfigurationManager 修改cluster_data/server/IDXXXX/kernel/propertysheet.ConfigurationManager登陆SAP GUI,执行事务码RZ10修改bootstrap.properties切换到目录: /usr/sap/BID/DVEBMGS00/j2ee/cluster/bootstrap 修改文件bootstrap.properties中的rdbms.driverLocation路径修改SDM中的路径切换到路径: /usr/sap/BID/DVEBMGS00/SDM/program/config 修改”Driver Paths”中的路径修改rdb中的oracle client路径切换到路径/usr/sap/BID/DVEBMGS00/j2ee/deploying修改rdbms.driverLocation路径修改temp中的oracle client路径切换到路径/usr/sap/BID/DVEBMGS00/j2ee修改文件: templateconfigurator.properties中的RDBMS_DRIVER_LOCATION6.启动SAP系统执行命令: R3trans –dx执行命令: startsap r3。

合集下载

Oracle Solaris Cluster for SAP 配置指南说明书

Oracle Solaris Cluster for SAP 配置指南说明书

Oracle Solaris Cluster for SAP Configuration GuideSolaris Cluster 3.3 3/13 and 4.xO R A C L E W H I T E P A P E R | M A Y 2016DisclaimerThe following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.Table of ContentsDisclaimer 11. Introduction 22. Oracle Solaris Cluster Framework and Data Services 33. SAP Scenarios 44. Oracle Solaris Cluster Geographic Edition 55. Licensing Information 56. References 51. IntroductionThe global economy offers unprecedented opportunity for companies to increase customers and revenue, but there is a downside from an IT point of view. Systems must be continuously available. The Oracle Solaris operating system includes features such as predictive self healing and fault manager that are designed to keep system and applications up and running, even if there is a hardware failure. Oracle Solaris Cluster software protects against system failure for even higher availability. In the SAP environment, high availability (HA) is very important as most SAP products are business critical and must stay always up and running. This configuration guide is intended to help identify the Oracle Solaris Cluster Data Service for SAP products that provide high availability for common SAP implementation scenarios.Oracle Solaris Cluster is a high availability cluster software product for the Oracle Solaris operating system. It is used to improve the availability of hardware and software services, by having redundant computers (known as cluster nodes), the Solaris Cluster framework software, and cluster data services (known as agents) for the applications to provide high availability. Applications are administrated and monitored in resource groups which consist of one or more resources. Resource groups can be configured as fail over, scalable, or multiple masters, depending on the application requirements.Oracle Solaris Cluster provides extended support for Oracle Solaris Zones, enabling server consolidation in HA environment. These virtualization capabilities allow scalable, multiple masters or failover applications and associated Oracle Solaris Cluster data services to run unmodified within zone clusters. Zone clusters on Oracle Solaris Cluster provide administrative isolation with full service protection through fine-grained monitoring of applications, policy-based restart, and fail over within a virtual cluster. This type of environment offers multiple layers of availability. For example, a failed application can be configured to first try to restart in its zone. If the restart fails, it can attempt to start in another zone using Oracle Solaris Cluster failover capability. If this fails again, it can attempt to reboot the zone using Oracle Solaris Cluster framework and start the application after the zone is rebooted.The Oracle Solaris Cluster Geographic Edition provides Disaster Recovery feature. For more information see chapter 4.2. Oracle Solaris Cluster Framework and Data ServicesOracle Solaris Cluster Framework and Data Services can be used to improve the availability of SAP components running on Oracle Solaris operating system. It eliminates every single point of failure (SPOF) in the system. All tiers of a SAP system can be consolidated within a Oracle Solaris cluster environment, enabling a single point of management with data services for database instance(s), Standalone Central Service instance(s), Enqueue Replication server instance(s), Primary and Additional Application Server instance(s), and liveCache instance(s). The earlier SAP version with Central Instance is also supported on Solaris Cluster.The following is a list of useful Solaris Cluster Data Services in SAP environments:» Oracle Solaris Cluster Data Service for SAP NetWeaver –This agent supports SAP Standalone Central Services instance(s), Enqueue Replication server instance(s), Primary and Additional Application Server instance(s), and earlier SAP versions with Central Instance. The Additional Application Server instances can be configured as multiple master resources, which may run on multiple cluster nodes at the same time, or as failover resources which run on one node only. All other instances are to be configured as failover resources.» Oracle Solaris Cluster Data Service for Oracle Database -This agent supports Oracle database single instance configuration. The Oracle database runs on one node and can fail over to other nodes.» Oracle Solaris Cluster Data Service for Oracle Real Application Clusters –This agent supports the Oracle RAC database, which may run on multiple cluster nodes simultaneously.» Oracle Solaris Cluster Data Service for Oracle External Proxy –This agent is used for interrogating the status of Oracle Database or the Oracle RAC database that is not on the same cluster as the SAP application, but on an external cluster.» Oracle Solaris Cluster Data Service for SAP MaxDB –It consists of two agents, one for the MaxDB database, and the other for the xserver processes. The MaxDB database is to be configured in restart and failover mode. The xserver processes are responsible for all connections to the MaxDB database. The xserver resource must be configured in multiple-master mode and runs on each of the cluster nodes that MaxDB database might failover to.» Oracle Solaris Cluster Data Service for SAP liveCache –It consists of two agents, liveCache and xserver. The liveCache agent is responsible for making the SAP liveCache database highly available in restart and failover mode. The xserver agent takes care of the health of the xserver processes, which establish all connections to the SAP liveCache. It must be configured in multiple-master mode and runs on each of the cluster nodes that liveCache may failover to.» Oracle Solaris Cluster Data Service for Sybase ASE –This agent supports the Sybase database in restart and failover mode.» Oracle Solaris Cluster Data Service for NFS –This agent can be used for sharing SAP central directories via NFS.» Oracle Solaris Cluster Data Service for Oracle Solaris Zones –This agent supports HA for Solaris Zones. The zone with its application can be switched over from one cluster node to another. Please note this is not the same as Oracle Solaris Zone Cluster.The Solaris Cluster Data Service for SAP NetWeaver can be integrated with sapstartsrv via SAP HA Connector and is certified by SAP with SAP HA Interface Certification NW-HA-CLU740. This agent is currently available on two Solaris Cluster versions:» Oracle Solaris Custer 4.x for Solaris 11.x operating systems» Oracle Solaris Cluster 3.3 3/13 for Solaris 10 operating systemsFor more information about Oracle Solaris Cluster framework and data services, please refer to the Oracle Solaris Cluster 4.3 documentation and Oracle IT Infrastructure Solutions for SAP High Availability.3. SAP ScenariosOracle Solaris Cluster support all the SAP products based on SAP NetWeaver 7.0x and 7.x with SAP kernel version updated to 720/720_EXT, 721/721_EXT, 722/722_EXT, 740, 741, 742, and 745.Historically, there are three installation scenarios for HA SAP system. For new SAP system installation, it is highly recommended to configure with Central Services (ASCS/SCS/ERS) scenario.» Standalone Central Services (ASCS/SCS/ERS) scenario –This is the default High-Availability SAP system installation with sapinst, include ABAP, Java and ABAP+Java system. The Single Point of Failure of this scenario is the ASCS/SCS instance(s), which consist of the Message Server and Enqueue Server processes. The Enqueue Server process holds the enqueue lock table in shared memory. The ERS instance(s) holds the Enqueue Replication Server process, which replicates the enqueue lock table on another cluster node. The (A)SCS and ERS instance(s) must be configured in failover resource group(s). In case of failure, the (A)SCS instance must failover to the node where the ERS instance is running and takes over the replicated enqueue lock table, thus to prevent enqueue data loss. The ERS instance will be switched over by the Solaris Cluster agent automatically to another available cluster node to re establish the redundancy of the enqueue lock table. The Primary Application Server instance may also hold some unique services making it aSingle Point of Failure as well. It can be protected in a failover resource group. One or more Additional Application Server instance(s) can be configured in failover mode or multiple master resource groups. In multiple master resource groups, the Solaris Cluster agent takes care for all the given number of application server instances. If one of the application server instances fails, it may start another one to keep the capacity the same as before.» ABAP Central Instance Scenario -This is the legacy SAP system architecture. Only earlier versions of ABAP-only SAP systems may have this scenario. The Single Point of Failure in this scenario is the Central Instance which holds the Message Server and the Enqueue Server together with the Primary Application Server in one instance. Dialog Instances or Additional Application Server instances can be configured in failover or multiple master resource groups as well. Since this will be not supported on SAP NetWeaver 7.5, it is recommended to migrate to the (A)SCS/ERS scenario as soon as possible. For migration please refer to the SAP note 2271095.» ABAP Central Instance + Java Central Services Scenario –Only the ABAP+Java SAP system based on NetWeaver 2004 with SAP kernel 640 can have this scenario. Since this is only in customer specific support by SAP, it is highly recommended to move from this scenario to the (A)SCS/ERS scenario as soon as possible. For migration please refer to the white paper Migration to Solaris Cluster Data Service for SAP NetWeaver.4. Oracle Solaris Cluster Geographic EditionThe Oracle Solaris Cluster Geographic Edition extends the Oracle Solaris Cluster by using multiple clusters in separated locations, especially long distances, to provide service continuity in case of disaster in one location. For more information, please refer to Oracle Solaris Cluster 4.3 Geographic Edition Overview.5. Licensing InformationFor Ordering and Licensing questions, please refer to Oracle Solaris Cluster 4.3 Licensing Information User Manual.6. ReferencesFor more information about HA SAP on Oracle Solaris Cluster, please refer to the Oracle Solaris Cluster 4.3 documentation and Oracle IT Infrastructure Solutions for SAP High Availability.Oracle Corporation, World Headquarters Worldwide Inquiries500 Oracle Parkway Phone: +1.650.506.7000Redwood Shores, CA 94065, USA Fax: +1.650.506.7200C O N N E C T W I T H U S/oracle /oracle /oracle Copyright © 2016, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0116White Paper TitleJanuary 2016Author: [OPTIONAL]Contributing Authors: [OPTIONAL]。

SAP BusinessObjects Analysis（OLAP 版）管理员指南说明书

SAP BusinessObjects Analysis（OLAP 版）管理员指南说明书

SAP BusinessObjects Analysis（OLAP版）管理员指南■SAP BusinessObjects 4.12013-06-29©2013SAP AG股份公司或其关联公司版权所有，保留所有权利。

未经SAP股份公司明确许可，不版权所有得以任何形式或为任何目的复制或传播本文的任何内容。

本文包含的信息如有更改，恕不另行事先通知。

由SAP股份公司及其分销商营销的部分软件产品包含其它软件供应商的丏有软件组件。

各国的产品规格可能不同。

上述资料由SAP股份公司及其关联公司（统称“SAP集团”）提供，仅供参考，不构成任何形式的陈述或保证，其中如若存在任何错误或疏漏，SAP集团概不负责。

与SAP集团产品和服务相关的保证仅限于该等产品和服务随附的保证声明（若有）中明确提出之保证。

本文中的任何信息均不构成额外保证。

SAP和本文提及的其它SAP产品和服务及其各自标识均为SAP股份公司在德国和其他国家的商标或注册商标。

如欲了解更多商标信息和声明，请访问：/china/about/company/legal/copyright/index.epx#trademark。

2013-06-29目录第1章文档历史记录 (7)第2章SAP BusinessObjects Analysis（OLAP版）简介 (8)2.1Analysis（OLAP版）的组件..82.1.1Analysis客户端..82.1.2Analysis多维分析服务..92.2关于本指南..92.2.1文档集..92.2.2本指南的读者..10第3章体系结构 (11)Analysis体系结构图..113.13.2SAP BusinessObjects Business Intelligence平台部署模型..12多维分析服务..133.33.3.1服务器故障转移..14第4章安装和配置 (15)4.1管理工具..154.1.1中央管理控制台（CMC）..154.1.2中央配置管理器（CCM）..15安装说明..164.24.3数据源..164.4Web应用程序服务器配置..164.5安装后配置字体..174.6为Essbase OLAP连接配置BI平台..194.7防火墙端口的使用..204.8克隆Analysis服务器部署..204.9导出限制..214.10会话超时设置..214.11辅助功能..22需要SAP发行说明..224.12第5章安全性 (23)5.1针对安全套接字层（SSL）配置MDAS..23权限管理 (24)第6章6.1权限和访问级别概述..246.2创建Analysis工作区权限..246.3Analysis对象的权限..256.4Analysis对象的访问级别..276.5数据访问..28更改对Analysis工作区的访问权限..296.66.7设置自定义组的权限..306.7.1设置编辑或删除自定义组的权限..30设置共享自定义组的权限..316.7.26.8导出到分析应用程序权限..326.8.1授予将工作区导出为分析应用程序的权限..32第7章MDAS维护 (34)7.1启动和停止服务器智能代理..347.2启动和停止多维分析服务..347.3重新启动多维分析服务..347.4启用和禁用MDAS实例..357.5添加和删除MDAS实例..357.6MDAS服务器的配置文件..367.6.1MDAS配置文件—mdas.properties..367.6.2MDAS客户端配置文件—mdaclient.properties..37MDAS属性和量度..387.77.7.1“属性”页面..387.7.2“量度”页面..39数据源连接 (40)第8章8.1创建OLAP数据源连接..408.1.3查找多维数据集或查询..428.1.5身份验证..448.3删除连接..478.4将连接移动到另一个文件夹..488.5数据源连接设置..488.5.1SAP NetWeaver Business Warehouse数据源的连接设置..498.5.2Microsoft Analysis Services数据源的连接设置..50SAP BusinessObjects Profitability and Cost Management数据源的连接设置8.5.3..518.5.4SAP BusinessObjects Extended Analytics数据源的连接设置..518.5.5SAP BusinessObjects Planning and Consolidation数据源的连接设置..52 8.5.6SAP HANA数据源的连接设置..538.5.7Teradata数据源的连接设置..53Oracle Essbase数据源的连接设置..548.5.88.6管理Analysis数据源连接..54编辑Analysis数据源连接的标题和说明..558.6.18.6.2显示使用数据源连接的工作区的列表..558.6.3更改对Analysis数据源连接的访问权限..568.6.4替换Analysis数据源连接..578.7为报表-报表界面配置连接..588.7.1为报表-报表界面启用SAP BW查询目标..588.7.2为RRI启用单一登录..58第9章管理工作区 (60)9.1概述..609.2编辑Analysis工作区的标题、说明和关键字..609.3显示链接到工作区的连接列表..61第10章共享工作区 (63)10.1使用OpenDocument URL共享工作区..6310.1.1使用参数化OpenDocument URL设置提示值..6310.1.2创建参数化OpenDocument URL..63第11章扩展与性能 (65)11.1群集化处理MDAS实例..6511.2负载平衡..65优化性能..6611.3第12章监控和日志记录 (67)12.1审核..67跟踪日志记录..6712.212.3在SAP BW服务器上为Analysis启用统计..68第13章Microsoft Analysis Services注意事项 (69)13.1MSAS连接的IIS配置..6913.1.1复制所需文件..6913.1.2创建应用程序池..70新建虚拟目录..7013.1.313.1.4配置安全性..7113.1.5设置Web服务扩展..7113.2Analysis（OLAP版）和Analysis Services安全性..7213.2.1Analysis Services角色安全性..7213.2.2查找更多信息..73第14章将工作区转换为分析 (74)14.1将工作区从Voyager转换为Analysis（OLAP版）..74更多信息 (76)附录A索引 (78)文档历史记录第1章文档历史记录下表概述了最重要的文档更改。

sap系统Copy

sap系统Copy

sap系统Copy1 体系情形描述 (2)1.1 源体系情形 (2)1.2 目标体系情形 (2)2 System Copy前的预备工作 (3)2.1 按照homogeneous system copy guide做好前期预备工作 (3)2.2 备份D00数据库操纵文件 (3)3 备份源体系（D00） (4)3.1 备份前的预备工作 (4)3.1.1 创建NFS (4)3.1.2 修改D00体系initD00.sap参数 (4)3.2 开端备份 (4)4 转移文件至目标体系 (5)5 重置目标体系（T03）数据库 (5)5.1 预备工作 (5)5.1.1 检查目标体系T03的Kernel版本 (5)5.1.2 修改2.2步生成的D00数据库操纵文件 (5)5.1.3 修改备份日记文件 (6)5.1.4 停止T03的SAP及数据库 (7)5.1.5 删除T03不消的数据文件 (7)5.1.6 修改T03体系initT03.sap的参数 (7)5.2 数据库复原 (8)5.2.1 Restore (8)5.2.2 Recovery (9)5.2.3 启动数据库 (10)6 启动R/3 (10)7 System copy后续工作 (10)1 体系情形描述此文档描述了一个专门情形下应用backup/restore的方法来完成Homogeneous system copy的例子。

在此例子中目标体系T03差不多搭建完毕，应用现有的T03情形来完成D00的system copy。

此方法是SAP标准方法的扩大。

文档中的步调全然上涵盖了所有操作的全然步调，若存在漏掉敬请谅解，我会在后期的实践和工作中赓续完美。

1.1 源体系情形OS ：AIX 3.2DB ：ORACLE 9.2.0SAPSID ：D00DBSID ：D00Hostname ：HQDEV1R/3 Version ：4.6C SR2Kernel ：46D_EXTCPU ：Memory ：16GB1.2 目标体系情形OS ：AIX 3.2DB ：ORACLE 9.2.0SAPSID ：T03DBSID ：T03Hostname ：t03qasR/3 Version ：4.6C SR2Kernel ：46D_EXTCPU ：Memory ：12GB注：目标体系差不多存在一个R/3体系，SAPSID为T03。

ERP实施方法论的比较(SAP、 Oracle、J.D.E、BANN、用友等实施方法论)

ERP实施方法论的比较(SAP、 Oracle、J.D.E、BANN、用友等实施方法论)

ERP实施方法论的比较-（SAP、 Oracle、J.D.E、BANN、用友等实施方法论）正确目标的实现必须有正确的策略和方法来保证。

ERP系统实施能否达到预期目标，实施策略和方法非常重要。

这里从基本策略和方法、主要经验、基本教训等几个方面分步进行说明。

根据企业为实施ERP确定的不同目标，企业在实施ERP时可以有多种不同策略。

划分ERP实施方法有两种通用尺度：一是实施过程花费的时间，二是业务变动量和企业希望实现的价值。

二者综合起来构成了不同的实施方法矩阵。

实施ERP的目的可能出于技术原因，比如为信息管理提供技术方案和支持工具等，也可能是为了增强企业战略和提高竞争力。

着眼于技术层面的实施只能为企业提供核心信息系统功能，而基本上不会牵涉到业务变革；着眼于战略层面的实施则力图使业务变革产生积极效应，并使其商业价值最大化。

实施速度的快慢，以及实施层面的侧重，不同的实施策略对企业意味着完全不同的结果。

“慢+技术层面”：这是企业最不期望的方式。

由于技术层面的重点极少放在商业价值上，因此实施工作应该完成得越快越好。

如果在选择ERP策略时选择了这种组合或在实施过程中被迫走进了这种组合，最好尽快终止实施工作，以免带来更大损失。

“快+技术层面”：这种实施方式主要是为紧迫的技术问题或对不能满足需要的现有系统进行快速减压。

这种方式可能费用最低，但不会直接增加商业价值，仅能将技术屏障转移到经营的有效性上去。

除非企业遇到的技术问题必须在最短的时间内解决，否则也不提倡采用这种实施方式，因为，系统到位后再进行优化一般要付出更大的代价。

“快+战略层面”：这种形成快速优势的实施方式，实际操作起来几乎是不可能的，除非企业的管理非常优秀，企业的变革能力非常出色，企业的信息技术水平和应用信息技术的能力非常高。

否则这种实施方式将可能使预期目标大打折扣。

当然，可以通过这种方式求得竞争差异，将重点放在特定的业务流程或作为解决企业最薄弱环节的手段（如在供应链管理这个局部）将大多数余下的业务流程依然按照“快+技术层面”来解决。