APEX

Matt,

Can you show us the definition of the tabular form? Also, how many rows are you showing at a time?

Sergio

The page is configured to show 500 rows, but I think there are less than that in the underlying table. How can I show you the definition of the tabular form? Do I just export the page or do you want the sql from "Region Source"?

Thanks.

Matt

The SQL from the region source would be useful.

Sergio

Here it is:

select
"ORIGINAL_VALUE",
"OBS_GROUP_NAME",
"MAPPED_VALUE",
"MAPPING_STATUS"
from "ETL_MAPPED_OBS_VALUE_V"
where upper("OBS_GROUP_NAME") like '%'||upper(:P8_REPORT_SEARCH)||'%' and
"MAPPING_STATUS" = 'committed'

420239,

Located a note that describes this bug being encountered "After applying iAS 9.0.2.3 Patch". If this matches your situation, you need to apply Patch 3355915.

Scott

I seem to be having the same problem. I am told, however, that the patch solution does not apply because we are on 9.0.4. I thought I had gotten around the problem by limiting the number of rows returned by the SQL query to less than 500, but now in creating a different page I get the page cannot be found error when I have only 85 rows. It occurs when I press either the CANCEL or SUBMIT button.

Mel,

Check the Apache error log.

Scott

I guess the IE error message is misleading. The Apache error log says:
mod_plsql: /pls/htmldb/wwv_flow.accept HTTP-400 Too many arguments passed in. Got 2134 parameters. Upper limit is 2000

If you recreate this in your workspace on htmldb.oracle.com, we can take a look. Just post the app ID here. If you try to recreate it there and it doesn't fail, that will be useful information as well.

Scott

I solved the problem by changing the Number of Rows to a lower number in the Layout and Pagination section of Report Attributes for the Region. Perhaps it is understandable to have a limit on the number of fields that can be displayed for update (rows x columns), but there should be a better way of communicating it. It would be nice to be able to tell where you are in relation to the limit apart from just trial and error.

Mel,

I don't know exactly what limitation you're running into in terms of what you're doing with the page. It's hard to debug these issues without seeing a test case or full problem description which, to date, no one has provided us.

Scott

Sorry I didn't want to take the time to import the application, create the data structure and populate it, when the page is now working. However it seems like you should be able to easily re-create the situation. All I did was go through the wizard for a tabular form. It was based on a view and displayed all the columns, most of them updatable. It seems like what makes it fail (error when either CANCEL or SUBMIT is clicked) is just having a lot of fields on one screen. I base this conclusion on the error message from the Apache error log (mod_plsql: /pls/htmldb/wwv_flow.accept HTTP-400 Too many arguments passed in. Got 2134 parameters. Upper limit is 2000) and on the fix of reducing the number of rows on one screen, using pagination.

Mel,

We haven't seen this problem developing our applications or developing applications for many, many different clients and if it's been reported elsewhere on this forum, I've missed it.

If you would be so kind as to send us a page export (htmldb_us@oracle.com), or at least tell us what you mean by "a lot of fields", either would be useful. Just wondering if the threshold is closer to 50 or 5000.

Thanks,
Scott

I would be glad to, but though I know how to export an application, I don't know how to do just a page export.
There are 28 columns specified in the region source select statement; 24 of them are editable. 85 rows are selected. I put the number of rows at 40 in Layout and Pagination to eliminate the problem, though I didn't try to determine how high I could go before it failed.

Mel,

On the Page Definition page there's a row of buttons above the page number selector. One of them is Export. (Assuming version 1.6).

Scott

I don't see it. I guess we're on version 1.5.1.00.12 (number at bottom right of page).

OK, in 1.5 there is a link on the right side tasks region of one of the export pages. It says "Export Pages" or something like that.

Scott

Mel,

I located a description of Bug 3116388 and a related support note that says:

Apply Patch 3355915 which includes the fix for this.

If the Patch still does not resolve the issue, then do the following:

1) Open the file $OH/Apache/modplsql/conf/plsql.conf

2) There is a new global directive which modifies the amount of paramters one can use. The name of the Parameter is PlsqlMaxParameters. The default value is 2000.

3) Add this new directive to the plsql.conf file and set the value to say 4000 and save changes.

4) Restart HTTP Server.

My recommendation is that you contact Oracle Support and open a tar, providing this information and your specific symptoms to get them started. They may recommend that you apply the above-referenced patch or they may have other advice.

Scott

Thanks Scott. We may open a tar. Actually you had mentioned the patch in this thread before, right before I joined in. You said "Located a note that describes this bug being encountered "After applying iAS 9.0.2.3 Patch". If this matches your situation, you need to apply Patch 3355915." Then I said that I was told (by our system administrator) that this solution didn't apply to us because we are on 9.0.4. Would that be right? What version is the patch 3355915 relevant for?

I don't have those answers, Mel. That's where Support can help you out.

Scott