My Oracle Support Banner

CDB Crashes After Renaming one of its PDBs With ORA-00600 [kpdbIdToTenantKey1], [4099] (Doc ID 2696394.1)

Last updated on JULY 20, 2024

Applies to:

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

Symptoms

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.

 

After  renaming the PDB per steps in the document "Rename a Pluggable Database In Oracle 12c (Doc ID 2439885.1)", The cdb crashes .

Before rename, the PDB could open and close without an issue.

Error in alert log:

ORA-00600: internal error code, arguments: [kpdbIdToTenantKey1], [4099], [], [], [], [], [], [], [], [], [], []



Changes

 Renamed the PDB.

alter pluggable database PDB1 close;
alter pluggable database PDB1 open restricted;
select name, open_mode, restricted from v$pdbs;

Then connect to the PDB and rename it:

alter session set container=PDB1;

alter pluggable database rename global_name to <NEW_PDB_NAME>;

 

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.