vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The json file content example: "[{"column_name":"COL1","column_type":"VARCHAR"}]"







 ibmcloud watson-query virtualized-table-delete 

Remove specified virtualized table. You must specify the schema and table name.

ibmcloud watson-query virtualized-table-delete --virtualized-schema VIRTUALIZED-SCHEMA --virtualized-name VIRTUALIZED-NAME



 Command options 

--virtualized-schema (string)
: The schema of virtualized table to be deleted. Required.

--virtualized-name (string)
: The name of virtualized table to be deleted. Required.





 Examples 

Delete virtualized table

ibmcloud watson-query virtualized-table-delete --virtualized-schema DV_IBMID_270001PD8Q --virtualized-name TABLE1









 Primary catalog 

Manage the primary WKC catalog information in watson query console.



 ibmcloud watson-query primary-catalog 

Get primary catalog ID from the table.

ibmcloud watson-query primary-catalog



 Examples 

Get primary catalog ID from the table DVSYS.INSTANCE_INFO

ibmcloud watson-query primary-catalog







 ibmcloud watson-query primary-catalog-set 

Insert primary catalog ID into table DVSYS.INSTANCE_INFO.

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



 Command options 

--guid (string)
: Primary catalog ID. Required.





 Examples 

Insert primary catalog ID into table DVSYS.INSTANCE_INFO

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)
* Reader role access to the Event Streams cluster resource type.
* Manager role access to the schema resource that matches the schema that is deleted.



An activity tracker event is generated to report the action. For more information, see [Activity Tracker events](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-at_eventsevents).





 Create a new version of a schema 

To create a new version of a schema, make a POST request to the /artifacts/{schema-id}/versions endpoint, (where {schema-id} is the ID of the schema). The body of the request must contain the new version of the schema.

If the request is successful, the new schema version is created as the new latest version of the schema, with an appropriate version number, and a response with status code 200 (OK), and a payload that contains metadata describing the new version (including the version number), is returned.

Example curl request:

curl -u token:$APIKEY -H 'Content-Type: application/json' $URL/artifacts/my-schema/versions -d '{"type":"record","name":"Citizen","fields":[{"name": "firstName","type":"string"},{"name":"lastName","type":"string"},{"name":"age","type":"int"},{"name":"phoneNumber","type":"string"}]}'

Example response:

{"id":"my-schema","type":"AVRO","version":2,"createdBy":"","createdOn": 1579267978382,"modifiedBy":"","modifiedOn":1579267978382,"globalId":83}

Creating a new version of a schema requires at least both:



