Uninstalling Oracle WebPass

Restore the Web Server configuration file.

Grid Control Agent does not start automatically on System Reboot

1. Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup

2. Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.

3. Run the root.sh script from the Oracle home of the Management Agent:

$/root.sh

4. Restart the Management Agent by running the following command from the Oracle home of the Management Agent:

$/bin/emctl start agent

This is a one-time action to be taken. Step (1) to Step (3) will ensure that the Management Agent starts up automatically every time you restart the host in the future.

Unable to recieve Grid Control Alerts in Email

Please make sure that you have setup the notifications as per the following documents:

Note 429426.1:Configuring Email Notification Method in EM - Steps and Troubleshooting
Note 429422.1: How To Configure Notification Rules in Enterprise Manager Grid Control?

If still the issue is there then proceed with the following


- Stop the OMS:

cd /opmn/bin
./opmnctl stopall


- Login to the Repository Database as the SYSMAN user and execute:

BEGIN
emd_maintenance.remove_em_dbms_jobs();
emd_maintenance.submit_em_dbms_jobs();
commit;
end;

- Check the schedule of the dbms_jobs using:

SELECT p.display_name
FROM (SELECT display_name, dbms_jobname
FROM mgmt_performance_names
WHERE is_dbmsjob = 'Y') p,
user_jobs j
WHERE UPPER(j.what) LIKE '%'||UPPER(p.dbms_jobname)||'%'
AND (
j.broken != 'N'
OR
j.failures > 0
OR
(j.next_date < SYSDATE-1/48 AND j.this_date IS NULL)
OR
(j.next_date < SYSDATE-1/6 AND j.this_date IS NOT NULL)
);

This query should NOT return any rows.

- Re-start the OMS:

cd /opmn/bin
./opmnctl startall

- Wait for sometime and check whether you are receiving the email notifications.

Installation of Enterprise Manager Grid Control 10g

Installation of Enterprise Manager Grid Control 10g Blog

Management Pack for Oracle GoldenGate (Oracle GoldenGate Director)

When you download management pack for oracle goldengate, you have two files, director server and director client.
Here is the brief information on each of them.

Oracle GoldenGate Director is a multi-tiered client-server application that enables the configuration and management of Oracle GoldenGate instances from a remote client.

Oracle GoldenGate instances
Each instance of an Oracle GoldenGate Manger process is identified within Oracle GoldenGate Director by the fully qualified domain name of the host, the port on which Manager is listening, and a user-defined data source name.
Because a Manager process is associated with a database, this combination is identified as a data source within the Oracle GoldenGate Director Client application.

Oracle GoldenGate Director Server
Oracle GoldenGate Director Server coordinates the management of Oracle GoldenGate instances. Oracle GoldenGate Director Server is installed as an Oracle Weblogic Server domain.
Oracle GoldenGate Director Server is composed of the following applications:
● The Oracle GoldenGate Director Server application, a collection of services that controls security, host information services, object modeling, diagramming,
consolidated event logging, and alert services.
● The Monitor Agent, a client to the Oracle GoldenGate hosts that establishes a dedicated session of GGSCI (GoldenGate Software Command Interface).
The connection is used to obtain process status and event information.

Oracle GoldenGate Director database
Oracle GoldenGate Director Server uses a database as a central repository to store information about users and groups, graphical diagrams created by users, consolidated events, and other information.
A user can log into any Oracle GoldenGate Director Client on any system and retrieve his or her own stored view of the network.

Oracle GoldenGate Director Client
Oracle GoldenGate Director Client is a client application of Oracle GoldenGate Director Server that provides a graphical user interface (GUI) for managing Oracle GoldenGate instances.
The client runs on any platform that supports Java and enables drag-and-drop manipulation, menus and toolbars, and other functionality expected of a desktop application.

Oracle GoldenGate Director Web
Oracle GoldenGate Director Web is a web application that is hosted within Oracle GoldenGate Director Server. It allows remote, browser-based monitoring and control of
Oracle GoldenGate instances without the need to install software on the client system.

Oracle GoldenGate Director Administrator
Oracle GoldenGate Director Administrator is a client of Oracle GoldenGate Director Server and is used for configuring Oracle GoldenGate Director Server itself. You can use it to add
or remove Oracle GoldenGate instances and users, and to manage the overall Oracle GoldenGate Director configuration.

So, in all, these components are all for user convinience and management pack is nothing but the combination of all above director tools which helps user to monitor and manage the goldengate.

