Re: Updating x$

Hi Dave,

There is a POKE feature in ORADEBUG,
but you'll be doing well to find the right location to poke. X$VERSION does not exist statically in the SGA, it is dynamically constructed in the PGA as required. (This is true of many of the X$ structures - you can tell which from the ADDR columns).

Neither can you adb the binary, because the string there is just "Oracle8 Enterprise Edition Release %d.%d.%d.%d.%d %s". So, yes, it is theoretically possible,
but I doubt that you'll succeed.

Regards,
Steve Adams

http://www.ixora.com.au/
http://www.oreilly.com/catalog/orinternals/
http://www.christianity.net.au/

On Wed, 28 Jun 2000 21:38:20 GMT, oracow_at_my-deja.com wrote:

>Thanks for the reply Doug,
>
>That might be a little more involved that I had anticipated. For your
>interest, I'm trying to update the version number in x$version on one
>of our test boxes. At first glance, I would guess this table to be
>relatively static.
>
>This is related to a known bug on Oracle 8.0.5 for Windows NT.
>
>Dave
>
>In article <203f8c26.e9e657fd_at_usw-ex0102-016.remarq.com>,
> fro_doe <fro_doeNOfrSPAM_at_hotmail.com.invalid> wrote:
>> Most (probably all) of the x$ tables are dumps of memory
>> structures from the SGA or PGA of the process. Aside from
>> changing the parameter that might affect a given value, the only
>> way I know of is to update the memory location (given by
>> the ADDR value from a x$ select) directly with a C program (or
>> maybe oradebug). This does not sound like a good idea to me. In
>> any case, the database protects updates to these "tables" by
>> reporting an ORA-2030 error on anything but a select.
>>
>> Doug.
>>
>> Got questions? Get answers over the phone at Keen.com.
>> Up to 100 minutes free!
>> http://www.keen.com
>>
>>
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
Received on Thu Jun 29 2000 - 00:00:00 CDT