1. Generate nu.novell.com credentials on novell support portal
2. Download SMT iso from novell
3. install and setup
4. a2enmod ssl
https://www.suse.com/documentation/smt11/book_yep/data/book_yep.html
As title, It is a memo of my daily work, it won't be very detail but enough to retrieve what I have to.
Tuesday, November 19, 2013
Monday, November 18, 2013
Reclaim VMDK space from thin disk on ESXi 5.0/5.1/5.5
There are 2 methods but both need you system to power down.
1. Use VMware convertor, it is free, but need to rename your VM and GUID also changed. It is not a very good choice if you have all those VM backup software that recognize GUID instead of VM Name (However, I have tested both, it give the best result for reclaiming space, especially some space in LVM will not be able to be reclaimed by method 2 )
2. Do it Manually in 2 steps
- zero out all empty space (Windows sdelete, Linux secure-delete)
Linux: execute "sfill -llfzv /" after installing secure-delete (you might want to zero out swap also)
Windows: "sdelete -z" (downloaded from microsoft technet)
- hole punching using vmkfstools in ESXi
SSH into ESXi host and run this command: vmkfstools -K <vmdkname>
**if space not able to reclaim, try storage vmotion to thick then thin to force it happens.
1. Use VMware convertor, it is free, but need to rename your VM and GUID also changed. It is not a very good choice if you have all those VM backup software that recognize GUID instead of VM Name (However, I have tested both, it give the best result for reclaiming space, especially some space in LVM will not be able to be reclaimed by method 2 )
2. Do it Manually in 2 steps
- zero out all empty space (Windows sdelete, Linux secure-delete)
Linux: execute "sfill -llfzv /" after installing secure-delete (you might want to zero out swap also)
Windows: "sdelete -z" (downloaded from microsoft technet)
- hole punching using vmkfstools in ESXi
SSH into ESXi host and run this command: vmkfstools -K <vmdkname>
**if space not able to reclaim, try storage vmotion to thick then thin to force it happens.
Friday, November 8, 2013
Install Oracle 12c on SLES 11SP3
/etc/fstab
none /dev tmpfs remount,size=6G 0 0
zypper install binutils gcc43 gcc-c++ glibc glibc-devel ksh libaio libaio-devel libcap1 libstdc++33 libstdc++43 libstdc++46 libgcc46 make sysstat
Install software only during when running ./runInstaller, do not create database
When it prompt for running root.sh script
Open terminal (using oracle owner account)
1. su root (don't use "su -" )
2. Execute those script required
3. Back to finish the installer
4. run ./netca to create LISTENER
5. run ./dbca to create your DB
For init script
you can install orarun packet using YaST or zypper
you have to modify /etc/sysconfig/oracle to select what service you want to start
/etc/init.d/oracle
1. Add 11g and 12c version support for startdb part
ORACLE_VERSION=`$ORACLE_HOME/bin/sqlplus -v | awk '{split($3, V, "."); print V[1]}'`
if [ $ORACLE_VERSION = "11" ]; then
to
ORACLE_VERSION=`$ORACLE_HOME/bin/sqlplus -v | awk '{split($3, V, "."); print V[1]}'`
if [ $ORACLE_VERSION = "11" ] || [ $ORACLE_VERSION = "12" ]; then
2.Change
if [ ! -z "$ORACLE_HOME" -a ! -d "$ORACLE_HOME" ]; then
to
if [ ! -z "$ORACLE_HOME" -a -d "$ORACLE_HOME" ]; then
3.
# Set Intelligent Agent Start/Stop
AGENT_VERSION="unknown"
to
ORACLE_VERSION=`$ORACLE_HOME/bin/sqlplus -v | awk '{split($3, V, "."); print V[1]}'`
# Set Intelligent Agent Start/Stop
AGENT_VERSION="unknown"
AGENT_VERSION="unknown"
Friday, November 1, 2013
After Cisco UCS Manager Upgrade to 2.1.X , FC and SAN disconnected due to Zoning behavior changed
How dare Cisco totally changed FC Zoning behavior in from 2.0 to 2.1 without warning, migration wizard or default allowing policy!!!!
It is totally not possible to upgrade to 2.1 without putting the whole SAN offline!
Once UCS Manager reboot according to follow manual, it block all FC traffic from Blade to SAN Storage.
And Cisco didn't add any warning here telling FC Zoning behavior will be changed. It still telling in the manual could upgrade without affecting service.
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/upgrading/from2.0/to2.1/b_UpgradingCiscoUCSFrom2.0To2.1.html#concept_C70F7CFF31AC46C7AD03E8022299C808
Please study complete about this sample config before upgrading to UCS Firmware bundle 2.1
http://www.cisco.com/en/US/products/ps11350/products_configuration_example09186a0080c0a508.shtml#anc7
It is totally not possible to upgrade to 2.1 without putting the whole SAN offline!
Once UCS Manager reboot according to follow manual, it block all FC traffic from Blade to SAN Storage.
And Cisco didn't add any warning here telling FC Zoning behavior will be changed. It still telling in the manual could upgrade without affecting service.
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/upgrading/from2.0/to2.1/b_UpgradingCiscoUCSFrom2.0To2.1.html#concept_C70F7CFF31AC46C7AD03E8022299C808
Please study complete about this sample config before upgrading to UCS Firmware bundle 2.1
http://www.cisco.com/en/US/products/ps11350/products_configuration_example09186a0080c0a508.shtml#anc7
Subscribe to:
Posts (Atom)