Using Google Chrome?

Download my
free Chrome Extension, Power Notes Searcher, to make searching for and evaluating SAP notes, much easier.

Recent Posts

Tuesday, May 29, 2012

Intel CPU Flags from dmidecode on Linux

If you run the dmidecode command on a Linux machine, you get a nice list of the Intel CPU flags for the CPUs on your machine, plus a handy text description:

FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (Fast floating-point save and restore)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Hyper-threading technology)
TM (Thermal monitor supported)
SBF (Signal break on FERR)

Monday, May 21, 2012

Script Korn Shell to use Bold Output

Here's how you can use a normal Korn shell script to put out bold text on the screen providing the emulator you are using supports it:

#!/bin/ksh
$ bold=`tput smso`
$ regular=`tput rmso`

$ echo "${bold}Please type in your name: \c"
$ echo "${regular}OK"


See the man page for tput for a wild array of other capabilities.
It's possible you can even use tput to draw in different parts of the screen.
This could be used to create a drop-down box or a menu select box in KSH.
It can be done!  Honest!

Monday, May 14, 2012

SQLPLUS ORA-01031: insufficient privileges as SYSDBA

This issue is commonly caused by the operating system group you are currently using, not having the correct permissions inside the Oracle binaries.  On UNIX, the Oracle binaries are always re-compiled after installation, with the group name of the "dba" group.  If your current user is not a member of that group, then you can't use "AS SYSDBA".  It's a protection measure to restrict the O/S users that can access the database "AS SYSDBA".
On Windows, the group is created as a local Windows group into which you need to add your user account (or group).  The local group name is not compiled into the Oracle binaries.

In UNIX, it's possible when using SQL*Plus to connect to an idle instance AS SYSDBA, you get “ORA-01031: insufficient privileges” even though you have changed the $ORACLE_HOME/rdbms/lib/config.c file database group to match your UNIX group and re-compiled the Oracle binaries.

As specified in Oracle note 400459.1, you should move the old $ORACLE_HOME/rdbms/lib/config.o to config.o.old and then re-link oracle using “relink oracle”.

Check that a new config.o file is generated, before performing the “relink all”.

For some reason, using relink doesn't always seem to trigger a rebuild of config.o.

Friday, May 11, 2012

IBM WebSphere IHS Plugin Hostname Cookies Conundrum

Whilst attempting to set up IBM WebSphere with a remote IBM HTTP Server (IHS) using the WAS Plugin, I was hitting an issue whereby cookies would only be served to the client browser when accessing the IHS server using the real host name and not the DNS alias I had created.

After 2 days of trying different combinations of configuration, I finally found this article here:

The host name DNS alias I had created used underscores.
Whilst this is permitted in the system, it is not a valid host name accord to the IETF RFCs, and therefore no cookies are served/retrievable by the WebSphere application server.

In short, always use hyphens instead of underscores in your WAS or IHS DNS aliases.

Thursday, May 10, 2012

Checking Sun/Oracle GlassFish Server Version

Here's how to check the version of Sun/Oracle GlassFish application server which is installed in a Linux environment:

From the bin directory of the GlassFish binary home directory:


$ asadmin version
Version = Sun GlassFish Enterprise Server v2.1
Command version executed successfully.

Monday, May 07, 2012

IBM WebSphere 6.1.0 GUI Install on RHEL 4.5

If you have been given the opportunity to install IBM WebSphere 6.1.0 on RedHat Enterprise Linux 4.5, then you may be wondering why you can't get the GUI installer to launch using the X-Windows terminal you've painstakingly enabled.

Well, the answer is simple; unless you are on the console, then you can't.  That is, you must be on DISPLAY ":0.0".
If your sys admin is denying you access, or it's a VM and you're not allowed console access, then you're also stuck.

The only other solution is to use the response files provided in the install directory of the installation media.
Customise the response file and then run the install.sh in silent mode.
There is a very helpful IBM help page on how to do all of this here: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.base.doc/info/aes/ae/tins_runSilent.html

Good luck.

ps. It presents a more systematic, repeatable approach to installing an environment if you use response files.  No mistakes, same every time.
What's more, you can also silently install the "UpdateInstaller" and also the FixPacks.