Log bundles are a group of logs saved to a compressed zip file. Oracle support can use these log bundles to troubleshoot issues with STA.
There are three main log bundle types: RDA, STA database, and library component.
Collect information about the STA server environment, the operating system, and the STA application. You can create RDA logs automatically or manually. STA generates an RDA bundle when STA is restarted or when the password or port change utility is unable to roll back to a previous value.
Oracle support can use RDA log bundles to troubleshoot issues with STA installation and configuration, and server system performance and security. You may want to create an RDA log bundle when:
The STA user interface displays a message indicating you should take a snapshot.
Oracle Service requests that you take a snapshot.
An unexpected STA application event occurs and it appears to be a bug.
A full dump of the STA MySQL database. You can only create these manually.
Oracle Service can use database bundles to troubleshoot issues with the database itself or with the STA application. You can use them to back up the database before an upgrade or to transfer it to another server. Although the dump file is compressed, it can be quite large, depending on the size of your STA database.
Logs for libraries, drives, media, robots, CAPs, PTPs, or elevators. Media bundles can only be created manually. All other library component bundles can be created manually or automatically.
The log bundles include information about component configuration and current top-level condition and health, if available. Also, for drives and media, the bundles include recent exchange history. Oracle support can use these log bundles to troubleshoot issues with individual components monitored by STA.
STA appends log information to a user-assigned prefix name to ensure each bundle has a unique name.
The filename is:
user-assigned_prefix--logtype_component_type-serial_number_timestamp.zip
Where:
user-assigned_prefix — maximum 210 alphanumeric characters or underscores. Multiple consecutive underscores are not valid. Spaces are automatically replaced with underscores. Cannot begin with AUX, CON, NUL, or PRN.
log_type — identifies the type of log bundle. For example, CAP, STA_DBSnapshot.
component_type— identifies the specific type of component, such as ROTATIONAL_CAP, HP_LTO5.
identifier—unique serial number of the hardware component. Does not apply to RDA log bundles.
timestamp—date and time when the log bundle was created.
For example:
NSDB--STA_DBSnapshot-14.4.2017.53.03.26.zip
NSCAP--Cap_CAP-516000100437+1643197981+4_-07.4.2017.51.08.09.zip
STA retains log bundles for 10 days, based on their creation date, then automatically purges them
You can create any number of log bundles. The size and number are limited only by the available disk space on the STA server. Once purged, log bundles no longer appear on the Service–Logs screen. If you want to retain selected bundles for a longer time, you can download them to your local computer within the 10-day period. You can also delete log bundles manually at any time.
See Also:
The location of log bundles depends on the log type and creation method.
Log bundle and database dump creation log directory:
/var/log/tbi/get_sta_db_bundle.log
Application generated RDA and library component log bundle directory:
/Oracle_storage_home/Middleware/rda/snapshots
Command line generated RDA log bundle directory:
/Oracle_storage_home/Middleware/rda/output
Where /Oracle_storage_home is the Oracle storage home location defined during STA installation. See the STA Installation and Configuration Guide for details.