SAP 安装指南: ECC 6.0 /ORACLE/WIN Installation Part II

Installation Screen	Suggested Response
Main Installation Screen  -> Choose Service	SAP Installation Master -> SAP ERP 2005 SR2 -> SAP Systems -> Oracle -> Central System -> Central System Installation                                          Next è
Define Parameters -> Parameter Mode	Select Custom                                                                                             Next è
Software Package Request -> Java Component NW2004sSR2	D:\CDs\51032269                                                                                      Next è
Java Development Kit	C:\j2sdk1.4.2_15_x64                                                                                Next è
General Parameters -> SAP System ID and Instllation Deive and Unicode	SAP System ID (SAPSID) : PS1,   Installation Drive: D: Unicode System (recommended): checked                                                Next è
SAP System -> Master Password	Password for all users of this SAP system and Confirm                           Next è
SAP System-> Windows Domain	Domain Model -> Local Installation                                                         Next è
SAP System -> OS User Passwords	SAP System Administrator password  and SAP System Service User Passowrd                                                                                                                    Next è
SAP System -> Database ->	Database Installation -> Installation Method                                            Next è
SAP System -> Database Parameters ->	Database IS (DBSID): PS1, Database Host: socw3s1xxxx                       Next è
Oracle -> Database System	Database Instance Parameters: DBHome, DB Server Version            Instance Memory: Instance Ram: 4063 Database Schema Parameters: ABAP Schema: SAPSID, JAVA Schema: SAPSIDDB                                                                                              Next è
Oracle -> Database System for OBR	Databse Server Drives: Drive for sapdataHome and Drive for Oracle Archive (oraarch): Select D: Drive                                                                        Next è
Oracle -> Standard Database Users	Oracle Database Users: Password of sys and system, use default          Next è
Oracle -> Listener Configuration	Oracle Listener Configuration: Select default                                         Next è
SAP System -> Secure Store Settings	Secure Store Settings: Keep it default                                                    Next è
SAP System -> Central and SCS Instance	Enter the Central and SCS instance parameters: default is 00 and 01    Next è
SAP System -> Central and SCS Instance -> Service Ports	Enter the Central and SCS instance service ports: default is 3600, 3900 and 3901                                                                                                                 Next è
Media Browser -> Software Package Request	Enter the location of the Export CD (1 and 2) : D:\CDs\export            Next è
SAP System -> Secure Store Information	Enter the required user information of Existing J2EE Engine Administrator : j2ee_admin, password: xxxxxxxxxx                            Next è
Media Browser -> Software Package Request	Enter the location of the UC Kernel NW2004sSR2 and Oracle client: UC_Kernel _NW2004sSR2:  D:\CDs\\51033032_15\KU_WINDOWS_X86_64 Oracle Client: D:\CDs\ 51033272\OCL_WINDOWS_X86_64            Next è
SAP System -> UnPack Archives	Select which Archives you want to uppack -> Select default                Next è
Parameter Summary	Choose Start to Start with the values shown or select the parameters you want to change and choose ‘Revise’                                                                   Start è
SAP System -> SAP Solution Manager	Enter the SAP Solution Manager Key                                                   Next è
Task Progress	Execution of Service has been completed Successfully                          OK è

1.     Reboot the server and log in as adm. Check the Oracle environment setup is correct and Brtools is working.

2.     Start SAP using the Microsoft Management Console. Use standard R/3 troubleshooting procedures (check trace files, etc.) if the SAP system does not start up.

3.     Log on to client 000 with an administrative account other than SAP* or DDIC. If no other user accounts exist, log on to the system with SAP* or DDIC and create a new user account (Tx SU01). Create the new user account with profiles SAP_ALL and SAP_NEW.
Note: You may have to create new company assignments in Tx SUCOMP first.

4.     Initial Checks: Run the following transactions:

·       Tx SM28 (SICK) – Initial consistency check. Correct errors if any exist.

·       Tx SM50/51 – Check processes. Document current kernel patch level.

·       Tx SM21 – System log. Look for errors and correct as necessary. If you receive the error In table TCPDB, there are 0 entries, run report RSCPINST as directed in note# 42305. However, this should not be the case, as the source system would already contain TCPDB entries for Unicode.

·       Tx DB02 – Check database consistency as soon as possible. Check the Database Recovery Model (should be “Full”) and, if necessary, change using SQL Enterprise Manager.

5.     System Licensing:
Request a permanent license through OSS. Install the new license using the operating system saplicense command or through Tx SLICENSE.

6.     System Patching (Optional):

·  Install the SPAM update and support packages to the latest levels or to match existing instances in the same landscape. Use appropriate OSS notes to ensure the correct groupings of support packages are imported and to avoid problems (i.e. note# 672651 and note# 598767). Follow step #3 in note 598767 to prevent SQL Error 229.

·       Note:  Keep the R/3 SPAM and Support Pack versions the same across instances of the same landscape.

7.     RFCs: Run Tx SM59 and verify/adjust the RFC calls to point to the correct systems or delete outright. It is likely the RFC connection (type R/3) can be deleted.

8.     Client Administration: Depending on the source system, some steps may not be required. However, all steps should be reviewed for applicability.

·       Tx SCC4: Create new clients and/or adjust the logical system names and settings of current clients to the new situation.

·       Tx SCCL: If needed, perform. local client copies to the requirements of the target system.

9.     Solution Manager

·       If the new SAP instance is connected to a SAP Solution Manager system, download and install the latest ST-PI and ST/A-PI plug-ins using Tx SAINT. Update the plug-in Support Packages to the latest levels.

·       Keep the ST-PI and ST/A-PI versions and Support Package levels the same across instances of the same landscape.

·       Additionally, configuration changes in RZ20 and RZ21 should be checked and reconfigured if needed.

10.     Spooling: Use Tx SPAD to adjust output devices to the target system hostname. Next, run a consistency check of TemSe objects in Tx SP12 (TemSe Data Storage -> Consistency Check)

11.     System Time Zone: If required, change the system time zone using Tx STZAC. Perform. this action in a client where modifications are allowed or use Tx SCC4 to temporarily change client settings to allow the time zone change.

12.     Help: Use Tx SR13 to set up the R/3 documentation link. Point to the local documentation server or the SAP help portal: http://help.sap.com.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/65240/viewspace-683579/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/65240/viewspace-683579/