SAP Landscape Management 3.0, Enterprise Edition

Preparing Additional Hosts for Database Relocation

Procedure

  1. If not already done, change the Windows user profile type of the <sapsid>adm and SAPService <SAPSID> users from local to roaming. Ensure that these users get the full set of SAP user environment variables on all hosts. For example, SAPSYSTEMNAME, ORACLE_SID, and dbs_ora_tnsname.
  2. Perform the general preparation tasks for a database installation of a distributed system described in the SAP installation guide.
  3. Install the database software and patches. For more information, see Setting up Multiple Oracle Homes in the installation guide.
  4. Copy the database parameter file (SPFILE/PFILE (per default located in %ORACLE_HOME%\database)) and the Oracle Net configuration files (for example, listener.ora (per default located in %ORACLE_HOME%\network\admin)) from the installation host to the newly created Oracle home.

    You could also create a specifically crafted database parameter file that better fits the host's environment.

  5. If you want to keep these files synchronized, you could put them into one of the file systems that are relocated with the database and create a link from the Oracle home subdirectory to this file system. On Windows 2003 you can use, for example, the linkd.exe tool to manage links. Proceed as follows:

    1. On the installation host:

      1. Stop the database and the instance service.

      2. Create the following directory:

        <path\to\sapdata1>\database

      3. Move all files from %ORACLE_HOME%\database to <path\to\sapdata1>\database

      4. Delete %ORACLE_HOME%\database.

      5. Create a link from %ORACLE_HOME%\database to <path\to\sapdata1>\database.

    2. On all additional hosts, create a link from %ORACLE_HOME%\database to <path\to\sapdata1>\database.

    You can use the same approach to keep the Oracle Net configuration files synchronized.

  6. Create the Oracle instance service, for example, by executing command %ORACLE_HOME%\bin\oradim.exe -NEW -SID <DBSID>-STARTMODE manual.

    You do not need to manually create the listener service. It is automatically created when it is started for the first time (which is done as part of the prepare operation for SAP Landscape Management).

  7. Use SAP Landscape Management to stop and unprepare the database instance on the installation host and to prepare it on the additional host.
  8. Create the local groups ORA_ <DBSID>_DBA and ORA_ <DBSID>_OPER and add the <sapside>adm and SAPService <SID> users to these local groups.
  9. Add these local groups to the access control lists of the %ORACLE_HOME% directory tree and grant full control rights.
  10. Attach the disks with the database files and also add these local groups to the access control lists of the /oracle/<DBSID> directory tree and grant full control rights.
Related Information