Monday, May 5, 2025

[DBT-10328] Specified GDB Name may have a potential conflict with an already existing database

[DBT-10328] Specified GDB Name may have a potential conflict with an already existing database

 

Issue:

dbca is not allowing to create DEV database throwing error message “DBT-10328 the specified GDB name may have potential conflicts”

Cause:

We have the DEV database entries on the /etc/oratab which is causing this issue

 

Fix/Solution:

Edit the /etc/oratab file and remove the DEV entry from /etc/oratab file

 

1. No database or database instance is running with name DEV

[root@oraclelab1 ~]# ps -ef|grep smon

oracle   13942     1  0 Apr30 ?        00:00:05 ora_smon_DEVDB

root     27910 27801  0 13:59 pts/3    00:00:00 grep --color=auto smon

[root@oraclelab1 ~]#

 

2. Old DEV entry exist on /etc/oratab file

 

[root@oraclelab1 ~]# cat /etc/oratab

#

# This file is used by ORACLE utilities.  It is created by root.sh

# and updated by either Database Configuration Assistant while creating

# a database or ASM Configuration Assistant while creating ASM instance.

 

# A colon, ':', is used as the field terminator.  A new line terminates

# the entry.  Lines beginning with a pound sign, '#', are comments.

#

# Entries are of the form:

#   $ORACLE_SID:$ORACLE_HOME:<N|Y>:

#

# The first and second fields are the system identifier and home

# directory of the database respectively.  The third field indicates

# to the dbstart utility that the database should , "Y", or should not,

# "N", be brought up at system boot time.

#

# Multiple entries with the same $ORACLE_SID are not allowed.

#

#

DEVDB:/u01/app/oracle/product/19.0.0.0/dbhome_1:N

DEV:/u01/app/oracle/product/19.0.0.0/dbhome_1:N

[root@oraclelab1 ~]#

 

After we removed the old DEV entry from /etc/oratafile file

[root@oraclelab1 ~]# vi /etc/oratab

[root@oraclelab1 ~]# cat /etc/oratab

#

# This file is used by ORACLE utilities.  It is created by root.sh

# and updated by either Database Configuration Assistant while creating

# a database or ASM Configuration Assistant while creating ASM instance.

 

# A colon, ':', is used as the field terminator.  A new line terminates

# the entry.  Lines beginning with a pound sign, '#', are comments.

#

# Entries are of the form:

#   $ORACLE_SID:$ORACLE_HOME:<N|Y>:

#

# The first and second fields are the system identifier and home

# directory of the database respectively.  The third field indicates

# to the dbstart utility that the database should , "Y", or should not,

# "N", be brought up at system boot time.

#

# Multiple entries with the same $ORACLE_SID are not allowed.

#

#

DEVDB:/u01/app/oracle/product/19.0.0.0/dbhome_1:N

[root@oraclelab1 ~]

    

 

 

 

No comments:

Post a Comment

-bash: oraenv: No such file or directory

-bash: oraenv: No such file or directory What Are Root.sh And OrainstRoot.sh Scripts In A Standalone RDBMS Installation? (Doc ID 1493121.1) ...