I had problems with views, before causing core dumps when I compiled themConcerns me...
MaryM wrote:As you say, if there are interlocking dependencies between the objects in the view(s), on the initial run of the script they may well be invalidated. If you run the following:
I know it's almost a cliche'd answer but... can you provide a bit more detail?
When I compile about 3 or 4 view in the code section of the view using the object browser it runs fine. It's when I go and compile another view in the code section, it will take longer to compile or freeze up and then throw an ORA-20876 error. I tell the dba whats going on and she checks and sees that the Apex engine has crashed and has to restart it.
I do not have access to SQL Plus or anything else. I will do this on the Oracle Hosted site to see if there is any problems.
The problem with the views before, was I was just compiling them and alot of my views use other views. So I just figured that I needed to compile the main data views, before the rest of the views, thinking that I needed to do compile them in order.
I uploaded 23 views that I had to change a field name in them to the Oracle Hosted site. They loaded and compiled fine. The views that didn't have any changes, there was a red mark next to them, so I recompiled them. There were no errors. Why do I have to recompile views that I didn't change?
the View VW_BAR is invalidated, despite not being materially affected by the change to VW_FOO, on which it has a dependency - there are no errors displayed. Re-compiling VW_BAR seperately thereafter validates it.
create or replace view VW_FOO as select sysdate tdate from dual; create or replace view VW_BAR as select (sysdate + 1) tdate from dual union select vf.tdate from vw_foo vf; CREATE OR REPLACE VIEW VW_FOO (TDATE, TDATE_2) AS select sysdate tdate, sysdate tdate_2 from dual; View created. View created. View created.
My Oracle Hosted Site info:Hello,
Here are my credentials for the Oracle hosted site.
In and of itself, I don't think this is particularly worrying, as the solution is to re-compile the invalid objects.
create or replace FORCE view VW_BAR as select (sysdate + 1) tdate from dual union select vf.tdate from vw_foo vf; create or replace view VW_FOO as select sysdate tdate from dual; ... Warning: compiled but with compilation errors View created.