Home » Archived » BIRT » oracle cache or BIRT caching?
| oracle cache or BIRT caching? [message #368922] |
Mon, 06 July 2009 17:35  |
Eclipse User |
|
|
|
We modified the params of a stored proc in oracle that I previous used in
a BIRT report. I then closed eclipse, created a new report and started
createing a data set and listed the stored procs and the stored proc that
we dropped and recreated was not there...the old param names were still
there. We had been banging our heads against the walls on this one
for 2 weeks now only to find out someone is caching something...either
BIRT on the harddrive as I shut eclipse down or oracle and neither
of those options makes any sense.
Also, anyone know where the logging would go for poeple logging to jdk
logging when using the BIRT designer?
Dean
|
|
| | | | | |
| Re: oracle cache or BIRT caching? [message #468225 is a reply to message #368983] |
Tue, 04 August 2009 11:09  |
| Eclipse User |
|
|
|
sorry, basically, here is what we did...we had a proc
proc(a, b, c, d) and a, b, c, d showed up in the list of params. We
dropped and recreated the proc with a, b, f instead of a, b, c, d. The
old proc of proc(a, b, c, d) showed up instead of proc a, b, f and worst
of all is that it seemed to survive a reboot of eclipse....we started
renaming the procs every time we changed their interface so we could make
progress and that seemed to work. It was a very bizarre issue.
thanks,
Dean
|
|
| | |
| Re: oracle cache or BIRT caching? [message #479407 is a reply to message #468225] |
Mon, 10 August 2009 18:05 |
| Eclipse User |
|
|
|
Dean Hiller wrote:
> sorry, basically, here is what we did...we had a proc
> proc(a, b, c, d) and a, b, c, d showed up in the list of params. We
> dropped and recreated the proc with a, b, f instead of a, b, c, d. The
> old proc of proc(a, b, c, d) showed up instead of proc a, b, f and worst
> of all is that it seemed to survive a reboot of eclipse....we started
> renaming the procs every time we changed their interface so we could make
> progress and that seemed to work. It was a very bizarre issue.
When the parameters or the resultset of a stored procedure are changed and
you ask BIRT to refresh its picture of what the stored proc looks like,
BIRT does not perform this refresh completely in the xml file supporting
the report.
Here's what I would check the next time this happens. Go into the xml
file, and I would get out of the BIRT design tool to do so. Use Emacs, or
textpad or some other editor that has solid textual searching capability.
Look around in this file for param f. I think you will see that param f
probably shows up in one node of the BIRT xml while c and d show up in
another section of the BIRT xml and it should be obvious the c and d need
to be changed to f. But, as you see, the UI presentation of this shows
a,b,c and d. I think you will find that f does actually exist in the xml
file though. Its a bit of a frustration point. I just edit the xml file
directly when this happens. Its easy to see what the xml should be
changed to. Close the file from the BIRT design tool, make the edit, save
it, open the file in BIRT design tool, and vhalla, a,b and f are shown.
Basically, don't trust the design tool to handle the .rptdesign tool
completely. Be ready to edit the xml file directly. Also, keep that file
in source control so you can revert if/when you mess up the xml file
yourself.
|
|
|
Goto Forum:
Current Time: Mon Nov 03 16:03:25 EST 2025
Powered by FUDForum. Page generated in 0.08286 seconds |
Home