The datbase schema used by Jira uses several column names and table names that are reserved words in the SQL standard. With a properly configured database-schema.xml file in Orion, this will be resolved in deploy time, but that is not guaranteed to work with all databases. I used our JDBC Validator (that validates all sql sent through a jdbc driver against the SQL-92, SQL-99 and SQL-200x draft) during the deployment and here are my findings: 1. create table Action... Action is a reserved word in SQL-92 and SQL-99. 2. create table Issue... Key (a column) is reserved in SQL-92 and SQL-99. 3. create table Project ... same as 2 4. create table os_PropertyData .. Value is reserved in SQL-92, SQL-99 and SQL-200x 5. create table os_PropertyDate... same as 4. 6. create table os_PropertyDecimal... sames as 4. 7. create table os_PropertyNumber... same as 4. 8. create table os_PropertyString... same as 4. 9. create table os_PropertyEntry... same as 2 All the above reserved words are likely to be reserved in many databases, so it might be a good idea to change them (you can find all the reserved words at http://developer.mimer.se/validator/sql-reserved-words.tml)