LDOM: Rescue Virtual Machine

# ldm add-vdsdev /apps/solaris/sol-10-u11-ga-sparc-dvd.iso iso_sol_10_11@primary-vds0

# ldm add-vdisk vdisk_iso iso_sol_10_11@primary-vds0 vmsolaris02

Login LDOM Console

 # ldm list-domain

NAME             STATE      FLAGS   CONS    VCPU  MEMORY   UTIL  NORM  UPTIME

primary          active     -n-cv-  UART    8     8G       0.5%  0.5%  61d 22h 52m

vmsolaris01           active     -n----  5000    64    64G      0.0%  0.0%  60d 23h 8m

vmsolaris02           active     -n----  5001    48    32G      0.2%  0.2%  54d 23h 23m

# ldm list-variable auto-boot? vmsolaris02

auto-boot?=true

# ldm set-var auto-boot\?=false vmsolaris02

# telnet <hostname> 5001

Trying 17.1.20.164...                                            

Connected to sun04.                                                

Escape character is '^]'.                                          

Connecting to console "vmsolaris02" in group "vmsolaris02" ....

Press ~? for control options ..                     

vmsolaris02 console login:

VNTSD commands       

~# --Send break      

~^B --Send alternate break

~. --Exit from this console

~w --Force write access   

~n --Console next         

~p --Console previous     

~? --Help                 

Press ~# to stop ldom

~#

Password: Debugging requested; hardware watchdog suspended.

c)ontinue, s)ync, r)eset? r                               

Resetting...                                              

NOTICE: Entering OpenBoot.                                

NOTICE: Fetching Guest MD from HV.                        

NOTICE: Starting additional cpus.                         

NOTICE: Initializing LDC services.                        

NOTICE: Probing PCI devices.                              

NOTICE: Finished PCI probing.                             

SPARC T4-2, No Keyboard

Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved.

OpenBoot 4.36.1, 32.0000 GB memory available, Serial #83577585.            

Ethernet address 0:14:4f:fb:4a:f1, Host ID: 84fb4af1.                      

{0} ok devalias      

vdisk_iso                /virtual-devices@100/channel-devices@200/disk@1

disk0                    /virtual-devices@100/channel-devices@200/disk@0

vnet2                    /virtual-devices@100/channel-devices@200/network@0

net                      /virtual-devices@100/channel-devices@200/network@0

disk                     /virtual-devices@100/channel-devices@200/disk@0  

virtual-console          /virtual-devices/console@1                       

name                     aliases                      

{0} ok boot -s /virtual-devices@100/channel-devices@200/disk@1            

Boot device: /virtual-devices@100/channel-devices@200/disk@0:a  File and args: -s /virtual-devices@100/channel-devices@200/disk@1

krtld: Unused kernel arguments: `/virtual-devices@100/channel-devices@200/disk@1'.                                              

SunOS Release 5.10 Version Generic_147147-26 64-bit                                                                             

Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved.                                                    

Booting to milestone "milestone/single-user:default".                                                                           

Hostname: vmsolaris02                                                                                                                

Requesting System Maintenance Mode                                                                                              

SINGLE USER MODE                                                                                                                

Root password for system maintenance (control-d to bypass):

single-user privilege assigned to /dev/console.            

Entering System Maintenance Mode                           

Dec 23 13:53:47 su: 'su root' succeeded for root on /dev/console

Oracle Corporation      SunOS 5.10      Generic Patch   January 2005

#

To reset user role

#  rolemod -K type=normal root                                     

UX: rolemod: root is currently logged in, some changes may not take effect until next login.

To reset password

# passwd

# ldm set-var auto-boot\?=true vmsolaris02

Oracle 11g R2 and T4-1 Performance Tunning

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

In alert log, below entries were found:
Deprecated system parameters with specified values:
  log_archive_start

Fix: alter system reset log_archive_start scope=spfile sid='*' ;

======
Performance Tunning with SPFILE


alter system set processes=20000 scope=spfile;
alter system set open_cursors=8000 scope=spfile;

alter system set pga_aggregate_target=13G scope=spfile;
alter system set sga_target=11G scope=spfile;
alter system set sga_max_size=11G scope=spfile;
alter system set memory_target=24G scope=spfile;
alter system set memory_max_target=24G scope=spfile;

alter system set recyclebin=OFF scope=spfile;
alter system set filesystemio_options=setall scope=spfile;


begin
for c in (select sid, serial# from v$session) loop
   dbms_system.set_int_param_in_session(c.sid,c.serial#,'session_cached_cursors', 200);
end loop;
end;
/

Oracle 11g R2: export table

ORA-20446: The owner of the job is not registered
ORA-06512: at “SYSMAN.MGMT_JOBS”, line 168
ORA-06512: at “SYSMAN.MGMT_JOBS”, line 86
ORA-06512: at line 1

Cause:

This is an Oracle bug in 11g, there is a fix available, you can use following workaround:

Fix
$ sqlplus /nolog
SQL> connect sysman/<password>
SQL> execute MGMT_USER.MAKE_EM_USER('USERID');

Oracle Linux 7: Network Bonding

Ref# http://www.unixmen.com/linux-basics-create-network-bonding-centos-6-5/

Create the bond
# nmcli con add type bond con-name bond0 ifname bond0 mode balance-rr
Add each interface to the bond:
# nmcli con add type bond-slave ifname em3 master bond0
# nmcli con add type bond-slave ifname em4 master bond0

Restart the NetworkManager service
# service NetworkManager restart

Types of Network Bonding

According the to the official documentation, here is the types of network bonding modes.

mode=0 (balance-rr)

Round-robin policy: It the default mode. It transmits packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.

mode=1 (active-backup)

Active-backup policy: In this mode, only one slave in the bond is active. The other one will become active, only when 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.

mode=2 (balance-xor)

XOR policy: 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)

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

mode=4 (802.3ad)

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.

Prerequisites:

- Ethtool support in the base drivers for retrieving the speed and duplex of each slave.
- 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 (balance-tlb)

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 (balance-alb)

Adaptive load balancing: includes balance-tlb plus receive load balancing (rlb) 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.