Toad Extension for Eclipse 2.3.4 Community Edition:

• DellToadExtensionForEclipse_CE_2.3.4_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.3.2 Community Edition:

• DellToadExtensionForEclipse_CE_2.3.2_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.3.0 Community Edition:

• DellToadExtensionForEclipse_CE_2.3.0_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.2.4 Community Edition:

• DellToadExtensionForEclipse_CE_2.2.4_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.2.3 Community Edition:

• DellToadExtensionForEclipse_CE_2.2.3_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.2.1 Community Edition:

• DellToadExtensionForEclipse_CE_2.2.1_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.2.0 Community Edition:

• DellToadExtensionForEclipse_CE_2.2.0_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.1.3 Community Edition:

• DellToadExtensionForEclipse_CE_2.1.3_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.1.2 Community Edition:

• DellToadExtensionForEclipse_CE_2.1.2_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.1.1 Community Edition:

• DellToadExtensionForEclipse_CE_2.1.1_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.1.0 Community Edition:

• DellToadExtensionForEclipse_CE_2.1.0_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.0.4 Community Edition:

• DellToadExtensionForEclipse_CE_2.0.4_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.0.3 Community Edition:

• DellToadExtensionForEclipse_CE_2.0.3_ReleaseNotes_Revision2_ENG.pdf

Toad Extension for Eclipse 2.0.2 Community Edition:

• DellToadExtensionForEclipse_CE_2.0.2_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.0.1 Community Edition:

• DellToadExtensionForEclipse_CE_2.0.1_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 2.0.0 Community Edition:

• DellToadExtensionForEclipse_CE_2.0.0_ReleaseNotes_Revision1_ENG.pdf

Toad Extension for Eclipse 1.9.3 Community Edition:

• ReleaseNotes_DellToadExtensionForEclipse_1.9.3_CE_Revision1.pdf

Introduction

Recently Oracle updated the MOS note “Common Exadata security scan findings (Doc ID 1405320.1)" related to Java vulnerabilities. In the October 2015 CPU, there were several Java vulnerabilities addressed. Many of these also affected Exadata images 12.1.2.x.x. Some of the vulnerabilities were very severe (CVSS score 10.0). 

Here is a snippet of the information found in “Common Exadata security scan findings (Doc ID 1405320.1)":

This Critical Patch Update contains 25 new security fixes for Oracle Java SE.  24 of these vulnerabilities may be remotely exploitable without authentication, i.e., may be exploited over a network without the need for a username and password. Some of the vulnerabilities were very severe (CVSS score 10.0). 

The Java vulnerabilities affects the Exadata image versions 12.1.2.1.0 and later.

The Exadata database server and Exadata Storage cells running Exadata image version 12.1.2.1.0 includes the JDK 7 package installed as an RPM. To update the RPM, first obtain the latest version by referring to Note 1439822.1. Make sure you look for the JDK 7. DO NOT use JDK 8 or later.

About Management Server (MS) process

•  It helps execute CELLCLI commands
• It provides Java interface to Enterprise Manager 12c Plugins.
• You can't execute CELLCI commands if MS process is down.

Managing MS process:

To stop MS process

# cellcli -e alter cell shutdown services ms

To start MS process

# cellcli -e alter cell startup services ms

To restart MS process

# cellcli -e alter cell restart services ms

In this article I am going to demonstrate how to update JDK version on an Exadata X2-2 running ESS version 12.1.2.2.0.

Assumption

• root user password for Compute nodes and Storage Cells
• root user equivalence must be setup between compute nodes and storage cells.
• No outage is required for database and storage cell services.

Environment

Procedure to update JDK on Exadata Compute nodes and Storage cells

Unless otherwise stated all the steps will be executed as 'root' user.

Step I - Download and copy latest JDK 7 package to Exadata Compute node and Storage cell

• Using the note [1439822.1]: All Java SE Downloads on MOS download the latest JDK 7 package

Here is the directly link

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=116578518457933&id=1439822.1&_adf.ctrl-state=15es4f8nb6_53

• As root user, login to Exadata Compute node 1 and perform the following steps

[root@oraclouddbadm01 jdk]# mkdir -p /u01/app/oracle/software/jdk

[root@oraclouddbadm01 jdk]# cd /u01/app/oracle/software/jdk

• Using WinScp or similar utility copy the JDK 7 package to Exadata Compute node

[root@oraclouddbadm01 jdk]# ls -ltr p21984104_17091_Linux-x86-64.zip

Step II - Update JDK on Exadata Storage cells

• Stop MS process on all Exadata Storage cells

[root@oraclouddbadm01 jdk]# dcli -g ~/cell_group -l root 'cellcli -e alter cell shutdown services ms'

oracloudceladm01:

oracloudceladm01: Stopping MS services...

oracloudceladm01: The SHUTDOWN of MS services was successful.

oracloudceladm02:

oracloudceladm02: Stopping MS services...

oracloudceladm02: The SHUTDOWN of MS services was successful.

oracloudceladm03:

oracloudceladm03: Stopping MS services...

oracloudceladm03: The SHUTDOWN of MS services was successful.

oracloudceladm04:

oracloudceladm04: Stopping MS services...

oracloudceladm04: The SHUTDOWN of MS services was successful.

oracloudceladm05:

oracloudceladm05: Stopping MS services...

oracloudceladm05: The SHUTDOWN of MS services was successful.

oracloudceladm06:

oracloudceladm06: Stopping MS services...

oracloudceladm06: The SHUTDOWN of MS services was successful.

oracloudceladm07:

oracloudceladm07: Stopping MS services...

oracloudceladm07: The SHUTDOWN of MS services was successful.

oracloudceladm08:

oracloudceladm08: Stopping MS services...

oracloudceladm08: The SHUTDOWN of MS services was successful.

oracloudceladm09:

oracloudceladm09: Stopping MS services...

oracloudceladm09: The SHUTDOWN of MS services was successful.

oracloudceladm10:

oracloudceladm10: Stopping MS services...

oracloudceladm10: The SHUTDOWN of MS services was successful.

oracloudceladm11:

oracloudceladm11: Stopping MS services...

oracloudceladm11: The SHUTDOWN of MS services was successful.

oracloudceladm12:

oracloudceladm12: Stopping MS services...

oracloudceladm12: The SHUTDOWN of MS services was successful.

oracloudceladm13:

oracloudceladm13: Stopping MS services...

oracloudceladm13: The SHUTDOWN of MS services was successful.

oracloudceladm14:

oracloudceladm14: Stopping MS services...

oracloudceladm14: The SHUTDOWN of MS services was successful.

• Unzip the JDK package

[root@oraclouddbadm01 ~]# cd /u01/app/oracle/software/jdk

[root@oraclouddbadm01 jdk]# ls -ltr p21984104_17091_Linux-x86-64.zip

-rw-r--r-- 1 root root 466264412 Nov 16 09:20 p21984104_17091_Linux-x86-64.zip

[root@oraclouddbadm01 jdk]# unzip p21984104_17091_Linux-x86-64.zip

Archive:  p21984104_17091_Linux-x86-64.zip

  inflating: jdk-7u91-linux-x64.rpm

  inflating: jdk-7u91-linux-x64.tar.gz

  inflating: jre-7u91-linux-x64.rpm

  inflating: jre-7u91-linux-x64.tar.gz

  inflating: readme.txt

  inflating: server-jre-7u91-linux-x64.tar.gz

[root@oraclouddbadm01 jdk]# ls -ltr

total 914016

-rw-r--r-- 1 root root       970 Oct 27 16:52 readme.txt

-r--r--r-- 1 root root 138164723 Oct 27 16:53 jdk-7u91-linux-x64.rpm

-r--r--r-- 1 root root  33765685 Oct 27 16:53 jre-7u91-linux-x64.rpm

-r--r--r-- 1 root root 153623439 Oct 27 16:53 jdk-7u91-linux-x64.tar.gz

-r--r--r-- 1 root root  47188352 Oct 27 16:53 jre-7u91-linux-x64.tar.gz

-r--r--r-- 1 root root  95979441 Oct 27 16:53 server-jre-7u91-linux-x64.tar.gz

-rw-r--r-- 1 root root 466264412 Nov 16 09:20 p21984104_17091_Linux-x86-64.zip

After unzipping the patch, locate the JDK RPM which will be named like "jdk-<version>-linux-x64.rpm" (i.e. jdk-7u91-linux-x64.rpm)

Copy only this rpm file over to the all storage cells. It can be staged in a temporary directory like /tmp.

