resmgr:pq queued

When trying to connect to database (11g,12c)  I  see wait events on "resmgr:pq queued" indefinitely.
What can be done to resolve the resmgr:pq queued wait message?

By changing the following parameter, this issue was resolved :

alter system set "_parallel_statement_queuing"=FALSE scope=both;

Clusterware out of sync

I had strange inconsistency in Clusterware 12c.

crsctl stat res -t -w "NAME = ora.dbname.db"

return information that db is configured on:
--------------------------------------------------------------------------------
Name           Target  State        Server                   State details      
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.dbname.db
      1        ONLINE  ONLINE       node04              Open,Readonly,STABLE
      2        ONLINE  UNKNOWN      node01              Abnormal Termination
                                                             ,STABLE
--------------------------------------------------------------------------------

but when I checked configuration for this database:

srvctl config database -d dbname
...
Database instances: dbname1,dbname1
Configured nodes: node03,node04

 In documentation is a info that crsctl has a option "relocate resource" but dosn't work :/

To relocate resource I had to use:
srvctl modify instance -d dbname -i dbname1 -n node03


In one of document on metalink I found that only modify option force clusterware to synchronize information about resources

KTBCONVERTREDO

ORA-600 [KTBCONVERTREDO_1]

After ora-4030 errors and sequence of ora-600 ktbConvertRedo_1

and  led to an instance crash. Restarting database didn't help

(database was up ~ 5minutes).

We tried also switchover  to physical standby but unfortunately

we received the same error. 

Smon generated trace and if you carefully look in trace there is

 a object_id. When we tried 

run queries on this object then we received the same error. 

Bingo!!! Object had been corrupted.

luckily that was table with logs from application and we can

 easy drop table and recreate empty structure.   
 

In metalink I found information that  event 10153 should be set

 to see object_id but without that in alertlog this information was.