Agent restart results in loss of management plug-in deployment

A hardware provider provided us 3 management plug-ins for the Grid Control Enterprise Manager (V11g).
The Plug-ins are deployed on one single agent. The agent is located on our OMS. Overall, we've got 20 instances of these plug-ins on the same agent.
Now, we've detected that restarting this agent causes that the deployment of one plug-in has been lost. The effect is that the plug-in instances are not working anymore. They are still existing but without no function (like zombie processes).
We help ourselves with the following workaround:
Deleting all pug-in instances, re-deploy the plug-ins to the agent, recreate all 20 plug-in instances.
This workaround costs a lot of time and is not acceptable in the long run. Fortunately, I was able to write a script for an automatic deletion and creation of the plug-in instances on the agent.

Plug-in deployment results in files installed in the repository to handle the new target type and files laid down on the agent to handle the new target type. Restarting the agent shouldn't be able to remove any of these artifacts.
Can you confirm after the agent is restarted that the plug-in files still remain on the agent? (sysman/admin/metadata/<target_type>.xml is the main one) Are there errors in the agent logs?
How are the target instances discovered? Are they the same ones each time with the same instance properties?

Similar Messages

SQL Server Management Plug-ins deploy error

Hi,
I have a GC 10.2.0.3.0.
I am trying to deploy the MS SQL server plug-in and am getting the following errors.
I have followed the instruction in this document: http://download.oracle.com/docs/cd/B16240_01/doc/apirefs.102/e12776/pisqp.htm
This thread did not help me much, Re: microsoft plug in deployment errors on grid control
At least one error has occurred. Refer to the Deployment Status page for more details.
The Deployment Status page shows ....
Deployment Errors and Warnings
Name microsoft_sqlserver_database Agent tenhrmdb201:3872
Version 3.3.3.1.0
An error occurred while communicating with the agent. It may be down or unreachable.
I have created a local user on the windows box(Agent) and given all the required permissions according to the document.
In the GC for the Agent Preferred Credentials, i have given the Host UserName = SERVER\username and the password.
Please help me find what am i missing here.

I had to add the Windows server's IP to the /etc/hosts file on the OEM server.
That fixed the issue.

Wilyhost Agent could connect to the Enterprise Manager

