vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Alter your table as described in [Updating retention time interval for schemas](https://cloud.ibm.com/docs/netezza?topic=netezza-create-schemasupdating_rt_sch).







 Altering temporal databases to nontemporal with the web console 

To alter a temporal database to nontemporal, set retention time interval to 0.



1. Log in to the web console as described in [Getting started with the web console](https://cloud.ibm.com/docs/netezza?topic=netezza-getstarted-console).
2. Alter your table as described in [Updating retention time interval for databases](https://cloud.ibm.com/docs/netezza?topic=netezza-databasesupdating_retention_db).







 Altering nontemporal databases to temporal with the web console 

To alter a nontemporal database to temporal, set retention time interval to a nonzero value.



1. Log in to the web console as described in [Getting started with the web console](https://cloud.ibm.com/docs/netezza?topic=netezza-getstarted-console).
2. Alter your table as described in [Updating retention time interval for databases](https://cloud.ibm.com/docs/netezza?topic=netezza-databasesupdating_retention_db).









 What to do next 

After you created time travel objects, you can start running time travel queries. For more information, see the following links:



* [Running queries syntax](https://cloud.ibm.com/docs/netezza?topic=netezza-runningqueries_tt)
* [Querying historical data](https://cloud.ibm.com/docs/netezza?topic=netezza-queryingdata_tt)
To alter a temporal database to nontemporal, set DATA_VERSION_RETENTION_TIME to 0.

For detailed syntax and the necessary privileges, see [the ALTER DATABASE command](https://www.ibm.com/docs/en/netezza?topic=npsscr-alter-database-2).

ALTER DATABASE <db_name> DATA_VERSION_RETENTION_TIME 0 NOCASCADE;

Example:

ALTER DATABASE DB1 DATA_VERSION_RETENTION_TIME 0 NOCASCADE;





 Altering nontemporal databases to temporal with the command-line 

To alter a nontemporal database to temporal, set DATA_VERSION_RETENTION_TIME to a nonzero value.

For detailed syntax and the necessary privileges, see [the ALTER DATABASE command](https://www.ibm.com/docs/en/netezza?topic=npsscr-alter-database-2).

ALTER DATABASE <db_name> DATA_VERSION_RETENTION_TIME <number-of-days> NOCASCADE;

Example:

ALTER DATABASE DB1 DATA_VERSION_RETENTION_TIME 30 NOCASCADE;







 Altering time travel objects with the web console 



 Altering temporal tables to nontemporal with the web console 

To alter a temporal table to nontemporal, set retention time interval to 0.



1. Log in to the web console as described in [Getting started with the web console](https://cloud.ibm.com/docs/netezza?topic=netezza-getstarted-console).
2. Alter your table as described in [Updating retention time interval for tables](https://cloud.ibm.com/docs/netezza?topic=netezza-create-tablesupdating_retention_db).



When you set retention time interval to 0, you cannot run time travel queries and you do not have access to historical rows for that table anymore. You can reclaim some or all of the now inaccessible historical rows in the table with GROOM TABLE.





 Altering nontemporal tables to temporal with the web console 

To alter a nontemporal table to temporal, set retention time interval to a nonzero value.



1.
12. Click Create Job. The job is now created, and the View/Add Schedule dialog box appears. Next, you can create a schedule for running the backup. Click Cancel if you don't want to create a schedule now.







 Scheduling the SQL backup job 

After you created a backup job, you can add one or more schedules for running the job automatically. You can create complex schedules for a job by creating multiple schedules. For example, you can schedule a backup job to run at midnight every Friday, and schedule the job to run at 8 PM on the first day of every month. When you schedule multiple SQL Server database jobs in the same instance, it's good practice to schedule the jobs so that their running times do not overlap. Simultaneous backups are supported, but are not recommended.

If a job is scheduled to start at the same time by multiple schedules, the job runs only once at the scheduled time. If the jobs have different retention types, the retention type of the schedule that is highest in the list is applied to the resulting safe set. For example, the job is scheduled to run at midnight each Saturday with the Weekly retention type, and every day at 12 midnight with the Daily retention type. On Saturdays, the job runs once at 12 midnight. Because the schedule with the Weekly retention type is higher in the list than the schedule with the Daily retention type, the Weekly retention type is applied to the safe set.

If a job is scheduled to run at slightly different times, the IBM Cloud Backup for Classic Agent attempts to run the job according to each schedule. For example, if a job is scheduled to run at 11 PM by one schedule and 11:01 PM by another schedule, the IBM Cloud Backup for Classic agent attempts to run the job twice. Try to avoid overlapping schedules. Problems can occur if a job is scheduled to run twice in a short period. In particular, try to avoid overlapping schedules for SQL Server database jobs in the same instance. Simultaneous backups in the same SQL Server instance are supported, but are not recommended.



1. In the View/Add Schedule dialog box, click Add Schedule.
2. In the new schedule row, in the Retention list, click a retention type.
3. Select the Backup Type:
Now you can see the history of all action variables, rather than one action at a time. For more information, see [Variable values](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-reviewreview-variable-values).





 21 October 2022 

Algorithm version updates
: The algorithm version setting for both actions and dialog now includes three choices: beta, latest, and previous. For more information, see [Algorithm version and training](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-algorithm-version).





 12 October 2022 

now(String timezone) method output includes time zone offset
: The string returned from the now(String timezone) method now includes the time zone offset (such as -05:00). The new format is yyyy-MM-dd HH:mm:ss 'GMT'XXX (where XXX represents the time zone offset). This change enables accurate time zone computations when used with other date and time methods such as before, after, and reformatDateTime.

If you have an existing action or dialog that depends on the previous format, you can adapt it by reformatting the output using now(timezone).reformatDateTime('yyyy-MM-dd HH:mm:ss').

For more information, see [Expression language methods for actions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-expression-methods-actionsexpression-methods-actions-now).





 23 September 2022 

Upload an image as a preview background
: On the Preview page, you can now upload an image of your organization's website as a background. For more information, see [Previewing and sharing your assistant](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-preview-share).





 16 September 2022 

Session ID information on Analyze page
: Session ID information for conversations is now displayed on the Conversations tab of the Analyze page. You can also filter customer conversation data by the session ID.
For example, CURRENT_DATE, CURRENT_TIMESTAMP or (equivalently) NOW(), or CURRENT_TIMESTAMP(subsecond-digits) or (equivalently) NOW(subsecond-digits).
* An expression that evaluates to a single timestamp for all rows in the table. For example, CURRENT_TIMESTAMP - INTERVAL ‘1 day’. The expression cannot refer to table columns or to a non-deterministic function (for example, RANDOM()) or be a sub-SELECT.
* The special identifier RETENTION_START_TIMESTAMP, in the particular cases of AS OF, BETWEEN, and FROM (but not BEFORE, AND, or TO). This refers to the retention start timestamp, which is the oldest possible row insert timestamp or delete timestamp that is available for time travel queries. For more information about retention start timestamps, insert timestamps, and delete timestamps, see [Timestamps in time travel queries](https://cloud.ibm.com/docs/netezza?topic=netezza-runningqueries_ttconcepts_tt).





 AS OF 

You can use the AS OF subclause when you want to retrieve the state of your data as it was at any specific time in the past.



 Syntax Description 

 AS OF <TIMESTAMP EXPRESSION 1> Includes all the rows that were valid at the timestamp that TIMESTAMP EXPRESSION 1 evaluates to, whose insert timestamp is less than or equal to TIMESTAMP EXPRESSION 1, and whose delete timestamp is NULL or is greater than TIMESTAMP EXPRESSION 1. If TIMESTAMP EXPRESSION 1 is less than the table’s retention start timestamp, an error is returned. 







 BEFORE 

You can use the BEFORE subclause when you want to to retrieve the state of your data as it was just before any specific time in the past.



 Syntax Description 

 BEFORE <TIMESTAMP EXPRESSION 1> Includes all the rows that were valid just before the timestamp that TIMESTAMP EXPRESSION 1 evaluates to.
In a time travel query, you can select the insert timestamp by using the _SYS_START virtual column of a temporal table.

The delete timestamp of a historical row is the date/time that the transaction deleting the row committed. It is not the time when a particular DELETE, UPDATE, MERGE, or TRUNCATE statement that deleted the row was run.

If a temporal table is truncated, the existing table rows are available to time travel queries and are treated as having been deleted as of the time the truncating transaction committed.

If the deleting (or truncating) transaction committed before the retention start timestamp, a deleted row is treated as having been deleted at the retention start timestamp. This generally applies only to existing deleted rows at the time of altering a nontemporal table to a temporal table; such rows are not visible to time travel queries against the table.

A historical row might be visible to a temporal query against the table if its delete timestamp falls within the table’s retention period. If this condition is true, the historical row cannot be removed (with GROOM TABLE) from the table.

The delete timestamp of a current row (not deleted, or marked for deletion but not committed) is NULL.

In a time travel query, you can select the delete timestamp by using the _SYS_END virtual column of a temporal table.

A historical row is considered valid from its insert timestamp up to just before the delete timestamp. A current row is considered valid from its insert timestamp forward. Time travel queries use timestamps or timestamp expressions to only return rows (current or historical) that are valid at a point in time or at any point within a time period.

The insert and delete timestamps for recently inserted and deleted rows might not be available for time travel queries until a short time (generally under 3 minutes) after the inserting and deleting transactions commit.
Setting up a schedule 

After the backup job is created, you can add one or more schedules for running the job automatically.



1. When you click Create Job, the Schedule window appears and gives you an option to create a custom schedule for the backup job.

By default Daily retention is selected for the job. Retention and Job schedule can be changed in this window, and multiple Retention schemes can also be assigned to the backup job.
2. Click Save to save the new schedule. The new job shows up under the Computers tab in Jobs section. The Last backup status shows that the job never ran. The scheduled backup job runs automatically at the scheduled time.







 Running a scheduled job 

Scheduled backup jobs can also be run immediately.



1. Click Select Action, and select Run Job. A new window appears and you can see information about the Destination Vault and Retention schemes that are assigned to the job.

If multiple vaults and retention schemes are assigned to the job, these options can be changed in this window by clicking the Destination and Retention Scheme menu options.
2. Click start Backup job to issue the backup job immediately. In the progress window, you can see the status of backup job and when the job is finished the job status changes from "Never Run" to "Completed".



To see the status of the last backup job that ran, click the Jobs tab. All job logs can be accessed from the action menu. Click Action and select History/Logs.

For more information about restoring VMs or Files and folders, see [Restoring vSphere data](https://cloud.ibm.com/docs/Backup?topic=Backup-VRARestoreVRARestore).
* For a Daily plan, enter the starting time (UTC) in hours and minutes, Coordinated Universal Time. For example, 12 noon is 12:00. Local time conversion is automatically provided on the screen, for example, 12 PM Central Daylight Time.



* Weekly



* For a Weekly plan, select the days of the week that you want backups to run. For example, you can select Monday, Wednesday, and Friday. Specify the starting time in the same manner as a Daily plan.



* Monthly



* For a Monthly plan, select the day of the month that you want backups to run. For example, "1" schedules a backup every first of the month. Specify the starting time in the same manner as a Daily plan.



* Specify by using cron expression



* Under Cron expression (UTC), enter the backup creation frequency in cron-spec format: minute, hour, day, month, and weekday. For example, to create a backup every day at 5:30 PM, you need to enter 30 17 * * .





The Backup destination shows the Block Storage for VPC volume's region. The Backup resource group is the resource group that is associated with the volume.
3. Specify a Retention type for the backups. You can specify either how long to keep them by number of days or the total number to retain.



* For Age, specify the number of days that you want to retain the backups. A default value for the maximum number of days to keep a backup is not provided.
* For Count, provide the number of backups that you want to keep.



To keep costs down, set a retention period or snapshots count adequate to your needs. For example, setting "7" for Age retains a week's worth of backups.
4. Under Optional, you can configure two options.



* Fast snapshot restore - When you enable this feature, you must specify the zone or zones where you want [fast restore](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-aboutsnapshots_vpc_fast_restore) enabled.
10. Enter the encryption password into the Password and Confirm Password fields. You can also add a Password Hint.

You need this password to restore files from the backup. Without the password, you can't restore an encrypted backup. Lost password cannot be recovered in any way.
11. Click Apply now to confirm the backup sets.
12. You can leave the Advanced Backup Options with their default settings. If you want detailed log files for the backup job, you can enable them by expanding the Log Detail Level menu and selecting File.
13. Click Create Job.
14. IBM Cloud Backup for Classic offers three job retention schemes: Daily, Weekly, Monthly. In the new schedule window, select the appropriate retention period and click Save.



Multiple retention schedules can be set up for same job but it’s important they are NOT be run at same time. For more information about Retention Schemes, see the [FAQ](https://cloud.ibm.com/docs/Backup?topic=Backup-faqsfaqs).







 Running a backup job 



1. The new job is displayed on the Computers tab. To start the job, click Select Actions and click Run Job.
2. Verify that the destination and retention scheme appear correctly and click Start Backup. The Progress Detail page shows the job progress. This window can be closed if needed, the backup job keeps running in background.
3. When the backup job is complete, the Process ID Status shows "Finished". You can view the job history and logs of existing backup jobs on the Computer tab. Select the job that you want to view, click Select Action, and choose History/Logs.
Local time conversion is automatically provided on the screen, for example, 12 PM Central Daylight Time.



* Weekly



* For a Weekly plan, select the days of the week that you want backups to run. For example, you can select Monday, Wednesday, and Friday. Specify the starting time in the same manner as a Daily plan.



* Monthly



* For a Monthly plan, select the day of the month that you want backups to run. For example, "1" schedules a backup every first of the month. Specify the starting time in the same manner as a Daily plan.



* Specify by using cron expression



* Under Cron expression (UTC), enter the backup creation frequency in cron-spec format: minute, hour, day, month, and weekday. For example, to create a backup every day at 5:30 PM, you need to enter 30 17 * * .





The Backup destination shows the Block Storage for VPC volume's region. The Backup resource group is the resource group that is associated with the volume.
3. Specify a Retention type for the backups. You can specify either how long to keep them by number of days or the total number to retain.



* For Age, specify the number of days that you want to retain the backups. A default value for the maximum number of days to keep a backup is not provided.
* For Count, provide the number of backups that you want to keep.



To keep costs down, set a retention period or snapshots count adequate to your needs. For example, setting "7" for Age retains a week's worth of backups.
4. Under Optional, you can configure two options.



* Fast snapshot restore - When you enable this feature, you must specify the zone or zones where you want [fast restore](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-aboutsnapshots_vpc_fast_restore) enabled. You can also specify the maximum number of fast restore snapshots that you want to retain.
If TIMESTAMP EXPRESSION 1 is less than the table’s retention start timestamp, an error is returned. 







 BEFORE 

You can use the BEFORE subclause when you want to to retrieve the state of your data as it was just before any specific time in the past.



 Syntax Description 

 BEFORE <TIMESTAMP EXPRESSION 1> Includes all the rows that were valid just before the timestamp that TIMESTAMP EXPRESSION 1 evaluates to. Whose insert timestamp is strictly less than TIMESTAMP EXPRESSION 1 and whose delete timestamp is NULL or is greater than TIMESTAMP EXPRESSION 1. If TIMESTAMP EXPRESSION 1 is less than or equal to the table’s retention start timestamp, an error is returned. 







 FROM...TO and BETWEEN...AND 

You can use the FROM...TO and BETWEEN...AND subclauses for data audit or trend analysis. Use it, when you need to get all historical transformation, for some or all rows, over a period of time.



 Syntax Description 

 FROM <TIMESTAMP EXPRESSION 1> TO <TIMESTAMP EXPRESSION 2> Includes all the rows that were valid at any time from TIMESTAMP EXPRESSION 1 to TIMESTAMP EXPRESSION 2 (exclusive), whose insert timestamp is strictly less than TIMESTAMP EXPRESSION 2 and whose delete timestamp is NULL or is greater than TIMESTAMP EXPRESSION 1. If TIMESTAMP EXPRESSION 1 or TIMESTAMP EXPRESSION 2 is less than or equal to the table’s retention start timestamp, an error is returned. If TIMESTAMP EXPRESSION 1 is greater than or equal to TIMESTAMP EXPRESSION 2, the query produces no rows. 
 BETWEEN <TIMESTAMP EXPRESSION 1> AND <TIMESTAMP EXPRESSION 2> Includes all the rows that were valid at any time between TIMESTAMP EXPRESSION 1 and TIMESTAMP EXPRESSION 2 (inclusive), whose insert timestamp is less than or equal to TIMESTAMP EXPRESSION 2 and whose delete timestamp is NULL or is greater than TIMESTAMP EXPRESSION 1. If TIMESTAMP EXPRESSION 1 or TIMESTAMP EXPRESSION 2 is less than the table’s retention start timestamp, an error is returned. If TIMESTAMP EXPRESSION 1 is greater than TIMESTAMP EXPRESSION 2, the query produces no rows.
AU-11 - Audit Record Retention 



  Control requirements 

AU-11 - 0
:   The organization retains audit records for [IBM Assignment: online for 90 days and offline for one (1) year] to provide support for after-the-fact investigations of security incidents and to meet regulatory and organizational information retention requirements.





  Additional IBM Cloud for Financial Services specifications 



*  All records specified by a customer and/or its regulators must be retained according to the specified retention policy. All organizations must comply with customer-specified retention policies.







  Implementation guidance 

See the resources that follow to learn more about how to implement this control.



*  [Audit logging of application provider events and SIEM](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-logging-audit-provider)
*  [Audit logging of IBM Cloud events](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-logging-audit)
*  [IBM Cloud account setup](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-setup)
*  [Setting up an operational logging solution](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-logging-operational-tutorial)







  IBM Cloud for Financial Services profile 

The rules related to this control that follow are part of the IBM Cloud for Financial Services v1.2.0 profile in [IBM Cloud® Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-getting-started).



*  Check whether Cloud Object Storage quota enforcement is off for buckets that are configured to use Activity Tracker Event Routing







  NIST supplemental guidance 

Organizations retain audit records until it is determined that they are no longer needed for administrative, legal, audit, or other operational purposes. This includes, for example, retention and availability of audit records relative to Freedom of Information Act (FOIA) requests, subpoenas, and law enforcement actions. Organizations develop standard categories of audit records relative to such types of actions and standard response processes for each type of action. The National Archives and Records Administration (NARA) General Records Schedules provide federal policy on record retention.
1801u 



 Issues Resolved 



Issues resolved for 1801u

 Issue Number Priority Summary 

 VRVDR-44406 Critical With multiple subnet on same VIF low rate of transit traffic observed when compared to 5400 performance 
 VRVDR-44253 Minor MSS clamping on bonding interface stops functioning after reboot 







 Security Vulnerabilities Resolved 



Security vulnerabilities resolved for 1801u

 Issue Number CVSS score Advisory Summary 

 VRVDR-44277 N/A DSA-4332-1 CVE-2018-16395, CVE-2018-16396: Debian DSA-4332-1 : ruby2.3 - security update 
 VRVDR-44276 N/A DSA-4331-1 CVE-2018-16839, CVE-2018-16842: Debian DSA-4331-1 : curl - security update 









 1801t 



 Issues Resolved 



Issues resolved for 1801t

 Issue Number Priority Summary 

 VRVDR-44172 Blocker Error “interfaces [openvpn] is not valid” reported in mss-clamp tests 
 VRVDR-43969 Minor Vyatta 18.x GUI reports the wrong status check memory usage 
 VRVDR-43847 Major Slow throughput for TCP conversations on bonding interface 







 Security Vulnerabilities Resolved 



Security vulnerabilities resolved for 1801t

 Issue Number CVSS score Advisory Summary 

 VRVDR-43842 N/A DSA-4305-1 CVE-2018-16151, CVE-2018-16152: Debian DSA4305-1: strongswan – security update 









 1801s 



 Issues Resolved 



Issues resolved for 1801s

 Issue Number Priority Summary 

 VRVDR-44041 Major SNMP ifDescr oid slow response time 







 Security Vulnerabilities Resolved 



Security vulnerabilities resolved for 1801s

 Issue Number CVSS score Advisory Summary 

 VRVDR-44074 9.1 DSA-4322-1 CVE-2018-10933: Debian DSA-4322-1: libssh – security update