ts of list ORACLE-L
Sent: Saturday, October 25, 2003 10:09
PM
Subject: Re: using temp tables for
staging databases?
No, blocks won't fill up to PCTFREE in case a
block is already above PCTUSED and the next insert would drop amount of free
space less than PCTFREE. Block
To: Multiple recipients of list ORACLE-L
Sent: Monday, October 27, 2003 4:59
PM
Subject: Re: using temp tables for
staging databases?
What you have described is expected behaviour -
if"the next insert would drop amount of free space less than PCTFREE",
recipients of list ORACLE-L
Sent: Wednesday, October 22, 2003 6:39
AM
Subject: Re: using temp tables for
staging databases?
Yes, I understand BBW, and how PCTFREE affects
block density, and hence BBW. My point, which you appear to have missed, is
PCTUSED does not affect
:33 EDT
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: using temp tables for staging databases?
All the time. Oracle Apps's open interfaces are built this way,
for
example.
However, the guys here covered their bases by specifying smaller
temporary
: using temp tables for staging databases?
All the time. Oracle Apps's open interfaces are built this way,
for
example.
However, the guys here covered their bases by specifying smaller
temporary tables, as if they could prevent them from becoming
large.
I
suppose
: Tim Gorman [EMAIL PROTECTED]
Date: 2003/10/20 Mon AM 10:19:33 EDT
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: using temp tables for staging databases?
All the time. Oracle Apps's open interfaces are built this way, for
example.
However, the guys here covered
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: using temp tables for staging databases?
All the time. Oracle Apps's open interfaces are built this way, for
example.
However, the guys here covered their bases by specifying smaller
temporary tables
PROTECTED]
Subject: Re: using temp tables for staging databases?
All the time. Oracle Apps's open interfaces are built this way, for
example.
However, the guys here covered their bases by specifying smaller
temporary tables, as if they could prevent them from becoming large. I
suppose
issue, since it all goes
across the same pipe.
From: Tim Gorman [EMAIL PROTECTED]
Date: 2003/10/21 Tue AM 09:24:25 EDT
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: using temp tables for staging databases?
For PCTFREE, setting it to less than the default of 10
Gorman [EMAIL PROTECTED]
Date: 2003/10/20 Mon AM 10:19:33 EDT
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
Subject: Re: using temp tables for staging
databases?
All the time. Oracle Apps's open interfaces
are built this way, for
example.
However, the guys here covered
"Multiple
recipients of list ORACLE-L" [EMAIL PROTECTED]Sent: Tuesday,
October 21, 2003 10:24 AMSubject: Re: using temp tables for staging
databases? I'm unclear how BBW is related to PCTUSED.
PCTUSED is used to control when blocks are returned to the freelist due
to deletions
use them. So I want to make sure Im not
missing something.
From: Tim Gorman [EMAIL PROTECTED]
Date: 2003/10/20 Mon AM 10:19:33 EDT
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
Subject: Re: using temp tables for staging
databases?
All the time. Oracle Apps's
Mon AM 10:19:33 EDT
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
Subject: Re: using temp tables for staging
databases?
All the time. Oracle Apps's open
interfaces
are built this way, for
example.
However, the guys here covered their bases
never use them. So I want to make sure Im not
missing something.
From: Tim Gorman [EMAIL PROTECTED]
Date: 2003/10/20 Mon AM 10:19:33 EDT
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
Subject: Re: using temp tables for staging
databases?
All
All that is nice, but from my practice so far, by far the most
frequent cause of the buffer busy waits id DBWR being unable to catch
up. This can come as a consequence of several things:
- Poorly written transaction that modifies thousands of blocks during
peak time hours. Typical example is bill
in DW.HTH.Arup Nanda- Original Message
- From: "Binley Lim" [EMAIL PROTECTED]To: "Multiple
recipients of list ORACLE-L" [EMAIL PROTECTED]Sent: Tuesday,
October 21, 2003 10:24 AMSubject: Re: using temp tables for staging
databases? I'm unclear how BBW is related to
This is for non-transactional data load instances. The guys here sware that by using
smaller temporary tables(not global temp tables) they can increase the speed of the
data loads.
Not worried about latch contention because its just for bulk loads. I know this bad in
transactional instances.
All the time. Oracle Apps's open interfaces are built this way, for
example.
However, the guys here covered their bases by specifying smaller
temporary tables, as if they could prevent them from becoming large. I
suppose they might feel that they indemnify themselves if the tables should
ever
not missing something.
From: Tim Gorman [EMAIL PROTECTED]
Date: 2003/10/20 Mon AM 10:19:33 EDT
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: using temp tables for staging databases?
All the time. Oracle Apps's open interfaces are built this way, for
example
which says
never use them. So I want to make sure Im not missing something.
From: Tim Gorman [EMAIL PROTECTED]
Date: 2003/10/20 Mon AM 10:19:33 EDT
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: using temp tables for staging databases?
All the time. Oracle Apps's
20 matches
Mail list logo
