Home
SQL programmingYou can use the HCL OneDB™ implementation of the SQL language to develop applications for HCL OneDB™ database servers.
Guide to SQL: ReferenceThe HCL OneDB™ Guide to SQL: Reference contains the reference information for the system catalog tables, data types, and environment variables of the HCL OneDB™ dialect of the SQL language, as implemented in HCL OneDB™. These topics also include information about the stores_demo, sales_demo, and superstore_demo databases that are included with HCL OneDB™.
Environment variablesVarious environment variables affect the functionality of your HCL OneDB™ products. You can set environment variables that identify your terminal, specify the location of your software and define other parameters.
Environment variables in HCL OneDB™ productsThe topics that follow discuss (in alphabetic order) environment variables that HCL OneDB™ database server products and their utilities use.
ONEDB_ STACKSIZE environment variable

ONEDB_ STACKSIZE environment variable

The ONEDB_ STACKSIZE environment variable specifies the stack size (in KB) that is applied to all client processes. Any value that you set for ONEDB_ STACKSIZE in the client environment is ignored by the database server.

size: is an integer, setting the stack size (in KB) for SQL client threads.

For example, to decrease the ONEDB_ STACKSIZE to 20 KB, enter the following command:

setenv ONEDB_ STACKSIZE 20

If ONEDB_ STACKSIZE is not set, the stack size is taken from the database server configuration parameter STACKSIZE or else defaults to a platform-specific value. The default stack size value for the primary thread of an SQL client is 32 KB for nonrecursive database activity.

Warning: For instructions on setting this value, see the HCL OneDB™ Administrator's Reference. If you incorrectly set the value of ONEDB_ STACKSIZE, it can cause the database server to fail.

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.