Shulou(Shulou.com)06/01 Report--

When deleting databases or configuring database options using dbca, you encounter a database instance that cannot be found or cannot be found that is not currently started, as follows:

[oracle@prodb-s ~]$ ps -ef |grep pmonoracle 2002 32138 0 22:49 pts/3 00:00:00 grep pmonoracle 32247 1 0 22:21 ? 00:00:00 ora_pmon_pro

The instance dbca wants to delete is named pro, but prodb appears instead:

This is usually because there is no canonical installation database and/etc/oratab has no or incorrect information.

Solution:

Directly modify the instance and path in/etc/oratab to the correct name and re-execute dbca:

[oracle@prodb-s ~]$ 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::## The first and second fields are the system identifier and home# directory of the database respectively. The third filed 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.## prodb:/u01/app/oracle/product/11.2.0/dbhome_1:N

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.