PLEASE SUGGEST SOME OPTIMIZER HINTS TO TUNE QUERY

Question

Below is explain plan for query
SELECT STATEMENT  ALL_ROWSCost: 607,111  Bytes: 169  Cardinality: 1                                                         
     18 HASH GROUP BY  Cost: 607,111  Bytes: 169  Cardinality: 1                                                    
          17 FILTER                                               
               14 TABLE ACCESS BY LOCAL INDEX ROWID TABLE GL.GL_JE_LINES Cost: 88  Bytes: 72  Cardinality: 2                                          
                    13 NESTED LOOPS  Cost: 408,270  Bytes: 11,384,009  Cardinality: 67,361                                     
                         10 HASH JOIN RIGHT OUTER  Cost: 11,954  Bytes: 5,578,020  Cardinality: 41,940                                
                              1 TABLE ACCESS FULL TABLE GL.GL_JE_CATEGORIES_TL Cost: 9  Bytes: 7,530  Cardinality: 251                           
                              9 HASH JOIN  Cost: 11,942  Bytes: 4,319,820  Cardinality: 41,940                           
                                   7 MERGE JOIN CARTESIAN  Cost: 4,171  Bytes: 4,233  Cardinality: 51                      
                                        2 TABLE ACCESS FULL TABLE XXFC.XXFC_COMPARATIVO_SD_GL_MAPEO Cost: 27  Bytes: 59,740  Cardinality: 1,030                 
                                        6 BUFFER SORT  Cost: 1.84467440737096E19  Bytes: 1,275  Cardinality: 51                 
                                             5 SORT UNIQUE  Cost: 4  Bytes: 1,275  Cardinality: 51            
                                                  4 TABLE ACCESS BY INDEX ROWID TABLE GL.GL_PERIODS Cost: 4  Bytes: 1,275  Cardinality: 51       
                                                       3 INDEX RANGE SCAN INDEX XXFC.IDX_GL_PERIODS_PORTAL Cost: 1  Cardinality: 51 
                                   8 TABLE ACCESS FULL TABLE GL.GL_CODE_COMBINATIONS Cost: 7,684  Bytes: 45,138,000  Cardinality: 2,256,900                      
                         12 PARTITION RANGE ITERATOR  Cost: 3  Cardinality: 108  Partition #: 15                                
                              11 INDEX RANGE SCAN INDEX GL.GL_JE_LINES_N1 Cost: 3  Cardinality: 108  Partition #: 15                           
               16 TABLE ACCESS BY GLOBAL INDEX ROWID TABLE GL.GL_JE_HEADERS Cost: 3  Bytes: 23  Cardinality: 1  Partition #: 17                                          
                    15 INDEX UNIQUE SCAN INDEX (UNIQUE) GL.GL_JE_HEADERS_U1 Cost: 2  Cardinality: 1                                     

Answer 1

You must provide sufficient information for us to answer your question. Please read Rob Van Wijk's helpful guide on the sort of things we need to know (and incidentally how you can start to solve your problem yourself): [When your query takes too long|http://forums.oracle.com/forums/thread.jspa?threadID=501834&tstart=0]. Randolf Geist has knocked up a [HOW TO: Post a SQL statement tuning request  |http://forums.oracle.com/forums/thread.jspa?threadID=863295] which is a template of the helpful way to layout a tuning question. Also, read [his blog on the topic|http://oracle-randolf.blogspot.com/2009/02/basic-sql-statement-performance.html]
You might also benefit from reading [Tom Kyte’s advice on how to ask questions|http://tkyte.blogspot.com/2005/06/how-to-ask-questions.html].
Cheers, APC
blog: http://radiofreetooting.blogspot.com