Unable to create MV in Oracle 9i, but works in 10g

Question

For what ever reason, we are developing in Oracle 10g, but production implementation will be in Oracle 9i. I was able to successfully create this MV using the FAST REFRESH ON COMMIT option in 10g, but received a ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view, when attempting to create it in 9i. I've followed Oracle's documentation on the restrictions for creating Fast Refresh MV's in 9i, and it appears all conditions have been met. The DBA has yet to grant me execute on the DBMS_MVIEW.EXPLAIN_MVIEW package and SELECT privilege on MV_CAPABILITIES_TABLE, so I don't know what could be wrong. Any ideas?
create materialized view log on tb_slea_eligible_emp
with sequence, rowid INCLUDING new values;
create materialized view log on tb_slea_election
with sequence, rowid INCLUDING new values;
create materialized view log on tb_slea_recclub_award
with sequence, rowid INCLUDING new values;
create materialized view log on tb_slea_initiation
with sequence, rowid INCLUDING new values;
DROP MATERIALIZED VIEW MV_SLEA_CONTRIBUTION;
CREATE MATERIALIZED VIEW MV_SLEA_CONTRIBUTION
BUILD IMMEDIATE
REFRESH FAST ON COMMIT
WITH PRIMARY KEY
AS
SELECT emp.slea_year,
       emp.empid,
       NVL (t1.original_bal, 0) recclub_amt,
       NVL (t2.initiation_amt, 0) initiation_amt,
       (NVL (t1.original_bal, 0) + NVL (t2.initiation_amt, 0)) firm_funded_amt,
       NVL (elect.slea_min_amt, 0) slea_min_amt,
       elect.slea_add_amt,
       NVL (elect.slea_fullyr_amt, 0) slea_fullyr_amt,
       (NVL (t1.original_bal, 0) + NVL (t2.initiation_amt, 0) + NVL (elect.slea_fullyr_amt, 0)) total_acct,
       emp.ROWID elig_emp_rowid,
       elect.ROWID election_rowid,
       t1.ROWID recclub_rowid,
       t2.ROWID initiation_rowid
  FROM tb_slea_eligible_emp emp,
       tb_slea_election elect,
       (SELECT ROWID, empid, original_bal
          FROM tb_slea_recclub_award
         WHERE slea_year = 2007 
           AND record_type = 'C') t1,
        (SELECT ROWID, empid, initiation_amt
          FROM tb_slea_initiation
         WHERE slea_year = 2007 ) t2
WHERE emp.empid = elect.empid
   AND emp.slea_year = 2007
   AND emp.empid = t1.empid(+)
   AND emp.empid = t2.empid(+)
   AND emp.slea_year = elect.slea_year
   AND emp.eligible_ind = 'Y'
   AND elect.record_type = 'C';
CREATE INDEX MV_SLEA_CONTRIB_IDX1 ON MV_SLEA_CONTRIBUTION
(elig_emp_rowid);
CREATE INDEX MV_SLEA_CONTRIB_IDX2 ON MV_SLEA_CONTRIBUTION
(election_rowid);
CREATE INDEX MV_SLEA_CONTRIB_IDX3 ON MV_SLEA_CONTRIBUTION
(recclub_rowid);
CREATE INDEX MV_SLEA_CONTRIB_IDX4 ON MV_SLEA_CONTRIBUTION
(initiation_rowid);

Answer 1

Yes, it boggles me as to why production is a STEP DOWN from development environment. Probably because there are like 20 other applications still on the production database that are not ready to upgrade to 10g...nevermind being ready for 11g!
I went through the compatibility checklist, but I still don't understand what can be wrong. I was hoping that maybe someone else has gone through MV incompatibility between 10g and 9i that could share their experience.