SRVCTL is not starting all DB nodes
Hi DBAs,
I have 11.5.10.2 (2 nodes) with 4 node RAC DB on Solaris 10 (64 bit). I turned off the applications and then stopped the RAC DB using srvctl stop -d RACDB. Now I am trying to start the DB with srvctl start -d RACDB but it is only starting 1st node and I am also not getting any error like srvctl couldn't start the RACDB2, RACDB3, RACDB4....
By logging into the server I can start the other 3 DB instances from SQL Plus. Please help me to resolve the issue.
Thanks
-Samar-
Hi Hussein,
The issue is that srvctl is not starting the database instances on remainng 3 nodes. Only 1st node instance is getting started. I also don't see any error while doing the srvctl start database -d RACDB command.
No recent changes are performed to the applications or DB.
Thanks
-Samar-
Similar Messages
-
Af:tree inside af:accordion is not showing all the nodes
Hi All,
I am using Oracle JDeveloper 11g Release 2.
I have af:tree enclosed inside af:panelStretchLayout, displaying data from database table. af:tree is not displaying all data(nodes) in the space available to it. It is hiding the data at middle. I have tried number of options but in vein. The code is given below:
<af:panelAccordion id="pa1">
<af:showDetailItem text="Browse Course Categories" id="sdi1" icon="/Images/tree.png">
*<af:panelStretchLayout id="psl112">*
*<f:facet name="center">*
<af:tree value="#{bindings.BaseCourseCategories1.treeModel}" var="node"
selectionListener="#{bindings.BaseCourseCategories1.treeModel.makeCurrent}"
rowSelection="single" id="t3" *styleClass="AFStretchWidth"*>
<f:facet name="nodeStamp">
<af:outputText value="#{node.CategoryTitle}" id="ot4"/>
</f:facet>
<f:facet name="contextMenu">
<af:popup childCreation="deferred" autoCancel="disabled" id="p1">
<af:menu text="Course Categories" id="m1">
<af:commandMenuItem text="Show Categories" id="cmi1"
actionListener="#{SelectAllCategoryBean.refreshChildCategories}"
action="refresh">
<f:attribute name="CategoryId"
value="#{node.CategoryId}"/>
</af:commandMenuItem>
<af:commandMenuItem id="cmi2" text="Add Category"
action="goCreateCourseCats"/>
</af:menu>
</af:popup>
</f:facet>
</af:tree>
</f:facet>
</af:panelStretchLayout>
</af:showDetailItem>
</af:panelAccordion>Any guidance or help....
Thanks in advance
BilalHi Peter,
I have checked for stretchChildren="first" property of af:panelAccordion, but didn,t found.
Thanks for response.
Regards
Bilal -
SQL Cluster services is not start in secound node.
SQL Cluster services is not start in secound node.
Start or Stop the Cluster Service on a Cluster Node
https://technet.microsoft.com/en-us/library/cc771742.aspx
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/ -
Listener does not start in Mutli-node install & concurrent p. manager
Hello everyone!
I have been using Oracle Apps 11.5.10.2 on Linux OS for some time now and it was working fine. Recently I decided to separate it into 2 tiers (DB and AS) and so I started the installation from scratch.
I have two questions regarding running the Applications on 2 nodes:
1) Where do you advise to put the concurrent manager in the configuration with only two nodes? I know that ideally it should be on a totally separate server, but I only have two machines available. I was thinking about putting it on the AS layer. Any suggestions?
2) I was able to install (stage/rapidwiz/.../ so on) the first node (default database-9i). After that, I started all the db processes using the addbctl.sh script as follows (I installed the VIS demo db):
$ ./addbctl.sh start VIS
This script works fine exiting with status 0.
However, when I try to start the listener using the provided addlnctl.sh script:
$ ./addlnctl.sh start VIS
it returns an error. The log (vis.log in network/admin) reads as follows:
TNSLSNR for Linux: Version 9.2.0.6.0 - Production on 05-SEP-2006 20:02:06
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
System parameter file is /mnt/hdd1/vis/visdb/9.2.0/network/admin/VIS_oradb/listener.ora
Log messages written to /mnt/hdd1/vis/visdb/9.2.0/network/admin/vis.log
Trace information written to /mnt/hdd1/vis/visdb/9.2.0/network/admin/vis.trc
Trace level is currently 0
Started with pid=4277
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROCVIS)))
Error listening on: (ADDRESS=(PROTOCOL=TCP)(Host=10.1.1.52)(Port=1521))
TNS-12532: TNS:invalid argument
TNS-12560: TNS:protocol adapter error
TNS-00502: Invalid argument
Linux Error: 515: Unknown error 515
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROCVIS)))
***********************EOF****************************************
This is the listener.ora file in $ORACLE_HOME/network/admin/VIS_oradb:
# $Header: ad8ilsnr.ora 115.6 2005/05/20 11:31:24 pariga ship $
# This file is automatically generated by AutoConfig. It will be read and
# overwritten. If you were instructed to edit this file, or if you are not
# able to use the settings created by AutoConfig, refer to Metalink document
# 165195.1 for assistance.
# Net8 definition for Database listener
VIS =
(ADDRESS_LIST =
(ADDRESS= (PROTOCOL= IPC)(KEY= EXTPROCVIS))
(ADDRESS= (PROTOCOL= TCP)(Host= oradb.vision )(Port= 1521))
SID_LIST_VIS =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME= /mnt/hdd1/vis/visdb/9.2.0)
(SID_NAME = VIS)
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /mnt/hdd1/vis/visdb/9.2.0)
(PROGRAM = extproc)
STARTUP_WAIT_TIME_VIS = 0
CONNECT_TIMEOUT_VIS = 10
TRACE_LEVEL_VIS = OFF
LOG_DIRECTORY_VIS = /mnt/hdd1/vis/visdb/9.2.0/network/admin
LOG_FILE_VIS = VIS
TRACE_DIRECTORY_VIS = /mnt/hdd1/vis/visdb/9.2.0/network/admin
TRACE_FILE_VIS = VIS
ADMIN_RESTRICTIONS_VIS = OFF
IFILE=/mnt/hdd1/vis/visdb/9.2.0/network/admin/VIS_oradb/listener_ifile.ora
*****************************EOF**********************************
I disabled the iptables firewall altogether (temporarily), but it did not help. I do not have any other services running on port 1521. I never changed any environment variables as I believe they are being set by all the ad*****ctl.sh scripts automatically. I did not make any customizations - just using stock E-Business CD's and default config.
Any help or advice is greatly appreciated !Steven Chan is a Director in the Oracle Applications Technology Group.
http://blogs.oracle.com/schan/comments?u=stevenChan&p=376&link=http%3A%2F%2Fblogs.oracle.com%2Fschan%2F2006%2F06%2F28%23a376
Hi Steven,
It is nice to see new posts from you. "Split Configurations" + "Shared Apps configuration" looks very attractive to me in terms of Apps SW management. You need to apply patch just once even if you have got multiple DB and Apps nodes in you configuration.
Some customers of mine saying that is isn't recommended configuration. Oracle recommends to keep CM tier on the same hosts as DB is running.
Just wonder if you can advice on the issue?
Thank you in advance, Yury
Yury,
That recommendation no longer applies.
With the high-bandwidth networks available today, combined with the fact that CM Tier hosts typically run in the same data centre as the Database Tier hosts, you can safely put the CM services on a different server.
Regards,
Steven
----------------------------------------------- -
Oracle Management Server not starting up. says node manager is down!!!
Hi ALL,
We are trying to startup (OMS) Oracle Management Server but it's not starting up. it tries to connect to the node manager and says failed to connect to Node Manager as the node manager is not running.
OPMN also not running.
I have attached a snapshot so you can see.
PLEASE HELP
hi Again, below are the error reports
2014-01-30 18:56:52,360 [Thread-2] INFO commands.BaseCommand run.554 - <ERR>weblogic.nodemanager.NMConnectException: Connection refused. Could not connect to NodeManager. Check that it is running at omkn-ms01.int.unisa.ac.za:7403.
2014-01-30 18:56:52,360 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.PlainSocketImpl.socketConnect(Native Method)
2014-01-30 18:56:52,360 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.Socket.connect(Socket.java:529)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.nodemanager.client.SSLClient.createSocket(SSLClient.java:38)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:228)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:200)
2014-01-30 18:56:52,362 [Thread-1] INFO commands.BaseCommand run.554 - <OUT>Attempt to connect to nm failed. Trying to start it...
2014-01-30 18:56:52,362 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:206)
2014-01-30 18:56:52,362 [Thread-1] INFO commands.BaseCommand run.554 - <OUT>status of node manager:
2014-01-30 18:56:52,362 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:53)
2014-01-30 18:56:52,362 [Thread-1] INFO commands.BaseCommand run.554 - <OUT>Not connected to Node Manager
2014-01-30 18:56:52,362 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:179)
2014-01-30 18:56:52,363 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:172)
regards,
Ambrose.I assumethe node manager is not running on Exadata though you have posted in the Exadata forum !
how are you starting it. Are you using the gcstartup script within init.d ?
Thanks -
Opmn does not start all processs when server ( windows 2003 is rebooted ).
There is a startup script which starts every process when run from cmd. But when the server is rebooted it does not start Portal, WebCache.
The startup Script :
@ECHO OFF
REM ---------------------------------------------
REM 10gAS Rel 2 Midtier startup script
REM ---------------------------------------------
date /t
time /t
REM ----------------------------------
REM Set Oracle Home
REm -----------------------------------
set ORACLE_HOME=d:\Oracle\Ora10gMid
set PATH=%ORACLE_HOME%\bin;%ORACLE_HOME%\dcm\bin;%ORACLE_HOME%\opmn\bin;%PATH%;
REM ----------------------------------
REM startup ProcessManager (OPMN)
REM ----------------------------------
REM call %ORACLE_HOME%\opmn\bin\opmnctl startall
call %ORACLE_HOME%\opmn\bin\opmnctl start
call %ORACLE_HOME%\opmn\bin\opmnctl startproc ias-component=WebCache
call %ORACLE_HOME%\opmn\bin\opmnctl startproc ias-component=OC4J
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc process-type=WebCacheAdmin
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc process-type=home
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc process-type=OC4J_BI_Forms
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc process-type=OC4J_Portal
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc process-type=HTTP_Server
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc ias-component=Discoverer
======================================================
I tried starting each process type individually and it does not start OC4J and WebCache components. This does not work only during reboot.
Thanks in advance for our valuable suggestions
vno bat file is needed for opmn to startall on service restart or system reboot. Opmn remembers the state of the services on a clean shutdown of the service & will bring it back. So just do a opmn startall, then restart the Oracle<OraHome>ProcessManager service & check using opmn status. All services should be in the same state as before the Oracle<OraHome>ProcessManager was restarted.
where/why are you trying to use a bat file to stopall/startall? It can be done via a script, but the user that starts the bat file MUST be the same user that installed OAS/OID. -
SAP not started on CI node thru Cluster Script
Hi
We have installed the PI 7.1 on HP Unix 11v3 and oracle conbination. We have done the cluster package failover
of CI to DB system and done the complete installation on DB with high availability option. Let on we have splited
the CI to CI and keep the DB to DB note. The installation happend successfully and system started successfully on
both node.
Now we are doing the HP-UNIX cluster configuration and integration. But we have found that the DB services are
starting up successfully on DB node but the CI services are not starting up on CI node. The cluster error file
are attached for your reference. Since the project golive is left just 20 day . Request you to provide solution
on the same. Please also let us know if any further log is required.
Regards
Vimal PathakOct 6 16:16:13 root@htlxici: (start_app ciPP9 01 pp9adm): P: Start
Oct 6 16:16:13 root@htlxici: (start_app ciPP9 01 pp9adm): P: FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 356 returns 0
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (start_app ciPP9 01 pp9adm): Finishing startup attempt
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (wait_pidlist): Killed the wait_pidlist background shell. PID: 29953
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (start_d): Leaving parallel dialog instance startup delay
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sapcontrol" owner: "pp9adm"
Oct 6 16:16:14 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:14 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:14 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 1016 for 1015 - Timeout: 100 secs)
Oct 6 16:16:17 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 1015 returns 1
Oct 6 16:16:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 5 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:16:22 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:22 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:22 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:23 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:24 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:24 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:24 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 1466 for 1464 - Timeout: 100 secs)
Oct 6 16:16:25 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 1464 returns 1
Oct 6 16:16:25 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:25 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 10 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:16:35 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:35 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:35 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 1919 for 1917 - Timeout: 100 secs)
Oct 6 16:16:37 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 1917 returns 1
Oct 6 16:16:37 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:37 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 15 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:16:52 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:52 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:53 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 2412 for 2410 - Timeout: 100 secs)
Oct 6 16:16:55 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 2410 returns 1
Oct 6 16:16:55 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:55 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 20 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:17:15 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:17:15 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:17:15 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 2878 for 2875 - Timeout: 100 secs)
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 2875 returns 1
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): Instance DVEBMGS01 not responding
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (start_d): ERROR: Instance DVEBMGS01 - fatal startup problem detected
Oct 6 16:17:17 root@htlxici master_control_script.sh[28963]: ##### Failed to start package ciPP9, rollback steps #####
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Entering SGeSAP sapinstance.sh 'stop' runtime steps ...
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: SGeSAP - B.05.00.00 - Last modified 02/11/08
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Found: /etc/cmcluster/scripts/sgesap/sap_functions.sh
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Found: /etc/cmcluster/scripts/sgesap/customer_functions.sh
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Not found: /etc/cmcluster/scripts/ext/ciPP9_customer_functions.sh
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_versions): Version check passed
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_versions): Log Level is 4
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance administrator : 'pp9adm'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance home directory : '/home/pp9adm'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Startprofile : '/usr/sap/PP9/SYS/profile/PP9_DVEBMGS01_ciPP9'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance profile : '/usr/sap/PP9/SYS/profile/PP9_DVEBMGS01_ciPP9'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance work directory : '/usr/sap/PP9/DVEBMGS01/work'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sappfpar" owner: "pp9adm"
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (init_params_sap_inst): Trying to determine instance type of DVEBMGS01...
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (init_params_sap_inst): Package will handle Application Server Instance DVEBMGS01
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_access): Testing directory /sapmnt/PP9/global...
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 3216 for 3215 - Timeout: 100 secs)
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 3215 returns 0
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_access): /sapmnt/PP9/global accessible
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (check_access): Testing directory /usr/sap/PP9...
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 3244 for 3243 - Timeout: 100 secs)
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 3243 returns 0
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (check_access): /usr/sap/PP9 accessible
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (init_params_sap_inst): System is not using Instance Agents
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_d): Initiate stopping of dialog instance DVEBMGS01 on ciPP9
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (is_ip_local): ciPP9 is local
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_app ciPP9 01 pp9adm): Attempting local stop of instance...
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_d): Waiting for parallel shutdown sequence to finish
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sapcontrol" owner: "pp9adm"
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_app ciPP9 01 pp9adm): Running /usr/sap/PP9/DVEBMGS01/exe/sapcontrol -nr 01 -function StopWait 100 1
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 3325 for 3322 - Timeout: 100 secs)
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (wait_pidlist): Forked the wait_pidlist background shell. PID: 3319
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (wait_pidlist): PIDLIST: 3271 -1
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (wait_pidlist): PIDlist watchdog initiated (PIDlist: 3271)
Oct 6 16:17:20 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 3322 returns 0
Oct 6 16:17:20 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/cleanipc" owner: "pp9adm"
Oct 6 16:17:22 root@htlxici sapinstance.sh[3089]: (clean_ipc): Searching shmem of DVEBMGS01 on htlxici using normal cleanup policy
Oct 6 16:17:23 root@htlxici: (clean_ipc): P: OsKey: 10110 0x0000277e Shared Memory Key: 10 removed
Oct 6 16:17:23 root@htlxici sapinstance.sh[3089]: (wait_pidlist): Killed the wait_pidlist background shell. PID: 3319
Oct 6 16:17:23 root@htlxici sapinstance.sh[3089]: (stop_d): Parallel dialog instance shutdown finished
Oct 6 16:17:23 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sapcontrol" owner: "pp9adm"
Oct 6 16:17:25 root@htlxici sapinstance.sh[3089]: (is_ip_local): ciPP9 is local
Oct 6 16:17:25 root@htlxici sapinstance.sh[3089]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:17:25 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 4369 for 4368 - Timeout: 100 secs)
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 4368 returns 1
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: (crit_test_app): Instance DVEBMGS01 not responding
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: Leaving SGeSAP sapinstance.sh 'stop' runtime steps ...
Oct 6 16:17:27 root@htlxici package_ip.sh[4578]: Removing 172.31.112.131
Oct 6 16:17:27 root@htlxici package_ip.sh[4578]: Remove IP address 172.31.112.131 from subnet 172.31.112.0
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: Number of components: 5 6
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: sorted components in array: 5 6
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: sorted indexes: 0 1
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: processing 1 /usr/sap/PP9/DVEBMGS01 1
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: processing 0 /usr/sap/PP9 1
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: Mount order: 1 2
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: max mnt order: 2
Oct 6 16:17:28 root@htlxici filesystem.sh[4610]: Unmounting filesystem on /dev/vx/dsk/pp9cidg/DVEBMGS61
Oct 6 16:17:29 root@htlxici filesystem.sh[4610]: Unmounting filesystem on /dev/vx/dsk/pp9cidg/sap_PP9
Oct 6 16:17:29 root@htlxici volume_group.sh[4678]: Deporting disk group pp9cidg
Oct 6 16:17:30 root@htlxici master_control_script.sh[28963]: ###### Failed to start package for ciPP9 ###### -
How do you fix an ipod that will begin to start, but never does?
It will begin to start, with the apple logo, but then you hear the hard drive click off then the screen goes blank. It has been repeating this for about an hour now.
Ive tried resetting and restoring, but I cant get it to do anything but cycle through the apple logo screen.How do you fix an ipod that will begin to start, but
never does?
It will begin to start, with the apple logo, but then
you hear the hard drive click off then the screen
goes blank. It has been repeating this for about an
hour now.
Ive tried resetting and restoring, but I cant get it
to do anything but cycle through the apple logo
screen.
I think i am having the same problem the logo will apple logo will pop up and after 15 mins a language choice pops up when I chose that i get to the normal menu but when i plug it into my computer it isnt recognized. In disk mode i can only get it recognized in "my computer" and soon after freezes and the fun starts all over again
Sony Vaio Windows XP 5th Gen 30GB iPod -
Services not starting after a node crash
hi
We have a 3 node cluster and one of the nodes crashed today, also the services did not get relocated to the other node and when we try to manullay stop/start/relocate the service we get the following error
srvctl stop service -d BCB -s BCB_J2EE -f
PRCD-1085 : Failed to stop service BCB_J2EE
PRCR-1065 : Failed to stop resource ora.BCB.BCB_j2ee.svc
CRS-2533: Server 'bcb528' is down. Unable to perform the operation on 'ora.BCB.BCB_j2ee.svc'
Would anyone has seen this before
Thx
JJthis is what i can find in log
[ CRSPE][60] Server [bcb528] is unreachable. Stopping the sequencer for: bcbCRON 1 1
2011-02-28 08:15:21.778: [ CRSPE][60] Sequencer for [bcbCRON 1 1] has completed with error: CRS-2533: Server 'bcb528' is down. Unable to pe
rform the operation on 'bcbCRON'
2011-02-28 08:15:21.778: [ CRSPE][60] Required instruction failed in op: START of [bcbCRON 1 1] on [bcb529] : 105247290
2011-02-28 08:15:21.781: [UiServer][62] Container [ Name: ORDER
MESSAGE:
TextMessage[CRS-2533: Server 'bcb528' is down. Unable to perform the operation on 'bcbCRON']
MSGTYPE:
TextMessage[1]
OBJID:
TextMessage[bcbCRON 1 1]
WAIT:
TextMessage[0] -
0ORGUNIt time dependent hierarchy not showing all valid nodes in BO , but in BW its correctly shown
Hi All,
We have 0ORGUNIT hierarchy shown in one of the Webi reports. 0ORGUNIT is time dependent hierarchy.
In BW report we can see below nodes for hierarchy
Hierarchy Valid From Valid To
Z05 Root Company 01.07.2013 31.12.9999 - Parent node
Z05 Branch 2 01.10.2013 31.12.9999 - Child Node
Z05 Division 09.12.2013 31.12.9999 - Child Node
In BO webi we can see only two nodes
Z05 Root Company 01.07.2013 31.12.9999 - Parent node
Z05 Division 09.12.2013 31.12.9999 - Child Node
Any idea why in BO webi the other node is not shown ? This is happening only for time dependent hierarchy and only in BO not in BW.
Thanks,
ShraddhaHi Shraddha ,
Check at webi query panel level any restrictions applied to hierarchy levels.
Check at BEx query level,select 0ORGUNIT ,hierarchy -Expand to level .
Here specify Max level.
lastly, check any filters/restrictions applied on data.If yes,remove restrictions. -
My new HP Split X2 2 in 1 is not starting all the time when I press power button.
I brought HP Split X2 2 in 1 (tablet com laptop)1one week back and I have the prob from day 1. Press the power button for 1 sec to 10 sec for 100 tmes a day, it is starting only once per day. No one knows at which attempt it may started it may be 10th or 50th or 100th. Certenly in the begining of the day it is not startng. If it starts by luck, then it works. After it start, even if u do a shutdown and restart, it works. But go to sleep and wake up in the morning, my attempts starts. Customer care talks to you politly but each time each member has diffrent solutions. Its a defective piece..
Any suggestons would be appritated. It has 2 batteries, 1 in touch panel and the other in key board.If you have a fairly new Mac...
You are still under warranty. Call Apple Care. Make sure you get a case number as all repairs have an additional 90 days of warranty.
#1 - You have 14 days from the date of purchase to return your computer with no questions asked.
#2 - You have 90 days of FREE phone tech support.
#3 - You have the standard one year Apple warranty.
#4 - If you've purchased an AppleCare Protection Plan, your warranty last for 3 years. You can obtain AppleCare anytime up to the first year of the purchase of your computer.
Take FULL advantage of your warranty. Posting on a message board should be done as a last resort and if you are out of warranty or Apple Care has expired. -
Public Interface not responding after second node is started in the cluster
Hi
Has anyone ever experienced the public interface not responding between nodes in the cluster (ping, ssh, scp) after the second nodeapps is started in the cluster?
This is a new install so all I have installed so far is the base release of CRS 10.2.0. This is on Solaris10. The vipca failed during the installation, however I was able to proceed and manually add the nodeapps using srvctl add nodeaps -n -o -A.
It seems after the second node is started I loose all connectivity to the public interfaces and to my default gateway.
Also I'm getting the following messages sometimes after I try and stop the nodeapps and start them back up.
CRS-1006: No more members to consider
CRS-0215: Could not start resource 'ora.node1.vip'.
Any suggestions on where I should start troubleshooting?
ThanksDo you have default GW?
It can connects with GW, can't it?
Check metalink
CRS-0215: Could not start resource 'ora..vip' [ID 356535.1]
CRS-1006: No more members to consider when starting service [ID 465364.1]
Good Luck -
SOA 11.1.1.5 two Node Cluster BAM not starting on the second Machine
Hi,
I have installed Oracle SOA 11.1.1.5 in a 2 Node Cluster. Both SOA Managed Servers are coming up fine. BAM Managed Server installed on the primary HOST also comes up fine. But my second BAM Managed Server is not starting. I don't see anything in the logs and on the Console the status is showing as Starting but it never starts. I can access the BAM Console for the one installed on the primary HOST but when giving the URL for the second HOST it doesn't come up as the I don't see an option the server is running.
I have 2 machines for this cluster setup
On machine one with IP Address: *192.168.2.2* all below servers come-up fine
Admin
BAM1
SOA1
On machine two with IP Address: *192.168.3.3* have the below servers and only the SOA is coming up fine BAM not starting
BAM2 not starting
SOA2 coming up fine also
After giving user/password this is what I see in the terminal window and it never moves looks like getting stuck:
<Mar 8, 2012 12:31:40 PM EST> <Info> <Security> <BEA-090065> <Getting boot ident
ity from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Mar 8, 2012 12:32:58 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Mar 8, 2012 12:33:01 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Mar 8, 2012 12:33:01 PM EST> <Info> <WorkManager> <BEA-002900> <Initializing se
lf-tuning thread pool>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320400> <The log fi
le C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BA
M2.log will be rotated. Reopen the log file if tailing has stopped. This can hap
pen on some platforms like Windows.>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320401> <The log fi
le has been rotated to C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\
servers\BAM2\logs\BAM2.log00001. Log messages will continue to be logged in C:\o
racle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BAM2.log.
>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\
logs\BAM2.log is opened. All server side log events will be written to this file
.>
<Mar 8, 2012 12:33:09 PM EST> <Notice> <Security> <BEA-090082> <Security initial
izing using security realm myrealm.>
<Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STANDBY>
<Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Mar 8, 2012 12:33:26 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional
package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.applcore.
model, Specification-Version: 0.1, Implementation-Version: 11.1.1.0.0, reference
d from: C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tm
p\_WL_user\usermessagingserver\wehyzl]. Make sure the referenced optional packag
e has been deployed as a library.>
<Mar 8, 2012 12:33:28 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageRe
ceiverBean(Application: usermessagingserver, EJBComponent: sdpmessagingengine.ja
r), the value for the activation config property 'connectionFactoryJNDIName' wil
l be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFacto
ry';>
<Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-012035> <The Remote interface
method: 'public abstract void oracle.ucs.userprefs.DefaultFactStore.setBusiness
FactValue(java.lang.String,java.lang.String,java.lang.Object) throws oracle.ucs.
userprefs.UserPrefsException' in EJB 'UserPrefsDefaultFactStore' contains a para
meter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Use
rPrefsDefaultFactStore' has call-by-reference set to false, this parameter is no
t Serializable and hence will be passed by reference. A parameter can be passed
using call-by-value only if the parameter type is Serializable.>
<Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageDi
spatcherBean(Application: usermessagingserver, EJBComponent: sdpmessagingclient-
ejb-parlayx.jar), the value for the activation config property 'connectionFactor
yJNDIName' will be ignored since it is overridden with the value 'OraSDPM/QueueC
onnectionFactory';>
<Mar 8, 2012 12:33:37 PM EST> <Warning> <Connector> <BEA-190110> <Resource Adapt
er is calling BootstrapContext.createTimer() and allocating a Timer Thread that
is not managed by WebLogic Server. This may adversely impact the performance/ope
ration of WebLogic Server.>
<Mar 8, 2012 12:33:37 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB DriverDis
patcherBean(Application: usermessagingdriver-email, EJBComponent: sdpmessagingdr
iver-dispatcher-ejb.jar), the value for the activation config property 'connecti
onFactoryJNDIName' will be ignored since it is overridden with the value 'OraSDP
M/QueueConnectionFactory';>
<Mar 8, 2012 12:33:43 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-adc-ejb.jar/META-INF/ejb-jar.xml. A version attribut
e is required, but this version of the Weblogic Server will assume that the JEE5
is used. Future versions of the Weblogic Server will reject descriptors that do
not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-ems-ejb.jar/META-INF/ejb-jar.xml. A version attribut
e is required, but this version of the Weblogic Server will assume that the JEE5
is used. Future versions of the Weblogic Server will reject descriptors that do
not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-eventengine-ejb.jar/META-INF/ejb-jar.xml. A version
attribute is required, but this version of the Weblogic Server will assume that
the JEE5 is used. Future versions of the Weblogic Server will reject descriptors
that do not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-reportcache-ejb.jar/META-INF/ejb-jar.xml. A version
attribute is required, but this version of the Weblogic Server will assume that
the JEE5 is used. Future versions of the Weblogic Server will reject descriptors
that do not specify the JEE version.>
<Mar 8, 2012 12:33:52 PM EST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-
26024> <Registration of driver Email-Driver did not complete; will retry periodi
cally until messaging server responds.>This is what I see in the diagnostic log
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> And this is what I see in the log
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048125> <BEA-149059> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014021> <The EJB 'BamAdcServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-adc-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014022> <******** oracle.bam.adc.ejb.BamAdcServerRemote is bound with JNDI name:BamAdcServerBean#oracle.bam.adc.ejb.BamAdcServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-adc-ejb_jarBamAdcServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149060> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149059> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> Any help is appreciated.
ThanksHi,
I have installed Oracle SOA 11.1.1.5 in a 2 Node Cluster. Both SOA Managed Servers are coming up fine. BAM Managed Server installed on the primary HOST also comes up fine. But my second BAM Managed Server is not starting. I don't see anything in the logs and on the Console the status is showing as Starting but it never starts. I can access the BAM Console for the one installed on the primary HOST but when giving the URL for the second HOST it doesn't come up as the I don't see an option the server is running.
I have 2 machines for this cluster setup
On machine one with IP Address: *192.168.2.2* all below servers come-up fine
Admin
BAM1
SOA1
On machine two with IP Address: *192.168.3.3* have the below servers and only the SOA is coming up fine BAM not starting
BAM2 not starting
SOA2 coming up fine also
After giving user/password this is what I see in the terminal window and it never moves looks like getting stuck:
<Mar 8, 2012 12:31:40 PM EST> <Info> <Security> <BEA-090065> <Getting boot ident
ity from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Mar 8, 2012 12:32:58 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Mar 8, 2012 12:33:01 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Mar 8, 2012 12:33:01 PM EST> <Info> <WorkManager> <BEA-002900> <Initializing se
lf-tuning thread pool>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320400> <The log fi
le C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BA
M2.log will be rotated. Reopen the log file if tailing has stopped. This can hap
pen on some platforms like Windows.>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320401> <The log fi
le has been rotated to C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\
servers\BAM2\logs\BAM2.log00001. Log messages will continue to be logged in C:\o
racle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BAM2.log.
>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\
logs\BAM2.log is opened. All server side log events will be written to this file
.>
<Mar 8, 2012 12:33:09 PM EST> <Notice> <Security> <BEA-090082> <Security initial
izing using security realm myrealm.>
<Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STANDBY>
<Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Mar 8, 2012 12:33:26 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional
package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.applcore.
model, Specification-Version: 0.1, Implementation-Version: 11.1.1.0.0, reference
d from: C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tm
p\_WL_user\usermessagingserver\wehyzl]. Make sure the referenced optional packag
e has been deployed as a library.>
<Mar 8, 2012 12:33:28 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageRe
ceiverBean(Application: usermessagingserver, EJBComponent: sdpmessagingengine.ja
r), the value for the activation config property 'connectionFactoryJNDIName' wil
l be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFacto
ry';>
<Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-012035> <The Remote interface
method: 'public abstract void oracle.ucs.userprefs.DefaultFactStore.setBusiness
FactValue(java.lang.String,java.lang.String,java.lang.Object) throws oracle.ucs.
userprefs.UserPrefsException' in EJB 'UserPrefsDefaultFactStore' contains a para
meter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Use
rPrefsDefaultFactStore' has call-by-reference set to false, this parameter is no
t Serializable and hence will be passed by reference. A parameter can be passed
using call-by-value only if the parameter type is Serializable.>
<Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageDi
spatcherBean(Application: usermessagingserver, EJBComponent: sdpmessagingclient-
ejb-parlayx.jar), the value for the activation config property 'connectionFactor
yJNDIName' will be ignored since it is overridden with the value 'OraSDPM/QueueC
onnectionFactory';>
<Mar 8, 2012 12:33:37 PM EST> <Warning> <Connector> <BEA-190110> <Resource Adapt
er is calling BootstrapContext.createTimer() and allocating a Timer Thread that
is not managed by WebLogic Server. This may adversely impact the performance/ope
ration of WebLogic Server.>
<Mar 8, 2012 12:33:37 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB DriverDis
patcherBean(Application: usermessagingdriver-email, EJBComponent: sdpmessagingdr
iver-dispatcher-ejb.jar), the value for the activation config property 'connecti
onFactoryJNDIName' will be ignored since it is overridden with the value 'OraSDP
M/QueueConnectionFactory';>
<Mar 8, 2012 12:33:43 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-adc-ejb.jar/META-INF/ejb-jar.xml. A version attribut
e is required, but this version of the Weblogic Server will assume that the JEE5
is used. Future versions of the Weblogic Server will reject descriptors that do
not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-ems-ejb.jar/META-INF/ejb-jar.xml. A version attribut
e is required, but this version of the Weblogic Server will assume that the JEE5
is used. Future versions of the Weblogic Server will reject descriptors that do
not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-eventengine-ejb.jar/META-INF/ejb-jar.xml. A version
attribute is required, but this version of the Weblogic Server will assume that
the JEE5 is used. Future versions of the Weblogic Server will reject descriptors
that do not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-reportcache-ejb.jar/META-INF/ejb-jar.xml. A version
attribute is required, but this version of the Weblogic Server will assume that
the JEE5 is used. Future versions of the Weblogic Server will reject descriptors
that do not specify the JEE version.>
<Mar 8, 2012 12:33:52 PM EST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-
26024> <Registration of driver Email-Driver did not complete; will retry periodi
cally until messaging server responds.>This is what I see in the diagnostic log
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> And this is what I see in the log
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048125> <BEA-149059> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014021> <The EJB 'BamAdcServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-adc-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014022> <******** oracle.bam.adc.ejb.BamAdcServerRemote is bound with JNDI name:BamAdcServerBean#oracle.bam.adc.ejb.BamAdcServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-adc-ejb_jarBamAdcServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149060> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149059> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> Any help is appreciated.
Thanks -
Node Manager not starting UCM Server automatically
Hi All,
I have configured Node Manager to start and stop UCM 11g server.
But whenever, I am restarting the host OS - Windows server 2003 64 bit, it does not start the UCM managed server, automatically.
I am running two managed servers on the same host OS, the first UCM manages server, starts automatically on every restart.
The second managed UCM server, does not start. I need to then manually start the managed server. There are no errors logged, and the manual start of the managed server happens without any issues.
As a workaround, I tried starting the managed server from Windows scheduler, but it does not start the server as well. I wrote a script like -
Myscript.cmd
call E:\..\user_projects\domains\prod_domain\bin\setDomainEnv.cmd
java weblogic.WLST c:\start....\ServerStart.py
scheduled the script (myscript.cmd) to run from the Windows Scheduler.
Any pointers would be very helpful. Are there any known issues, if there are two managed servers, and one starts automatically, which affects the starting of the second managed server?
I see the following error in the log file -
<14/10/2011 6:35:22 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<14/10/2011 6:35:33 PM EST> <Info> <Management> <BEA-141223> <The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.>
<14/10/2011 6:35:33 PM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:71)
Regards
AviHi Avi,
Give a cross check to your ServerStart.py
As the error states The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist
In your ServerStart.py you might have specified as follows
sh start MAnagedWeblogic.sh server=PRD_UCM_Server1
While these are the list of Server you have in your weblogic
PRDAdminServer,
PRD_UCM_server1,(You have Specified in your command PRD_UCM_Server1
PRD_IBR_server1
The Command should be as follows
sh start ManagedWeblogic.sh server=PRD_UCM_server1
This should help
Regards
Fabian -
Node Manager installed as service does not start managed servers. WLS 10.3
Hi All,
I have installed the node manager as a windows service. When the service starts up it does start the managed servers.
In the nodemanager.log file it shows that the node manager is reading the startup.properties file for all of the managed servers.
<Jul 24, 2009 6:38:13 AM> <INFO> <Loading domains file: C:\bea\WLSERV~1.3\common\NODEMA~1\nodemanager.domains>
<Jul 24, 2009 6:38:13 AM> <INFO> <Loaded node manager configuration properties from 'C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.properties'>
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <IntegrationServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\IntegrationServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <ProdBackupServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\ProdBackupServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <QAServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\QAServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <INFO> <Plain socket listener started on port 5556, host localhost>
The node manager properties file contains the following
#Mon Apr 20 10:54:45 PDT 2009
DomainsFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
JavaHome=C\:\\bea\\JROCKI~1
AuthenticationEnabled=false
NodeManagerHome=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1
LogLevel=INFO
DomainsFileEnabled=true
StartScriptEnabled=false
StartScriptName=startWebLogic.cmd
ListenAddress=localhost
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=true
LogFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
The managed servers' boot.properties file and startup file are below
boot.properties:
#Thu Jul 23 13:48:26 PDT 2009
CustomTrustKeyStoreFileName=C\:\\bea\\wlserver_10.3\\common\\ssl\\supportTrust2008.jks
TrustKeyStore=CustomTrust
password={3DES}mvtUK8oB8JEiQoVES4AQIQ\=\=
CustomTrustKeyStorePassPhrase={3DES}34+15HRlP6qqpZX3bTPp+Q\=\=
CustomTrustKeyStoreType=JKS
username={3DES}P5mMHiWLnf2UtssZbQtezkDtIS0COiHW
startup.properties:
#Server startup properties
#Thu Jul 23 13:48:27 PDT 2009
Arguments=-Xms1024m -Xmx1024m -Xnohup
JavaHome=C\:\\bea\\jrockit_160_05
SSLArguments=-Dweblogic.security.SSL.ignoreHostnameVerification\=false -Dweblogic.ReverseDNSAllowed\=false
RestartMax=2
RestartDelaySeconds=0
RestartInterval=3600
BeaHome=C\:\\bea
ClassPath=C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\lib\\itext\\WEB-INF\\lib\\itext.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic_sp.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic.jar;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\massmutual\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\assuritylife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\minnesotalife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\lib\\ltclibrary\\WEB-INF\\classes\\
AdminURL=http\://localhost\:7001
JavaVendor=BEA
AutoRestart=true
AutoKillIfFailed=false
I am wondering if I left out a parameter some where.
Any help would be greatly appreciated.
Thanks,
GregFirst of all, I assume you mean "... up it does NOT start ..."?
It might be helpful to point out that the purpose of the NodeManager is not to start the servers, but to "control" the servers through remote commands. When the NodeManager starts back up, it tries to reset the servers to the last known state it set them to, based on remote commands.
For instance, if your system was running and you stopped the servers through the admin console and then restarted the machine, the NodeManager would not start the servers on machine startup, because the last controlled state of the servers was down. If all of your WebLogic servers were running as a result of NodeManager commands, and you pulled the plug on the box, when you restarted the machine, the NodeManager probably would restart the servers.
Maybe you are looking for
-
Airport Extreme Sharing printer to Leopard and Windows 7 via Ethernet port.
Hello! My home office is in a mixed environment, 1 iMac with Leopard 10.5.8, and the other iMac running Windows 7 Ultimate x64 on bootcamp. Both computers are connected to the Airport Extreme (dual band version, firmware 7.4.2) via Ethernet. I attach
-
I got my hands on a MacBook A1181 (3,1) and I was wondering what is the maximum amount of RAM I can put in it, and can I put in a 500GB hard drive? Some people say 2 GB some say 4GB, and do i need to get a specific hard drive from Apple or can I just
-
We are getting the following error in our NT event logs on a regular basis - and at the same time as some other problems we are having. What does this mean, and is there a fix for it?? The Open Procedure for service "https4.1" in DLL "e:\Netscape\Ser
-
Problem integrating JSF with Spring
Here is faces-config.xml <application> <el-resolver>org.springframework.web.jsf.el.SpringBeanFacesELResolver</el-resolver> </application> <managed-bean> <managed-bean-name>dateuser</managed-bean-name> <managed-bean-class>com.datesite.user.DateUser</m
-
hi all i recently upgraded my speakers to creative 6700 6. system and when i play a track with lots of base and turn the volume up past a certain level the sound kinda of cuts out or distorts for a split second every time there is a drum beat or some