Why it is not using PARALLEL hint with only this query?

[tamilselvan]

Add a hint /*+ INDEX(GLCC) */ and post the explain plan here.

Tamil

[pando]

pobably resource manager is on

[samdba]

Originally posted by tamilselvan
Add a hint /*+ INDEX(GLCC) */ and post the explain plan here.

Tamil

Here it is. Pl. note that cost has increased 3 folds.

Operation Object Name Rows Bytes Cost Object Node In/Out PStart PStop

SELECT STATEMENT Hint=CHOOSE 1 10084
NESTED LOOPS 1 145 10084
HASH JOIN 1 134 10082
TABLE ACCESS FULL GL_PERIODS 260 4 K 4
NESTED LOOPS 227 25 K 10077
NESTED LOOPS 226 17 K 7365
NESTED LOOPS 3 144 15
HASH JOIN 1 27 14
TABLE ACCESS FULL FND_FLEX_HIERARCHIES_TL 34 374 5
TABLE ACCESS BY INDEX ROWID FND_FLEX_VALUES 87 1 K 8
INDEX RANGE SCAN FND_FLEX_VALUES_N3 87 1
INDEX RANGE SCAN FND_FLEX_VALUE_HIERARCHIES_N1 335 6 K 1
TABLE ACCESS BY INDEX ROWID GL_CODE_COMBINATIONS 30 K 884 K 2450
INDEX RANGE SCAN GL_CODE_COMBINATIONS_N2 30 K 29
TABLE ACCESS BY INDEX ROWID GL_JE_LINES 30 K 1 M 12
INDEX RANGE SCAN GL_JE_LINES_N1 30 K 2
TABLE ACCESS BY INDEX ROWID GL_JE_HEADERS 150 K 1 M 2
INDEX UNIQUE SCAN GL_JE_HEADERS_U1 150 K 1

Thanks,

[tamilselvan]

I never tune a query by seeing the cost. I don't care about it b/c of the bugs invloved in the CBO.

I tune queries by reducing the LOG IOs only.

After adding the hint, Does the total logical IOs come down or increase?

Tamil