[root@oraclouddbadm01 jdk]# dcli -l root -g ~/cell_group -f /u01/app/oracle/software/jdk/jdk-7u91-linux-x64.rpm -d /tmp

[root@oraclouddbadm01 jdk]# dcli -l root -g ~/cell_group ls -l /tmp/jdk*

oracloudceladm01: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm02: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm03: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm04: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm05: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm06: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm07: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm08: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm09: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm10: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm11: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm12: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm13: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

oracloudceladm14: -r--r--r-- 1 root root 138164723 Nov 16 12:51 /tmp/jdk-7u91-linux-x64.rpm

• Identify the currently installed JDK version

[root@oraclouddbadm01 jdk]# dcli -l root -g ~/cell_group 'rpm -q jdk'

oracloudceladm01: jdk-1.7.0_85-fcs.x86_64

oracloudceladm02: jdk-1.7.0_85-fcs.x86_64

oracloudceladm03: jdk-1.7.0_85-fcs.x86_64

oracloudceladm04: jdk-1.7.0_85-fcs.x86_64

oracloudceladm05: jdk-1.7.0_85-fcs.x86_64

oracloudceladm06: jdk-1.7.0_85-fcs.x86_64

oracloudceladm07: jdk-1.7.0_85-fcs.x86_64

oracloudceladm08: jdk-1.7.0_85-fcs.x86_64

oracloudceladm09: jdk-1.7.0_85-fcs.x86_64

oracloudceladm10: jdk-1.7.0_85-fcs.x86_64

oracloudceladm11: jdk-1.7.0_85-fcs.x86_64

oracloudceladm12: jdk-1.7.0_85-fcs.x86_64

oracloudceladm13: jdk-1.7.0_85-fcs.x86_64

oracloudceladm14: jdk-1.7.0_85-fcs.x86_64

Currently installed JDK version is jdk-1.7.0_85

• Update the JDK patch on all the storage cells.

[root@oraclouddbadm01 jdk]# dcli -l root -g ~/cell_group 'rpm -Uvh /tmp/jdk-7u91-linux-x64.rpm'

oracloudceladm01: Preparing... ##################################################

oracloudceladm01: jdk          ##################################################

oracloudceladm01: Unpacking JAR files...

oracloudceladm01: rt.jar...

oracloudceladm01: jsse.jar...

oracloudceladm01: charsets.jar...

oracloudceladm01: tools.jar...

oracloudceladm01: localedata.jar...

oracloudceladm01: jfxrt.jar...

oracloudceladm02: Preparing... ##################################################

oracloudceladm02: jdk          ##################################################

oracloudceladm02: Unpacking JAR files...

oracloudceladm02: rt.jar...

oracloudceladm02: jsse.jar...

oracloudceladm02: charsets.jar...

oracloudceladm02: tools.jar...

oracloudceladm02: localedata.jar...

oracloudceladm02: jfxrt.jar...

...

...

...

oracloudceladm14: Preparing... ##################################################

oracloudceladm14: jdk          ##################################################

oracloudceladm14: Unpacking JAR files...

oracloudceladm14: rt.jar...

oracloudceladm14: jsse.jar...

oracloudceladm14: charsets.jar...

oracloudceladm14: tools.jar...

oracloudceladm14: localedata.jar...

oracloudceladm14: jfxrt.jar...

[root@oraclouddbadm01 jdk]#

• Verify the JDK package is updated

[root@oraclouddbadm01 jdk]# dcli -l root -g ~/cell_group 'rpm -q jdk'

oracloudceladm01: jdk-1.7.0_91-fcs.x86_64

oracloudceladm02: jdk-1.7.0_91-fcs.x86_64

oracloudceladm03: jdk-1.7.0_91-fcs.x86_64

oracloudceladm04: jdk-1.7.0_91-fcs.x86_64

oracloudceladm05: jdk-1.7.0_91-fcs.x86_64

oracloudceladm06: jdk-1.7.0_91-fcs.x86_64

oracloudceladm07: jdk-1.7.0_91-fcs.x86_64

oracloudceladm08: jdk-1.7.0_91-fcs.x86_64

oracloudceladm09: jdk-1.7.0_91-fcs.x86_64

oracloudceladm10: jdk-1.7.0_91-fcs.x86_64

oracloudceladm11: jdk-1.7.0_91-fcs.x86_64

oracloudceladm12: jdk-1.7.0_91-fcs.x86_64

oracloudceladm13: jdk-1.7.0_91-fcs.x86_64

oracloudceladm14: jdk-1.7.0_91-fcs.x86_64

JDK version is updated to jdk-1.7.0_91

• Remove the RPM file from /tmp directory

[root@oraclouddbadm01 jdk]# dcli -g ~/cell_group -l root 'rm -f /tmp/jdk-7u91-linux-x64.rpm'

[root@oraclouddbadm01 jdk]# dcli -g ~/cell_group -l root 'ls -l /tmp/jdk-7u91-linux-x64.rpm'

oracloudceladm01: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm02: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm03: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm04: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm05: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm06: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm07: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm08: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm09: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm10: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm11: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm12: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm13: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

oracloudceladm14: ls: cannot access /tmp/jdk-7u91-linux-x64.rpm: No such file or directory

• Redeploy MS so it uses the updated JDK package

[root@oraclouddbadm01 jdk]# dcli -g ~/cell_group -l root 'cellcli -e alter cell shutdown services ms'

oracloudceladm01:

oracloudceladm01: Stopping MS services...

oracloudceladm01: The SHUTDOWN of MS services was successful.

oracloudceladm02:

oracloudceladm02: Stopping MS services...

oracloudceladm02: The SHUTDOWN of MS services was successful.

oracloudceladm03:

oracloudceladm03: Stopping MS services...

oracloudceladm03: The SHUTDOWN of MS services was successful.

oracloudceladm04:

oracloudceladm04: Stopping MS services...

oracloudceladm04: The SHUTDOWN of MS services was successful.

oracloudceladm05:

oracloudceladm05: Stopping MS services...

oracloudceladm05: The SHUTDOWN of MS services was successful.

oracloudceladm06:

oracloudceladm06: Stopping MS services...

oracloudceladm06: The SHUTDOWN of MS services was successful.

oracloudceladm07:

oracloudceladm07: Stopping MS services...

oracloudceladm07: The SHUTDOWN of MS services was successful.

oracloudceladm08:

oracloudceladm08: Stopping MS services...

oracloudceladm08: The SHUTDOWN of MS services was successful.

oracloudceladm09:

oracloudceladm09: Stopping MS services...

oracloudceladm09: The SHUTDOWN of MS services was successful.

oracloudceladm10:

oracloudceladm10: Stopping MS services...

oracloudceladm10: The SHUTDOWN of MS services was successful.

oracloudceladm11:

oracloudceladm11: Stopping MS services...

oracloudceladm11: The SHUTDOWN of MS services was successful.

oracloudceladm12:

oracloudceladm12: Stopping MS services...

oracloudceladm12: The SHUTDOWN of MS services was successful.

oracloudceladm13:

oracloudceladm13: Stopping MS services...

oracloudceladm13: The SHUTDOWN of MS services was successful.

oracloudceladm14:

oracloudceladm14: Stopping MS services...

oracloudceladm14: The SHUTDOWN of MS services was successful.

[root@oraclouddbadm01 jdk]# dcli -g ~/cell_group -l root 'ls -l /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy'

oracloudceladm01: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm02: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm03: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm04: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm05: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm06: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm07: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm08: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm09: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm10: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm11: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm12: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm13: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

oracloudceladm14: -rwxr-xr-x 1 root root 22060 Sep 17 18:14 /opt/oracle/cell/cellsrv/deploy/scripts/unix/setup_dynamicDeploy

[root@oraclouddbadm01 jdk]# dcli -g ~/cell_group -l root 'cd /opt/oracle/cell/cellsrv/deploy/scripts/unix; sh setup_dynamicDeploy'

oracloudceladm01: unzipping wls

oracloudceladm01:

oracloudceladm01: CLASSPATH=/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/default//lib/tools.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/features/weblogic.server.modules_10.3.6.0.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/webservices.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/utils/config/10.3/config-launch.jar::/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbynet.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbytools.jar::

oracloudceladm01:

oracloudceladm01: Initializing WebLogic Scripting Tool (WLST) ...

oracloudceladm01:

oracloudceladm01: Welcome to WebLogic Server Administration Scripting Shell

oracloudceladm01:

oracloudceladm01: Type help() for help on available commands

oracloudceladm01:

oracloudceladm01:

oracloudceladm01:

oracloudceladm01: Exiting WebLogic Scripting Tool.

oracloudceladm01:

oracloudceladm01: /opt/oracle/cell/cellsrv/deploy/scripts/unix

oracloudceladm01: MS now has a new self-signed identity and certificate.

oracloudceladm01: sleep until wls is ready ...

oracloudceladm01:

oracloudceladm01: CLASSPATH=/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/jdk1.7.0_91/lib/tools.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/features/weblogic.server.modules_10.3.6.0.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/webservices.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/jdk1.7.0_91/lib/tools.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/features/weblogic.server.modules_10.3.6.0.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/webservices.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/xqrl.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/xqrl.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/utils/config/10.3/config-launch.jar::/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbynet.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbytools.jar::

oracloudceladm01:

oracloudceladm01: Initializing WebLogic Scripting Tool (WLST) ...

oracloudceladm01:

oracloudceladm01: Welcome to WebLogic Server Administration Scripting Shell

oracloudceladm01:

oracloudceladm01: Type help() for help on available commands

oracloudceladm01:

oracloudceladm01: Connecting to t3://localhost:8888 with userid weblogic ...

oracloudceladm01: Successfully connected to Admin Server 'msServer' that belongs to domain 'msdomain'.

oracloudceladm01:

oracloudceladm01: Warning: An insecure protocol was used to connect to the

oracloudceladm01: server. To ensure on-the-wire security, the SSL port or

oracloudceladm01: Admin port should be used instead.

oracloudceladm01:

oracloudceladm01: Location changed to edit tree. This is a writable tree with

oracloudceladm01: DomainMBean as the root. To make changes you will need to start

oracloudceladm01: an edit session via startEdit().

oracloudceladm01:

oracloudceladm01: For more help, use help(edit)

oracloudceladm01:

oracloudceladm01: Starting an edit session ...

oracloudceladm01: Started edit session, please be sure to save and activate your

oracloudceladm01: changes once you are done.

oracloudceladm01: Activating all your changes, this may take a while ...

oracloudceladm01: The edit lock associated with this edit session is released

oracloudceladm01: once the activation is completed.

oracloudceladm01:

oracloudceladm01: The following non-dynamic attribute(s) have been changed on MBeans

oracloudceladm01: that require server re-start:

oracloudceladm01: MBean Changed : Security:Name=myrealmMSUserAuthenticator

oracloudceladm01: Attributes changed : ControlFlag

oracloudceladm01:

oracloudceladm01: MBean Changed : Security:Name=myrealm

oracloudceladm01: Attributes changed : AuthenticationProviders

oracloudceladm01:

oracloudceladm01: Activation completed

oracloudceladm01:

oracloudceladm01: weblogic.Deployer invoked with options:  -verbose -name MS -source /opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/lib/CliService_CliServicePortImpl.war -targets msServer -user weblogic -adminURL t3://localhost:8888 -deploy

oracloudceladm01: <Nov 16, 2015 1:10:15 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, MS [archive: /opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/lib/CliService_CliServicePortImpl.war], to msServer .>

oracloudceladm01: Task 0 initiated: [Deployer:149026]deploy application MS on msServer.

oracloudceladm01: Task 0 completed: [Deployer:149026]deploy application MS on msServer.

oracloudceladm01: Target state: deploy completed on Server msServer

oracloudceladm01: java.lang.Exception: [Deployer:149169]Requires server restart for completion.

oracloudceladm01:

oracloudceladm01:

oracloudceladm01: Target Assignments:

oracloudceladm01: + MS  msServer

oracloudceladm01: 0

oracloudceladm02: unzipping wls

oracloudceladm02:

oracloudceladm02: CLASSPATH=/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/default//lib/tools.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/features/weblogic.server.modules_10.3.6.0.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/webservices.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/utils/config/10.3/config-launch.jar::/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbynet.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbytools.jar::

oracloudceladm02:

oracloudceladm02: Initializing WebLogic Scripting Tool (WLST) ...

oracloudceladm02:

oracloudceladm02: Welcome to WebLogic Server Administration Scripting Shell

oracloudceladm02:

oracloudceladm02: Type help() for help on available commands

oracloudceladm02:

oracloudceladm02:

oracloudceladm02:

oracloudceladm02: Exiting WebLogic Scripting Tool.

oracloudceladm02:

oracloudceladm02: /opt/oracle/cell/cellsrv/deploy/scripts/unix

oracloudceladm02: MS now has a new self-signed identity and certificate.

oracloudceladm02: sleep until wls is ready ...

oracloudceladm02:

oracloudceladm02: CLASSPATH=/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/jdk1.7.0_91/lib/tools.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/features/weblogic.server.modules_10.3.6.0.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/webservices.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/jdk1.7.0_91/lib/tools.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/features/weblogic.server.modules_10.3.6.0.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/webservices.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/xqrl.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/xqrl.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/utils/config/10.3/config-launch.jar::/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbynet.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbytools.jar::

oracloudceladm02:

oracloudceladm02: Initializing WebLogic Scripting Tool (WLST) ...

oracloudceladm02:

oracloudceladm02: Welcome to WebLogic Server Administration Scripting Shell

oracloudceladm02:

oracloudceladm02: Type help() for help on available commands

oracloudceladm02:

oracloudceladm02: Connecting to t3://localhost:8888 with userid weblogic ...

oracloudceladm02: Successfully connected to Admin Server 'msServer' that belongs to domain 'msdomain'.

oracloudceladm02:

oracloudceladm02: Warning: An insecure protocol was used to connect to the

oracloudceladm02: server. To ensure on-the-wire security, the SSL port or

oracloudceladm02: Admin port should be used instead.

oracloudceladm02:

oracloudceladm02: Location changed to edit tree. This is a writable tree with

oracloudceladm02: DomainMBean as the root. To make changes you will need to start

oracloudceladm02: an edit session via startEdit().

oracloudceladm02:

oracloudceladm02: For more help, use help(edit)

oracloudceladm02:

oracloudceladm02: Starting an edit session ...

oracloudceladm02: Started edit session, please be sure to save and activate your

oracloudceladm02: changes once you are done.

oracloudceladm02: Activating all your changes, this may take a while ...

oracloudceladm02: The edit lock associated with this edit session is released

oracloudceladm02: once the activation is completed.

oracloudceladm02:

oracloudceladm02: The following non-dynamic attribute(s) have been changed on MBeans

oracloudceladm02: that require server re-start:

oracloudceladm02: MBean Changed : Security:Name=myrealmMSUserAuthenticator

oracloudceladm02: Attributes changed : ControlFlag

oracloudceladm02:

oracloudceladm02: MBean Changed : Security:Name=myrealm

oracloudceladm02: Attributes changed : AuthenticationProviders

oracloudceladm02:

oracloudceladm02: Activation completed

oracloudceladm02:

oracloudceladm02: weblogic.Deployer invoked with options:  -verbose -name MS -source /opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/lib/CliService_CliServicePortImpl.war -targets msServer -user weblogic -adminURL t3://localhost:8888 -deploy

oracloudceladm02: <Nov 16, 2015 1:10:17 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, MS [archive: /opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/lib/CliService_CliServicePortImpl.war], to msServer .>

oracloudceladm02: Task 0 initiated: [Deployer:149026]deploy application MS on msServer.

oracloudceladm02: Task 0 completed: [Deployer:149026]deploy application MS on msServer.

oracloudceladm02: Target state: deploy completed on Server msServer

oracloudceladm02: java.lang.Exception: [Deployer:149169]Requires server restart for completion.

oracloudceladm02:

oracloudceladm02:

oracloudceladm02: Target Assignments:

oracloudceladm02: + MS  msServer

oracloudceladm02: 0

oracloudceladm03: unzipping wls

...

...

...

oracloudceladm14: unzipping wls

oracloudceladm14:

oracloudceladm14: CLASSPATH=/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/default//lib/tools.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/features/weblogic.server.modules_10.3.6.0.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/webservices.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/utils/config/10.3/config-launch.jar::/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbynet.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbytools.jar::

oracloudceladm14:

oracloudceladm14: Initializing WebLogic Scripting Tool (WLST) ...

oracloudceladm14:

oracloudceladm14: Welcome to WebLogic Server Administration Scripting Shell

oracloudceladm14:

oracloudceladm14: Type help() for help on available commands

oracloudceladm14:

oracloudceladm14:

oracloudceladm14:

oracloudceladm14: Exiting WebLogic Scripting Tool.

oracloudceladm14:

oracloudceladm14: /opt/oracle/cell/cellsrv/deploy/scripts/unix

