Lengthy Crosstab reports fail

[unknown]

We have a few crosstab reports that use a number array
(study.study_id) for a Retrieval Argument. When watching
the reports run in Infomaker, approximately 36,540 rows are
returned and then the reports start to build the crosstab.
But, before any of these reports are displayed, Infomaker
shuts down.

We have done significant testing on one of the reports.
One thing that works is simply switching the Retrieval
Argument to a different number array (sample.sample_id) and
entering in all of the sample_ids (180 of them for this
report) individually. No other changes were made to the SQL
or report formatting. The report then runs without error.
While this works, the users do not want to have to go into
the application and select all the individual samples. They
want to run the report on the study, which is a natural
(default) grouping.

Running the failing crosstab report as a tabular report runs
correctly but this will require reconfiguration of several
reports and may not work for all of the reports in question.

Any ideas for how we can get this report format to
consistently work with study.study_id as the Retrieval
Argument?
We are running 10.2.1 Build 9004.
Thanks,

[John Olson [Team Sybase]]

Scott,

What do you mean by switching it "to a different number array"? It sounds
like you're still passing a number array with the same number of values. I
must be missing something in your explanation else I'd say just use the
array that works and put the numbers you want in it.

I have run into problems before passing long arrays as an argument. 180
items for a number array argument is long. Could you instead do a join on a
table that would provide those IDs?

Regards,
John

Post by unknown
We have a few crosstab reports that use a number array
(study.study_id) for a Retrieval Argument. When watching
the reports run in Infomaker, approximately 36,540 rows are
returned and then the reports start to build the crosstab.
But, before any of these reports are displayed, Infomaker
shuts down.
We have done significant testing on one of the reports.
One thing that works is simply switching the Retrieval
Argument to a different number array (sample.sample_id) and
entering in all of the sample_ids (180 of them for this
report) individually. No other changes were made to the SQL
or report formatting. The report then runs without error.
While this works, the users do not want to have to go into
the application and select all the individual samples. They
want to run the report on the study, which is a natural
(default) grouping.
Running the failing crosstab report as a tabular report runs
correctly but this will require reconfiguration of several
reports and may not work for all of the reports in question.
Any ideas for how we can get this report format to
consistently work with study.study_id as the Retrieval
Argument?
We are running 10.2.1 Build 9004.
Thanks,

[unknown]

John,
In this schema, if sdg.sdg_id is used, there is only one
item (one sdg_id) needed to pull all the subordinate records
associated with it (all samples, aliquots, tests, and
results.

Using number array as an argument type has always been a
requirement for our application, so number array is used
even when there is only goin g to be one argument.

So, in this case, it's a question of entering one sdg_id, or
(up to) perhaps 180 sample.sample_ids associated with that
one sdg_id.

Does that help?
Scott,

Post by John Olson [Team Sybase]
What do you mean by switching it "to a different number
array"? It sounds like you're still passing a number
array with the same number of values. I must be missing
something in your explanation else I'd say just use the
array that works and put the numbers you want in it.
I have run into problems before passing long arrays as an
argument. 180 items for a number array argument is long.
Could you instead do a join on a table that would provide
those IDs?
Regards,
John

Post by unknown
crosstab reports that use a number array
(study.study_id) for a Retrieval Argument. When

watching the reports run in Infomaker, approximately

Post by unknown
36,540 rows are returned and then the reports start to
build the crosstab. But, before any of these reports are
displayed, Infomaker shuts down.
We have done significant testing on one of the reports.
One thing that works is simply switching the Retrieval
Argument to a different number array (sample.sample_id)
and entering in all of the sample_ids (180 of them for
this report) individually. No other changes were made
to the SQL or report formatting. The report then runs
without error. While this works, the users do not want
to have to go into the application and select all the
individual samples. They want to run the report on the
study, which is a natural (default) grouping.
Running the failing crosstab report as a tabular report
runs correctly but this will require reconfiguration of
several reports and may not work for all of the reports

in question. >

Post by unknown
Any ideas for how we can get this report format to
consistently work with study.study_id as the Retrieval
Argument?
We are running 10.2.1 Build 9004.
Thanks,