You can refer to the admin guide for management pack on how and where to install the server and related client tools and to check how they are linked to each other.

Installation of 10.2.0.5 GC Fails During Relink of Target 'agent nmo nmb nmhs emsubagent'

Installation of 10.2.0.5 GC Fails During Relink of Target 'agent nmo nmb nmhs emsubagent'

Note: It is a known bug and further information could be retreived from 837072.1

1) Modify the following files:

cd $ORACLE_HOME/sysman/lib

vi env_emagent.mk

vi ins_emagent.mk

2) Make the following changes to the ins_emagent.mk file:

i. On line 29, change the following line from:

# libnmevc \

To this:

# libnmevc

Removing the trailing slash will remove the "Syntax Error" from the make file.

3) Make the following changes to the env_emagent.mk file:

i. At or around line 2427, you should see the following line:

NEW_LD_SHLIBS = $(EMAGENT_SHLIBS)

This needs to be changed to include the EMAGENT_SHLIBS redefined after it:

NEW_LD_SHLIBS = $(EMAGENT_SHLIBS)

EMAGENT_SHLIBS= $(LIBURLDATAFETCHLET_SHARED) \

$(LIBDMSFETCHLET_SHARED) \

$(LIBOSFETCHLET_SHARED) \

$(LIBTNMECR_SHARED) \

$(LIBSPFETCHLET_SHARED) \

$(LIBOCI_SHARED) \

$(LIBWBEMFETCHLET_SHARED) \

$(LIB_UT_FETCHLET_SHARED) \

$(LIBPORTFETCHLET_SHARED) \

$(LIBTESTFETCHLET_SHARED) \

$(LIBVERFETCHLET_SHARED) \

$(LIBPROPFROMASSOCFETCHLET_SHARED) \

$(LIBSQLFETCHLET_SHARED) \

$(LIBSQLTFETCHLET_SHARED) \

$(LIBTNMECLU_SHARED) \

$(LIBTNMEVR_SHARED) \

$(LIBNMEVQ_SHARED) \

$(LIBNMEVC_SHARED) \

$(LIBNMEVSP_SHARED) \

$(LIBNMS_SHARED) \

$(LIBNMS0_SHARED) \

$(LIBNMSP_SHARED) \

$(LIB_NMADBG_SHARED) \

$(LIB_NMADM_SHARED) \

$(LIB_NMALK_SHARED) \

$(LIB_NMARL_SHARED) \

$(LIB_NMASF_SHARED) \

$(LIB_NMASTK_SHARED) \

$(LIBNMEPS_SHARED) \

$(LIB_OJMX_FETCHLET_SHARED) \

$(LIBNMECLURAC_SHARED) \

$(LIBHCFETCHLET_SHARED) \

$(LIBSGAFETCHLET_SHARED)

Grid Control Migration to New Server with Different Hostname or Domainname

Grid Control OMS and Repository Database can be migrated to new server with different hostname or domainname by using any of the two methods below.The steps below are applicable only if both source and destination servers are on the same OS platform.

Method 1

---------

1.Stop the OMS and Agent running on OMS server( the agent installed with the OMS) .

2.Clean up the Central Management Agent ( the agent installed with the OMS):

Connect to the repository DB as SYSMAN and execute the following PL/SQL API:

SQL> exec mgmt_admin.cleanup_agent('');

Note: - This command may take some time to complete, so please don't interrupt.

- To get the old agent name use the following query:

select target_name from mgmt_targets where target_type='oracle_emd';

3.Migrate the Repository Database to target server .You can refer to 'Doc ID 602955.1' for the same.

4.Install Additional OMS on new server following the document below

'Installing an Additional Oracle Management Service Release 5 (10.2.0.5)'

http://download.oracle.com/docs/cd/B16240_01/doc/install.102/e10953/installing_em.htm#CHDJFFGJ

5.Point the target Agents to the new OMS following the steps in the Documentation below

'Configuring the Management Agent to Use a New Management Service'

http://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10954/postinstall_config.htm#i1024275

Method 2

---------

If you prefer to reduce downtime and dont want to stop the source OMS before the installation of Additional OMS then follow the steps as below

1.Install Additional OMS on new server pointing to existing repository database on source server following the document below

'Installing an Additional Oracle Management Service Release 5 (10.2.0.5)'

http://download.oracle.com/docs/cd/B16240_01/doc/install.102/e10953/installing_em.htm#CHDJFFGJ

2.Then stop both the OMS and migrate Database to new server

