Re: Performance in 12.2
- From: Jared Still <jkstill@xxxxxxxxx>
- To: Pete Sharman <peter.sharman@xxxxxxxxxxxxxx>
- Date: Sun, 10 Jun 2018 09:50:57 -0700
On Sun, Jun 3, 2018 at 5:40 PM, Pete Sharman <peter.sharman@xxxxxxxxxxxxxx>
wrote:
So for those that wondered where this might have ended, the client in
question had a replica database that was about to be rebuilt. I truncated
all four PLSCOPE tables and the performance issue went away. I still have
no understanding of why those tables were even populated since
PLSCOPE_SETTINGS was set to 'IDENTIFIERS:NONE'. We’ll monitor the tables
and set up a job to do the truncation regularly if they start being
populated again.
For this particular client I do not have access to their CSI, so I am
unable to log it as a bug. ☹
And indeed I was going to suggest it was a bug if it didn't get mentioned
by the end of the thread.
Personally I seem to be running across more and more bugs lately.
How about this one, supposedly fixed in 11.2.0.4
If the FRA fills and there is a Guaranteed Restore Point in the FRA, RVWR
(Recover Writer) will crash the instance rather than suspending it.
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Principal Consultant at Pythian
Pythian Blog
http://www.pythian.com/blog/author/still/
Github:
https://github.com/jkstill
Other related posts:
