search

aodn / content

Tracks AODN Portal content and configuration issues
0 stars 0 forks source link

reporting db blocks harvester/pipeline #405

Closed lbesnard closed 2 years ago

lbesnard commented 5 years ago

The reporting database is blocking a liquibase change in the SOOP TMV pipeline. This means the pipelines can't run.

This is an ongoing issue with the reporting db. While xav is away, I don't know who can fix it. @ggalibert ?

SEVERE 2/25/19 12:19 PM:liquibase: Change Set changelog.xml::soop_tmv_trajectory_map::talend failed.  Error: Error executing SQL DROP VIEW IF EXISTS soop_tmv_trajectory_map: ERROR: cannot drop view soop_tmv_trajectory_map because other ob
jects depend on it
  Detail: view reporting.soop_all_deployments_view depends on view soop_tmv_trajectory_map
view reporting.soop_data_summary_view depends on view reporting.soop_all_deployments_view
bpasquer commented 5 years ago

This is an issue that has been mentioned as part of the PO's workflow review, but has not been addressed yet. You can ask Leigh to drop the view( He did it for me few weeks ago with SOOP-BA)

mhidas commented 5 years ago

Why do those views even need to be there all the time? I thought they were only used once a month when Jacqui creates the reports. Can't they just be removed as soon as she's done?

jachope commented 5 years ago

@mhidas agreed they are only required for one day a month. Xav (or Seb) runs then one evening at an agreed date and the next day I complete all the reporting. Other than that don't believe they are required? @smancini ?

ggalibert commented 5 years ago

Instead of creating a view, I believe we could just run an SQL query to produce the table required for reporting.