3.Configure the OMS on new server to point to Repository on new server.You can refer to documentattion below for the same

http://download.oracle.com/docs/cd/B16240_01/doc/install.102/e10953/postinstall_config.htm#i1020180

4.Clean up the Central Management Agent on the source server ( the agent installed with the OMS):

Connect to the repository DB as SYSMAN and execute the following PL/SQL API:

SQL> exec mgmt_admin.cleanup_agent('');

Note: - This command may take some time to complete, so please don't interrupt.

- To get the old agent name use the following query:

select target_name from mgmt_targets where target_type='oracle_emd';

5.Start the OMS on new server

6.Point the target Agents to the new OMS following the steps in the Documentation below

'Configuring the Management Agent to Use a New Management Service'

http://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10954/postinstall_config.htm#i1024275

How to deal with Multiple Entries for the same host in Grid Control

How to deal with Multiple Entries for the same host in Oracle Enterprise Manager Grid Control 10g.

Steps:

Please find below the steps to remove the host entry. 

Delete targets discovered using the Agent. Targets-->Oracle Applications-->Remove. Wait around 20 min to let it complete.

To view the removal status, click on the global "Setup" link
--> Management Services and Repository
--> Overview page
--> General section
--> Deleted Targets

However,  you can change the host property of an agent through emcli utility . It will not create the duplicate entry.

How to setup emcli:

http://download.oracle.com/docs/cd/B16240_01/doc/em.102/b40004/cli.htm#sthref10

Emcli sample command:

emcli modify_target -name="" -type="" -properties="MachineName=hostname.domainname" -on_agent

oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsDiscoveryException: Fail to get EMDClient for Host hostname

Error:

Caused By: oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsDiscoveryException: Fail to get EMDClient for Host hostname

Caused By: java.sql.SQLException: ORA-01403: no data found

ORA-06512: at "SYSMAN.EM_JOB_UTIL", line 1087

ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 19035

ORA-06512: at line 1

Cause:

Hostname lacks domainname

Solution:

Step 1.  Bounce the Agent.

Step 2.  Create a backup copy of AGENT_HOME/sysman/emd/targets.xml.

Step3. Edit targets.xml and change the host property from hostname to hostname.domainname

Step4. Start , upload the agent and redo the discovery.

If this doesn’t work , you can restore the targets.xml.

However,  you can change the host property of an agent through emcli utility . It will not create the duplicate entry.

How to setup emcli:

http://download.oracle.com/docs/cd/B16240_01/doc/em.102/b40004/cli.htm#sthref10

Emcli sample command:

emcli modify_target -name="" -type="" -properties="MachineName=hostname.domainname" -on_agent

Installing Oracle Enterprise Manager Grid Control 11g on RHEL 5

In this article I will take you through step by step installation of Oracle Weblogic Server,Oracle Database 11g and Enterprise Manager Grid Control 11g.
Please make sure following rpm's are installed.
binutils
compat-libstdc++
elfutils-libelf
glibc-2.5-12
glibc-2.5-24
ksh
libaio
libgcc
libstdc++
make
elfutilslibelf-devel
elfutils-libelf-devel-static
kernel-headers
glibcheaders
glibc-devel
libstdc++-devel
libgomp
gcc
gcc-c++
libaiodevel
sysstat
unixODBC
unixODBC-devel
rng-utils
setarch
compatdb
pdksh
compat-libstdc++-33
compat-libstdc++-296
lsof
strace
wget
system-config-lvm

Installation Oracle WebLogic Server 11gR1 (10.3.2)

. Before installing,  create OS users and group.

groupadd dba

useradd -g dba -G oinstall oraoem

mkdir /u01/app/oraoem/Middleware

chown -R oraoem:dba /u01/app/oraoem/Middleware

./wls1032_linux32.bin

Install Database 11gR2

The following requirements are necessary:

/etc/sysctl.conf:

kernel.shmmni = 4096

kernel.sem = 250 32000 100 128

fs.file-max = 6815744

fs.aio-max-nr = 1048576

net.ipv4.ip_local_port_range = 9000 65500

net.core.rmem_default = 262144

net.core.rmem_max = 4194304

net.core.wmem_default = 262144

net.core.wmem_max = 1048576

/etc/security/limits.conf:

ora11gr2 soft nproc 2047

ora11gr2 hard nproc 16384

ora11gr2 soft nofile 1024

ora11gr2 hard nofile 65536

oraoem soft nproc 2047

oraoem hard nproc 16384

oraoem soft nofile 1024

oraoem hard nofile 65536

/etc/profile:

if [ $USER = "ora11gr2" ]; then

if [ $SHELL = "/bin/ksh" ]; then

ulimit -u 16384

ulimit -n 65536

else

ulimit -u 16384 -n 65536

fi

fi

if [ $USER = "oraoem" ]; then

if [ $SHELL = "/bin/ksh" ]; then

ulimit -u 16384

ulimit -n 65536

else

ulimit -u 16384 -n 65536

fi

fi

useradd -g dba ora11gr2

mkdir -p /u01/app/ora11gr2

chown -R ora11gr2:dba /u01/app/ora11gr2

unzip linux_11gR2_database_1of2.zip

unzip linux_11gR2_database_2of2.zip

export ORACLE_BASE=/u01/app/ora11gr2

./runInstaller

At this point, we are installing Oracle Binaries only, without creating a database.

Installation of RDBMS patches:

I recommend to download and install these patches:

OPatch p6880880_112000_LINUX.zip

p6880880_112000_LINUX.zip

p9165206_112010_LINUX.zip

p9352237_112010_LINUX.zip

DBCA

Network Configuration (Listener, TNS)

 

Database Preparations

Ensure that the UNDO tablespace and the TEMP tablespace are autoextensible in

the existing, certified Oracle Database. Moreover, resize UNDO tablespace to

>200M.

Documentation mentions that for RDBMS 11.2.0.1 as Grid Control Repository, patch for

bug# 9002336 and 9067282 should be installed. I prefer to install PSU 11.2.0.1.1, which

contains bugfix 9067282. Bug 9002336 can be addressed by underscore parameter

"_optimizer_distinct_agg_transform = false"

SQL> alter system set "_optimizer_distinct_agg_transform"=false

scope=spfile;

SQL> alter system set log_buffer=10485760 scope=spfile;

SQL> alter system set processes = 500 scope=spfile;

SQL> alter system set session_cached_cursors=200 scope=spfile;

SQL> alter database datafile

'/u01/app/ora11gr2/oradata/EMREP/undotbs01.dbf' resize 256M;

Check whether fine grained access control is installed:

select value from v$option where parameter = 'Fine-grained

access control';

At this point, deinstall DB Control:

./emca -deconfig dbcontrol db -repos drop

Note:

My Oracle Support Node 561429.1 mentions that 11.2.0.1 can only be used as repository,

if DNS is used. For my demo installation, I prefer usage of /etc/hosts. I have tested and

found no issues without DNS.

Upgrade Weblogic Server To WDJ7


cd /u01/app/oraoem/Middleware
cd utils/bsu
./bsu.sh

Click Tab "Get Patches", Select WDJ7 and click "Download Selected".

Instllation Enterprise Manager Grid Control 11g

Installation is now complete and Grid Control can be accessed via browser:

https://testsystem:7799/em/

Click on "Setup" Tab, then Agents, then testsystem:3872. Then you see that EMREP database

is not configured yet.

Unlock and set the password:

SQL> user dbsnmp identified by xxx account unlock;

Configure the respective password for dbsnmp and finish.

Enterprise Manager Grid Control 11g Patches

Environment-Files:

/home/oraoem/OMS.env:

export ORACLE_HOME=/u01/app/oraoem/Middleware/oms11g

export PATH=$ORACLE_HOME/bin:$PATH

/home/oraoem/AGENT.env:

export ORACLE_HOME=/u01/app/oraoem/Middleware/agent11g

export PATH=$ORACLE_HOME/bin:$PATH

Stoppen von OMS und Agent

as root: /etc/init.d/gcstartup stop

OMS Patch: (as oraoem)

. /home/oraoem/OMS.env

unzip p9659466_111010_Generic.zip

cd 9659466

/u01/app/oraoem/Middleware/oms11g/OPatch/opatch apply

/u01/app/oraoem/Middleware/oms11g/bin/rcuJDBCEngine

sys/xxx@ora-vm2.intra:1521:EMREP JDBC_SCRIPT

post_install_script.sql $PWD $ORACLE_HOME

Agent Patch: (as oraoem)

. /home/oraoem/AGENT.env

unzip p9738008_111010_LINUX.zip

cd 9738008

/u01/app/oraoem/Middleware/agent11g/OPatch/opatch apply

unzip p9676134_111010_Generic.zip

cd 9676134

/u01/app/oraoem/Middleware/agent11g/OPatch/opatch apply