2 Installing and Configuring DIVAmigrate

This chapter describes installing and configuring the DIVAmigrate utility and includes the following information:

Installing DIVAmigrate

The DIVAmigrate Utility is part of the standard DIVArchive installation, and is placed in the %DIVA_HOME%\Program\ folder. You can install DIVAmigrate on the DIVArchive Manager computer, or any other computer capable of communicating with the Manager using the TCP/IP protocol. You can confirm connectivity by successfully pinging the Manager from the client computer.

Windows Files and Folders

You will find the following new files and folders after you complete the initial DIVArchive installation in Windows:

%DIVA_HOME%\Program
   Migrate
      bin
         client.bat
         migrate.bat
      lib
         migrate.jar
   conf
      migrate
         migrate.conf.ini
   log
      migrate

Linux Files and Directories

You will find the following new files and directories after you complete the initial DIVArchive installation in Linux:

%DIVA_HOME%/Program   Migrate
      bin
         client.sh
         migrate.sh
      lib
         migrate.jar
   conf
      migrate
         migrate.conf.ini
   log
      migrate

Configuring the DIVAmigrate Service

The DIVAmigrate Service requires a valid configuration file during install and start procedures. The default DIVAmigrate configuration file is named migrate.conf and is located in the %DIVA_HOME%\Program\conf\migrate\ folder.

The configuration file is a standard properties file similar to the Manager configuration file. The configuration file is not auto-reloadable, and therefore any changes made to the file do not take effect until the DIVAmigrate Service is restarted.

Notes:

The Windows Service Wrapper configuration must not be modified, and is not included in the default configuration file in Appendix B.

The DIVA Service Options section also must not be modified unless instructed by Oracle Support. However, this section is included in the default configuration file in Appendix B.

Use the following procedure to modify the DIVAmigrate configuration file:

Caution:

