INS-30060: Check for group existence failed.

Install Oracle 11gR2 on RHEL5 issue

solution

./runInstaller -ignoreSysPrereqs –ignoreInternalDriverError

Reference:
Cause: Unexpected error occurred while trying to check for group existence.
Action: Refer to the logs or contact Oracle Support Services. Note for advanced users: Launch the installer by passing the following flag ‘-ignoreInternalDriverError’.

EM Configuration issue. $ORACLE_HOME/odprimary_PRIDB not found

oracle control 12c agent issue

root cause

A common cause for this error is changing the hostname of the server in either /etc/hosts or DNS. In this case the there were no changes to the hostname as we were able to connect to the hostname listed in the last known state on the database home page.

Resolution

changing /etc/hosts to the following:
127.0.0.1 localhost.localdomain localhost
172.17.100.250 cloudcc12c cloudcc12c.com

reference:

http://www.oracledistilled.com/grid-control/em-configuration-issue-oracle_homeodprimary_pridb-not-found/

http://fusionsecurity.blogspot.com/2011/05/error-message-can-not-resolve-hostname.html

Installing VMWare Tools - What is the location of the directory of C header files that match your running

Resolution

vi /usr/src/kernels/{uname -r}/include/linux/utsrelease.h

Remove old define kernel

Add {uname -r} define kernel

#define UTS_RELEASE "uname -r"

Continue installation tools

What is the location of the directory of C header files that match your running

kernel? [/usr/src/linux/include] /usr/src/kernels/ {uname -r}/include/

oracle linux yum setup

http://public-yum.oracle.com/

Public Yum Server

Last updated: 9 May, 2011
Introduction

The Oracle public yum server offers a free and convenient way to install packages from the Oracle Linux and Oracle VM installation media via a yum client.

You can download the full Oracle Linux and Oracle VM installation media via edelivery.oracle.com/linux. Note that errata are not available via this public yum server. To access errata (bug fixes, security fixes and enhancement), you must have a valid support contract to access Unbreakable Linux Network (ULN). For more information, see the FAQ below.

This yum server is offered without support of any kind. If you require support, please consider purchasing Oracle Linux support via the online store, or via your sales representative.
Getting Started

Download and Install Oracle Linux

Download and copy the appropriate yum configuration file in place, by running the following commands as root:
Oracle Linux 4, Update 6 or Newer

# cd /etc/yum.repos.d
# mv Oracle-Base.repo Oracle-Base.repo.disabled
# wget http://public-yum.oracle.com/public-yum-el4.repo

Oracle Linux 5

# cd /etc/yum.repos.d
# wget http://public-yum.oracle.com/public-yum-el5.repo

Oracle Linux 6

# cd /etc/yum.repos.d
# wget http://public-yum.oracle.com/public-yum-ol6.repo

Oracle VM 2

# cd /etc/yum.repos.d
# wget http://public-yum.oracle.com/public-yum-ovm2.repo

Enable the appropriate repository by editing the yum configuration file
Open the yum configuration file in a text editor
Locate the section in the file for the repository you plan to update from, e.g. [el4_u6_base]
Change enabled=0 to enabled=1

Begin using yum, for example:

yum list

yum install firefox

You may be prompted to confirm the import of the Oracle OSS Group GPG key.

nic bonding by hp dl380

Bonding之前要確認網路介面和網路線是否有接到正確port

Bonding部分由於只有四條線故只綁兩個port分別為

Service LAN: eth0 , eth5

Storage LAN:eth2 , eth4

1.編輯核心模組

#vi /etc/modprobe.conf

alias eth0 bnx2 alias eth1 bnx2 alias eth2 bnx2 alias eth3 bnx2 alias eth4 e1000e alias eth5 e1000e alias scsi_hostadapter cciss alias scsi_hostadapter1 ata_piix #增加如下設定 alias bond0 bonding alias bond1 bonding options bonding max_bonds=2

2.建立虛擬網卡

# vi /etc/sysconfig/network-scripts/ifcfg-bond0

DEVICE=bond0 BOOTPROTO=static IPADDR=172.17.100.xxx NETMASK=255.255.254.0 GATEWAY=172.17.101.254 ONBOOT=yes USERCTL=no BONDING_OPTS="mode=6 miimon=100"

# vi /etc/sysconfig/network-scripts/ifcfg-bond1

