During non-business hours, CIS refreshes data and may perform system maintenance.
You should not schedule or subscribe to a report during the times listed on this page, as the run may be terminated, fail, not run at all, or the data may be unreliable.
Tip: As a best practice recommendation, schedule or subscribe to reports at 8:00 AM to avoid the data refresh schedules and maintenance windows. Your reports will likely be ready for you when you start your day at 8:30 AM.
Maintenance Window
This window is when CIS reserves to take Cognos Analytics Production offline for maintenance. CIS is not usually performing maintenance during these times.
When planned maintenance will result in a Cognos Analytics outage, CIS will email you ahead of time.
|
Users Affected |
Sunday |
Monday-Friday |
Saturday |
Impact on Records |
|
All users |
5 am - Noon |
5 am - 8 am |
3:30 am - 8 am |
When maintenance is being performed, reports or jobs scheduled during this window will fail or not run. |
Data Refresh Schedules
These schedules are when CIS refreshes data sources used by Cognos Analytics. These occur regularly—CIS will not notify you each time they run.
Use the table below to determine when to avoid scheduling reports to run for the package(s) you report against.
the run may be terminated, fail, not run at all, or the data may be unreliable.
Tip: You can determine what package your report uses by viewing the properties of the entry.
|
Users Affected |
Window |
Reporting packages affected |
Sunday |
Monday - Friday |
Saturday |
Impact on Reports |
|
Coeus reporting users |
Coeus Load |
•Conflict of Interest •IRB •IACUC •Sponsored Projects |
n/a |
11:00 pm - midnight |
n/a |
During this window, scheduled jobs or reports will be terminated and no jobs or reports will run. |
| 25Live reporting users | Event Scheduling | Event Scheduling | 7 am - 7:30 am | 4 am - 4:30 am | 7 am - 7:30 am |
During this window, scheduled jobs or reports will run, but data may be inaccurate or incomplete. Generally, the load runs very quickly (<1 minute), but we recommend not scheduling reports during this window. This package includes data items from ODS in certain query subjects. Reports that include these ODS data items are affected by the ODS (Banner) Refresh and ODS (Banner) Load windows below. |
| Banner reporting users |
ODS (Banner) Refresh |
•Accounts Receivable •Admission •Continuing Education •Course Evaluation •Course Proposal •Course Proposal (Departmental) •Event Scheduling (only certain query subjects include ODS data) •Faculty •Financial Aid •GSIM •GSIM Post 2015 •Recruitment •Student •Student (Departmental) |
11 pm - completion (approx 3.5 hours) | 11 pm - completion (approx 3.5 hours) | n/a |
During this window, scheduled jobs or reports will be terminated and no jobs or reports will run. Run time for the ODS refresh depends on the amount of data that was loaded during the day. On average the run time is about 3 hours. Note: For ODS refresh windows that affect Banner reporting in other Cognos Analytics environments (QA, Development, and Test), see ODS Non-Production Data Refresh Schedules. |
| ODS (Banner) Load | n/a | n/a | 5pm - completion (approx 9 hours) |
During this window, scheduled jobs or reports will be terminated and no jobs or reports will run. On average, the run time for the ODS load is between 8 and 9 hours. Note: For ODS load windows in other Cognos Analytics environments (QA, Development, and Test), see ODS Non-Production Data Refresh Schedules. |
||
| Banner Real-Time Data |
•Accounts Receivable •Admission •Continuing Education •Financial Aid •Student |
every 30 minutes (:15 and :45 minutes past the hour) |
This replication schedule will not adversely affect scheduled reports and can be ignored when you specify a schedule run time. These packages contains a folder (named Banner (real-time) data) of specific ODS data items that are updated from Banner every 30 minutes. This allows for more current "real-time" reporting than using data refreshed only once nightly. Real-time reporting is accomplished through something called materialized views for replication. CIS refreshes this content via an Application Manager chain named PODS_REFRESH_STAGING_MVS. |
|||
Why don't I see a data refresh schedule for my package?
Some packages are not refreshed because:
- they report directly against live Production data
- the data does not change, like historical data from legacy systems
See Package Data Sources & Refresh Schedules for details about a specific package.
Comments (0)
Brown Community members, log in to submit a comment.