Configuration

In this roadmap step, SUM asks for all information required to run the update with DMO.

The following actions are carried out:

Configuration of processes and other performance relevant parameters

DMO-specific actions:

Provision of connection parameters and users of the target database
Installation of target database client on the DMO host

Note

If you encounter problems with the installation of the client, you can install it manually. Make sure that you use the correct directory for the installation.
Extraction of kernel for target database
Upload of additional packages, customer transport requests, and modifications

Further features:

When you execute a migration to the target database, select either the Standard or Downtime-optimized scenario strategy in the initial dialogs of SUM. The option Single System is not intended for DMO. For more information about the options, see in the SUM Guide the section Planning Initial Dialogs for the Specification of the Scenario.
The number of R3load processes, which you can set in the phase PREP_CONFIGURATION/INITSUBST, is the only visible parameter that affects the migration performance in the downtime. Note that you can configure the number of processes dynamically at a later point in time.
In the new DMO-specific phases, you provide connection data and user credentials for the target database.
In phase SYB_DMO_DBOPTIONS, you can set options for the target database to prevent issues and to optimize the migration performance.

If the source system contains large tables, and several parallel import jobs are configured as well, you might experience a long run time during the migration. Furthermore, it may happen that the SAP ASE database runs out of locks or is unable to allocate further space for object syslogs in database <SID>, because the segment logsegment is full or has no free extents.

To prevent these issues and to optimize the migration performance to SAP ASE, you can choose in phase SYB_DMO_DBOPTIONS that SUM activates the database option select into/bulkcopy/pllsort. SUM deactivates the option again later on in phase SYB_DMO_DBOPTIONS_BULKOFF.

Furthermore, if you choose the option, SUM displays a reminder in phase SYB_DMO_DBOPTIONS_BULKOFF as well to perform a full database backup (See also section Postprocessing). A full database backup is required after you have performed all necessary follow-up activities and before you resume the production operation of your system. This has the advantage that all database changes resulting from follow-up activities are included in the full backup. In case a full database backup is not done, no regular transaction log is available, which limits recovery options.
In phase SYB_MIGCONFIG, you have to enter the following target database parameters:
- hostname of target database
- port number of target database
- path to the SAP License file for the migrated SAP system
- password of the user SAPSR3 on the target database
To retrieve the target database port number, you can proceed as follows:
1. Log in to the operating system of the target database host as user "syb<SAPSID>".
2. Windows systems: Select the drive, on which the SAP ASE database is installed, and open the file <DRIVE>:\sybase\<SAPSID>\ini\sql.ini.
  
  Unix/Linux systems: Open the file /sybase/<SAPSID>/interfaces.
3. The port number is the last value in the line beginning with the master of the block [<SAPSID>] (Windows systems) or <SAPSID> (Unix systems). It is separated by a comma from the host name.