Home
Administering
Learn how to administer settings in HCL Launch elements and communication between the elements.
Managing data
Releasing VC LOB space
After you upgrade to HCL Launch 7.0.5 and later, you can compress the amount of large object (LOB) storage space that HCL Launch uses in the vc_persistent_record database table.
Releasing LOB space in DB2 databases
You can release the large object (LOB) storage in the DB2 database.

Administering
Learn how to administer settings in HCL Launch elements and communication between the elements.
- High availability and failover
  You can configure clustered HCL Launch servers, and agents for high availability. You can also configure agents and agent relays for failover.
- Setting up high-availability clusters
  To configure a high-availability cluster, you store shared files on network storage. Then, you configure multiple servers, set each server to access the same files and database, and configure a load balancer to distribute the traffic between the servers.
- Adding cold standby servers
  You can add cold standby servers to serve as a backup server or for disaster recovery. You must start the secondary server or servers when the active server fails, and network traffic is routed to the secondary servers.
- Backup and recover
  You can back up and recover the contents of your HCL Launch installation.
- Server settings and configuration
  After you install HCL Launch, you can modify the server configuration and configure more options.
- Setting user preferences
  Each user can specify display options for the server, including the language for the server and how the server shows times and dates.
- Agents and agent relay configuration
  After you install an agent for HCL Launch, you can modify its configuration or create an agent relay to facilitate communication to remote relays.
- License management
  HCL Launch provides a 60-day license-free evaluation period. To use all product features after the evaluation period, you must have a license.
- Setting up the wizard for new users
  HCL Launch includes a wizard to help users become familiar with the procedures and steps in creating a deployment. Some configuration is required before the wizard can be used.
- Customizing the table views
  Customize a table view in the HCL Launch application by hiding or showing, and reordering of the table columns.
- Managing data
  - Migrating Codestation from filesystem repositories to S3 repositories
    You can migrate your Codestation artifacts from filesystem to S3 using the S3 migrator tool.
  - Relocating CodeStation
    You can move the CodeStation artifacts to a different location on the server.
  - Caching artifacts on agent relays
    Agent relays can cache downloaded artifacts. Caching artifacts in this way improves performance because agents retrieve artifacts from agent relays instead of from the server.
  - Releasing VC LOB space
    After you upgrade to HCL Launch 7.0.5 and later, you can compress the amount of large object (LOB) storage space that HCL Launch uses in the vc_persistent_record database table.
    - Releasing LOB space in Oracle databases
      You can release the large object (LOB) storage in the Oracle databases.
    - Releasing LOB space in MySQL or Maria databases
      You can release the large object (LOB) storage in the MySQL or Maria databases.
    - Releasing LOB space in Microsoft SQL Server databases
      You can release the large object (LOB) storage in the Microsoft SQL Server database.
    - Releasing LOB space in DB2 databases
      You can release the large object (LOB) storage in the DB2 database.
  - Scanning and removing orphaned Codestation blob files
    The csorphanscan tool scans for orphaned Codestation blob files and relocates them to an orphan’s directory.
  - Cleaning up targets

Releasing LOB space in DB2 databases

You can release the large object (LOB) storage in the DB2 database.

Before you begin

Plan downtime for upgrading HCL Launch and releasing LOB space.

About this task

Release LOB storage for DB2 database using the following steps:

Procedure

Set the experimental.vcUpgrade.enabled=true parameter in the conf/server/installed.properties file.
Restart the HCL Launch server.
Check on the progress of the conversion:
```
select count(*) from vc_persistent_record where persistent_data is not null
```
The compression process is complete when the row count reported by the query is 0.
Catalog the HCL Launch DB2 database:
```
db2 catalog tcpip node dbname remote ipAddress server port
db2 catalog database dbname at node dbname
```
For example, enter the following command:
```
db2 catalog tcpip node mydb remote 10.134.119.178 server 48408
```
You must catalog the database only once on the client system. If you have to catalog a different database, either use a different node and database name (mydb in this example) or uncatalog the cataloged database:
```
db2 uncatalog database mydb
db2 uncatalog node mydb
```
Connect to the cataloged database:
```
db2 connect to mydb user db2inst1 using db2inst1
```
Catalog the database every time you start up the DB2 command window.

Check the database size:

db2 -v "CALL GET_DBSIZE_INFO(?, ?, ?, -2)"

Check how much space each tablespace is using:

db2 -v "SELECT varchar(tbsp_name, 30) as tbsp_name, decimal(tbsp_free_pages * tbsp_page_size)/1024/1024 as free_space_mb, decimal(tbsp_total_pages * tbsp_page_size)/1024/1024 as total_space_mb FROM TABLE(MON_GET_TABLESPACE('',-2))"

Compress the database table:
```
db2 -v "REORG TABLE VC_PERSISTENT_RECORD LONGLOBDATA"
db2 -v "ALTER TABLESPACE USERSPACE1 LOWER HIGH WATER MARK"
db2 -v "ALTER TABLESPACE USERSPACE1 REDUCE MAX"
```
The preceding example includes the assumption that the vc_persistent_record table is in a tablespace called USERSPACE1. Replace USERSPACE1 with the tablespace name that contains the vc_persistent_record table.

Note: The ALTER TABLESPACE commands must only be performed if the HCL Launch is offline.

What to do next

Verify that the space is reduced:
```
db2 -v "CALL GET_DBSIZE_INFO(?, ?, ?, -2)"
```
Set the experimental.vcUpgrade.enabled parameter back to false in the conf/server/installed.properties file.