Troubleshooting
Problem
This document will help you analyze and resolve onbar problems.
Resolving The Problem
Troubleshooting OnBar Archive and Restore
- Learn More
- Collect Data - Archive
- Collect Data - Restore
- Analyzing Data- selected tab,
To investigate the onbar problem you must first collect the troubleshooting data described in one of these Onbar Collecting Data documents:
If you do not understand some of the terms, the format of a Onbar file, or XBSA functions used in this document please click on the Learning More tab above.
How to tell if a problem is caused by Onbar or the Storage Manager
The first step in analyzing an Onbar problem is determining if the problem is caused by Onbar or the Storage Manager (SM).
1. Open both the Onbar activity log (bar_act.log) and the Onbar debug log (bar_debug.log).
2. Find the error in the bar_act.log. Note the values of the first four columns. These will be used in the next step. Here is an example:
2009-05-07 10:41:14 26404 26402 /opt/informix/bin/onbar_d -b -L 0
2009-05-07 10:41:34 26404 26402 Begin level 0 backup rootdbs.
2009-05-07 10:41:34 26404 26402 Successfully connected to Storage Manager.
2009-05-07 10:41:34 26404 26402 XBSA Error (BSACreateObject): A system error occurred. Aborting XBSA session. <-- error
2009-05-07 10:41:46 26404 26402 /opt/informix/bin/onbar_d: process exit 3 (0x03) <-- error
3. Use the value of the first four columns to find the corresponding output in the bar_debug.log for more details about the error:
2009-05-07 10:41:34 26404 26402 BSACreateObject: enter <-- starting point
2009-05-07 10:41:34 26404 26402 BSACreateObject: object owner name createTime
2009-05-07 10:41:34 26404 26402 BSACreateObject: INFORMIX informix /prod /prod/rootdbs 0 0 0 0 0 0
2009-05-07 10:41:34 26404 26402 BSACreateObject: copytype copyid restoreOrder size resource type status desc objectInfo
2009-05-07 10:41:34 26404 26402 BSACreateObject: 3 0 0 0 0 0 52822016 R 4 1
2009-05-07 10:41:34 26404 26402 BSACreateObject: return 3 (0x03) <-- ending point
In this example Onbar runs the XBSA function BSACreateObject. Between the starting point and ending point is the information Onbar is sending to the SM. The SM returns error 0x03. This means there is a problem that must be resolved by a change or a fix on the SM side of this problem. That could mean changing a parameter in a file, setting an environment variable, resolving an error and so on. In this case you would need to look at the SM message and error logs to determine the corrective action.
Here is an example where the fault is on the Onbar side. Here is the bar_act.log:
2009-09-28 09:21:35 544850 483410 /usr2/support/products/sr_11.10.FC1/bin/onbar_d -b -L 0
2009-09-28 09:21:36 544850 483410 Archive started on rootdbs, sblob (Requested Level 0).
2009-09-28 09:21:37 544850 483410 Begin level 0 backup rootdbs.
2009-09-28 09:21:37 544850 483410 Successfully connected to Storage Manager.
544850 483410 (-43080) Process 544850 received signal 3. Process will exit after cleanup.
2009-09-28 09:22:01 544850 483410 /usr2/support/products/sr_11.10.FC1/bin/onbar_d complete, returning 141 (0x8d)
Here is the offending section of the bar_debug.log:
2009-09-28 09:21:49 544850 483410 BSASendData: enter
544850 483410 bar_sighdlr: enter
544850 483410 bar_sighdlr: input signo: 3 <-- error
544850 483410 get_pid: enter
544850 483410 getpid: return 544850 (0x85052)
544850 483410 bar_sighdlr: ccb->exit_sig_received = TRUE
544850 483410 bar_sighdlr: return
2009-09-28 09:21:49 544850 483410 BSASendData: input 4585816880
2009-09-28 09:21:49 544850 483410 BSASendData: input: bufferLen = 61440, numBytes = 61440
2009-09-28 09:21:49 544850 483410 BSASendData: output: bufferLen = 61440, numBytes = 61440
2009-09-28 09:21:49 544850 483410 BSASendData: return 0 (0x00)
2009-09-28 09:21:49 544850 483410 barSendData: return 141 (0x8d) <-- error
In this case Onbar receives a signal 3 while processing a BSASendData function. The function completes successfully indicated by the "return 0". An Onbar function barSendData fails with error 141 or 0x8d. Looking at the Onbar return codes (linked below) you see that 141 means Onbar received an operating system signal and that it is likely the Onbar command was interrupted. Further inspection of signal 3 verifies an interrupt signal was sent to Onbar.
Related Information
[{"Product":{"code":"SSGU8G","label":"Informix Servers"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF022","label":"OS X"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"10.0;11.1;11.5;11.7;11.70;12.1","Edition":"","Line of Business":{"code":"","label":""}}]
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21394008