Problems with Partition pruning using LIST option in 9i

Question

I am declaring the following partitions on a fact table and when
I do an explain plan on the following SELECT statements it is
doing a full table scan on the fact table. However if I use
the "PARTITION" statement in the FROM clause it picks up the
correct partition and runs great. I have used the analyze
command and dbms_utility.analyze_schema command on all tables
and indexes. I had simaliar problems when partitioning with the
RANGE options too. I have looked through all of the INIT file
parameters and don't see anything obvious. Is there something I
am missing?
Any help would be appreciated!
Thanks,
Bryan
Facttable create statement....
CREATE TABLE FactTable (
ProductGID INTEGER NULL,
CustomerGID INTEGER NULL,
OrganizationGID INTEGER NULL,
TimeGID INTEGER NULL,
FactValue NUMBER NOT NULL,
ModDate DATE NULL,
CombinedGID INTEGER NOT NULL)
PARTITION BY LIST (CombinedGID)
(PARTITION sales1 VALUES(9999101),
PARTITION sales2 VALUES(9999102),
PARTITION sales3 VALUES(9999103),
PARTITION model1 VALUES(9999204),
PARTITION model2 VALUES(9999205),
PARTITION model3 VALUES(9999206));
Select statement....that is causing a full table scan.....the
*tc tables are the equivelent to dimension tables in a star
schema.
SELECT tco.parentgid, tcc.parentgid, tcp.parentgid, sum
(factvalue)
FROM facttable f, custtc tcc, timetc tct, prodtc tcp, orgtc tco
WHERE
tco.childgid = f.organizationgid
AND tco.parentgid = 18262
AND tcc.childgid = f.customergid
AND tcc.parentmembertypegid = 16
AND tcp.childgid = f.productgid
AND tcp.parentmembertypegid = 7
AND tct.childgid = f.timegid
AND tct.parentgid = 1009
GROUP BY tco.parentgid, tcc.parentgid, tcp.parentgid;
Select statement that works great....
SELECT tco.parentgid, tcc.parentgid, tcp.parentgid, sum
(factvalue)
FROM facttable partition(sales1) f, custtc tcc, timetc tct,
prodtc tcp, orgtc tco
WHERE
tco.childgid = f.organizationgid
AND tco.parentgid = 18262
AND tcc.childgid = f.customergid
AND tcc.parentmembertypegid = 16
AND tcp.childgid = f.productgid
AND tcp.parentmembertypegid = 7
AND tct.childgid = f.timegid
AND tct.parentgid = 1009
GROUP BY tco.parentgid, tcc.parentgid, tcp.parentgid;

Answer 1

Hi Hoek,
the DB version is 10.2 (italian version, then SET is correct).
...there's something strange: now I can INSERT rows but I can't update them!
I'm using this command string:
UPDATE TW_E_CUSTOMER_UNIFIED SET END_VALIDITY_DATE = TO_DATE('09-SET-09', 'DD-MON-RR') WHERE
id_customer_unified = '123' and start_validity_date = TO_DATE('09-SET-09', 'DD-MON-RR');
And this is the error:
Error SQL: ORA-14402: updating partition key column would cause a partition change
14402. 00000 - "updating partition key column would cause a partition change"
*Cause:    An UPDATE statement attempted to change the value of a partition
key column causing migration of the row to another partition
*Action:   Do not attempt to update a partition key column or make sure that
the new partition key is within the range containing the old
partition key.
I think that is impossible to use a PARTITION/SUBPARTITION like that: in fact the update of "END_VALIDITY_DATE" cause a partition change.
Do u agree or it's possible an update on a field that implies a partition change?
Regards Steve