How to Check Linux Version?

Advertisements

While researching an old install for an upgrade system requirement compliance, I discovered that I b=need to validate which Linux version was installed.  So, here is a quick note on the command I used to validate which version of Linux was installed.

Command

  • cat /etc/os-release

Example Output of the command “os-release” file

How to install locate command in Linux Redhat and Centos

Advertisements

To install the locate command (mlocate) in Redhat or Centos, use the ’YUM’ command, install function. 

  • Logon as ‘root’ or use with ‘sudo’ permissions
  • Then, run a ’man’ command to confirm that the locate command is not already installed: ‘man locate’

Example ‘man’ command (as root user)

[root@blog-server ~]# man locate

  • If the ’man’ documentation page returns, then it is already installed.  If no ’man’ documentation page is returned, then run the ‘yum install’ command.
  • Run the ‘yum install’ command as ‘root’ or ‘sudo’ user:

Example ‘yum install’ command (as root user)

[root@blog-server ~]# yum install mlocate

Example ‘yum install’ command (as sudo user)

[root@blog-server ~]# sudo yum install mlocate

Then run the [root@data-server ~]# updated

Example Run ‘updatedb’ Command (as Root user)

[root@blog-server ~]# updated

Example Run ‘updatedb’ Command (as sudo user)

[root@blog-server ~]# sudo updatedb

How To quit the Linux vi editor without saving changes

Advertisements

To quit the Linux ’vi’ editor without saving any changes which have been made:

To Exit the insert or append mode

  1. From within insert or append mode, press the ‘Esc‘ key.

To Enable VI Command Line

  1. Press the ‘:’ (colon) Key. The cursor should reappear in the lower-left corner of the screen beside a colon prompt.
  2. Then, Enter the ‘q!’ Command and press the ‘Enter’ Key.

Example VI Command Line

: q!

This will quit the Linux VI editor, and all changes the document made in this session will be lost.

Useful Links – AIX

Advertisements

Here are a few references for IBM AIX/UNIX, which may be helpful.

AIX Comand Documentations

What is AIX?

Advertisements

AIX (Advanced Interactive eXecutive) is an operating system developed by IBM for business all across the world that needs data metrics that can keep up with the ever-changing scope of business in today’s world. AIX is a version of UNIX. AIX is designed to work on a number of computer platforms from the same manufacturer. On its launch, the system was designed for IBM’s RT PC RISC workstation.

User interface

AIX was developed with Bourne Shell as the default shell for three versions of the OS. Afterwards, it was changed to KornShell going forward from version 4. The OS uses Common Desktop Environment (CDE) as the default user interface for graphics. The System Management Interface Tool on the OS allows users to access the menu using a hierarchy of commands instead of the command line. 

Compatible systems

The operating system works on a number of hardware platforms. The initial OS was designed for the IBM RT PC and used a microkernel that controlled the mouse, disk drives, keyboard, and display. This allowed users to use all these components between operating systems by the use of a hot key-the alt+tab combination. The OS was also fitted on newer systems such as the IBM PS/2 series, IDM mainframes, AI-64 systems and can also be used with the Apple’s server network. AIX is commonly used on IBM’s 64-bit POWER processor and systems. AIX can run most Linux applications (after recompiling) and has full support for Java 2.

Since its introduction to computer infrastructure, the operating system has undergone a lot of upgrades with five versions released since 2001. The latest version of the software is the AIX 7.2. All of these come with a high tech security system and fast uptimes.

As an operating system AIX has become popular with students who learn quickly by working on AIX projects live. Working professionals have also been attracted by the dependability of the system and the intuitive that is part of its design.

Related References

Netezza – JDBC ISJDBC.CONFIG Configuration

Advertisements

This jdbc information is based on Netezza (7.2.0) JDBC for InfoSphere Information Server11.5.  so, here are a few pointers for building an IBM InfoSphere Information Server (IIS) isjdbc.config file.

Where to place JAR files

For Infosphere Information Server installs, as a standard practice, create a custom jdbc file in the install path.  And install any download Jar file not already installed by other applications in the jdbc folder. Usually, jdbc folder path looks something like this:

  • /opt/IBM/InformationServer/jdbc

CLASSPATH

  • nzjdbc3.jar
  • Classpath must have complete path and jar name

CLASS_NAMES

  • netezza.Driver

JAR Source URL

IBM Netezza Client Components V7.2 for Linux

File name

  • nz-linuxclient-v7.2.0.0.tar.gz

