DBControl/11g OEM and Shared Servers - Part II

As noted in this post here, I previously had problems with the 11g EM Agent connecting to the database using a shared server instead of a dedicated one.

I've recently had the joy of performing a switchover of a dataguard primary & secondary so have had to re-create a bunch of stuff, including the OEM repositories.  Due to some major configuration issues with the standby I've ended up dropping and recreating the repositories completely, so have had to revisit this issue.

I followed my own advice in the previous post, which got rid of one of the sessions using shared servers, but the OMS was still connecting using a shared server.  I have a vague memory of resolving this before but the details eluded me, so I did it this way.


  • cd $ORACLE_HOME/$HOSTNAME_SERVICENAME/
    (e,g. cd $ORACLE_HOME/server1.domain.local_ORCL/
  • vi sysman/config/emoms.properties
  • Find the line starting:
    oracle.sysman.eml.mntr.emdRepConnectDescriptor
  • After the SERVICE_NAME or SID section, add:
    (SERVER\=DEDICATED)
  • Save the file
  • Restart dbconsole:
    $ORACLE_HOME/bin/emctl stop dbconsole
    $ORACLE_HOME/bin/emctl start dbconsole
Job done.

After thinking about it and exploring the settings some more, I think I may have resolved this before by going to Setup->Management Services and Repository->Monitoring Configuration and setting a custom connect descriptor, but I'm not completely sure.

Comments

Post a Comment

Popular posts from this blog

Data Guard with Transparent Application Failover (TAF)

One of the problems with Data Guard is that even after switching/failing over to the standby database, all clients need to be reconfigured to communicate with the new primary. The simplest way to achieve this (if using a centralised tnsnames.ora ), is to modify the file and  add the line " (FAILOVER=YES) ",  and either multiple ( DESCRIPTION=...) or (ADDRESS=...)  lines, one for each of the standby systems, in the order that the client should attempt connections . This tells the client to try each address in turn until one succeeds. Doing so provides basic failover functionality within Oracle Net, and will probably function correctly most of the time.  Though be aware - because both primary and standby can share the same instance name (e.g. the same SID, therefore the same connection string), there is potential for this simple scheme to go wrong. An example in an active data guard environment (where the standby is open read only): a temporary network issue causes all c
Read more

RMAN-05531 During RMAN Duplicate from Active Data Guard Standby

[oracle@target dbs]$ rman auxiliary sys@dup target sys@source [...] RMAN> duplicate target database to DUP from active database db_file_name_convert '/u2/data/PROD','/u2/data/DUP' LOG_FILE_NAME_CONVERT '/u2/data/PROD/onlinelog','/u2/data/DUP' nofilenamecheck; Starting Duplicate Db at 25-FEB-15 using target database control file instead of recovery catalog allocated channel: ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: SID=171 device type=DISK RMAN-00571: =================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ======= RMAN-00571: =================================================== RMAN-03002: failure of Duplicate Db command at 02/25/2015 16:04:44 RMAN-05501: aborting duplication of target database RMAN-05531: a mounted database cannot be duplicated while datafiles are fuzzy Using Oracle 11.2.0.3 (anything below 11.2.0.3.6), this is the error if an attempt is made to duplicate from an activ
Read more

Data pump - "ORA-39786: Number of columns does not match between export and import databases"

Today I was asked if it was possible to import data for a specific table from a data pump export file, which was taken from when a table had a different structure to what it has now. e.g. when the export was taken, there were 10 columns.  Now there are 11. I thought that was simple, and I was sure I'd heard of this being done before.  Simply import using the "CONTENT=DATA_ONLY" parameter.  Right? Apparently not: Centos-/home/oracle/demo> impdp DEMO_USER/yyyyyyy directory=INBOUND dumpfile=demo_data.dmp logfile=impdpdemo.log content=data_only tables=xxxxxxxx Import: Release 10.2.0.4.0 - 64bit Production on Tuesday, 08 July, 2014 14:32:20 Copyright (c) 2003, 2007, Oracle.  All rights reserved. Connected to: Oracle Database 10g Release 10.2.0.4.0 - 64bit Production Master table "DEMO_USER"."SYS_IMPORT_TABLE_01" successfully loaded/unloaded Starting "DEMO_USER"."SYS_IMPORT_TABLE_01":  xxxxxxxx/******** directory=INBOUND dumpfile
Read more