In some occasions, the analytics team may need to take specific actions to check or update changes in the datamarts. Examples in which this may happen may include the following:
...
- Log in to your favorite SSH tool (e.g. SecureCRT)
- connect to "analytics" server (command: ssh analytics)
- enter the following: /home/unix/analytics/TigerETL3/runEtlShell.sh
paste & run the etl-command separately for each PDO, changing PDO-12480 to the relevant PDO returned above.
Code Block language scala AnalyticsEtlDB("analytics.tiger.agents.PdoStar.fromSQL", deltaFromSql("""SELECT DISTINCT a.pdo_name||','||a.pdo_sample_id FROM cognos.pdo_star5 a WHERE a.pdo_name = 'PDO-12480'""") flatMap DataSetEtl() flatMap analytics.tiger.agents.PdoStar.pipeline)
The command takes a little while. You'll know it's complete when you get the scala prompt again
...
- Rerun the PDO_STAR query above. This refresh is immediate, so you can run the query right away.
- If it returns nothing, the DM is all set.
- If it still returns records, ensure that that is unexpected behavior and try the refresh again. (occasionally, there are other samples that need to remain with the "old" IDs, as is usually the case in sample swaps)
- If it still returns unexpected records, talk with Nasko.
2.4. Refreshing the ReadgroupMetadata DM in SEQPROD Database
Tip | ||||
---|---|---|---|---|
| ||||
Review Analytics ETL Framework for more details on this section |
...