亚洲av成人无遮挡网站在线观看,少妇性bbb搡bbb爽爽爽,亚洲av日韩精品久久久久久,兔费看少妇性l交大片免费,无码少妇一区二区三区

  免費注冊 查看新帖 |

Chinaunix

  平臺 論壇 博客 文庫
123下一頁
最近訪問板塊 發(fā)新帖
查看: 30808 | 回復(fù): 23
打印 上一主題 下一主題

oracle10g rac for hp-ux雙機盤符不一致,咋辦 [復(fù)制鏈接]

論壇徽章:
0
跳轉(zhuǎn)到指定樓層
1 [收藏(0)] [報告]
發(fā)表于 2008-12-27 09:47 |只看該作者 |倒序瀏覽
rt

oracle10g rac 安裝IA hp-ux  使用ASM存儲方式
但是雙機盤符不一致如何 修改?請大家?guī)蛶兔?多謝了!

論壇徽章:
0
2 [報告]
發(fā)表于 2008-12-27 12:10 |只看該作者
多種解決方法
1.修改盤符,也就是另一臺主機的pv的設(shè)備文件名,讓他與第一臺主機盤符一致,具體看hp的紅寶書
2.創(chuàng)建另一臺主機的pv設(shè)備文件名字的連接,和第一臺主機一致,就是第2臺主機pv相同的硬件地址2個設(shè)備文件名,第2個和主機一的pv設(shè)備文件名一樣
3.創(chuàng)建類似第2種方法,但是要修改2臺主機,2臺主機都不用pv的名字,而是用新的名字
是將c3t19d5改為諸如asmdisk1的ASM disks名字,在dev目錄下mknod來創(chuàng)建
[root@racnode1]# ls -lL c3t19d7
crw-r----- 1 root sys 32, 20 Feb 24 07:14 c3t19d7
[root@racnode1]# mkdir /dev/asmdisk
[root@racnode1]# cd /dev/asmdisk
[root@racnode1]# mknod asmdisk1 c 32 20
[root@racnode1]# ls -l
crw-r--r-- 1 root other 32, 20 May 7 07:50 asmdisk1
major and minor numbers和c3t19d7一樣.
[root@racnode1]# chown oracle:dba disk1
[root@racnode1]# ls –l /dev/disk
crw-r--r-- 1 oracle dba 32, 20 May 7 07:50 disk1
現(xiàn)在ASM_DISKSTRING可以設(shè)置為/dev/asmdisk/*,現(xiàn)在asm可以按照按asmdisk1這樣的標示來訪問磁盤,asm僅掃描匹配ASM_DISKSTRING設(shè)置的磁盤標示
用V$ASM_DISK來查看掃描到的磁盤

[ 本帖最后由 hp-ux民工 于 2008-12-27 22:36 編輯 ]

論壇徽章:
0
3 [報告]
發(fā)表于 2008-12-27 14:05 |只看該作者
非常感謝樓上的解答

我覺得第二種方法和3方法都比較好實施所以我試著第三種方法
進入/dev/rdsk目錄執(zhí)行下面命令 和您顯示有出入 看不出來主次設(shè)備號啊
bash-3.2# ls -lL c79t0d0
crw-r-----   1 bin        sys        188 0x4f0000 Sep 23 11:46 c79t0d0

您的解答里
“”root@racnode1]# chown oracle:dba disk1                  出現(xiàn)disk1是不是asmdisk1寫錯了的
[root@racnode1]# ls –l /dev/disk                                     這個命令無法執(zhí)行說沒有disk目錄
crw-r--r-- 1 oracle dba 32, 20 May 7 07:50 disk1“”

論壇徽章:
0
4 [報告]
發(fā)表于 2008-12-27 16:49 |只看該作者
樓上的哥們,是我的錯,
1.我把disk1寫成disk啦
2.我把環(huán)境從Solaris搬到hp-ux啦
  不過你可以按照方法去修改,不是讓你必須一樣的
crw-r-----   1 bin        sys        188 0x4f0000 Sep 23 11:46 c79t0d0

已經(jīng)看出來主號和次號啦,主號188 次號 0x4f0000
mknod asmdisk1 c 188 0x4f0000
就可以啦,我現(xiàn)在沒環(huán)境,沒法驗證,你可以自己測試下

俺僅僅是個初學(xué)asm的菜鳥,說錯啦,休怪!。

[ 本帖最后由 hp-ux民工 于 2008-12-27 16:54 編輯 ]

論壇徽章:
0
5 [報告]
發(fā)表于 2008-12-27 20:43 |只看該作者
If the ioscan command shows different device names for the same device on any
node, then:
a. Change directory to the /dev/rdsk directory.
b. Enter the following command to list the raw disk device names and their
associated major and minor numbers:
# ls -la
The output from this command is similar to the following for each disk device:
crw-r--r-- 1 bin sys 188 0x032000 Nov 4 2003 c3t2d0
In this example, 188 is the device major number and 0x32000 is the device
minor number.
c. Enter the following command to create a new device file for the disk that you
want to use, specifying the same major and minor number as the existing
device file:
# mknod ora_ocr_raw_100m c 188 0x032000
d. Repeat these steps on each node, specifying the correct major and minor
numbers for the new device files on each node.

Enter commands similar to the following on every node to change the owner,
group, and permissions on the character raw device file for each disk device that
you want to use:
■ OCR:
# chown rootinstall /dev/rdsk/cxtydz
# chmod 640 /dev/rdsk/cxtydz
■ Oracle Clusterware voting disk or database files:
# chown oracle:dba /dev/rdsk/cxtydz
# chmod 660 /dev/rdsk/cxtydz

[ 本帖最后由 hp-ux民工 于 2008-12-27 20:45 編輯 ]

論壇徽章:
0
6 [報告]
發(fā)表于 2008-12-27 20:59 |只看該作者
Please note that the device paths for Oracle Clusterware and ASM disks must be the same
from both systems. If they are not the same use the following command to map them to a
new virtual device name:
#mksf -C disk -H <hardware path> -I 62 <new virtual device name>
#mksf -C disk -H <hardware path> -I 62 -r <new virtual device name>
Example:
#mksf -C disk -H 0/0/10/0/0.1.0.39.0.1.0 -I 62 /dev/dsk/c8t1d0
#mksf -C disk -H 0/0/10/0/0.1.0.39.0.1.0 -I 62 -r /dev/rdsk/c8t1d0
As you can see at the following output of the ioscan command, now multiple device names
are mapped to the same hardware path.

[ 本帖最后由 hp-ux民工 于 2008-12-27 21:27 編輯 ]

1.JPG (29.34 KB, 下載次數(shù): 217)

asm

asm

論壇徽章:
0
7 [報告]
發(fā)表于 2008-12-27 21:13 |只看該作者
How to Change an Instance Number
Not only in cluster environments it is often useful to have a consistent device file naming. The
following procedures may be used to change the instance numbers of such devices. These
numbers determine the naming of the correpsonding device files.
The ioconfig provides the mapping between instance numbers used by the kernel and the
information the I/O system uses to communicate with peripheral devices (hardware paths).
Two copies are maintained (/stand/ioconfig and /etc/ioconfig).
At boot time the ioconfig information is stored in the io_tree kernel data structure (see
ioinit(1M)). The only purpose of the ioconfig is to maintain configuration information when
the system is not running. Even if hardware is removed from the system all mappings keep in
place. This guarantees that no new device file names will appear after such changes. If
removed hardware is added back to the system the original mapping can be reused, since it is
still present in the ioconfig files.
Usually we want to change mappings for disk and lan devices. For lan devices we change
directly the corresponding lan instance numbers. For disk devices we need to take care of the
ext_bus instance numbers. The numbers of such 'External Busses' (aka card instances) are
responsible for the 'c' numbers being part of disk device names.
Look at the following extract of an ioscan -fn output:
ext_bus 3 2/0/1 c720 CLAIMED INTERFACE Built-in SCSI
target 0 2/0/1.3 tgt CLAIMED DEVICE
target 1 2/0/1.5 tgt CLAIMED DEVICE
disk 4 2/0/1.5.0 sdisk CLAIMED DEVICE SEAGATE ST15150N
/dev/dsk/c3t5d0 /dev/rdsk/c3t5d0
The ext_bus instance number (3) is responsible for the 'c3' in 'c3t5d0'. The target (t5) and the
LUN (d0), which affect the rest of the name, are not changeable by software. Instead they
map directly to the underlying hardware configuration.
In the following three procedures are documented, an easy/quick one (Procedure I) and two
other more complicated ones (Procedure II and III).
Usually Procedure I is sufficient and there is no need to try II or III. These are only needed if
Procedure I fails. Procedure II usually works in all cases, but requires two reboots. Procedure
III needs only one reboot and should work in all cases, but you need the ioconfig2infile tool
(adapted from WTEC's parse_ioconfig), which can be obtained from the HP internal site
ftp://einstein.grc.hp.com/TOOLS/MISC (HP internal).


Procedure I
Default procedure, requires one reboot and works without additional tools.
1) Extract a configuration template from the current ioscan output
# ioscan -f | grep -e INTERFACE -e DEVICE | \
grep -v target | \
awk '{print $3, $1, $2}' > /infile
2) Edit /infile and change the ext_bus and lan instances as desired
No class is allowed to get more than one line for the same instance!
3) Bring down the system gracefully to run level 1
# init 1
4) Apply the ioconfig change
# /sbin/ioinit -f /infile -r
The system will reboot immediately if the change is successful.
Warnings like “Input is identical to kernel” can be ignored.
If unsuccessful, the most likely error to happen is:
“ioinit: Instance number X already exists for class XXX”
The problem is that your desired instance assignment conflicts with an existing instance
number. If that instance is bound to hardware that is no longer visible in ioscan, then
you are in trouble and need to perform the Procedure II or III.
5) Verify the changes
Once the system is up, verify that all the instance numbers were changed as expected. It
may be necessary to re-import volume groups to ensure that /etc/lvmtab contains the
correct entries. The lan configuration may need to be changed also.
Procedure II
Reliable, requires two reboots and works without additional tools.
1) Extract a configuration template from the current ioscan output
# ioscan -f | grep -e INTERFACE -e DEVICE | \
grep -v target | \
awk '{print $3, $1, $2}' > /infile
2) Edit /infile and change the ext_bus and lan instances as desired
No class is allowed to get more than one line for the same instance!

[ 本帖最后由 hp-ux民工 于 2008-12-27 21:19 編輯 ]

論壇徽章:
0
8 [報告]
發(fā)表于 2008-12-27 21:20 |只看該作者
3) Move away the current ioconfig files and shutdown/reboot
# mv /stand/ioconfig /stand/ioconfig.sav
# mv /etc/ioconfig /etc/ioconfig.sav
# shutdown -ry 0
4) Recreate ioconfig files.
Due to the missing ioconfig files the system will come to an ioinitrc prompt. Now
recreate new ioconfig files from scratch. This prevents you from running into possible
assignment conflicts.
(in ioinitrc)# /sbin/ioinit -c
5) Apply the ioconfig change with your prepared infile
(in ioinitrc)# /sbin/ioinit -f /infile -r
The system will reboot again now if the change was successful.
Warnings like “Input is identical to kernel” can be ignored.
6) Verify the changes
Once the system is up, verify that all the instance numbers were changed as expected. It
may be necessary to re-import volume groups to ensure that /etc/lvmtab contains the
correct entries. The lan configuration may need to be changed also.
Procedure III
Reliable, requires one reboot, needs ioconfig2infile tool. Since the infile is directly extracted
from the current ioconfig you get all mappings, even old ones for hardware that is not longer
visible in ioscan.
1) Extract a configuration template using ioconfig2infile
# ioconfig2infile /etc/ioconfig >/infile
2) Edit /infile and change the ext_bus and lan instances as desired
No class is allowed to get more than one line for the same instance!
3) Bring down the system gracefully to run level 1
# init 1
4) Apply the ioconfig change
# /sbin/ioinit -f /infile -r
The system will reboot immediately if the change is successful.
Warnings like “Input is identical to kernel” can be ignored.
5) Verify the changes
Once the system is up, verify that all the instance numbers were changed as expected. It
may be necessary to re-import volume groups to ensure that /etc/lvmtab contains the
correct entries. The lan configuration may need to be changed also.
NOTE:
If anything goes wrong you can always put the ioconfig copy /etc/ioconfig.sav and
/stand/ioconfig.sav back in place and reboot.

論壇徽章:
0
9 [報告]
發(fā)表于 2008-12-27 21:29 |只看該作者
以上3種方法,僅供參考,這是我以前從施工中從別的官方文檔中總結(jié)出來的。

論壇徽章:
0
10 [報告]
發(fā)表于 2008-12-27 21:47 |只看該作者
民工兄答得很好呀,建議此貼精華!
您需要登錄后才可以回帖 登錄 | 注冊

本版積分規(guī)則 發(fā)表回復(fù)

  

北京盛拓優(yōu)訊信息技術(shù)有限公司. 版權(quán)所有 京ICP備16024965號-6 北京市公安局海淀分局網(wǎng)監(jiān)中心備案編號:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年舉報專區(qū)
中國互聯(lián)網(wǎng)協(xié)會會員  聯(lián)系我們:huangweiwei@itpub.net
感謝所有關(guān)心和支持過ChinaUnix的朋友們 轉(zhuǎn)載本站內(nèi)容請注明原作者名及出處

清除 Cookies - ChinaUnix - Archiver - WAP - TOP