RE: ** can two processes use the same rollback extent

1)rollback segment will not shrink. Correct, assuming you do not shrink it manually. 2)It will keep growing till tablespace fills up. Correct assuming that you have a SQL statement that causes the rollback segment to grow in such a way and that you have no constraints on the rollback

RE: ** can two processes use the same rollback extent

1.) Correct, except that the DBA can always shrink it manually. 2.) Well, that's true, but a rollback segment w/ optimal set could conceivably grow to fill the tablespace as well. It depends on the size of the rollback tablespace and the size(s) of your transaction(s). The reason that it's

Re: On the front page of OTN

Yes, saw that 2. SED rules! Oh Yeah! ;D Cheers Nuno Souto [EMAIL PROTECTED] - Original Message - Quite a surprise to find this on the front page of OTN http://otn.oracle.com/pub/articles/dulaney_sed.html -- Please see the official ORACLE-L FAQ: http://www.orafaq.net --

Re: Exporting a partition with transport tablespace

The need to set primary and unique constraints to NOVALIDATE when doing an exchange partition. (It still doesn't help with problems of parent/child tables when dropping partitions though). Regards Jonathan Lewis http://www.jlcomp.demon.co.uk The educated person is not the person who can

Re: any single serial session will never get more than 5% of pga

Notes in-line Regards Jonathan Lewis http://www.jlcomp.demon.co.uk The educated person is not the person who can answer the questions, but the person who can question the answers -- T. Schick Jr One-day tutorials: http://www.jlcomp.demon.co.uk/tutorial.html Three-day seminar: see

Re: pga_aggregate_target

Yes, they are in kilobytes, as I wrote in my message before. If you check the source of v$pgastat you see that for statistics in bytes then QESMMSGAVL (value) column is multiplied by QESMMSGAMU which is 1024 (to get bytes from kilobytes). Tanel. - Original Message - To: Multiple

Re: Exporting a partition with transport tablespace

Thanks, I haven't hit this problem before. Actually, in my post I recommended to use novalidate option for exchanging required partition back from temporary transport table, that way Oracle won't check the contents in the partition (should be used only when this partition doesn't change in the

Re: TNSPING VS. REGULAR PING..! WHY SUCH A DIFFERENCE

Possibly due initially to the fact that ping is ICMP and runs very low in the TCP/IP stack that is in the network layer or the third level up from the hardware and TNSPING is application layer which puts it up at the top of the stack or two more layers higher. This alone can contribute to the

Re: Exporting a partition with transport tablespace

So your 'novalidate' referred to the without validation clause of exchange; I thought you were referring to the workaround for uk/pk exchanges where even if you did including indexes without validate on the exchange, Oracle still did a horrendous check of the UK and PK constraints by

pl/sql open cursor question

I have a function like below (psudo code). If cursor cur1 have multiple rows, would the code leave the cursor open when this function is called? So if this function is called 1000 times, I would have 1000 open cursors? function XYZ(gid in number) return varchar2 is cursor cur1 is select C1 from

Re: Exporting a partition with transport tablespace

Yep, I didn't remember the exact clause in the exchange partition syntax. Tanel. So your 'novalidate' referred to the without validation clause of exchange; I thought you were referring to the workaround for uk/pk exchanges where even if you did including indexes without

Re: pl/sql open cursor question

cursor for loops automatically close cursors. dont use when others then null on code you are putting in an application. if you have a bug you will have a hard time finding it. Its a fundamental flaw. - Original Message - To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent:

Re: pl/sql open cursor question

Hi if we assume it is implements this way (see below) there will only be one cursor since c_gid is a bind variable and there for the cursor will be sharded from call to call of the function. create or replace function XYZ (gid in number) return varchar2 is cursor cur1(c_gid number) is

Re: pl/sql open cursor question

I thought just the execution plan was shared? I thought the definition of a cursor, was the memory area used to store the data. That data does not stay persistent in memory with a cursor for loop it closes. correct me if Im wrong? - Original Message - From: Peter Gram

Re: pl/sql open cursor question

Hi: I thought in the orginal code (cursor cur1 is select C1 from tab1 where ID = gid;), gid is a parameter passed in so it is already a bind variable. I don't see any difference to what you proposed. Your method is just make cur1 take a paramter? Am I wrong here? Also what happens when your

Re: pl/sql open cursor question

What I don't understand is the loop construction: Actually only one (row) is read form the cursor, and then the function is left with a return. Because it's an unconditional return, the code within the loop will either execute once, or never. When no data is found NULL is returned. When an error

Re: pga_aggregate_target

So you did, guess I was skimming too fast. :) Jared On Sun, 2003-12-28 at 03:29, Tanel Poder wrote: Yes, they are in kilobytes, as I wrote in my message before. If you check the source of v$pgastat you see that for statistics in bytes then QESMMSGAVL (value) column is multiplied by

Re: order by

[EMAIL PROTECTED] wrote: Hello list, Can someone please explain to me why the following order by clauses are valid and yield the same results : select empno, deptno from emp order by sqrt (1) ; and select empno, deptno from emp order by sqrt ( 3.14234 ) ; The docs say that in

Re: pl/sql open cursor question

dont use when others then null on code you are putting in an application. if you have a bug you will have a hard time finding it. Its a fundamental flaw. One place where I have found it justified, is in logon trigger where users must be able to log on, despite any errors which occur in a

Re: pl/sql open cursor question

dont use when others then null on code you are putting in an application. if you have a bug you will have a hard time finding it. Its a fundamental flaw. One place where I have found it justified, is in logon trigger where users must be able to log on, despite any errors which occur in a logon

Re: pl/sql open cursor question

Carel, It might seem that the loop construct would be more expensive, but it didn't appear that way on my test system. ( 9.2.0.4, RH 8.0 ) function a: create or replace function a return varchar2 is begin for srec in (select dummy from ctest) loop return srec.dummy; end loop;