Oracle DBCA does not see started instances and Handling Methods

Oracle DBCA does not see started instances and Handling Methods

I. Problem description: I tested the Oracle database in a unit. I wanted to use DBCA to check the database configuration information. Of course, I am also in a panic. Who would have thought of the following picture. Create new data and configure the database operation button to Gray. What is the situation? The instance has not been started. It is impossible. I have just logged on to it. Okay, start the process.

Ii. solution:

1. check the/etc/oratab file and find that the information about the path is the previously installed ORACLE Software Directory (/u01 /.....) and the current software directory (/home/oracle/app /.....) inconsistent.

Before modification:

[Oracle @ tora01 etc] $ cat 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 shocould, "Y", or shocould not,

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

#

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

#

#

Holytest:/u01/app/oracle/product/11.2.0/db_1: N

After modification:

[Oracle @ tora01 etc] $ cat 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 shocould, "Y", or shocould not,

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

#

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

#

#

Holytest:/home/oracle/app/oracle/product/11.2.0/dbhome_1: N

2. Start DBCA again for verification and find that it is back to normal

Iii. Conclusion: A small discovery, an in-depth understanding of the oratab file. The last N in this file. If you need to enable the data automatically, you need to change it to Y. This is an experience and you must continue to study hard.