CCSQ Data & Analytics

CAP and CDR Maintenance Outage

A maintenance event for CAP and CDR is scheduled for Friday, October 23rd, beginning at 8:00 pm EDT. During this maintenance event, the Data and Analytics team will implement the URL changes as announced during our bi-weekly Communications Calls and in our Weekly Communications. The event will complete later that evening, and a communication will be sent out once maintenance is complete.

Call to Action: If you have not saved your tables, please make sure to do so. This is to ensure that your information will be saved throughout the maintenance process. Any long running jobs would also have to be restarted.

Prior to the planned maintenance window, users should save any of the tables in their own CASLIB to Hive in order for the information to be saved. You can save your existing CASLIB data loaded into memory using the following code. You’ll need to update the code to reference your CASLIB name and table. You will need to save each table individually. After the maintenance window, you will need to load your tables back into memory in order to continue working with them. As a reminder, whenever there is maintenance on the environment, you will need to make sure all of your code and table changes are saved.

* Save CAS in-memory table to Hive;

PROC CASUTIL;

SAVE REPLACE

INCASLIB="mylib" CASDATA="mytable"

OUTCASLIB="mylib" CASOUT="mytable";

RUN;

SAS Viya and CDR Restart

A small maintenance event and restart for SAS Viya and CDR will occur on October 9th at 8:00 pm EDT. The environment will be unavailable for around 15 minutes. During the small downtime this evening, we will add additional Storage Gateway configurations for SAS Viya and correct the vertex issue that was observed in the CDR on October 6th and 7th. A communication will be sent out after the restart is complete.

Call to Action: Please ensure any data that needs to be stored on the SAS Workbench is saved prior to the 8:00 pm EDT maintenance window. Any long-running jobs that are reading or writing to workbench would have to be restarted.

CAP and CDR Maintenance Outage

A maintenance event for CAP and CDR is scheduled for Friday, September 18th, beginning at 8:00 pm EDT. This event will complete later that evening. A communication will be sent out once maintenance is complete.

Call to Action: If you have not saved your tables, please make sure to do so. This is to ensure that your information will be saved throughout the maintenance process. Also, please avoid running jobs that will extend into the maintenance window.

Prior to the planned maintenance window, users should save any of the tables in their own CASLIB to Hive in order for the information to be saved. You can save your existing CASLIB data loaded into memory using the following code. You’ll need to update the code to reference your CASLIB name and table. You will need to save each table individually. After the maintenance window, you will need to load your tables back into memory in order to continue working with them. As a reminder, whenever there is maintenance on the environment, you will need to make sure all of your code and table changes are saved.

* Save CAS in-memory table to Hive; 

PROC CASUTIL; 

         SAVE REPLACE                                           

         INCASLIB="mylib" CASDATA="mytable" 

         OUTCASLIB="mylib" CASOUT="mytable"; 

RUN;

CAP and CDR Unscheduled Maintenance Outage

An unscheduled maintenance event for CAP and CDR is scheduled for Sunday, September 13th, beginning at 3:00 pm EDT. This event will complete later that evening. A communication will be sent out once maintenance is complete.

Call to Action: If you have not saved your tables, please make sure to do so. This is to ensure that your information will be saved throughout the maintenance process. Any log running jobs would also have to be restarted.

Prior to the planned maintenance window, users should save any of the tables in their own CASLIB to Hive in order for the information to be saved. You can save your existing CASLIB data loaded into memory using the following code. You’ll need to update the code to reference your CASLIB name and table. You will need to save each table individually. After the maintenance window, you will need to load your tables back into memory in order to continue working with them. As a reminder, whenever there is maintenance on the environment, you will need to make sure all of your code and table changes are saved.

* Save CAS in-memory table to Hive; 

PROC CASUTIL; 

         SAVE REPLACE                                           

         INCASLIB="mylib" CASDATA="mytable" 

         OUTCASLIB="mylib" CASOUT="mytable"; 

RUN;

CAP and CDR Maintenance Outage

The next maintenance event for CAP and CDR is scheduled for Friday, August 21st, beginning at 8:00 pm EDT and will extend until the evening of Sunday, August 23. A communication will be sent out once maintenance is complete. 

