Troubleshooting Non-Default Databases with Hive
Use these entries to help you troubleshoot any issues you might have installing Hive with non-default databases.
Problem: Hive Metastore Install Fails Using Oracle
Check the install log:
cp /usr/share/java/${jdbc_jar_name} ${target}] has failures:
true
The Oracle JDBC.jar file cannot be found.
Solution
Make sure the file is in the appropriate directory on the Hive Metastore server and click Retry.
Problem: Install Warning when "Hive Check Execute" Fails Using Oracle
Check the install log:
java.sql.SQLSyntaxErrorException: ORA-01754: a table may contain only one
column of type LONG
The Hive Metastore schema was not properly loaded into the database.
Solution
Ignore the warning, and complete the install. Check your database to confirm the
Hive Metastore schema is loaded. In the Ambari Web GUI, browse to Services > Hive. Choose
Service Actions > Service Check to check that the schema is
correctly in place.
Problem: Hive Check Execute may fail after completing an Ambari upgrade to version 1.4.2
For secure and non-secure clusters, with Hive security authorization enabled, the Hive service check may fail. Hive security authorization may not be configured properly.
Solution
Two workarounds are possible. Using Ambari Web, in HiveConfigsAdvanced:
Disable
hive.security.authorization, by setting thehive.security.authorization.enabledvalue to false.or
Properly configure Hive security authorization. For example, set the following properties:
For more information about configuring Hive security, see Metastore Server Security and Hive Authorization.
Table 8.1. Hive Security Authorization Settings
Property Value hive.security.authorization.manager org.apache.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider
hive.security.metastore.authorization.manager org.apache.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider
hive.security.authenticator.manager org.apache.hadoop.hive.ql.security.ProxyUserAuthenticator