Cognos data import: Difference between revisions
Jump to navigation
Jump to search
TOstryzniuk (talk | contribs) |
Ttenbergen (talk | contribs) |
||
| (38 intermediate revisions by 4 users not shown) | |||
| Line 2: | Line 2: | ||
== Process == | == Process == | ||
[[Decision Support Services]] sends an automated email report to Lisa and Pagasa | |||
every morning. The data is then imported into [[CCMDB.accdb]] master on Regional server and provided to collectors via regular roll-out and news and backup. | |||
=== | === Cognos extract via email === | ||
Decision Support Services | Generally the email from [[Decision Support Services]] arrives around anytime between 0700-1100. This can be delayed if the ETL that feeds the process is delayed. If it will be delayed [[Decision Support Services]] will send an email to Lisa. | ||
=== | ==== Process if the email does not arrive ==== | ||
If the email has not arrived by 1100, we contact [[Decision Support Services]] (see that page for contact info, it keeps changing). | |||
=== Steps to import and roll-out === | |||
Once the email arrives each morning we run [[LoadCognos.bat]] (if the .bat isn't visible, it is the file of type "Windows Batch File"). | |||
The import and roll-out is generally done by the first of the following who is available: | |||
# [[Database Manager]] | |||
# [[Data Processor]] | |||
== | ==== What happens in the process ==== | ||
{{Collapsable | always=This information is only relevant for troubleshooting and should not usually be done manually. | full= | |||
* [[LoadCognos.bat]] calls | * [[LoadCognos.bat]] calls | ||
* [[LoadCognos.vbs]] which calls | * [[LoadCognos.vbs]] which calls | ||
* [[CCMDB.accdb]].[[ | * [[CCMDB.accdb]].[[Function CognosImport]] for the actual steps performed during import, and how the queries and tables work together and the email to collectors is generated. | ||
* process then returns to [[LoadCognos.bat]] which copies [[CCMDB.accdb]] to the [[Regional Server]] and then calls [[Updt all.bat]] to [[Rolling out changes | roll it out]] to all collectors | * process then returns to [[LoadCognos.bat]] which copies [[CCMDB.accdb]] to the [[Regional Server]] and then calls [[Updt all.bat]] to [[Rolling out changes | roll it out]] to all collectors | ||
== Cognos | '''Fallback process''' | ||
*'''2020-Oct-6''' - Tuesday - ran at 0740. No issues. | The import can also be manually run on any computer that has [[CCMDB.accdb]] using the [[Cognos2_Service_Starter#Cognos_Import_Button]] and the data can be manually sent out to collectors following the same process as [[Rolling out changes]]. | ||
'''When run on Tina's computer the process will roll out any current changes in the local file; if anything was changed, update [[log]] saying it has been rolled out! ''' | |||
}} | |||
=== Newly encountered units or services === <!-- linked from VBA via [New unit or service encountered during Cognos data import], fix there if this heading is changed --> | |||
If a unit or service is part of the import that is not already in our reference tables, the import process will catch this and an email will be sent. The recipients of the email are hard-coded in . | |||
Lisa will investigate what the new what the new unit/service is about is about and whether it might affect our collection process or Julie's reports. She will then either add it to the master version [[CCMDB.accdb]] herself or ask Tina to do it. | |||
==== Newly encountered units ==== | |||
Newly encountered units need to be added to the [[s_Cognos_Units table]], see more info there about what the fields mean. | |||
If the unit is one we collect then [[Level of care hierarchy]] needs to be determined (discuss with the [[Statistician]] if not clear) and entries need to be added to [[Boarding Loc]] and [[s_level_of_care table]]. | |||
==== Newly encountered services ==== | |||
Newly encountered services need to be added to the [[s_Cognos_Services table]], see more info there about what the fields mean. | |||
If the service is one we collect then it needs to be added to [[Service tmp entry]] options. | |||
== Problem Log == | |||
{{Collapsable | |||
| always= This is the problem log from when the process was automated. Now that it's done manually there haven't really been problems for some time. | |||
| full= | |||
The VBA logs its progress to a log file \\ad.wrha.mb.ca\wrha\REGION\Shared\ICU_DATA_COLLECTION\Maintenance\ccmdb_log.txt | |||
* 2021-03-04 - Pagasa provided screen shot of error "Error in sub notify_about_new_Congos: The operation failed. The messaging interfaces have rerutned an unknown error. If the problem persists, restart Outlook. - -2147467259" | |||
** This happened when PC was rebooted at the end of the day before, locked in and then left like that over night. | |||
*'''2020-Nov-10''' - email was delayed to 9:17, then rolled out ok | |||
*'''2020-Nov-09''' - Pagasa is away and the updater task has failed on her PC; Tina will do it manually until Pagasa comes back | |||
*'''2020_Oct_23''' - Chastity report came late @ 08:46, Run manually cognos. | |||
*'''2020_Oct_21''' - Chastity email -ETL failed last night so there will be no report today. No new cognos. | |||
*'''2020_Oct_9''' - task was stuck because CFE was open | |||
*'''2020_Oct_8''' - Task schedule did not run because computer were rebooted by EHealth overnight. | |||
*Pagasa changed the Task schedule so it does not run on weekends. Concern will be this long weekend and the task may hang because data from email not deleted before it runs on Tues AM. | |||
*'''2020-Oct-6 & 7''' - Tuesday - ran at 0740. No issues.| | |||
*'''2020-Oct-5 - Monday''' - Task schedule screen stuck open Monday morning. This seems to occur because data is sent by email from Chastity on both Saturday and Sunday. Because Pagasa is not in during the weekend to delete the email from Chastity with data in email, the task scheduler then does not run on Monday. Pagasa has to run it manually when she comes in before 0900. | *'''2020-Oct-5 - Monday''' - Task schedule screen stuck open Monday morning. This seems to occur because data is sent by email from Chastity on both Saturday and Sunday. Because Pagasa is not in during the weekend to delete the email from Chastity with data in email, the task scheduler then does not run on Monday. Pagasa has to run it manually when she comes in before 0900. | ||
*''''2020-Sept 28- Oct 2.20''' - Task schedule ran without issue. | *''''2020-Sept 28- Oct 2.20''' - Task schedule ran without issue. | ||
| Line 42: | Line 81: | ||
*email was not generated and sent out to staff that new cognos data is available....... | *email was not generated and sent out to staff that new cognos data is available....... | ||
*other bug that appeared after Cognos ran today was the '''CCMDB PROGRAM''' is popping up a '''PW message box when you EXIT'''. Had to press cancel to get rid of it. [[User:TOstryzniuk|Trish Ostryzniuk]] 15:15, 2020 September 4 (CDT) | *other bug that appeared after Cognos ran today was the '''CCMDB PROGRAM''' is popping up a '''PW message box when you EXIT'''. Had to press cancel to get rid of it. [[User:TOstryzniuk|Trish Ostryzniuk]] 15:15, 2020 September 4 (CDT) | ||
}} | |||
== Related articles == | == Related articles == | ||
Latest revision as of 13:15, 18 November 2025
This page explains how to get data from the Cognos EPR Report into CCMDB.accdb and rolled out to collectors.
Process
Decision Support Services sends an automated email report to Lisa and Pagasa every morning. The data is then imported into CCMDB.accdb master on Regional server and provided to collectors via regular roll-out and news and backup.
Cognos extract via email
Generally the email from Decision Support Services arrives around anytime between 0700-1100. This can be delayed if the ETL that feeds the process is delayed. If it will be delayed Decision Support Services will send an email to Lisa.
Process if the email does not arrive
If the email has not arrived by 1100, we contact Decision Support Services (see that page for contact info, it keeps changing).
Steps to import and roll-out
Once the email arrives each morning we run LoadCognos.bat (if the .bat isn't visible, it is the file of type "Windows Batch File"). The import and roll-out is generally done by the first of the following who is available:
What happens in the process
| This information is only relevant for troubleshooting and should not usually be done manually. |
Fallback process The import can also be manually run on any computer that has CCMDB.accdb using the Cognos2_Service_Starter#Cognos_Import_Button and the data can be manually sent out to collectors following the same process as Rolling out changes. When run on Tina's computer the process will roll out any current changes in the local file; if anything was changed, update log saying it has been rolled out! |
Newly encountered units or services
If a unit or service is part of the import that is not already in our reference tables, the import process will catch this and an email will be sent. The recipients of the email are hard-coded in . Lisa will investigate what the new what the new unit/service is about is about and whether it might affect our collection process or Julie's reports. She will then either add it to the master version CCMDB.accdb herself or ask Tina to do it.
Newly encountered units
Newly encountered units need to be added to the s_Cognos_Units table, see more info there about what the fields mean.
If the unit is one we collect then Level of care hierarchy needs to be determined (discuss with the Statistician if not clear) and entries need to be added to Boarding Loc and s_level_of_care table.
Newly encountered services
Newly encountered services need to be added to the s_Cognos_Services table, see more info there about what the fields mean.
If the service is one we collect then it needs to be added to Service tmp entry options.
Problem Log
| This is the problem log from when the process was automated. Now that it's done manually there haven't really been problems for some time. |
|
The VBA logs its progress to a log file \\ad.wrha.mb.ca\wrha\REGION\Shared\ICU_DATA_COLLECTION\Maintenance\ccmdb_log.txt
|