| Gliffy | ||
|---|---|---|
|
...
Issue/Error: Once a week (1am on Fri) PdoStar5 goes through 1y-refresh. Sometime you might want to trigger it earlier.
Diagnosis:
Remedy: Connect to "analytics" server using your favorite SSH tool and run the following line:
...
INSERT INTO pdo_star_interesting_products values('P-123456');
Note: Create Also create new JIRA RPT ticket (MM add more info?)and assign to raymond to track the following: Assign PdM-approved minimum requirement(s) for coverage met. pdo_star5_aux will need product_goal assigned as well as sample_coverage_normalized and sample_coverage_unformatted set. DCFM_RULES must be updated. DCFM_Agent may need to be updated. PDO_SEQ_STAR needs "Sample Coverage" calculated field updated.
Issue: Missing BAM file path in PDO Tracker or WGS/WES Project Tracker report (PDO_STAR5_Aux DM) (for on-prem only)
...
Remedy: Contact Tammy, Andrew B. , Mike DaSilva or John W. to clear the bad run from their dashboard. Designation ETL will recover as soon as the run is cleared.
Issue: Scala ETL ERROR: analytics.etl.DeckEventAgent$ (Most likely 'lcSet' tag is missing)
Diagnosis: Sometimes this Squid web-service returns no LcSet. Comment about this incident is automatically posted in IPI-61224 and ticket reopened.
Remedy: Just follow up with LIMS team. Our DeckEventAgent will catch up as soon as LIMS service is fixed. No other intervention is needed.
Issue: analytics.etl.PkViolationWarning. unique constraint (COGNOS.RGHQS_METADATA_PK) violated
Diagnosis: This happens when 2+ readgroups having same (fc, lane, mol_index) try to get into datamart. Picard calls it "CLASH". RunMercuryAgent would ignore abusing readgroups and move on with the rest of 'good' ones. Email would give you detailed troubleshooting info.
Remedy: There isn't much for us to do. If upstream issues are resolved you can request a ReadgroupMetadata refresh for the whole run/fc (see above). You can search for the RG in GPINFOJIRA by searching the FC ID to see if it has been blacklisted and already handled upstream.
Issue/Error: ETL: DB error, server: (thorium or vorarestore), Error: ORA-12008: error in materialized view refresh path, ORA-25153: Temporary Tablespace is Empty
Diagnosis: This happens when the DB team is doing some kind of backup or transfer.
Remedy: These errors can be ignored. Everything is actually fine.
...