Hi Gurus,
I'm trying to setup Diagnostic for Solman 7.0. I'd installed Wily Introscope and SDM Agent in Solution Manager. The Agent was configured for this server. The Application Agent in Diagnostic Setup -> Managed system was OK, but when I try to run the Setup Wizard for Self-Monitoring, every steps are in green (OK) but the first was in red with this error:
Step Wilyhost Agent Details
Created destination SM1_DVEBMGS00_server0
Created destination SM1|qfmasr003_SM1_00
Created action SAP GC|SM1_DVEBMGS00_server0 - SAP GC|SM1_DVEBMGS00_server0
Created action SM1 - SM1 AbapSystem
Created action SM1|qfmasr003_SM1_00 - SM1|qfmasr003_SM1_00 AbapInstance
Created 3 action(s).
0 Wilyhost Agent(s) and 0 EP Agent(s) from host qfmasr003 are connected to the EM.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (qfmasr003.xxxxxxxx.com:6000) no Wilyhost Agent was detected from host qfmasr003. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
The file jvm_smdagent.out said this:
LoadBalanceRestricted=no
P4ClassLoad=P4Connection
SAPDBHOST=
SAPINFO=SMD_98_server
SAPMYNAME=qfmasr003_SMD_98
SAPSTARTUP=1
SAPSYSTEM=98
SAPSYSTEMNAME=SMD
application.home=/usr/sap/SMD/exe
file.encoding=UTF-8
file.encoding.pkg=sun.io
file.separator=/
j2ee.dbhost=
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path=/usr/sap/SMD/exe/jstartup.jar:/usr/sap/SMD/exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.00.15.20080806065909/launcher/smdagentlauncher.jar
java.class.version=48.0
java.endorsed.dirs=/j2sdk1.4.2_17/jre/lib/endorsed
java.ext.dirs=/j2sdk1.4.2_17/jre/lib/ext
java.home=/j2sdk1.4.2_17/jre
java.io.tmpdir=/tmp
java.library.path=/j2sdk1.4.2_17/jre/lib/i386/server:/j2sdk1.4.2_17/jre/lib/i386:/j2sdk1.4.2_17/jre/../lib/i386:/usr/sap/SMD/exe:/tmp/sapinst_exe.18845.1222346568:/usr/sap/SMD/exe:/usr/sap/SMD/exe:/usr/sap/SMD/exe
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=1.4.2_17-b06
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.4
java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
java.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
java.version=1.4.2_17
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=1.4.2_17-b06
jstartup.debuggable=yes
jstartup.mode=JCONTROL
jstartup.ownHardwareId=G1082288837
jstartup.ownProcessId=1666
jstartup.whoami=server
line.separator=
memory.manager=128M
os.arch=i386
os.name=Linux
os.version=2.6.9-5.ELsmp
path.separator=:
sun.arch.data.model=32
sun.boot.class.path=/j2sdk1.4.2_17/jre/lib/rt.jar:/j2sdk1.4.2_17/jre/lib/i18n.jar:/j2sdk1.4.2_17/jre/lib/sunrsasign.jar:/j2sdk1.4.2_17/jre/lib/jsse.jar:/j2sdk1.4.2_17/jre/lib/jce.jar:/j2sdk1.4.2_17/jre/lib/charsets.jar:/j2sdk1.4.2_17/jre/classes
sun.boot.library.path=/j2sdk1.4.2_17/jre/lib/i386
sun.cpu.endian=little
sun.cpu.isalist=
sun.io.unicode.encoding=UnicodeLittle
sun.java2d.fontpath=
sun.os.patch.level=unknown
sys.global.dir=/usr/sap/SMD/SYS/global
user.country=US
user.dir=/usr/sap/SMD/J98/SMDAgent
user.home=/home/smdadm
user.language=en
user.name=smdadm
user.timezone=
Running SMD Agent ...
[Runtime] START
==> Loading application com.sap.smd.agent.application.runtime : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.global.configuration : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.connectors : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.wily : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.filesystem : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.tracing : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.remotesetup : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.wilyhost : 7.0015.20080806065229.0000
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Introscope Agent Release 7.2.0.0 (Build 540138)
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Using Java VM version "Java HotSpot(TM) Server VM 1.4.2_17" from Sun Microsystems Inc.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Trying to load file from ./applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Loaded file from ./applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] The agent extension property "introscope.agent.extensions.directory" is not set. No extensions will be loaded.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Introscope Agent startup complete.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent J98" based on the value of the System Property "com.wily.introscope.agent.agentName".
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent J98
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
10/14/08 01:13:57 PM ARST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at qfmasr003.quickfood.com.ar:6000,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "qfmasr003", Process = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
10/14/08 01:13:57 PM ARST [INFO] [IntroscopeAgent] Remote Agent Configuration Service is enabled
==> Loading application com.sap.smd.agent.application.logviewer : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.flightrecorderdumpscan : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.telnet : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.database : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.datacollector : 7.0015.20080806065229.0000
Initialization done.
[ms://qfmasr003.xxxxxxxxxxxxxxxxxx:8101/P4] Agent ready.
==> Loading application com.sap.smd.agent.application.remoteos : 7.0015.20080806065229.0000
only Initial Configuration files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only file configuration information will be considered
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
only Abap configuration will be considered
only Abap configuration will be considered
only file version information will be considered
only End2End log files will be considered
only software change logs will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
10/15/08 01:16:17 PM ARST [WARN] [IntroscopeAgent.IsengardServerConnectionManager] The Introscope Agent is sending data to the Introscope Enterprise Manager too slowly. Keeping the connection alive.
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only file configuration information will be considered
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
only Abap configuration will be considered
only Abap configuration will be considered
only file version information will be considered
only End2End log files will be considered
only software change logs will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only Initial Configuration files will be considered
This error is the same, when I try to connecto other system for Diagnostics,
Any comments, suggestions, recomendations.... anythings.....
Thanks in advice,
Sergio Mazzeo.

Hi Sergio,
did you already stop and start your SMD agent on OS level ? It is not enough to restart it from the SMD.
kind regards
Davy

Updating a management plug-in

Hi,
I would like to know is there a way to update a deployed management plug-in?
Thanks in advance.

To be more specific, you don't have to undeploy the original version. You can simply deploy the newer (greater version) of the management plug-in to the same agents where the old one has been deployed.
One thing you'll have to be careful for, though, is the instance properties. If they have changed or new ones added in the new version, you'll have to reconfigure the target instances for that target type or they may run into problems.
As a development side note, if this is a plug-in you are developing and you have changed the target metadata at all, you need to make sure that you increment the meta_ver at the top of that file.

Management Plug-ins

Using OEM Grid 10.2.0.3 setup page, I am trying to deploy Management Plug-ins, ibm_db2_database version 3.1.1.0.0 to an management agent locared on the AIX server; and microsoft_sqlserver_database version 3.2.3.1.0 to the Widnows 2003 SP2 Server. I have set the preference for both server and agent on those servers but I the same error on both; "Internal error occurred while undeploying the Management Plug-in entry(ies) of type ECM_UNDEPLOY. Make sure that this Management Plug-in is valid. Consult the OMS log file(s) for more details."
Is there anyway I can install/setup plugin directly to the server without deploying through the OEM Grid setup page?

I had to add the Windows server's IP to the /etc/hosts file on the OEM server.
That fixed the issue.

OEM agent restarts frequently

Hi,
I have an OEM agent monitoring RAC database,agent is getting restarted 2-3 times a day.
Agent:10gR5 with latest PSU
OMS:10gR5 PSU4
OS: Solaris 5.10
Agent log shows below error
emagent.trc
2011-08-23 00:13:53,462 Thread-26796 ERROR scheduler: Collection rac_database:dbname:aq_monitoring_alerts has not finished in 721 minutes (allowed: 720).
Exiting agent.
2011-08-23 00:13:53,711 Thread-26796 ERROR : Signalled to Exit with status 3. Hung collection
2011-08-23 00:13:53,748 Thread-1 ERROR main: EMAgent abnormal terminating
2011-08-23 00:14:10,558 Thread-1 WARN upload: Merging leftover data file named rawdata3.dat
2011-08-23 00:14:10,687 Thread-1 WARN upload: Merging leftover data file named rawdata4.dat
2011-08-23 00:14:10,810 Thread-1 WARN upload: Merging leftover data file named rawdata5.dat
2011-08-23 00:14:10,945 Thread-1 WARN upload: Merging leftover data file named rawdata6.dat
2011-08-23 00:14:11,136 Thread-1 WARN command: Job Subsystem Timeout set at 600 seconds
2011-08-23 00:14:11,350 Thread-1 WARN upload: Upload manager has no Failure script: disabled
emagent.nohup
(pid=17814): emagent now exiting abnormally - exiting abnormally Consult '.trc' and '.log' files.
----- Tue Aug 23 17:04:14 2011::Checking status of EMAgent : 17814 -----
----- Tue Aug 23 17:04:24 2011::Checking status of EMAgent : 17814 -----
----- Tue Aug 23 17:04:24 2011::EMAgent exited at Tue Aug 23 17:04:24 2011 with return value 3. -----
----- Tue Aug 23 17:04:24 2011::EMAgent has requested a restart. Will be restarted. -----
----- Tue Aug 23 17:04:25 2011::Restarting EMAgent. -----
----- Tue Aug 23 17:04:32 2011::Agent Launched with PID 22499 at time Tue Aug 23 17:04:32 2011 -----
----- Tue Aug 23 17:04:32 2011::Execing EMAgent process is taking longer than expected 120 secs. -----
----- Tue Aug 23 17:04:32 2011::Time elapsed between Launch of Watchdog process and execing EMAgent is 149662 secs -----
(pid=22499): starting emagent version 10.2.0.5.0
(pid=22499): emagent started successfully
Thanks in advance....

On June the 8'th last year you had the same issue with a 10.2.0.4 agent. See EM agent restarts with error host_storage has not finished in 721 minutes (
Did you ever solve that one?
I think it is best to create a Service Request.
Eric

I'm trying to install iOS 5.0 but getting message that my computer does not have sufficient space to backup my iPad; continuing will result in loss of all media on iPad. I was going to install iCloud but it seems that you have to have iOS 5.0, help?

i'm trying to install iOS 5.0 but getting message that my computer does not have enough space to backup my iPad and continuing will result in loss of all media on iPad. an option seemed to be backing up on iCloud, but i think you have to have iOS 5.0 to install iCloud.
how do i install iOS 5.0 without losing anything on my iPad?

If you really do not have enough space on your HDD for a backup of your iPad, you do not have enough space at all. Free up at least 15% of your HDD, in any case more than 0.8GB for the iPad update.
Make backups on an external disk.
After freeing up enough space, try again.

Use of SQL fetchlet to create a custom management plug-in

Hi,
I would appreciate if you anyone could help me out on this:
I need to fetch some data from EMF tables and create a custom Management plug-in in OEM so that it can be monitored from OEM itself. For getting the data from database table i am using SQL fetchlet coz it provides the facility to use SQL statement in it. Following is the code i have developed in target-type.xml file.
<TargetMetadata META_VER="1.0" TYPE="emf_filer">
<Display>
<Label NLSID="emf_filer">Error Management Filer</Label>
</Display>
<Metric NAME="emf_filer" TYPE="TABLE">
<Display>
<Label NLSID="emf_filer_resp">Response</Label>
</Display>
<TableDescriptor>

<ColumnDescriptor NAME="Status" TYPE="NUMBER" >
<Display>
<Label NLSID="emf_filer_resp_status">Status</Label>
</Display>
</ColumnDescriptor>
<ColumnDescriptor NAME="PROGRAM_NAME" TYPE="STRING" >
<Display>
<Label NLSID="PROGRAM_NAME">Program Name</Label>
</Display>
</ColumnDescriptor>
<ColumnDescriptor NAME="PROGRAM_TYPE" TYPE="STRING" >
<Display>
<Label NLSID="PROGRAM_TYPE">Program Type</Label>
</Display>
</ColumnDescriptor>
<ColumnDescriptor NAME="RICEW_ID" TYPE="STRING" >
<Display>
<Label NLSID="RICEW_ID">Rice Id</Label>
</Display>
</ColumnDescriptor>
<ColumnDescriptor NAME="Request_id" TYPE="NUMBER" IS_KEY="TRUE" >
<Display>
<Label NLSID="Request_id">Request Id</Label>
</Display>
</ColumnDescriptor>
<ColumnDescriptor NAME="EBIZ_INSTANCE_NAME " TYPE="STRING" >
<Display>
<Label NLSID="EBIZ_INSTANCE_NAME">Instance Name</Label>
</Display>
</ColumnDescriptor>
</TableDescriptor>
<QueryDescriptor FETCHLET_ID="SQL">
<Property NAME="MachineName" SCOPE="INSTANCE">MachineName</Property>
<Property NAME="Port" SCOPE="INSTANCE">Port</Property>
<Property NAME="SID" SCOPE="INSTANCE">SID</Property>
<Property NAME="UserName" SCOPE="UserName">apps</Property>
<Property NAME="password" SCOPE="password">password</Property>
<Property NAME="ServiceName" SCOPE="INSTANCE">ServiceName</Property>
<Property NAME="STATEMENT" SCOPE="INSTANCE">
BEGIN
SELECT PROGRAM_NAME, PROGRAM_TYPE,
RICEW_ID,REQUEST_ID, EBIZ_INSTANCE_NAME FROM XX_EMF_MESSAGE_HEADER WHERE STATUS = 'ERROR' AND RICEW_ID = 'INT-DL019';
END;
</Property>

<Property NAME="NUMROWS" SCOPE="GLOBAL">40
</Property>
</QueryDescriptor>
<ExecutionDescriptor>
<GetTable NAME="emf_filer"/>
<GetView NAME="emf_View" FROM_TABLE="emf_filer">
<Column NAME="PROGRAM_NAME"/>
<Column NAME="PROGRAM_TYPE"/>
<Column NAME="RICEW_ID"/>
<Column NAME="REQUEST_ID"/>
<Column NAME="EBIZ_INSTANCE_NAME"/>
<Filter COLUMN_NAME="REQUEST_ID" OPERATOR="GT">0</Filter>
</GetView>
</ExecutionDescriptor>
<InstanceProperties>
<InstanceProperty NAME="UserName" CREDENTIAL="TRUE" OPTIONAL="FALSE" NEED_REENTER="FALSE" HIDE_ENTRY="FALSE">
<Display>
<Label NLSID="UserName_emf">Username</Label>
</Display>
</InstanceProperty>
<InstanceProperty NAME="password" CREDENTIAL="TRUE" OPTIONAL="FALSE" NEED_REENTER="TRUE">
<Display>
<Label NLSID="password_emf">Password</Label>
</Display>
</InstanceProperty>
<InstanceProperty NAME="MachineName" CREDENTIAL="FALSE" OPTIONAL="FALSE">
<Display>
<Label NLSID="MachineName_emf">Listener Machine Name</Label>
</Display>
</InstanceProperty>
<InstanceProperty NAME="Port" CREDENTIAL="FAL
My doubt here is:
As per Oracle it is importent to use response matrics with status column. How can i accomodate Response matrics with this code. what will be the columns except Status that i need to mention? if i use just one matrics i.e response then what will i use in in FROM clause in ExecutionDescriptor [<GetView NAME="emf_View" FROM_TABLE="emf_filer">]? i wuld appreciate if anyone could clarify my issues.
Thanks for your help.
Regards,
AS

That is what i am trying to ask..as i will b using 2 dfifferent matrics so i will have to use 2 diffrent QueryDescriptors one for Response matric and one for other one. Now following QueryDescriptor will be added in other(Not Response) matric then what should i add in QueryDescriptor in Response matric?
Query Descriptor for matric other than "Reposnse":
QueryDescriptor FETCHLET_ID="SQL">
     <Property NAME="MachineName" SCOPE="INSTANCE">MachineName</Property>
     <Property NAME="Port" SCOPE="INSTANCE">Port</Property>
     <Property NAME="SID" SCOPE="INSTANCE">SID</Property>
     <Property NAME="UserName" SCOPE="UserName">UserName</Property>
     <Property NAME="password" SCOPE="password">password</Property>
     <Property NAME="ServiceName" SCOPE="INSTANCE">ServiceName</Property>
     <Property NAME="STATEMENT" SCOPE="GLOBAL">
          SELECT PROGRAM_NAME,
                         PROGRAM_TYPE,
                         RICEW_ID,REQUEST_ID,
                         EBIZ_INSTANCE_NAME
          FROM XX_EMF_MESSAGE_HEADER WHERE STATUS = 'ERROR' AND RICEW_ID = 'INT-DL019';
          </Property>
</QueryDescriptor>
what should be the QueryDescriptor for Response matric?? Will it be same or different?
Thanks for your help.
Regards,
AS
Edited by: user9959418 on Oct 31, 2008 1:10 PM

Logs for sql server agent restart

Hi,
Can I get log on the sql server agent restart history of week. I mean the sql server agent has been restarted several times in last week I want to know the date and time when the sql server agent restarted in that week. Is it possible to get
the info?
Thanks in advance,
Pavan
Pavan

In addition to Uri's post, here is some more information that might help you:
SQLAGENT.OUT, the log file for SQL Agent. SQL Server Agent can maintain up to 10 Error Logs files. The currently used SQL Server Agent Error Log will be named SQLAGENT.OUT
where is the SQLAGENT.OUT file?
C:\Program Files\Microsoft SQL Server\MSSQL11.SQL2012\MSSQL\Log\
What will be when a new file create?
The old file should get a name like SQLAGENT.X and the new file get the name SQLAGENT.OUT (X is numbers 1-9)
This can help you to get more information on sql agent properties (like the location of the log file, the user that start the service and more):
EXEC msdb..sp_get_sqlagent_properties
[Personal Site] [Blog] [Facebook]

Disable automatic Agent restart

I need to temporarily disable the agent restart when a RAC node is bounced.
Can someone tell me how the agent is configured for automatic restart on an AIX RAC node?

Yeah, I knew about the watchdog.
I'm talking about server restarts though.
I have not specifically configured the em agent (10.2.0.2) to restart when the cluster node restarts; however, it does restart on it's own. This is also the case with the non-RAC em agent installs. I could not locate anything in /etc/init.d for this purpose. I seem to recall reading something about gcstart or something like that, but I could not locate the document.
Thanks.

Where to upload test case results in SAP Solution Manager?

Hi Experts,
I am new to test management module in SAP Solution Manager. I need to know where to upload test case results in sap solution manager.
Please provide screenshots on how to upload test results.
Regards,
Sanjana

Hi Sanjan,
let me provide you some more information.
First of all you create a SAP Solution Manager Project in Transaction SOLAR_PROJECT_ADMIN. I think this should be no problem. After creating the Project, make sure that the tap "Test Cases" is switched on in this project. The tap "Test Cases" is the tap below "Project Standards".
Go to transaction "solar02" and choose your created project. Find the tap "Test Cases" and upload a sample file. Please note that the configuration structure of this project can be configured in solar01 (Business Blueprint). There are many settings you can choose in a project regarding ti your requirements. Try to find them out! :-)
In transaction Test Plan Management (STWB_2) you can choose all relevant test cases you uploaded in your project and generate Test Packages which are mapped to your choosen Testers.
In Transaction stwb_work you will see the testers workbench.
Best regrads
J.Eichner

