Automatic SQL Cursor Invalidation and Execution

Is there a way to handle automatic cursor invalidation?

We have a process called LIQUIDITY_GENERATION that inserts into a large sub-partitioned table, A_large . The LIQUIDITY_GENERATION process has one INSERT/SELECT(parallel 4) statement that joins to five different sub-partitioned tables, B_large, C_large, D_large, E_small and F_small. This process used to run in 20 minutes till December last year.

A new project, GAP ANALYSIS released in January started inserting data into few of the sub-partitioned tables [ B_large, C_large and D_large] used by LIQUIDITY_GENERATION. The data inserted by the new project is not currently selected by the process, LIQUIDITY_GENERATION.