Updating a data dictionary is simply not done. Remember, we're
the DBA (you will be assimilated) and not fun loving students
who can play with their alma mater's equipment. Updating the data
dictionary directly would cause the database to lose support from
Oracle Corp. and the perpetrator would b
y, June 12, 2003 7:29 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: RE: db file sequential read [WAS:wait event puzzler]
>
>
> he is talking about altering the column in the data
> dictionary. Ive updated TS$ myself and its not that big of a deal.
>
> id be a bit
he is talking about altering the column in the data dictionary. Ive updated TS$ myself
and its not that big of a deal.
id be a bit concerned about actually altering a column. Oracle may have some
underlying code that you dont know about that assumes a maximum column length = 30 or
there is som
Yes , did some small benchmarks of a Batch process running for a Few minutes & Loading
the CPUs by 50 %
Database Exists on Veritas Filesystems (VXFS)
truss of the process Both application & Database Calls made
Run with Value of vxio:vol_maxio = 512 ( = 256 K [Default] )
-
VIVEK_SHARMA,
Hi, did you have benchmark result or other whitepaper talking about
this thoery?
For db file sequential read, it is single block read to index and then
to table, so i think enlarge the maxio size of the os won't help?(I just guess, did
not test it).
