Re: ORA-12850 running ash_wait_chains against 19c database
Date: Thu, 11 Jul 2019 14:05:35 +0100
Message-ID: <CACj1VR7+bhEFibe8HCX-acPqh0GxHLTgbM6fOunUPO-sy_p7MQ_at_mail.gmail.com>
Are you able to query the other gv$ views like gv$instance?
If you only need to run it against one instance then modify the script to
use v$active_session_history and remove the (blocking_)inst_id predicates.
Hope this helps,
On Thu, 11 Jul 2019 at 14:00, Chris Stephens <cstephens16_at_gmail.com> wrote:
> we recently installed 19c GI/RDBMS as a 3 node RAC cluster.
Andy
>
> TFA is reporting "CHA Problem Cause : CHA detected that commits were
> blocked for several seconds because the Log Writer Process (LGWR) was
> blocked."
>
> I thought I would use Tanel's ash_wait_chains.sql to dig in a little more
> but:
>
> SQL> _at_ash_wait_chains event2 1=1 sysdate-1 sysdate
> Error report -
> ORA-12850: Could not allocate slaves on all specified instances: 3 needed,
> 1 allocated
>
> I did some googling and some searching on support.oracle.com to no avail.
> I've got an SR open but was wondering if anyone else has hit this and/or
> has a solution to prevent the ORA-12850.
>
> Thanks in advance for any help!
>
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Jul 11 2019 - 15:05:35 CEST