Tags: anymore, appex, creating, crop, database, excel, export, file, flow_excel_output, function, mysql, oracle, sql, working
Problem with FLOW_EXCEL_OUTPUT not working anymore
I've just had a new problem crop up with AppEx where the export function for creating an excel file no longer works. I think that it's probably a lost permission issue, but I can't find the FLOW_EXCEL_OUTPUT function/procedure/package anywhere.
When I try to generate the csv outpout, I just get the error page that Page Cannot be Found.
Any ideas on where to start looking?
Leave a comment...
- 6 Comments
- In Appex 2.00049 there is nothing exact like this!
But in schema FLOWS_020000 there is similar text (FLOW_EXCEL_OUTPUT_R) in these two package bodies
Hope this help!#1; Fri, 22 Feb 2008 12:16:00 GMT
- Thanks. Looking at the packages, PUBLIC already has eEXECUTE on WWV_FLOW, but not on WWV_RENDER_REPORT3. In a bit, I'll try to grant EXECUTE to PUBLIC on the above package and see if that gets it back working again.
-- edited (follow-up)
Okay, I just granted EXECUTE to PUBLIC on WWV_RENDER_REPORT3 and the export to csv still doesn't work.
To clarify, let me specify that this is on Oracle 10gR2, AppEx ver. 2.0.0.00.49, and the pages are using the Report Export functionality of a report under the Report Attributes. At one time this was working fine, but several months ago I did upgrade the database from 10gR1 to 10gR2. I'm thinking something broke permission-wise at that time, but no idea where to look or how to fix it.#2; Fri, 22 Feb 2008 12:17:00 GMT
- But there is no object you are looing for...just something similar (with "_R" suffix).
This leadme to something strange...
In Appex on licenced Oracle (i.e. 9...10R2) you should grant to HTMLDB_PUBLIC_USER not to PUBLIC user!!!
PUBLIC is user on XE!!
Be carefull with grants like this1#3; Fri, 22 Feb 2008 12:18:00 GMT
- Okay, I finally got it all figured out. Checking the apache error log lead me in the right direction (though it took me a while to remember to look there).
Somehow I had a bunch of Invalid Objects in the SYS schema, which in turn invalidated some objects in the FLOWS_020000 schema. Getting the objects compiled fixed my problem.#4; Fri, 22 Feb 2008 12:19:00 GMT
- And the real name of that problematic object is ?
Give me an answer to hear...
THX!#5; Fri, 22 Feb 2008 12:20:00 GMT
- At this point, I forget exactly which objects they were, but UTL_FILE was one of them. The SYS schema had around 30 invalid objects, which (some of them anyway) affected about 6 in the FLOWS_020000 schema. The one I remeber (since it was in the apache error log) was WWV_FLOW_GEN_API1. From there, I saw a bunch of the invalid objects and just went out and started comipling all of them, so not sure excatly which ones would fixed just this problem.
Bill Ferguson#6; Fri, 22 Feb 2008 12:21:00 GMT