CCMDB Wiki

Cognos data import: Difference between revisions

← Older edit
 
(26 intermediate revisions by 2 users not shown)
Line 2: Line 2:


== Process ==
== Process ==
Tina receives the data in a scheduled, automated email from Chastity every morning as early as possible, usually before 8. The data is then imported into [[CCMDB.accdb]] master on Regional server and provided to collectors via regular roll-out and news and backup.
[[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.


=== Outlook Rule in Tina's profile to get data to Pagasa ===
=== Cognos extract via email ===
Decision Support Services sends a report to Tina. The report needs to go to Pagasa so we can schedule the automated import on a machine that sits on WRHA network at all times. So, there is an outlook rule "Cognos to Pagasa" in Tina's Outlook profile to forward the email to Pagasa from Chastity.  
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.


=== Scheduled Task on Pagasa's PC ===
==== Process if the email does not arrive ====
There is a scheduled task on Pagasa's PC that calls [[LoadCognos.bat]] early each morning.
If the email has not arrived by 1100, we contact [[Decision Support Services]] (see that page for contact info, it keeps changing).  
*it pulls the data from and Excel sheet in an email that is sent to Pagasa (from a Chastity who is works in decision support)
'''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! '''
There should be no instructions required if the scheduled task running [[LoadCognos.bat]] works. Follow the trail through that file if troubleshooting is required.


=== newly encountered units ===
=== Steps to import and roll-out ===
If a unit is encountered that isn't in [[s_Cognos_Units table]], an email will be sent to Tina. The new unit then needs to be added to [[s_Cognos_Units table]] with the other fields filled in appropriately. [[Boarding Loc]] and [[Level of care hierarchy]]/[[s_level_of_care table]] entries need to be considered to see if they need to be updated.
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]]


=== newly encountered services ===
==== What happens in the process ====
If a service is encountered that isn't in [[S Cognos Services table]] an email will be sent to Tina. The new service then needs to be added to [[Cognos_SubServices table]] with the other fields filled in appropriately. [[Service tmp entry]] entries need to be considered to see if they need to be updated.
{{Collapsable | always=This information is only relevant for troubleshooting and should not usually be done manually. | full=  
 
== Background ==
* [[LoadCognos.bat]] calls
* [[LoadCognos.bat]] calls
* [[LoadCognos.vbs]] which calls  
* [[LoadCognos.vbs]] which calls  
* [[CCMDB.accdb]].[[Sub CognosImport]] for the actual steps performed during import, and how the queries and tables work together and the email to collectors is generated.
* [[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


== Known problems with data import ==
'''Fallback process'''
=== Shared Health Re-boots ===
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]].  
The task requires the user be logged in. If Shared Health re-boots the computer over night, the task won't run until Pagasa logs on.  


=== [[CFE]] left open on Pagasa's PC ===
'''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! '''
'''[[CFE]] needs to be closed at the end of the work day on Pagasa's computer.''' The update process needs to download the newest version of [[CCMDB.accdb]] from the [[Regional Server]] before it runs so that it doesn't overwrite the master version with an older version from Pagasa's PC. This download of the newest version is blocked when [[CFE]] is open.  
}}
 
=== 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 ==
== Problem Log ==
{{Collapsable  
{{Collapsable  
| always= detailed log
| 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=
| 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-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-Nov-09''' - Pagasa is away and the updater task has failed on her PC; Tina will do it manually until Pagasa comes back
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Cognos_data_import"