vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Datastore Properties - Target](https://cloud.ibm.com/docs-content/v1/content/68e10678b2f8b8694884ecb5442c326c9b60a3fb/Db2whc/connecting/images/IIDR_target_datastore.jpg)

Figure 5. View of target datastore properties

c. If the user (for example, admin) that connects to the Access Server does not exist, create that user:

Zoom

![New User](https://cloud.ibm.com/docs-content/v1/content/68e10678b2f8b8694884ecb5442c326c9b60a3fb/Db2whc/connecting/images/IIDR_management_user.jpg)

Figure 6. View of New User creation tool

d. Click the Access Manager tab.

e. On the Datastore Management tab, assign the user to both the source and target datastores by right-clicking each datastore and then clicking Assign User. Ensure that the credentials for accessing each instance are correct.

Zoom

![IIDR Management Console - Access Manager](https://cloud.ibm.com/docs-content/v1/content/68e10678b2f8b8694884ecb5442c326c9b60a3fb/Db2whc/connecting/images/IIDR_management_assign_user.jpg)

Figure 7. IIDR Management Console - Access Manager







 What to do next 

Define a subscription and perform data replication. For information, see:



* [Loading data from InfoSphere Data Replication](https://www.ibm.com/support/knowledgecenter/SS6NHC/com.ibm.swg.im.dashdb.doc/learn_how/loaddata_iidr.html)









 Data Studio 

These instructions explain how to create a connection from IBM® Data Studio to a Db2 Warehouse on Cloud database.



 Prerequisites
1. Verify that the Connector ID and region are specified correctly.
2. Open the Logging Dashboard and review the Connector logs. Often, the issue is with the IAM API key and you see a message similar to the following example. For more information, see [Why isn't my API key working](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-connector-api).

Failed to get configuration from API /v1/connectors/U2F0ZWxsaXRlQ29ubmVjdG9yOiJjaTExMGxpdzFwazluMGdybXUyMCI, region us-east, code: 401. IAM Error: "status code: 400. Provided API key could not be found.", API Error: "null", hostname: "482bddf6c60b"
3. Check the log on the agent container. If there are no errors in the IBM Log Analysis Dashboard, this means there is an issue that is occuring before the agent communcates with the tunnel servers. You can get more information by looking at the log file on the agent container. The command varies by container platform. If you are using Docker, you can use the following command:

docker logs <container id>
4. You should be able to determine from the log messages what the issue is. The most common reason for errors is that your agent does not have public outbound access to talk to the IBM tunnel servers. See [Why is my Connector Agent unable to establish the tunnel with IBM Cloud](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-connector-tunnel).
5. Verify that you are using the correct container hardware platform. For example, you are trying to run the agent image on an arm64 platform. The connector agent will only run on linux/amd64 platforms or those platforms that can emulate amd64. If this is the case, you will see an error similar to:
Error from server: Get https://<10.xxx.xx.xxx>:<port>/<address>: dial tcp <10.xxx.xx.xxx>:<port>: connect: connection timed out

 Why it’s happening 

The OpenVPN server is experiencing configuration issues that prevent accessing the pod from its internal address.

 How to fix it 

Before you begin: [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



1. Check if a cluster and worker node updates are available by viewing your cluster and worker node details in the console or a cluster ls or worker ls command. If so, [update your cluster and worker nodes to the latest version](https://cloud.ibm.com/docs/openshift?topic=openshift-update).
2. Restart the OpenVPN pod by deleting it. Another VPN pod is scheduled. When its STATUS is Running, try to connect the pod that you previously could not connect to.

oc delete pod -n kube-system -l app=vpn







 500 error when trying to log in to a Red Hat OpenShift cluster via oc login 

 What’s happening 

When you try to log in to a Red Hat OpenShift cluster via oc login for the first time and you see an error message similar to the following.

$ oc login SERVER -u apikey -p <APIKEY>
The server uses a certificate signed by an unknown authority.
You can bypass the certificate check, but any data you send to the server could be intercepted by others.
Use insecure connections? (y/n): y

Error from server (InternalError): Internal error occurred: unexpected response: 500

 Why it’s happening 

Some recent changes to the IAM user role have not yet been synchronized to the Red Hat OpenShift cluster.

 How to fix it 

Synchronize the IAM user information to the Red Hat OpenShift cluster.
Classic clusters: Why does the master status have an ingress IP address for NLB error? 

Classic infrastructure

 What’s happening 

When you run ibmcloud oc cluster get -c <cluster_name_or_ID>, you see the following error message in the Master Status field.

CAE003: Unable to determine the ingress IP address for the network load balancer.

Additionally, when you run ibmcloud oc nlb-dns create to create a subdomain for a network load balancer (NLB), the command might fail with a message that the cluster is not found, the input parameters are incorrect, or you don't have the required roles.

 Why it’s happening 

The Konnectivity server could not be configured because load balancer IP address that exposes the default Ingress controller could not be found. The Ingress controller's load balancer service might not have been assigned an IP address because your cluster does not have a subnet with available portable IP addresses, or the load balancer setup did not complete.

 How to fix it 

Verify that your cluster has available subnets, and that the load balancer setup completed successfully.



 Verifying that your cluster has available subnets 



1. Check that your cluster has a Subnet CIDR for public and private subnets. If you set up a private VLAN-only cluster, you might have only a private subnet.

ibmcloud oc cluster get --cluster <cluster_name_or_ID> --show-resources

Example output

NAME: <cluster_name>
...

Subnet VLANs
VLAN ID Subnet CIDR Public User-managed
2345678 10.xxx.xx.xxx/29 false false
2876543 169.xx.xxx.xxx/29 true false
2.
From the IBM DB2 Connection window, enter the connection information by using the definitions in Table 1.
5. Click Connect to establish the connection. Tableau offers several options for connecting to your data. To make full use of your Db2 on Cloud database, choose the Connect Live option.





Table 1. Fields in Tableau for connection information

 Tableau field Db2 connections information field 

 Step 1: Enter a server name Host name 
 Step 2: Port Port number 
 Step 3: Enter a database on the server Database name 
 Username User ID 
 Password Password 









 Microsoft Excel 

These instructions explain how to connect Microsoft Excel to a Db2 on Cloud database.



 Prerequisites 

Before attempting to connect to your Db2 on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2onCloud/connecting?topic=Db2onCloud-connect_ovprereqs).

You must have the Db2 driver package or the IBM® Data Server Driver Package installed on your local computer.

Restriction: Connections between Excel and Db2 on Cloud are supported on only the Windows operating system.





 Procedure 



1. In the web console, go to the Run SQL page.
2. Type one or more SELECT statements in the editor text box.
3. Click one of the Run options.
4. Click Excel ODC File.
5. Download and open the BLUExcel.odc file in Excel. If a security notice is displayed, click Enable.
6. Click Open to connect to the Db2 on Cloud database. The Connect To DB2 Database dialog box opens.
7. Type the user ID and password that you use to log in to Db2 on Cloud. To obtain the user ID and password, click Connect in the web console or Connect > Connection Information in the web console.
8. Ensure that the connection mode is Share, and then click OK.







 Results 

The query results are displayed in an Excel spreadsheet. These results are the same results that are displayed in the Results viewer.
To specify a domain user, use the format <username>@<domain name>.
* password: Provide the password that is associated with the username.



8. Optional: If you want to change the default path and port settings, click Advanced Options.



* You can change the paths for the installation directory and data directory.
* The agent server uses three TCP/IP ports for authenticating connections to the server, transferring data between the file systems and Discovery, and monitoring the agent server. The default port numbers are 8397 and 8398. If those values conflict with other port assignments in your system, change the port numbers.



9. On the summary page, review the options that you selected, and click Install to start installing the software.
10. Optional: If you want to secure traffic between the Windows Agent service and the crawler, enable TLS support.

Copy the file named tls.p12 from the decompressed directory to the root directory where the agent is installed. For example, the root directory might be C:Program FilesIBMesdistributedesadmin.

TLS support is available starting with the 4.7 release.
11. Restart your computer.









 Configuring shared directories on the agent server 

After the software is installed, you must set up shared network directories that the Windows File System agent can access. To define a new file system share, export a local or remote network directory.

If you are replacing an agent that you installed with a release that is earlier than 4.6.0.0, skip this procedure. The replacement instructions explain how to reuse the file share that was defined previously.



1. Export a local directory from the server where the agent is installed:

esagent --addshare <d:><example>

Where d: represents the drive letter you want to use and where example represents the path to the local directory.
2. Export a remote network directory that is accessible from the server where the agent is installed:

esagent --addshare <\files.example.comdata>
If you log in to your account by using credentials that contain your corporation's name and also have what appears to be a personal account, the work within your personal account might belong to the corporation.

A corporate individual account is no different from any other account. You can invite users to a corporate individual account and objects that are created in a corporate individual account are owned by the account.

If you work for a corporation that owns your work, a personal account that usually contains your name is considered a corporate individual account.







 Modifying, exporting, and deleting personal data 

Regardless of what type of IBM Cloud account is used, if you have rights to the objects in the account, you can modify, export, and delete them. Before you make changes, coordinate with other users to make sure that you don't unnecessarily modify or delete data.

Before you delete data from an account, determine whether it is a personal account or a corporate individual account.



 Personal account 

If you own a personal account, you can make changes and delete your data. If you share your account with another user, you own the data, but you might want to contact them about the shared work.

If you can't log in to your IBM Cloud account, [contact IBM Support](https://www.ibm.com/cloud/support).





 Corporate individual account 

If you own a corporate individual account, you must coordinate any changes with both your corporation and other members of your team. Delete your personal data regardless of whether it is stored in a corporate account or a corporate individual account. Make sure that you don't delete work that you shared with other users.

Before you start to manage your personal data for the Continuous Delivery components, make sure that you are working in your IBM Cloud account. To view the IBM Cloud account that you are currently working in, on the menu bar, click your profile avatar.

If you can't log in to your IBM Cloud account, contact your corporation, and work with them to delete your personal data.

If you want to delete all of your personal data from Continuous Delivery, the order in which you delete that data is important.
When you choose Data Service, your existing IBM Cloud data services appear in the Service Instance list.
6. Click Create. The connection is available to all legacy projects.
7. On the Connections pane, select the connection and click Apply.



To add an existing connection to a legacy project:



1. From your project's Assets page, click the Find and add data icon.
2. On the Connections pane, select the connection and click Apply.









 SPSS Statistics 

These instructions explain how to create a connection from IBM® SPSS® Statistics to a Db2 Warehouse on Cloud database.



 Prerequisites 

Before attempting to connect to your Db2 Warehouse on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-connect_ovprereqs).





 Procedure 



1. In SPSS Statistics, click File > Open Database > New Query.
2. In the Database Wizard, click Add ODBC data source.
3. Use the ODBC Data Source Administrator window to add an ODBC data source name (DSN) for the Db2 Warehouse on Cloud database:

a. On the User DSN tab, click Add.

b. On the Create New Data Source window, select the driver that is named IBM DB2 ODBC DRIVER and click Finish.

Be sure that the driver that you select is not a driver with a similar name such as IBM DB2® ODBC DRIVER - DB2COPY. If the driver does not appear in the list, exit SPSS Statistics, then download and install the driver. See [Driver package](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-dr_pkgdr_pkg).

c. In the ODBC IBM Driver - Add window, enter a data source name (usually the name of the database you are connecting to), and click Add.

d.
service dragent restart







 Step 2: Launch the monitoring UI to verify that you are getting data to monitor the bare metal server 

Complete the following steps to launch the web UI:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in with your user ID and password, the IBM Cloud console opens.
2. Click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/icon_hamburger.svg) > Observability.
3. Select Monitoring.

The list of instances that are available on IBM Cloud is displayed.
4. Select your instance. Then, click Open dashboard.



It may take some time before you see the bare metal entry while the information is initally collected and processed by the monitoring agent.

You only can monitor one instance per browser. You could have multiple tabs for the same instance.





 Step 3: Monitor your bare metal 

In the Advisor tab, you can monitor and troubleshoot the health, risk, and capacity of hosts and Kubernetes clusters.

Zoom

![Advisor tab](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/advisor-tab.png)

Advisor tab



* Data is refreshed every 10 minutes.
* Metrics are prioritized by event count and severity.
* For more information, see [Advisor](https://docs.sysdig.com/en/docs/sysdig-monitor/advisor/).



In the Advisor section, choose to monitor by host. Check out the predefined dashboards that you can use to monitor the health of your resources.

When you choose to monitor by host, you can choose any of the following dashboards:



* Host Resource Usage
* If you're storing time-series data, encoding time at the start of your _id sorts the primary index by time, for example, 001j40Ox1b2c1B2ubbtm4CsuLB4L35wQ.
* Partitioned databases group documents that share a partition key together. A partition key must have many values and must not include hot spots to avoid directing a large proportion of your application's traffic to a few partitions.



For more information, see the following blog posts:



* [Time-sortable _ids](https://blog.cloudant.com/2018/08/24/Time-sortable-document-ids.html)
* [Introduction to partitioned databases](https://blog.cloudant.com/2019/03/05/Partition-Databases-Introduction.html)







 Querying and secondary indexes 

IBM Cloudant allows queries to run against a single database that returns an array of matching documents and a bookmark, which allows access to the next block of search results. Achieving better query performance depends on having your queries that are supported by suitable secondary indexes. An index allows the database to answer a query without having to trawl through every document in the database, yielding much faster performance.

See the following tips:



* It's sometimes difficult to measure the performance of your queries until your data set is large enough to expose slow operations. Generate enough realistic data so that you can test your indexing and query performance before you get to production.
* IBM Cloudant might return data to you without an index, but you must never rely on this data for production workloads. If your result set includes the warning, No matching index found. Create an index to optimize query time, then you need to revisit your indexing strategy. Use the [explain](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-queryexplain-plans) feature to see which index is being selected for each query.
* With several object types in the same database, many use cases can be serviced by a few indexes on fixed attributes.
Merging and querying data 

You might keep only the most recent data locally in a database and use data lakes as your long term storage. With Netezza Performance Server, you can seamlessly query both local and remote data without having to load the remote data into a database first.



 Before you begin 

In the examples, the publicly available [New York taxi trip record data](https://www1.nyc.gov/site/tlc/about/tlc-trip-record-data.page) for yellow taxis in January 2021 and 2022 is used. To follow this example, make sure that the data is in an accessible S3 bucket.





 1. Create an external data source. 

External datasources allow an administrator to grant access to S3 without providing the keys directly to a user.

a) Set ENABLE_EXTERNAL_DATASOURCE.

set ENABLE_EXTERNAL_DATASOURCE = 1;

b) Create an external data source.

create EXTERNAL DATASOURCE 'DATA SOURCE' on 'REMOTE SOURCE'
using (
ACCESSKEYID 'ACCESS KEY ID' SECRETACCESSKEY 'SECRET ACCESS KEY' BUCKET 'BUCKET' REGION 'REGION'
);

Example:

create EXTERNAL DATASOURCE EXAMPLEDATALAKE on AWSS3 
using (
ACCESSKEYID 'XXXX' SECRETACCESSKEY 'XXXX' BUCKET 'exampledatalakebucket' REGION 'US-EAST-1'
);

For more information, see [CREATE EXTERNAL DATASOURCE command](https://www.ibm.com/docs/en/netezza?topic=tables-create-external-datasource-command).





 2. Identify the data from Netezza Performance Server to merge and compare. 

In this example, data that was loaded into Netezza Performance Server (YELLOW_TAXI_JANUARY_2022) is compared with data from a data like (YELLOW_TAXI_JANUARY_2021).

To follow this example, ensure that YELLOW_TAXI_JANUARY_2022 is in your Netezza Performance Server database.

a) Create an external table for the data that you want to load (YELLOW_TAXI_JANUARY_2022).
If you can create multiple gateways, are there any considerations for reusing a Node.js application to create a gateway and destination in each space?

The approach is as follows:



* You can create a single Secure Gateway instance for all three spaces. However, you must remember the gateway and destination [limitations for your specific plan](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-secure-gateway-service-plans).
* There are no additional considerations for reusing a Node.js application as no service bindings are required by Secure Gateway.







 What is the recommended approach to creation automation across multiple orgs? 

Consider an environment that has three orgs: one for development, one for staging, and one for production. Is a Secure Gateway service instance required for each org and is the configuration available to all spaces within that org?

For automation across orgs, the approach is as follows:



* You are not required to have a Secure Gateway service instance in each org. You could have an instance in one org and use the gateways within that instance from all of your other environments. With this setup, you must remember the gateway and destination [limitations for your specific plan](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-secure-gateway-service-plans).
* You can have a Secure Gateway service instance in each org and the configuration will be available to all your spaces.







 Does my app need to be in the same space? 

Do I need to run the Node.js app in the same IBM Cloud space as the Secure Gateway service? No, you do not need to run your app in the same IBM Cloud space as the Secure Gateway service.





 Can a Secure Gateway client handle two gateways on the same machine? 

Yes. For a client to handle two gateways, you can specify multiple connections through the command line as shown in this excerpt from [Startup Argument Examples](https://cloud.ibm.com/docs/SecureGateway?topic=SecureGateway-client-interactingstartup-examples):
Note that you cannot delete a job run without also deleting any associated pods. Any attempt to delete with the propagationPolicy=Orphan option is rejected.





 Serving CRD methods 



Serving CRDs for Code Engine

 Group Version Kind 

 serving.knative.dev v1 Configuration 
 serving.knative.dev v1 Revision 
 serving.knative.dev v1 Route 
 serving.knative.dev v1 Service 



For more information about these CRDs, see [Knative Serving API Specification](https://github.com/knative/specs/blob/main/specs/serving/knative-api-specification-1.0.md).





 Source-to-image CRD methods 



Source-to-image CRDs for Code Engine

 Group Version Kind 

 shipwright.io v1alpha1 Build 
 shipwright.io v1alpha1 BuildRun 



After you retrieve the Kubernetes configuration, you can view the Source-to-image CRD details by using one of the following methods.



* Use kubectl explain --api-version='shipwright.io/v1alpha1' <KIND>.
* [Download the Swagger or OpenAPI specification of CRDs](https://kubernetes.io/docs/concepts/overview/kubernetes-api/).







 Subscription CRD methods 



Subscription CRDs for Code Engine

 Group Version Kind 

 sources.codeengine.cloud.ibm.com v1alpha1 CosSource 
 sources.knative.dev v1 PingSource 



After you retrieve the Kubernetes configuration, you can view the Subscription CRD details by using one of the following methods.



* Use kubectl explain --api-version='sources.knative.dev/<VERSION>' <KIND>.
* [Download the Swagger or OpenAPI specification of CRDs](https://kubernetes.io/docs/concepts/overview/kubernetes-api/).