11.1.0.7 – our survey says…
January 9, 2009 4 Comments
Uh-uh (Family fortunes anyone? No? Don’t blame you)
Un-bloody-believable.
First day testing the 11.1.0.7 patch in preparation for an OLS implementation (for which there are various significant performance fixes in 10.2.0.4 and therefore should be in 11.1.0.7 rather than the current production version of 11.1.0.6), and one of the very first SQL statements that the application issues on startup goes bang.
End of file on communication channel.
T’rific…..
Ok, ok, I don’t know for sure yet that it’s 100% definitely the patch.
But it’s going to be. I’ve reduced the suspect SQL statement down and down and it’s gotta be.
What a way to finish the week.
I’d shout at it if I thought it would help.
Damn it.
Heh. We had MMAN crashing the instance after patching and before we could upgrade the data dictionary.
Hi
i actually upgraded my 11.1.0.6 instance today during the morning and got the same error.
here is the step that i done to resolve it (not realy sure what was the helping step)
1 create pfile from the spfile
2 Remove all the line with the “__” prefix
STRM11.__java_pool_size=67108864
STRM11.__large_pool_size=67108864
STRM11.__oracle_base=’/orahome/app/oracle’#ORACLE_BASE set from environment
STRM11.__pga_aggregate_target=1342177280
STRM11.__sga_target=3690987520
STRM11.__shared_io_pool_size=0
STRM11.__shared_pool_size=2080374784
STRM11.__streams_pool_size=536870912
3 Create new spfile and use it
the upgrade was fine except one error at the end (Note 744693.1)
good luck
Yehuda
Pingback: 11.1.0.7 Follow up « OraStory
It’s taken 11 days for Oracle to confirm that this is a bug in 11.1.0.7 – now that’s service…