We use SIDs at UMN and our connection is working fine. We put the SID in the "Database" field.
Tim Meyer Interim Manager - Research Data Management Academic Health Center - Office of Information Systems Technical Manager, CTSI-BPIC Phone: 612.624.8386 meye0...@umn.edu On Wed, Dec 21, 2016 at 8:01 AM, McClay, James C <jmcc...@unmc.edu> wrote: > Nebraska was getting the same error yesterday. No resolution yet. > > > > James McClay, MD, MS, FACEP > > Associate Professor, Emergency Medicine > > Chair, UNMC Biomedical Informatics Program > > 981150 Nebraska Medical Center > > Omaha, NE 68198-1150 > > jmcc...@unmc.edu > > www.linkedin.com/in/infodoc > > Twitter: @jmcclay > > 402-559-3587 <(402)%20559-3587> > > > > *From:* Gpc-dev [mailto:gpc-dev-boun...@listserv.kumc.edu] *On Behalf Of > *French, > Tony > *Sent:* Wednesday, December 21, 2016 7:16 AM > *To:* GPC-DEV@LISTSERV.KUMC.EDU > *Subject:* PopMedNet MDQ with Oracle SID > > > > Has anyone been successful at configuring the PopMedNet client to connect > to Oracle using a SID, instead of a service name? I’m getting an > “ORA-12514, TNS:listener does not currently know of service requested in > connect descriptor” error when I attempt to use our SID for the Database > value. (Our DBA’s have chosen to continue supporting Oracle SIDs instead > of service names.) > > > > > > > > Thanks, > > Tony > > > > > > *Tony French *| *Software Development Manager, Research* > > * Center for Biomedical Informatics* > > *1101 West Tenth Street * > > *Indianapolis, IN, 46202* > > Tel 317-274-9087 <(317)%20274-9087> | Fax: 317-274-9305 <(317)%20274-9305> > > Twitter: @Regenstrief | Facebook.com/regenstriefinstitute > <https://urldefense.proofpoint.com/v2/url?u=http-3A__facebook.com_regenstriefinstitute&d=DwMFAw&c=ZukO2fIan9e5E9v43wuy1w&r=2VCh0Oru51DJNpJ2_4EbvA&m=JnAn689lTQ4GEQFxCI1E2K1EJFAAFUJIcj9nLDKrlss&s=QwQURYFi_owVcZLgxud4TuTI4XagajBEbj_MjF4udiE&e=> > > www.regenstrief.org > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.regenstrief.org_&d=DwMFAw&c=ZukO2fIan9e5E9v43wuy1w&r=2VCh0Oru51DJNpJ2_4EbvA&m=JnAn689lTQ4GEQFxCI1E2K1EJFAAFUJIcj9nLDKrlss&s=DetcBP2vNT_cPHzu0ZNVcOBScR2TY9dQcq18SDNeH88&e=> > > > > Confidentiality Notice: The contents of this message and any files > transmitted with it may contain confidential and/or privileged information > and are intended solely for the use of the named addressee(s). > Additionally, the information contained herein may have been disclosed to > you from medical records with confidentiality protected by federal and > state laws. Federal regulations and State laws prohibit you from making > further disclosure of such information without the specific written consent > of the person to whom the information pertains or as otherwise permitted by > such regulations. A general authorization for the release of medical or > other information is not sufficient for this purpose. > > If you have received this message in error, please notify the sender by > return e-mail and delete the original message. Any retention, disclosure, > copying, distribution or use of this information by anyone other than the > intended recipient is strictly prohibited. > > > > 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. > > _______________________________________________ > Gpc-dev mailing list > Gpc-dev@listserv.kumc.edu > http://listserv.kumc.edu/mailman/listinfo/gpc-dev > >
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
