Summary of Solutions to oracle Installation Problems

Scenario Description: The oracle11g software is installed normally and the configuration listening is faulty. The DBCA database has been installed and needs to be re-built for some reason. DBCA deletes the database and re-creates the database. Various problems are encountered during the reconstruction process. 1. DBCA database creation. When you allocate PGA and SGA memory, if your "devshm" Size

Scenario Description: oracle 11g software is installed normally, and configuration listening is faulty. The DBCA database must be reinstalled once for some reason. DBCA deletes the database and re-creates the database. Various problems are encountered during the reconstruction process. 1. DBCA database creation. When you allocate PGA and SGA memory, if your "/dev/shm" Size

Scenario: The oracle 11g software is installed normally and the configuration listening is normal.

Fault: The DBCA database must be re-built once for some reason. DBCA deletes the database and re-creates the database. Various problems are encountered during the reconstruction process.

1. DBCA database creation. When the PGA and SGA memory are allocated, if the size of your "/dev/shm" cannot meet certain conditions (ORACLE database has introduced an Automatic Memory Management feature since version 11g, this feature requires more shared memory (/dev/shm). Therefore, if you decide to apply this feature, make sure that the shared memory is greater than the initial parameters MEMORY_MAX_TARGET and MEMORY_TARGET in ORACLE (note, these two parameters are the initialization parameters corresponding to the automatic memory management feature) values.
If the MEMORY_MAX_TARGET and MEMORY_TARGET parameters are set to a non-zero value in the initialization parameters and do not comply with the system shared memory, the ORACLE database will trigger the ORA-00845 at startup: MEMORY_TARGET not supported on this system error .), When you proceed to the next step, the following error will be reported:

Solution: Modify the initialization parameter so that the SGA setting in the initialization parameter is smaller than/dev/shm, and adjust the size of/dev/shm. This section describes how to increase the size of "/dev/shm". For details, see "http://blog.chinaunix.net/uid-23284114-id-3232508.html"

2. Keep "Next" until the "finish" button starts to install the database. When the scroll bar reaches about 40%, it will report an error.

, (Log "$ ORACLE_BASE/export toollogs/dbca/$ ORACLE_SID/trace. log shows "tnslisten related information") Here we select ingore and continue to go down until the scroll bar reaches Around 74% and an error is reported, as shown in figure

, (From the background log "$ ORACLE_BASE/export toollogs/dbca/$ ORACLE_SID/trace. log, you can see"

[Thread-40] [13:50:23. 055 CST] [HAUtils. isHASConfigured: 349] Ignoring exception in isHASConfigured: PRCT-1011: Failed to run "getcrshome"
PRCT-1011: Failed to run "getcrshome information"), here we choose OK, continue to wow go down, when to 85%, from the arrival of 85%, has been waiting for more than 2 hours, we will send the installation interface, but it will not appear. In this case, we open a new session and use the "sqlplus/as sysdba" command to find that the database can be logged on, and the database can be started and closed normally. For example

Solution: in the above cases, it is likely that the database password of your oracle database contains the "@" symbol, this is not recognized by oracle (for details, see the link "http://ipmingsee.blog.163.com/blog/static/71263720107925849361/"), this is a blood lesson. The problem was simple, but it took me more than four hours to analyze it. During this period, I could not solve the problem multiple times. I changed the password and found that there was no more error dialog box as described above.

3) view the log information during installation to check the progress:
$ Tail-100f $ ORACLE_BASE/export toollogs/dbca/$ ORACLE_SID/$ ORACLE_SID.log