BWA-MEM results in "An error occurred setting metadata for this dataset"

i was running wheat genome reference to create BAM file using BWA_MEM . it was running smoothly
but out file was 34.3 MB and the finaly error message was surfaced reading as:
An error occurred setting the metadata for this dataset Set it manually or retry auto-detection

1 Like

A few more details would help, thanks!

  1. Where are you using Galaxy? public URL? your own server (version)?
  2. If your own server, is this the first time you have run BWA-MEM?
  3. Is the wheat genome already indexed or are you using it as a custom genome?
  4. If a custom genome, this the first time you have executed BWA-MEM with it?

How to troubleshoot this type of problem in general

  1. Click on the link inside the dataset to re-detect metadata. In many cases, this will clear up the problem.

  2. Check if the results are empty. Example: BAM results that have no data lines, only header lines.

  • Double check that the intended target genome was actually mapped against. Use the rerun or job details buttons to review the original genome selected, modify if incorrect, and rerun.
  • If using a custom genome, is it formatted correctly?
  • Review quality metrics for fastq inputs with the tool FastQC and address content issues.
  • Review the tool settings and online manuals. Does your data meet the minimum mapping criteria set by the parameters used? Is the tool appropriate for your datatype (spliced versus unspliced)? Adjust as needed. Most tool form options for most Galaxy tools are the same as when using a tool line-command.
  1. Test for server-side problems.
  • Try at least one re-run to see if that resolves the problem (transient server/cluster issues).
  • Is the tool marked as deprecated (public Galaxy server)? If so, choose an alternative tool that is not. See the Galaxy Tutorials if you are not sure of alternatives.
  • Low memory resources (server/cluster that runs the jobs, different from account quota disk space) and related technical issues are possible.
    • When running your own Galaxy, review the admin logs, disk space where you write outputs, etc.
    • When using a public Galaxy server, contact the admins by email or through a bug report. Contact information is usually on the home page of a public server and often also here:
    • Problems at a usegalaxy.* server can be reported at this forum. Specify which server by URL with your question.

Full help: Troubleshooting resources for errors or unexpected results

I am using public URL ,custom wheat genome and and i am usinf BWA MEM first time.
thanks…for ur response

1 Like

Could you share the exact URL for the public server? Thanks!

1 Like

Thanks for clarifying.

I reviewed the datasets with a metadata problem and all looks Ok technically.

Did you try clicking on the link to re-autodetect the metadata? That should be enough to resolve the problem.

That said, I see Stringtie jobs in your history. If the reads are RNA-seq, then you’ll want to use a spliced mapper like HISAT2 (instead of BWA). The custom reference genome also should be reformatted before using it with downstream tools – it contains description line content on the title lines (">" lines) that will cause problems when using it along with the matched reference annotation. Please see the Tutorial and FAQ links above for the how-to for all of this.

Thanks sir. i will try it and update you sir accordingly.

I think as the reference genome of wheat is large genome,so there is memory allocation problem…is any solution to handle wheat genome.

1 Like

I assume this is similar to a problem we’ve recently had: pysam is not able to handle the large chromosomes of wheat. To index the BAM file, it can only handle contigs (chromosomes) of max 512MB. The solution provided by the wheat consortium is that they split the large chromosomes.

1 Like

Agree, the problem is rooted in memory/resource issues.