CLSRSC-184 CLSRSC-258: Failed to configure and start ASM



1.在配置Oracle DB 12c RAC的过程中,在Grid执行脚本root.sh的时候,你可能会遇到如题所示的报错
[root@rac1 ~]# /oracle/app/12.1.0.2/grid/root.sh
Performing root user operation.

The following environment variables are set as:
    ORACLE_OWNER= grid
    ORACLE_HOME=  /oracle/app/12.1.0.2/grid

Enter the full pathname of the local bin directory: [/usr/local/bin]: 
   Copying dbhome to /usr/local/bin ...
   Copying oraenv to /usr/local/bin ...
   Copying coraenv to /usr/local/bin ...

Creating /etc/oratab file...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /oracle/app/12.1.0.2/grid/crs/install/crsconfig_params
2015/11/21 22:03:46 CLSRSC-4001: Installing Oracle Trace File Analyzer (TFA) Collector.

2015/11/21 22:04:12 CLSRSC-4002: Successfully installed Oracle Trace File Analyzer (TFA) Collector.

2015/11/21 22:04:13 CLSRSC-363: User ignored prerequisites during installation

OLR initialization - successful
  root wallet
  root wallet cert
  root cert export
  peer wallet
  profile reader wallet
  pa wallet
  peer wallet keys
  pa wallet keys
  peer cert request
  pa cert request
  peer cert
  pa cert
  peer root cert TP
  profile reader root cert TP
  pa root cert TP
  peer pa cert TP
  pa peer cert TP
  profile reader pa cert TP
  profile reader peer cert TP
  peer user cert
  pa user cert
2015/11/21 22:05:05 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.conf'


CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
CRS-2672: Attempting to start 'ora.evmd' on 'rac1'
CRS-2672: Attempting to start 'ora.mdnsd' on 'rac1'
CRS-2676: Start of 'ora.mdnsd' on 'rac1' succeeded
CRS-2676: Start of 'ora.evmd' on 'rac1' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'rac1'
CRS-2676: Start of 'ora.gpnpd' on 'rac1' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'rac1'
CRS-2672: Attempting to start 'ora.gipcd' on 'rac1'
CRS-2676: Start of 'ora.cssdmonitor' on 'rac1' succeeded
CRS-2676: Start of 'ora.gipcd' on 'rac1' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'rac1'
CRS-2672: Attempting to start 'ora.diskmon' on 'rac1'
CRS-2676: Start of 'ora.diskmon' on 'rac1' succeeded
CRS-2676: Start of 'ora.cssd' on 'rac1' succeeded


ASM failed to start. Check /oracle/app/grid/cfgtoollogs/asmca/asmca-151121PM100657.log for details.


2015/11/21 22:07:48 CLSRSC-184: Configuration of ASM failed


2015/11/21 22:07:49 CLSRSC-258: Failed to configure and start ASM


Died at /oracle/app/12.1.0.2/grid/crs/install/crsinstall.pm line 2017.
The command '/oracle/app/12.1.0.2/grid/perl/bin/perl -I/oracle/app/12.1.0.2/grid/perl/lib -I/oracle/app/12.1.0.2/grid/crs/install /oracle/app/12.1.0.2/grid/crs/install/rootcrs.pl ' execution failed


2.解决办法:
扩大/dev/shm的大小:
[root@rac1 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2              30G  5.2G   24G  19% /
tmpfs                1004M  204K 1004M   1% /dev/shm
/dev/sdb1              41G   14G   25G  37% /oracle
[root@rac1 ~]# umount /dev/shm
umount: /dev/shm: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
[root@rac1 ~]# fuser -km /dev/shm
/dev/shm:             5090m  5125m  5172m
[root@rac1 ~]# umount /dev/shm
[root@rac1 ~]# vi /etc/fstab
#
# /etc/fstab
# Created by anaconda on Sun Nov  8 16:01:55 2015
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=50921d9d-11bf-46f6-815e-65bf11cd734e /                       ext4    defaults        1 1
UUID=2e531048-7ae9-4c4a-b5b9-228e0420d958 /oracle                 ext4    defaults        1 2
UUID=05fc1c47-9f9f-4525-941a-7a5b54abc261 swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults,size=3G        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0

[root@rac1 ~]# mount /dev/shm
[root@rac1 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2              30G  5.2G   24G  19% /
/dev/sdb1              41G   14G   25G  37% /oracle
tmpfs                 3.0G     0  3.0G   0% /dev/shm




3.重新执行root.sh脚本,成功。

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/27126919/viewspace-1843223/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/27126919/viewspace-1843223/

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Spring Boot是一个用于快速开发Java应用程序的框架,它提供了很多便捷的功能和配置选项。在使用Spring Boot时,有时会遇到一些报错信息,其中一个常见的报错是"Failed to configure a DataSource: 'url' attribute is not specified and no embedded"。 这个报错通常是由于没有正确配置数据源引起的。在Spring Boot中,数据源是用于连接数据库的重要组件。当你在应用程序中使用数据库时,需要配置数据源的相关信息,如数据库的URL、用户名、密码等。 出现这个报错的原因是因为在配置文件中没有正确指定数据源的URL属性,并且也没有使用嵌入式数据库。解决这个问题的方法有两种: 1. 配置数据源的URL属性:在你的应用程序的配置文件(如application.properties或application.yml)中,添加以下配置项: ``` spring.datasource.url=jdbc:mysql://localhost:3306/mydatabase ``` 其中,`jdbc:mysql://localhost:3306/mydatabase`是你数据库的URL,根据实际情况进行修改。 2. 使用嵌入式数据库:如果你不想手动配置数据源,可以考虑使用Spring Boot提供的嵌入式数据库(如H2、HSQLDB等)。在这种情况下,你只需要在配置文件中添加以下配置项: ``` spring.datasource.url=jdbc:h2:mem:testdb spring.datasource.driver-class-name=org.h2.Driver spring.datasource.username=sa spring.datasource.password= ``` 这样就可以使用嵌入式数据库进行开发和测试了。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值