SLCs are not set by default when creating a database with job 'db_create'

Detail name	Value
Changelog Number	20233
Type	Bug
Status	Resolved
Affected Versions	Exasol 8.0.0
Fix Versions	Exasol 8.32.0, Exasol 8.29.6
Resolution Date	2024-11-08

Description

UDFs (User Defined Functions) and SQL statements related to Virtual Schemas will can be failing with error

Error: SQL Error [22061]: Cannot access bucket 'slc' in bucketfs '__builtin__' (Session: ...)

The issue stems from the parameter ‘builtin_script_language_name' of the 'db_create' ConfD job (see documentation) defining an SLC (Script Language Container) being optional and having no default.

Workaround

To avoid this error one can pass the ‘builtin_script_language_name' argument to ‘db_create’. For example, the following may be appended to the list of arguments of a 'db_create’ job call:

"builtin_script_language_name": "slc-6.0.0-c4-5-standard-EXASOL-8.0.0/ScriptLanguages-standard-EXASOL-8.0.0-slc-v6.0.0-PB5EHDLN".

This parameter value corresponds to the SLC shipped with the particular release. It is subject to rarely change.

Known values per DB version:

DB version	“builtin_script_language_name” value
8.27.* and earlier	"slc-6.0.0-c4-5-standard-EXASOL-8.0.0/ScriptLanguages-standard-EXASOL-8.0.0-slc-v6.0.0-PB5EHDLN"
8.28.*	"slc-8.0.0-c4-5-standard-EXASOL-all/ScriptLanguages-standard-EXASOL-all-slc-v8.0.0-34MHFEH5"
8.29., 8.31.	"slc-8.1.0-c4-5-standard-EXASOL-all/ScriptLanguages-standard-EXASOL-all-slc-v8.1.0-CJDGGFPK"

In case DB is already created and you get the error above, it is possible to change it via ConfD job ‘db_configure` by passing the respective value to the ‘builtin_script_language_name’ parameter.

Fix

UDFs and SQL statements related to Virtual Schemas work even when ‘builtin_script_language_name' is not passed to 'db_create' ConfD job.