* Reader role access to the Event Streams cluster resource type.
* Writer role access to the schema resource that matches the schema that gets a new version.
--source-table-def-file ([VirtualizeTableSourceTableDefFile](https://cloud.ibm.com/docs/watson-query-cli-plugin?topic=watson-query-cli-plugin-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)
: The schema of the table that will be virtualized. Required.

--virtualized-table-def-file ([VirtualizeTableVirtualTableDefFile](https://cloud.ibm.com/docs/watson-query-cli-plugin?topic=watson-query-cli-plugin-CLI-namecli-virtualize-table-parameter-virtual-table-def-item-example-schema))
: Required.

--is-included-columns (string)
: The columns that are included in the source table.

--replace (bool)
: Determines whether to replace columns in the virtualized table.





 Examples 

Virtualize table

ibmcloud watson-query virtualized-table-create --source-table-name table1 --source-table-def-file source_tabel_def.json --virtualized-schema DV_IBMID_270001PD8Q --sources CONN1:TABLE1 --virtualized-table-name TABLE1 --virtualized-table-def-file virtualized_table_def.json. The json file content example: "[{"column_name":"COL1","column_type":"VARCHAR"}]"







 ibmcloud watson-query virtualized-table-delete 

Remove specified virtualized table. You must specify the schema and table name.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 
 Creating views ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) !
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). You should review these before deciding that logical replication is appropriate for your use-case.





 Configuring the Subscriber 

To configure your Databases for EnterpriseDB 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 EnterpriseDB deployments. Instead, your deployment includes a set of functions that can be used to set and manage logical replication for the subscription.

Only the admin user that is provided by Databases for EnterpriseDB has permissions to run the following replication commands that allow you to subscribe and replicate content from an external PostgreSQL publisher.



 Subscriber Functions 

create_subscription

Arguments:
subscription_name Unique name to create the subscription channel with
host_ip Publisher hostname or public IP address
port Port number publisher is running on
username admin user created on the publisher
password Password of the admin user on the publisher
db_name The name of the database to be replicated
publisher_name The name of publisher channel on the publisher

Usage:
"username" : "db2inst1",
"warehouse" : "exampleString"
}
Show more





 VirtualizeTableSourceTableDefFile 

The following example shows the format of the VirtualizeTableSourceTableDefFile object.

[ {
"column_name" : "Column1",
"column_type" : "INTEGER"
} ]





 VirtualizeTableVirtualTableDefFile 

The following example shows the format of the VirtualizeTableVirtualTableDefFile object.

[ {
"column_name" : "Column_1",
"column_type" : "INTEGER"
} ]
<xsd:element name="property" type="propertyType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="table">
<xsd:annotation>
<xsd:documentation>Represents a table.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="namedObjectType">
<xsd:sequence>
<xsd:element ref="column" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Table columns.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="column">
<xsd:annotation>
<xsd:documentation>The column.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="namedObjectType">
<xsd:sequence>
<xsd:element name="datatype" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
<para>Full data type. e,g, VARCHAR(20).</para>
<para>ARRAY</para>
<para>BIGINT</para>
<para>BINARY</para>
<para>BIT</para>
<para>BLOB</para>
<para>BOOLEAN</para>
Distribution keys for multi-partitioned plans 

When creating a table in one of the IBM® Db2® Warehouse on Cloud [multi-partitioned plans](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-aboutplans_cfgs), you can decide how you want to distribute data among data partitions.

You can use either [hash distribution](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-distribution_keyshash_distrib) or [random distribution](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-distribution_keysrandom_distrib).



 Hash distribution 

With hash distribution, data is distributed by applying a hashing algorithm to the values in the columns that are listed in a distribution key. A well-chosen distribution key can balance two objectives:



* Maximizing parallel processing of queries and maximizing the use of available storage space by distributing table data evenly across the system, and
* Minimizing the time that it takes to fetch data by collocating data that is likely to be fetched together.



In general, a well-chosen hash distribution key produces the best performance. You can specify the distribution key by including the DISTRIBUTE BY HASH clause in the CREATE TABLE statement:

CREATE TABLE MYTABLE
(
COL1 INT,
COL2 VARCHAR(5)
)
DISTRIBUTE BY HASH( COL1 )

For more information about choosing hash distribution keys, see [Choosing a hash distribution key for a table in an MPP database](https://www.ibm.com/support/knowledgecenter/SS6NHC/com.ibm.swg.im.dashdb.doc/learn_how/choosing_dist_key_mpp.html).





 Random distribution 

With random distribution, data is distributed evenly across the system. Random distribution maximizes parallel processing of queries and maximizes the use of available storage space.

Consider using random distribution as a simpler alternative to hash distribution, for the following reasons:



1. If you don't have enough information to choose an effective hash distribution key,
[EMP Endpoint](https://cloud.ibm.com/docs-content/v1/content/e2b18e1112dc55facb736744a935365dce13849a/databases-for-enterprisedb/images/emp-endpoint.png)

Figure 1. EMP Endpoint



1. Copy the Endpoint URL into a new browser window to start the EMP.
2. In the resulting window, log in using your IBM Cloud account credentials.









 Databases for EnterpriseDB schema migration by using EMP 



 Extract the schema 



1. Log in to the EnterpriseDB migration portal (EMP).
2. Click Portal Wiki
3. Follow the steps in DDL Extractor guide section
4. After a successful attempt, a file like _gen_ot_ddls_2005111737123.sql is created in the specified path







 Validate the extracted schema 



1. Log in to the EnterpriseDB migration portal (EMP)
2. Create a project by clicking New.
3. Enter a project name, and load the DDL Extractor-generated file for assessment. EMP accepts only single string project names without spaces.

Zoom

![migration-portal-setup](https://cloud.ibm.com/docs-content/v1/content/e2b18e1112dc55facb736744a935365dce13849a/databases-for-enterprisedb/images/emp-new-project.png)

Figure 2. migration-portal-setup
4. Click Create & Assess.
5. Fix any issue report by the EMP and make sure you are getting 100% coverage successfully







 Migrate your exported converted schema into your EnterpriseDB formation 

Export and deploy the converted schema from migration portal to your provisioned Databases for EnterpriseDB formation.



1. Select the Migrate to... button to begin the migration process.

Zoom

!
* Location as North America or other [region](https://cloud.ibm.com/docs/schematics?topic=schematics-multi-region-deployment) for this workspace. Decide where you want to create your workspace? The location determines where your Schematics jobs run?, and where your workspace data is stored? You can choose between a location, such as North America, or a metro city, such as Frankfurt or London. If you select a location, Schematics determines the location based on availability. If you select a metro city, your workspace is created in this location. For more information about where your data is stored, see [Where is your information stored](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location)? The location that you choose is independent from the region or regions where you want to provision your IBM Cloud resources. The console does not support all available locations. To create the workspace in a different location, use the [CLI](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-new) or [API](https://cloud.ibm.com/apidocs/schematics/schematicscreate-a-workspace) instead.
* Optional, enter a descriptive name for your workspace.
* Click Next.



* Click Create. Your workspace is created with a Draft state and the workspace Settings page opens.







 Importing your Terraform template 

If you want to upload a tape archive file (.tar) instead of importing your workspace to a Git repository, you must use the [ibmcloud schematics workspace upload](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-upload) command and see the [upload a tar file to your workspace](https://cloud.ibm.com/apidocs/schematics/schematicsupload-template-tar) API.
--help or -h Required Lists the supported commands. 
 command Optional Specify the name of the command to fetch the command details. 



Example

ibmcloud schematics help





 ibmcloud schematics version 

List the versions of all supported open source projects in Schematics, such as the IBM Cloud Provider Plug-in for Terraform, Ansible, Helm, and Kubernetes that are used to run Schematics Actions on IBM Cloud resources.

Syntax

ibmcloud schematics version [--output OUTPUT] [--json JSON_FILE]

Command options



Schematics version flags

 Flag Required / Optional Description 

 --json or -j Deprecated Returns the CLI output in JSON format. 
 --output or -o Optional Returns the CLI output in JSON format. Currently only JSON file format is supported. 



Example

ibmcloud schematics version --output json > "<filename.json>"







 Inventories commands 

Review the command that you want to create, update, list, delete and to work with your IBM Cloud Schematics inventory.



 ibmcloud schematics inventory create 

Create a resource inventory in IBM Cloud Schematics that you can reference in a Schematics action. A resource inventory includes all the target hosts where you want to run an Ansible playbook. You can create an inventory by using a payload file or the interactive mode.

Syntax

ibmcloud schematics inventory create --name INVENTORY_NAME [--description DESCRIPTION] [--location GEOGRAPHY] [--resource-group RESOURCE_GROUP] [--inventories-ini INVENTORY_INI_FILE] [--resource-query RESOURCE_QUERY_ID] [--file FILE_NAME ] [--output OUTPUT] [--no-prompt]

You need to pass either --inventories-ini file path or --resource-query ID for the inventory to use the target host details.

Command options



Schematics inventory create flags

 Flag Required / Optional Description 

 --name or -n Required The unique name of a resource inventory. 
 --description or -d Optional The short description of an inventory.
For more information about choosing hash distribution keys, see [Choosing a hash distribution key for a table in an MPP database](https://www.ibm.com/support/knowledgecenter/SS6NHC/com.ibm.swg.im.dashdb.doc/learn_how/choosing_dist_key_mpp.html).





 Random distribution 

With random distribution, data is distributed evenly across the system. Random distribution maximizes parallel processing of queries and maximizes the use of available storage space.

Consider using random distribution as a simpler alternative to hash distribution, for the following reasons:



1. If you don't have enough information to choose an effective hash distribution key,
2. If you know that collocation isn't needed for the queries that are entered against the table, or
3. If the table is small enough that performance is not affected by the distribution.



You can use random distribution by including the DISTRIBUTE BY RANDOM clause in the CREATE TABLE statement.

If you specify DISTRIBUTE BY RANDOM when creating a table with a primary or unique key, the database manager implements the random distribution by creating a hash key on the unique or primary key. In this case, when you view the table definition in the web console or the catalog tables, you'll see this hash distribution key despite the fact that you specified DISTRIBUTE BY RANDOM when you created the table.

CREATE TABLE MYTABLE
(
COL1 INT,
COL2 VARCHAR(5)
)
DISTRIBUTE BY RANDOM





 Default behavior 

If you do not specify a distribution clause when creating a table in a multi-partitioned plan, a default hash distribution key is used.
This set up adds a layer of security to your IBM Cloud resources, and minimize the surface of potential vulnerabilities. Note now the Actions support only one SSH key for all virtual server instances. The SSH key must contain n at the end of the key details in case of command-line or API calls.





 ibmcloud schematics action create 

Create an action to run an Ansible playbook on a single target host or a group of target hosts. You use Ansible playbooks to perform cloud operations or install software on cloud resources. To try out this capability or to get started, use one of the [IBM-provided Ansible playbooks](https://github.com/Cloud-Schematics?q=topic%3Aansible-playbook). 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
[Working with Schematics Actions](https://cloud.ibm.com/docs/schematics?topic=schematics-action-workingaction-working)



* [Creating and running a Schematics action](https://cloud.ibm.com/docs/schematics?topic=schematics-action-workingcreate-action)



* [Prerequisites](https://cloud.ibm.com/docs/schematics?topic=schematics-action-workingaction-working-prereq)
* [To create an action](https://cloud.ibm.com/docs/schematics?topic=schematics-action-workingcreate-action-working)



* [Editing the Schematics Actions settings](https://cloud.ibm.com/docs/schematics?topic=schematics-action-workingaction-settings)
* [Deleting an action](https://cloud.ibm.com/docs/schematics?topic=schematics-action-workingdelete-ansible-actions)
* [Action state](https://cloud.ibm.com/docs/schematics?topic=schematics-action-workingaction-state-diagram)



* [State diagram flow](https://cloud.ibm.com/docs/schematics?topic=schematics-action-workingstate-diagram-flow)



* [Reviewing Actions job details](https://cloud.ibm.com/docs/schematics?topic=schematics-action-workingaction-jobs)



[Creating an Ansible playbook](https://cloud.ibm.com/docs/schematics?topic=schematics-create-playbookcreate-playbook)



* [Referencing Ansible collections in your playbook](https://cloud.ibm.com/docs/schematics?topic=schematics-create-playbookschematics-collections)
"lastname": "Brown",
"age": 16,
"location": "New York City, NY"
},
{
"_id": "doc2",
"firstname": "John",
"lastname": "Brown",
"age": 21,
"location": "New York City, NY"
},
{
"_id": "doc3",
"firstname": "Greg",
"lastname": "Greene",
"age": 35,
"location": "San Diego, CA"
},
{
"_id": "doc4",
"firstname": "Anna",
"lastname": "Greene",
"age": 44,
"location": "Baton Rouge, LA"
},
{
"_id": "doc5",
"firstname": "Lois",
"lastname": "Brown",
"age": 33,
"location": "Syracuse, NY"
}
]
}
Show more
2. Run this command to create the documents.

curl "https://username:password@myhost.cloudant.com/couchbackup-demo/_bulk_docs" -X POST -H "Content-Type: application/json" -d @bulkcreate.dat
3. Review the results.

[
{
"ok": true,
"id": "doc1",
"rev": "1-57a08e644ca8c1bb8d8931240427162e"
},
{
"ok": true,
"id": "doc2",
"rev": "1-bf51eef712165a9999a52a97e2209ac0"
},
{
"ok": true,
On successful, returns the list of the workspace.

For more information, see [FAQ](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faq), and [troubleshooting section](https://cloud.ibm.com/docs/schematics?topic=schematics-wks-create-api).







 Generating a workspace plan using Terraform 



1. Follow the steps in [Setting up Terraform for Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-terraform-setup) to create your workspace with Terraform.
2. See [Managing IBM Cloud resources with Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-manage-lifecycle) to start creating, updating, or deleting IBM Cloud resources with Terraform.







 Next steps 

The next stage of working with workspace is [deploying workspaces](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wks).

For more information, see [FAQ](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faq), and [troubleshooting section](https://cloud.ibm.com/docs/schematics?topic=schematics-wks-create-api).
* [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)



[Software deployment in IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-softwareget-started-software)



* [Before you begin](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-softwarevsi-postgres-prereq)
* [Setting up and configuring a classic VSI to run PostgreSQL with Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-softwarevsi-postgres)
* [What's next?](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-softwarewhats-next)



[Using Blueprints to deploy large-scale cloud environments](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-blueprintsget-started-blueprints)



* [Deploy blueprint through UI](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-blueprintsdeploy-bp-ui)



* [Creating a blueprint in Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-blueprintsget-started-blueprints-create-ui)