Does 'save as' in 10.8 overwrite the original or result in loss of the original file?

Is it true that the restored using "Save As" in Mountain Lion results in loss of the original file? I expect "Save As" to result in saving a separate file under whatever name is assigned to it while leaving the original alone. There was a post elsewhere online today to the effect that unless one or another preference is globally set for the Mac using Save As will just result in renaming the file; the original will be lost unless it can be retrieved from Time Machine or elsewhere. What is the truth here? I understand that third-party apps (say, Photoshop) maintain normal "Save" and "Save As" behavior but that using Apple apps or others that employ the OS's saving scheme manifest this behavior. If this is true and not remediable then I'll probably leave the Mac platform after 24 years once my 2006 Mac Pro is left too far behind. This one's a deal breaker for me though the thought of using Windows 8 leaves me cold too.

As someone online noted:
"In Apple's brave new world, there is no "Save" or "Save As". Everything you do is recorded, and you can always go back to previous versions of your work. There is no real destruction. It's just not working the way we want it to work.
Apple shifted the paradigm out from under our feet. I too find myself lost. In software support, this is known as a "problem occurring in the first half of the 'user interface'". For over 50 years, computer users have had to explicitly save their work. You didn't save it, it was lost. We even got into the habit of saving our work every so often in case the computer crashed, and hours of work was lost. The original Mac's big contribution: It reminded us to save our work when we quit the program. Now, there is no more save, and we can't wrap our minds around it."
From what I understand BOTH FILES will be saved with the changes - but what "Save As" should do is allow the copy to be saved with the changes and the original to stand alone. The whole business is a mess and nothing I want to deal with. I don't want the ORIGINAL file autosaved with my changes nor do I want to have to go fishing to figure out which version is the one I started with at that session.

