Dbconsole - emctl agent status - incorrect for 'emctl resetTZ agent'

When I run - emctl resetTZ agent
...Agent is running. Stop the agent and rerun the command.
When I run - emctl stop agent
... Agent is not running.
When I run - emctl status agent
... Agent is Not Running
The agent is not running but "emctl resetTZ agent" thinks the agent is.
How do I fix this issue?
I'm using Oracle 10.2.0.4 on AIX 6.1

These are the processes for ps -ef|grep -i agent. None of them are for Oracle.
srddb01:orasrd 2> ps -ef|grep -i agent
root 176230 172258 0 Oct 11 - 0:00 /opt/freeware/cimom/pegasus/bin/cimssys platform_agent
root 286940 299212 0 Oct 11 - 213:45 /var/opt/tivoli/ep/_jvm/jre/bin/java -Xmx384m -Xminf0.01 -Xmaxf0.4 -Xbootclasspath/a:/var/opt/tivoli/ep/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/rcpbootcp.jar:/var/opt/tivoli/ep/lib/icl.jar:/var/opt/tivoli/ep/lib/jaas2zos.jar:/var/opt/tivoli/ep/lib/jaasmodule.jar:/var/opt/tivoli/ep/lib/lwinative.jar:/var/opt/tivoli/ep/lib/lwirolemap.jar:/var/opt/tivoli/ep/lib/passutils.jar:../../runtime/agent/lib/cas-bootcp.jar -Xverify:none -cp eclipse/launch.jar:eclipse/startup.jar:/var/opt/tivoli/ep/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/launcher.jar com.ibm.lwi.LaunchLWI
orasrd 426000 1028282 1 14:28:09 pts/0 0:00 grep -i agent
root 430290 172258 0 Oct 11 - 4:33 /usr/sbin/rsct/bin/vac8/IBM.CSMAgentRMd
srddb01:orasrd 3> ps -ef|grep -i agent
root 176230 172258 0 Oct 11 - 0:00 /opt/freeware/cimom/pegasus/bin/cimssys platform_agent
root 286940 299212 0 Oct 11 - 213:45 /var/opt/tivoli/ep/_jvm/jre/bin/java -Xmx384m -Xminf0.01 -Xmaxf0.4 -Xbootclasspath/a:/var/opt/tivoli/ep/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/rcpbootcp.jar:/var/opt/tivoli/ep/lib/icl.jar:/var/opt/tivoli/ep/lib/jaas2zos.jar:/var/opt/tivoli/ep/lib/jaasmodule.jar:/var/opt/tivoli/ep/lib/lwinative.jar:/var/opt/tivoli/ep/lib/lwirolemap.jar:/var/opt/tivoli/ep/lib/passutils.jar:../../runtime/agent/lib/cas-bootcp.jar -Xverify:none -cp eclipse/launch.jar:eclipse/startup.jar:/var/opt/tivoli/ep/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/launcher.jar com.ibm.lwi.LaunchLWI
root 430290 172258 0 Oct 11 - 4:33 /usr/sbin/rsct/bin/vac8/IBM.CSMAgentRMd

Similar Messages

PR status incorrect for POs craeted via PUR_ORDER_CREATE_VIA_SD_EVNT functi

We use the ALE process to create Purchase Orders automaticaly from Sales orders.
The standard function module assigned to the Business Object BUS2032 in SWETYPV for ALECREATE is PUR_ORDER_CREATE_VIA_SD_EVNT
SAP creates a PR and then converts it into a PO using this functional module. However, the procurement status does not get updated on the PR and the PR still shows as open.
Is there any standard correction report to update the status on these PRs or any OSS note that addresses this issue?
Thanks in advance for your replies.

Dear Vinay,
Please check the FM which automatically creates the P.O. whether it has any parameter for PR status, if it is there, then make sure you pass the required value if the same is not there and it is a standard FM then raise a SAP message.
Hope this helps!
Thank you,
Reetesh

Host agent status is unknown for database (DB6) hosts in landscape browser

Hi,
Host status is unknown for database (DB6) hosts in landscape browser.
Trusted connection between DAA and host agent is working and host agent status is also green in Agent admin. SMD_DataEnrichment_Registrator is also registered correctly. But Outside discovery is not working for database in LMDB.
Solution manager:7.1 SP10
Host agent version:172 Patch 178.
Any help on this issue will be appreciated.
Regards,
Pragadees

I have noticed in your other posting as well that you want to make a lot of customisations. I would suggest you read more on EM from this link and see what you can achieve.
http://www.oracle.com/pls/db102/portal.portal_db?selected=21

UCCX Agent Status when making a Outbound Call

Hi Need a little Help ! Advice with the Above subject matter.
I have a customer, who is running reports with Historical reporting however the reports do not give a True reflection of Agents status.
i.e. if the Agent makes an outgoing call the Reports show the agent as being not ready.
I would like to know if it is possible to change how this is reported of if it is possible for the agent to add a note when on a call which would be reflected in the Historical reports.
Can we change the state it shows when an agent is on an outbound call to show "Outbound Call" instead of "Not Ready" as it currently shows ?
Cheers
Charles

Hi Charles
We have raised the same problem towards Cisco a long time ago. The fact that an agent talking is reported as "Not ready", instead of ex. "Talking Out" is not only a problem in HR, but also in some steps of scripting, since the agent is infact on the system and is anything but "Not ready".
Ex. you could check to se if any agent are logged in to CSQ, before selecting resource. If agents are logged in, you could check to see if number of agent logged in = number of agents not ready. If this is true, then no agents are available to answer call and another CSQ could be selected.
But now since an agent talking is reported as "Not ready" because he's talking, the check for agents logged in = agents not reayd might be true, causing script no to work as intended.
So for many reasons an agent talking should be "talking" and not "Not ready". I haven't heard about any workarounds on this agent state, but I do know that Cisco has been informed on this isseu and did recognise that it would make sense to implement but I don't know when this could happen. If not in verison 8.5, then perhaps in ver. 9.
You might be able to pull something from the DB to show correct agent state, but thats not "out of the box"
Regards
Henrik

Doubt about emctl resetTZ agent

