My Oracle Support Banner

PDB Connections Are Going To Different PDB In Same Container (Doc ID 2738565.1)

Last updated on DECEMBER 29, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

Client connection issue with PDB

There is a possible chance to connect to the wrong PDB when shared servers and multitenant is used.
Issue occurs when the PDB is unplugged and plugged back in.

During the authentication process conflicting information is being returned by the database side.
The client sends the AUTH_SESS_KEY packet that includes the proper SERVICE_NAME for PDB2 in this case.
(1) [07-FEB-2017 22:05:41:390] nsbasic_bsd: 44 29 28 53 45 52 56 49 |D)(SERVI|
(1) [07-FEB-2017 22:05:41:390] nsbasic_bsd: 43 45 5F 4E 41 4D 45 3D |CE_NAME=|
(1) [07-FEB-2017 22:05:41:390] nsbasic_bsd: 70 64 62 32 29 29 29 00 |pdb2))).|


The server however response to that packet is conflicting.
(1) [07-FEB-2017 22:05:41:398] nsbasic_brc: 41 55 54 48 5F 44 42 4E |AUTH_DBN|
(1) [07-FEB-2017 22:05:41:398] nsbasic_brc: 41 4D 45 04 00 00 00 04 |AME.....|
(1) [07-FEB-2017 22:05:41:398] nsbasic_brc: 50 44 42 31 00 00 00 00 |PDB1....| ..
(1) [07-FEB-2017 22:05:41:399] nsbasic_brc: 4D 45 04 00 00 00 04 70 |ME.....p|
(1) [07-FEB-2017 22:05:41:399] nsbasic_brc: 64 62 32 00 00 00 00 1B |db2.....|

So the authentication process is off at this stage.


 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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