WARNING: This message has originated from an External Source. This may be a phishing expedition that can result in unauthorized access to our IT System. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
Utah has also been working with DRNOC on this. Our timeout is set to 7200, still no results. After 12-16 hours the datamart client errors out with no results. I have just sent them our debug info, waiting for more feedback. Reid From: [email protected] <[email protected]> On Behalf Of Wolfe, Frances A Sent: Wednesday, February 17, 2021 7:16 AM To: [email protected] Subject: Re: Issues running MDQ queries WARNING: This message has originated from an External Source. This may be a phishing expedition that can result in unauthorized access to our IT System. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. As a follow up, our team looked at the sql code and have questions about how the query was written. It looks like the query goes 24 levels deep in the sub-queries selecting things from massive tables (ENCOUNTER and DIAGNOSIS specifically are millions of rows). Looking at it, it doesn’t seem possible that this query could run in an hour, so the suggestion to extend the default to 3600 is insufficient. I will add this information to my question to Query Fulfillment and see if they have an recommendations on indexing the DIAGNOSIS, ENCOUNTER and DEMOGRAPHICS tables that might allow the query to run. As usual, any helpful input is appreciated! From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Wolfe, Frances A Sent: Wednesday, February 17, 2021 1:10 AM To: [email protected]<mailto:[email protected]> Subject: FW: Issues running MDQ queries Non-UNMC email WARNING: This message has originated from an External Source. This may be a phishing expedition that can result in unauthorized access to our IT System. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. Hello, As I mentioned in today’s DEV/PM meeting, we are experiencing errors in running some of the MDQ queries recently issued. Below is a suggestion we received from Query Fulfillment to increase the timeout time. We already did this before running the queries. I have followed up this email with a request for more help and also logged a problem ticket. I will share what we find out and would appreciate any insights from others experiencing the same time out error. Thanks! From: PCORnet Query Fulfillment <[email protected]<mailto:[email protected]>> Sent: Tuesday, February 16, 2021 2:19 PM To: PCORnet Front Door <[email protected]<mailto:[email protected]>> Cc: Wolfe, Frances A <[email protected]<mailto:[email protected]>> Subject: Re: Issues running MDQ queries Non-UNMC email Hi Frances, Based on the error message, it appears that the query "timed out" before it completed running. In order to resolve this, I suggest increasing the "timeouts" in the DataMart Client. You can do this by following Hi Frances, Based on the error message, it appears that the query "timed out" before it completed running. In order to resolve this, I suggest increasing the "timeouts" in the DataMart Client. You can do this by following these steps: 1. Open the DataMart Client 2. Select "Settings" and then click on your "PCORnet" network 3. In the Network Settings, select your DataMart Name and click "Edit" 4. In the Models section, select the PCORnet CDM option and click "Edit" 5. This will open a window called "Model Settings". You will notice a Connection and Command Timeout option. I suggest increasing both to at least 3600. 6. Then click "OK" to close the recent two windows, and "Apply" to save the settings. 7. Re-start the DataMart Client and then re-execute the queries If you encounter any other issues, feel free to reach out to the PopMedNet Team and enter a service desk ticket here: https://popmednet.atlassian.net/servicedesk/customer/portal/1/group/6 [popmednet.atlassian.net]<https://urldefense.com/v3/__https:/popmednet.atlassian.net/servicedesk/customer/portal/1/group/6__;!!JkUDQA!Yo27sEiinWz1fQznw57qeabzAur1sD4pXvAFq98W2wonCGnfrfGx_IyTVMOhJaYfVSVf$> Best, Kim On Tue, Feb 16, 2021 at 8:44 AM PCORnet Front Door <[email protected]<mailto:[email protected]>> wrote: Hi Frances, I am adding in Query Fulfillment here to assist with your request. Thanks, On Mon, Feb 15, 2021 at 7:39 PM Wolfe, Frances A <[email protected]<mailto:[email protected]>> wrote: Please see additional error I received the same error for wp014. I see the note below for wp014 and wp011 and have downloaded the file. It is not clear to me what should be done. Is the expectation that we are to write a query based on the logic and run it in a different application? Thanks [cid:[email protected]] From: Wolfe, Frances A Sent: Monday, February 15, 2021 5:21 PM To: PCORnet Front Door <[email protected]<mailto:[email protected]>> Subject: Issues running MDQ queries Hello, I have been having issues running the FD1370 MDQ series today. I have had to quit the application a number of times and start again as it didn’t appear the application was responding. I received the error below for wp011. It is pointed to CDMv6 and have extended the command time to 3600 as stated in the work plan. Another query produced “no results”. I will continue to try to run these. It would be good to know if there are things I should troubleshoot for and or if you have heard other sites having difficulties. Thank you C4UN [cid:[email protected]] _______________________________ Frances Annette Wolfe, MBA UNMC PCORnet Project Manager Department of Emergency Medicine College of Medicine University of Nebraska Medical Center 981150 Nebraska Medical Center | Omaha, NE 68198 - 1150 [email protected]<mailto:[email protected]> The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender. -- -------------------------------------------------------------------------- Query Fulfillment for the PCORnet Distributed Research Network Operations Center QF Email: [email protected]<mailto:[email protected]> QF Wiki: https://pcornet.imeetcentral.com/p/aQAAAAAClFkW [pcornet.imeetcentral.com]<https://urldefense.com/v3/__https:/pcornet.imeetcentral.com/p/aQAAAAAClFkW__;!!JkUDQA!Yo27sEiinWz1fQznw57qeabzAur1sD4pXvAFq98W2wonCGnfrfGx_IyTVMOhJZfMOnT1$> The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender. ________________________________ To unsubscribe from the GPCDEV-L list, click the following link: https://po.missouri.edu/cgi-bin/wa?SUBED1=GPCDEV-L&A=1 [po.missouri.edu]<https://urldefense.com/v3/__https:/po.missouri.edu/cgi-bin/wa?SUBED1=GPCDEV-L&A=1__;!!JkUDQA!c2pwE6y5bLrbV5UIVq92YZ9a0yOhJK3vEUwyZ4WVx2-8K71m7Pfhk44F61FmMdoAk0ak$> The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender. ________________________________ To unsubscribe from the GPCDEV-L list, click the following link: https://po.missouri.edu/cgi-bin/wa?SUBED1=GPCDEV-L&A=1 ######################################################################## To unsubscribe from the GPCDEV-L list, click the following link: https://po.missouri.edu/cgi-bin/wa?SUBED1=GPCDEV-L&A=1