Hi,
I just have run this command:
emctl resetTZ agentI had to run it because a customer changed the computer's time zone (windows server 2008 R2 64bits) where weblogic 10.3.4 and forms 11.1.1.4 are installed and is unable to start the EMAGENT process. After i run the command i got this message:
C:\u01\app\oracle\product\Middleware\11.1.1.4\asinst_1\EMAGENT\emagent_asinst_1\bin>emctl resetTZ agent
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Updating C:\u01\app\oracle\product\Middleware\11.1.1.4\asinst_1\EMAGENT\emagent_asinst_1/sysman/config/emd.properties...
Successfully updated C:\u01\app\oracle\product\Middleware\11.1.1.4\asinst_1\EMAGENT\emagent_asinst_1/sysman/config/emd.properties.
Login as the em repository user and run the script:
exec mgmt_target.set_agent_tzrgn('forms11gR2:5155','America/Bogota')
and commit the changes
This can be done for example by logging into sqlplus and doing
SQL> exec mgmt_target.set_agent_tzrgn('forms11gR2:5155','America/Bogota')
SQL> commit
C:\u01\app\oracle\product\Middleware\11.1.1.4\asinst_1\EMAGENT\emagent_asinst_1\bin>I'm a little confused, should i execute the above script ?? i mean i do not have a em repository user.
Also now i am able to start the EMAGENT process without run the above script :)
Any idea or recommendation ?? :)
Regards
Carlos

if you dont have an em repository use then don't run it
else execute the script
end if
there is no need to run the script at the user level as it is once set will remain for all the users.
you can run the sql> script for the same at any level.

Emctl agent status command not working

Every time I issue the command "emctl agent status", I get the following message:
EM Configuration issue. /u01/app/oracle/product/OSE_10.2.0.1.0/itt.ppd.ppd-ds.com_HSI1t not found
I've tried various environments. How can I determine the agent status?
Baffling product :)
Thanks
John

C:\>emctl status agent
Oracle Enterprise Manager 10g Database Control Release 10.1.0.2.0
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
Agent Version     : 10.1.0.2.0
OMS Version       : 10.1.0.2.0
Protocol Version : 10.1.0.2.0
Agent Home        : D:\oracle\product\10.1.0\Db_1\ALwarid-Taj.fakhruddin.local_t
aj
Agent binaries    : D:\oracle\product\10.1.0\Db_1
Agent Process ID : 2992
Agent Process ID : 2992
Agent URL         : http://ALwarid-Taj.fakhruddin.local:1832/emd/main
Started at        : 2006-10-08 08:46:10
Started by user   : SYSTEM
Last Reload       : 2006-10-08 08:46:10
Last successful upload                       : 2006-10-08 10:33:28
Total Megabytes of XML files uploaded so far :     0.06
Number of XML files pending upload           :        0
Size of XML files pending upload(MB)         :     0.00
Available disk space on upload filesystem    :    38.19%
Agent is Running and Ready

I have the following errors executing ./emctl secure status agent

[oracle@SVDBGRICONTROL bin]$ ./emctl secure status agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Checking the security status of the Agent at location set in /u01/app/oracle/product/10.2.0/agent10g/sysman/config/emd.properties... Done.
Agent is secure at HTTPS Port 3872.
Checking the security status of the OMS at http://SVDBGRICONTROL:4889/em/upload/... Done.
OMS is running but has not been secured. No HTTPS Port available.

this is my emoms.trc please any solution.......
2006-08-21 02:17:31 Thread-3086993088 INFO TargetManager: save to targets.xml success
2006-08-21 02:17:31 Thread-3076520880 WARN http: snmehl_connect: connect failed to (10.3.6.222:1159): Connection refused (error = 111)
2006-08-21 02:17:31 Thread-3076520880 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://10.3.6.222:1159/em/upload: retStatus=-32
2006-08-21 02:17:31 Thread-3076520880 WARN http: snmehl_connect: connect failed to (10.3.6.222:1159): Connection refused (error = 111)
2006-08-21 02:17:31 Thread-3076520880 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://10.3.6.222:1159/em/upload: retStatus=-32
2006-08-21 02:17:31 Thread-125782960 ERROR upload: Error in uploadXMLFiles. Trying again in 60.00 seconds or earlier.
2006-08-21 02:17:31 Thread-125782960 ERROR upload: Exceeded max. amount of upload data: 2650 files, 128.086041 MB Data. 18.53% of disk used. Disabling collections.
2006-08-21 02:17:31 Thread-125782960 WARN collector: Disable collector
2006-08-21 02:17:31 Thread-125782960 ERROR collector: Collector state files cleaned, severity will be resent
2006-08-21 02:17:36 Thread-125782960 ERROR upload: Error in uploadXMLFiles. Trying again in 72.00 seconds or earlier.
2006-08-21 02:17:37 Thread-69258160 WARN http: snmehl_connect: connect failed to (10.3.6.222:1159): Connection refused (error = 111)
2006-08-21 02:17:37 Thread-69258160 ERROR command: nmejcn: failed http connection to https://10.3.6.222:1159/em/upload: retStatus=-32
2006-08-21 02:17:53 Thread-69258160 WARN http: snmehl_connect: connect failed to (10.3.6.222:1159): Connection refused (error = 111)
2006-08-21 02:17:53 Thread-69258160 ERROR command: nmejcn: failed http connection to https://10.3.6.222:1159/em/upload: retStatus=-32
2006-08-21 02:18:01 Thread-125782960 WARN http: snmehl_connect: connect failed to (10.3.6.222:1159): Connection refused (error = 111)
2006-08-21 02:18:01 Thread-125782960 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://10.3.6.222:1159/em/upload: retStatus=-32
2006-08-21 02:18:01 Thread-125782960 WARN http: snmehl_connect: connect failed to (10.3.6.222:1159): Connection refused (error = 111)
2006-08-21 02:18:01 Thread-125782960 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://10.3.6.222:1159/em/upload: retStatus=-32
2006-08-21 02:18:09 Thread-36989872 WARN http: -1,7: nmehl_httpListener: signaled to exit from emctl

Essbase Analytics for HFM- Data Update Agent Status

