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

On Jul 26, 2:04 pm, NetComrade <netcomradeNS..._at_bookexchange.net> wrote:

> >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 :)
>

You're not the only one. Anyone running the same table name in two schemas in same instance is exposed to this problem, since 9ir1. There are umpteen calls on this in Metalink since then, all answered and closed the same way: upgrade to 10.2.0.3 or 11 or turn off all the sga auto management switches. Oracle has done bleeding nothing to fix this until 10.2.0.3 and even then it's not reliable!

I got hit by this one when pulling in click results from google, two years ago. Took us ages to figure out why the heck we losing clicks! Then we found them in the wrong schema... Suffice to say management was not impressed at all!

It's why Oracle never recommends running two or more of Peoplesoft or their own applications in the same instance. No wonder, with 25000 tables getting mixed data...

And they want to convince me they're running "very large and mixed applications databases" in their outsource service sites?

Yeah! Right... Received on Thu Jul 26 2007 - 05:33:04 CDT