Re: here's a good one from dizwell on the recent product launch

On Fri, 20 Jul 2007 00:19:26 -0700, Noons <wizofoz2k_at_yahoo.com.au> wrote:

>On Jul 20, 2:16 am, DA Morgan <damor..._at_psoug.org> wrote:
>
>
>Before I forget:
>
>>
>> > 1- A table gets updated in the WRONG schema.
>>
>> So it is an issue for you: Send me a case I can test in 11g.
>
>Set SGA to auto memory management
>for everything and use a pga_aggregate
>as well.
>Create two schemas in the database,
>with differently named tables and one
>table with same name in both.
>Load the system with heavy updating,
>using vanilla UPDATE <tablename>
>statements in both schemas. Add a few
>heavy ORDER BY selects. Make sure
>you are not using UPDATE <owner.tablename>.
>Run them all under the username of one
>of the schemas.
>Then after a while, inject a few of those updates,
>but this time on the table that is commonly named.
>Increase load on these and watch which table
>gets updated.
>
>Happens since 9i, various Metalink SRs.
>Workaround? Turn off the pga_aggregate and the
>SGA auto memory management and go back to setting
>all the umpteen memory caches manually.
>No fix "until 11g".

We hit this, we have many db's with almost identical schemas.. Is this still not fixed? After we applied 10.2.0.3, I heard maybe one complain. Lucky it was not a payroll database :)

http://groups.google.com/group/comp.databases.oracle.server/browse_frm/thread/84db8cf221d5781/eed68bf53ca0f7b6?lnk=st&q=author%3Anetcomrade&rnum=34#eed68bf53ca0f7b6 .......
We run Oracle 9iR2,10gR1/2 on RH4/RH3 and Solaris 10 (Sparc) remove NSPAM to email Received on Wed Jul 25 2007 - 23:04:22 CDT