Hi,
In Essbase Analytics for HFM, Data Update Agent status is showing 'Not Active', so as 'Analytic Link Data' status.
The Start/Stop option for the same is disabled. Other connectivity statuses in Bridge are all 'Available'.
What needs to be done to make Data Update status 'Active'.

Hi HP,
The Essbase Analytics Link and HFM needs to be registered with the same Shared Services. Hope you are doing the same.
Thanks & Regards
Sandy

Agent Status Reports OMS Version : (unknown)

I upgraded our 11g OEM installation to 12.1.0.1 and just completed patching to 12.1.0.3. Some of the 11g agents were on platforms not supported by 12.1.0.1 (part of the motivation fro the 12.1.0.3 upgrade, now complete).
Following the instructions in Chapter 7, Installing Oracle Management Agent in the Oracle Enterprise Manager Cloud Control Basic Installation Guide 12c Release 3 (12.1.0.3) I was able to get the agent installed and started on one of the servers I was not able to upgrade during the upgrade process. The new agent is up and running but reports OMS Version : (unknown) -
cmspweb:app/agent12g/agent_inst/bin->./emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.
Agent Version     : 12.1.0.3.0
OMS Version       : (unknown)
Protocol Version : 12.1.0.1.0
Agent Home        : /usr/local/oracle/app/agent12g/agent_inst
Agent Binaries    : /usr/local/oracle/app/agent12g/core/12.1.0.3.0
Agent Process ID : 3821
Parent Process ID : 3767
Agent URL         : https://garmin.ucdavis.edu:3872/emd/main/
Repository URL    : https://oracle-emrep1.ucdavis.edu:4904/empbs/upload
Started at        : 2013-10-08 11:56:26
Started by user   : oracle
Last Reload       : (none)
Last successful upload                       : (none)
Last attempted upload                        : (none)
Total Megabytes of XML files uploaded so far : 0
Number of XML files pending upload           : 0
Size of XML files pending upload(MB)         : 0
Available disk space on upload filesystem    : 69.43%
Collection Status                            : Collections enabled
Heartbeat Status                             : OMS is unreachable [bad response]
Last attempted heartbeat to OMS              : 2013-10-08 14:30:13
Last successful heartbeat to OMS             : (none)
Next scheduled heartbeat to OMS              : 2013-10-08 14:30:43
Agent is Running and Ready
and the upload fails with the error EMD upload error:full upload has failed: uploadXMLFiles skipped :: OMS version not checked yet. If this issue persists check trace files for ping to OMS related errors. (OMS_DOWN) which makes sense. Searching the web I found a number of suggestions including securing the agent, which I was able to do and resynching the agent from the console which I am *not* able to do as the agent and targets are not showing in the console.
The targets.xml file on the agent host has one line -
<Targets AGENT_TOKEN="CB22F0CA441C8CDECF3CA3ABA0D8C02C9AACFF98A41D653CFB2F41B7BC41EE0D"/>
and I realize that is not at all a complete file. In the gcagent.log file I see ping errors -
2013-10-08 14:29:43,596 [319:8C08BF97] INFO - attempting initial heartbeat
2013-10-08 14:29:43,805 [319:8C08BF97] WARN - improper ping interval (EM_PING_NOTIF_RESPONSE: ERROR- Failed to update Target type Metadata)
2013-10-08 14:29:43,810 [319:8C08BF97] WARN - Ping protocol error
o.s.gcagent.ping.PingProtocolException [OMS sent an invalid response: "ERROR- Failed to update Target type Metadata"]
The firewall is open and the agent is using the correct port and I am stumped. If anyone has any suggestions I would certainly appreciate them.
Thank you.
Bill Wagman

Is this a newly installed agent?
Did it work before? What has changed since it last worked?
Anything in the emagent.trc file?
$emctl upload
EMD upload error: uploadXMLFiles skipped :: OMS
version not checked yet..
this is emctl status agent[dev01/AixAgentOracleHome/agent10g]$emctl status agent
Oracle Enterprise Manager 10g Database Control Release 10.1.0.4
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
Agent Version : 10.1.0.4.0
OMS Version : UnknownThe agent does not connect successfully with the OMS, no version there.

No log for am policy agent for iis6

