<?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>question Re: Can we use Oracle SID in --connect option of sqoop loader? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-use-Oracle-SID-in-connect-option-of-sqoop-loader/m-p/178106#M67778</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1179/nileshshrimant.html" nodeid="1179"&gt;@Nilesh Shrimant&lt;/A&gt;&lt;/P&gt;&lt;P&gt;According to the JDBC Driver implementation it can take SID as well like, If the database to which you want to connect resides on host prodHost, at port 1521, and system identifier (SID) ORCL, and you want to connect with user name scott and password tiger, then use either of the two following connection strings:&lt;/P&gt;&lt;PRE&gt;Using host:port:sid 

syntax:
String connString="jdbc:oracle:thin:@prodHost:1521:ORCL";&lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;NOTICE: &lt;/STRONG&gt;After Port there is a Colon (:) and then SID.&lt;BR /&gt;&lt;A href="https://docs.oracle.com/cd/B28359_01/java.111/b31224/jdbcthin.htm" target="_blank"&gt;https://docs.oracle.com/cd/B28359_01/java.111/b31224/jdbcthin.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Are you getting any error while using SID in the same URL ?&lt;/P&gt;</description>
    <pubDate>Fri, 08 Sep 2017 11:36:13 GMT</pubDate>
    <dc:creator>jsensharma</dc:creator>
    <dc:date>2017-09-08T11:36:13Z</dc:date>
    <item>
      <title>Can we use Oracle SID in --connect option of sqoop loader?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-use-Oracle-SID-in-connect-option-of-sqoop-loader/m-p/178105#M67777</link>
      <description>&lt;P&gt;Geerally when we use --connect option in sqoop we use "jdbc:oracle:thin:@hostname:port/DB_SERVICE_NAME". &lt;/P&gt;&lt;P&gt;But can we user DB_SID instead of DB_SERVICE_NAME in connect option? If yes what will be the syntax for that.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Sep 2017 10:34:23 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-use-Oracle-SID-in-connect-option-of-sqoop-loader/m-p/178105#M67777</guid>
      <dc:creator>nilesh_shrimant</dc:creator>
      <dc:date>2017-09-08T10:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: Can we use Oracle SID in --connect option of sqoop loader?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-use-Oracle-SID-in-connect-option-of-sqoop-loader/m-p/178106#M67778</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1179/nileshshrimant.html" nodeid="1179"&gt;@Nilesh Shrimant&lt;/A&gt;&lt;/P&gt;&lt;P&gt;According to the JDBC Driver implementation it can take SID as well like, If the database to which you want to connect resides on host prodHost, at port 1521, and system identifier (SID) ORCL, and you want to connect with user name scott and password tiger, then use either of the two following connection strings:&lt;/P&gt;&lt;PRE&gt;Using host:port:sid 

syntax:
String connString="jdbc:oracle:thin:@prodHost:1521:ORCL";&lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;NOTICE: &lt;/STRONG&gt;After Port there is a Colon (:) and then SID.&lt;BR /&gt;&lt;A href="https://docs.oracle.com/cd/B28359_01/java.111/b31224/jdbcthin.htm" target="_blank"&gt;https://docs.oracle.com/cd/B28359_01/java.111/b31224/jdbcthin.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Are you getting any error while using SID in the same URL ?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Sep 2017 11:36:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-use-Oracle-SID-in-connect-option-of-sqoop-loader/m-p/178106#M67778</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2017-09-08T11:36:13Z</dc:date>
    </item>
    <item>
      <title>Re: Can we use Oracle SID in --connect option of sqoop loader?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-use-Oracle-SID-in-connect-option-of-sqoop-loader/m-p/178107#M67779</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/3418/jsensharma.html" nodeid="3418"&gt;@Jay SenSharma&lt;/A&gt;, Thanks very much for the information. "String connString="jdbc:oracle:thin:@prodHost:1521:ORCL" this worked fine.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Sep 2017 16:03:44 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-use-Oracle-SID-in-connect-option-of-sqoop-loader/m-p/178107#M67779</guid>
      <dc:creator>nilesh_shrimant</dc:creator>
      <dc:date>2017-09-08T16:03:44Z</dc:date>
    </item>
    <item>
      <title>Re: Can we use Oracle SID in --connect option of sqoop loader?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-use-Oracle-SID-in-connect-option-of-sqoop-loader/m-p/178108#M67780</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1179/nileshshrimant.html" nodeid="1179"&gt;@Nilesh Shrimant&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Good to know that your issue is resolved. It will be wonderful if you can make the correct answer as "&lt;STRONG&gt;Accepted&lt;/STRONG&gt;" so that it will be useful for other HCC users to quickly browse the answered threads.&lt;BR /&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1179/nileshshrimant.html" nodeid="1179"&gt;&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 08 Sep 2017 16:10:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-use-Oracle-SID-in-connect-option-of-sqoop-loader/m-p/178108#M67780</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2017-09-08T16:10:14Z</dc:date>
    </item>
  </channel>
</rss>

