Unable to connect to Oracle database ORA-00942: table or view does not exist
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
Unable to migrate to Oracle database.
The following appears in the atlassian-fisheye-<date>.log:
1
2013-05-09 11:10:15,136 ERROR - Unable to connect to Oracle database jdbc:oracle:thin:@HostnameXXX:1635:dbnameXXX: java.sql.SQLException: ORA-00942: table or view does not exist
Diagnosis
Try connecting to your Oracle database with a database client such as SQLDeveloper or DBVisualizer using the login credentials of your Fisheye/Crucible database user.
Once you are connected, try to manually create a table in the database.
1
2
3
4
create table t (
a number,
b varchar2(10)
);If you are thrown a permission error, then your Fisheye/Crucible database user does not have sufficient privileges to create tables in the database. After failing to create tables Fisheye/Crucible tries to insert data into the tables and throws the above error.
Cause
The Fisheye/Crucible database user does not have sufficient privileges to create tables in database.
Solution
Resolution
The Fisheye/Crucible database user should have at least the connect and resource privilege to the database. If you are unsure how to grant this permission, talk to your oracle DBA.
In this particular case the resource role is missing: this is the role that grants the ability for users to create objects in their own schema.
Generally, these are the permissions needed, as stated in the following command:
1
grant connect, resource, create table to <database_user_name>;
Was this helpful?