Member since
10-31-2019
3
Posts
0
Kudos Received
0
Solutions
11-04-2019
04:44 AM
@bgooley Ah,alright! Will be willing to see the feature being rolled out soon. Thanks!
... View more
11-01-2019
04:30 AM
@bgooley @Shelton So, I am able to connect to SQL Developer/SQL Plus for the kerberos authenticated DB. Steps followed: 1. kinit -k -t <keytabfile> <user>@<Realm/domain> 2. A ticket is created by the above command. Point the credential file location in SQL Developer to this ticket file location. 3. Provide host,post and DB service name. Click on the checkbox where it mentions Kerberos authentication. 4. Voila, SQL Developer connects to the database (without passing username/password) But, similar set of steps fails in Sqoop to connect to the db since there is no option in Sqoop to mention that the DB has to connected using kerberos authentication (There was a checkbox in sqldeveloper). Is there any way to do the same in Sqoop? My sqoop command is as below: sqoop export -Dmapred.job.queue.name=<processingqueue> --connect "jdbc:oracle:thin:@hostname:portnumber/DBNAME" --table <targettable> --hcatalog-table <tableinhive> --hcatalog-partition-keys <partitioncolumn> --hcatalog-partition-values <partitionvalue> --hcatalog-database <dbname> The above command works fine when I provide a username and password for an on-premise database but for a database with kerberos authentication (where you are not supposed to provide any username/password, it fails)
... View more
10-31-2019
02:35 AM
While doing a sqoop-export to load data from HDFS to Oracle hosted on cloud, I face the below issue.
ERROR manager.SqlManager: Error executing statement: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
I have done a kinit username@domainname already before initializing the sqoop command and kinit has generated a valid kerberos ticket as well. Even though I do this and run the command from the location where the kerberos user keytab file is located, it still gives me the above issue. As I can see in the sqoop.properties file, parameter org.apache.sqoop.security.authentication.type=KERBEROS is commented out. Is this the reason for the above issue? How can we resolve the above issue where we need sqoop to export data from HDFS to kerberos authenticated DB?
... View more
Labels:
- Labels:
-
Apache Sqoop