I've made the mat. view change and it was very usefull. The whole insert just takes only 9 seconds instead of the 20 minutes before. The costs of the whole statement is decreased to 151, which is less than the average cost of just one of the 15 statements before. The subquery was already...
Hi sem,
yes, i'm sure that my session is the only one, because only my application uses this table and the application is a single user one. So locking should not be the problem. I have analyzed the query QRY_ATA_ACTUAL_ERROR_CASES which is actually a union all statement of 15 querys(!).
They...
[COLOR=red]Also, when you say the "select is done in 5 seconds", do you mean the entire select (fetching all the rows) or are you just talking about 5 seconds to see the first few rows ?[/color red]
Oh oh... I think thats the clue... I tried to export the selected data to test this and it seems...
Hi Dagon,
this table is used to store the accounting period which must not be the actual month/year. I'm writing only a small part of the whole accounting algorithm. The where clause is just for safety reasons because the accounting can only be done for one month at once. The problem is that i...
CREATE OR REPLACE TRIGGER "AGTABR"."BEFORE_INSERT" BEFORE INSERT ON TBL_ERRORCASES_ATA
FOR EACH ROW
begin
if :old.DATE_ADDED is null then
:new.DATE_ADDED:=sysdate;
end if;
SELECT TBL_ERRORCASES_ATA_TYPE_SEQ.nextval INTO :new.ID FROM dual;
SELECT monat,jahr INTO...
Hello everybody,
i have a problem with, from my point of view simple insert - select statement. It takes nearly 20 minutes to finish, on an good equipped server. At first i thought the selection would take so long, but this is done in nearly five seconds. The rest of the time is spend for...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.