Author Archives: alesk

Upgrading Oracle Linux 6.4 to 6.5 (plus UEK2 to UEK3)

Steps for upgrading Oracle Linux 6.4 to 6.5 and UEK2 kernel to UEK3:

// Download and replace yum repository file with the new one!
# cd /etc/yum.repos.d
# rm public-yum-ol6.repo 
# export http_proxy=proxy.acme.com:80   (optional)
# wget http://public-yum.oracle.com/public-yum-ol6.repo
# nano public-yum-ol6.repo
// find section [ol6_UEKR3_latest] and set Enabled=1
# yum update
# reboot

That’s it. Don’t forget to set Enabled=1 in ol6_UEKR3 section, unless you don’t want to upgrade UEK2 kernel to version UEK3.

Installing and configuring ArcServe 16.1 agent on Fedora 20

A quick note about CA ArcServe Universal Agent 16.1 installation of Fedora 20 (x64):

$ sudo mount -o loop  ArcServe16SP1.iso /mnt/dvd
$ cd /mnt/dvd/ArcServe16SP1/DataMoverandAgent/Linux
$ sudo ./install

You’ll be greeted with:

Cannot identify your Linux distribution or it is not yet supported.

Important! You are installing UNIX and Linux Data Mover on a system that is 
running an operating system that is not currently supported by ARCserve. 
To check the latest list of supported operating systems, go to ca.com/support. 
If you continue, be aware that unexpected results could occur.

Do you want to continue? (YES/NO):(default: NO) YES

...
Read the license terms
...

ENTER YES (Y) TO ACCEPT THE TERMS AND CONDITIONS OF THIS AGREEMENT AS SET 
FORTH ABOVE AND PROCEED WITH THE INSTALLATION PROCESS.

ENTER NO (N) TO HALT THE INSTALLATION PROCESS.

Please enter your choice:[Y|N] (default: N) Y


Do you want to view the installation notes? (y/n):(default: y) n

Preparing for the installation, please wait...| 

The following products are available to install:


#####################################################################
#       ARCserve Installation Options
#####################################################################
#  1. CA ARCserve Backup for Linux Data Mover                               (ABdatmov)
#  2. CA ARCserve Backup for Linux Client Agent                             (ABagntux) 
#  3. CA ARCserve Backup for Linux Agent for Oracle                         (ABora)
#  4. CA ARCserve Backup for Linux Enterprise Option for SAP R/3 for Oracle (ABsap)
#                                                                       
#  0. Quit                                                              
#####################################################################

Note: Client Agent will be installed automatically if Data Mover is selected.
Please enter your selection separated by "," For example: 1,2. Press Enter to select the default components (E.g. Data Mover, Client Agent)...

Your choices are: 2

lease specify the installation path of Client Agent for Linux                   (default: /opt/CA): <ENTER>

The following program will be installed:

  . Install Client Agent for Linux                     (ABagntux)      ==> [ /opt/CA/ABuagent ]

Are you sure? (y)es/(n)o/(q)uit: y


All CA ARCserve Backup agents can be configured for automatic startup 
and shutdown as part of your operating system startup and shutdown.
Do you want to enable automatic startup and shutdown of all backup agents? [y|n]:(default: y) y

Checking available space in /opt/CA                           ==> [ OK ]


Installation log file is                           ==> [ /tmp/ARCserveInstall123113-0938.log ]

    Common Agent Module                      (ABcmagt)       ==> [ INSTALL SUCCESSFUL ]
    Client Agent for Linux                   (ABagntux)      ==> [ INSTALL SUCCESSFUL ]

###########################################################################

    Installation log file is                      ==> [ /tmp/ARCserveInstall123113-0938.log ]
###########################################################################

Do you want to view the readme? [y|n]:(default: y) n

Configuration:

[alesk@fedora20 CA]$ ls -al /opt/CA
total 8
drwxr-xr-x  4 root root   35 Dec 31 09:42 .
drwxr-xr-x. 6 root root   62 Dec 31 09:42 ..
drwxr-xr-x  4 root root 4096 Dec 31 09:42 ABcmagt
drwxr-xr-x  4 root root 4096 Dec 31 09:42 ABuagent


$ sudo nano /opt/CA/ABcmagt/agent.cfg

[0]
#[LinuxAgent]
NAME      LinuxAgent
VERSION   16.0
HOME      /opt/CA/ABuagent
#ENV      CA_ENV_DEBUG_LEVEL=4
ENV       AB_OS_TYPE=FEDORAPROJECT_X86_64
ENV       UAGENT_HOME=/opt/CA/ABuagent
#ENV       LD_ASSUME_KERNEL=2.4.18
ENV       LD_LIBRARY_PATH=/opt/CA/ABcmagt:$LD_LIBRARY_PATH:/SharedComponents/lib:/opt/CA/ABuagent/lib
ENV       SHLIB_PATH=/opt/CA/ABcmagt:$SHLIB_PATH:/SharedComponents/lib:/opt/CA/ABuagent/lib
ENV       LIBPATH=/opt/CA/ABcmagt:$LIBPATH:/SharedComponents/lib:/opt/CA/ABuagent/lib
BROWSER   cabr
AGENT     uagentd
MERGE     umrgd
VERIFY    umrgd
NOPASSWORD                      <<< ADDED
CAUSER  A:alesk N:root          <<< ADDED

[36] DISABLED
#[ABcmagt]
NAME      ABcmagt               
HOME      /opt/CA/ABcmagt
NO_HOSTS_EQUIV=1                <<< ADDED
#TCP_PORT  6051
#UDP_PORT  6051
#UDP_BCAST_PORT  41524
#DOS_MAXITEMS    1000
#DOS_DEFAULTTIMEOUT   30

