Installing VectorH Using a Response File
Response File--Define Configuration for the Installation
A response file contains parameters that define how an instance is to be installed and configured. You can use any name for the response file.
Each entry in the response file must be on a separate line and in the following form:
variable=value
where variable is a response file parameter name.
Install Vector Using a Response File
To install Vector using install.sh
Install Vector by invoking install.sh using the ‑respfile flag to pass the full path to the response file:
./install.sh -respfile /full/path/to/resp.txt
To install Vector using RPM directly
After the response file is generated, install Vector by following these steps:
1. Set the II_RESPONSE_FILE environment variable to the absolute path and name of the response file.
2. Install the RPM packages by invoking RPM.
3. Run the service script, which automatically uses the value of II_RESPONSE_FILE:
/etc/init.d/actian-vectorXX configure
where XX is the instance ID.
Example Response File
# Actian Response File
# Generated by the Actian Response File API
# Created: Tue Mar 10 20:46:19 2020
# [ Database Locations ]
II_SYSTEM=/opt/Actian/VectorVH
II_DATABASE=/opt/Actian/VectorVH
II_CHECKPOINT=/opt/Actian/VectorVH
II_JOURNAL=/opt/Actian/VectorVH
II_WORK=/opt/Actian/VectorVH
II_DUMP=/opt/Actian/VectorVH
II_VWDATA=/opt/Actian/VectorVH
II_LOG_FILE=/opt/Actian/VectorVH
# [ HDFS Locations ]
II_HDFSDATA=/Actian/VectorVH
II_HDFSBACKUP=/Actian/VectorVH
II_HDFSWORK=/Actian/VectorVH
# [ Instance Configuration ]
II_INSTALLATION=VH
II_TIMEZONE_NAME=America-Los_Angeles
II_DATE_FORMAT="US"
II_MONEY_FORMAT="L:$"
II_ENABLE_SQL92="NO"
II_USERID=actian
II_GROUPID=actian
# [ Installation Options ]
II_LOG_FILE_SIZE_MB=512
II_START_ON_BOOT=Yes
II_MTS_JAVA_HOME=/usr/lib64/jvm/java
# [ Vector Configuration ]
II_VWCFG_MAX_MEMORY=1004M
II_VWCFG_BUFFERPOOL=502M
II_VWCFG_BLOCK_SIZE=512K
II_VWCFG_GROUP_SIZE=8
II_VWCFG_MAX_PARALLELISM=2
# [ HDFS Configuration ]
SLAVES_LIST=datanode1,datanode2,datanode3
DEFAULT_FS=hdfs://namenode:8020
# [ Yarn Configuration ]
ENABLE_YARN=true
YARN_AM_QUEUE=vector
# [ Upgrade Configuration ]
II_UPGRADE_USER_DB="YES"
II_REMOVE_ALL_FILES="NO"
Response File Parameters
Parameters in the response file determine how Vector is to be installed and configured.
Some parameters are valid on certain operating systems only or generated by certain installation methods only.
CONNECT_LIMIT
CONNECT_LIMIT specifies the maximum number of concurrent users.
DEFAULT_FS
DEFAULT_FS specifies the file system to be used, as one of the following:
• DEFAULT_FS=viewfs://namespace/
• DEFAULT_FS=hdfs://ha_name
• DEFAULT_FS=hdfs://namenode:8020
ENABLE_YARN
ENABLE_YARN enables VectorH integration with Hadoop YARN.
Default: false
II_AUTH_STRING
The II_AUTH_STRING parameter defines the authorization string required for an evaluation version of the product. The authorization string is emailed to you when you download the product.
II_CHECKPOINT
The II_CHECKPOINT parameter defines the location of the checkpoint files that serve as a static backup of the database. This parameter cannot be changed, even during installation updates. Specific databases can designate alternate locations for checkpoints as a parameter to the createdb command.
Default: Same as II_SYSTEM
II_COMPONENT_CORE
The II_COMPONENT_CORE parameter defines whether the core package for Linux is included in the installation. The core package is required by all other optional packages and must always be included in the installation.
This parameter has the following options:
YES
(Default) Include the core package.
NO
Do not include the core package.
II_DATABASE
The II_DATABASE parameter defines the location of the master database (iidbdb) and the default location for database files.
Default: Same as II_SYSTEM
II_DATE_FORMAT
The II_DATE_FORMAT parameter defines the format used to display date values.
The following are valid II_DATE_FORMAT settings and their output formats:
For valid input formats, see the SQL Language Guide.
II_DBMS_AUTHENTICATION
The II_DBMS_AUTHENTICATION parameter enables or disables the DBMS authentication feature. Valid values are YES and NO.
Default: "YES"
II_DUAL_LOG
The II_DUAL_LOG parameter defines the location of the backup (secondary) transaction log file. By default, dual transaction logging is disabled (parameter is set to blank ("")). If you desire dual logging, configure the II_SYSTEM location value for this parameter setting.
Default: ""
II_DUMP
The II_DUMP parameter defines the location of dump files used to store changes made during an online checkpoint.
Default: Same as II_SYSTEM
II_ENABLE_SQL92
The II_ENABLE_SQL92 parameter defines whether the SQL92 standard setting is enabled.
This parameter has the following options:
YES
Enable the SQL92 standard.
NO
(Default) Do not enable the SQL92 standard.
II_GROUPID
The II_GROUPID parameter specifies the group ID to which the current user's user ID belongs and that owns the installation. The ID is added to the system if it does not exist.
Default: Current user's group ID
II_HDFSBACKUP
The II_HDFSBACK parameter defines the HDFS location of the checkpoint files that serve as a static backup of the database. This parameter cannot be changed, even during installation updates.
Default: Same as II_HDFSDATA