Quey Tuning
Below is the execution plan for a quey, when I see the below plan, uses Hash Join (I guess FTS which is a bad plan)
Need you help to tune this query
Execution Plan
----------------------------------------------------------
Plan hash value: 3159819237
-------------------------------------------------------------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time |
-------------------------------------------------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 1 | 416 | | 13448 (4)| 00:03:34 |
|* 1 | FILTER | | | | | | |
| 2 | HASH GROUP BY | | 1 | 416 | | 13448 (4)| 00:03:34 |
|* 3 | HASH JOIN | | 1564 | 635K| | 13447 (4)| 00:03:34 |
|* 4 | HASH JOIN | | 1564 | 531K| | 12042 (3)| 00:03:12 |
|* 5 | HASH JOIN | | 1564 | 433K| | 9411 (3)| 00:02:30 |
| 6 | TABLE ACCESS FULL | HOST_CLIENT_LIST_LKP | 629 | 10693 | | 3 (0)| 00:00:01 |
|* 7 | HASH JOIN | | 1564 | 407K| | 9407 (3)| 00:02:30 |
|* 8 | TABLE ACCESS FULL | DOCUMENT_CODES_LKP | 318 | 6360 | | 2 (0)| 00:00:01 |
|* 9 | HASH JOIN | | 4841 | 1167K| | 9405 (3)| 00:02:30 |
|* 10 | HASH JOIN | | 4841 | 822K| | 6325 (3)| 00:01:41 |
|* 11 | TABLE ACCESS FULL | REPO_REMARKETING | 9093 | 257K| | 1060 (4)| 00:00:17 |
|* 12 | HASH JOIN | | 37986 | 5378K| 3560K| 5264 (3)| 00:01:24 |
|* 13 | TABLE ACCESS FULL | CUST_ACCT | 71363 | 2717K| | 2414 (3)| 00:00:39 |