Bogus data from collection in 3.1

Question

Hello-
My college recently upgraded from version 2.2 to 3.1. After exporting/importing my applications to the new environment, we started experiencing problems where there were none before. The primary problem has to do with inaccurate data being returned from a collection. I can currently still run the same page in both environments and even though the collection is pulling from the same production table... they are returinng different data. Thinking the problem may have been the result of the export/import, I tried creating the same page from scratch by copy/pasting the code from 2.2 into 3.1; this, however, did not resolve the problem. I've also copy/pasted the code from my create collection statement (based on a query) into SQL workshop... there it worked fine. Any suggestions how I might debug a problem such as this?
The other problem we're having in 3.1 is that some pages are now timing out. These pages ran long in 2.2 but did successfully return output. Any suggestions on this would also be appreciated.
Thanks.
Don

Answer 1

Hi John-
First-off, thanks for your response. Here's my create collection code:
=====================================================================
APEX_COLLECTION.DELETE_ALL_COLLECTIONS;
APEX_COLLECTION.CREATE_COLLECTION_FROM_QUERY_B(
p_collection_name => 'INPROG',
p_query => 'select sfrstcr_pidm, sum(NVL(sfrstcr_credit_hr,0))
from sfrstcr
where sfrstcr_rsts_code in (''RE'',''NG'')
and sfrstcr_term_code = v(''P2_TERM'')
and NVL(sfrstcr_credit_hr,0) > 0
and sfrstcr_levl_code <> ''09''
and exists
(select ''x'' from ssbsect
where ssbsect_term_code = sfrstcr_term_code
and ssbsect_crn = sfrstcr_crn
and exists
(select ''x'' from sobptrm
where sobptrm_term_code = ssbsect_term_code
and sobptrm_ptrm_code = ssbsect_ptrm_code
and trunc(sysdate) >= trunc(sobptrm_start_date)))
group by sfrstcr_pidm');
APEX_COLLECTION.CREATE_COLLECTION_FROM_QUERY_B(
p_collection_name => 'OUTPROG',
p_query => 'select sfrstcr_pidm, sum(NVL(sfrstcr_credit_hr,0))
from sfrstcr
where sfrstcr_rsts_code in (''RE'',''NG'')
and sfrstcr_term_code = v(''P2_TERM'')
and NVL(sfrstcr_credit_hr,0) > 0
and sfrstcr_levl_code <> ''09''
and exists
(select ''x'' from ssbsect
where ssbsect_term_code = sfrstcr_term_code
and ssbsect_crn = sfrstcr_crn
and exists
(select ''x'' from sobptrm
where sobptrm_term_code = ssbsect_term_code
and sobptrm_ptrm_code = ssbsect_ptrm_code
and trunc(sysdate) < trunc(sobptrm_start_date)))
group by sfrstcr_pidm');
==============================================================
Here's some sample output. The errant data is coming from my OUTPROG collection ('credits not in progress' column). As you can see, in 2.2 there are no credits not in progress for these 3 records... which is correct. It "appears" the credits from my INPROG collection ('credits in progress") are somehow making their way to the OUTPROG column. This pattern, for the most part, hold true... there are, however, exceptions. (I hate exceptions)
Version 3.1
Crn     Course Credits     Course Start Date     DC Date     Credits in Progress     Credits Not In Progress     
30329     4     18-Apr-09     24-Apr-09     24     24     
30329     4     18-Apr-09     24-Apr-09 4     4
30329     4     18-Apr-09     24-Apr-09     8     8
Version 2.2
30329     4     18-Apr-09     24-Apr-09     24          
30329     4     18-Apr-09     24-Apr-09     4          
30329     4     18-Apr-09     24-Apr-09     8