Install Hubble Accelerator

Follow these steps to install Hubble Accelerator:

Download the Hubble Accelerator RPM from the SE URL provided by insightsoftware Support.
Install the local Hubble Accelerator rpm (replace 5.x.x-x with the actual version of the rpm, example: 5.0.0-78):
```
yum localinstall hubble-accelerator-5.0.0-xx.exx.x86_64.rpm
```
This step will create the Hubble Accelerator directories and copy the installation packages for all the Accelerator components.
Run the Hubble Accelerator installer that will install all the rpms for all the components, and configure them:

Note: Replace 5.x.x with the actual version of the rpm, for example, 5.0.0.
```
/opt/insightsoftware/hubble-accelerator/5.0.0/install.sh
```
Stop Vector service.
```
systemctl stop actian-vectorVW
```
For Accelerator build 4.3.x with Vector version 6.3.x or later, Actian has provided the flexibility for switching back to the old behavior of not padding spaces to strings using CHAR / NCHAR functions. When CHAR and NCHAR types are used with x100 tables, the correct behavior is to pad these datatypes with spaces to the explicit and/or implicit length of the datatype. This parameter x100_nopad_char_compat adds a backward compatibility configuration option to allow the user to fall back to the old behavior (Vector version 5.x) where these datatypes were not padded.

To set ii.localhost.dbms.*.x100_nopad_char_compat to ON in config.dat:
1. Go to the directory:
```
cd $II_SYSTEM/ingres/files/
```
2. Open config.dat:
```
vi config.dat
```
3. Find and change the line to:
```
ii.localhost.dbms.*.x100_nopad_char_compat: ON
```
4. Save and exit:
```
:wq!
```
In Vector version 6.3, the default configuration for string truncation is set to "fail," whereas in Vector version 5.0, it was "ignore." To apply this change, follow these steps:
1. Navigate to the directory containing the config.dat file:
```
cd $II_SYSTEM/ingres/files/
```
2. Open config.dat in edit mode using vi:
```
vi config.dat
```
3. Enter i to enter insert mode.
4. Change the value of ii.<host>.config.string_truncation to ignore.
```
ii.<host>.config.string_truncation: ignore
```
5. Save the updated config.dat file and exit the editor by entering :wq!.
f. Restart the Vector database to apply the changes.
To improve performance, follow these steps to update the config.dat file:
1. Navigate to the directory containing the config.dat file:
```
cd $II_SYSTEM/ingres/files/
```
2. Open config.dat in edit mode using vi:
```
vi config.dat
```
3. Enter insert mode by typing i.
4. Update the following values:
  - Change ii.localhost.dbms.*.qef_dsh_memory to 2147483648:
```
ii.localhost.dbms.*.qef_dsh_memory: 2147483648
```
  - Change ii.localhost.dbms.*.qef_memory to 8397044736:
```
ii.localhost.dbms.*.qef_memory: 8397044736
```
  - Change ii.localhost.dbms.*.qef_sort_mem to 4194304:
```
ii.localhost.dbms.*.qef_sort_mem: 4194304
```
  - Change ii.localhost.dbms.*.stack_size to 2048576:
```
ii.localhost.dbms.*.stack_size: 2048576
```
5. Exit insert mode by clicking Esc.
6. Save the updated config.dat file and exit the editor with :wq!.
7. Restart the Vector database to apply the changes.
To update the heap space, follow these steps:
1. Navigate to the directory containing the connect-distributed file:
```
cd /usr/bin/
```
2. Open connect-distributed in edit mode using vi:
```
vi connect-distributed
```
3. Locate the line:
```
export KAFKA_HEAP_OPTS="-Xms6M -Xmx8G"
```
4. Enter insert mode by typing i.
5. Change the value from -Xms6M -Xmx8G to -Xms8G -Xmx12G:
```
export KAFKA_HEAP_OPTS="-Xms8G -Xmx12G"
```
6. Exit insert mode by typing Esc.
7. Save the updated connect-distributed file and exit the editor with :wq!.
To update the vectorwise.db.conf file, follow these steps:
1. Navigate to the directory containing the vectorwise.db.conf file:
2. Open vectorwise.db.conf in edit mode using vi:
3. Enter insert mode by typing i.
4. Update the following values:
  1. Change max_memory_size to 100133242368:
```
max_memory_size=100133242368
```
  2. Change max_transactions to 30000:
```
max_transactions=30000
```
  3. Change max_parallelism_level to 24:
```
max_parallelism_level=24
```
  4. Change max_table_update_ratio to 0.05:
```
max_table_update_ratio=0.05
```
  5. Change max_global_update_memory to 0.25:
```
max_global_update_memory=0.25
```
5. Exit insert mode by typing Esc.
6. Save the updated vectorwise.db.conf file and exit the editor with :wq!.
Stop all services using sink connector
Start all services using sink connector
After updating the config.dat file, restart the vector instance and run the post-installation script to implement the non-default parameter. Use the following commands as the actian or root user:

Restart the Vector instance (in case of upgrading an Accelerator (for implementing non-default Db parameter) after updating config.dat file using below commands:
```
systemctl restart actian-vectorVW
```
or

Restart the Vector instance and run post installation script (in case of fresh installation of an Accelerator for implementing non-default parameter) after updating config.dat file using below command:
```
systemctl restart actian-vectorVW 
```
Reboot the machine.
Start all services using sink connector.
Check if areplicate is running if not start using below command.
```
/etc/init.d/areplicate start
```
In case of upgrade, for version 3.3.x or higher, the current vector database 'db' needs to be upgraded:
```
upgradedb db
```
Test if you can access the Vector database:
```
sql db
```
Confirm that replication is installed.
```
repctl version
```
The password for the replication user, and the Hubble user for the database will be in:
```
cat /opt/insightsoftware/hubble-accelerator/.vector
```
Feel free to remove the password from that file for security reasons, but leave the file empty.
The password for the replication user, in the replication console can be found in:
```
cat /opt/insightsoftware/hubble-accelerator/.attunity
```
Feel free to remove the password from that file for security reasons, but leave the file empty.

Enable and start the Hubble Appliance API service:

systemctl enable hubble-applianceapi

systemctl start hubble-applianceapi

Install Hubble Accelerator

Was this article helpful?