DEVICE=bond1 BOOTPROTO=static IPADDR=192.168.200.xxx NETMASK=255.255.255.0 ONBOOT=yes USERCTL=no BONDING_OPTS="mode=6 miimon=100"

3. 編輯Service LAN eth0 eth5

# vi /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0 BOOTPROTO=none BROADCAST=172.17.101.255 HWADDR=xx:xx:xx:xx:xx:xx NETWORK=172.17.100.0 ONBOOT=yes TYPE=Ethernet USERCTL=no IPV6INIT=no PEERDNS=yes #增加如下設定,並把舊設定(IPADDR, NETMASK, GATEWAY)值註解 MASTER=bond0 SLAVE=yes

4. 編輯Storage LAN eth2 eth4

# vi /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth2 BOOTPROTO=none HWADDR= xx:xx:xx:xx:xx:xx ONBOOT=yes TYPE=Ethernet USERCTL=no IPV6INIT=no PEERDNS=yes #增加如下設定,並把舊設定(IPADDR, NETMASK, GATEWAY)值註解 MASTER=bond1 SLAVE=yes

5.確認取消其他網卡設定值eth1 eth3

DEVICE=eth3 BOOTPROTO=dhcp HWADDR= xx:xx:xx:xx:xx:xx #取消開機啟動, 並把舊設定(IPADDR, NETMASK, GATEWAY)值註解 ONBOOT=no DHCP_HOSTNAME=au10dmzh48.winxtar.com TYPE=Ethernet

6.取消automount

#vi /etc/fstab

先註解nfs避免設定錯誤導致reboot無法automount導致系統開不起來

/dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 #192.168.200.1:/vol/test /d01 nfs rw,rsize=32768,wsize=32768,sync,nointr,hard 0 0

7. reboot

Ping 172.17.101.254

Ping 192.168.200.1

拔線看看是否有斷線,如果接正常即可把automount啟動並且在次reboot測試automount.

Bonding mode

Options for mode types:
You can set up your bond interface according to your needs. In order to do this, you simply change the mode type depicted in the examples below (mode=X). There are seven mode types available. They are as follows:

mode=0
This mode uses the Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.

mode=1
This mode uses an Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode.

mode=2
Transmit based on [(source MAC address XOR'd with destination MAC address) modulo slave count]. This selects the same slave for each destination MAC address. This mode provides load balancing and fault tolerance.

mode=3
Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.

mode=4
IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification.

*Pre-requisites:

1. Ethtool support in the base drivers for retrieving the speed and duplex of each slave.

2. A switch that supports IEEE 802.3ad Dynamic link aggregation. Most switches will require some type of configuration to enable 802.3ad mode

mode=5
Adaptive transmit load balancing: channel bonding that does not require any special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave.

*Prerequisite: Ethtool support in the base drivers for retrieving the speed of each slave.

mode=6
Adaptive load balancing: includes balance-transmit load balancing plus receive load balancing for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server.

ASDM cannot be launched - Cisco bug ID CSCsr89144

Problem: Exception in thread "SGZ Loader:

launchSgzApplet" java.lang.NumberFormatException: For

input string: "1 year 0"

This problem is caused by Cisco bug ID CSCsr89144 (registered customers only) in ASA running for more

than one year with ASDM 6.0.3 or 6.1. As a result, ASDM cannot be launched.

Solution

This error can be resolved by reloading the ASA.

參考:

http://www.cisco.com/image/gif/paws/110282/asdm-tshoot.pdf

http://bbs.51cto.com/thread-790458-1.html

umount device

相信很多人都遇過在linux下要umount某個device時發生"umount: /u01: device is busy" 的錯誤.這個訊息代表要被umount的device正被process使用/user占用中.

此問題通常可用採以下幾個解法:

* 執行 lsof |grep XXX (XXX為要umount的目錄名稱)找出目前佔用此device的ProcessID/user,剔除掉該PID或請user離開該目錄後進行正常umount.

* 執行 fuser -m /dev/sdd1 則更直接的列出佔用此device的PID,剔除掉該PID後進行正常umount.

* 執行 umount -f /dev/sdd1 強制umount

* 若以上指令都無法生效時,就只剩下 umount -l /dev/sdd1 這種暴力umount的指令可以用了.這個指令常用於Networked File System(NFS)的 mount device.

PS: 但正常的作法應該是先停掉nfs service之後就可以umount了.

出處:

http://dbasdiary.blogspot.com/2009/03/umount-device.html