| Need your kind suggesions ( regarding Data block ) [message #231377] |
Mon, 16 April 2007 18:22  |
Dipali Vithalani
Messages: 278
Registered: March 2007
Location: India
|
Senior Member |
|
|
Hi dear friends,
Today, after 5 hours, i have to give a seminar in our company about the Oracle 10g. Today i will cover Databloks. In this i wish to cover it's format, row chaining and migration, PCTFREE - PCTUSED : how they work and their cases in different kind of applications..
Friends, I want to present the seminar at the best...
Should i make any changes in seminar content..?
Is there any new or extra ordinary point about data blocks with any one of you..?
Any suggetions..?
And ya, if possible please give me the different behavior of PCTFREE - PCTUSED in various kind of applications ( so that i can approve my content..)
I am waiting..
Thank You..
(Note : by mistak, i have put the same topic in certification's category.. Sorry for that.. )
|
|
|
|
|
|
|
|
| Re: Need your kind suggesions ( regarding Data block ) [message #231383 is a reply to message #231382] |
Mon, 16 April 2007 19:51  |
harshad.gohil
Messages: 157
Registered: April 2007
Location: USA
|
Senior Member |
|
|
Hi Dipali,
1) When we specify a standard blocksize = say x than we cannot set nonstandard block size DB_xk_cache_size . Internal oracle reson behind this rule.....
It's not like that .... You have gone to some different parts
Oracle 9i supports tablespaces with different block sizes. The DB_BLOCK_SIZE is used to specify the standard block size which is used for the SYSTEM and TEMPORARY tablespaces. All subsequent tablespaces will also be assigned this block size unless specified otherwise.
A number of rules apply to the use of variable block sizes:
* All partitions of a partitioned object must reside in tablespaces with the same block size.
* All temporary tablespaces must be of the standard block size.
* Index Organized Table Overflow and out-of-line LOB segments can be stored in a tablespace with a different block size that that of the base table.
For your second part
This allows large tables and indexes to have a larger block size than smaller objects. This is especially useful in hybrid databases where DSS transactions benefit from large block sizes, whilst OLTP operations are best suited to smaller block sizes. It also means that tablespaces can be transported between databases with differing block sizes. The database is created with a standard block size and up to 5 none-standard block sizes.
As on DSS is used not much used for heavvy transaction it means no frequent updates as such.... at the other hand on OLTP env there is frequent updates, so high PCT.
Hope this helps.
Regards,
Harsh
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Need your kind suggesions ( regarding Data block ) [message #231551 is a reply to message #231389] |
Tue, 17 April 2007 08:12 |
rleishman
Messages: 3728
Registered: October 2005
Location: Melbourne, Australia
|
Senior Member |
|
|
Is that right? I may have my terminology all twisted, but I thought Locally Managed Tablespaces eliminated the need for the STORAGE clause, not PCTFREE / PCTUSED / INITRANS / MAXTRANS.
Isn't it ASSM that replaces PCTUSED? But even then it doesn't replace PCTFREE - or does it?
Ross Leishman
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
