oracle11g RAC1执行脚本结果

[[email protected] ~]# /u01/app/oraInventory/orainstRoot.sh
Changing permissions of /u01/app/oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.

Changing groupname of /u01/app/oraInventory to oinstall.
The execution of the script is complete.
[[email protected] ~]# /u01/app/11.2.0/grid/root.sh
Performing root user operation for Oracle 11g 

The following environment variables are set as:
    ORACLE_OWNER= grid
    ORACLE_HOME=  /u01/app/11.2.0/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: /u01/app/11.2.0/grid/crs/install/crsconfig_params
Creating trace directory
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
Adding Clusterware entries to inittab
CRS-2672: Attempting to start ‘ora.mdnsd‘ on ‘testdb11a‘
CRS-2676: Start of ‘ora.mdnsd‘ on ‘testdb11a‘ succeeded
CRS-2672: Attempting to start ‘ora.gpnpd‘ on ‘testdb11a‘
CRS-2676: Start of ‘ora.gpnpd‘ on ‘testdb11a‘ succeeded
CRS-2672: Attempting to start ‘ora.cssdmonitor‘ on ‘testdb11a‘
CRS-2672: Attempting to start ‘ora.gipcd‘ on ‘testdb11a‘
CRS-2676: Start of ‘ora.gipcd‘ on ‘testdb11a‘ succeeded
CRS-2676: Start of ‘ora.cssdmonitor‘ on ‘testdb11a‘ succeeded
CRS-2672: Attempting to start ‘ora.cssd‘ on ‘testdb11a‘
CRS-2672: Attempting to start ‘ora.diskmon‘ on ‘testdb11a‘
CRS-2676: Start of ‘ora.diskmon‘ on ‘testdb11a‘ succeeded
CRS-2676: Start of ‘ora.cssd‘ on ‘testdb11a‘ succeeded

ASM created and started successfully.

Disk Group DATA created successfully.

clscfg: -install mode specified
Successfully accumulated necessary OCR keys.
Creating OCR keys for user ‘root‘, privgrp ‘root‘..
Operation successful.
CRS-4256: Updating the profile
Successful addition of voting disk af733aefc8e94f66bfadb582b6afbd8b.
Successfully replaced voting disk group with +DATA.
CRS-4256: Updating the profile
CRS-4266: Voting file(s) successfully replaced
##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- ---------
 1. ONLINE   af733aefc8e94f66bfadb582b6afbd8b (/dev/raw/raw1) [DATA]
Located 1 voting disk(s).
CRS-2672: Attempting to start ‘ora.asm‘ on ‘testdb11a‘
CRS-2676: Start of ‘ora.asm‘ on ‘testdb11a‘ succeeded
CRS-2672: Attempting to start ‘ora.DATA.dg‘ on ‘testdb11a‘
CRS-2676: Start of ‘ora.DATA.dg‘ on ‘testdb11a‘ succeeded
CRS-2672: Attempting to start ‘ora.registry.acfs‘ on ‘testdb11a‘
CRS-2676: Start of ‘ora.registry.acfs‘ on ‘testdb11a‘ succeeded
Configure Oracle Grid Infrastructure for a Cluster ... succeeded
时间： 2024-10-24 14:46:45

oracle11g RAC1执行脚本结果的相关文章

编写脚本标准的格式与执行脚本

编写脚本标准的格式: 第一行:#!/bin/bash  表示定义该脚本是一个shell脚本(固定格式) 第二行:#              这里的#属于注解,没有任何意义,shell 不会解析它. 第三行:#说明一下该脚本的作用 第四行:#写一下脚本的author(作者) 编写时间 第五行:写脚本内容 二三四行可有可无,建议养成好习惯. 要执行脚本(例如:first_shell.sh): (1)   加执行权限: chmod o+x first_shell.sh 运行脚本:./first_sh

Crontab执行脚本中的ssh命令访问被拒绝

我们经常会通过crontab来执行定时任务,通常生产环境中在不同主机直接进行登录是通过ssh来连接的.比如我们通过在备份服务器上设定定时任务,定期通过scp(使用SSH的远程拷贝命令)来拷贝远程服务器的数据到备份服务器上,这也是我遇到的一个事情. 环境描述: 脚本与定时任务: 定时任务设置如下: 无论是否执行成功,都把信息输出到2222.txt中 脚本内容如下: 我这里仅用ssh命令来测试,实际上这个命令如果可以正常执行的话,你执行scp命令也一样 #!/bin/bash ssh -v 192.

【MYSQL】在脚本中使用变量-执行脚本时传参

在shell脚本里可以定义变量,并在执行脚本时任意传参. #!/bin/bashdb_name=$1 #将第一个值赋给db_name变量sql_name=$2 #将第二个值赋给sql_name变量mysql -uroot -p123456 -h192.168.227.129 $db_name < $sql_name 在执行shell脚本时,在执行命令后面直接传参即可 ./sqlrecovery jinqy jinqy.sql

在Powershell中禁止执行脚本

在Powershell中执行脚本时,有如下报错: 无法加载文件 F:\script\1.ps1,因为在此系统中禁止执行脚本.有关详细信息,请参阅 "get-help about_signing". 所在位置 行:1 字符: 8 + .\1.ps1 <<<< + CategoryInfo          : NotSpecified: (:) [], PSSecurityException + FullyQualifiedErrorId : RuntimeExc

python中获取执行脚本路径方法

1.sys.path[0]:获取执行脚本目录绝对路径 #每次执行脚本时,python会将执行脚本目录加入PYTHONPATH环境变量中(sys.path获取) #!/usr/bin/python3 import os import sys print(sys.path) print(sys.path[0]) 执行结果: [[email protected] tmp]# ./py_test1/pytest24.py ['/tmp/py_test1', '/usr/local/lib/python3

执行脚本传入参数

执行脚本传入参数具体用在什么地方?

Shell执行脚本

Shell作用是解释执行用户的命令,用户输入一条命令,Shell就解释执行这一条,这种方式称为交互式,但还有另一种执行命令的方式称为批处理方式,用户事先写一个Shell脚本,Shell可以一次把这些命令执行完. 如下例子: 第一种执行方式:chmode+x script.sh 执行过程: Shell会fork一个子进程并调用exec执行./script.sh这个程序,exec系统调用会把子进程代码段替换成./script.sh程序的代码段,exec有一种机制,如果要执行的是一个文本文件,并且第一

2.3-命令批量执行脚本

命令批量执行脚本,同样需要两个脚本来实现:1 exe.expect 2 exe.sh 3 ip.list    IP列表 cat exe.expect #!/usr/bin/expect set host [lindex $argv 0]            #第一个参数,IP列表 set passwd "hd792310" set cm [lindex $argv 1]              #第二个参数,cm要执行的命令 spawn ssh [email protected]

[BASH]获取执行脚本的路径

SCRIPT=$(readlink -f "$0") #当前执行脚本的真实路径,兼容软链接 basedir=$(dirname "$SCRIPT") #当前执行脚本的所在目录