Maybe very silly question abou Log Miner

I'm trying to use Log Miner as some kind of audit technology. Original idea was to take archived redologs and read them on other dedicated database. However, I cannot overcome one single problem, which I know from beginning of my logmining in 8.1.6. Problem is that keys used for identifiing row to be updated (in where conditions) are ommited and instead of this in sql_redo from v$logmnr_contents are used rowids. Example of original insert:

update log_test set text3 = 'some new value' where id = 777;

and INSERT from v$logmnr_contents:

update "BOLEK"."LOG_TEST" set "TEXT3" = 'some new value' where "TEXT3" = 'some old value' and ROWID = 'AAAFrVAABAAAHrKAAC';

I knew that this is the format of logminer output, but it still puzzles me if there is no other way to find a key used for original update. With this is logmining in any other database then the original one unusable from audit point of view. For auditing, I need to know exactly which row was updated.
Is there any way to accomplish this, or is this just a limitation that logminer has and there is nothing to do with?

Thanks for your answers

--
_________________________________________

Dusan Bolek, Ing.
Oracle team leader

Note: pagesflames_at_usa.net has been cancelled due to changes (maybe we
can call it an overture to bankruptcy) on that server. I'm still using
this email to prevent SPAM. Maybe one day I will change it and have a
proper mail even for news, but right now I can be reached by this
email.