<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RTDM: Oracle DB from SAS DS2 process in SAS Customer Intelligence</title>
    <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Oracle-DB-from-SAS-DS2-process/m-p/349116#M391</link>
    <description>&lt;P&gt;Accessing data from DS2&amp;nbsp;doesn't actually have any connection to SMC libraries at all. It's based entirely on the configuration of Fed Server (not SMC) and getting the fully qualified path correct (catalog.schema.table) and making sure it's accessible in your DSFederatedDSN. The best way to work through this is to go into Fed Server Manager and use the "SQL" tab to open a query window, then select the DSFederatedDSN (which should contain your BASE_DSN, plus your Oracle connection) and paste the query in that window. Once you get that query to execute successfully in that window, your SQLSTMT package should work correctly.&lt;/P&gt;</description>
    <pubDate>Tue, 11 Apr 2017 13:50:30 GMT</pubDate>
    <dc:creator>shill</dc:creator>
    <dc:date>2017-04-11T13:50:30Z</dc:date>
    <item>
      <title>RTDM: Oracle DB from SAS DS2 process</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Oracle-DB-from-SAS-DS2-process/m-p/349031#M390</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are using SAS RTDM (SAS CI Studio 6.4M1 Hotfix 01) to host a number of decision services. The biggest of those has grown rather large, to the point that performance when editing the diagram in SAS CI Studio is an issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a side-project, I planned to migrate parts of the logic to DS2 code snippets.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is where I happened upon a problem that has me stumped:&lt;/P&gt;&lt;P&gt;The diagram pulls data from an Oracle DB (access defined in SMC) every few nodes. I initially thought I could access the DB using the SQLSTMT package and the libref I see when choosing the DB table for a new data process. Since I'm here talking about it, this approach obviously wasn't successful.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So here's my question(s): How do I pass the libref to the DS2 code? Or is there a way to call data process functions? Do I need to change anything in SAS Management Console to make it work?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Right now, trying to access with libref.tablename syntax in SQLSTMT&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DECLARE PACKAGE SQLSTMT get('SELECT id, var1, var2 from oracledb.testtable');&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;throws an error&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[com.sas.tkts.sql.FSException: [com.sas.tkts.sql.FSException: T_EXECUTE2: Table Service: Function failed.] SQLSTATE:[42000] MESSAGE:[Syntax error or access violation] NATIVEERROR:[-2130708373]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The syntax is correct, the whole package works fine when running it in SAS Base.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;An alternative would be to use sub-diagrams, but by now I'd really like to know what I'm doing wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for reading!&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2017 09:16:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Oracle-DB-from-SAS-DS2-process/m-p/349031#M390</guid>
      <dc:creator>CMark02</dc:creator>
      <dc:date>2017-04-11T09:16:39Z</dc:date>
    </item>
    <item>
      <title>Re: RTDM: Oracle DB from SAS DS2 process</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Oracle-DB-from-SAS-DS2-process/m-p/349116#M391</link>
      <description>&lt;P&gt;Accessing data from DS2&amp;nbsp;doesn't actually have any connection to SMC libraries at all. It's based entirely on the configuration of Fed Server (not SMC) and getting the fully qualified path correct (catalog.schema.table) and making sure it's accessible in your DSFederatedDSN. The best way to work through this is to go into Fed Server Manager and use the "SQL" tab to open a query window, then select the DSFederatedDSN (which should contain your BASE_DSN, plus your Oracle connection) and paste the query in that window. Once you get that query to execute successfully in that window, your SQLSTMT package should work correctly.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2017 13:50:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Oracle-DB-from-SAS-DS2-process/m-p/349116#M391</guid>
      <dc:creator>shill</dc:creator>
      <dc:date>2017-04-11T13:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: RTDM: Oracle DB from SAS DS2 process</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Oracle-DB-from-SAS-DS2-process/m-p/349191#M392</link>
      <description>&lt;P&gt;Thanks for the reply! Going to try that once I've got all the login details cleared up.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2017 16:34:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Oracle-DB-from-SAS-DS2-process/m-p/349191#M392</guid>
      <dc:creator>CMark02</dc:creator>
      <dc:date>2017-04-11T16:34:25Z</dc:date>
    </item>
  </channel>
</rss>

