vania-janet/multiturn-rag-retrieval-data huggingface dataset:
FAQs 

Frequently asked questions about IBM Cloud® Data Transfer Service.



 What is Data Transfer Service? 

This service allows authorized users (generally the account's administrator) to send compatible devices to one of the IBM Cloud® data centers to be connected directly to the account's network. The device is housed in a dedicated rack and is mounted as an iSCSI target for two weeks. During that period, the administrator can access the device on the network to use it with other devices and services on the account. After the two-week period, an extension can be requested to keep the device connected to the network. Otherwise, the device is either returned to the party specified in the request, or the device is destroyed onsite.





 Can a device for data transfer be sent internationally? 

Hardware can be sent both domestically and internationally to any of the IBM Cloud® data centers. However, you as the Client are responsible for the meeting the following requirements.



* Ensuring that no import or export license is required to ship the Device to the IBM® data center, or to return it to Client (if applicable).
* Ensuring that Client or any Client user whose data is included in the Content is not subject to any US Government order that revokes or denies their US export privileges. You must notify IBM® immediately if your enterprise or any such user becomes subject to any such order.
* Obtaining all licensing, shipping, and customs clearance for the Device, including paying any duties, taxes, and shipping costs to and from (if applicable) the IBM® data center.
* Complying with all applicable laws, including privacy, import and export, which are associated with delivery and return of the Device, and the transfer of Content to the IBM® data center.
* Having proper agreements in place, and obtaining all required permissions, with Client’s user for any user data Client transfers to the hardware.



Include a pre-paid return-shipping label and all appropriate export documents with your shipment. IBM Cloud® packages the device for return by using the label and documents that you provided. If return isn't requested, the device is destroyed.





 What types of devices can be sent with a data transfer request? 

Use the following Hardware Requirements guidelines when you select a device to submit for data transfer.
* At the end of the rule, the year 2009 is already annotated as being a mention of the RegExpYear class. The RegExpYear class is part of the rule pattern instead of the number 2009. This selection is also preferred because you want the model to find any year that is annotated by the RegExpYear class as the last token in the date pattern instead of the specific text 2009 only.



The number 3 and the comma (,) after it are shown as the second and third tokens in the pattern. As the pattern is currently specified, the model will find only occurrences of dates that specify the 3rd day of a month. We want the model to find dates that specify any day of the month, so next we will change the feature settings for the day token.
4. Above the day 3 cell, click the Text icon to open the feature settings for the token.

![Shows the user clicking the Text Feature Settings icon.](https://cloud.ibm.com/docs-content/v1/content/148d3bd95f946aa1bb53ea1540475f522e6b61c9/watson-knowledge-studio-data/images/rule-add4.png)

Currently, the rule is set to match the exact text, 3. Instead, we want it to match any number.
5. Change the feature setting to be numeric by selecting Character Type : Numeric, and then clearing the selection, Text : 3.

![Shows the user clicking the "Character Type : Number" option as the feature setting for the "3" token.](images/rule-add5.png "Shows the user clicking the "Character Type : Number" option as the feature setting for the "3" token.")

You changed the definition for the number 3 cell.

![Shows the cell that represents the "3" token now has a "Character Type" icon above it to indicate that any numeric value can match that token in the pattern.]
You need access only to the private repo to clone the content during the toolchain creation. The personal access token can be created with an expiry date to limit its lifetime to expire after one day.

After you have a personal access token, you can create a URL to access the repo from other regions. While you are configuring the tool integration, in the Source repository URL field, update the repo URL to use your user name and access token.

https://user:XXXXXXX@us-south.git.cloud.ibm.com/group/node-hello-world

Where user is your GitLab user name, XXXXXXX is the access token, [group](https://us-south.git.cloud.ibm.com/help/user/group/index.md) is the group where the repo is stored, and node-hello-world is the repo name.

If your GitLab repo isn't located within a GitLab group, the value of group is the same as your user name.





 I configured a tool integration for my toolchain, why wasn't it configured? 

If an error occurs during the setup process or if the communication between the toolchain and the tool does not complete properly, the configuration fails.

 What’s happening 

After you add and configure a tool integration for your toolchain, an error message is displayed to indicate that the setup failed.

 Why it’s happening 

When you add a tool integration, the toolchain communicates with the tool that is represented by the tool integration to provision any necessary resources and associate them with the toolchain. If an error occurs during the setup process or if the communication between the toolchain and the tool does not complete properly, the tool integration is put into an error state.

 How to fix it 

You can try to configure the tool integration again:



1. On its tool card, hover over the Setup failed message and click Reconfigure.

Zoom

!
Why does the Ingress status show an ERRDSISS error? 

Virtual Private Cloud

Classic infrastructure

Satellite

You can use the the ibmcloud ks ingress status-report ignored-errors add command to add an error to the ignored-errors list. Ignored errors still appear in the output of the ibmcloud ks ingress status-report get command, but are ignored when calculating the overall Ingress Status.

  What’s happening 

When you check the status of your cluster's Ingress components by running the ibmcloud ks ingress status-report get command, you see an error similar to the following example.

The subdomain has TLS secret issues (ERRDSISS).

  Why it’s happening 

IBM Cloud Kubernetes Service generates a TLS certificate for managed domains and creates a TLS secret on the cluster containing the certificate. Normally, the certificate status should be created or deleted, but the status indicates problems with the certificate or secret generation.

  How to fix it 

Check the SSL Cert Status of your managed domains and, if needed, regenerate them.



1.  Get the list of the managed domains using the ibmcloud ks nlb-dns ls[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_nlb-dns-ls).
2.  Check the SSL Cert Status column.

creating or regenerating status.
:   Wait a few hours and check the status again. If the status does not change, ensure that the namespace appearing in the Secret Namespace exists.

rate_limited status.
:   Let's Encrypt refused to generate a new certificate for this domain. This usually happens when the cluster is deleted and recreated with the same name, or the ibmcloud ks nlb-dns secret regenerate command was invoked multiple times. The rate limit will expire after 7 days (there is no way to manually remove it). Certificate generation will be automatically attempted again after 7 days.
3.  Wait 10-15 minutes, then check if the warning is resolved.
4.  If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the case details, be sure to include any relevant log files, error messages, or command outputs.
You cannot stream from the second Activity Tracker instance to another Activity Tracker instance.

Currently, you can only stream up to 1TB of data per day.

If you have any regulatory requirement for data residency and compliance needs, you must control the location where Activity Tracker, Event Streams, Kafka Connect and the destination tool are available.



 Configure streaming 

Consider the following information when streaming data to an Event Streams instance:



* You must have manager role to configure streaming in the Activity Tracker instance. This role includes the logdnaat.dashboard.manage IAM action role that allows a user to perform admin tasks such as configure streaming.
* When you configure streaming, the Activity Tracker instance and the Event Streams instance must be provisioned in the same account.
* To connect the Activity Tracker instance to the Event Streams instance, you need the following information:



* Endpoint URLs to call the APIs
* Credentials for authentication



* If you configure the account to restrict access to configured IP addresses via IAM settings, or if the account limits the network locations that connections are accepted from via context based restrictions rules (CBR) for the Event Streams service, you must allowlist the Activity Tracker CIDR blocks in the account. For more information, see [Activity Tracker CIDR blocks](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-cidr) and [Event Streams - Restricting network access](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-restrict_access).
* To create a topic in Event Streams, you must have manager role. This role includes the messagehub.topic.manage IAM action role that allows an app or user to create or delete topic.
* The credential that Activity Tracker uses to publish data in Event Streams must have writer role. This role includes the messagehub.topic.write IAM action role that allows an app or service to write data to 1 or more topics.



Consider the following information when streaming data to an Activity Tracker instance:



* The Activity Tracker instance data that will receive data must be configured with a paid service plan.
Why does the Ingress status show an ERRDSISS error? 

Virtual Private Cloud

Classic infrastructure

Satellite

You can use the the ibmcloud oc ingress status-report ignored-errors add command to add an error to the ignored-errors list. Ignored errors still appear in the output of the ibmcloud oc ingress status-report get command, but are ignored when calculating the overall Ingress Status.

 What’s happening 

When you check the status of your cluster's Ingress components by running the ibmcloud oc ingress status-report get command, you see an error similar to the following example.

The subdomain has TLS secret issues (ERRDSISS).

 Why it’s happening 

Red Hat OpenShift on IBM Cloud generates a TLS certificate for managed domains and creates a TLS secret on the cluster containing the certificate. Normally, the certificate status should be created or deleted, but the status indicates problems with the certificate or secret generation.

 How to fix it 

Check the SSL Cert Status of your managed domains and, if needed, regenerate them.



1. Get the list of the managed domains using the ibmcloud oc nlb-dns ls[command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_nlb-dns-ls).
2. Check the SSL Cert Status column.

creating or regenerating status.
: Wait a few hours and check the status again. If the status does not change, ensure that the namespace appearing in the Secret Namespace exists.

rate_limited status.
: Let's Encrypt refused to generate a new certificate for this domain. This usually happens when the cluster is deleted and recreated with the same name, or the ibmcloud oc nlb-dns secret regenerate command was invoked multiple times. The rate limit will expire after 7 days (there is no way to manually remove it). Certificate generation will be automatically attempted again after 7 days.
3. Wait 10-15 minutes, then check if the warning is resolved.
4.
Why does my instance shut down or not start after provisioning? 

  What’s happening 

Your IBM Cloud® Hyper Protect Virtual Servers for VPC instance shuts down or doesn't start after provisioning.

  Why it’s happening 

Causes vary.

  How to fix it 

Check whether you have performed the following actions correctly.



*  Attach data volume within 15 min

If you have a volumes section in the contract, the IBM Cloud Hyper Protect Virtual Servers for VPC instance assumes that a data volume will be attached. The cloud user must either attach the volume during the instance creation, or within 15 minutes after instance creation starts. After this 15-minute wait period, the instance shuts down.
*  Contract is mandatory

If you create a Hyper Protect Virtual Servers for VPC instance without any contract that's passed in through the "User Data" section, the instance starts running, and then shuts down eventually.
*  Contract format is yaml

The contract must follow the YAML format. If the format is not proper, it fails the contract validation check, and the instance shuts down eventually.
*  Contract schema

If the contract schema is incorrect, the contract validation fails when the instance is booting and the instance shuts down. You can check for errors that are associated with hpcr-contract log identifier in your IBM Log Analysis instance.
*  Image or Profile mismatch

Hyper Protect Virtual Servers for VPC instances can be created from the UI, CLI, and any other interface that IBM Cloud® Virtual Private Cloud (VPC) supports. You must select the right image and profile combination. Without the right combination of the image and profile, the instance fails to start.
*  Logging configuration failure

When the instance boots, monitor the serial console to identify any errors that are logged by the bootloader or from the logging service. If you don't see any logs in your private IBM Log Analysis instance, it might be because your logging configuration failed. Failure to configure logging also leads to the instance shutting down. If your logging configuration fails, check whether the logging hostname, port, and ingestion key that are provided in the contract are correct.
* headers: Array of response headers to match. If a response does not meet the header criteria then the request is not counted towards the rate limiting rule. An array of header matching criteria includes following properties.

<-- <ul> -->

* name: The name of the response header to match.
* op: The operator when matching, eq means equals, ne means not equals. Valid values are eq and ne.
* value: The value of the header, which is exactly matched.

<-- </ul> -->

<-- </ul> -->

<-- </ul> -->

* threshold: The threshold that triggers the rate limit mitigations, combined with period. For example, threshold per period. Min value: 2, max value: 1000000.
* period: The time, in seconds, to count matching traffic. If the count exceeds threshold within this period the action is performed. Min value: 1, max value: 3600.
* action: The action performed when the threshold of matched traffic within the period defined is exceeded.

<-- <ul> -->

* mode: The type of action performed. Valid values are: simulate, ban, challenge, js_challenge.
* timeout: The time, in seconds, as an integer to perform the mitigation action. Timeout be the same or greater than the period. This field is valid only when mode is simulate or ban. Min value: 10, max value: 86400.
* response: Custom content-type and body to return. This overrides the custom error for the zone. This field is not required. Omission results in the default HTML error page. This field is valid only when mode is simulate or ban.

<-- <ul> -->

* content_type: The content-type of the body, which must be one of the following: text/plain, text/xml, application/json.
* body: The body to return. The content here must conform to the content_type. Max length is 10240.
@sys-date.festival Checks whether the customer is asking about hours on another specific holiday. We are closed on Christmas Day, July 4th, and President's Day. On other holidays, we are open from 10AM to 5PM. 
 @sys-time.part_of_day == 'night' Checks whether the user includes any terms that mention night as the time of day in the input. We are not open late; we close at 9PM most days. 
 @sys-date.datetime_link && input.text.contains('today') && now().sameOrAfter(@sys-time) Checks whether the input contains a phrase such as today at 8. It also checks whether the @sys-time that is detected is earlier than the current time of day. You can add a context variable to the conditional response that creates a $new_time variable with the value <? @sys-time.plusHours(12) ?>. You can use this approach to create a date variable that captures the more likely time meant by a user who, at noontime asks, Are you open today at 8. The system assumes the user means 8AM instead of 8PM. You mean today at $new_time, correct? 
 @sys-time.range_link && entities[0].role?.type == 'time_from' && entities[1].role?.type == 'time_to' Checks whether the input contains a time range. The condition also makes sure that the first @sys-time system entity listed in the entities array is the start time and that the second one is the end time before including them in the response. You want to know if we're open between <? entities[0] ?> and <? entities[1] ?>, is that correct? 
 @sys-time && entities.size() < 2 && entities[0].role?.type == 'time_to' Checks whether the input contains one @sys-time mention that has a time_to role type. If the user input matches this condition, it suggests that the user specified the end time of an open-ended time range.
> SELECT day('2009-07-30')
: Result value

30





 dayofmonth 

dayofmonth(date)
: Returns the day of month of the date/timestamp.
: Example of an SQL function usage fragment

> SELECT dayofmonth('2009-07-30')
: Result value

30





 dayofweek 

dayofweek(date)
: Returns the day of the week for date/timestamp (1 = Sunday, 2 = Monday, ..., 7 = Saturday).
: Example of an SQL function usage fragment

> SELECT dayofweek('2009-07-30')
: Result value

5





 dayofyear 

dayofyear(date)
: Returns the day of year of the date/timestamp.
: Example of an SQL function usage fragment

> SELECT dayofyear('2016-04-09')
: Result value

100





 decimal 

decimal(expr)
: Casts the value expr to the target data type DECIMAL(10,0), truncating the result if needed. Use CAST(expr AS DECIMAL(p,f)) to specify precision and fractional digits explicitly.





 decode 

decode(bin, charset)
: Decodes the first argument by using the second argument character set.
: Example of an SQL function usage fragment

> SELECT decode(encode('abc', 'utf-8'), 'utf-8')
: Result value

abc





 degrees 

degrees(expr)
: Converts radians to degrees.
: Example of an SQL function usage fragment

> SELECT degrees(3.141592653589793)
: Result value

180.0





 dense_rank 

dense_rank()
: Computes the rank of a value in a group of values. The result is one plus the previously assigned rank value. Unlike the function rank, dense_rank does not produce gaps in the ranking sequence.





 double 

double(expr)
The following table shows equivalent interval clauses.



Table 31. Equivalent INTERVAL clauses.

 INTERVAL expression INTERVAL TO expression 

 INTERVAL 1 DAY - INTERVAL 2 HOURS - INTERVAL 3 MINUTES - INTERVAL 4 SECONDS INTERVAL '1 2:3:4.100' DAY TO SECOND 
 INTERVAL 1 YEAR - INTERVAL 2 MONTH INTERVAL '1-2' YEAR TO MONTH 



The following example demonstrates equivalent interval expressions when you deal with YEAR and MONTH time units.

-- equivalent interval expressions with YEAR and MONTH time units
WITH ts AS (
SELECT CURRENT_TIMESTAMP AS now FROM VALUES ('dummy')
)
SELECT
now - INTERVAL 1 YEAR - INTERVAL 2 MONTH AS LONG_VERSION,
now - INTERVAL '1-2' YEAR TO MONTH AS SHORT_VERSION
FROM ts

The result of the example query is shown in the following table.



Table 32. Query result for example: equivalent interval expressions with YEAR and MONTH time units.

 LONG_VERSION SHORT_VERSION 

 2017-08-16 10:38:07.304 2017-08-16 10:38:07.304 



The following example demonstrates equivalent interval expressions, when you deal with DAY, HOUR, MINUTE, and SECOND time units.

-- equivalent interval expressions when you deal with DAY, HOUR, MINUTE, and SECOND time units
WITH ts AS (
SELECT CURRENT_TIMESTAMP AS now FROM VALUES ('dummy')
)
SELECT
now - INTERVAL 1 DAY - INTERVAL 2 HOURS - INTERVAL 3 MINUTES - INTERVAL 4 SECONDS AS LONG_VERSION,
now - INTERVAL '1 2:3:4.100' DAY TO SECOND AS SHORT_VERSION
FROM ts

The result of the example query is shown in the following table.



Table 33. Query result for example: equivalent interval expressions when you deal with DAY, HOUR, MINUTE and SECOND time units.

 LONG_VERSION SHORT_VERSION 

 2018-10-15 08:33:00.84 2018-10-15 08:33:00.84 







 columnReference 





 qualifiedName 

A qualified name is a sequence of identifiers that are separated by .. For example, a column name can be qualified by the name of the relation the column is defined in.

Qualified names are available in the following context:
* How long does it take for DNS changes to propagate?

DNS change propagation times depend on the time-to-live (TTL) setting for the DNS record. The default TTL is one day, which means any modifications to a domain name take one day to propagate throughout the entire internet. TTL can be lowered if you plan to make changes frequently; however, the lower the TTL is, the higher the load becomes on the name server. Higher loads have a potential to increase the response time to end users, which could impact their overall satisfaction.

The higher the TTL setting, the higher DNS performance is due to local ISP caching. The lower the TTL setting, the lower DNS performance is due to increased name resolution.

To verify TTL, check the Start of Authority (SOA) record for the domain. A great tool for reviewing domain information is offered by [CentralOps.net](http://centralops.net/co/)

TTL is listed in seconds. Divide by 60 to convert TTL to minutes, or by 3600 to convert to hours.
* After transferring a domain, how long does it take for the domain and the changes made to become visible?

Your domain and/or changes to it are visible on IBM Cloud DNS servers immediately after the transfer completes. Due to the propagation nature of DNS, there will be a delay before changes are visible on other DNS servers.
* Can I complete AXFR requests on the private network?

Currently, IBM Cloud does not support AXFR request on the private network. All AXFR requests must be completed on the public network.
* How can I run my own name servers?

The easiest way to run and manage your own name servers is to use a control panel tool such as Plesk or cPanel. Both of these products have built in domain name servers that allow you to add, modify, or delete domain names.

To begin, register your domain name as a name server with your domain name registrar and assign two IP addresses from your server IP ranges.
* Are zone update notifies supported for secondary DNS zones?

Zone update notifies are not supported at this time.