Error creating issue: org.ofbiz.core.entity.GenericEntityException: while inserting:(ORA-00942: table or view does not exist ))

[amit raj]

Hello friends,

we are getting these errors while creating , editing or assging issue in JIRA 6.3, could you help please?

we have checked database table permission and DBA side, there is no issue from DBA side. also checked with enabling safe mode that also did not work.  any idea please?

Error creating issue: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:CustomFieldValue][id,3753620][stringvalue,10065][issue,333038][parentkey,null][customfield,10018] (SQL Exception while executing the following:INSERT INTO customfieldvalue (ID, ISSUE, CUSTOMFIELD, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (ORA-00942: table or view does not exist ))

Thank you

Amit Raj

[Nic Brough -Adaptavist-]

"There is no issue from DBA side" - well, yes there is - your JIRA user does not have access to a table, either because the permissions are incorrect or the table is not there.

First, you need to establish what the problem is in the database - is the table there?  If it is, then the permissions on the database are incorrect.  If it is not, then you've got bigger problems, and need to go further.

If the table is missing, then you need to investigate further, starting with telling us what the starting point is - have you just set up a new JIRA?  Have you just upgraded JIRA and the errors started after that?  Or is it a JIRA that was working ok yesterday and these errors have just started without you doing anything unusual to it?

[crf]

If the DB thinks the table doesn't exist, then this should have been detected by OfBiz Entity Engine much earlier during the startup, and there should be warnings/errors about it there which may be more informative about the nature of the problem.

I agree with Nic, though – this sort of problem is generally due to permission problems of some kind, often that the user that restored the database is not the same user that JIRA is using to connect to the database and/or that the schema name is set incorrectly.

[Nic Brough -Adaptavist-]

Oh, schema names, I forgot about those.  Thanks Chris!

[amit raj]

Thank you Nic and Chris. your inputs helped to figure out the root cause. Root cause was having two instances of JIRA schemas running on same Database. though this configuration have been running for years. we suddenly started getting errors. we dropped one of the schema and moved to different database that fixed the issue. As Atlassian recommends not to have two JIRA schema on same server.