Running Achilles issue

Developers
1

Hi folks,

A question regarding running achilles:

  1. DB - postgresql
  2. WebAPI, Atlas running well

The question:
When running achilles, I use ‘postgres’ account to run,
and the achilles_ tables’ owner is ‘postgres’.

Since when create the database, the owner is ‘ohdsi_admin_user’,

In inserting the source, i set up using ‘ohdsi_admin_user’ to access the data cmd database;

After running the achilles, I have to manually reset the ‘achilles_’ created tables’ permission.

My question is:

when running achilles, what account I should use so I don’t have manually adjust the newly created achilles tables?

Thanks,
R. Z.

2

At the end of the achilles running, I got this errors,
I appreciate any advice. Thanks.

image
image754×301 9.64 KB

3

Whichever account you run Achilles with will be the one that creates the tables. An alternative would be to set the createTable parameter to FALSE and create the tables ahead of time with a different owner if you preferred to control table ownership in that way.

In the error you’re describing it appears that analysis 1203 failed and caused an issue when merging results. There will be an error in the log for debugging 1203 that would help resolve your issue.

4

Thank you so much Frank!

It turn out 'cdmVersion=‘5.4’ caused this issue in my case. I set it to 'cdmVersion=‘5’ resolved this issue (running many time with different accounts). I am still not sure whether the cdm data was not on cdm5.4. The error message was not very informative.

5

I think I had a similar problem. I ended comparing the tables I got with the specs at:

https://ohdsi.github.io/CommonDataModel/cdm53.html#Clinical_Data_Tables

and later I added the columns or tables that were missing with null values of course (using cdmVersion=5.3). After I did this Achilles run well.

Jose

6

Thank you for the confirmation Jose.

7

I have a similar issue with my cdm 5.4 data. I set to cdmversion=5 as suggested but it gives me these errors.
Error 1203: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name ‘discharge_to_concept_id’.
Error 1900:
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name ‘admitting_source_concept_id’.
Error 2004:
com.microsoft.sqlserver.jdbc.SQLServerException: The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.
In the end, the procedure fails with error
Error:
com.microsoft.sqlserver.jdbc.SQLServerException: Cannot find the object “OMOP.dbo.achilles_results” because it does not exist or you do not have permissions.