Filter by partition number and partioning key together in LAT

The scenario which I am working on is to retrieve a LOB which was created and deleted the same day, which means it doesn't have any entry in any of the backups. I am using OBJECT FILTERS-ADVANCED for giving table name, column name(Partitioning key) and its value. But this way the job is going through the BACKUPS of all the partitions (37 in my case right now) and taking whole day to finish.

If I add OBJECT FILTERS-BY NAME and give just the partition number, it fetches all the data inserted/updated and ignore the OBJECT_FILTER-ADVANCE values.

Is there a way I can search a particular partition with a partitioning key value ?

There is a case open with IBM,TS021528850, which can give you the job logs of the reruns of my job. Though all of them are abending, it still gives an idea of the time taken for each job before it abends. There are few with OBJECT FILTERS-BY NAME and few with OBJECT_FILTER-ADVANCE to compare.

This is the idea I propose:

1. Give us combined option of Partition number and Partitioning key column value, so the tool doesn't search for all other partitions when we know data is only in one partition.

Benefit :

1. This change will reduce job run time drastically. The jobs with filter by value takes 7-8 hours to complete while the job with partition takes hardly an hour.

Impact : We are getting requests to restore deleted documents. If the deleted documents have entry in backup, I can recover them using Redirected Recovery of that partition. But if the document was inserted and row updated to delete the LOB, I have to use LAT for REDO statement. That's where this combination will help us to get the data recovered and restored fast.

Workaround : I don't have any workaround. My jobs are right now creating B37( CASE-TS021528850), but even the rerun to recreate the issue takes a whole day. We have to tell users that we cannot restore the document, which is not something we want to do.