Page Not Found in "wwv_flow" transitions after 3.1 upgrade

Question

After upgrading to 3.1, apparently successfully (all our applications seem to run fine), we now can not use the development environment.
Any time you make a change which routes to the /pls/apex/wwv_flow.accept address we get a "Page not found" (404) error in IE.
This is occurring on our main production environment and did not occur with our prior test upgrades on other servers.
Although I found many "Page not found" errors searching the forum, I didn't find anything similar to the error we are encountering.
Thanks in advance for any feeedback or suggestions,
Barney
Message was edited by:
barneymattox
corrected title to wwv_flow from www_flow

Answer 1

Scott,
Okay, to start off with, let me apologize. I just realized I was going through the same sequence (at least once per a session, since sessions can survive Apache restarts).
From the looks of it, something on the specific page at the top of my first applications page list brings down the entire development environment.
Since it may indicate another issue (e.g. bug), I'll continue to go forward towards the specific cause:
So, the sequence that specifically causes the failure:
1) Login
2) Click on top Application (100)
3) Click on top Page (24) (due to view mode)
4) Click Edit Report Region (click on first region label on page) [Other steps may also cause, but this fails every time instantly]
5) Everything is now broken...
Exporting and importing the page does not change this behavior. However, knowing this I can easily work around the issue. Though I can continue to pursue this investigation to isolate the cause as needed.
[Edit: I've isolated the cause.  The issue is with the Report Source for this top page.  It was the last page editted before the upgrade.  The report is a 5,594 character query.  It worked in the 3.0 version, but if I start a new report page from scratch and try to use this query, I get the error:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
<Return to Application>
And, once again, the development environment is trashed until you start your next session.  Although 5,594 characters is large, I've had much larger in my career.  I'm not certain if this is truly a size issue or relates to the number of bind variables, or some other aspect of the query.  I'll investigate further tomorrow.]
Barney
Message was edited by:
barneymattox