Installing Oracle 10.2.0.5 Enterprise Manager Grid Control on Linux and upgrading the repository database to 10.2.0.5
This note explains the procedure used to install 10.2.0.5 Grid Control on a Linux operating system (64 bit Red Hat Enterprise Linux Server release 5.6) as well as the steps taken to upgrade the repository database from the default 10.1.0.4 version to 10.2.0.5.
We will be using the silent installation method and not doing the installation using the OUI in interactive mode.
The steps can be broadly outlined as follows:
- Install any missing RPM’s especially the 32 bit RPM’s needed for OEM
- Create the users and groups
- Configure kernel parameters and hosts file
- Edit the response files needed for the silent installation
- Install Grid Control 10.2.0.3 (OMS and Agent) using response files
- Upgrade Grid Control to 10.2.0.5 using response files
- Configure database repository (10.1.0.4) and OMS using response files
- Upgrade repository database to 10g Release 2 (10.2.0.1) using DBUA
- Apply 10.2.0.5 patch to database software and upgrade repository database to 10.2.0.5
Download the software
Download the Grid Control software from the following link:
We need the 10.2.0.3 OEM Grid Control base release and the 10.2.0.5 patch release
- Linux_x86_64_Grid_Control_full_102030_disk1.zip
- Linux_x86_64_Grid_Control_full_102030_disk2.zip
- gc_x86_64_10205_part1of2.zip
- gc_x86_64_10205_part2of2.zip
Create a staging directory and unzip all the downloaded software there.
Install RPMS
We need to install some 32 bit RPMS as well even though the server is a 64 bit machine,.
We can use the following command to check if a particular version of an RPM has been installed or not.
rpm -qa --queryformat "%{N}-%{VERSION}.%{RELEASE} (%{ARCH})\n" | grep <package name>
For example:
rpm -qa --queryformat "%{N}-%{VERSION}.%{RELEASE} (%{ARCH})\n" | grep compat
All the RPM’s can be obtained from the Server sub-directory on the media CD.
Mount the CD
mount -t auto /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/Server
[root@kens-db-049 Server]# pwd
/mnt/cdrom/Server
[root@kens-db-049 Server]# rpm -ivh libXp-1.0.0-8.1.el5.i386.rpm
warning: libXp-1.0.0-8.1.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:libXp ########################################### [100%]
[root@kens-db-049 Server]# rpm -ivh libXp-1.0.0-8.1.el5.x86_64.rpm
warning: libXp-1.0.0-8.1.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:libXp ########################################### [100%]
[root@kens-db-049 Server]# rpm -ivh glibc-headers-2.5-58.x86_64.rpm
warning: glibc-headers-2.5-58.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:glibc-headers ########################################### [100%]
[root@kens-db-049 Server]# rpm -ivh glibc-devel-2.5-58.i386.rpm
warning: glibc-devel-2.5-58.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:glibc-devel ########################################### [100%]
[root@kens-db-049 Server]# rpm -ivh glibc-devel-2.5-58.i386.rpm
warning: glibc-devel-2.5-58.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
package glibc-devel-2.5-58.i386 is already installed
[root@kens-db-049 Server]# rpm -ivh gcc-4.1.2-50.el5.x86_64.rpm
warning: gcc-4.1.2-50.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:gcc ########################################### [100%]
[root@kens-db-049 Server]# rpm -ivh libstdc++-devel-4.1.2-50.el5.x86_64.rpm
warning: libstdc++-devel-4.1.2-50.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:libstdc++-devel ########################################### [100%]
[root@kens-db-049 Server]# rpm -ivh glibc-devel-2.5-58.x86_64.rpm
warning: glibc-devel-2.5-58.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:glibc-devel ########################################### [100%]
[root@kens-db-049 Server]# rpm -qa --queryformat "%{N}-%{VERSION}.%{RELEASE} (%{ARCH})\n" | grep compat
avahi-compat-libdns_sd-0.6.16.9.el5_5 (x86_64)
compat-libstdc++-296-2.96.138 (i386)
compat-libstdc++-33-3.2.3.61 (i386)
java-1.4.2-gcj-compat-1.4.2.0.40jpp.115 (x86_64)
compat-libgcc-296-2.96.138 (i386)
compat-libstdc++-33-3.2.3.61 (x86_64)
[root@kens-db-049 Server]# rpm -ivh compat-db-4.2.52-5.1.x86_64.rpm
warning: compat-db-4.2.52-5.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:compat-db ########################################### [100%]
[root@kens-db-049 Server]# rpm -ivh compat-db-4.2.52-5.1.i386.rpm
warning: compat-db-4.2.52-5.1.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:compat-db ########################################### [100%]
[root@kens-db-049 Server]# rpm -ivh openmotif22-2.2.3-18.x86_64.rpm
warning: openmotif22-2.2.3-18.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:openmotif22 ########################################### [100%]
[root@kens-db-049 Server]# rpm -ivh gdbm-1.8.0-26.2.1.i386.rpm
warning: gdbm-1.8.0-26.2.1.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:gdbm ########################################### [100%]
Create the User account (oracle) and the Group (dba)
[root@kens-db-049 Server]# /usr/sbin/groupadd dba
[root@kens-db-049 Server]# /usr/sbin/useradd -g dba oracle
[root@kens-db-049 Server]# passwd oracle
Changing password for user oracle.
New UNIX password:
Retype new UNIX password:
passwd: all authentication tokens updated successfully.
Configure the Kernel Parameters
Edit the /etc/sysctl.conf file
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default=262144
net.core.rmem_max=262144
net.core.wmem_default=262144
net.core.wmem_max=262144
[root@kens-db-049 Server]# /sbin/sysctl –p
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
kernel.msgmnb = 65536
kernel.msgmax = 65536
kernel.shmmax = 68719476736
kernel.shmall = 4294967296
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_default = 262144
net.core.wmem_max = 262144
Add the following lines to the /etc/security/limits.conf file:
* soft nproc 2047
* hard nproc 16384
* soft nofile 1024
* hard nofile 65536
Check the /etc/hosts file and ensure that it is defined properly
[root@kens-db-049 Server]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
10.6.20.49 kens-db-049.corporateict.domain kens-db-049
::1 localhost6.localdomain6 localhost6
Create the required directories for the ORACLE_HOME’s and for the repository database data files
[root@kens-db-049 u01]# mkdir app
[root@kens-db-049 u01]# chown oracle:dba app
[root@kens-db-049 u01]# su - oracle
[oracle@kens-db-049 ~]$ cd /u01/app/
[oracle@kens-db-049 app]$ mkdir oracle
[oracle@kens-db-049 app]$ cd oracle/
[oracle@kens-db-049 oracle]$ mkdir product
[oracle@kens-db-049 oracle]$mkdir /u01/app/oracle/oradata
Edit the response file
[oracle@kens-db-049 oracle]$ cd /u01/stage/GC_10203/Disk1/response
Take a backup of the response file em_with_new_db.rsp
[oracle@kens-db-049 oracle]$ cp em_with_new_db.rsp em_with_new_db.rsp.bak
Make the following changes to the response file
UNIX_GROUP_NAME="dba"
FROM_LOCATION="/u01/stage/GC_10203/Disk1/rdbms/Disk1/stage/products.xml"
BASEDIR="/u01/app/oracle/product"
INSTALLATION_NAME="oms10g"
s_gdbName="oramgnt.calm.wa.gov.au"
s_mountPoint="/u01/app/oracle/oradata"
s_operGroup="dba"
s_adminGroup="dba"
b_emailSelected=false
b_metalinkSelected=false
b_proxySelected=false
s_securePassword="password31"
s_securePasswordConfirm="password31"
b_lockedSelected=false
b_passwordsDifferent=false
b_passwordsSame=true
sl_adminPwds="password31"
sl_adminPwdsConfirm="password31"
s_reposPwd="password31"
s_reposPwdConfirm="password31"
Start the 10.2.0.3 Grid Control installation in silent mode using the edited response file
./runInstaller -noconfig -ignoreSysPrereqs -silent -responseFile /u01/stage/GC_10203/Disk1/response/em_with_new_db.rsp use_prereq_checker=false
Note- this error was encountered and fixed using the solution provided in the Metalink note below.
Silent Grid Control Installation with New DB, fails with "OUI-10150:Error The password for a database account cannot be null" [ID 942939.1]
Once the silent installation starts, we should be able to see output as shown below
Installation in progress (Thu Jun 30 15:40:56 WST 2011)
...... 39% Done.
...... 78% Done.
... 80% Done.
Install successful
Linking in progress (Thu Jun 30 15:41:22 WST 2011)
Link successful
Setup in progress (Thu Jun 30 15:41:34 WST 2011)
...... 100% Done.
Setup successful
End of install phases.(Thu Jun 30 15:41:35 WST 2011)
WARNING:A new inventory has been created in this session. However, it has not yet been registered as the central inventory of this system.
To register the new inventory please run the script '/home/oracle/oraInventory/orainstRoot.sh' with root privileges.
If you do not register the inventory, you may not be able to update or patch the products you installed.
The following configuration scripts need to be executed as the "root" user.
#!/bin/sh
#Root script to run
/home/oracle/oraInventory/orainstRoot.sh
/u01/app/oracle/product/db10g/allroot.sh
To execute the configuration scripts:
1. Open a terminal window
2. Log in as "root"
3. Run the scripts
As root, execute the orainstRoot.sh and allroot.sh scripts
[root@kens-db-049 u01]# /home/oracle/oraInventory/orainstRoot.sh
[root@kens-db-049 u01]# /u01/app/oracle/product/db10g/allroot.sh
Applying the 10.2.0.5 patch to Grid Control
At this stage we have only installed the base 10.2.0.3 OEM software and have not configured any components as yet. We will stop all the processes using opmnctl stopall command and then apply the 10.2.0.5 patch in the same silent manner.
[root@kens-db-049 u01]# su - oracle
[oracle@kens-db-049 ~]$ cd /u01/app/oracle/product/oms10g/opmn/bin
[oracle@kens-db-049 bin]$ ./opmnctl stopall
opmnctl: stopping opmn and all managed processes...
Create a staging directory for the 10205 patch software and unzip the same
[oracle@kens-db-049 stage]$ mkdir GC_10205
[oracle@kens-db-049 stage]$ mv gc_x86_64_10205_part1of2.zip ./GC_10205
[oracle@kens-db-049 stage]$ mv gc_x86_64_10205_part2of2.zip ./GC_10205
[oracle@kens-db-049 stage]$ cd GC_10205
[oracle@kens-db-049 GC_10205]$ ls
gc_x86_64_10205_part1of2.zip gc_x86_64_10205_part2of2.zip
[oracle@kens-db-049 GC_10205]$unzip gc_x86_64_10205_part1of2.zip
[oracle@kens-db-049 GC_10205]$unzip gc_x86_64_10205_part2of2.zip
Make a backup of the response file and make the following changes:
[oracle@kens-db-049 response]$ pwd
/u01/stage/GC_10205/3731593/Disk1/response
[oracle@kens-db-049 response]$ cp patchset.rsp patchset.rsp.bak
UNIX_GROUP_NAME="dba"
FROM_LOCATION="/u01/stage/GC_10205/3731593/Disk1/stage/products.xml"
ORACLE_HOME="/u01/app/oracle/product/oms10g"
b_softwareonly=true
b_startOMS=false
s_sysPassword="password31"
oracle.iappserver.st_midtier:szl_InstanceInformation=( "password31" )
Start the silent installation of the 10205 Grid Control patch
[oracle@kens-db-049 Disk1]$ pwd
/u01/stage/GC_10205/3731593/Disk1
[oracle@kens-db-049 Disk1]$ ./runInstaller -noconfig -silent -responseFile /u01/stage/GC_10205/3731593/Disk1/response/patchset.rsp
Run the root.sh – note, this script does not produce any output
[root@kens-db-049 u01]# /u01/app/oracle/product/oms10g/root.sh
Now patch the Agent10g Oracle Home.
We will use the same response file which we used to patch the oms10g Oracle Home.
We just need to change the Oracle Home location in the response file to point to the Agent Oracle Home.
Run the root.sh as root after the patch of the Agent Home completes.
Change
ORACLE_HOME="/u01/app/oracle/product/oms10g"
To
ORACLE_HOME="/u01/app/oracle/product/agent10g"
[oracle@kens-db-049 Disk1]$ ./runInstaller -noconfig -silent -responseFile /u01/stage/GC_10205/3731593/Disk1/response/patchset.rsp
[root@kens-db-049 u01]# /u01/app/oracle/product/agent10g/root.sh
Configure Grid Control Components
At this stage, we have installed the Grid Control 10.2.0.5 software. We now need to configure the repository database and the OMS.
[oracle@kens-db-049 bin]$ pwd
/u01/app/oracle/product/db10g/oui/bin
./runConfig.sh ORACLE_HOME=/u01/app/oracle/product/db10g ACTION=configure MODE=perform
This will create the 10.1.0.4 ORAMGNT repository database. We can see the various log files of the database creation process as well as the data files, redo log files and control files which have been created in the appropriate location which we have specified in the response file earlier.
[oracle@kens-db-049 bin]$ ls -l /u01/app/oracle/product/db10g/admin/oramgnt/create/
total 32
-rw-r--r-- 1 oracle dba 927 Jul 1 12:25 cloneDBCreation.log
-rw-r--r-- 1 oracle dba 377 Jul 1 12:24 CloneRmanRestore.log
-rw-r--r-- 1 oracle dba 40 Jul 1 12:25 lockAccount.log
-rw-r--r-- 1 oracle dba 211 Jul 1 12:25 oramgnt.log
-rw-r--r-- 1 oracle dba 391 Jul 1 12:25 postDBCreation.log
-rw-r--r-- 1 oracle dba 27 Jul 1 12:25 postScripts.log
-rw-r--r-- 1 oracle dba 1553 Jul 1 12:24 rmanRestoreDatafiles.sql
-rw-r--r-- 1 oracle dba 15 Jul 1 12:25 ultraSearchCfg.log
[oracle@kens-db-049 u01]$ cd app/oracle/oradata/oramgnt
[oracle@kens-db-049 oramgnt]$ ls
control01.ctl control02.ctl control03.ctl mgmt.dbf mgmt_ecm_depot1.dbf redo01.log redo02.log redo03.log redo04.log sysaux01.dbf system01.dbf temp01.dbf undotbs01.dbf users01.dbf
[oracle@kens-db-049 oramgnt]$ . oraenv
ORACLE_SID = [oracle] ? oramgnt
[oracle@kens-db-049 oramgnt]$ sqlplus sys as sysdba
SQL*Plus: Release 10.1.0.4.0 - Production on Fri Jul 1 12:29:51 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> select name from v$database;
NAME
------
ORAMGNT
After the repository database has been configured, we need to configure the OMS.
While configuring the OMS, we encountered this error:
error while loading shared libraries: libdb.so.2: cannot open shared object file: No such file or directory
To resolve theis error, we need to apply patch 6078836: RH5.0 / OEL5.0 CERT : SPECIAL LIBRARY NEEDED TO RUN OHS ON REDHAT5 MACHINE
[oracle@kens-db-049 ~]$ unzip p6078836_101330_LINUX.zip
Archive: p6078836_101330_LINUX.zip
creating: 6078836/
inflating: 6078836/libdb.so.2
inflating: 6078836/README.txt
[oracle@kens-db-049 ~]$ su -
Password:
[root@kens-db-049 ~]# cp /home/oracle/6078836/libdb.so.2 /usr/lib
[root@kens-db-049 lib]# ls -l libgdbm*
lrwxrwxrwx 1 root root 16 Jun 29 21:15 libgdbm.so.2 -> libgdbm.so.2.0.0
[root@kens-db-049 lib]# ls /usr/lib/libdb.so*
/usr/lib/libdb.so.2
[root@kens-db-049 lib]# ln -s /usr/lib/libdb.so.2 libgdbm.so.2.0.0
[root@kens-db-049 lib]# ls -l libgdbm.so.2.0.0
lrwxrwxrwx 1 root root 19 Jul 1 13:26 libgdbm.so.2.0.0 -> /usr/lib/libdb.so.2
[oracle@kens-db-049 oms10g]$ export OMS_HOME=/u01/app/oracle/product/oms10g
[oracle@kens-db-049 oms10g]$ export PERL5LIB=$OMS_HOME/perl/lib/5.6.1
$OMS_HOME/perl/bin/perl $OMS_HOME/sysman/install/ConfigureGC.pl /u01/app/oracle/product
The configuration of the OMS will also include the configuration of the agent as well and the last part of the configuration will include securing the agent and starting the agent.
We can view the logfiles of the OMS and Agent configuration which will be found at the following locations:
/u01/app/oracle/product/agent10g/cfgtoollogs/cfgfw
/u01/app/oracle/product/oms10g/cfgtoollogs/cfgfw
At this stage our 10.2.0.5 Grid Control OMS and Agent should be running. We can check the status of the OMS via the ./emctl status oms command from the OMS Oracle Home and the ./emctl status agent command run from the Agent Oracle Home.
Upgrading the Grid Control Repository Database to 10.2.0.5 from 10.1.0.4
The repository database installed out of the box is a 10.1.0.4 database (10g Release 1). We need to upgrade this to 10.2.0.5 (10g Release 2).
To upgrade from 10g R1 to 10gR2, we need to first install the base 10gR2 software (10.2.0.1) followed by the 10.2.0.5 patch. While we are installing and upgrading the software, we are also upgrading the database as well using the DBUA and catupgrd.sql script.
First stop Grid Control
[oracle@kens-db-049 DB_10201]$ cd /u01/app/oracle/product/oms10g/opmn/bin
[oracle@kens-db-049 bin]$ ./opmnctl stopall
opmnctl: stopping opmn and all managed processes...
Stop the 10.1.0.4 listener
[oracle@kens-db-049 cfgtoollogs]$ lsnrctl stop
LSNRCTL for Linux: Version 10.1.0.4.0 - Production on 01-JUL-2011 15:29:18
Copyright (c) 1991, 2004, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)))
The command completed successfully
Shutdown the database and take backup before the upgrade
Start the database
Download the 10.2.0.5 patch - p8202632_10205_Linux-x86-64.zip
Note – when we try and run the OUI, the 10201 installer will report an error stating that this is not a supported Operating System.
Checking Operating System version - Failed
Ignore the error and launch the installer with the -ignoreSysPrereqs option
While the upgrade is in progress, we can do a tail –f of the Oracle_Server.log file which can be found at the location shown below.
[oracle@kens-db-049 upgrade]$ pwd
/u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/dbua/oramgnt/upgrade
[oracle@kens-db-049 upgrade]$ ls -lrt
total 76
-rw-r----- 1 oracle dba 1913 Jul 1 15:33 upgrade.xml
-rw-r----- 1 oracle dba 3558 Jul 1 15:38 UpgradeResults.html
-rw-r----- 1 oracle dba 546 Jul 1 15:38 PreUpgrade.log
-rw-r----- 1 oracle dba 91 Jul 1 15:38 Oracle_Server.log
-rw-r----- 1 oracle dba 33533 Jul 1 15:39 trace.log
-rw-r----- 1 oracle dba 21587 Jul 1 15:39 sqls.log
SQL> select comp_name,status,version from dba_registry;
COMP_NAME
------
STATUS VERSION
------
Oracle Database Catalog Views
VALID 10.2.0.1.0
Oracle Database Packages and Types
VALID 10.2.0.1.0
Oracle Workspace Manager
VALID 10.2.0.1.0
Stop database and listener before applying the 10.2.0.5 patch
[oracle@kens-db-049 DB_10205]$ . oraenv
ORACLE_SID = [oracle] ? oramgnt
[oracle@kens-db-049 DB_10205]$ sqlplus sys as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Jul 4 12:43:47 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> quit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
[oracle@kens-db-049 DB_10205]$ lsnrctl stop
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 04-JUL-2011 12:44:22
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=kens-db-049.corporateict.domain)(PORT=1521)))
The command completed successfully
[oracle@kens-db-049 DB_10205]$ su -
Password:
[root@kens-db-049 ~]# /u01/app/oracle/product/10.2.0/db_1/root.sh
Running Oracle 10g root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/10.2.0/db_1
Enter the full pathname of the local bin directory: [/usr/local/bin]:
The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
Start the 10.2.0.5 listener
Upgrade the database to 10.2.0.5 using the STARTUP UPGRADE command and running the catupgrd.sql script
[oracle@kens-db-049 DB_10205]$ lsnrctl start
LSNRCTL for Linux: Version 10.2.0.5.0 - Production on 04-JUL-2011 12:50:16
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Starting /u01/app/oracle/product/10.2.0/db_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 10.2.0.5.0 - Production
System parameter file is /u01/app/oracle/product/10.2.0/db_1/network/admin/liste ner.ora
Log messages written to /u01/app/oracle/product/10.2.0/db_1/network/log/listener .log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=kens-db-049.corporateict .domain)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=kens-db-049.corporateict .domain)(PORT=1521)))
STATUS of the LISTENER
------
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.5.0 - Production
Start Date 04-JUL-2011 12:50:16
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/10.2.0/db_1/network/admin/list ener.ora
Listener Log File /u01/app/oracle/product/10.2.0/db_1/network/log/listen er.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=kens-db-049.corporateict.domain)(POR T=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))