oracloudceladm14: MS now has a new self-signed identity and certificate.

oracloudceladm14: sleep until wls is ready ...

oracloudceladm14:

oracloudceladm14: CLASSPATH=/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/jdk1.7.0_91/lib/tools.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/features/weblogic.server.modules_10.3.6.0.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/webservices.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/jdk1.7.0_91/lib/tools.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/weblogic.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/features/weblogic.server.modules_10.3.6.0.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/webservices.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/xqrl.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/server/lib/xqrl.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/utils/config/10.3/config-launch.jar::/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbynet.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/deploy/wls/wlserver_10.3/common/derby/lib/derbytools.jar::

oracloudceladm14:

oracloudceladm14: Initializing WebLogic Scripting Tool (WLST) ...

oracloudceladm14:

oracloudceladm14: Welcome to WebLogic Server Administration Scripting Shell

oracloudceladm14:

oracloudceladm14: Type help() for help on available commands

oracloudceladm14:

oracloudceladm14: Connecting to t3://localhost:8888 with userid weblogic ...

oracloudceladm14: Successfully connected to Admin Server 'msServer' that belongs to domain 'msdomain'.

oracloudceladm14:

oracloudceladm14: Warning: An insecure protocol was used to connect to the

oracloudceladm14: server. To ensure on-the-wire security, the SSL port or

oracloudceladm14: Admin port should be used instead.

oracloudceladm14:

oracloudceladm14: Location changed to edit tree. This is a writable tree with

oracloudceladm14: DomainMBean as the root. To make changes you will need to start

oracloudceladm14: an edit session via startEdit().

oracloudceladm14:

oracloudceladm14: For more help, use help(edit)

oracloudceladm14:

oracloudceladm14: Starting an edit session ...

oracloudceladm14: Started edit session, please be sure to save and activate your

oracloudceladm14: changes once you are done.

oracloudceladm14: Activating all your changes, this may take a while ...

oracloudceladm14: The edit lock associated with this edit session is released

oracloudceladm14: once the activation is completed.

oracloudceladm14:

oracloudceladm14: The following non-dynamic attribute(s) have been changed on MBeans

oracloudceladm14: that require server re-start:

oracloudceladm14: MBean Changed : Security:Name=myrealmMSUserAuthenticator

oracloudceladm14: Attributes changed : ControlFlag

oracloudceladm14:

oracloudceladm14: MBean Changed : Security:Name=myrealm

oracloudceladm14: Attributes changed : AuthenticationProviders

oracloudceladm14:

oracloudceladm14: Activation completed

oracloudceladm14:

oracloudceladm14: weblogic.Deployer invoked with options:  -verbose -name MS -source /opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/lib/CliService_CliServicePortImpl.war -targets msServer -user weblogic -adminURL t3://localhost:8888 -deploy

oracloudceladm14: <Nov 16, 2015 1:10:15 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, MS [archive: /opt/oracle/cell12.1.2.2.0_LINUX.X64_150917/cellsrv/lib/CliService_CliServicePortImpl.war], to msServer .>

oracloudceladm14: Task 0 initiated: [Deployer:149026]deploy application MS on msServer.

oracloudceladm14: Task 0 completed: [Deployer:149026]deploy application MS on msServer.

oracloudceladm14: Target state: deploy completed on Server msServer

oracloudceladm14: java.lang.Exception: [Deployer:149169]Requires server restart for completion.

oracloudceladm14:

oracloudceladm14:

oracloudceladm14: Target Assignments:

oracloudceladm14: + MS  msServer

oracloudceladm14: 0

[root@oraclouddbadm01 jdk]#

[root@oraclouddbadm01 jdk]# dcli -g ~/cell_group -l root 'cellcli -e alter cell startup services ms'

oracloudceladm01:

oracloudceladm01: Starting MS services...

oracloudceladm01: The STARTUP of MS services was successful.

oracloudceladm02:

oracloudceladm02: Starting MS services...

oracloudceladm02: The STARTUP of MS services was successful.

oracloudceladm03:

oracloudceladm03: Starting MS services...

oracloudceladm03: The STARTUP of MS services was successful.

oracloudceladm04:

oracloudceladm04: Starting MS services...

oracloudceladm04: The STARTUP of MS services was successful.

oracloudceladm05:

oracloudceladm05: Starting MS services...

oracloudceladm05: The STARTUP of MS services was successful.

oracloudceladm06:

oracloudceladm06: Starting MS services...

oracloudceladm06: The STARTUP of MS services was successful.

oracloudceladm07:

oracloudceladm07: Starting MS services...

oracloudceladm07: The STARTUP of MS services was successful.

oracloudceladm08:

oracloudceladm08: Starting MS services...

oracloudceladm08: The STARTUP of MS services was successful.

oracloudceladm09:

oracloudceladm09: Starting MS services...

oracloudceladm09: The STARTUP of MS services was successful.

oracloudceladm10:

oracloudceladm10: Starting MS services...

oracloudceladm10: The STARTUP of MS services was successful.

oracloudceladm11:

oracloudceladm11: Starting MS services...

oracloudceladm11: The STARTUP of MS services was successful.

oracloudceladm12:

oracloudceladm12: Starting MS services...

oracloudceladm12: The STARTUP of MS services was successful.

oracloudceladm13:

oracloudceladm13: Starting MS services...

oracloudceladm13: The STARTUP of MS services was successful.

oracloudceladm14:

oracloudceladm14: Starting MS services...

oracloudceladm14: The STARTUP of MS services was successful.

[root@oraclouddbadm01 jdk]# dcli -g ~/cell_group -l root 'service celld status'

oracloudceladm01: rsStatus:             running

oracloudceladm01: msStatus:             running

oracloudceladm01: cellsrvStatus:        running

oracloudceladm02: rsStatus:             running

oracloudceladm02: msStatus:             running

oracloudceladm02: cellsrvStatus:        running

oracloudceladm03: rsStatus:             running

oracloudceladm03: msStatus:             running

oracloudceladm03: cellsrvStatus:        running

oracloudceladm04: rsStatus:             running

oracloudceladm04: msStatus:             running

oracloudceladm04: cellsrvStatus:        running

oracloudceladm05: rsStatus:             running

oracloudceladm05: msStatus:             running

oracloudceladm05: cellsrvStatus:        running

oracloudceladm06: rsStatus:             running

oracloudceladm06: msStatus:             running

oracloudceladm06: cellsrvStatus:        running

oracloudceladm07: rsStatus:             running

oracloudceladm07: msStatus:             running

oracloudceladm07: cellsrvStatus:        running

oracloudceladm08: rsStatus:             running

oracloudceladm08: msStatus:             running

oracloudceladm08: cellsrvStatus:        running

oracloudceladm09: rsStatus:             running

oracloudceladm09: msStatus:             running

oracloudceladm09: cellsrvStatus:        running

oracloudceladm10: rsStatus:             running

oracloudceladm10: msStatus:             running

oracloudceladm10: cellsrvStatus:        running

oracloudceladm11: rsStatus:             running

oracloudceladm11: msStatus:             running

oracloudceladm11: cellsrvStatus:        running

oracloudceladm12: rsStatus:             running

oracloudceladm12: msStatus:             running

oracloudceladm12: cellsrvStatus:        running

oracloudceladm13: rsStatus:             running

oracloudceladm13: msStatus:             running

oracloudceladm13: cellsrvStatus:        running

oracloudceladm14: rsStatus:             running

oracloudceladm14: msStatus:             running

oracloudceladm14: cellsrvStatus:        running

[root@oraclouddbadm01 jdk]# dcli -g ~/cell_group -l root 'uptime'

oracloudceladm01: 13:45:46 up 29 days,  8:30,  0 users,  load average: 0.63, 0.80, 0.88

oracloudceladm02: 13:45:46 up 29 days,  8:30,  0 users,  load average: 1.10, 1.00, 0.94

oracloudceladm03: 13:45:46 up 29 days,  8:26,  0 users,  load average: 0.83, 0.95, 0.95

oracloudceladm04: 13:45:46 up 23 days, 18:25,  0 users,  load average: 1.11, 1.02, 0.97

oracloudceladm05: 13:45:46 up 29 days,  8:29,  0 users,  load average: 1.10, 1.12, 1.07

oracloudceladm06: 13:45:46 up 29 days,  8:30,  0 users,  load average: 0.73, 0.88, 0.89

oracloudceladm07: 13:45:46 up 29 days,  8:30,  0 users,  load average: 0.97, 1.19, 1.08

