Last updated on APRIL 16, 2017
Applies to:Oracle Secure Backup - Version: 10.2.0.1 to 10.2.0.2 - Release: 10.2 to 10.2
Information in this document applies to any platform.
Checked for relevance on 29-Jun-2011.
When an issue arises, the first place to begin troubleshooting is the job transcripts / properties and the OSB daemon logs.
Primary Oracle Secure Backup Daemons (Background Processes) and what is in the logs:
Information pertaining to jobs run, log file and transcript cleanup, security messages with regards to certificate signing for hosts, and information regarding the starting of obhttpd and obscheduled services.
Information pertaining to NDMP traffic messages between clients and the hosts acting as a media server.
Information pertaining to verification of user access for SBT backup/restore operations. Indicates which OS user is requesting verification backup/restore operation and if that user is preauthorized for those operations as an OSB user. Information about the import process of data into the sbtpiece catalog after each database backup.
Information pertaining to the import process of file system backup metadata into the backup catalog (indices.cur) that occurs after each file system backup. Startup instances will also be visible anytime a restore or browse operation begins.
Information pertaining to the Web Tool.
Information pertaining to library and drive operations. The detail of this logfile can be increased/decreased by turning debug on/off for a device. Hardware errors are collected in this location as well and are located in the file hardware-errors. In order to view these hardware errors you need to use the obtool dumpdev command.
Information pertaining to the job schedule. However, unless the scheduler encounters an error you will only see what dates the scheduler is currently serving in its log file.
OSB Daemon Logs: Background Processes Rarely Accessed During Troubleshooting
This log will only be present if an error occurred pushing a policy change to daemons within the domain. The error will reference what daemon was unresponsive during the policy change.
This log will only be present if an error occurred attempting to update the scheduler with status of a job. The error will reference which job was attempting to be updated and why the update could not complete.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms