Creating Container Database for Oracle Grid Infrastructure Management Repository Failed on 12cR1 (12.1.0.2)

Creating Container Database for Oracle Grid Infrastructure Management Repository Failed on 12cR1 (12.1.0.2)

While upgrading from 11.2.0.4  to 12.1.0.2 cluster and rootupgrade.sh script has successfully completed on both node. But it is failed on post installation where MGMT instance creation is going on…

         

oracle@rac131:+ASM1>more  /u01/app/oracle/cfgtoollogs/dbca/_mgmtdb/_mgmtdb.log

+OCR_VOTING has enough space. Required space is 1566 MB, available space is 36468 MB.

File Validations Successful.

Validation of server pool succeeded.

Registering database with Oracle Grid Infrastructure

DBCA_PROGRESS : 5%

Copying database files

DBCA_PROGRESS : 7%

DBCA_PROGRESS : 9%

DBCA_PROGRESS : 16%

DBCA_PROGRESS : 23%

DBCA_PROGRESS : 30%

DBCA_PROGRESS : 37%

DBCA_PROGRESS : 41%

Creating and starting Oracle instance

DBCA_PROGRESS : 43%

DBCA_PROGRESS : 48%

DBCA_PROGRESS : 49%

DBCA_PROGRESS : 50%

DBCA_PROGRESS : 55%

DBCA_PROGRESS : 60%

DBCA_PROGRESS : 61%

DBCA_PROGRESS : 64%

Completing Database Creation

DBCA_PROGRESS : 68%

DBCA_PROGRESS : 79%

ORA-01034: ORACLE not available

ORA-01034: ORACLE not available

ORA-01034: ORACLE not available

DBCA_PROGRESS : DBCA Operation failed.

12c Grid Infrastructure Installation fails at 80% when creating the container database for GIMR with the following error:

ORA-01034: ORACLE not available

The following error stack was found in another log file:

Error starting mgmt database in local node, PRCR-1013 : Failed to start resource ora.mgmtdb

PRCR-1064 : Failed to start resource ora.mgmtdb on node rac131

CRS-2800: Cannot start resource 'ora.MGMTLSNR' as it is already in the INTERMEDIATE state on server 'rac131'

CAUSE

The ora.MGMTLSNR listener was running on port 1521, which was causing the issue.

RESOLUTION

                

What is happening is that ora.MGMTLSNR listener is running on port 1521, which is causing the issue since TNS/ASM/RIM listener and a management listener cannot run on the same port.

  To workaround this issue please do the following:

Solution Steps:

Stop the mgmt listener using below command to management listener:

oracle@rac131:+ASM1>srvctl stop mgmtlsnr -n rac131 -f

Validate the  mgmt listener old configuration

oracle@rac131:+ASM1>srvctl config MGMTLSNR

Name: MGMTLSNR

Type: Management Listener

Owner: oracle

Home: <CRS home>

End points: TCP:1521

Management listener is enabled.

Management listener is individually enabled on nodes:

Management listener is individually disabled on nodes:

Modify the mgmt listener                                 

oracle@rac131:+ASM1>srvctl modify mgmtlsnr -endpoints "TCP:1531"

Start the mgmt listener                                    

oracle@rac131:+ASM1>srvctl start MGMTLSNR

Validate the  mgmt listener new configuration

oracle@rac131:+ASM1>srvctl config MGMTLSNR

Name: MGMTLSNR

Type: Management Listener

Owner: oracle

Home: <CRS home>

End points: TCP:1531

Management listener is enabled.

Management listener is individually enabled on nodes:

Management listener is individually disabled on nodes:

Restart or retry the installation where it got failure message

Once that is done, then re-start the installation again.

Reference : 12c Grid Infrastructure Installation Fails While Creating Container Database: GIMR CRS-2800: Cannot start resource 'ora.MGMTLSNR' (Doc ID 2191588.1)