oracloudceladm08: 13:45:46 up 29 days,  8:30,  0 users,  load average: 0.61, 0.89, 0.95

oracloudceladm09: 13:45:46 up 29 days,  8:30,  0 users,  load average: 1.10, 1.02, 0.99

oracloudceladm10: 13:45:46 up 29 days,  8:30,  0 users,  load average: 0.59, 0.85, 0.89

oracloudceladm11: 13:45:46 up 29 days,  8:30,  0 users,  load average: 0.94, 1.00, 1.02

oracloudceladm12: 13:45:46 up 29 days,  8:29,  0 users,  load average: 0.70, 0.90, 1.02

oracloudceladm13: 13:45:46 up 29 days,  8:30,  0 users,  load average: 1.07, 1.00, 0.97

oracloudceladm14: 13:45:46 up 29 days,  8:30,  0 users,  load average: 1.26, 1.11, 1.02

• Stop MS process on all Exadata Compute nodes

[root@oraclouddbadm01 jdk]# dcli -g ~/dbs_group -l root 'dbmcli -e alter dbserver shutdown services ms'

oraclouddbadm01:

oraclouddbadm01:

oraclouddbadm01: Stopping MS services...

oraclouddbadm01: The SHUTDOWN of MS services was successful.

oraclouddbadm02:

oraclouddbadm02:

oraclouddbadm02: Stopping MS services...

oraclouddbadm02: The SHUTDOWN of MS services was successful.

oraclouddbadm03:

oraclouddbadm03:

oraclouddbadm03: Stopping MS services...

oraclouddbadm03: The SHUTDOWN of MS services was successful.

oraclouddbadm04:

oraclouddbadm04:

oraclouddbadm04: Stopping MS services...

oraclouddbadm04: The SHUTDOWN of MS services was successful.

oraclouddbadm05:

oraclouddbadm05:

oraclouddbadm05: Stopping MS services...

oraclouddbadm05: The SHUTDOWN of MS services was successful.

oraclouddbadm06:

oraclouddbadm06:

oraclouddbadm06: Stopping MS services...

oraclouddbadm06: The SHUTDOWN of MS services was successful.

oraclouddbadm07:

oraclouddbadm07:

oraclouddbadm07: Stopping MS services...

oraclouddbadm07: The SHUTDOWN of MS services was successful.

oraclouddbadm08:

oraclouddbadm08:

oraclouddbadm08: Stopping MS services...

oraclouddbadm08: The SHUTDOWN of MS services was successful.

• Copy the JDK package to /tmp directory on all the Compute nodes

Copy only this rpm file over to the all storage cells. It can be staged in a temporary directory like /tmp.

•  Identify the currently installed JDK version

[root@oraclouddbadm01 jdk]# dcli -l root -g ~/dbs_group 'rpm -q jdk'

oraclouddbadm01: jdk-1.7.0_85-fcs.x86_64

oraclouddbadm02: jdk-1.7.0_85-fcs.x86_64

oraclouddbadm03: jdk-1.7.0_85-fcs.x86_64

oraclouddbadm04: jdk-1.7.0_85-fcs.x86_64

oraclouddbadm05: jdk-1.7.0_85-fcs.x86_64

oraclouddbadm06: jdk-1.7.0_85-fcs.x86_64

oraclouddbadm07: jdk-1.7.0_85-fcs.x86_64

oraclouddbadm08: jdk-1.7.0_85-fcs.x86_64

Currently installed JDK version is jdk-1.7.0_85

• Update the JDK patch on all the Compute Nodes

[root@oraclouddbadm01 jdk]# dcli -l root -g ~/dbs_group 'rpm -Uvh /tmp/jdk-7u91-linux-x64.rpm'

oraclouddbadm01: Preparing... ##################################################

oraclouddbadm01: jdk          ##################################################

oraclouddbadm01: Unpacking JAR files...

oraclouddbadm01: rt.jar...

oraclouddbadm01: jsse.jar...

oraclouddbadm01: charsets.jar...

oraclouddbadm01: tools.jar...

oraclouddbadm01: localedata.jar...

oraclouddbadm01: jfxrt.jar...

oraclouddbadm02: Preparing... ##################################################

oraclouddbadm02: jdk          ##################################################

oraclouddbadm02: Unpacking JAR files...

oraclouddbadm02: rt.jar...

oraclouddbadm02: jsse.jar...

oraclouddbadm02: charsets.jar...

oraclouddbadm02: tools.jar...

oraclouddbadm02: localedata.jar...

oraclouddbadm02: jfxrt.jar...

...

...

...

oraclouddbadm08: Preparing... ##################################################

oraclouddbadm08: jdk          ##################################################

oraclouddbadm08: Unpacking JAR files...

oraclouddbadm08: rt.jar...

oraclouddbadm08: jsse.jar...

oraclouddbadm08: charsets.jar...

oraclouddbadm08: tools.jar...

oraclouddbadm08: localedata.jar...

oraclouddbadm08: jfxrt.jar...

[root@oraclouddbadm01 jdk]#

• Verify the JDK package is updated

[root@oraclouddbadm01 jdk]# dcli -l root -g ~/dbs_group 'rpm -q jdk'

oraclouddbadm01: jdk-1.7.0_91-fcs.x86_64

oraclouddbadm02: jdk-1.7.0_91-fcs.x86_64

oraclouddbadm03: jdk-1.7.0_91-fcs.x86_64

oraclouddbadm04: jdk-1.7.0_91-fcs.x86_64

oraclouddbadm05: jdk-1.7.0_91-fcs.x86_64

oraclouddbadm06: jdk-1.7.0_91-fcs.x86_64

oraclouddbadm07: jdk-1.7.0_91-fcs.x86_64

oraclouddbadm08: jdk-1.7.0_91-fcs.x86_64

JDK version is updated to jdk-1.7.0_91

• Redeploy MS so it uses the updated JDK package

       ...

       ...

       ...

Important Notes

• ·         Exadata Compute Nodes include Java JDK starting with Exadata Image version 12.1.2.1.0.
• ·         Once the JDK is updated, MS process must be reconfigured to use the latest JDK version both Compute nodes and Storage cells.
• ·         Exadata Storage cells and compute nodes include JDK 7 package installed.
•           Download latest JDK 7 package
  
•           DO NOT use JDK 8 or later

Reference:

Conclusion

Introduction

In this article we will see how to configure Enterprise Manager Security specific to OMS, Securing OMS is the key role to do as all the servers, databases, accounts information will be available in Oracle management repository which is heart of Enterprise manager (or) cloud control. We also go through with the enabling security for the OMS and also agent with step by step procedure

Securing EM

Likewise the security of database by creating wallet in similar we can secure the entire enterprise manager, the components that can be secured are Infrastructure and operating system that EM configured, securing oracle management repository, the agents which are configured to the EM, securing communication between the components and operational security from OMR database level such as privilege, role management, groups and system and configuring auditing so on.

When it comes to infrastructure and operating system security, there are few key components to be considered, for example in order to access the server using “oracle’ account, it’s recommended to login to oracle through the personal account. So that direct access to the server can be avoided, like that various options available and same time need to take care of unsecure devices and better to consider disabling them. Same time it is highly recommended to setup MOS for oracle updates in order to apply critical patch updates and also OS level patches.

In order to ensure for secure communications we should consider to securing OMS as well, we have to perform securing both the OMS and also dependent agents so that agent can be reachable and communicated with the OMS.

Apart from the above securing methods, on top of that additionally we need to enable security at database level. They are Oracle advanced security like data redeaction, transparent data encryption. Auditing sys user activities, restricting use of SYSMAN user.

Enabling security for Oracle Management Service

To secure the OMS the basic rule is to secure the OMS, in order to do that after securing OMS we have to perform by stopping the OMS, so downtime of OMS should be acceptable in this case. By that it generates the root key inside the OMR which is used to distribute wallets which has digital certificates for the agents. After securing the OMS we should be able to use Enterprise Manager using HTTPS channel. Securing OMS is very short and simple procedure

1)     $OMS_HOME/bin/emctl stop oms

2)     $OMS_HOME/bin/emctl secure oms

3)     $OMS_HOME/bin/emctl start oms