Do not use Word, WordPad, or any other word processor or editing tool that adds extra characters to a file. Always use a plain text editor such as Notepad, or Notepad++.

  1. Create a copy of the migrate.conf.ini file.

    It is important to create a copy and keep the original file intact to refer back to in case the configuration you are working on either does not work, becomes corrupt, or has or creates errors.

  2. Rename the copied file to migrate.conf.

  3. Open the file with any plain text editor and populate the following parameters. These parameters are all mandatory unless otherwise noted in the description.

    SERVICE_NAME

    This parameter is the name for the Windows Service. The default value is DivaMigrate.

    DIVAMANAGER_HOST

    This parameter is the host name or IP address of the DIVArchive Manager. The default value is 127.0.0.1.

    DIVAMANAGER_PORT

    This parameter is the port number to connect to the DIVArchive Manager. The default value is 9000.

    DIVA_MIGRATE_MANAGEMENT_PORT

    This parameter is the management port number. The default value is 9191.

    DIVAMANAGER_DBURL

    This parameter is a URL to connect to the database. You can use this parameter instead of using the DIVAMANAGER_DBHOST and DIVAMANAGER_DBPORT, or DIVAMANAGER_TNSNAME parameters. When you use this parameter you have the additional flexibility to explicitly identify whether to use the Oracle JDBC thin driver, or the Oracle JDBC OCI driver, to connect to the Oracle Database. For example, you can use jdbc:oracle:thin:@host:port:oracle_sid or jdbc:oracle:oci:@tnsname. This is not a mandatory parameter.

    DIVAMANAGER_DBUSER

    This parameter is the user name the Manager uses to connect to the DIVArchive Database. The default value is diva, and is case sensitive.

    DIVAMANAGER_TNSNAME

    This parameter is the TNS Name of the DIVArchive Schema within the Oracle Database. DIVAmigrate ignores this setting if the DIVAMNAGER_DBHOST and DIVAMANAGER_DBPORT settings are defined. There must be a corresponding entry in TNSNAMES.ORA found under the Oracle 11 Client installation. This is not a mandatory parameter.

    DIVAMANAGER_DBHOST

    This parameter specifies the host name or IP address of the computer containing the DIVArchive Database. If using a host name, this must be present in the hosts file on the computer where the DIVArchive Manager is installed. For example, you can use either 127.0.0.1 or localhost. This is not a mandatory parameter.

    DIVAMANAGER_DBPORT

    This parameter is the Oracle Listener Port you configured during the DIVArchive Database installation. The default value is port 1521. This is not a mandatory parameter.

    DIVAMANAGER_DBSID

    The DIVArchive Database instance System Identifier (SID) in the Oracle Database where the DIVArchive Manager connects. This value is typically lib5, which is the default value. Consult your location's System Configuration Plan for confirmation.

    DIVAMANAGER_DBSERVICENAME

    This parameter is the DIVArchive Database Instance Identifier (SID) in Oracle where DIVArchive Manager connects. Typically, lib5.world (the default), is used in most DIVArchive installations. Consult your delivery plan if you are unsure.

    You must set either this value, or DIVAMANAGER_DBSID, when you use DIVAMANAGER_DBHOST and DIVAMANAGER_DBPORT for database connections. If you set both parameters, then SERVICENAME takes precedence over SID.

    MAX_SIMULTANEOUS_REQUESTS

    This parameter is the maximum number of simultaneous Manager requests processed by DIVAmigrate. The default value is 15. This is not a mandatory parameter.

    DB_SCAN_PERIODICITY

    This parameter (in seconds) determines how often DIVAmigrate looks for new jobs in the database. The default value is 60 seconds. This is not a mandatory parameter.

    DIVA_RECONNECT_PERIODICITY

    This parameter (in seconds) determines the time between reconnection attempts if connectivity with the Manager is lost. The default value is 30 seconds.

    MAX_FAILED_REQUESTS_PAUSE

    This parameter identifies the maximum number of sequential failure requests that can occur before DIVAmigrate pauses the migration job. DIVAmigrate pauses the job if the configured number of requests fails sequentially. The default value is 10. This is not a mandatory parameter.

    REQUEST_STATUS_CHECK_DELAY_SECS

    This parameter (in seconds) determines how often DIVAmigrate scans manager for request status. The default value is 5 seconds. This is not a mandatory parameter.

    JOB_MAX_INACTIVE_TIME

    This parameter (in hours) determines the Migrations Plan's maximum inactivity time. If, after the service is restarted, it finds running jobs having the last access time greater than this value, the Migration Plan for those jobs are recreated. The default value is 24 hours. This is not a mandatory parameter.

    MAX_SIMULTANEOUS_JOB

    This parameter is the maximum number of simultaneous jobs or process request that can run at the same time.

Configuring the Logging Settings

DIVAmigrate uses the same logging methods used for the DIVArchive Manager. However, DIVAmigrate logs are located in the %DIVA_HOME%\Program\log\migrate folder. DIVAmigrate logs are automatically archived and divided into separate files each time the current log file reaches its size limit. You set the following DIVAmigrate logging parameters in the migrate.conf file:

LOGGING_DIRECTORY

This parameter identifies the DIVAmigrate log file storage directory. The default is ../../log/migrate.

LOGGING_ROOT_LEVEL, LOGGING_TRACE_LEVEL, and LOGGING_SERVICE_LEVEL

You can modify these three parameters to suit the required level of activity logging. The default value is INFO.

Tip:

Only use the higher logging levels when instructed to do so by Oracle Support to avoid large log files being created.

Valid options for each parameter are:

  • DEBUG

  • INFO

  • WARN

  • ERROR

  • FATAL

LOGGING_MAXFILESIZE

This parameter identifies the maximum size of the log file before it is archived. When the current log file is archive, a new file is created. You must specify the file size using KB or MB to indicate Kilobytes or Megabytes respectively. The default value is 10MB. For example, LOGGING_MAXFILESIZE=10MB.

LOGGING_LIFETIME

All files older than the value of this parameter are removed. This includes trace, service, and .zip files. The value for this parameter is in hours, and the default value is 50.