Hello!
Im trying to get Policy Agent for IIS to run on my Win Srv 2003 with IIS6 and Sharepoint Services.
I am running the OpenSSO version of Access Manager.
I have installed the agent and done the initial cofiguration.
When i try to browse the resource i get a login prompt (IIS Basic Auth)and cannot login followed by "Not Authorized 401.3"
I should get redirected to the AM Login page, shouldn't I?
I tried to look for answers in the log file but the /debug/<id> directory i empty.
Anyone know what to do?
The amAgent.properties file:
# $Id: AMAgent.properties,v 1.103 2005/09/19 22:08:34 madan Exp $
# The syntax of this file is that of a standard Java properties file,
# see the documentation for the java.util.Properties.load method for a
# complete description. (CAVEAT: The SDK in the parser does not currently
# support any backslash escapes except for wrapping long lines.)
# All property names in this file are case-sensitive.
# NOTE: The value of a property that is specified multiple times is not
# defined.
# WARNING: The contents of this file are classified as an UNSTABLE
# interface by Sun Microsystems, Inc. As such, they are subject to
# significant, incompatible changes in any future release of the
# software.
# The name of the cookie passed between the Access Manager
# and the SDK.
# WARNING: Changing this property without making the corresponding change
# to the Access Manager will disable the SDK.
com.sun.am.cookie.name = iPlanetDirectoryPro
# The URL for the Access Manager Naming service.
com.sun.am.naming.url = http://login.lta.mil.se:8080/opensso/namingservice
# The URL of the login page on the Access Manager.
com.sun.am.policy.am.login.url = http://login.lta.mil.se:8080/opensso/UI/Login
# Name of the file to use for logging messages.
com.sun.am.policy.agents.config.local.log.file = C:/Sun/Access_Manager/Agents/2.2/debug/Identifier_1414639615/amAgent
# This property is used for Log Rotation. The value of the property specifies
# whether the agent deployed on the server supports the feature of not. If set
# to false all log messages are written to the same file.
com.sun.am.policy.agents.config.local.log.rotate = true
# Name of the Access Manager log file to use for logging messages to
# Access Manager.
# Just the name of the file is needed. The directory of the file
# is determined by settings configured on the Access Manager.
com.sun.am.policy.agents.config.remote.log = amAuthLog.sharepoint.lta.mil.se.80
# Set the logging level for the specified logging categories.
# The format of the values is
# <ModuleName>[:<Level>][,<ModuleName>[:<Level>]]*
# The currently used module names are: AuthService, NamingService,
# PolicyService, SessionService, PolicyEngine, ServiceEngine,
# Notification, PolicyAgent, RemoteLog and all.
# The all module can be used to set the logging level for all currently
# none logging modules. This will also establish the default level for
# all subsequently created modules.
# The meaning of the 'Level' value is described below:
# 0 Disable logging from specified module*
# 1 Log error messages
# 2 Log warning and error messages
# 3 Log info, warning, and error messages
# 4 Log debug, info, warning, and error messages
# 5 Like level 4, but with even more debugging messages
# 128 log url access to log file on AM server.
# 256 log url access to log file on local machine.
# If level is omitted, then the logging module will be created with
# the default logging level, which is the logging level associated with
# the 'all' module.
# for level of 128 and 256, you must also specify a logAccessType.
# *Even if the level is set to zero, some messages may be produced for
# a module if they are logged with the special level value of 'always'.
com.sun.am.log.level = 5
# The org, username and password for Agent to login to AM.
com.sun.am.policy.am.username = UrlAccessAgent
com.sun.am.policy.am.password = PN4rEZ1uhx1404ivWY6HPQ==
# Name of the directory containing the certificate databases for SSL.
com.sun.am.sslcert.dir = C:/Sun/Access_Manager/Agents/2.2/iis6/cert
# Set this property if the certificate databases in the directory specified
# by the previous property have a prefix.
com.sun.am.certdb.prefix =
# Should agent trust all server certificates when Access Manager
# is running SSL?
# Possible values are true or false.
com.sun.am.trust_server_certs = true
# Should the policy SDK use the Access Manager notification
# mechanism to maintain the consistency of its internal cache? If the value
# is false, then a polling mechanism is used to maintain cache consistency.
# Possible values are true or false.
com.sun.am.notification.enable = true
# URL to which notification messages should be sent if notification is
# enabled, see previous property.
com.sun.am.notification.url = http://sharepoint.lta.mil.se:80/amagent/UpdateAgentCacheServlet?shortcircuit=false
# This property determines whether URL string case sensitivity is
# obeyed during policy evaluation
com.sun.am.policy.am.url_comparison.case_ignore = true
# This property determines the amount of time (in minutes) an entry
# remains valid after it has been added to the cache. The default
# value for this property is 3 minutes.
com.sun.am.policy.am.polling.interval=3
# This property allows the user to configure the User Id parameter passed
# by the session information from the access manager. The value of User
# Id will be used by the agent to set the value of REMOTE_USER server
# variable. By default this parameter is set to "UserToken"
com.sun.am.policy.am.userid.param=UserToken
# Profile attributes fetch mode
# String attribute mode to specify if additional user profile attributes should
# be introduced into the request. Possible values are:
# NONE - no additional user profile attributes will be introduced.
# HTTP_HEADER - additional user profile attributes will be introduced into
# HTTP header.
# HTTP_COOKIE - additional user profile attributes will be introduced through
# cookies.
# If not within these values, it will be considered as NONE.
com.sun.am.policy.agents.config.profile.attribute.fetch.mode=NONE
# The user profile attributes to be added to the HTTP header. The
# specification is of the format ldap_attribute_name|http_header_name[,...].
# ldap_attribute_name is the attribute in data store to be fetched and
# http_header_name is the name of the header to which the value needs
# to be assigned.
# NOTE: In most cases, in a destination application where a "http_header_name"
# shows up as a request header, it will be prefixed by HTTP_, and all
# lower case letters will become upper case, and any - will become _;
# For example, "common-name" would become "HTTP_COMMON_NAME"
com.sun.am.policy.agents.config.profile.attribute.map=cn|common-name,ou|organiz ational-unit,o|organization,mail|email,employeenumber|employee-number,c|country
# Session attributes mode
# String attribute mode to specify if additional user session attributes should
# be introduced into the request. Possible values are:
# NONE - no additional user session attributes will be introduced.
# HTTP_HEADER - additional user session attributes will be introduced into HTTP header.
# HTTP_COOKIE - additional user session attributes will be introduced through cookies.
# If not within these values, it will be considered as NONE.
com.sun.am.policy.agents.config.session.attribute.fetch.mode=NONE
# The session attributes to be added to the HTTP header. The specification is
# of the format session_attribute_name|http_header_name[,...].
# session_attribute_name is the attribute in session to be fetched and
# http_header_name is the name of the header to which the value needs to be
# assigned.
# NOTE: In most cases, in a destination application where a "http_header_name"
# shows up as a request header, it will be prefixed by HTTP_, and all
# lower case letters will become upper case, and any - will become _;
# For example, "common-name" would become "HTTP_COMMON_NAME"
com.sun.am.policy.agents.config.session.attribute.map=
# Response Attribute Fetch Mode
# String attribute mode to specify if additional user response attributes should
# be introduced into the request. Possible values are:
# NONE - no additional user response attributes will be introduced.
# HTTP_HEADER - additional user response attributes will be introduced into
# HTTP header.
# HTTP_COOKIE - additional user response attributes will be introduced through
# cookies.
# If not within these values, it will be considered as NONE.
com.sun.am.policy.agents.config.response.attribute.fetch.mode=NONE
# The response attributes to be added to the HTTP header. The specification is
# of the format response_attribute_name|http_header_name[,...].
# response_attribute_name is the attribute in policy response to be fetched and
# http_header_name is the name of the header to which the value needs to be
# assigned.
# NOTE: In most cases, in a destination application where a "http_header_name"
# shows up as a request header, it will be prefixed by HTTP_, and all
# lower case letters will become upper case, and any - will become _;
# For example, "common-name" would become "HTTP_COMMON_NAME"
com.sun.am.policy.agents.config.response.attribute.map=
# The cookie name used in iAS for sticky load balancing
com.sun.am.policy.am.lb.cookie.name = GX_jst
# indicate where a load balancer is used for Access Manager
# services.
# true | false
com.sun.am.load_balancer.enable = false
####Agent Configuration####
# this is for product versioning, please do not modify it
com.sun.am.policy.agents.config.version=2.2
# Set the url access logging level. the choices are
# LOG_NONE - do not log user access to url
# LOG_DENY - log url access that was denied.
# LOG_ALLOW - log url access that was allowed.
# LOG_BOTH - log url access that was allowed or denied.
com.sun.am.policy.agents.config.audit.accesstype = LOG_BOTH
# Agent prefix
com.sun.am.policy.agents.config.agenturi.prefix = http://sharepoint.lta.mil.se:80/amagent
# Locale setting.
com.sun.am.policy.agents.config.locale = en_US
# The unique identifier for this agent instance.
com.sun.am.policy.agents.config.instance.name = unused
# Do SSO only
# Boolean attribute to indicate whether the agent will just enforce user
# authentication (SSO) without enforcing policies (authorization)
com.sun.am.policy.agents.config.do_sso_only = true
# The URL of the access denied page. If no value is specified, then
# the agent will return an HTTP status of 403 (Forbidden).
com.sun.am.policy.agents.config.accessdenied.url =
# This property indicates if FQDN checking is enabled or not.
com.sun.am.policy.agents.config.fqdn.check.enable = true
# Default FQDN is the fully qualified hostname that the users should use
# in order to access resources on this web server instance. This is a
# required configuration value without which the Web server may not
# startup correctly.
# The primary purpose of specifying this property is to ensure that if
# the users try to access protected resources on this web server
# instance without specifying the FQDN in the browser URL, the Agent
# can take corrective action and redirect the user to the URL that
# contains the correct FQDN.
# This property is set during the agent installation and need not be
# modified unless absolutely necessary to accommodate deployment
# requirements.
# WARNING: Invalid value for this property can result in the Web Server
# becoming unusable or the resources becoming inaccessible.
# See also: com.sun.am.policy.agents.config.fqdn.check.enable,
# com.sun.am.policy.agents.config.fqdn.map
com.sun.am.policy.agents.config.fqdn.default = sharepoint.lta.mil.se
# The FQDN Map is a simple map that enables the Agent to take corrective
# action in the case where the users may have typed in an incorrect URL
# such as by specifying partial hostname or using an IP address to
# access protected resources. It redirects the browser to the URL
# with fully qualified domain name so that cookies related to the domain
# are received by the agents.
# The format for this property is:
# com.sun.am.policy.agents.config.fqdn.map = [invalid_hostname|valid_hostname][,...]
# This property can also be used so that the agents use the name specified
# in this map instead of the web server's actual name. This can be
# accomplished by doing the following.
# Say you want your server to be addressed as xyz.hostname.com whereas the
# actual name of the server is abc.hostname.com. The browsers only knows
# xyz.hostname.com and you have specified polices using xyz.hostname.com at
# the Access Manager policy console, in this file set the mapping as
# com.sun.am.policy.agents.fqdn.map = valid|xyz.hostname.com
# Another example is if you have multiple virtual servers say rst.hostname.com,
# uvw.hostname.com and xyz.hostname.com pointing to the same actual server
# abc.hostname.com and each of the virtual servers have their own policies
# defined, then the fqdnMap should be defined as follows:
# com.sun.am.policy.agents.fqdn.map = valid1|rst.hostname.com,valid2|uvw.hostname.com,valid3|xyz.hostname.com
# WARNING: Invalid value for this property can result in the Web Server
# becoming unusable or the resources becoming inaccessible.
com.sun.am.policy.agents.config.fqdn.map =
# Cookie Reset
# This property must be set to true, if this agent needs to
# reset cookies in the response before redirecting to
# Access Manager for Authentication.
# By default this is set to false.
# Example : com.sun.am.policy.agents.config.cookie.reset.enable=true
com.sun.am.policy.agents.config.cookie.reset.enable=false
# This property gives the comma separated list of Cookies, that
# need to be included in the Redirect Response to Access Manager.
# This property is used only if the Cookie Reset feature is enabled.
# The Cookie details need to be specified in the following Format
# name[=value][;Domain=value]
# If "Domain" is not specified, then the default agent domain is
# used to set the Cookie.
# Example : com.sun.am.policy.agents.config.cookie.reset.list=LtpaToken,
# token=value;Domain=subdomain.domain.com
com.sun.am.policy.agents.config.cookie.reset.list=
# This property gives the space separated list of domains in
# which cookies have to be set in a CDSSO scenario. This property
# is used only if CDSSO is enabled.
# If this property is left blank then the fully qualified cookie
# domain for the agent server will be used for setting the cookie
# domain. In such case it is a host cookie instead of a domain cookie.
# Example : com.sun.am.policy.agents.config.cookie.domain.list=.sun.com .iplanet.com
com.sun.am.policy.agents.config.cookie.domain.list=
# user id returned if accessing global allow page and not authenticated
com.sun.am.policy.agents.config.anonymous_user=anonymous
# Enable/Disable REMOTE_USER processing for anonymous users
# true | false
com.sun.am.policy.agents.config.anonymous_user.enable=false
# Not enforced list is the list of URLs for which no authentication is
# required. Wildcards can be used to define a pattern of URLs.
# The URLs specified may not contain any query parameters.
# Each service have their own not enforced list. The service name is suffixed
# after "# com.sun.am.policy.agents.notenforcedList." to specify a list
# for a particular service. SPACE is the separator between the URL.
com.sun.am.policy.agents.config.notenforced_list = SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/UI/* SERVER_PROTO://SERVER_HOST:SERVER_PORTCONSOLE_DEPLOY_URI/* SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/login_images/* SERVER_PROTO://SERVER_HOST:SERVER_PORT/docs* SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/namingservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/sessionservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/loggingservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/profileservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/policyservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/config* SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/js/* SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/css/* SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/authservice SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/SAMLAwareServlet SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/SAMLSOAPReceiver SERVER_PROTO://SERVER_HOST:SERVER_PORTSERVER_DEPLOY_URI/SAMLPOSTProfileServlet
# Boolean attribute to indicate whether the above list is a not enforced list
# or an enforced list; When the value is true, the list means enforced list,
# or in other words, the whole web site is open/accessible without
# authentication except for those URLs in the list.
com.sun.am.policy.agents.config.notenforced_list.invert = false
# Not enforced client IP address list is a list of client IP addresses.
# No authentication and authorization are required for the requests coming
# from these client IP addresses. The IP address must be in the form of
# eg: 192.168.12.2 1.1.1.1
com.sun.am.policy.agents.config.notenforced_client_ip_list =
# Enable POST data preservation; By default it is set to false
com.sun.am.policy.agents.config.postdata.preserve.enable = false
# POST data preservation : POST cache entry lifetime in minutes,
# After the specified interval, the entry will be dropped
com.sun.am.policy.agents.config.postcache.entry.lifetime = 10
# Cross-Domain Single Sign On URL
# Is CDSSO enabled.
com.sun.am.policy.agents.config.cdsso.enable=false
# This is the URL the user will be redirected to for authentication
# in a CDSSO Scenario.
com.sun.am.policy.agents.config.cdcservlet.url =
# Enable/Disable client IP address validation. This validate
# will check if the subsequent browser requests come from the
# same ip address that the SSO token is initially issued against
com.sun.am.policy.agents.config.client_ip_validation.enable = false
# Below properties are used to define cookie prefix and cookie max age
com.sun.am.policy.agents.config.profile.attribute.cookie.prefix = HTTP_
com.sun.am.policy.agents.config.profile.attribute.cookie.maxage = 300
# Logout URL - application's Logout URL.
# This URL is not enforced by policy.
# if set, agent will intercept this URL and destroy the user's session,
# if any. The application's logout URL will be allowed whether or not
# the session destroy is successful.
com.sun.am.policy.agents.config.logout.url=
# Any cookies to be reset upon logout in the same format as cookie_reset_list
com.sun.am.policy.agents.config.logout.cookie.reset.list =
# By default, when a policy decision for a resource is needed,
# agent gets and caches the policy decision of the resource and
# all resource from the root of the resource down, from the Access Manager.
# For example, if the resource is http://host/a/b/c, the the root of the
# resource is http://host/. This is because more resources from the
# same path are likely to be accessed subsequently.
# However this may take a long time the first time if there
# are many many policies defined under the root resource.
# To have agent get and cache the policy decision for the resource only,
# set the following property to false.
com.sun.am.policy.am.fetch_from_root_resource = true
# Whether to get the client's hostname through DNS reverse lookup for use
# in policy evaluation.
# It is true by default, if the property does not exist or if it is
# any value other than false.
com.sun.am.policy.agents.config.get_client_host_name = true
# The following property is to enable native encoding of
# ldap header attributes forwarded by agents. If set to true
# agent will encode the ldap header value in the default
# encoding of OS locale. If set to false ldap header values
# will be encoded in UTF-8
com.sun.am.policy.agents.config.convert_mbyte.enable = false
#When the not enforced list or policy has a wildcard '*' character, agent
#strips the path info from the request URI and uses the resulting request
#URI to check against the not enforced list or policy instead of the entire
#request URI, in order to prevent someone from getting access to any URI by
#simply appending the matching pattern in the policy or not enforced list.
#For example, if the not enforced list has the value http://host/*.gif,
#stripping the path info from the request URI will prevent someone from
#getting access to http://host/index.html by using the URL http://host/index.html?hack.gif.
#However when a web server (for exmample apache) is configured to be a reverse
#proxy server for a J2EE application server, path info is interpreted in a different
#manner since it maps to a resource on the proxy instead of the app server.
#This prevents the not enforced list or policy from being applied to part of
#the URI below the app serverpath if there is a wildcard character. For example,
#if the not enforced list has value http://host/webapp/servcontext/* and the
#request URL is http://host/webapp/servcontext/example.jsp the path info
#is /servcontext/example.jsp and the resulting request URL with path info stripped
#is http://host/webapp, which will not match the not enforced list. By setting the
#following property to true, the path info will not be stripped from the request URL
#even if there is a wild character in the not enforced list or policy.
#Be aware though that if this is set to true there should be nothing following the
#wildcard character '*' in the not enforced list or policy, or the
#security loophole described above may occur.
com.sun.am.policy.agents.config.ignore_path_info = false
# Override the request url given by the web server with
# the protocol, host or port of the agent's uri specified in
# the com.sun.am.policy.agents.agenturiprefix property.
# These may be needed if the agent is sitting behind a ssl off-loader,
# load balancer, or proxy, and either the protocol (HTTP scheme),
# hostname, or port of the machine in front of agent which users go through
# is different from the agent's protocol, host or port.
com.sun.am.policy.agents.config.override_protocol =
com.sun.am.policy.agents.config.override_host =
com.sun.am.policy.agents.config.override_port = true
# Override the notification url in the same way as other request urls.
# Set this to true if any one of the override properties above is true,
# and if the notification url is coming through the proxy or load balancer
# in the same way as other request url's.
com.sun.am.policy.agents.config.override_notification.url =
# The following property defines how long to wait in attempting
# to connect to an Access Manager AUTH server.
# The default value is 2 seconds. This value needs to be increased
# when receiving the error "unable to find active Access Manager Auth server"
com.sun.am.policy.agents.config.connection_timeout =
# Time in milliseconds the agent will wait to receive the
# response from Access Manager. After the timeout, the connection
# will be drop.
# A value of 0 means that the agent will wait until receiving the response.
# WARNING: Invalid value for this property can result in
# the resources becoming inaccessible.
com.sun.am.receive_timeout = 0
# The three following properties are for IIS6 agent only.
# The two first properties allow to set a username and password that will be
# used by the authentication filter to pass the Windows challenge when the Basic
# Authentication option is selected in Microsoft IIS 6.0. The authentication
# filter is named amiis6auth.dll and is located in
# Agent_installation_directory/iis6/bin. It must be installed manually on
# the web site ("ISAPI Filters" tab in the properties of the web site).
# It must also be uninstalled manually when unintalling the agent.
# The last property defines the full path for the authentication filter log file.
com.sun.am.policy.agents.config.iis6.basicAuthentication.username =
com.sun.am.policy.agents.config.iis6.basicAuthentication.password =
com.sun.am.policy.agents.config.iis6.basicAuthentication.logFile = C:/Sun/Access_Manager/Agents/2.2/debug/Identifier_1414639615/amAuthFilter

If the agent doesnot start properly you would always get redirected to com.sun.am.policy.agents.config.accessdenied.url , if thats not specified you will get a 403.
For the agent itself check that the naming.url is correct. the agent username and passwords are correct, and see that the user has priviledges to write to the agent log files. Apart from these post the windows event logs.

How to view shared (NFS) 11g agent status?

I have installed the MASTER agent and the NFS agent on the same host.
Master Location = /app/oracle/ogc/agent11g (note 748535.1)
NFS State Location = /app/oracle/ogc/emstate
I see an agent running in OEM console, but I don't know if its the Master or NFS.
From the operating system I see an agent process running, but again I don't know which agent is up:
$ ps -ef|grep agent11g |grep -v grep
ogc 11421 1 0 Nov08 ? 00:00:01 /app/oracle/ogc/agent11g/perl/bin/perl /app/oracle/ogc/agent11g/bin/emwd.pl agent /app/oracle/ogc/emstate/sysman/log/emagent.nohup
ogc 11452 11421 0 Nov08 ? 00:00:31 /app/oracle/ogc/agent11g/bin/emagentIf I try to confirm the agent status using emctl, it says the agent is not running:
$ export ORACLE_HOME=/app/oracle/ogc/emstate
export PATH=$ORACLE_HOME/bin:$PATH
$ 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 is Not Running
$ export ORACLE_HOME=/app/oracle/ogc/agent11g
export PATH=$ORACLE_HOME/bin:$PATH
$ 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 is Not RunningHow can I confirm the NFS status from the command line?

Problem Solved by setting correct PATH:
export ORACLE_HOME=/app/oracle/ogc/emstate
export PATH=$ORACLE_HOME/bin:$PATH
emctl status agentOS command correctly shows agent status.

This log -------------policy agent 2.1 for iis5.0

Sun Java System Identity Server Policy Agent 2.1 for Microsoft IIS 5.0
Sun\Identity_Server\Agents\2.1\debug\C__Inetpub_wwwroot\amAgent
2004-07-25 18:06:22.156 Warning 1064:00D01120 PolicyAgent: OnPreprocHeaders(): Identity Server Cookie not found.
2004-07-25 18:06:22.156 Error 1064:00D01120 PolicyAgent: do_redirect() ServerSupportFunction did not succeed: Attempted status = 302 Found
2004-07-25 18:06:22.156 Warning 1064:00D01120 PolicyAgent: OnPreprocHeaders(): No cookies found.
2004-07-25 18:06:22.156 Error 1064:00D01120 PolicyAgent: do_redirect() ServerSupportFunction did not succeed: Attempted status = 302 Found
2004-07-25 18:07:53.921 Error 1064:00D01120 PolicyEngine: am_policy_evaluate: InternalException in Service::getPolicyResult with error message:Policy not found for resource: http://guorui.mygodsun.com:49153/index.asp and code:7
2004-07-25 18:07:53.921 Warning 1064:00D01120 PolicyAgent: am_web_is_access_allowed(http://guorui.mygodsun.com:49153/index.asp, GET) denying access: status = no policy found (7)
2004-07-25 18:07:53.937 128 1064:00D01120 RemoteLog: User amAdmin was denied access to http://guorui.mygodsun.com:49153/index.asp.
2004-07-25 18:07:54.062 Error 1064:00D01120 PolicyAgent: do_redirect(): Error while calling am_web_get_redirect_url(): status = success
2004-07-25 18:07:54.078 Error 1064:00D01120 PolicyAgent: do_redirect() WriteClient did not succeed: Attempted message = HTTP/1.1 403 Forbidden
Content-Length: 13
Content-Type: text/plain
403 Forbidden
from that log,help me
my:
Sun Java System Identity Server 6.1
Sun Java System Directory Server 5.2
Sun Java System Identity Server Policy Agent 2.1 for Microsoft IIS 5.0
help me for that how config?
what error ?
thanks!

Sorr for so many people faced the sam or similar issues. I just joined this support a short while. If you think any old problem which is still critical to you, please repost. We shall try our best to give you assistance. Jerry
Here are some of tips for debugging Web agent.
From the AMAgent.properties, are both IIS and AM are in the same domain? If they are not, then you need to use CDSSO. Also please check in AM, under "Service Configuration-> Platform -> Cookie Domains" , whether cookie is set for the entire domain which includes AM and IIS ("test.com") or just the AM machine name.
Also check whether correct value for "Agent-Identity Server Shared Secret" is entered. This should be your internal ldap password (amldapuser). In the AMAgent.properties for the below property the password will be encrypted and assigned: "com.sun.am.policy.am.password".
Could you also check if the Identity servver and the IIS web server are time synchronized. The problem may be that agent requests policy decisions and the response from server may be timed out due to non-syncrhonized clock.
Don't forget to restart the whole IIS service using internet
management console after making agent changes.
Some of the common error codes:
20: Application authentication failed. This occurs when Agent cannot sucessfully authenticate with Identity Server. This is mainly due to incorrect password for agent entered during agent installation. Please refer to another faq describing how to change password.
7: Policy not found. This error occurs typically if there are no policies defined on Identity server for the given web server URL. Otherwise, there may be time skew between Identity Server and Agent. So, polices fetched from Identity Server is instantly flushed by Agent and attempted to refetch over and over again. This can be solved by running rdate or similar command to synchronize time between the two machines. It is recommended to run NNTP server syncrhonize times between your Identity systems.

ODI agent status shown prepared in Weblogic

hi,
I have installed FDMEE 11.1.2.4. When i start services everything is ok except ODI Java EE agent. I haven't configured it ( i think it was preconfigured).
I have tried starting ODI agent from enterprise manager but i am getting an error; will paste below.
I have seen that in weblogic server under erpi integrator server my odi console status is active and odi agent status is prepared. I don't know how to start JAVA EE agent.
Any help?
Error:
Invoking Start Up operation for application oraclediagent on target ErpIntegrator0.
[Deployer:149193]Operation 'start' on application 'oraclediagent' has failed on 'ErpIntegrator0'
[Deployer:149034]An exception occurred for task [Deployer:149026]start application oraclediagent on ErpIntegrator0.: [HTTP:101216]Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent".
com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=MasterMemberSet(
    ThisMember=null
    OldestMember=null
    ActualMemberSet=MemberSet(Size=0
    MemberId|ServiceVersion|ServiceJoined|MemberState
    RecycleMillis=1200000
    RecycleSet=MemberSet(Size=0
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:58)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:427)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:968)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:937)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:919)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1296)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:297)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:204)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:181)
at oracle.odi.runtime.agent.coherence.OdiAgentCoherenceCache.<init>(OdiAgentCoherenceCache.java:52)
at oracle.odi.runtime.agent.servlet.AgentServlet.initCoherence(AgentServlet.java:812)
at oracle.odi.runtime.agent.servlet.AgentServlet.initializeClusterCache(AgentServlet.java:762)
at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:437)
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:250)
at javax.servlet.GenericServlet.init(GenericServlet.java:242)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:672)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
:com.tangosol.net.RequestTimeoutException:Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=MasterMemberSet(
    ThisMember=null
    OldestMember=null
    ActualMemberSet=MemberSet(Size=0
    MemberId|ServiceVersion|ServiceJoined|MemberState
    RecycleMillis=1200000
    RecycleSet=MemberSet(Size=0
Operation Start Up on target oraclediagent Failed. Please see error logs for details.
Regards

Hi JanGLi,
The ODI Agent is completely failing to start here from the error that you initially pasted so agent tests are not going to work wherever you try them. Port 6550 should have something listening on it as that's the port that the FDMEE managed server listens on so that would only prove that the FDMEE managed server is up. I can't see the connection closed error having anything to do with running out of connections in the connection pool either as it's simply a message saying that a connection was closed (not that the connection pool is exhausted).
On the plus side though I have seen the 'Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent"' error in the past (I get a lot of the really nice issues coming my way). Which operating system are you using here? I've seen this happen on Windows when there are multiple network interfaces and an incorrect interface has been put to the top of the bind order (e.g. an interface that has fallen back to a link local address in the 169.254.0.0/16 range as DHCP has failed).
Regards
Craig

Install Fails With SQL Server Version - Status: Incorrect

Hi. I am working to install BPC 7 in a single server environment. During installation the setup diangostic detects a problem with [[Microsoft and 3rd Party Software]], below is what appears:
X - SQL Server Version
____    OK - Required: 10.0.1600.22 or higher
____    OK - Currently: Not Installed
____    X   - Status: Incorrect
X - SQL Reporting Services Server Version
____    OK - Required: 10.0.1600.22 or higher
____    OK - Currently: Not Installed
____    X   - Status: Incorrect
X - OLAP Server Version
____    OK - Required: 10.0.1600.22 or higher
____    OK - Currently: Not Installed
____    X   - Status: Incorrect
Under [[Computer Services Status]] SQL Server is alright:
OK - MS SQL Server Service
____    OK - Required: Running
____    OK - Currently: Running
____    OK - Status: OK
OK - MS SQL Server Agent Service
____    OK - Required: Running
____    OK - Currently: Running
____    OK - Status: OK
OK - SQL Integrated Service
____    OK - Required: Running
____    OK - Currently: Running
____    OK - Status: OK
OK - SQL Report Service
____    OK - Required: Running
____    OK - Currently: Running
____    OK - Status: OK
OK - MS SQL Server OLAP Service
____    OK - Required: Running
____    OK - Currently: Running
____    OK - Status: OK
What I've Checked so far:
- Collation
- Account for installation is SQL SysAdmin and a Windows account
- Mixed mode authentication
I should mention, this is a single server install on a 64 bit version of Windows, with 64 bit version of SQL.
Any experience, ideas or suggestions are welcome.
Joe
Edited by: jwainz on Mar 29, 2010 5:55 PM

I think the clearest statement about this is on page 11 of the Master Guide (SAP BPC 7.0 M Master Guide at [http://service.sap.com/instguidesEPM-BPC]).
Look at the rows for OLAP Server and Microsoft SQL Server. In each of those, you wil find this statement:
"Can be 64‒bit when separate from Application/web services"
On page 10 in the Installation Guide, for look at the rows for Application server Web Server. The prerequisites are as follow:
App Server:
Windows Server 2003 or Windows Server 2003 R2 Standard or Enterprise Edition SP2 (32-bit) configured with NTFS, set to English (United States)
Web Server:
Windows Server 2003 or Windows Server 2003 R2 Standard or Enterprise Edition SP2 (32-bit) configured with NTFS
Finally, the PAM is a bit confusing. For product SAP BPC 7.0 FOR MICROSOFT, click on the tab Operating Systems and then click on the tab BPC Server. That is the software that you install for the Application Server and the Web Server server types. The Operating System Version listed is WINDOWS SERVER 2003/IA32 32BIT

A problem for grid control agent installation.

Hi, All:
I am installing EM grid control agent installation in wanted server...
after agent installation and excuting root.sh, OUI start to run automatically Agent Configuration Assistant... then got an error, the reason for error from the log is :
Requesting an Oracle Wallet and Agent Key from the OMS... Failed.
Invalid Agent Registration Password.
The Agent has not been secured.
that means I put wrong agent registration password,
so how can I fix this in the mid way?
thanks a lot in advance.

I tried
emctl secure agent
when prompt for password:
(just type enter, leave it empty)
TZ set to US/Eastern
Oracle Enterprise Manager 10g Database Control Release 10.2.0.3.0
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
Enter Agent Registration password :
Stopping agent...
seems like that process is never ending....
then I typed CTL+C
..............................Failed to stop agent.

Dbconsole - emctl agent status - incorrect for 'emctl resetTZ agent'

Similar Messages

Maybe you are looking for