After successful startup of OMS, EM can be accessed using HTTPS channel as (ex: https://em12c.localdomain:7801/em).

After able to connect to the Cloud control url using HTTPS we can confirm/assume that OMS is secured.  We can also check the status of OMS including secured or not using the below command.  

[oracle@em12c ~]$ emctl status oms -details -sysman_pwd welcome1

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

Console Server Host        : em12c.localdomain

HTTP Console Port          : 7789

HTTPS Console Port         : 7801

HTTP Upload Port           : 4890

HTTPS Upload Port          : 4901

EM Instance Home           : /u01/app/oracle/gc_inst/em/EMGC_OMS1

OMS Log Directory Location : /u01/app/oracle/gc_inst/em/EMGC_OMS1/sysman/log

OMS is not configured with SLB or virtual hostname

Agent Upload is locked.

OMS Console is locked.

Active CA ID: 1

Console URL: https://em12c.localdomain:7801/em

Upload URL: https://em12c.localdomain:4901/empbs/upload

 WLS Domain Information

Domain Name            : GCDomain

Admin Server Host      : em12c.localdomain

Admin Server HTTPS Port: 7102

Admin Server is RUNNING

 Managed Server Information

Managed Server Instance Name: EMGC_OMS1

Managed Server Instance Host: em12c.localdomain

WebTier is Up

Oracle Management Server is Up

After securing the OMS, we need to create certification authority using emctl, usually certification authority (CA) created if CA is expiring or to change key strength. Whenever CA is created every time it will be assigned with unique number. By default the certification authority 1 will be created during the installation of EM, so for every new creation of CA the next number will be allocated such as 2, 3 and the key strength may not require to have same strength.  The existing CA 1 can be viewed using the below command and various details are available below including the key strength.

[oracle@em12c ~]$ emcli get_ca_info -ca_id="1" -details

Info about CA with ID: 1

CA is configured

Signature algorithm : sha512

Key strength : 1024

DN: CN=em12c.localdomain, C=US, ST=CA, L=EnterpriseManager on em12c.localdomain, OU=EnterpriseManager on em12c.localdomain, O=EnterpriseManager on em12c.localdomain

Serial# : 75736055487891743580

Valid From: Wed Oct 24 10:01:12 EDT 2012

Valid Till: Sun Oct 23 10:01:12 EDT 2022

Number of Agents registered with CA ID 1 is 4

192.168.0.10:3872

db12c.localdomain:3872

em12c.localdomain:3872

host1.localdomain:3872

[oracle@em12c ~]$

 To create of view to trust the certification chain we have to create CA, it can be performed using the emcli command as below by mentioning the home location and the username we are using to setup.  

[oracle@em12c ~]$ mkdir -p /home/oracle/cert_auth

[oracle@em12c ~]$ emcli setup -url=https://em12c.localdomain:7801/em -username=sysman -dir=/home/oracle/cert_auth

Oracle Enterprise Manager 12c 3.

Copyright (c) 1996, 2013 Oracle Corporation and/or its affiliates. All rights reserved.

Enter password

Warning: This certificate has not been identified as trusted in the local trust store

--------------------------------------

[

[

  Version: V3

  Subject: CN=em12c.localdomain, C=US, ST=CA, L=EnterpriseManager on em12c.localdomain, OU=EnterpriseManager on em12c.localdomain, O=EnterpriseManager on em12c.localdomain

  Signature Algorithm: SHA512withRSA, OID = 1.2.840.113549.1.1.13

  Key:  Sun RSA public key, 1024 bits

  modulus: 133627010103079426106767978733765070671256452755264124298364177515855963402396209268550264027014910629979186232646076391897498654631460970590402851272991410948484798398337141209797689184905537665702466156563546606727372497472894081972082766339094634591866887572507346786958080223041346139625330884681339231267

  public exponent: 65537

  Validity: [From: Wed Oct 24 10:01:12 EDT 2012,

               To: Sun Oct 23 10:01:12 EDT 2022]

  Issuer: CN=em12c.localdomain, C=US, ST=CA, L=EnterpriseManager on em12c.localdomain, OU=EnterpriseManager on em12c.localdomain, O=EnterpriseManager on em12c.localdomain

  SerialNumber: [    041b0c85 330d0fa3 5c]

Certificate Extensions: 2

[1]: ObjectId: 2.5.29.19 Criticality=true

BasicConstraints:[

  CA:true

  PathLen:2147483647

]

[2]: ObjectId: 2.5.29.15 Criticality=true

KeyUsage [

  DigitalSignature

  Non_repudiation

  Key_CertSign

  Crl_Sign

]

]

  Algorithm: [SHA512withRSA]

  Signature:

0000: 0E 2B 35 C6 F3 99 A5 11   1E 56 23 41 25 DC F9 41  .+5......V#A%..A

0010: 83 16 2E 1D 22 4B 02 21   B6 0C 31 81 0D E2 6E B8  ...."K.!..1...n.

0020: 7B 65 67 E4 50 36 6A 1F   C8 B0 D2 A4 10 DD 86 DB  .eg.P6j.........

0030: 33 CF 0E 3E E6 6A 96 37   9D 38 18 15 4C BD 87 1E  3..>.j.7.8..L...

0040: C3 EE 14 58 9D AD A3 83   2A 46 33 99 37 E8 55 43  ...X....*F3.7.UC

0050: 0B 82 F0 A7 64 84 95 32   39 C8 00 76 9D B7 52 C9  ....d..29..v..R.

0060: 40 A7 94 38 24 CC EE 01   37 3C 2B C8 1E FD 3E 5A  @..8$...7<+...>Z

0070: C9 AA D4 B0 ED B6 B2 F3   34 5B DA BC 24 F3 10 59  ........4[..$..Y

]

--------------------------------------

Warning: This certificate could be compromised

Warning: This certificate has not been identified as trusted in the local trust store

--------------------------------------

[

[

  Version: V3

  Subject: CN=em12c.localdomain

  Signature Algorithm: SHA512withRSA, OID = 1.2.840.113549.1.1.13

  Key:  Sun RSA public key, 1024 bits

  modulus: 112368975731894125914161537621417272129612339366145866018201999698606351882724580621563935552262439838814097775099738716022935964599562271114030308566143956134180271738280849095747824057799964636516344438690254947507575679885195443085855831701212602259616566202725828803312983711909337862922623119576842004049

  public exponent: 65537

  Validity: [From: Wed Jul 03 01:13:48 EDT 2013,

               To: Sun Jul 02 01:13:48 EDT 2023]

  Issuer: CN=em12c.localdomain, C=US, ST=CA, L=EnterpriseManager on em12c.localdomain, OU=EnterpriseManager on em12c.localdomain, O=EnterpriseManager on em12c.localdomain

  SerialNumber: [   -461beffa 00b97ef6]

Certificate Extensions: 3

[1]: ObjectId: 2.5.29.19 Criticality=true

BasicConstraints:[

  CA:false

  PathLen: undefined

]

[2]: ObjectId: 2.5.29.15 Criticality=true

KeyUsage [

  DigitalSignature

  Non_repudiation

  Key_Encipherment

  Key_Agreement

]

[3]: ObjectId: 2.5.29.14 Criticality=false

SubjectKeyIdentifier [

KeyIdentifier [

0000: 83 F4 BB 20 B5 6A B0 4B   8E A3 05 BC 06 A8 46 02  ... .j.K......F.

0010: 5E A3 EB 00                                        ^...

]

]

]

  Algorithm: [SHA512withRSA]

  Signature:

0000: 90 A8 37 59 D1 18 94 99   5A DF 05 85 37 A8 E4 82  ..7Y....Z...7...

0010: 58 69 52 33 5E 82 F1 37   07 C8 0A C1 05 11 FD A0  XiR3^..7........

0020: 10 D5 02 C6 81 DE C2 E3   F2 CC B2 C1 23 31 B4 A6  ............#1..

0030: EB 6D 86 2D 4D 27 9B 78   C6 4A 40 04 07 0D AB 47  .m.-M'.x.J@....G

0040: 7F 4E B9 0D 48 68 9B 17   F7 7A AA 1A 9C D6 D8 AC  .N..Hh...z......

0050: 03 8C 38 6B A6 07 61 02   4F C1 8D A8 0E 51 6C 94  ..8k..a.O....Ql.

0060: 01 56 FC 7C CB 49 E9 03   64 93 EB 9E FD 81 60 F9  .V...I..d.....`.

0070: 14 43 09 6D 0B 6A 72 09   CE 1B 68 30 18 C9 E0 6B  .C.m.jr...h0...k

]

--------------------------------------

Do you trust the certificate chain? [yes/no] yes

Emcli setup successful

[oracle@em12c ~]$

After setup of the EM, we can create new certification authority using the below command.

[oracle@em12c ~]$ emctl secure createca -key_strength 2048

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

Creating CA... Started.

Enter Enterprise Manager Root (SYSMAN) Password :

Successfully created CA with ID 2

[oracle@em12c ~]$ 

The new created certification authority again using emctl command, but we have to mention the CA unique ID.

[oracle@em12c ~]$ emcli get_ca_info -ca_id="2" -details

Info about CA with ID: 2

CA is configured

Signature algorithm : sha512

Key strength : 2048

DN: CN=em12c.localdomain, C=US, ST=CA, L=CA2, OU=EnterpriseManager on em12c.localdomain, O=EnterpriseManager on em12c.localdomain

Serial# : -3843635707979125701

Valid From: Thu Oct 29 19:33:06 EDT 2015

Valid Till: Mon Oct 27 19:33:06 EDT 2025

There are no Agents registered with CA ID 2

[oracle@em12c ~]$

After creating the new CA, it is necessary to maintain Oracle wallet which contains the credentials and trusted certificates and private keys. During the installation of EM the preexisting wallet will be available by default. So whenever we create new CA we have to recreate the wallet. It can be created using below command and we need to provide the passwords of weblogic server.

[oracle@em12c ~]$ emctl secure create_admin_creds_wallet -admin_pwd welcome1 -nodemgr_pwd welcome1

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

Creating Admin Credentials Wallet...

Created Admin Credentials Wallet successfully

Run this command on all OMS's in your environment

[oracle@em12c ~]$

If we have more than one OMS then this command has to be performed on all the OMS.

[oracle@em12c ~]$ emctl status oms -details

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

Enter Enterprise Manager Root (SYSMAN) Password :

Console Server Host        : em12c.localdomain

HTTP Console Port          : 7789

HTTPS Console Port         : 7801

HTTP Upload Port           : 4890

HTTPS Upload Port          : 4901

EM Instance Home           : /u01/app/oracle/gc_inst/em/EMGC_OMS1

OMS Log Directory Location : /u01/app/oracle/gc_inst/em/EMGC_OMS1/sysman/log

OMS is not configured with SLB or virtual hostname

Agent Upload is locked.

OMS Console is locked.

Active CA ID: 2

Console URL: https://em12c.localdomain:7801/em

Upload URL: https://em12c.localdomain:4901/empbs/upload

WLS Domain Information

Domain Name            : GCDomain

Admin Server Host      : em12c.localdomain

Admin Server HTTPS Port: 7102

Admin Server is RUNNING

Managed Server Information

Managed Server Instance Name: EMGC_OMS1

Managed Server Instance Host: em12c.localdomain

WebTier is Up

Oracle Management Server is Up

[oracle@em12c ~]$

We can refer the emctl.log for more information on the status of the connectivity with node manager.

2015-10-31 20:45:32,106 [main] INFO  commands.EmbeddedWLSTRunner flush.112 - Not connected to Node Manager

2015-10-31 20:45:32,108 [main] INFO  commands.EmbeddedWLSTRunner flush.112 -

2015-10-31 20:45:32,108 [main] INFO  commands.EmbeddedWLSTRunner flush.112 -

2015-10-31 20:45:32,109 [main] INFO  oms.AdminCredsWalletUtil setInstanceHome.177 - Getting credentials from wallet

2015-10-31 20:45:32,148 [main] INFO  oms.AdminCredsWalletUtil setInstanceHome.192 - Read the credentials from wallet

2015-10-31 20:45:32,152 [main] INFO  commands.EmbeddedWLSTRunner flush.112 - Connecting to Node Manager ...

2015-10-31 20:45:32,153 [main] INFO  commands.EmbeddedWLSTRunner flush.112 -

2015-10-31 20:45:32,153 [main] INFO  commands.EmbeddedWLSTRunner flush.112 -

2015-10-31 20:45:32,470 [main] INFO  commands.EmbeddedWLSTRunner flush.112 - Successfully Connected to Node Manager.

Securing Agent

Securing OMS will not be sufficed; we have to secure all the agents dependent to the OMS. This can be done after exporting the environment for the AGENT_HOME using below command.

[oracle@em12c ~]$ emctl secure agent -emdWalletSrcUrl https://em12c.localdomain:7801/em

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

Agent is already stopped...   Done.

Securing agent...   Started.

Enter Agent Registration Password :

EMD gensudoprops completed successfully

Securing agent...   Successful.

[oracle@em12c ~]$

After successful securing the agent, we can check the status of agent using “-secure” option.

[oracle@em12c config]$ emctl status agent -secure

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

Checking the security status of the Agent at location set in /u01/app/oracle/agent/agent_inst/sysman/config/emd.properties...  Done.

Agent is secure at HTTPS Port 3872.

Checking the security status of the OMS at https://em12c.localdomain:7801/empbs/upload/...  Done.

OMS is secure on HTTPS Port 4901

[oracle@em12c config]$

We can see that the Agent is secured with OMS and with HTTPS.  After that enforce to upload agent using the traditional command.

[oracle@em12c ~]$ emctl upload agent

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

---------------------------------------------------------------

EMD upload error:full upload has failed: Upload Recent Sending Statistics

________________________________

Channel=severity send[ms]=21118 fsz=489

Channel=severity send[ms]=21136 fsz=484

..........................................................

Avg send time=1496.172 milliseconds

Backoff Event List

________________________________

Upload Failure List

_______________________________

Connection Event List

_____________________________

Upload timed out before completion.

Number of files to upload before the uploadNow call: 253, total size (MB): 0.4314556

Remaining number of files to upload: 169, total size (MB): 0.33713245 (TIMEOUT)

[oracle@em12c ~]$

[oracle@em12c ~]$ emctl upload agent

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

---------------------------------------------------------------

EMD upload completed successfully

[oracle@em12c ~]$

We can see that agent is uploaded successfully after securing the OMS and Agent as well. 

Securing Agent using Cloud Control

Securing the agents can be either done using command line command and also from EM GUI, There are more features are involved by using cloud control, like we can secure multiple agents at a time, after login to the cloud control from the summary page follow Setup à manage cloud control à agents.

After following the navigation we can view the agents whichever registered with OMS .

Then select the agent to be secured and we can provide the name of the task.

 From the parameters tab we need to provide the password of console in order to provide appropriate authorization to submit the job. 

After that we need to click the submit button hence the job will be submitted, we can check the status from the status message. 

It takes 60-70 seconds more or less in order to resecure each agent and we can determine the status whether succeeded or not. 

Summary

We’ve seen how to trust the certification chain and creating new certification authority to create the wallet and how to view the various CA Unique ID’s and also securing agents to the OMS with the new CA in command line and also using the cloud control.

Reference

http://docs.oracle.com/cd/E29505_01/doc.1111/e24473/security.htm#BABFBGEH

This video provides an overview of the Library window in Toad Data Point from Dell Software.

This video provides an overview of notifications in Toad Intelligence Central from Dell Software.

Toad for MySQL 7.7

• Online Help (html) - Complete and detailed help for users of Toad for MySQL.
• Release Notes (html) - Find a list of resolved issues, what's new in this release, and the system requirements.
• Installation Guide (html) - Instructions for installing this product.

Toad for MySQL 7.5

• Release Notes (html) - Find a list of resolved issues, what's new in this release, and the system requirements.
• Installation Guide (html) - Instructions for installing this product.

Toad for MySQL 7.3

• Release Notes (html)
• Installation Guide (html)

Toad for MySQL 7.2

• Release Notes (html)
• Installation Guide (html)

You can also find product documentation for earlier versions of Toad for MySQL at: http://documents.software.dell.com/Toad for MySQL/.

 
Released: 1 December 2015

Easily share information across your team with Toad™ Intelligence Central. This centralized repository for sharing Toad files and other data enables efficient, well-governed collaboration. Whether you’re gathering and prepping data in Toad Data Point, or sharing PL/SQL code and code analysis reports in Toad for Oracle, you can centrally publish your work in Toad Intelligence Central. This makes it quick and easy to share and view queries, files, objects and datasets — right within the tool. With this server-side component, you’ll reduce the risk of reporting failures, security threats and data loss while ensuring data governance.

POST QUESTION / COMMENT

Do you have a question or comment about this freeware?  Post it to the product forum:

Go to Forum

Toad Intelligence Central 2.7  Release Notes

Toad Intelligence Central 2.7 Deployment Guide

Toad Intelligence Central 2.7 Quick Start Guide

Written by Deepak Vohra

The debian distributions for Oracle database 10g XE include only the i386 architecture packages and not the amd64 architecture packages. The MultiarchSpec provides for cross-architecture installation of binary packages in the package manager dpkg and the packaging tool apt. In this article we shall install the i386 binaries on a amd64 architecture Ubuntu, which has added support for installing packages from multiple architectures on a single system since the 11.04 version. We shall be using Ubuntu 12.04. This article has the following sections.

Finding the Platform Architecture

Installing Oracle database XE i386 binaries

Configuring the Oracle database XE

Finding the Platform Architecture

To find what architecture does a Ubuntu platform support run the command uname –i; for example the supported architecture is x86_64.

The architecture supported by dpkg on a platform may be obtained with the following command.

dpkg –print-architecture

The foreign architecture supported may be obtained with the following command.

dpkg –print-foreign-architecture

The output on Ubuntu 12.04 installed on a x86_64 platform shows the architecture to be amd64 and foreign architecture to be i386.

The foreign architecture supported is stored in the file /etc/dpkg/dpkg.cfg.d/multiarch.

Having ascertained that we are installing i386 binaries on a amd64 platform that supports i386 as a foreign architecture, we shall install Oracle database XE i386 binaries next.

Installing Oracle database XE i386 binaries

First, fetch the i386 debian distributions for the oracle-xe-universal and libaio, which oracle-xe-universal has a dependency on using the following command.

wget -c http://oss.oracle.com/debian/dists/unstable/main/binary-i386/libaio_0.3.104-1_i386.deb http://oss.oracle.com/debian/dists/unstable/non-free/binary-i386/oracle-xe-universal_10.2.0.1-1.1_i386.deb

The libaio:i386 debian distribution gets downloaded.

The oracle-xe-universal:i386 debian distribution also gets downloaded.

Next, install the libaio:i386 debian binaries on the amd64 architecture. For the cross-architecture installation we need to include --force-architecture in the dpkg command.

sudo dpkg -i --force-architecture libaio_0.3.104-1_i386.deb

The libaio:i386 package gets installed.

Install the oracle-xe-universal:i386 package using the following command.

sudo dpkg -i --force-architecture oracle-xe-universal_10.2.0.1-1.1_i386.deb

If the system does not meet the minimum requirements for swap space the following message gets output indicating that a minimum swap space of 1024 MB is required.

Increase the swap space with the following commands.

sudo su

swapoff -a

cd /host/ubuntu/disks/

mv swap.disk swap.disk.bak

dd if=/dev/zero of=swap.disk bs=1024 count=1024000

mkswap swap.disk

swapon -a

free –m

The output shows that the swap space has been increased.

Rerun the dpkg command for the oracle-xe-universal:i386 package. The output indicates that oracle-xe-universal:i386 depends on libc6 and bc packages. The oracle-xe-universal:i386 package does not get installed due to the missing dependencies.

Ubuntu 12.04 on a amd64 platform does provide a libc6 package, but it is for the amd64 architecture. Output information about the libc:amd64 package using the dpkg-query command.

dpkg-query –s libc6:amd64

The output shows that the Architecture of the package is amd64. MultiArch- aware packages include the Multi-Arch header, which is set to “Same” for the libc6:amd64 package. Multi-Arch: same indicates that the package may be co-installed with a same-name package for a different architecture, libc6:i386 for the libc6:amd64 package, but must not be used to satisfy the dependency of any package of a different architecture from itself. Therefore, we won’t be able to substitute the libc6:i386 with the libc6:amd64 package. If the Multi-Arch were set to “foreign” the libc6:amd64 could have been used instead of libc6:i386, but it is not a feasible provision.

For correcting the dependencies run the following command twice in a sequence, which builds a dependency tree from the package list and installs the required packages.

sudo apt-get –f install

The oracle-xe-universal:i386 package dependencies bc:i386 and libc6:i386 are listed to be installed.

As the output indicates the libc6:i386, bc:i386 dependencies get setup, and the oracle-xe-universal:i386 package gets installed.

The importance of Multi-Arch: same type package becomes apparent if a same-name package for a different architecture is also required as a dependency for some other package. The bc:i386 package is not multiarch-aware (does not include the Multi-Arch header) as indicated in the package information obtained using the dpkg-query command.

If the bc:amd64 package were also required and installed, the bc:i386 package would get removed and because the oracle-xe-universal:i386 package has a dependency on the bc:i386 package the Oracle database XE would instance would stop and the oracle-xe-universal:i386 package would also get removed as shown below.

It should also be noted that we did not install the dependencies libc6:i386 and bc:i386 directly using is the sudo apt-get command for the dependencies as these dependencies have further dependency on other packages. If the libc6:i386 dependency is installed directly, it lists some other dependencies and does not get installed as shown below.

Similarly, the bc:i386 package has dependency on other packages including the libc6:i386 package.

It is best to build the dependency tree for the packages and use the sudo apt-get –f install command to install the missing dependencies. If not certain why a package has been installed run the aptitude why command for the package. For example the aptitude why libc6:i386 command outputs the dependence of oracle-xe-universal:i386 on libc6:i386.

Configuring the Oracle database XE

Having installed the oracle-xe-universal:i386 package and the required dependencies we shall configure the database next. Run the following command to configure the Oracle Database XE.

sudo /etc/init.d/oracle-xe configure

A prompt for specifying the HTTP port for Oracle Application Express gets displayed. If no value is provided, the default port of 8080 is used. A prompt for specifying the port for the database listener gets displayed with the default port as 1521. Specify the password for the SYS and SYSTEM users. Select “y” for starting database on boot. The Oracle Net Listener gets started. The database gets configured. The database instance gets started.

Next, specify the environment variables in the .bash_profile, which is opened using a vi editor. Use the following command to open the .bash_profile.

$ vi ~/$HOME/.bash_profile

We shall be using the following environment variables for ORACLE_HOME, PATH, ORACLE_SID and NLS_LANG; other variables may be specified if required.

export ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server

export PATH=$PATH:$ORACLE_HOME/bin

export ORACLE_HOME

export ORACLE_SID=XE

export NLS_LANG=’$ORACLE_HOME/bin/nls_lang.sh’

export PATH

Specify the environment variables and values as shown below in the vi editor.

The Application Express may be accessed using url http://127.0.0.1:8080/apex/. Specify the Username and Password and click on Login.

The Oracle database XE Application Express page gets displayed.

The configuration files for the Oracle database XE may be listed with the dpkg-query command for oracle-xe-universal:i386 package.

In this article we learnt about installing Oracle database XE i386 binaries on amd64 architecture Ubuntu 12.04 OS. The article illustrates the cross-architecture support for packages, provided by Ubuntu 12.04 (11.04 and later), and the procedure discussed may be used for cross-architecture installation of binaries for another version of Oracle Database also.

Product Features

• Key product features with screenshots

System requirements

Before installing Toad - Mac Edition 1.2, ensure that your system meets the following minimum hardware and software requirements.

Software Requirements

Hardware Requirements

I'm trying to connect to Sybase IQ 16 with Toad for SAP Solutions 3 from my laptop as a client.

After setting up all connection manager fields I’m getting a massage which states... <Database error> <Database server not found>

Do i need an ODBC connection on my laptop (client side?)

Note: with same connection settings Aqua Data Studio connects without any problem.

This video provides an overview of the Library window in Toad Data Point from Dell Software.

This video provides an overview of notifications in Toad Intelligence Central from Dell Software.

Toad for MySQL 7.7

• Online Help (html) - Complete and detailed help for users of Toad for MySQL.
• Release Notes (html) - Find a list of resolved issues, what's new in this release, and the system requirements.
• Installation Guide (html) - Instructions for installing this product.

Toad for MySQL 7.5

• Release Notes (html) - Find a list of resolved issues, what's new in this release, and the system requirements.
• Installation Guide (html) - Instructions for installing this product.

Toad for MySQL 7.3

• Release Notes (html)
• Installation Guide (html)

Toad for MySQL 7.2

• Release Notes (html)
• Installation Guide (html)

You can also find product documentation for earlier versions of Toad for MySQL at: http://documents.software.dell.com/Toad for MySQL/.

 
Released: 1 December 2015

Easily share information across your team with Toad™ Intelligence Central. This centralized repository for sharing Toad files and other data enables efficient, well-governed collaboration. Whether you’re gathering and prepping data in Toad Data Point, or sharing PL/SQL code and code analysis reports in Toad for Oracle, you can centrally publish your work in Toad Intelligence Central. This makes it quick and easy to share and view queries, files, objects and datasets — right within the tool. With this server-side component, you’ll reduce the risk of reporting failures, security threats and data loss while ensuring data governance.

POST QUESTION / COMMENT

Do you have a question or comment about this freeware?  Post it to the product forum:

Go to Forum

Toad Intelligence Central 2.7  Release Notes