Unpack tar.gz

  • tar -zxvf nz-linuxclient-v7.2.0.0.tar.gz -C /opt/IBM/InformationServer/jdbc

DB2 DEFAULT PORT

  • 1521

JDBC URL FORMAT

  • jdbc:netezza://:/

JDBC URL EXAMPLE

  • jdbc:netezza://10.999.0.99:5480/dashboard

isjdbc.config EXAMPLE

CLASSPATH=usr/jdbc/nzjdbc3.jar;/usr/jdbc/nzjdbc.jar;/usr/local/nz/lib/nzjdbc3.jar;

CLASS_NAMES= org.netezza.Driver;

Isjdbc.config FILE PLACEMENT

  • /opt/IBM/InformationServer/Server/DSEngine

Related References

SQL Server JDBC ISJDBC.CONFIG Configuration

Advertisements

This jdbc information is based on Oracle Database 11g Release 2, (11.2.0.4) JDBC for InfoSphere Information Server11.5, and ReedHat Linux 6.  so, here are a few pointers for building an IBM InfoSphere Information Server (IIS) isjdbc.config file.

Where to place JAR files

For Infosphere Information Server installs, as a standard practice, create a custom jdbc file in the install path.  And install any download Jar file not already installed by other applications in the jdbc folder. Usually, jdbc folder path looks something like this:

  • /opt/IBM/InformationServer/jdbc

CLASSPATH

  •  sqljdbc.jar
  •  sqljdbc4.jar
  •  sqljdbc41.jar
  •  sqljdbc42.jar
  • Classpath must have complete path and jar name

CLASS_NAMES

  • microsoft.jdbc.sqlserver.SQLServerDriver;com.microsoft.sqlserver.jdbc

JAR Source URL

DEFAULT PORT

  • 1433

JDBC URL FORMAT

  •  jdbc:microsoft:sqlserver://HOST:1433;DatabaseName=DATABASE

JDBC URL EXAMPLE

  • jdbc:sqlserver://RNO-SQLDEV-SVR1DEV01:55198;databaseName=APP1;

isjdbc.config EXAMPLE

CLASSPATH=/opt/IBM/InformationServer/jdbc/sqljdbc_3.0/enu/sqljdbc4.jar;/opt/IBM/InformationServer/jdbc/sqljdbc_3.0/enu/sqljdbc.jar;/opt/IBM/InformationServer/jdbc/sqljdbc_3.0/enu/sqljdbc41.jar;/opt/IBM/InformationServer/jdbc/sqljdbc_3.0/enu/sqljdbc42.jar;

CLASS_NAMES=com.microsoft.jdbc.sqlserver.SQLServerDriver;com.microsoft.sqlserver.jdbc

Isjdbc.config FILE PLACEMENT

  • /opt/IBM/InformationServer/Server/DSEngine

Related References

Vendor Reference Link:

Oracle JDBC ISJDBC.CONFIG Configuration

Advertisements

This jdbc information is based on Oracle Database 11g Release 2 (11.2.0.4), on a RAC (Oracle Real Application Clusters), JDBC for InfoSphere Information Server11.5 on Red Hat Linux.  so, here are a few pointers for building an IBM InfoSphere Information Server (IIS) isjdbc.config file.

Where to place JAR files

For Infosphere Information Server installs, as a standard practice, create a custom jdbc folder in the install path and copy the jar file into the folder (not install activity required).   Usually, jdbc folder path looks something like this:

  • /opt/IBM/InformationServer/jdbc

JAR Source URL

  • In this example, we used the jar files from the client install, but if you want to skip the client install you can download the drivers here: Oracle JDBC Drivers

Oracle DEFAULT PORT

  • 1521

JDBC URL FORMAT

  • jdbc:oracle:thin:@//:/ServiceName

or

  • jdbc:oracle:thin:@<host>:<port>:<SID>

JDBC URL EXAMPLE

  • jdbc:oracle:thin:@//RAC01-scan:1521/DW

Create And Place A jdbc configuration file

The Isjdbc.config file needs to be placed in the DSEngine directory:

Isjdbc.config File Path

  • /opt/IBM/InformationServer/Server/DSEngine

isjdbc.config Example

CLASSPATH=/opt/app/oracle/product/11.2.0/client_1/jdbc/lib/ojdbc6.jar;

CLASS_NAMES=oracle.jdbc.OracleDriver

isjdbc.config Properties Notes

CLASSPATH

  • jar
  • Classpath must have complete path and jar name

CLASS_NAMES

  • oracle.jdbc.OracleDriver

Related References