Error -5000 will result in loss of all content?

I'm trying to upgrade my iPad to the iOS5. I get an error -5000 that says if I continue it will result in loss of all content.
How do I get around this?

Back up your iPad first, then upgrade. You can restore all your apps and data after it updates!

Hi, I rented a movie last night. There was a power failure in my area and as a result I didn't manage to finish it. May I know how to resume watching today?

Hi, I rented a movie last night. There was a power failure in my area and as a result I didn't manage to finish it. May I know how to resume watching today?

CHWei,
You may find a solution by reading: Cannot resume a movie rental using...: Apple Support Communities.

SCOM 2012 SP1- Getting Event ID 20070 on some agents and Event ID 200000 on management servers

On a significant number of my 2012 SP1 Agents, I am getting the following Event IDs in my OperationsManager event log:
20070
The OpsMgr Connector connected to XXXXXX.domain.net, but the connection was closed immediately after authentication occurred. The most likely
cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration.
21006
The OpsMgr Connector could not connect to XXXXXX.domain.net:5723. The error code is 10060L(A connection attempt failed because the connected
party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.).
21015
OpsMgr was unable to set up a communications channel to XXXXXX.domain.net. Communication will resume when XXXXXX.domain.net is available and
communication from this computer is allowed.
On my various 2012 SP1 Management Servers, I am getting the following Event IDs in my OperationsManager event logs:
20000
A device which is not part of this management group has attempted to access this Health Service.
Requesting Device Name: servername.domain.com
Here are my settings and what I have tried:
We have agents assigned by AD-integration, and they are receiving their proper assignment
Agents are manually installed with SCCM 2012
“Automatically approve new manually installed agents” is selected
I have rebuilt the Health Service State folder and rebooted the service on the agent server
I have rebuilt the Health Service State folder on my management server and rebooted it to reset all services
On several agent servers that I am experiencing this issue, they are on the same network as their assigned management server, so there is no firewall issue.

Hi,
Here is a KB for your reference.
Troubleshooting gray agent states in System Center Operations Manager
http://support.microsoft.com/kb/2288515
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Agent restart results in loss of management plug-in deployment

Similar Messages

Maybe you are looking for