IBM Data Lifecycle - Integration and Governance Connect with experts and peers to elevate technical expertise, solve problems and share insights. Join / Log in
I have an archive request I've built that contains the following tables:TABLE #1 - My start table. This is a DB2 table that has ssn information on it. When the archive runs it typically pulls in roughly one million rows, but that number varies.TABLE #2 - A DB2 table that contains additional PII related to each SSN in TABLE #1. This is the table that rows are archived and deleted from when the archive runs.I have a relationship defined between the two tables based on SSN and two other key index columns that are on both tables.When I run the archive, currently about 1 million rows from TABLE #2 are selected to be archived and deleted. But, because of a short processing window the job is being allotted, I need to limit the number of rows that are selected during each run from TABLE #2.Is there a way to do this? I know there is a row limit that I can declare in the archive request editor, but because the number of rows that are selected from the start table varies that is not working for me. I need to specifically limit the number of rows selected for archival and deletion from TABLE #2.
In the table map definition can you limit the row number for each table in the definition.
Thank you, Mr. Reinaud!! I had never used the Table Map option before. I took a quick look and it looks like I'll be fine now. Thank you again!!!