Re: ORA-12850 running ash_wait_chains against 19c database

yeah, all other SQL I've run against GV$ views has been fine. I haven't spent any time trying to figure out what part of the SQL is causing the issue. I was just hoping someone else had already run across this.

if no quick solution, i'll definitely just make the SQL instance specific. thanks!

chris

On Thu, Jul 11, 2019 at 8:05 AM Andy Sayer <andysayer_at_gmail.com> wrote:

> 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,
> Andy
>
> 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.
>>
>> 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-l