vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The instance must be enabled for IAM and the IBMid if the user must be added as a database user.

The syntax of a Db2 Table URI is thoroughly described in section [Table unique resource identifier](https://cloud.ibm.com/docs/sql-query?topic=sql-query-overviewunique).





 Identifier 

An identifier is a name that uniquely identifies an entity. The two types of identifiers are unquoted identifiers and back quoted identifiers.



 Unquoted identifier 

An unquoted identifier is at least one character long. The following valid characters can be used:



* Digits 0-9
* Letters a-z, A-Z
* Underscore _







 Back quoted identifier 

It is an identifier that is embraced by grave accent characters. A back quoted identifier can contain any character. That includes the grave accent character that must be escaped like this .

The following example shows how to add a column name that contains a special character:

SELECT col1 as Lösung FROM VALUES 1, 2 ,3







 Table Identifier 

A table identifier uniquely identifies a table or view in the catalog of the Data Engine instance. The following valid characters can be used:



* Digits 0-9
* Letters a-z, A-Z
* Underscore _







 Number 

A number is either a signed or unsigned integer or a decimal number.





 Unsigned number 

An unsigned number is an integer or decimal number without sign or type suffix.





 >Unsigned integer number 

An unsigned integer is an integer number without sign or type suffix.



 Integer number 

An integer number is represented by a sequence of at least one digit, thus 0 to 9. The integer number can have a suffix denoting the type of integer number. The three types of integer numbers are:



* Y: tiny integer number
* S: small integer number
* L: large integer number



For more information about data types, see [dataType](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referencedataType).
You can create an action by using a payload file or the command's interactive mode.

Ensure the location and the url endpoint are pointing to the same region when you create or update the workspaces and actions. For more information about location and endpoint, see [Where is my information stored?](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location).

Syntax

ibmcloud schematics action create --name ACTION_NAME [--description DESCRIPTION] --location GEOGRAPHY --resource-group RESOURCE_GROUP [--template GIT_TEMPLATE_REPO] [--playbook-name PLAYBOOK_NAME] [--credential CREDENTIAL_FILE] [--credential-json CREDENTIAL_JSON_FILE] [--bastion BASTION_HOST_IP_ADDRESS] [--bastion-credential-json BASTION_CREDENTIAL_JSON_FILE] [--inventory INVENTORY_ID] [—-inventory-connection-type INVENTORY_CONNECTION_TYPE] [--input INPUT_VARIABLES_LIST] [--input-file INPUT_VARIABLES_FILE_PATH] [--env ENV_VARIABLES_LIST] [--env-file ENV_VARIABLES_FILE_PATH] [--github-token GITHUB_ACCESS_TOKEN] [--output OUTPUT] [--file FILE_NAME ] [--json] [--no-prompt]

Command options



Schematics Actions create flags

 Flag Required / Optional Description 

 --name or -n Required A unique name for the action. 
 --description or -d Optional The short description for an action. 
 --location or -l Required The geography or location where you want to create the action, such as us-south, us-east, eu-de, or eu-gb. The geography or location determines where your action runs and where your action data is stored. For more information, see [Where is my information stored?](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location).
Site map 



 Getting started 

[Getting started: IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-startedgetting-started)

[Using Workspaces to deploy infrastructure and cloud services](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-terraformget-started-terraform)



* [Before you begin](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-terraformprereq)
* [Creating an IBM Cloud Object Storage instance with Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-terraformcreate-cos)



* [Output](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-terraformcreate-cos-output)



* [What's next?](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-terraformwhats-next-gs)



[Using Agents to perform configuration management](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started-ansiblegetting-started-ansible)



* [Before you begin](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started-ansibleansible-prereq)
* [Starting and stopping Virtual Servers for VPC](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started-ansibleansible-vsi)
* [What's next?](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started-ansibleansible-whats-next)
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Creating views ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Creating dashboards !
[IBM Cloud Schematics CLI](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-cli-reference)



* [Prerequisites](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencecli-prerequisites)
* [Actions commands](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-action-commands)



* [Inventory host groups](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceinventory-host-grps)
* [ibmcloud schematics action create](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-create-action)
* [ibmcloud schematics action update](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-update-action)
* [ibmcloud schematics action get](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-get-action)
* [ibmcloud schematics action list](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-list-action)
* [ibmcloud schematics action delete](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-delete-action)
curl -s -X POST -H "Content-Type: Application/json" --data '{ "name": "test-source-jdbc", "config": { "connector.class": "io.aiven.connect.jdbc.JdbcSourceConnector", "tasks.max": "1", "connection.url":"jdbc:netezza://localhost:5480/db1;user=user1;password=secret","connection.user":"user1","connection.password":"secret","dialect.name":"GenericDatabaseDialect","topic.prefix":"my","mode": "bulk", "poll.interval.ms":"60000", "table.whitelist":"TEST_TABLE", "batch.max.rows":"10000000" } }' http://localhost:8083/connectors | jq
{
"name": "test-source-jdbc",
"config": {
"connector.class": "io.aiven.connect.jdbc.JdbcSourceConnector",
"tasks.max": "1",
"connection.url": "jdbc:netezza://localhost:5480/db1;user=user1;password=secret,
"connection.user": ""user1,
"connection.password": "secret",
"dialect.name": "GenericDatabaseDialect",
"topic.prefix": "my",
"mode": "bulk",
"poll.interval.ms": "60000",
"table.whitelist": "TEST_TABLE",
"batch.max.rows": "10000000",
"name": "test-source-jdbc"
},
"tasks": [],
"type": "source"
}
Show more
* For the sink connector, run the following command.
Example 1: Create views that you export to be imported into other modules.

This example creates two views, FirstName, and NotFirstName. The view FirstName collects information about the given names that are represented in the FirstNamesDictionary dictionary. The second view collects the names that are left when you exclude the given names. Two dictionaries are necessary to make the text extraction easier. One dictionary contains all of the given names that you want to search for. The second dictionary, LastNamesDictionary, contains the surnames to search for. The FirstName and the NotFirstName views are exported so that they can be imported and used in other modules, such as module person in Examples 2 and 3.

module personName;

create dictionary FirstNamesDictionary as
('Smith', 'John', 'Mary', 'Sam', 'George');

create view FirstName as
extract dictionary 'FirstNamesDictionary'
on D.text as firstName
from Document D;

export view FirstName;

create dictionary LastNamesDictionary as
('Stewart', 'Johnson', 'Smith', 'Hopkins', 'George');

create view NotFirstName as
select F.firstName as notFirstName from FirstName F
where ContainsDict('LastNamesDictionary', F.firstName);

export view NotFirstName;
Show more

Example 2: Importing the view FirstName by using alias import

This example imports one of the views that were created and exported in Example 1. Then, the PersonFirstName view is output so that its results can be viewed.

The sample import statement is known as an alias import. It imports the view FirstName, with no module qualifier, to the namespace of the current module, person. The imported view can be accessed only through the alias name PersonFirstName and not through any other form. For example, you cannot refer to the imported view as personName.FirstName because it is imported only through the alias name.

module person;

import view FirstName from module personName as PersonFirstName;

output view PersonFirstName;
Manage Wason Knowledge Catalog(WKC) policy enforcement status.



 ibmcloud watson-query policy-status-update 

Turn on WKC policy enforcement status.

ibmcloud watson-query policy-status-update --status STATUS



 Command options 

--status (string)
: Set the status of WKC policy - can be 'enable' or 'disable'. Required.





 Examples 

Turn on or off WKC policy enforcement status

ibmcloud watson-query policy-status-update --enable







 ibmcloud watson-query policy-status 

Get WKC policy enforcement status, return enabled or disabled.

ibmcloud watson-query policy-status



 Examples 

Get WKC policy enforcement status

ibmcloud watson-query policy-status









 Virtualization 

Create virtualized table.



 ibmcloud watson-query virtualized-table-create 

Transform a given data source table into a virtualized table.

ibmcloud watson-query virtualized-table-create --source-table-name SOURCE-NAME --source-table-def-file SOURCE-TABLE-DEF-FILE --sources SOURCES --virtualized-table-name VIRTUALIZED-NAME --virtualized-schema VIRTUALIZED-SCHEMA --virtualized-table-def-file VIRTUALIZED-TABLE-DEF-FILE [--is-included-columns IS-INCLUDED-COLUMNS] [--replace REPLACE]



 Command options 

--source-table-name (string)
: The name of the source table. Required.

--source-table-def-file ([VirtualizeTableSourceTableDefFile](https://cloud.ibm.com/docs/watson-query-cli-plugincli-virtualize-table-parameter-source-table-def-item-example-schema))
: Required.

--sources ([]string)
: The name of data source. Required.

--virtualized-table-name (string)
: The name of the table that will be virtualized. Required.

--virtualized-schema (string)
Manage Wason Knowledge Catalog(WKC) policy enforcement status.



 ibmcloud watson-query policy-status-update 

Turn on WKC policy enforcement status.

ibmcloud watson-query policy-status-update --status STATUS



 Command options 

--status (string)
: Set the status of WKC policy - can be 'enable' or 'disable'. Required.





 Examples 

Turn on or off WKC policy enforcement status

ibmcloud watson-query policy-status-update --enable







 ibmcloud watson-query policy-status 

Get WKC policy enforcement status, return enabled or disabled.

ibmcloud watson-query policy-status



 Examples 

Get WKC policy enforcement status

ibmcloud watson-query policy-status









 Virtualization 

Create virtualized table.



 ibmcloud watson-query virtualized-table-create 

Transform a given data source table into a virtualized table.

ibmcloud watson-query virtualized-table-create --source-table-name SOURCE-NAME --source-table-def-file SOURCE-TABLE-DEF-FILE --sources SOURCES --virtualized-table-name VIRTUALIZED-NAME --virtualized-schema VIRTUALIZED-SCHEMA --virtualized-table-def-file VIRTUALIZED-TABLE-DEF-FILE [--is-included-columns IS-INCLUDED-COLUMNS] [--replace REPLACE]



 Command options 

--source-table-name (string)
: The name of the source table. Required.

--source-table-def-file ([VirtualizeTableSourceTableDefFile](https://cloud.ibm.com/docs/cli?topic=cli-CLI-namecli-virtualize-table-parameter-source-table-def-item-example-schema))
: Required.

--sources ([]string)
: The name of data source. Required.

--virtualized-table-name (string)
: The name of the table that will be virtualized. Required.

--virtualized-schema (string)
ibmcloud watson-query primary-catalog-set --guid d77fc432-9b1a-4938-a2a5-9f37e08041f6







 ibmcloud watson-query primary-catalog-delete 

Remove the setting of the primary catalog for enforced publication.

ibmcloud watson-query primary-catalog-delete --guid GUID



 Command options 

--guid (string)
: The watson query user name, if the value is PUBLIC, it means revoke access privilege from all watson query users. Required.









 Publish objects 

Publish virtualized table to WKC.



 ibmcloud watson-query virtualized-table-publish 

Publish virtualized tables to WKC.

ibmcloud watson-query virtualized-table-publish --catalog-id CATALOG-ID --allow-duplicates ALLOW-DUPLICATES --assets ASSETS



 Command options 

--catalog-id (string)
: Catalog ID. Required.

--allow-duplicates (bool)
: Whether duplicated asset allowd. Required.

--assets ([CatalogPublishParametersAssetsItem[]](https://cloud.ibm.com/docs/cli?topic=cli-CLI-namecli-catalog-publish-parameters-assets-item-example-schema))
: Asset description. Example: "[{"schema": "db2inst1","table": "employee"}]". Required.





 Examples 

Publish virtualized tables to WKC

ibmcloud watson-query virtualized-table-publish --catalog-id 12c60f7e-c366-4cda-ba3a-bfbb577a5f56 --allow-duplicates true --virtualized-schema DV_IBMID_6610020D12 --virtualized-table EMPLOYEE









 Schema examples 

The following schema examples represent the data that you need to specify for a command option. These examples model the data structure and include placeholder values for the expected value type.
target-table-storage Target table file storage location ibm-lh data-copy --target-table-storage <TARGET_TABLE_STORAGE> 
 target-tables Data migration target table. <catalog>.<schema>.<table1>. Example: <iceberg.demo.customer1> ibm-lh data-copy --target-tables <TARGET_TABLES> 
 schema Schema file that includes CSV specifications, and so on ibm-lh data-copy --schema <SCHEMA> 
 target-s3-creds S3 credentials of target location ibm-lh data-copy --target-s3-creds <TARGET_S3_CREDS> 
 ingestion-engine-endpoint Endpoint of ingestion engine. hostname=<hostname>,port=<port> ibm-lh data-copy --ingestion-engine-endpoint <INGESTION_ENGINE_ENDPOINT> 
 dbuser Username of ingestion engine ibm-lh data-copy --dbuser <DBUSER> 
 dbpassword User password of ingestion engine ibm-lh data-copy --dbpassword <DBPASSWORD> 
 trust-store-path Path of truststore to access ingestion engine. This is used for making SSL connections. ibm-lh data-copy --trust-store-path <TRUST_STORE_PATH> 
 trust-store-password Password of truststore to access ingestion engine. This is used for making SSL connections. ibm-lh data-copy --trust-store-password <TRUST_STORE_PASSWORD> 
 create-if-not-exist Create target table if not existed ibm-lh data-copy --create-if-not-exist 



2. Configuration file option

The Configuration file contains a global ingest configuration section and multiple individual ingest configuration sections to perform the ingestion job. The specifications of the individual ingestion sections override the specifications of the global ingestion section.

a. Global ingest config section



Table 2. Global ingest config options and variables

 Parameter Description Declaration
[Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 
 Create views ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 
 Create dashboards ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 
 Create screens !
ibmcloud watson-query primary-catalog-set --guid d77fc432-9b1a-4938-a2a5-9f37e08041f6







 ibmcloud watson-query primary-catalog-delete 

Remove the setting of the primary catalog for enforced publication.

ibmcloud watson-query primary-catalog-delete --guid GUID



 Command options 

--guid (string)
: The watson query user name, if the value is PUBLIC, it means revoke access privilege from all watson query users. Required.









 Publish objects 

Publish virtualized table to WKC.



 ibmcloud watson-query virtualized-table-publish 

Publish virtualized tables to WKC.

ibmcloud watson-query virtualized-table-publish --catalog-id CATALOG-ID --allow-duplicates ALLOW-DUPLICATES --assets ASSETS



 Command options 

--catalog-id (string)
: Catalog ID. Required.

--allow-duplicates (bool)
: Whether duplicated asset allowd. Required.

--assets ([CatalogPublishParametersAssetsItem[]](https://cloud.ibm.com/docs/watson-query-cli-plugincli-catalog-publish-parameters-assets-item-example-schema))
: Asset description. Example: "[{"schema": "db2inst1","table": "employee"}]". Required.





 Examples 

Publish virtualized tables to WKC

ibmcloud watson-query virtualized-table-publish --catalog-id 12c60f7e-c366-4cda-ba3a-bfbb577a5f56 --allow-duplicates true --virtualized-schema DV_IBMID_6610020D12 --virtualized-table EMPLOYEE









 Schema examples 

The following schema examples represent the data that you need to specify for a command option. These examples model the data structure and include placeholder values for the expected value type.
nz_get_mgmt_table_name
nz_get_mgmt_table_names
nz_get_mgmt_view_name
nz_get_mgmt_view_names
nz_get_model
nz_get_mview_basename
nz_get_mview_definition
nz_get_mview_matrelid
nz_get_mview_name
nz_get_mview_names
nz_get_mview_objid
nz_get_mview_owner
nz_get_object_name
nz_get_object_objid
nz_get_object_owner
nz_get_object_type
nz_get_procedure_name
nz_get_procedure_names
nz_get_procedure_signatures
nz_get_role_name
nz_get_role_names
nz_get_schema_name
nz_get_schema_names
nz_get_schema_objid
nz_get_sequence_name
nz_get_sequence_names
nz_get_sequence_objid
nz_get_sequence_owner
nz_get_stableTXid
nz_get_synonym_definition
nz_get_synonym_name
nz_get_synonym_names
nz_get_synonym_objid
nz_get_synonym_owner
nz_get_sysmgmt_table_name
nz_get_sysmgmt_table_names
nz_get_sysmgmt_table_objid
nz_get_sysmgmt_view_name
nz_get_sysmgmt_view_names
nz_get_sysmgmt_view_objid
nz_get_sys_table_name
nz_get_sys_table_names
nz_get_sys_view_name
nz_get_sys_view_names
nz_get_table_distribution_key
nz_get_table_fks
nz_build_html_help_output
nz_catalog_dump
nz_catalog_size
nz_change_owner
nz_check_statistics
nz_check_views
nz_cksum
nz_clone
nz_columns
nz_compiler_stats
nz_compressedTableRatio
nz_db_group_access_listing
nz_db_size
nz_db_tables_rowcount
nz_db_tables_rowcount_statistic
nz_db_user_access_listing
nz_db_views_rowcount
nz_ddl
nz_ddl_aggregate
nz_ddl_all_grants
nz_ddl_comment
nz_ddl_database
nz_ddl_diff
nz_ddl_ext_table
nz_ddl_function
nz_ddl_grant_group
nz_ddl_grant_role
nz_ddl_grant_user
nz_ddl_group
nz_ddl_history_config
nz_ddl_mview
nz_ddl_object
nz_ddl_owner
nz_ddl_procedure
nz_ddl_role
nz_ddl_scheduler_rule
nz_ddl_schema
nz_ddl_security
nz_ddl_sequence
nz_ddl_synonym
nz_ddl_sysdef
nz_ddl_table
nz_ddl_table_redesign
nz_ddl_user
nz_ddl_view
nz_ddl_view+
nz_dimension_or_fact
nz_find_32bit_udx
nz_find_control_chars_in_data
nz_find_non_integer_strings
nz_find_object
nz_find_object_orphans
nz_find_object_owners
nz_find_table_orphans
nz_fix_the_permissions
nz_frag
nz_genstats
nz_get
(https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) 
 blueprint create ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) 
 blueprint update ![Check mark icon.]
Your external (publisher) PostgreSQL needs to have a replication user that has the [PostgreSQL privilege REPLICATION](https://www.postgresql.org/docs/current/sql-createrole.htmlreplication), and that user needs to have privileges on the databases you would like replicate.
3. The PostgreSQL you are replicating from needs to have [TLS/SSL enabled](https://www.postgresql.org/docs/current/ssl-tcp.html).



There are inherent limitations and some restrictions to logical replication outlined in the [PostgreSQL documentation](https://www.postgresql.org/docs/current/logical-replication-restrictions.html). Review these before deciding that logical replication is appropriate for your use-case.





 Configuring the Subscriber 

To configure your Databases for PostgreSQL deployment and to make sure that your data is replicated across correctly,



1. You need to create a database in your deployment with same name as the database you intend to replicate.
2. Logical Replication works at the table level, so every table you select to publish, you need to create in the subscriber before starting the logical replication process. (You can use [pg_dump](https://www.postgresql.org/docs/current/app-pgdump.html) to help.) The table on the subscriber does not need to be identical to its publisher counterpart. However, the table on the subscriber must contain at least every column present in the table on the publisher. Additional columns present in the subscriber must not have NOT NULL or other constraints. If they do, replication fails.



Note Native PostgreSQL subscription commands require superuser privileges, which are not available on Databases for PostgreSQL deployments. Instead, your deployment includes a set of functions that can be used to set and manage logical replication for the subscription.