As you can see all that I did was a couple of changes in agent.cfg file:

NOPASSWORD .... enable single user mode wihch is needed for ACLs
CAUSER     .... Access Control List (A=Allow access, N=Deny access)
NO_HOSTS_EQUIV=1   ... disable UNIX/Linux host equiv. authentication

Commands to start/stop CA agent:

$ sudo /etc/init.d/bab_agent start
$ sudo /etc/init.d/bab_agent stop

PostgreSQL ODBC driver installation on Linux

After I installed PostgreSQL 9.3 on my Fedora 20 I soon realized that I need PostgreSQL ODBC as well, because I’ll be using Oracle DG4ODBC to connect to PostgreSQL cluster.

I could simply install PostgreSQL ODBC with yum:

$ sudo yum install postgresql-odbc 

…and this is perhaps the best option on a long run (in general I prefer using yum as much as possible, even if I sacrifice of not having the latest version of some software), but in this particular case I had a good reason to install the very last version from source.

First download the latest PostgreSQL ODBC driver from:
http://www.postgresql.org/ftp/odbc/versions/src/

$ wget http://ftp.postgresql.org/pub/odbc/versions/src/psqlodbc-09.03.0100.tar.gz
$ tar -xzvf psqlodbc-09.03.0100.tar.gz
$ ./configure --with-libpq=/usr/pgsql-9.3 --disable-openssl
$ make
$ sudo make install

Installation will end with the following instructions (excerpt):

Libraries have been installed in:
   /usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.

A quick check if libraries are indeed there:

$ ls -la /usr/local/lib
total 1960
drwxr-xr-x.  2 root root      44 Dec 29 16:08 .
drwxr-xr-x. 13 root root    4096 Dec 25 22:52 ..
-rwxr-xr-x.  1 root root     971 Dec 29 16:08 psqlodbcw.la
-rwxr-xr-x.  1 root root 1996735 Dec 29 16:08 psqlodbcw.so

Upgrade Fedora 19 to 20 (KDE spin)

This is a short note about upgrading my laptop with Fedora 19 (KDE spin) to Fedora 20. On this laptop originally run Fedora 17, which was upgraded with fedup tool to 18 and later on to 19. Since both upgrades in the past were done without a big drama, I decided to repeat the exercise with Fedora 20. If you’re not familiar with fedup I would recommend reading official documentation. Before I started with the upgrade I run “sudo yum update” on Fedora 19 to refresh the system with the latest packages, then I followed the following steps:

1) Update fedup tool
Make sure you have up to date version of fedup installed, version 0.7, which was installed on my Fedora 19 didn’t work due to a known bug.

$ sudo yum --enablerepo=updates-testing update fedup

2) Prepare system for upgrade

$ sudo fedup --network 20

This step will download all the packages and prepare upgrade “transaction”. In my case over 2400 packages were downloaded (it took close to 90 minutes on 50Mbps internet connection, be patient, it can take hours). During download fedup just stopped downloading without
reporting any error, simply returning to the prompt. Fortunately you can repeat the command again and it’ll continue downloading packages from where it stopped. Overall, I repeated fedup command three times before I was notified that I can reboot.

3) Reboot and wait for upgrade to complete

Eventually fedup will ask you to reboot. You’ll see “System upgrade” option in Grub menu that you should select after you reboot. Fedup will also give you a warning if some repository is missing, for example I later on disabled Dropox repository (the first time you run yum you’ll be notified of any repository not (yet) available for Fedora 20).
Another thing you’ll notice while running yum are warnings that some group is missing. Just ignore the warnings, it’s known bug (see section 3.3) in Fedora 20.

$ sudo reboot 

Be patient, this will take awhile (another 90 minutes on my laptop with ~2400 packages).
And that’s it, after 90 minutes and last reboot I had working Fedora 20 on my laptop.

4) Quirk
Since Fedora 20 obsoleted old Network Management applet and replaced it with the new one, at first I didn’t even notice that UMTS modem was not showing at all in new Network Manager. After inserting broadband modem USB stick I checked with lsusb if modem is recognized by the kernel and it showed as Globtrotter HSDPA modem. It took me some time to figure out that the reason was disabled ModemManager service, so I fixed the issue with:

$ sudo systemctl start ModemManager.service
$ sudo systemctl enable ModemManager.service

That’s more or less it. So far I didn’t notice anything else that doesn’t work. All I can say is that I’m impressed by fedup capabilities, I’m sure the number of glitches will drop with the maturity of the product.

How to fix default (ugly) fonts in SQL Developer on Linux

Here is a short note on how to (at least) partially fix ghastly default fonts that SQL Developer is cursed with it on Linux. After I installed the recently released SQL Developer 4.0 on my Fedora 19 workstation, I immediately increased the font size from 11 points to 14 by editing:

$ nano ~/.sqldeveloper/system4.0.0.13.80/o.sqldeveloper.12.2.0.13.80/ide.properties

# To modify the font size for all look-and-feels in all locales, set
# the Ide.FontSize property.  For example:
Ide.FontSize=14

…plus, I changed the way how Java is smoothing fonts by adding two variables in product.conf file:

$ nano ~/.sqldeveloper/4.0.0/product.conf

AddVMOption -Dswing.aatext=true
AddVMOption -Dawt.useSystemAAFontSettings=lcd

Make sure that SQL Developer is not running while editing product.conf file, because it’ll overwrite your changes at exit!

And here is, somehow prettier SQL Developer IDE:

sqldeveloper-fonts-linux