Synonym with Same Name in Loop-back DB link Causing 'SQL*Net message from dblink' and 'Cursor: pin S wait on X' (Doc ID 2585072.1)

Last updated on MARCH 01, 2020

Applies to:

Symptoms

• When create  loop-back DB link to access different schema's table in the same instance, and the synonym name is the same as the table name.
  'SQL*Net message from dblink' wait and 'cursor: pin S wait on X' wait occur:
  NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or public documentation delivered with an Oracle database product.  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
  
  

  -------------------------------------------------------------------------------
  Chain 1:
  -------------------------------------------------------------------------------
  Oracle session identified by:
  {
  instance: 1 (xxxx.xxxx)
  os id: 3224
  process id: 44, ORACLE.EXE (SHAD)
  session id: 16
  session serial #: 58289
  pdb id: 3 (xxxx)
  }
  is waiting for 'cursor: pin S wait on X' with wait info:
  {
  p1: 'idn'=0x78e56eb7
  p2: 'value'=0x10000000000
  p3: 'where'=0x500000000
  time in wait: 7 min 13 sec
  heur. time in wait: 1201 min 49 sec
  
  }
  and is blocked by
  => Oracle session identified by:
  {
  instance: 1 (xxxx.xxxx)
  os id: 4836
  process id: 42, ORACLE.EXE (SHAD)
  session id: 256
  session serial #: 44029
  pdb id: 3 (xxxxx)
  }
  which is waiting for 'SQL*Net message from dblink' with wait info:
  {
  p1: 'driver id'=0x54435000
  p2: '#bytes'=0x1
  time in wait: 1201 min 49 sec                                <<<<<
  
  }

  Chain 1 Signature: 'SQL*Net message from dblink'<='cursor: pin S wait on X'
  Chain 1 Signature Hash: 0x24c3b166

  ...

  -------------------------------------------------------------------------------
  Chain 10:
  -------------------------------------------------------------------------------
  Oracle session identified by:
  {
  instance: 1 (xxxx.xxxx)
  os id: 5280
  process id: 23, ORACLE.EXE (SHAD)
  session id: 386
  session serial #: 14181
  pdb id: 3 (xxxx)
  }
  is waiting for 'SQL*Net message from dblink' with wait info:
  {
  p1: 'driver id'=0x54435000
  p2: '#bytes'=0x1
  time in wait: 1201 min 49 sec                                <<<<< Waiting time is the same as Sid:256

The Sid:386 is waiting for Sid:256 by 'SQL*Net message to dblink' wait and Sid:256 is waiting for Sid:16 by 'SQL*Net message to dblink' wait too.

Meanwhile, Sid:16 is blocked by Sid:256 due to 'cursor: pin S wait on X' wait.

Changes

 None.

Cause

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