1. Log into SAS Viya and go to the Data Explorer section of SAS Studio. Make a note of all your existing favorites under “My Favorites” (i.e., favorites/shortcuts referencing workspace path, CASLIB, or home directories). This is a necessary step to follow because some of the favorites/shortcuts to workspace path, CASLIB, or home directories will not be migrated following the maintenance window. As a reminder, the favorites can be found here: 
   
   
   
   
2. If you have not saved your tables, please make sure to do so. This is to ensure that your information will be saved throughout the maintenance process.

   Prior to the planned maintenance window, users should save any of the tables in their own CASLIB to Hive in order for the information to be saved. You can save your existing CASLIB data loaded into memory using the following code. You’ll need to update the code to reference your CASLIB name and table. You will need to save each table individually. After the maintenance window, you will need to load your tables back into memory in order to continue working with them. As a reminder, whenever there is maintenance on the environment, you will need to make sure all of your code and table changes are saved 

 * Save CAS in-memory table to Hive; 

PROC CASUTIL; 

          SAVE REPLACE                                           

          INCASLIB="mylib" CASDATA="mytable" 

          OUTCASLIB="mylib" CASOUT="mytable"; 

RUN; 

SAS Viya Maintenance Outage

The next maintenance event for SAS Viya to implement security improvements is scheduled for Friday, August 14, beginning at 8:00 pm EDT. A communication will be sent out once maintenance is complete.

Call to Action: If you have not saved your tables, please make sure to do so. This is to ensure that your information will be saved throughout the maintenance process.

Prior to the planned maintenance window, users should save any of the tables in their own CASLIB to Hive in order for the information to be saved. You can save your existing CASLIB data loaded into memory using the following code. You’ll need to update the code to reference your CASLIB name and table. You will need to save each table individually. After the maintenance window, you will need to load your tables back into memory in order to continue working with them. 

As a reminder, whenever there is maintenance on the environment, you will need to make sure all of your code and table changes are saved. 

* Save CAS in-memory table to Hive; 

PROC CASUTIL; 

SAVE REPLACE

INCASLIB="mylib" CASDATA="mytable"

OUTCASLIB="mylib" CASOUT="mytable"; 

CAP and CDR Maintenance Outage

The next maintenance event for CAP and CDR is scheduled for Friday, July 31st beginning at 8:00 pm EDT and will extend until the evening of Sunday, August 2. A communication will be sent out once maintenance is complete. 

1. Users will likely need to configure their personal preferences again when they login after maintenance is complete. Please review and make note of your current preferences today from the application settings. Your user settings are found in the drop-down menu at the top right of the Viya application in your browser.

   

2. If you have not saved your tables, please make sure to do so. This is to ensure that your information will be saved throughout the maintenance process.
   Prior to the planned maintenance window, users should save any of the tables in their own CASLIB to Hive in order for the information to be saved. You can save your existing CASLIB data loaded into memory using the following code. You’ll need to update the code to reference your CASLIB name and table. You will need to save each table individually. After the maintenance window, you will need to load your tables back into memory in order to continue working with them. As a reminder, whenever there is maintenance on the environment, you will need to make sure all of your code and table changes are saved. 

 * Save CAS in-memory table to Hive; 

PROC CASUTIL; 

          SAVE REPLACE                                           

          INCASLIB="mylib" CASDATA="mytable" 

          OUTCASLIB="mylib" CASOUT="mytable"; 

RUN; 

CAP and CDR Monthly Maintenance

Monthly maintenance for CAP and CDR is scheduled for tonight, July 24, beginning at 8:00 pm EDT. A communication will be sent out once maintenance is complete.

Call to Action

If you have not saved your tables, please make sure to do so. This is to ensure that your information will be saved throughout the maintenance process.

Prior to the planned maintenance window, users should save any of the tables in their own CASLIB to Hive in order for the information to be saved.

You can save your existing CASLIB data loaded into memory using the following code. You’ll need to update the code to reference your CASLIB name and table. You will need to save each table individually. After the maintenance window, you will need to load your tables back into memory in order to continue working with them.

* Save CAS in-memory table to Hive;

PROC CASUTIL;

SAVE REPLACE
INCASLIB="mylib" CASDATA="mytable"
OUTCASLIB="mylib" CASOUT="mytable";

RUN;

As a reminder, whenever there is maintenance on the environment, you will need to make sure all of your code and table changes are saved.