[Info-Ingres] audit trail recovery on a table with blobs

Martin Bowes

unread,

Mar 5, 2010, 4:46:21 AM3/5/10

to Ingres and related product discussion forum

Hi All,

I'm in the wonderful position of needing to do an audit trail based recovery of a data deleted from a table about a month ago. And Yes the base checkpoint is not available. But I still have the journals!

The problem is that when I do:

/dbsystem/II/ingres/bin/auditdb ace_pack_live -b27-Jan-2010:16:15:54 -e27-Jan-2010:16:15:55 -uace -table=gobz -file=ace.gobz.trl

I get a SIGSEGV in the errlog.

bb3.ctsu::[ , 8eb1e200]: Fri Mar 5 09:30:08 2010 Segmentation Violation (SIGSEGV) @PC 0000000000929ed9

RSP 00007fffffa8ba10 RBP 00007fffffa8c210 RSI 00007fffffa8b844

RDI 00002b1799f2a300 RAX 0000000000000000 RBX 00002b1799fb586a

RCX 00007fffffa8b844 RDX 0000000000000000

-----------BEGIN STACK TRACE------------

0: 7fffffa8c210 dmfjsp [0x929ed9] <static function, no info available>

1: 7fffffa9c260 dmfjsp [0x929cae] <static function, no info available>

2: 7fffffadc550 dmfjsp [0x923837] <static function, no info available>

3: 7fffffadc6f0 dmfjsp [0x924a8c] <static function, no info available>

4: 7fffffb115e0 dmfjsp(dmfatp+0xf21) [0x9221b1]( ... )

5: 7fffffb186d0 dmfjsp(dmfjsp_libmain+0x478) [0x57e4e8]( ... )

6: 7fffffb18870 dmfjsp(main+0x6e4) [0x449b6c]( ... )

-----------END STACK TRACE----------

bb3.ctsu.ox.ac.uk ::[II_JSP , 27673 , 00002b178eb1e200]: Fri Mar 5 09:30:08 2010 E_DM904A_FATAL_EXCEPTION A fatal error has occurred in the DMF Facility.

The table in question has 4 long varchars.

When I try the same audit command on a table without long varchars it succeeds.

The installation on which the recovery is being attempted is running: II 9.2.0 (a64.lnx/143)NPTL + p13556.

The installation on which the journals were written is running: II 9.2.0 (a64.lnx/143)NPTL + p13695

Is it possible to do an audit trail recovery on tables with long varchars?

Marty

Ingres Forums

unread,

Mar 5, 2010, 11:07:33 AM3/5/10

to

Hi Marty

One thing is for sure, you should not be hitting a SEGV. That's a bug
a should be logged in a Service Desk issue.

Alex

--
hanal04
------------------------------------------------------------------------
hanal04's Profile: http://community.ingres.com/forum/member.php?userid=443
View this thread: http://community.ingres.com/forum/showthread.php?t=11734

Ingres Forums

unread,

Mar 5, 2010, 3:49:48 PM3/5/10

to

Hi Marty,

I have the exact same problem on II 9.1.1 (axm.vms/104) p13401.

E_DM9049_UNKNOWN_EXCEPTION An Unexpected Exception occurred in the
DMF Facility, exception number 12.

E_DM904A_FATAL_EXCEPTION A fatal error has occurred in the DMF
Facility.

Do you happen to have XML stored in those long varchars ?

Francois

--
francois.d...@ssq.ca
------------------------------------------------------------------------
francois.d...@ssq.ca's Profile: http://community.ingres.com/forum/member.php?userid=3420

Martin Bowes

unread,

Mar 9, 2010, 10:18:47 AM3/9/10

to Ingres and related product discussion forum

Hi Francois,

I've finally managed to construct a reliable test case...see attached.

The critical feature is the RFP which acts on the delete.

Once that's in place the SIGSEGV is on the auditdb -table -file is
certain.

Marty

Hi Marty,

Francois

_______________________________________________
Info-Ingres mailing list
Info-...@kettleriverconsulting.com
http://ext-cando.kettleriverconsulting.com/mailman/listinfo/info-ingres

README