My Oracle Support Banner

ORA-02050, ORA-02056, ORA-02063 happened during taking a snapshot of standby statspack using dblink (Doc ID 2281286.1)

Last updated on FEBRUARY 24, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.


On : version, RDBMS

Environment :

  - This is a Data Guard whcih composed of  4node RAC(Primary side) and  4node RAC(Standby side)


  Customer has installed standby statspack for performance tuning. However, when the snapshots of standby statspack were taken using dblink from remote standby nodes,
  The following errors  often happened.   The snapshots of standby statspack are taken every 30 minutes.

Error 2056 trapped in 2PC on transaction 1448.7.162608. Cleaning up.
Error stack returned to user:
ORA-02050: transaction 1448.7.162608 rolled back, some remote DBs may be in-doubt
ORA-02056: 2PC: k2lcom: bad two-phase command number rdonly from coord
ORA-02063: preceding line from STDBY_LINK_L2



 Standby statspack  was installed for performance tuning in standby side


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.