Linux Scroll

Just another WordPress.com site

Monthly Archives: November 2011

Sort by memory usage

# ps -eo pmem,pcpu,rss,vsize,args | sort -k 1 -r | more
%MEM %CPU RSS VSZ COMMAND
0.3 0.0 6984 8608 detect_group:btmp
0.3 0.0 6708 155144 python ./hpssd.py
0.3 0.0 6688 8352 detect_group:uroot_log
0.3 0.0 6344 7964 detect_group:nessus
0.3 0.0 6248 7952 detect_group:heartbeat

Advertisements

VCS WARNING V-16-1-10263 Cannot clear resource of Operations type None

Cannot clear resource of Operations type ‘None’

Description: For a persistent resource, which cannot be controlled by VCS,
faults cannot be cleared through VCS. Persistent resources are designated
with “No” (None) operations from VCS perspective. Examples of such resource
types are NIC, MultiNICA, MultiNICB, Proxy. VCS will only MONITOR those
resources. It will not attempt to bring the resource online or offline.

Solution: Please rectify the fault, for example, if the NIC pointed to by this
resource is malfunctioning, replace the NIC. VCS will detect the state of this
resource to be online if the fault has been rectified (outside VCS control).

What is the difference between ODBC and OLEDB?

ODBC is Open Data Base Connectivity, which is a connection method to data sources and other things. It requires that you set up a data source, or what’s called a DSN using an SQL driver or other driver if connecting to other database types. Most database systems support ODBC.

OLE is Object Linking and Embedding. OLEDB is partly distinguished from OLE itself, now called “automation”.

OLEDB is the successor to ODBC, a set of software components that allow a “front end” such as GUI based on VB, C++, Access or whatever to connect with a back end such as SQL Server, Oracle, DB2, mySQL etal. In many cases the OLEDB components offer much better performance than the older ODBC.

OLEDB is a different type of data provider that came about with MS’s Universal Data Access in 1996 and does not require that you set up a DSN. It is commonly used when building VB apps and is closely tied to ADO. It works with COM, and DCOM as of SQL 7.0.

Corrupt label; wrong magic number

Error messages:

WARNING: /scsi_vhci/ssd@g50060e9015320e000001340c000062b2 (ssd21):
        Corrupt label; wrong magic number

Solution:

# format
Searching for disks...

AVAILABLE DISK SELECTIONS:
       0. c1t0d0 
          /pci@400/pci@0/pci@8/scsi@0/sd@0,0
       1. c1t1d0   solaris
          /pci@400/pci@0/pci@8/scsi@0/sd@1,0
       2. c3r60060E3015440D000001320C00006B86e0 
          /scsi_vhci/ssd@g50060e9015320e000001340c000062b2


Specify disk (enter its number): 2
selecting c3r60060E3015440D000001320C00006B86e0
[disk formatted]

Disk not labeled.  Label it now? y

FORMAT MENU:
        disk       - select a disk
        type       - select (define) a disk type
        partition  - select (define) a partition table
        current    - describe the current disk
        format     - format and analyze the disk
        repair     - repair a defective sector
        label      - write label to the disk
        analyze    - surface analysis
        defect     - defect list management
        backup     - search for backup labels
        verify     - read and display labels
        save       - save new disk/partition definitions
        inquiry    - show vendor, product and revision
        volname    - set 8-character volume name
        !     - execute , then return
        quit
format> quit

# init 6

Solaris install patch

Download patch to /tmp

Login to console

sc> console

Login to system.

Swift to System Maintenance Mode.

# init S
****    SYSCON CHANGED TO /dev/console  ****
# svc.startd: The system is coming down for administration.  Please wait.
Nov  5 05:26:43 server3 syslogd: going down on signal 15
svc.startd: Killing user processes: done.
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
SINGLE USER MODE

Root password for system maintenance (control-d to bypass):
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode

Nov  5 05:27:03 su: 'su root' succeeded for root on /dev/console

    Authorized uses only. All activity may be monitored and reported.

You have new mail.
# 

Install patch:

# patchadd 120753-06
Validating patches...

Loading patches installed on the system...

Done!

Loading patches requested to install.

Done!

Checking patches that you specified for installation.

Done!


Approved patches will be installed in this order:

120753-06


Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 120753-06 has been successfully installed.
See /var/sadm/patch/120753-06/log for details

Patch packages installed:
  SUNWlibm
  SUNWlibmsr

Verify patch

# patchadd -p | grep 120753-06
Patch: 120753-06 Obsoletes: Requires: Incompatibles: Packages: SUNWlibmsr SUNWlibm
# shutdown -y -i6 -g0

dladm

# dladm show-dev
vsw0            link: unknown   speed: 1000  Mbps       duplex: full
vsw1            link: unknown   speed: 1000  Mbps       duplex: full
vsw2            link: unknown   speed: 1000  Mbps       duplex: full
vsw3            link: unknown   speed: 1000  Mbps       duplex: full
e1000g0         link: up        speed: 1000  Mbps       duplex: full
e1000g1         link: up        speed: 1000  Mbps       duplex: full
e1000g2         link: up        speed: 1000  Mbps       duplex: full
e1000g3         link: up        speed: 1000  Mbps       duplex: full

Postfix – delete queue mail

# mailq
-Queue ID- –Size– —-Arrival Time—- -Sender/Recipient——-
C922E4AC239 486 Thu Nov 3 11:52:28 root@xxx.yahoo.com
(connect to smtp.xxxx.com[11.22.33.44]:25: Connection timed out)
receive@yahoo.com

# postsuper -d C922E4AC239
postsuper: Deleted: 1 message

# postsuper -d ALL
postsuper: Deleted: 1 message