Re: Usage of Temporary Table?

  • From: rjamya <rjamya@xxxxxxxxx>
  • To: VIVEK_SHARMA <VIVEK_SHARMA@xxxxxxxxxxx>
  • Date: Fri, 15 Sep 2006 12:52:58 -0400

if you have few rows, why bother with indexes? you can easily search for
sys_context at tahiti.oracle.com, it will yield much more info or at
asktom.oracle.com

Raj

On 9/15/06, VIVEK_SHARMA <VIVEK_SHARMA@xxxxxxxxxxx> wrote:

Thanks Raj for the Global Temporary Tables' Advice.



Only 3 Tables hold the login info. Each Table has only 1 or 2 indexes.

These are small Tables with a few rows being inserted / updated into each
table per user login



Database will be a RAC Setup.



Approx a Total of 30,000 Concurrent users will login to do a set of OLTP
Transactions for an upcoming Benchmark.



If you could clarify what sys_context & VPD meant?

Any Docs, Links?



Regards


------------------------------

*From:* rjamya [mailto:rjamya@xxxxxxxxx]
*Sent:* Friday, September 15, 2006 5:18 PM
*To:* VIVEK_SHARMA
*Cc:* oracle-l@xxxxxxxxxxxxx
*Subject:* Re: Usage of Temporary Table?



you can use GTTs, they can be made session specific. However, you might
pay a performance penalty if you over index them and if this is RAC, never
ever try to truncate them. They will do all you want. GTTs are a good thing
when used in moderation.

OTOH, if the data is small (i.e. few rows) have you considered using
sys_context? Tom (of askTom fame) has a bunch of examples of using
sys_context especially when he shows VPD.

Raj




*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *VIVEK_SHARMA *Sent:* Friday, September 15, 2006 1:11 PM *To:* oracle-l@xxxxxxxxxxxxx *Subject:* Usage of Temporary Table?



Folks



On login by a User into our Hybrid Banking Application certain session
information e.g. role of user, operational authority of user etc is
INSERTED into a few Tables which needs to be preserved only till the life of
the respective user login session i.e. till the User logs OUT.



Additionally on a Database re-start we would prefer the respective tables
to get automatically Truncated/Flushed but with the Table Structure &
corresponding Indexes continuing to exist. We would prefer NOT to manually
create the Table Structure & respective indexes on DB restart.



NOTE - Both Dedicated & Shared Servers Database connections are used.

Currently PERMANENT Tables are being used for the same



*Qs Can some types of Temporary tables be used instead in Oracle – 10.2?*



NOTE – Redo need NOT be logged for these Tables.



Thanks indeed


**************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS***




-- ---------------------------------------------- Got RAC?

Other related posts: