Em grid control 10.2.0.5 add local database problem

Hi,
I can not add local database to gc.
The following error is reported:
Exception caught when retrieving oracle_database metadata - SAXParseException in parsing Response :: Computed columns can be specified only after other columns
when I want to add monitor passwd the following is reported
Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor The Connection descriptor used by the client was: (description=(address=(host=devstdby.ucstech.eu)(protocol=tcp)(port=1521))(connect_data=(sid=devstdby)(server=dedicated)))
I have emrep db (10.1) with listener on 1521 port
and db which I want to add to gc with listener running on 1522 port
both on the same machine
Both listeners are correctly configured in gc and running, why listener running on port 1522 is not used to connect to second db ?

Hello could you check the configuration of both Listeners within OEM?
So look for both listeners in the All Targets tab and select configure.
Check for the values in:
Port Number
listener.ora directory
Oracle Home
Make sure these values are correct.
Regards
Rob
For more Tips and Tricks on OEM GC see: http://oemgc.wordpress.com

Similar Messages

Grid Control 10.2.0.1.1 Silent Installation Problem

I seem to be having issue installing Grid Control 10.2.0.1.1; I am using the silent install with existing database method and for some reason, the installation process is not using some variable I have specified in the response file.
My operating environment is as follows
Redhat Enterprise Linux 5.2 [Tikanga] - 32bit
Repository: Oracle Database 11gR2Variables that I have specifed in the response file and are not being used are below.
>
s_mgmtTbsName="/u02/oradata/emrep/oradata/mgmt.dbf"
s_ecmTbsName="/u02/oradata/emrep/oradata/mgmt_ecm_depot1.dbf"
>
slientInstall log has the following entries
silentInstall2010-08-18_01-15-29-PM.log
*** Error Dialog: OUI-10150:Error: The file system location /u01/app/oracle/product/oms10g/oradata does not exist. Please enter the path of an existing directory. in component Oracle Enterprise Manager Grid Console 10.2.0.1.1 . Installation cannot continue for this component. ***
User Selected: S&top installation of this component only.
The file system location /u01/app/oracle/product/oms10g/oradata does not exist. Please enter the path of an existing directory.
This silent installation was unsuccessful.installActions log file has the following entries
INFO: Setting variable 's_mgmtTbsName' to '/u01/app/oracle/product/oms10g/oradata/mgmt.dbf'. Received the value from the variable calculation.
INFO: Calling Query fileQueries10.1.0.3.0 exists
filename = /u01/app/oracle/product/oms10g/oradata
INFO: Query Returned: false
User Selected: S&top installation of this component only.
The file system location /u01/app/oracle/product/oms10g/oradata does not exist. Please enter the path of an existing directory.
This silent installation was unsuccessful.Regard,
Phiri

[oracle@oracledba Disk1]$ cat response/em_using_existing_db.rsp
## copyright (c) 1999, 2004 Oracle. All rights reserved.          ##
## Specify values for the variables listed below to customize     ##
## your installation.                                             ##
## Each variable is associated with a comment. The comment        ##
## identifies the variable type.                                  ##
## Please specify the values in the following format:             ##
##         Type         Example                                   ##
##         String       "Sample Value"                            ##
##         Boolean      True or False                             ##
##         Number       1000                                      ##
##         StringList   {"String value 1","String Value 2"}       ##
## The values that are given as <Value Required> need to be       ##
## specified for a silent installation to be successful.          ##
## This response file is generated by Oracle Software             ##
## Packager.                                                      ##
RESPONSEFILE_VERSION=2.2.1.0.0
#Name       : UNIX_GROUP_NAME
#Datatype   : String
#Description: Unix group to be set for the inventory directory. Valid only in Unix platforms.
#Example: UNIX_GROUP_NAME = "install"
UNIX_GROUP_NAME="oinstall"
#Name       : FROM_LOCATION
#Datatype   : String
#Description: Complete path to the products.xml.
#Example: FROM_LOCATION = "../stage/products.xml"
FROM_LOCATION="/u02/orasoft/gc_10201/Disk1/rdbms/Disk1/stage/products.xml"
#Name       : FROM_LOCATION_CD_LABEL
#Datatype   : String
#Description: This variable should only be used in multi-CD installations. It includes the label of the compact disk where the file "products.xml" exists. The label can be found in the file "disk.label" in the same directory as products.xml.
#Example: FROM_LOCATION_CD_LABEL = "CD Label"
#FROM_LOCATION_CD_LABEL="EM10g"
#Name       : BASEDIR
#Datatype   : String
#Description: Directory where the ORACLE_HOMES gets created
#Example: BASEDIR = "C:\OHOME1" or BASEDIR = "/scratch/OracleHomes"
BASEDIR="/u01/app/oracle/product"
#Name       : INSTALLATION_NAME
#Datatype   : String
#Description: Oracle Home Name. Used in creating folders and services.
#Example: INSTALLATION_NAME = "OHOME1"
INSTALLATION_NAME="oms10g"
#Name       : NEXT_SESSION
#Datatype   : Boolean
#Description: Set to true to allow users to go back to the File Locations page for another installation. This flag also needs to be set to true in order to process another response file (see NEXT_SESSION_RESPONSE).
#Example: NEXT_SESSION = true
NEXT_SESSION=true
#Name       : NEXT_SESSION_ON_FAIL
#Datatype   : Boolean
#Description: Set to true to allow users to invoke another session even if current install session has failed. This flag is only relevant if NEXT_SESSION is set to true.
#Example: NEXT_SESSION_ON_FAIL = true
NEXT_SESSION_ON_FAIL=true
#Name       : DEINSTALL_LIST
#Datatype   : StringList
#Description: List of components to be deinstalled during a deinstall session.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name, Version : External name. Please use the internal name and version while specifying the value.
#    oracle.sysman.top.agent, 10.2.0.0.0 : Oracle Management Agent 10.2.0.0.0
#    oracle.sysman.top.em_seed, 10.2.0.0.0 : Oracle Enterprise Manager Repository Database 10.2.0.0.0
#    oracle.sysman.top.oms, 10.2.0.0.0 : Oracle Enterprise Manager Grid Console 10.2.0.0.0
#Example: DEINSTALL_LIST = {"oracle.sysman.top.agent","10.2.0.0.0"}
DEINSTALL_LIST={"oracle.sysman.top.oms","10.2.0.1.1"}
#Name       : SHOW_DEINSTALL_CONFIRMATION
#Datatype   : Boolean
#Description: Set to true if deinstall confimation is needed during a deinstall session.
#Example: SHOW_DEINSTALL_CONFIRMATION = true
SHOW_DEINSTALL_CONFIRMATION=true
#Name       : SHOW_DEINSTALL_PROGRESS
#Datatype   : Boolean
#Description: Set to true if deinstall progress is needed during a deinstall session.
#Example: SHOW_DEINSTALL_PROGRESS = true
SHOW_DEINSTALL_PROGRESS=true
#Name       : REMOVE_HOMES
#Datatype   : StringList
#Description: List of the homes to be removed during a deinstall session. Each home is represented by its full path.
#Example: REMOVE_HOMES = {<full_path_of_home1>,<full_path_of_home2>, ...}
REMOVE_HOMES=<Value Unspecified>
#Name       : ACCEPT_LICENSE_AGREEMENT
#Datatype   : Boolean
#Description: By setting this variable to true, you are accepting the license agreement. This variable is used only for silent installations.
#Example: ACCEPT_LICENSE_AGREEMENT = true
ACCEPT_LICENSE_AGREEMENT=true
#Name       : TOPLEVEL_COMPONENT
#Datatype   : StringList
#Description: The top level component to be installed in the current session.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name, Version : External name. Please use the internal name and version while specifying the value.
#    oracle.sysman.top.agent, 10.2.0.0.0 : Oracle Management Agent 10.2.0.0.0
#    oracle.sysman.top.em_seed, 10.2.0.0.0 : Oracle Enterprise Manager Repository Database 10.2.0.0.0
#    oracle.sysman.top.oms, 10.2.0.0.0 : Oracle Enterprise Manager Grid Console 10.2.0.0.0
#Example: TOPLEVEL_COMPONENT = {"oracle.sysman.top.agent","10.2.0.0.0"}
TOPLEVEL_COMPONENT={"oracle.sysman.top.oms","10.2.0.1.1"}
#Name       : SELECTED_LANGUAGES
#Datatype   : StringList
#Description: Languages in which the components will be installed.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name : External name. Please use the internal name while specifying the value.
#    en,   : English
#    de,   : German
#    es,   : Latin American Spanish
#    es_MX,   : Mexican Spanish
#    es_ES,   : Spanish
#    fr,   : French
#    fr_CA,   : Canadian French
#    it,   : Italian
#    iw,   : Hebrew
#    ja,   : Japanese
#    ko,   : Korean
#    pt_BR,   : Brazilian Portuguese
#    zh_CN,   : Simplified Chinese
#    zh_TW,   : Traditional Chinese
#Example: SELECTED_LANGUAGES = {"en"}
#SELECTED_LANGUAGES={"en"}
#Name       : COMPONENT_LANGUAGES
#Datatype   : StringList
#Description: Languages in which the components will be installed.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name : External name. Please use the internal name while specifying the value.
#    en,   : English
#    de,   : German
#    es,   : Latin American Spanish
#    es_MX,   : Mexican Spanish
#    es_ES,   : Spanish
#    fr,   : French
#    fr_CA,   : Canadian French
#    it,   : Italian
#    iw,   : Hebrew
#    ja,   : Japanese
#    ko,   : Korean
#    pt_BR,   : Brazilian Portuguese
#    zh_CN,   : Simplified Chinese
#    zh_TW,   : Traditional Chinese
#Example: COMPONENT_LANGUAGES = {"en"}
#Component : oracle.sysman.top.oms
COMPONENT_LANGUAGES={"en"}
#Name       : s_reposHost
#Datatype   : String
#Description: Hostname of the Repository database
#Component : oracle.sysman.top.oms
#Example    :s_reposHost="stadv26.us.oracle.com"
s_reposHost="oracledba"
#Name       : s_reposPort
#Datatype   : String
#Description: Port on which the Repository database is running
#Component : oracle.sysman.top.oms
#Example    :s_reposPort="1521"
s_reposPort="1521"
#Name       : s_reposSID
#Datatype   : String
#Description: SID or Service name of the Repository database
#Component : oracle.sysman.top.oms
#Example    :s_reposSID="emrep"
s_reposSID="emrep"
#Name       : s_reposDBAPwd
#Datatype   : String
#Description: Password of DBA user used to create repository schema
#Component : oracle.sysman.top.oms
# Example   : s_reposDBAPwd="password"
s_reposDBAPwd="emgc10g"
#Name       : s_mgmtTbsName
#Datatype   : String
#Description: Mgmt tablespace name
#Component : oracle.sysman.top.oms
#This will get created on the machine where the database is present
#So make sure that the directory given here is present in the machine where the database exists
#ORACLE_HOME/oradata/mgmt.dbf
#Example   : s_mgmtTbsName=/scratch/OracleHomes/oradata/mgmt.dbf
s_mgmtTbsName="/u02/oradata/emrep/oradata/mgmt.dbf"
#Name       : s_ecmTbsName
#Datatype   : String
#Description: ECM tablespace name
#Component : oracle.sysman.top.oms
#This will get created on the machine where the database is present
#So make sure that the directory given here is present in the machine where the database exists
#ORACLE_HOME/oradata/mgmt_ecm_depot1.dbf
#Example    : s_ecmTbsName=/scratch/OracleHomes/oradata/mgmt_ecm_depot1.dbf
s_ecmTbsName="/u02/oradata/emrep/oradata/mgmt_ecm_depot1.dbf"
#Name       : b_emailSelected
#Datatype   : Boolean
#Description: Whether to receive automatic threshold notification email
#Component : oracle.sysman.top.oms
#Example    : b_emailSelected=false/true
b_emailSelected=<Value Unspecified>
#Name       : s_emailAddress
#Datatype   : String
#Description: Address to receive threshold notification email, this will be effected only when b_emailSelected=true
#Component : oracle.sysman.top.em_seed
s_emailAddress=<Value Unspecified>
#Name       : s_emailServer
#Datatype   : String
#Description: SMTP gateway used to send threshold notification email, this will be effected only when b_emailSelected=true
#Component : oracle.sysman.top.em_seed
s_emailServer=<Value Unspecified>
#Name       : b_metalinkSelected
#Datatype   : Boolean
#Description: Whether MetaLink connection was configured
#Component : oracle.sysman.top.em_seed
#Example    : b_metalinkSelected=false/true
b_metalinkSelected=<Value Unspecified>
#Name       : s_metalinkUser
#Datatype   : String
#Description: user name for MetaLink access, this will be effected only when b_metalinkSelected=true
#Component : oracle.sysman.top.em_seed
s_metalinkUser=<Value Unspecified>
#Name       : s_metalinkPassword
#Datatype   : String
#Description: password for MetaLink access, this will be effected only when b_metalinkSelected=true
#Component : oracle.sysman.top.em_seed
s_metalinkPassword=<Value Unspecified>
#Name       : b_proxySelected
#Datatype   : Boolean
#Description: Whether proxy connection was configured
#Component : oracle.sysman.top.em_seed
#Example: b_proxySelected=false/true
b_proxySelected=<Value Unspecified>
#Name       : EM_PROXYUSER
#Datatype   : String
#Description: User name for proxy access,this will be effected only when b_proxySelected=true
#Component : oracle.sysman.top.em_seed
EM_PROXYUSER=<Value Unspecified>
#Name       : EM_PROXYREALM
#Datatype   : String
#Description: Server providing proxy access, this will be effected only when b_proxySelected=true
#Component : oracle.sysman.top.em_seed
EM_PROXYREALM=<Value Unspecified>
#Name       : EM_PROXYPASSWORD
#Datatype   : String
#Description: Password for proxy access, this will be effected only when b_proxySelected=true
#Component : oracle.sysman.top.em_seed
EM_PROXYPASSWORD=<Value Unspecified>
#Name       : EM_PROXYHOST
#Datatype   : String
#Description: Server providing proxy access, this will be effected only when b_proxySelected=true
#Component : oracle.sysman.top.em_seed
EM_PROXYHOST=<Value Unspecified>
#Name       : EM_DONTPROXYFOR
#Datatype   : String
#Description: Domains which should not use proxy access, this will be effected only when b_proxySelected=true
#Component : oracle.sysman.top.em_seed
EM_DONTPROXYFOR=<Value Unspecified>
#Name       : EM_PROXYPORT
#Datatype   : String
#Description: Port for proxy access, this will be effected only when b_proxySelected=true
#Component : oracle.sysman.top.em_seed
EM_PROXYPORT=<Value Unspecified>
#Name       : s_securePassword
#Datatype   : String
#Description: Password for secure communication with Management Server
#Component : oracle.sysman.top.oms
#Example    : s_securePassword="password"
s_securePassword="emgc10g"
#Name       : s_securePasswordConfirm
#Datatype   : String
#Description: Confirmation of password for secure communication with Management Server
#Component : oracle.sysman.top.oms
#Example    : s_securePasswordConfirm="password"
s_securePasswordConfirm="emgc10g"
#Name       : b_lockedSelected
#Datatype   : Boolean
#Description: Whether agent communication should be locked
#Component : oracle.sysman.top.oms
#Example    : b_lockedSelected=true/false
b_lockedSelected=false
#Name       : s_reposPwd
#Datatype   : String
#Description: Password of repository schema owner
#Component : oracle.sysman.top.oms
#Example    : s_reposPwd="password"
s_reposPwd="emgc10g"
#Name       : s_reposPwdConfirm
#Datatype   : String
#Description: Password for repository schema owner
#Component : oracle.sysman.top.oms
#Example    : s_reposPwdConfirm="password"
s_reposPwdConfirm="emgc10g"
#Please Don't change the values of these variables
n_firstInstanceValidation=2
n_firstReposValidation=1
n_firstReposPwdValidation=2
n_firstSecureValidation=2
n_firstVldnEmailSer=2
#Name       : b_upgrade
#Datatype   : Boolean
#Description: To Specify whether it is Normal Install or Upgrade
#Component : oracle.sysman.top.oms
#PLEASE DON'T CHANGE THIS VALUE
b_upgrade=false
#Name       : b_showOptConfigPage
#Datatype   : Boolean
#Description: whether to perform optional configuration
#Component : oracle.sysman.top.oms
#PLEASE DON'T CHANGE THIS VALUE
b_showOptConfigPage=TRUE
#Name       : s_installType
#Datatype   : String
#Description: Type of Grid Control install being performed
#Component : oracle.sysman.top.oms
#PLEASE DON'T CHANGE THIS VALUE
s_installType="NOSEED"
[oracle@oracledba Disk1]$

Installing OEM Grid Control on Solaris Sparc using an existing database

During installing OEM 10g on Solaris, after select "using an existing database" the connect string for database (host:port:sid) never is solicited and the path for datafiles neither, then the installation cancel.
On Windows, this type of installation in the same version work fine!
1_ How I do to install OEM 10g on Solaris using an existing db?
Tx,
Diego.

Have you installed the Management Agent for the target database?

Oracle 10.2 Grid Control – Adding Database residing on different hosts

I used to work with Oracle 9.2 Enterprise Manager. Now I have installed Oracle 10.2.0.2 Grid Control on Windows 2000. I want to do database administrator from Oracle Grid Control for Oracle 9i, Oracle 10.1 and 10.2 databases. I do not want to install any agents on my database servers because they are production servers,
All of I am interested in to have nice user interface of Oracle 10g grid control, so I can do database administration such as adding a database file, looking at database users, sessions etc. I was able to do all of that with Oracle9i enterprise manager. IN Oracle9i EM, one can manually add a database instance if it cannot be discovered using an agent. Is it possible to do that in Oracle 10g grid control?
When I start Grid Control, go to targets tab and then database tab and want to add a database, it asks for host name. When I enter hostname (which is accessible from the network), it says host not found. Is an agent required on the host before Grid Control can recognize it. In Oracle 9i enterprise manager, there was an option to manually add a database (i.e. automatic discovery was not successful), is it possible to do that with Oracle 10g grid control.

Over the years, working with Oracle, I've found tremendous value in reading the docs. You might find similar value doing that too.
The only issue you seem to have is an unwillingness to learn the architecture and concepts behind the product you are trying to install. You get rid of the error by deleting the entry and doing it correctly.
There is no way to drop a brick on your foot and not have it hurt. <g>

Create dataguard 11gR2 uisng Grid Control fails

Hello !
I'm testing to use data guard using grid control. I have a fresh standard database created with dbca
When i start the gui i come to the Add Standby Database: Database Location screen
I add the information required and select next, then I get:
Internal Error has occurred. Check the log file for details.
I'm trying io locate the log files, but not sure where they are. Where shall I look ?
I have also tested to create a standby db using rman and it worked fine.
Appreciate your comments.
Thanks
Magnus

Hi!
The logfiles for OMS are, if you use GC11g:
$MIDDLEWARE_HOME/<Instance_Name>/user_projects/domains/EMGC_DOMAIN/servers/EMGC_OMS1/sysman/log
or something similiar
If you using GC 10, than the logfiles are: $oms_ORACLE_HOME/sysman/log
kIND REGARDS1

Grid control 10.2.0.3 with DB 10.2.0.4

Hi,
I have installed Oracle Enterprise Manager Grid Control 10.2.0.3 with new database along with the installation.
I also have a Existing database 10.2.0.4 in another server.
1. How can I upgrade my Grid control 10.2.0.3 to 10.2.0.4?
2. How can I monitor/Connect my Existing database 10.2.0.4 from Grid Control 10.2.0.3?
Is it possible to monitor database 10.2.0.4 from Grid Control 10.2.0.3 which is lower version?
Kindly provide the exact document/steps to do the above activities.
Regards,

Thanks for All for replying.
*1. How can I upgrade my Grid control 10.2.0.3 to 10.2.0.4?*
I have upgraded the Grid Control Agent and OMS from 10.2.0.3 to 10.2.0.4
When we upgrade the OMS which also upgrade the Repository database.
Apply the patchset p3731593_10204_Linux-x86-64.zip (Which comes with Grid_Control_10.2.0.4.0_Linux-x86-64.zip)
su - oracle
cd 3731593/Disk1
./runInstaller (Run two times for Agent and oms upgrade)
Agent upgrade_
During upgrade
Specify Home Details: Select the Agent Home to upgrade Grid Control Agent.
Ex: /u01/app/oracle/OracleHomes/agent10g
OMS upgrade+
Specify Home Details: Select the oms home to upgrade oms
Ex: /u01/app/oracle/OracleHomes/oms10g
*2. How can I monitor/Connect my Existing database 10.2.0.4 from Grid Control 10.2.0.3?*
Install Grid Agent on the existing database server 10.2.0.4
Download Linux_x86_64_Grid_Control_agent_download_10_2_0_4_0.zip from OTN http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
su - oracle
cd /u01/software/GridAgent/linux_x64/agent
./runInstaller
Refer:
[To Install an Additional Management Agent Using OUI|http://download.oracle.com/docs/cd/B16240_01/doc/install.102/e10953/installing_em.htm#sthref318]
OracleÂ® Enterprise Manager Grid Control Installation and Basic Configuration
10g Release 4 (10.2.0.4)
Part Number E10953-05
3 Installing Enterprise Manager
Thanks
Mukarram Khan
Edited by: Mukarram Khan on Feb 6, 2009 11:04 PM

What does "remove target" do in Grid Control?

I have some targets that got created during agent installation that aren't real databases. I was wondering what removing the target does. Does it just remove the meta data about the target or if the target is a database will it try to delete the database? Does it modifiy the listener.ora file?

It only deregisters the target and it won't show up in GC.
For e.g. if you remove a database, you won't be able to manage it in Grid Control. It will NOT drop the database on your managed target.

Grid Control on Windows 64bit

Hi all,
I very new on Grid Control because actual I only have one database to administrate so the Enterprise Manger is very fine.
But in the future this will be expanded to 4 or 5 databases on different machines so I think the Grid Control will "help" me... Or I'm wrong?
Now the thing is, that my company is using Windows 2003 R2 64bit as OS and the Databases will be 10.2.0.4 64bit.
So now I'm on the Oracle Grid Control page and see, that Grid Control is not available for Windows in 64bit.
So I think now, that I have to have an additional Windows 32bit Server for running Grid Control and the Agent’s as 64bit for Windows for the Databases.
Or does someone have a different idea??
Thanks for your help.
Br
Joerg

Hi,
thanks for your post.
I have checked it on MetaLink and as you can see on the screenshot Windows x64 is not certified.
So I think I have to run an additional Windows 2003 32bit.
How ever... thanks.
br
Joerg

Figures in Grid Control and Enterprise Manager Console don't match!

Hi,
I have just installed Oracle 10g Grid Control and it is managing an existing database on another server. It appears to gather information as expected in most areas (I can look at the alert log through grid control and it is up to date to the nearest 60 seconds as I expect) but today I looked at how full my undo tablespace is and the figures seemed completely wrong. When looking through grid control it showed me that Undo was 20% full. When I looked in the old java console, it showed it was 30% full!
Is there any reason why figures in Grid Control would not be accurate or up to date? I have no error messages and it seems to be gathering data fine.
Is it more likely the old java console is not accurate? (I've always found it accurate in the past I think!).
These are Solaris Sparc servers, Oracle 10.2.0.3 Grid Control monitoring an Oracle 10.2.0.3 database on a remote server via management agent.
Thanks,
Paula

And this morning my old console says 21%, and the new Grid Control says 14%. So they both seem to be gathering the info and putting it out but they have completely different opinions on how much space is used. I think that makes the whole thing fairly useless. Not so glad I spent an age trying to get grid control set up now!!!
Any thoughts much appreciated!!!!
Thanks,
Paula

How to create logical standby database without using Oracle Grid Control

Hi All,
I want to create Logical standby database on 11gr2 on RHEL 5 without using oracle Grid Control.
I already have a primary database as well as physical standby database.
What i want to create a logical standby database as well on the same machine where physical standby database is running.
So anyone of you help me out to do that
Thanks in advance

Hi,
Creating a Logical Standby Database
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm#SBYDB00300
Regards,
Tom

Grid Control and Ora-12557 error

Hello, I'm trying to install the Oracle DataGuard in my work. I have two server with these features:
2 Processors Intel Xeon 2.8 GHz
4 GB Ram
6 SATA hdd 250GB (Raid 5)
for each server. Actually, only one server have the database production, and the another server I have for testing purpose. I must be have a high availability system. I want to build an Oracle RAC system, but I think that I need an external storage (something like SAN, or fibre channel or iSCSI). Well, I assumed that I don't create a Oracle RAC because I do not have the hardware requirements. Then, I thougth use Oracle DataGuard. For that, I have one server in one building and another server in another building like a standby database. If a server fail, then I use the another.
I decided to create Oracle DataGuard configuration. I installed windows 2003 server standard edition in my server for test purpose, and then I installed the Oracle Database 10 g with my database. After I installed the Oracle Grid Control with a new database for repository. Well, when the installation of Oracle Grid Control was completed, I didn´t connect to my database because sqlplus show me an error (Ora-12557). Before I install the Oracle Grid Control I can connect perfectly with my database, but after that I can not connect any time.
Anyone can help me, please????

After formatting (clean server)
1. Install grid control Repository and Management Server
2. Patch it to the latest version (10.2.0.3)
3. Install agent on your other server ,see that you should be able to communicate, check for propert username/password settings.
4. Install your first database , lets say you install it on the same machine with grid
Check for ports/etc and see its in a working order
5. From Grid control ,create your standby on another machine , grid required no interfearance from user once some pre-requisits (you should be able to ping/ftp) on the host.
there are number of possibilites for meeting your requirements, keep refering installation guide where possible.

Grid control switchover issue

Hi,
I have carried out the following
a 10g database install on 2 servers
enabled dataguard between them so I have a primary and a standby database.
I then installed Grid Control onto each server using the opetion to install into an existing database. this worked.
On the standby server opmnctl is shutdown and the database is a PHYSICAL STANDBY.
when I do a dataguard switchover I see the standby database is now the primary. I restart opmnctl and go to the web browser to look at Grid Control.
The issue I have is that Grid Control, even though it is on the standby server, points to the primary server. How can I change this behaviour
When I first started Grid Control I had to perform the following actions
[oracle@griddg bin]$ ./emctl status emkey
Oracle Enterprise Manager 10g Release 3 Grid Control
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Please enter repository password:
The Em Key exists in the Management Repository, but is not configured properly or is corrupted in the file system.
Configure the Em Key by running "emctl config emkey -repos".
[oracle@griddg bin]$ ./emctl config emkey -repos
Oracle Enterprise Manager 10g Release 3 Grid Control
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Please enter repository password:
The Em Key has been configured successfully.
after this gridcontrol was able to start but points to the wrong host.
rgds
alan

hi,
the steps I took are as follows
1 - precreate a database on the primary and standby.
2 - configure the tnsnames and listener files so that the databases can talk to each other
3 - create a standby control file from the primary database.
4 - copy all database files from the primary to the standby
5 - copy the standby controlfile to the standby
6 - start the primary database
7 - start the standby database but only mounted, check database_role from v$database; it should be physical standby
8 - install Grid Control on the primary server with the option to install onto an existing database. Complete this installation.
9 - Install Grid Control onto the standby server with the option to install onto an existing database. Complete the installation and then carry out an 'opmnctl stopall'
10 - all being well Grid Control should now show both hosts and databases.
11 - create a dataguard configuration from within GC
The standby database cannot be discovered correctly in GC and this must be because it is in a mount state, not sure what to do about this. This then meant that I had to carry out a switchover from the command line. I am just testing this now and will post back when complete.
regards
Alan

Grid control mgmt aganet question...

I installed a new 2 node cluster 10.2.0.3 on linux Itanium and I setup the db as a standby database so that we can test our dtata gurad switchover which we are using to facilitate our ASM migration from our production database.
We successfully switched roles and the new cluster came up as a primary. While the database was up and running as the primary database I installed the grid control mgmt aganets and that all went well and I could loging to the grid control mgmt server and administer the clustered database.
I since have dropped the database and have recreated it as a standby which is now in sync from our prod database. The grid control mgmt agents have been stopped since they could not connect whcile the database is running in a syandby role.
We plan top switch roles of the databases and the new cluster will be coming online as our primary over the weekend.
My quesion is? Will I need to reinstall the grid control agents or can I simply just start them up once the database is up and running as primary again? Is there data in the sysman repository that will be missing that will warrant a reinstall of the grid agaents since this database is not going to be the same database that was in existence at the time when the agents had been installed?
Thanks very much.

It is something that works. It will be best for you to give it a go on your own. If you really want do a lot of practice, then pickup the related Step-by-steps documents and start doing it. You cannot start if you spend time contemplating or having a lot of doubt about it.
Oracle has a lot of pages dedicated to VM and Grid Control. I would suggest that you read up on it.
<br>
Oracle Database FAQs
</br>

Database size unavailable in Grid Control

On one of the 10g databases that I monitoring through Grid Control, under space summary, its shows the database size as Unavailable. When I open up db console, it does show the size of the database but not under Grid Control. Please help!
Edited by: zee_dba on Oct 15, 2009 7:34 AM

Agent is up and running. I was getting Metrics "Current Open Cursors Count" error. After increasing the open_cursor parameter, I got rid of that error, restarted the agent, but still the database size is unavailable.
Database Size (GB) Unavailable
Problem Tablespaces 0
Segment Advisor Recommendations 62
Space Violations 1
Dump Area Used (%) 81

Configuration of grid control agent 11g

Hello guys,
I have problem with configuration of Grid control agent 11g. Root cause of the problem is that target machine is in DMZ Zone. So there is lack of ports enabled. Other agents I've been installed works properlly.
The one I am talking is able to upload data, but in case of configration I get error message: "Error occurred while getting information for the specified target. Possible reasons include: the target doesn't exist; connection to the target failed."
Here you are output from emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Agent Version : 11.1.0.1.0
OMS Version : 11.1.0.1.0
Protocol Version : 11.1.0.0.0
Agent Home : /orahome/agent11g
Agent binaries : /orahome/agent11g
Agent Process ID : 3011
Parent Process ID : 2985
Agent URL : https://demodb:1830/emd/main/
Repository URL : https://admin:4900/em/upload
Started at : 2011-02-11 10:23:43
Started by user : oracle
Last Reload : 2011-02-11 10:39:40
Last successful upload : 2011-02-11 17:04:08
Total Megabytes of XML files uploaded so far : 20.98
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 14.21%
Last successful heartbeat to OMS : 2011-02-11 17:13:05
Agent is Running and Ready
emctl status oms -details
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Console Server Host : admin
HTTP Console Port : 7788
HTTPS Console Port : 7799
HTTP Upload Port : 4889
HTTPS Upload Port : 4900
OMS is not configured with SLB or virtual hostname
Agent Upload is locked.
OMS Console is locked.
Active CA ID: 1
Enabled ports:
from admin to demodb -1830
from demodb to admin - 4900, 4889
What else ports neeeds to be enabled? 1521..?
Thanks in advance!
Have a nice day

Thanks Lubiez Jean-Valentin! I think the point is here.
Configuring the Firewall to Allow Incoming Communication From the Management Service
While the Management Agents in your environment must upload data from your managed hosts to the Management Service, the Management Service must also communicate with the Management Agents. As a result, if the Management Agent is protected by a firewall, the Management Service must be able to contact the Management Agent through the firewall on the Management Agent port.
By default, the Enterprise Manager installation procedure assigns port 1830 to the Management Agent. However, if that port is occupied, the installation may assign an alternate port number.
After you determine the port number assigned to the Management Agent, you must then configure the firewall to allow incoming HTTP or HTTPS traffic (depending upon whether or not you have enabled Enterprise Manager Framework Security) on that port.
As I said already port 1830 was enabled. I did it because I saw that agent status - attached also here.
In case anybody know please tell me who to determine the port assigned to the Mangement Agent...

Em grid control 10.2.0.5 add local database problem

Similar Messages

Maybe you are looking for