An upload accepts a single trace, compressed or not, a package with several files, and also a whole folder. The format is recognized by the file content, not by the extension in the name. This page shows how many analyses each case becomes and what is left out.
Accepted formats
| Format | Example | What it becomes |
|---|---|---|
| Text | ORCL1_ora_4242.trc | One analysis. |
| gzip or bzip2 | .trc.gz, .trc.bz2 | One analysis. The server reads the trace as a stream, without writing the decompressed version. |
| zip | traces.zip | One analysis per file inside. |
| tar, plain or compressed | .tar, .tar.gz, .tgz, .tar.bz2 | One analysis per file inside. |
Other formats, such as 7z, rar and xz, are not opened, and the analysis ends with an error. With Analyze together, everything in one upload becomes a single analysis (analyze together). For a large trace, compressing reduces the upload, which has a size limit (limits).
Whole folder
In the console, use Choose folder or drag the folder to Drag the traces here; in the app, use Choose folder. The files in the folder and its subfolders go in, with no limit on files per upload, with these exceptions:
- the .trm files;
- hidden files, whose name starts with a dot, and the
__MACOSXfolder; - empty files.
Each remaining file becomes an analysis, and they all have to fit in your limits of queued and stored analyses. In the app, reading the folder stops at 20,000 files.
.trm files
Next to each .trc, Oracle may write a .trm with the same name, with metadata about the trace structure, which ADR uses for search and navigation. It is not a trace. The page, the app, the API and the zip and tar reader leave .trm files out, and the page says how many were left out, as in 2 .trm files are left out (they are not traces).
One analysis per file in the zip or tar
Without Analyze together, each file inside the zip or tar becomes an analysis, with the package name in front, as in traces.zip / ORCL1_ora_4242.trc. When reading the package:
- empty files are left out, and identical files go in only once;
- files your account has already analyzed are not processed again (repeated upload);
- the package can have up to 20,000 files.
If the package has more than one trace, the page and the app first ask whether they are from the same process. After the upload, the page goes back to the Analyses list, because the package becomes several analyses. If they do not fit in your limits, the package analysis ends with an error and suggests uploading again with Analyze together checked.
Compressed file inside a compressed file
A zip or tar inside another zip or tar is not opened. It becomes an analysis with an error: zip or tar inside another compressed file is not opened; upload it separately. A .gz or .bz2 inside the package is read normally.
With Analyze together, a tar inside a zip is opened, at that level only, and several zips uploaded together become a single collection. A zip inside another zip is left out of the collection, with a warning in the report.
File that is not a trace
- A file that is not an Oracle trace ends with the error the file does not look like an Oracle trace (event 10046).
- Other Oracle files are recognized and rejected with their type and the command to generate the 10046: the optimizer trace (10053), the incident trace (ORA-00600 or ORA-07445), the state dump or hanganalyze dump and the alert log.
- In a collection, a file that is not a trace is left out, with a warning that ends in does not look like an Oracle trace and was left out of the collection. If no file is a trace, the analysis ends with an error.
The analysis with an error stays in History with the reason and counts toward the stored analyses limit until you delete it. The uploaded file has already been deleted: fix it and upload again.
Where to go next
- To upload: through the browser or with the Android app.
- To combine the files of one operation: analyze together.
- For the numbers of each limit: limits and repeated upload.