Tag Archives: determine

Determining SELinux mode before Oracle installation

SELinux (Security-Enhanced Linux) provides for additional OS layer security with a default installation. However, this added security can cause issues for installation of multiple software packages of which Oracle is one. This article shows how to determine the mode of SELinux before installing Oracle.

1. Logon to your server as root.
2. Execute the command getenforce or sesstatus to determine the current OS mode of SELinux.

[root@mylinux /]# /usr/sbin/getenforce
Permissive
[root@mylinux /]# /usr/sbin/sestatus
SELinux status: enabled
SELinuxfs mount: /selinux
Current mode: permissive
Mode from config file: permissive
Policy version: 21
Policy from config file: targeted
[root@mylinux /]#

3. This completes determination of SELinux mode before Oracle installation.

Larry J. Catt, OCP 9i, 10g
oracle@allcompute.com
www.allcompute.com

Determination of Components installed on your Oracle RDBMS.

Oracle provides the view DBA_REGISTRY which records all components installed on our RDBMS. This view provides more then just the components installed, but also: version, if it is valid, date of modification, etc. This information is very helpful in the administration of any RDBMS. This article covers the determination of what components are installed within our Oracle RDBMS.

1. Logon to your database server with SYSDBA privileges from your remote client.

C:\>sqlplus ljcatt/password5@orcl as sysdba

SQL*Plus: Release 10.2.0.1.0 – Production on Fri Feb 19 19:24:41 2010

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL>

2. Execute the following SQL statement: select comp_name, version, status, modified from DBA_REGISTRY;

SQL> column comp_name format a35
SQL> column version format a12
SQL> column status format a8
SQL> select comp_name, version, status, modified from DBA_REGISTRY;

COMP_NAME VERSION STATUS MODIFIED
———————————– ———— ——– ————
Oracle Database Catalog Views 10.2.0.4.0 VALID 08-SEP-2009 13:50:15
Oracle Database Packages and Types 10.2.0.4.0 INVALID 08-SEP-2009 13:50:15
Oracle Workspace Manager 10.2.0.4.3 VALID 08-SEP-2009 13:50:15
JServer JAVA Virtual Machine 10.2.0.4.0 VALID 08-SEP-2009 13:50:15
Oracle XDK 10.2.0.4.0 VALID 08-SEP-2009 13:50:15
Oracle interMedia 10.2.0.4.0 VALID 08-SEP-2009 13:50:15
Spatial 10.2.0.4.0 VALID 08-SEP-2009 13:50:15
Oracle Text 10.2.0.4.0 VALID 08-SEP-2009 13:50:15
Oracle Ultra Search 10.2.0.4.0 INVALID 08-SEP-2009 13:50:20
Oracle XML Database 10.2.0.4.0 VALID 08-SEP-2009 13:50:20
Oracle Application Server Metadata 10.1.2.0.2 VALID 07-JUL-2006 02:52:19
Repository Version-R

Oracle Application Server Distribut 10.1.2.0.2 VALID 06-JUL-2006 23:34:41
ed Configuration Management

Oracle Business Intelligence Discov 10.1.2.0.2 VALID 06-JUL-2006 23:34:43
erer

Oracle Workflow 10.1.2.0.2 VALID 06-JUL-2006 23:37:16
Oracle Application Server Integrati 10.1.2.0.2 VALID 06-JUL-2006 23:40:19
on B2B

Oracle Application Server Integrati 10.1.2.0.2 VALID 06-JUL-2006 23:40:25
on BAM

Oracle Application Server Certifica 10.1.2.0.2 VALID 06-JUL-2006 23:40:42
te Authority

Oracle Internet Directory 10.1.2.0.2 VALID 06-JUL-2006 23:41:16
Oracle Application Server Single Si 10.1.2.0.2 VALID 06-JUL-2006 23:43:27
gn-On

Oracle Application Server Portal 10.1.2.0.2 VALID 07-JUL-2006 00:01:41
Oracle Application Server Syndicati 10.1.2.0.2 VALID 07-JUL-2006 00:01:55
on Services

Oracle Application Server UDDI Regi 10.1.2.0.2 VALID 07-JUL-2006 00:02:06
stry

Oracle Application Server Web Clipp 10.1.2.0.2 VALID 07-JUL-2006 00:02:17
ing

