Home
AdministeringIn addition to administering the database server, you can tune performance, replicate data, and archive data.
System administrationThese topics contain concepts, procedures, and reference information for database and database server administrators to use for managing and tuning HCL OneDB™ database servers.
Administrator's ReferenceThe HCL OneDB™ Administrator's Reference includes comprehensive descriptions of HCL OneDB™ configuration parameters, the system-monitoring interface (SMI) tables in the sysmaster database, the syntax of database server utilities such as onmode and onstat, logical-log records, disk structures, event alarms, and unnumbered error messages.
Configuring and monitoring HCL OneDB™
Database configuration parametersThe HCL OneDB™ database server uses a configuration file, which is called the onconfig file, during initialization. This file contains default configuration parameter values. You can modify the parameter values to improve performance and other characteristics of the instance or database.
LICENSE_SERVER configuration parameterThe LICENSE_SERVER configuration parameter specifies the OneDB instance about the FlexNet Server Device it needs to connect to obtain the necessary CPU license resources.

LICENSE_SERVER configuration parameter

The LICENSE_SERVER configuration parameter specifies the OneDB instance about the FlexNet Server Device it needs to connect to obtain the necessary CPU license resources.

onconfig.std value

Not set.

values

For the cloud based license server, a URL that points to the FlexNet Operations license server API, with <Device_ID> set to the Server Device name.

https://hclsoftware.compliance.flexnetoperations.com/instances/<Device_ID>/ request

For a local license server, the server will be the hostname and port number of the machine running the LLS.

https://corporate-lls.local:7070/instances/<Device_ID>/request

takes effect

On starting the instance, the FlexNet server indicated is queried to determine if sufficient licenses are available.

Usage

The HCL OneDB Server instance must obtain sufficient license resources to start up all the CPU VPs specified in the onconfig file. It will fail to start if the licenses are not available. Any subsequent dynamic change to the CPU VP configuration will require rechecking the license entitlement with the FlexNet license server. The OneDB instance will disable CPU VPs if there are no available licenses.

Care should be taken with the VPCLASS and AUTO_TUNE parameters to ensure that the correct initial request for CPU resource is made, and that any CPU VPs dynamically added by the system have sufficient licenses and do not cause license starvation issues for other instances using the same license server device.

If there are possible issues with license allocation between multiple OneDB instances, using the same FlexNet Server Device, then it is possible to tie the license allocations to specific instances using FlexNet’s Reservation Group feature.

License allocations are returned when the OneDB instance is stopped. If an instance fails, and is unable to return the licenses, then the licenses will be re-allocated when the server is restarted. If it is not possible to restart the server after a failure, and the licenses need to be returned for use by another instance, then the onclean utility can be used to return the licenses.

A Local License server cannot be installed on a virtual machine. The OneDB instance, acting as a Client Device, accesses the license server through HTTP to a nominated port number, the default being 7070. Control and monitoring of the LLS through the REST interface is accomplished through a separate HTTPS port.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.