Recent content by Spikmeister

We're having a similar problem running 8.1.7.3 on a Sun Cluster... Suddenly things will just slow down and almost stop, normally the only way we've been able to sort it is to fail over to the other node of the cluster!

Just as an update, rather than trying to get round this problem I have simply set up an error log and if my procedure errors due to the rollback segment then it picks up from where it left off... So far this has proved effective...

when inserting it it'll need to be two quote marks, ie: '' Although this might cause you problems when using it later. For a system I worked on we replaced all quote marks in data with something we could later replace back (<Q>) to avoid errors occuring. Either that or you just remove all the...

I'll put money on it being because there's a quote mark in your string. That would turn it into: &quot;insert into test (PROJECTNUMBER, PROJECTNAME) VALUES(12345,'foto's')&quot; Which wouldn't work. Try removing the quote first and see if that works.

But in his long example he spoke about people changing the data that would then be read by the long procedures cursor - this cannot happen with my table.

Ah, now it makes sense... Thank you...

Please elaborate, I thought it was parsed during runtime...???

BTW, does your code contain a lot of huge transactions? Yep it does... I don't wish for an arguement to happen in here. The fact that the rollback segement that I'm using as the largest and also the last to be used in the round robin approach that Oracle uses must surely play a part in it...

I have two procedures that do identical things, one uses a Standard cursor that it loops through: CURSOR Cursor_SP IS SELECT ID, CCT_ID FROM SP_2 WHERE Inserted_By = 'I'; BEGIN FOR List_SP IN Cursor_SP LOOP (Lots of data crunching with other tables) END LOOP; END; The...

I have to say that we use utl_smtp to send out over 10000 e-mails a month from one of our systems and it works pretty well.

I've had that error many times in my playing with this code to get it to work. I've put it in before all the UPDATEs and INSERTs and &quot;CREATE TABLE AS SELECT&quot;s which are followed by COMMITs. I've had a lot of trial and error while writing this and trying to get the &quot;SET...

Well I'll end this by thanking everyone for their helpful suggestions. I managed to get the full load to run without tripping ORA-01555, mainly by using the &quot;set transaction use rollback segment R07&quot; within my loops and therefore before every commit. I'm not sure if this will work...

I'm using Oracle 8i and doing a data load of almost 800000 records. I then need to update all these records after doing some complex searching on other tables. However I keep getting this error (normally only a couple of hundred records short as well!): ORA-01555: snapshot too old: rollback...

It's an Oracle database and I have no problem selecting from hierarchy@test.world at all, even using a standard connect by rather than one in a dynamic cursor.

I'm trying to use a connect by within a dynamic cursor but I keep encountering the error: ORA-09999: Message 9999 not found; product=RDBMS; facility=ORA ORA-02063: preceding line from TEST.WORLD Here's the sql from my dynamic cursor: select hier_view.ho_id, hier_view.lo_id...