Oracle Application Server Wireless 10.1.2.0.2 VALID 07-JUL-2006 00:08:24
Oracle Database Java Packages 10.2.0.4.0 VALID 08-SEP-2009 13:50:20

25 rows selected.

SQL>

This completes determination of components installed on your Oracle RDBMS.

Larry J. Catt, OCP 9i, 10g
oracle@allcompute.com
www.allcompute.com

Determine Oracle RDBMS component upgrade and modification history.

The Oracle RDBMS provides a history of upgrade and modification to database components through the view DBA_REGISTRY_LOG. This information can be used by the DBA to determine times which installation, upgrades, and modifications have been made to various RDBMS components. This article covers the use of the view DBA_REGISTRY_LOG.

1. Logon to your database server with SYSDBA privileges from your remote client.

C:\>sqlplus ljcatt/password5@orcl as sysdba

SQL*Plus: Release 10.2.0.1.0 – Production on Wed Feb 24 20:51:08 2010

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL>

2. Execute the following SQL statement: select * from DBA_REGISTRY_LOG;

SQL> column optime format a28
SQL> column namespace format a10
SQL> column comp_id format a10
SQL> column message format a10
SQL> set pagesize 100
SQL> select * from DBA_REGISTRY_LOG order by optime;
OPTIME NAMESPACE COMP_ID OPERATION MESSAGE
—————————- ———- ———- ———– ———-
18-JUL-09 03.13.00.026718 PM SERVER UPGRD_BGN
18-JUL-09 03.47.27.539499 PM SERVER CATPROC INVALID 10.2.0.4.0
18-JUL-09 03.48.35.621297 PM SERVER RDBMS INVALID 10.2.0.4.0
18-JUL-09 04.01.47.151968 PM SERVER JAVAVM VALID 10.2.0.4.0
18-JUL-09 04.04.58.654033 PM SERVER XML VALID 10.2.0.4.0
18-JUL-09 04.05.43.121515 PM SERVER CATJAVA VALID 10.2.0.4.0
18-JUL-09 04.07.27.818615 PM SERVER CONTEXT VALID 10.2.0.4.0
18-JUL-09 04.11.48.629069 PM SERVER XDB VALID 10.2.0.4.0
18-JUL-09 04.13.49.808540 PM SERVER OWM VALID 10.2.0.4.3
18-JUL-09 04.22.02.603685 PM SERVER ORDIM VALID 10.2.0.4.0
18-JUL-09 04.28.32.273345 PM SERVER SDO VALID 10.2.0.4.0
18-JUL-09 04.29.25.682363 PM SERVER WK INVALID 10.2.0.4.0
18-JUL-09 04.35.37.187381 PM SERVER UPGRD_END
18-JUL-09 05.45.01.775983 PM SERVER UTLRP_BGN
18-JUL-09 05.48.54.633250 PM SERVER UTLRP_END
18-JUL-09 07.06.22.748873 PM SERVER UTLRP_BGN
18-JUL-09 07.09.59.268882 PM SERVER UTLRP_END
19-JUL-09 01.16.55.416850 PM SERVER UTLRP_BGN
19-JUL-09 01.17.15.642776 PM SERVER UTLRP_END
13-AUG-09 12.56.24.513219 PM SERVER UTLRP_BGN
13-AUG-09 12.57.04.276009 PM SERVER UTLRP_END
08-SEP-09 01.27.01.558155 PM SERVER UTLRP_BGN
08-SEP-09 01.27.46.036417 PM SERVER UTLRP_END
08-SEP-09 01.30.25.121025 PM SERVER UTLRP_BGN
08-SEP-09 01.31.13.640322 PM SERVER UTLRP_END
08-SEP-09 01.37.39.576965 PM SERVER UTLRP_BGN
08-SEP-09 01.37.58.850834 PM SERVER UTLRP_END
08-SEP-09 01.43.30.395883 PM SERVER UTLRP_BGN
08-SEP-09 01.44.25.124050 PM SERVER UTLRP_END
08-SEP-09 01.50.01.872579 PM SERVER UTLRP_BGN
08-SEP-09 01.50.15.180842 PM SERVER UTLRP_END

31 rows selected.

SQL>

3. The information above can be used to determine dates of upgrades, installations, and recompilation of various ORACLE RDBMS components.

Larry J. Catt, OCP 9i, 10g
oracle@allcompute.com
www.allcompute.com