ixbar file layout. IDS 7.31.FC6x2 on Solaris 2.7

Hi, Anybody intimately familiar with the ixbar (onbar emergency boot file) file layout? I am IDS 7.31.FC6x2 on Solaris 2.7 using Veritas Netbackup as my onbar partner. There was a problem with the netbackup server last night. When the problem was fixed (server reboot), the handshake from my database to the netbackup server started working again. My onbar logical log backup was aborting during the netbackup server problem. Once the handshake was restored, onbar started backing up the logical logs again. the first log (940776) that failed to back up when the problem hit, did back up this morning as noted in the online.log. However in ixbar, the log backup for this log did not show up in numerical/time sequence order which is the norm in the ixbar file. Also the ixbar file fields for this log are not the 'norm', plus this log backup does not appear in the sysutils bar_* tables. I may or may not have an opportunity to test what would happen if I tried to restore this logical log. Below are sample ixbar records from my system. the first and last records indicate successful backups (properly recorded in systutils and ixbar), the second entry is the 940776 goofy log. Notice the difference in records is that log 940776 has a "0" in the last field, whereas the others do not. Anyone have a clue what that last field is for and if it is important to any restore? (yes, my example does not show 940776 out of order, but it's just my example)... --------------- ixbar records ----------------- sapdbfprdshm 940775 L 0 207460 0 0 1069211298 2003-11-18 21:08:15 1 0 0 207460 sapdbfprdshm 940776 L 0 207569 0 0 1069251528 2003-11-19 08:18:08 1 0 0 0 sapdbfprdshm 940936 L 0 207729 0 0 1069254489 2003-11-19 09:08:06 1 0 0 207729 ------------------------------------------------ thanks, Norma Jean ----------------------------------------- ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================

Hi, The last field is "required action id" (column 13). For logical log backups "required action id" is same as "action id" field (column 5). The "required action id" is associated with incremental backups. Since, there are no incremental logical log backups, this field is not used for logical log backup objects. So, restore should be fine. Thanks, Paresh. --------------- ixbar records ----------------- sapdbfprdshm 940775 L 0 207460 0 0 1069211298 2003-11-18 21:08:15 1 0 0 207460 sapdbfprdshm 940776 L 0 207569 0 0 1069251528 2003-11-19 08:18:08 1 0 0 0 sapdbfprdshm 940936 L 0 207729 0 0 1069254489 2003-11-19 09:08:06 1 0 0 207729 ------------------------------------------------ "NormaJean.S...." <NormaJean.Sebastian@t To: ids@iiug.org ellabs.com> cc: Sent by: Subject: ixbar file layout. IDS 7.31.FC6x2 on Solaris 2.7 [2196] forum.subscriber@iiug. org 11/19/2003 11:29 AM Hi, Anybody intimately familiar with the ixbar (onbar emergency boot file) file layout? I am IDS 7.31.FC6x2 on Solaris 2.7 using Veritas Netbackup as my onbar partner. There was a problem with the netbackup server last night. When the problem was fixed (server reboot), the handshake from my database to the netbackup server started working again. My onbar logical log backup was aborting during the netbackup server problem. Once the handshake was restored, onbar started backing up the logical logs again. the first log (940776) that failed to back up when the problem hit, did back up this morning as noted in the online.log. However in ixbar, the log backup for this log did not show up in numerical/time sequence order which is the norm in the ixbar file. Also the ixbar file fields for this log are not the 'norm', plus this log backup does not appear in the sysutils bar_* tables. I may or may not have an opportunity to test what would happen if I tried to restore this logical log. Below are sample ixbar records from my system. the first and last records indicate successful backups (properly recorded in systutils and ixbar), the second entry is the 940776 goofy log. Notice the difference in records is that log 940776 has a "0" in the last field, whereas the others do not. Anyone have a clue what that last field is for and if it is important to any restore? (yes, my example does not show 940776 out of order, but it's just my example)... --------------- ixbar records ----------------- sapdbfprdshm 940775 L 0 207460 0 0 1069211298 2003-11-18 21:08:15 1 0 0 207460 sapdbfprdshm 940776 L 0 207569 0 0 1069251528 2003-11-19 08:18:08 1 0 0 0 sapdbfprdshm 940936 L 0 207729 0 0 1069254489 2003-11-19 09:08:06 1 0 0 207729 ------------------------------------------------ thanks, Norma Jean ----------------------------------------- ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================