Large Cluster Waits 11g
We have a 3 node RAC system with AIX machines.
We have been seeing an issue with Cluster Waits.
Example: run a query it can take 10 sec. sometimes and then 200 secs another time.
(we get the same explain plan and hash plan) . The 200 sec query has large Cluster waits. 38 to 45%
In gerneral what could be causing those cluster waits?
Hi,
bgeiss wrote:
We have a 3 node RAC system with AIX machines.
We have been seeing an issue with Cluster Waits.
Example: run a query it can take 10 sec. sometimes and then 200 secs another time.Generating Automatic Workload Repository Reports> (we get the same explain plan and hash plan) . The 200 sec query has large Cluster waits. 38 to 45%
>
In gerneral what could be causing those cluster waits?
How is the health of your cluster?
http://download.oracle.com/docs/cd/E11882_01/server.112/e16638/autostat.htm#PFGRF02601
Generating an Oracle RAC AWR Report
http://download.oracle.com/docs/cd/E11882_01/server.112/e16638/autostat.htm#CHDCFBJC
Post here Report of AWR when you run the query.
Please format your report.
When you post code/report/query, or any formatted text, on this site, type these 6 characters:
(small letters only, inside curly brackets) before and after sections of formatted text, to preserve spacing.
Regards,
Levi Pereira
Edited by: Levi Pereira on Aug 17, 2011 2:11 PM
Edited by: Levi Pereira on Aug 17, 2011 2:12 PM
Similar Messages
-
Best practice for using messaging in medium to large cluster
What is the best practice for using messaging in medium to large cluster In a system where all the clients need to receive all the messages and some of the messages can be really big (a few megabytes and maybe more)
I will be glad to hear any suggestion or to learn from others experience.
Shimipublish/subscribe, right?
lots of subscribers, big messages == lots of network traffic.
it's a wide open question, no?
% -
AWR SQL ordered by Cluster Wait Time
I am beginner in Oracle Performance issue, I am working on sql query which appear on the top of queries list in the section SQL ordered by Cluster Wait Time
have any one an explanation for this ?
Thanks,
Edited by: BIJGA on 19 sept. 2011 09:44====================SQL ordered by Elapsed Time
Elapsed Time (s) Executions Elapsed Time per Exec (s) %Total %CPU %IO SQL Id SQL Module SQL Text
1,769.05 2 884.53 3.51 64.30 35.91 acgncjwd5hmjc MYPROG BEGIN MY_PROC (15400...
==============================SQL ordered by Cluster Wait Time
Cluster Wait Time (s) Executions %Total Elapsed Time(s) %Clu %CPU %IO SQL Id SQL Module SQL Text
33.60 12 3.78 888.29 25.96 35.07 61.61 284532152m5up MYPROG SELECT 1 FROM MYTABLE L WHERE (..
Remrak the query 284532152m5up was executed by
OPEN myLock for SELECT 1 FROM MYTABLE L WHERE... for update;
close myLock;
Thanks, -
10.1.0.3
Solaris 5.1
Veritas Active/Passive cluster.
Single Instance. NON-RAC environment.
Does anyone know how to track down cluster wait events in an active/passive wait situation? All instances on are 1 of 2 nodes. We use the clustering for active/passive failover.Hi,
How cluster wait event comes in to picture as you are using only one node as Active. It comes in to account for RAC system running ACTIVE/ACTIVE on cluster? I am not sure why you are concerned on ACTIVE/Passive cluster with all database running only on one node.
Regards -
Converting 8 node to 4 node caused CLUSTER waits
Hi,
We had an 8 node 10.2.0.3 cluster which was working fine. For some reasons, we reinstalled the cluster with 4 nodes (fresh OSs, but everything was same). we mounted the previous asm diskgroups with the new cluster. Everything seems to be working fine, except we have lots of waits on cluster class, mostly gc cr block busy. Does anyone have any idea about that?
thanksAWR says a few sql statements causing the cluster waits, but these are not new queries. On the 8 node cluster we had the same sql queries, but we rarely had CLUSTER waits.Not Sure about nodes to 4 nodes.
But I think we need to investigate and improve from that query before.
check Top 5 Timed Events, Wait Events, objects, indexes , gather stats, block size and etc...
Good Luck -
Weblogic - Fusion Middleware Cluster - Clarification - 11g
Hello All,
I've checked the forum and would need just a little clarification regarding weblogic cluster & fusion Middleware + Load Balancing.
My current Setup is:
==============
1 APP Server: Runs Fusion Middleware 11g Forms and Reports + Weblogic + OHS (windows 2008R2)
1 DB Server: Standalone database 11gR2 installation (windows 2008R2)
I've been asked to add a new app server and setup load balancing between the two app servers in order to split the incoming forms & reports requests.
What do I do? Do I install the new app server like the first one and just add it to an existing domain(clustering)? Is there a difference between fusion middleware clustering and weblogic clustering (as in database RAC - the whole idea being failover 24/7 no single point of failure?)
I would appreciate any assistance, and need not great detail, just need to make sense of the whole thing.
I'm already on with the following document: [http://docs.oracle.com/cd/E21764_01/web.1111/e13709/toc.htm]
Thanks in advance
Jan S.Hi Jan
You are almost there. I would like to clarify some points for you.
1. You already have WLS + Forms/Reports and of course Backend RCU Database that has all the meta data for Forms/Reports. This RCU database is on single server Oracle database.
I've been asked to add a new app server and setup load balancing between the two app servers in order to split the incoming forms & reports requests.
2. The first question for above requirement is, do you need the new Server on the same Existing physical box or a different remote physical box. If on the same physical box (which I doubt), then there is NO need to install any new software like WLS, Forms/Reports etc. All you do is create a new Managed Server and add it to your existing Domain. NOW, do you currently have a Clustered Domain. If you, all you do is add this new server to that cluster. If not, then you need to add a New cluster and add your old and this NEW managed server to that Cluster. If your existing domain is only single server and is very recent, I would prefer create a brand new Cluster domain with Different Port numbers (you can change port numbers anytime later also). Then add/create one or two managed servers.
3. If you are give a new physical box for this new managed server, then YES, you do need to install exactly SAME version of Weblogic Server and same version of Forms/Reports server on this new machine. Then create a Cluster Domain with 2 managed servers. One managed server on first box where you will have Admin Server + Managed Server 1. Then run pack command. Go to other machine. Run unpack command to create second Managed Server. Now you got 2 managed servers in a Single Clustered Domain.
4. Now comes the Load Balancing Part. Never ever expose the individual managed server host and port and WebApp urls for any Clustered Domain. Instead install Apache Http Web App Server which I guess is same as Oracle Http Server. Oracle renamed it (there is no need for this, but it may be company policy). Anyhow all you do is, just install Apache Web Server. Copy some .dll (.so on linux) files to this apache installation. Then update httpd.conf file or weblogic.conf file with details of clustered weblogic domain managed servers host, port, url patterns etc.
5. All the External Requests will now go to Apache Web Server like http://apachehost:apacheport/xxxUrl. This Apache will take care of LOAD Balancing, Failover etc and based on input url pattern will redirect requests to back end cluster of weblogic managed servers.
6. The backend RCU database that has Metadata for Forms/Reports NEED NOT be Clustered. If you really have extremely heavy data, then you can have Oracle RAC database. Have multiple DB Nodes in RAC. For each Node, create a DataSource in Weblogic conolse and finally one master Multi Data Soiurce that uses all these single Datasources. But very rarely you really need RAC or clustered database for RCU. So for now, just go with single non-clustered Database that has RCU Schemas.
In conclusion, even though you have Forms/Reports, just follow the standard normal Weblogic Clustered domain Architecture for your requirement. All clustering is at application server level and nothing to do with any Oracles softwares like SOA/BPM, Forms/Report, BI etc etc.
Thanks
Ravi Jegga -
Hi All,
In 10g
stop cluster in local node
option 1. crsctl stop crs
alternatively
option 2. srvctl stop instance
srvctl stop asm
srvctl stop nodeapps
srvctl stop crs
same with starting the resources
option 1. crsctl start crs
alternatively
option 2. srvctl start nodeapps
srvctl start asm
srvctl start instance
crsctl start crs
is there any difference if i stop all resources in a go or if i stop using second option lot of options all work but slight doubt which of these are oracle
prescribed
And in 11g since OCR and Voting disk on ASM
./crsctl stop cluster -all --- to stop everything in all nodes or
crsctl stop cluster -n node1 or
./crsctl stop has on single node
option 2 - I am not aware of option 2
can any one enlighten me on these...Hello! I hope my experience will be helpful.
In order to get a graceful shutdown of the databases in my cluster, I first stop the databases using the srvctl stop database command. Once the database has been shutdown properly, and is shown to be in OFFLINE state, then I use "crsctl stop cluster" command to stop the other cluster processes. Finally, I use "crsctl stop crs" command to shutdown High Availability services. I issue the "crsctl" commands on each individual cluster node, because I am not a big fan of the "-all" option to shut things down.
I hope this helps you!
Thanks and Best Wishes,
Mark -
I believe by default cluster size is limited to 436 members by default. We would like to increase this to about 550 temporarily. Can someone remind me of the setting to do this? Any critical drawbacks (I know its no ideal). Thanks in advance... Andrew.
There was some changes made in in some 3.7.1.x release to support large clusters. Previous there was some issues with the preferred MTU, which was 64K causing OOM in the Publisher/Receiver.
-
How manager phone numbers in large cluster
hiï¼all
I want to know in large CUCM clusters(10000+ phones) how to manager the user's phone numbers?Any product help this job?I'm rellay confused.If you want to use a provisioning tool to help manage this (likely the easiest route), then you can check out various offerings from 3rd-party vendors such as 2Ring's MACC, CUPM (Cisco Unified Provisioning Manager), and even vendors like Mitel have products that help with this.
Hailey
Please rate helpful posts! -
Has anybody configured Forms/Reports as cluster in 11g patch3?
Situation:
Three OEL machines (r5u5 32 bit).
Versions: WLS 10.3.3, Forms/reports 11.1.1.2 with patchset 11.1.1.3.
On the first machine I successfully installed the admin server and the first instances of the forms and reports managed servers.
On the second machine I successfully expanded the cluster from the first machine. All managed servers can be brought up and are working
Problem:
When installing the third machine, the same way as I did the second machine, the config process, remains in the state "in progress" on the step "starting managed server WLS_FORMS2" and several retries to start the managed server ... fail, ending in a failure of the installation.
Tests so far:
Hostname is underscoreless ... yes ;-)
The http and webcache are installed with it, first I did a trial with not selecting them.
Question:
It seems to me not a lot of environments are running forms in a WLS cluster and I can nowhere find info on what might be the problem. Has anybody done this kind of an environment yet (installation of forms in clustered mode) ? and/or encountered the same kind of problems ... ?Have a look here it describes the step by step install:
http://www.formsmigration.com/wls_install.html
Then this covers the patch up to 11.1.1.3:
http://www.formsmigration.com/wls_patch_to_1033.html
You seem to be installing the weblogic server 10.3.4 and then the forms and reports 11.1.1.2. I think that this is an incompatible combination, and you need to install weblogic server 10.3.2 with that version of forms and reports. Y9ou can then patch up to newer versions afterwards.
cheers
Tony -
How to design a large cluster to cache 1 TB of data?
I am evaluating Coherence to cache large amount of transactional data in the grid, in the order of 1TB.
- Are there customers who have successfully cached such amount of data for improving performance of reads and writes? What is the configuration of the infrastructure - how many nodes/hosts? What quality and types of hardware are recommended for such grids?
- What are the considerations for using large JVMs (10GB per node)? I understand we will be able allocate large memory per node using partitioned backing and NIO buffers from 3.5. Is this recommended for my cache of 1 TB? What are the sizing considerations for using such heaps?
Please share your inputs on architecture
Regards,
SairamIt is very hard to give fixed rules for how many JVMs to run per physical server or how large heaps you can use!
The number of JVMs per server does for instance depend on how many service threads you intend to use for each cache node. If you do not intend to have a cache store (used to sync to database) and no cache queries are likely to be long runing you can first try to set the number of service threads to zero (causing all requests to be performed directly by the receiving thread without any hand-off). With this configuration you may get away with more than one JVM per core. If you on the other hand intend to run a mix of quick and more long runing queries and cant accept that a long runing one will block all other requests you may want to use a thread pool of service threads in each JVM and in this case you may want to run just one or perhaps two JVMs per quad core CPU...
When it comes to heaps size this is almost totally application dependent. I know of telecom applications (soft real-time!) that can run with 6 Gb heap using the concurrent collector while other applications I have been involved with get to long pauses with even under 1Gb of heap! You need to test with you own mix of use-cases and tune from there. In some cases you actually get shorter pauses with a larger heap (if you use the extra space to make the young generation larger it will result in less frequent young generation GC that in turn may result in more temporary data becoming unreferenced and efficiently de-allocated instead of geting promoted to the other generations) so tuning this require some "thinkering"... I would start with a 2Gb heaps size and if that works try to increase it from there... Remember to check out the new options to use compressed pointers (compressed oops) in newer 64-bit Sun JVMs!
If using off-heap data storage (with close to zero effect on the heap) and you need a lot of indexes for your queries (that together with the primary key must be located on the heap) this may cap how much data each JVM can handle! Also note that even if using a overflow map it would not protect you against the heap to fill up with key and index data so this is always an issue at some point!
The theorethical size of the splitting off-heap backing map is 2Gb per partition (but I think I have read in the forum some where that there is a lower actua llimit) but you can probably make use of 32-64 gig of off-heap memory per JVM...
You must of course also consider the amount of processing needed per server - that may limit how few servers you can get away with - no matter how much memory you can put in them...
/Magnus
Edited by: MagnusE on Mar 1, 2010 9:51 AM -
Hi there!
I am working on the design of a cluster that will support more than 200 databases with smalls SGAs, my question is, which are the considerations to keep in mind knowing that many databases implies greater amount of interconnect traffic. If anyone has experience running over 100 databases on the Oracle Clusterware please share your experience, good or bad, unfotunately found no documents explaining which are the guidelines or best practices to implement a cluster with these characteristics. Workload design recommendations are welcome.
Thanks in advance.
Jhi,
this is not direct answer but gives some idea
http://www.dba-oracle.com/t_optimal_number_rac_nodes.htm
I think that tuning in this case will be reactive rather than proactive, having set some rough boundaries as there are many variables/Dbs. -
RAC 9i to 11g 3 node cluster upgradation.
Hi,
I have been given the requirement to migrate a 9i RAC 3 node database( 9i cluster) to 11g R2 RAC database iam looking for a document or steps to do this activity. any help on this is highly appreciated.
should I upgrade the cluster first and then upgrade each node one by one or I should upgrade the cluster and upgrade all the home in one go ?
Thanks,
Satish Abraham.Jhi,
you may want to take look this first:
Upgrade 9i to 11gR2 -
Active session Spike on Oracle RAC 11G R2 on HP UX
Dear Experts,
We need urgent help please, as we are facing very low performance in production database.
We are having oracle 11G RAC on HP Unix environment. Following is the ADDM report. Kindly check and please help me to figure it out the issue and resolve it at earliest.
---------Instance 1---------------
ADDM Report for Task 'TASK_36650'
Analysis Period
AWR snapshot range from 11634 to 11636.
Time period starts at 21-JUL-13 07.00.03 PM
Time period ends at 21-JUL-13 09.00.49 PM
Analysis Target
Database 'MCMSDRAC' with DB ID 2894940361.
Database version 11.2.0.1.0.
ADDM performed an analysis of instance mcmsdrac1, numbered 1 and hosted at
mcmsdbl1.
Activity During the Analysis Period
Total database time was 38466 seconds.
The average number of active sessions was 5.31.
Summary of Findings
Description Active Sessions Recommendations
Percent of Activity
1 CPU Usage 1.44 | 27.08 1
2 Interconnect Latency .07 | 1.33 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Findings and Recommendations
Finding 1: CPU Usage
Impact is 1.44 active sessions, 27.08% of total activity.
Host CPU was a bottleneck and the instance was consuming 99% of the host CPU.
All wait times will be inflated by wait for CPU.
Host CPU consumption was 99%.
Recommendation 1: Host Configuration
Estimated benefit is 1.44 active sessions, 27.08% of total activity.
Action
Consider adding more CPUs to the host or adding instances serving the
database on other hosts.
Action
Session CPU consumption was throttled by the Oracle Resource Manager.
Consider revising the resource plan that was active during the analysis
period.
Finding 2: Interconnect Latency
Impact is .07 active sessions, 1.33% of total activity.
Higher than expected latency of the cluster interconnect was responsible for
significant database time on this instance.
The instance was consuming 110 kilo bits per second of interconnect bandwidth.
20% of this interconnect bandwidth was used for global cache messaging, 21%
for parallel query messaging and 7% for database lock management.
The average latency for 8K interconnect messages was 42153 microseconds.
The instance is using the private interconnect device "lan2" with IP address
172.16.200.71 and source "Oracle Cluster Repository".
The device "lan2" was used for 100% of interconnect traffic and experienced 0
send or receive errors during the analysis period.
Recommendation 1: Host Configuration
Estimated benefit is .07 active sessions, 1.33% of total activity.
Action
Investigate cause of high network interconnect latency between database
instances. Oracle's recommended solution is to use a high speed
dedicated network.
Action
Check the configuration of the cluster interconnect. Check OS setup like
adapter setting, firmware and driver release. Check that the OS's socket
receive buffers are large enough to store an entire multiblock read. The
value of parameter "db_file_multiblock_read_count" may be decreased as a
workaround.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Additional Information
Miscellaneous Information
Wait class "Application" was not consuming significant database time.
Wait class "Cluster" was not consuming significant database time.
Wait class "Commit" was not consuming significant database time.
Wait class "Concurrency" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Wait class "User I/O" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
Hard parsing of SQL statements was not consuming significant database time.
The database's maintenance windows were active during 100% of the analysis
period.
----------------Instance 2 --------------------
ADDM Report for Task 'TASK_36652'
Analysis Period
AWR snapshot range from 11634 to 11636.
Time period starts at 21-JUL-13 07.00.03 PM
Time period ends at 21-JUL-13 09.00.49 PM
Analysis Target
Database 'MCMSDRAC' with DB ID 2894940361.
Database version 11.2.0.1.0.
ADDM performed an analysis of instance mcmsdrac2, numbered 2 and hosted at
mcmsdbl2.
Activity During the Analysis Period
Total database time was 2898 seconds.
The average number of active sessions was .4.
Summary of Findings
Description Active Sessions Recommendations
Percent of Activity
1 Top SQL Statements .11 | 27.65 5
2 Interconnect Latency .1 | 24.15 1
3 Shared Pool Latches .09 | 22.42 1
4 PL/SQL Execution .06 | 14.39 2
5 Unusual "Other" Wait Event .03 | 8.73 4
6 Unusual "Other" Wait Event .03 | 6.42 3
7 Unusual "Other" Wait Event .03 | 6.29 6
8 Hard Parse .02 | 5.5 0
9 Soft Parse .02 | 3.86 2
10 Unusual "Other" Wait Event .01 | 3.75 4
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Findings and Recommendations
Finding 1: Top SQL Statements
Impact is .11 active sessions, 27.65% of total activity.
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.
Recommendation 1: SQL Tuning
Estimated benefit is .05 active sessions, 12.88% of total activity.
Action
Investigate the PL/SQL statement with SQL_ID "d1s02myktu19h" for
possible performance improvements. You can supplement the information
given here with an ASH report for this SQL_ID.
Related Object
SQL statement with SQL_ID d1s02myktu19h.
begin dbms_utility.validate(:1,:2,:3,:4); end;
Rationale
The SQL Tuning Advisor cannot operate on PL/SQL statements.
Rationale
Database time for this SQL was divided as follows: 13% for SQL
execution, 2% for parsing, 85% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "d1s02myktu19h" was executed 48 times and had
an average elapsed time of 7 seconds.
Rationale
Waiting for event "library cache pin" in wait class "Concurrency"
accounted for 70% of the database time spent in processing the SQL
statement with SQL_ID "d1s02myktu19h".
Rationale
Top level calls to execute the PL/SQL statement with SQL_ID
"63wt8yna5umd6" are responsible for 100% of the database time spent on
the PL/SQL statement with SQL_ID "d1s02myktu19h".
Related Object
SQL statement with SQL_ID 63wt8yna5umd6.
begin DBMS_UTILITY.COMPILE_SCHEMA( 'TPAUSER', FALSE ); end;
Recommendation 2: SQL Tuning
Estimated benefit is .02 active sessions, 4.55% of total activity.
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"fk3bh3t41101x".
Related Object
SQL statement with SQL_ID fk3bh3t41101x.
SELECT MEM.MEMBER_CODE ,MEM.E_NAME,Pol.Policy_no
,pol.date_from,pol.date_to,POL.E_NAME,MEM.SEX,(SYSDATE-MEM.BIRTH_DATE
) AGE,POL.SCHEME_NO FROM TPAUSER.MEMBERS MEM,TPAUSER.POLICY POL WHERE
POL.QUOTATION_NO=MEM.QUOTATION_NO AND POL.BRANCH_CODE=MEM.BRANCH_CODE
and endt_no=(select max(endt_no) from tpauser.members mm where
mm.member_code=mem.member_code AND mm.QUOTATION_NO=MEM.QUOTATION_NO)
and member_code like '%' || nvl(:1,null) ||'%' ORDER BY MEMBER_CODE
Rationale
The SQL spent 92% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "fk3bh3t41101x" was executed 14 times and had
an average elapsed time of 4.9 seconds.
Rationale
At least one execution of the statement ran in parallel.
Recommendation 3: SQL Tuning
Estimated benefit is .02 active sessions, 3.79% of total activity.
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"7mhjbjg9ntqf5".
Related Object
SQL statement with SQL_ID 7mhjbjg9ntqf5.
SELECT SUM(CNT) FROM (SELECT COUNT(PROC_CODE) CNT FROM
TPAUSER.TORBINY_PROCEDURE WHERE BRANCH_CODE = :B6 AND QUOTATION_NO =
:B5 AND CLASS_NO = :B4 AND OPTION_NO = :B3 AND PR_EFFECTIVE_DATE<=
:B2 AND PROC_CODE = :B1 UNION SELECT COUNT(MED_CODE) CNT FROM
TPAUSER.TORBINY_MEDICINE WHERE BRANCH_CODE = :B6 AND QUOTATION_NO =
:B5 AND CLASS_NO = :B4 AND OPTION_NO = :B3 AND M_EFFECTIVE_DATE<= :B2
AND MED_CODE = :B1 UNION SELECT COUNT(LAB_CODE) CNT FROM
TPAUSER.TORBINY_LAB WHERE BRANCH_CODE = :B6 AND QUOTATION_NO = :B5
AND CLASS_NO = :B4 AND OPTION_NO = :B3 AND L_EFFECTIVE_DATE<= :B2 AND
LAB_CODE = :B1 )
Rationale
The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 0% for SQL execution,
0% for parsing, 100% for PL/SQL execution and 0% for Java execution.
Rationale
SQL statement with SQL_ID "7mhjbjg9ntqf5" was executed 31 times and had
an average elapsed time of 3.4 seconds.
Rationale
Top level calls to execute the SELECT statement with SQL_ID
"a11nzdnd91gsg" are responsible for 100% of the database time spent on
the SELECT statement with SQL_ID "7mhjbjg9ntqf5".
Related Object
SQL statement with SQL_ID a11nzdnd91gsg.
SELECT POLICY_NO,SCHEME_NO FROM TPAUSER.POLICY WHERE QUOTATION_NO
=:B1
Recommendation 4: SQL Tuning
Estimated benefit is .01 active sessions, 3.03% of total activity.
Action
Investigate the SELECT statement with SQL_ID "4uqs4jt7aca5s" for
possible performance improvements. You can supplement the information
given here with an ASH report for this SQL_ID.
Related Object
SQL statement with SQL_ID 4uqs4jt7aca5s.
SELECT DISTINCT USER_ID FROM GV$SESSION, USERS WHERE UPPER (USERNAME)
= UPPER (USER_ID) AND USERS.APPROVAL_CLAIM='VC' AND USER_ID=:B1
Rationale
The SQL spent only 0% of its database time on CPU, I/O and Cluster
waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
Look at performance data for the SQL to find potential improvements.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "4uqs4jt7aca5s" was executed 261 times and had
an average elapsed time of 0.35 seconds.
Rationale
At least one execution of the statement ran in parallel.
Rationale
Top level calls to execute the PL/SQL statement with SQL_ID
"91vt043t78460" are responsible for 100% of the database time spent on
the SELECT statement with SQL_ID "4uqs4jt7aca5s".
Related Object
SQL statement with SQL_ID 91vt043t78460.
begin TPAUSER.RECEIVE_NEW_FAX_APRROVAL(:V00001,:V00002,:V00003,:V0000
4); end;
Recommendation 5: SQL Tuning
Estimated benefit is .01 active sessions, 3.03% of total activity.
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"7kt28fkc0yn5f".
Related Object
SQL statement with SQL_ID 7kt28fkc0yn5f.
SELECT COUNT(*) FROM TPAUSER.APPROVAL_MASTER WHERE APPROVAL_STATUS IS
NULL AND (UPPER(CODED) = UPPER(:B1 ) OR UPPER(PROCESSED_BY) =
UPPER(:B1 ))
Rationale
The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "7kt28fkc0yn5f" was executed 1034 times and
had an average elapsed time of 0.063 seconds.
Rationale
Top level calls to execute the PL/SQL statement with SQL_ID
"91vt043t78460" are responsible for 100% of the database time spent on
the SELECT statement with SQL_ID "7kt28fkc0yn5f".
Related Object
SQL statement with SQL_ID 91vt043t78460.
begin TPAUSER.RECEIVE_NEW_FAX_APRROVAL(:V00001,:V00002,:V00003,:V0000
4); end;
Finding 2: Interconnect Latency
Impact is .1 active sessions, 24.15% of total activity.
Higher than expected latency of the cluster interconnect was responsible for
significant database time on this instance.
The instance was consuming 128 kilo bits per second of interconnect bandwidth.
17% of this interconnect bandwidth was used for global cache messaging, 6% for
parallel query messaging and 8% for database lock management.
The average latency for 8K interconnect messages was 41863 microseconds.
The instance is using the private interconnect device "lan2" with IP address
172.16.200.72 and source "Oracle Cluster Repository".
The device "lan2" was used for 100% of interconnect traffic and experienced 0
send or receive errors during the analysis period.
Recommendation 1: Host Configuration
Estimated benefit is .1 active sessions, 24.15% of total activity.
Action
Investigate cause of high network interconnect latency between database
instances. Oracle's recommended solution is to use a high speed
dedicated network.
Action
Check the configuration of the cluster interconnect. Check OS setup like
adapter setting, firmware and driver release. Check that the OS's socket
receive buffers are large enough to store an entire multiblock read. The
value of parameter "db_file_multiblock_read_count" may be decreased as a
workaround.
Symptoms That Led to the Finding:
Inter-instance messaging was consuming significant database time on this
instance.
Impact is .06 active sessions, 14.23% of total activity.
Wait class "Cluster" was consuming significant database time.
Impact is .06 active sessions, 14.23% of total activity.
Finding 3: Shared Pool Latches
Impact is .09 active sessions, 22.42% of total activity.
Contention for latches related to the shared pool was consuming significant
database time.
Waits for "library cache lock" amounted to 5% of database time.
Waits for "library cache pin" amounted to 17% of database time.
Recommendation 1: Application Analysis
Estimated benefit is .09 active sessions, 22.42% of total activity.
Action
Investigate the cause for latch contention using the given blocking
sessions or modules.
Rationale
The session with ID 17 and serial number 15595 in instance number 1 was
the blocking session responsible for 34% of this recommendation's
benefit.
Symptoms That Led to the Finding:
Wait class "Concurrency" was consuming significant database time.
Impact is .1 active sessions, 24.96% of total activity.
Finding 4: PL/SQL Execution
Impact is .06 active sessions, 14.39% of total activity.
PL/SQL execution consumed significant database time.
Recommendation 1: SQL Tuning
Estimated benefit is .05 active sessions, 12.5% of total activity.
Action
Tune the entry point PL/SQL "SYS.DBMS_UTILITY.COMPILE_SCHEMA" of type
"PACKAGE" and ID 6019. Refer to the PL/SQL documentation for addition
information.
Rationale
318 seconds spent in executing PL/SQL "SYS.DBMS_UTILITY.VALIDATE#2" of
type "PACKAGE" and ID 6019.
Recommendation 2: SQL Tuning
Estimated benefit is .01 active sessions, 1.89% of total activity.
Action
Tune the entry point PL/SQL
"SYSMAN.EMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS" of type "PACKAGE" and
ID 68654. Refer to the PL/SQL documentation for addition information.
Finding 5: Unusual "Other" Wait Event
Impact is .03 active sessions, 8.73% of total activity.
Wait event "DFS lock handle" in wait class "Other" was consuming significant
database time.
Recommendation 1: Application Analysis
Estimated benefit is .03 active sessions, 8.73% of total activity.
Action
Investigate the cause for high "DFS lock handle" waits. Refer to
Oracle's "Database Reference" for the description of this wait event.
Recommendation 2: Application Analysis
Estimated benefit is .03 active sessions, 8.27% of total activity.
Action
Investigate the cause for high "DFS lock handle" waits in Service
"mcmsdrac".
Recommendation 3: Application Analysis
Estimated benefit is .02 active sessions, 5.05% of total activity.
Action
Investigate the cause for high "DFS lock handle" waits in Module "TOAD
9.7.2.5".
Recommendation 4: Application Analysis
Estimated benefit is .01 active sessions, 3.21% of total activity.
Action
Investigate the cause for high "DFS lock handle" waits in Module
"toad.exe".
Symptoms That Led to the Finding:
Wait class "Other" was consuming significant database time.
Impact is .15 active sessions, 38.29% of total activity.
Finding 6: Unusual "Other" Wait Event
Impact is .03 active sessions, 6.42% of total activity.
Wait event "reliable message" in wait class "Other" was consuming significant
database time.
Recommendation 1: Application Analysis
Estimated benefit is .03 active sessions, 6.42% of total activity.
Action
Investigate the cause for high "reliable message" waits. Refer to
Oracle's "Database Reference" for the description of this wait event.
Recommendation 2: Application Analysis
Estimated benefit is .03 active sessions, 6.42% of total activity.
Action
Investigate the cause for high "reliable message" waits in Service
"mcmsdrac".
Recommendation 3: Application Analysis
Estimated benefit is .02 active sessions, 4.13% of total activity.
Action
Investigate the cause for high "reliable message" waits in Module "TOAD
9.7.2.5".
Symptoms That Led to the Finding:
Wait class "Other" was consuming significant database time.
Impact is .15 active sessions, 38.29% of total activity.
Finding 7: Unusual "Other" Wait Event
Impact is .03 active sessions, 6.29% of total activity.
Wait event "enq: PS - contention" in wait class "Other" was consuming
significant database time.
Recommendation 1: Application Analysis
Estimated benefit is .03 active sessions, 6.29% of total activity.
Action
Investigate the cause for high "enq: PS - contention" waits. Refer to
Oracle's "Database Reference" for the description of this wait event.
Recommendation 2: Application Analysis
Estimated benefit is .02 active sessions, 6.02% of total activity.
Action
Investigate the cause for high "enq: PS - contention" waits in Service
"mcmsdrac".
Recommendation 3: Application Analysis
Estimated benefit is .02 active sessions, 4.93% of total activity.
Action
Investigate the cause for high "enq: PS - contention" waits with
P1,P2,P3 ("name|mode, instance, slave ID") values "1347616774", "1" and
"3599" respectively.
Recommendation 4: Application Analysis
Estimated benefit is .01 active sessions, 2.74% of total activity.
Action
Investigate the cause for high "enq: PS - contention" waits in Module
"Inbox Reader_92.exe".
Recommendation 5: Application Analysis
Estimated benefit is .01 active sessions, 2.74% of total activity.
Action
Investigate the cause for high "enq: PS - contention" waits in Module
"TOAD 9.7.2.5".
Recommendation 6: Application Analysis
Estimated benefit is .01 active sessions, 1.37% of total activity.
Action
Investigate the cause for high "enq: PS - contention" waits with
P1,P2,P3 ("name|mode, instance, slave ID") values "1347616774", "1" and
"3598" respectively.
Symptoms That Led to the Finding:
Wait class "Other" was consuming significant database time.
Impact is .15 active sessions, 38.29% of total activity.
Finding 8: Hard Parse
Impact is .02 active sessions, 5.5% of total activity.
Hard parsing of SQL statements was consuming significant database time.
Hard parses due to cursor environment mismatch were not consuming significant
database time.
Hard parsing SQL statements that encountered parse errors was not consuming
significant database time.
Hard parses due to literal usage and cursor invalidation were not consuming
significant database time.
The Oracle instance memory (SGA and PGA) was adequately sized.
No recommendations are available.
Symptoms That Led to the Finding:
Contention for latches related to the shared pool was consuming
significant database time.
Impact is .09 active sessions, 22.42% of total activity.
Wait class "Concurrency" was consuming significant database time.
Impact is .1 active sessions, 24.96% of total activity.
Finding 9: Soft Parse
Impact is .02 active sessions, 3.86% of total activity.
Soft parsing of SQL statements was consuming significant database time.
Recommendation 1: Application Analysis
Estimated benefit is .02 active sessions, 3.86% of total activity.
Action
Investigate application logic to keep open the frequently used cursors.
Note that cursors are closed by both cursor close calls and session
disconnects.
Recommendation 2: Database Configuration
Estimated benefit is .02 active sessions, 3.86% of total activity.
Action
Consider increasing the session cursor cache size by increasing the
value of parameter "session_cached_cursors".
Rationale
The value of parameter "session_cached_cursors" was "100" during the
analysis period.
Symptoms That Led to the Finding:
Contention for latches related to the shared pool was consuming
significant database time.
Impact is .09 active sessions, 22.42% of total activity.
Wait class "Concurrency" was consuming significant database time.
Impact is .1 active sessions, 24.96% of total activity.
Finding 10: Unusual "Other" Wait Event
Impact is .01 active sessions, 3.75% of total activity.
Wait event "IPC send completion sync" in wait class "Other" was consuming
significant database time.
Recommendation 1: Application Analysis
Estimated benefit is .01 active sessions, 3.75% of total activity.
Action
Investigate the cause for high "IPC send completion sync" waits. Refer
to Oracle's "Database Reference" for the description of this wait event.
Recommendation 2: Application Analysis
Estimated benefit is .01 active sessions, 3.75% of total activity.
Action
Investigate the cause for high "IPC send completion sync" waits with P1
("send count") value "1".
Recommendation 3: Application Analysis
Estimated benefit is .01 active sessions, 2.59% of total activity.
Action
Investigate the cause for high "IPC send completion sync" waits in
Service "mcmsdrac".
Recommendation 4: Application Analysis
Estimated benefit is .01 active sessions, 1.73% of total activity.
Action
Investigate the cause for high "IPC send completion sync" waits in
Module "TOAD 9.7.2.5".
Symptoms That Led to the Finding:
Wait class "Other" was consuming significant database time.
Impact is .15 active sessions, 38.29% of total activity.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Additional Information
Miscellaneous Information
Wait class "Application" was not consuming significant database time.
Wait class "Commit" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
CPU was not a bottleneck for the instance.
Wait class "Network" was not consuming significant database time.
Wait class "User I/O" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
The database's maintenance windows were active during 100% of the analysis
period.
Please help.Hello experts...
Please do the needful... It's really very urgent.
Thanks,
Syed -
JDev 11g: problems deploying webapplication to integratedWLS
Hi,
We have been developing a large application in 11g preview for some time. It is based on EJB3 and ADF Rich Faces. It worked very well in the embedded oc4j in tp4. But now when we deploy it on wls it wont deploy with following messages:
C:\Programmer\oracle\jdeveloper\system\system11.1.1.0.31.51.56\DefaultDomain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=;C:\PROGRA~1\oracle\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\PROGRA~1\oracle\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\PROGRA~1\oracle\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\PROGRA~1\oracle\JDK160~1\lib\tools.jar;C:\PROGRA~1\oracle\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\PROGRA~1\oracle\WLSERV~1.3\server\lib\weblogic.jar;C:\PROGRA~1\oracle\modules\features\weblogic.server.modules_10.3.0.0.jar;C:\PROGRA~1\oracle\WLSERV~1.3\server\lib\webservices.jar;C:\PROGRA~1\oracle\modules\ORGAPA~1.5/lib/ant-all.jar;C:\PROGRA~1\oracle\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Programmer\oracle\jdeveloper\modules\features\adf.share_11.1.1.jar;;C:\PROGRA~1\oracle\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;C:\PROGRA~1\oracle\WLSERV~1.3\server\lib\xqrl.jar;;
PATH=C:\PROGRA~1\oracle\patch_wls1030\profiles\default\native;C:\PROGRA~1\oracle\patch_jdev1111\profiles\default\native;C:\PROGRA~1\oracle\patch_cie660\profiles\default\native;C:\PROGRA~1\oracle\WLSERV~1.3\server\native\win\32;C:\PROGRA~1\oracle\WLSERV~1.3\server\bin;C:\PROGRA~1\oracle\modules\ORGAPA~1.5\bin;C:\PROGRA~1\oracle\JDK160~1\jre\bin;C:\PROGRA~1\oracle\JDK160~1\bin;C:\Programmer\oracle\db10g\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programmer\ATI Technologies\Fire GL 3D Studio Max;C:\Programmer\Subversion\bin;c:\programmer\java\jre1.6.0_06\bin;C:\Programmer\Groovy\Groovy-1.5.6\bin;C:\Programmer\Groovy\Groovy-1.5.6\bin;C:\PROGRA~1\oracle\WLSERV~1.3\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
Starting WLS with line:
C:\PROGRA~1\oracle\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Dcom.sun.management.jmxremote -DproxySet=false -Djbo.34010=false -Xverify:none -da -Dplatform.home=C:\PROGRA~1\oracle\WLSERV~1.3 -Dwls.home=C:\PROGRA~1\oracle\WLSERV~1.3\server -Dweblogic.home=C:\PROGRA~1\oracle\WLSERV~1.3\server -Ddomain.home=C:\PROGRA~1\oracle\JDEVEL~1\system\SYSTEM~1.56\DEFAUL~1 -Doracle.home=C:\Programmer\oracle\jdeveloper -Doracle.security.jps.config=C:\PROGRA~1\oracle\JDEVEL~1\system\SYSTEM~1.56\DEFAUL~1\config\oracle\jps-config.xml -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Xms1024m -Xmx1024m -XX:MaxPermSize=256m -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\PROGRA~1\oracle\patch_wls1030\profiles\default\sysext_manifest_classpath;C:\PROGRA~1\oracle\patch_jdev1111\profiles\default\sysext_manifest_classpath;C:\PROGRA~1\oracle\patch_cie660\profiles\default\sysext_manifest_classpath -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\PROGRA~1\oracle\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
<11-10-2008 23:19:48 BST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
C:\Programmer\oracle\patch_wls1030\profiles\default\sysext_manifest_classpath\weblogic_ext_patch.jar;C:\Programmer\oracle\wlserver_10.3\L10N\beehive_ja.jar;C:\Programmer\oracle\wlserver_10.3\L10N\beehive_ko.jar;C:\Programmer\oracle\wlserver_10.3\L10N\beehive_zh_CN.jar;C:\Programmer\oracle\wlserver_10.3\L10N\beehive_zh_TW.jar;C:\Programmer\oracle\wlserver_10.3\L10N\p13n_wls_ja.jar;C:\Programmer\oracle\wlserver_10.3\L10N\p13n_wls_ko.jar;C:\Programmer\oracle\wlserver_10.3\L10N\p13n_wls_zh_CN.jar;C:\Programmer\oracle\wlserver_10.3\L10N\p13n_wls_zh_TW.jar;C:\Programmer\oracle\wlserver_10.3\L10N\testclient_ja.jar;C:\Programmer\oracle\wlserver_10.3\L10N\testclient_ko.jar;C:\Programmer\oracle\wlserver_10.3\L10N\testclient_zh_CN.jar;C:\Programmer\oracle\wlserver_10.3\L10N\testclient_zh_TW.jar;C:\Programmer\oracle\wlserver_10.3\L10N\tuxedocontrol_ja.jar;C:\Programmer\oracle\wlserver_10.3\L10N\tuxedocontrol_ko.jar;C:\Programmer\oracle\wlserver_10.3\L10N\tuxedocontrol_zh_CN.jar;C:\Programmer\oracle\wlserver_10.3\L10N\tuxedocontrol_zh_TW.jar;C:\Programmer\oracle\wlserver_10.3\L10N\workshop_ja.jar;C:\Programmer\oracle\wlserver_10.3\L10N\workshop_ko.jar;C:\Programmer\oracle\wlserver_10.3\L10N\workshop_zh_CN.jar;C:\Programmer\oracle\wlserver_10.3\L10N\workshop_zh_TW.jar>
<11-10-2008 23:19:48 BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsystems Inc.>
<11-10-2008 23:19:48 BST> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for CR380042 Thu Sep 11 13:33:40 PDT 2008
WebLogic Server Temporary Patch for 7372756 Fri Sep 12 17:05:44 EDT 2008
WebLogic Server 10.3 Mon Aug 18 22:39:18 EDT 2008 1142987 >
<11-10-2008 23:19:49 BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<11-10-2008 23:19:49 BST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<11-10-2008 23:19:49 BST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Programmer\oracle\jdeveloper\system\system11.1.1.0.31.51.56\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<11-10-2008 23:19:51 BST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<11-10-2008 23:19:54 BST> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddi was not deployed. Error: [Deployer:149158]No application files exist at 'C:\PROGRA~1\oracle\WLSERV~1.3\server\lib\uddi.war'.>
<11-10-2008 23:19:54 BST> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddiexplorer was not deployed. Error: [Deployer:149158]No application files exist at 'C:\PROGRA~1\oracle\WLSERV~1.3\server\lib\uddiexplorer.war'.>
<11-10-2008 23:19:56 BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<11-10-2008 23:19:56 BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<11-10-2008 23:19:57 BST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<11-10-2008 23:19:57 BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<11-10-2008 23:19:57 BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<11-10-2008 23:19:57 BST> <Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 192.168.136.1, 192.168.68.1, 192.168.1.64, 127.0.0.1>
<11-10-2008 23:19:57 BST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.68.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<11-10-2008 23:19:57 BST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<11-10-2008 23:19:57 BST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 192.168.1.64:7101 for protocols iiop, t3, ldap, snmp, http.>
<11-10-2008 23:19:57 BST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.136.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<11-10-2008 23:19:57 BST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
<11-10-2008 23:19:57 BST> <Warning> <Server> <BEA-002611> <Hostname "fartelda-27.sam-teld.fo", maps to multiple IP addresses: 192.168.136.1, 192.168.68.1, 192.168.1.64, 127.0.0.1>
<11-10-2008 23:19:57 BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<11-10-2008 23:19:57 BST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<11-10-2008 23:19:58 BST> <Warning> <Server> <BEA-002611> <Hostname "FARTELDA-27", maps to multiple IP addresses: 192.168.136.1, 192.168.68.1, 192.168.1.64, 127.0.0.1>
DefaultServer startup time: 12203 ms.
DefaultServer started.
[Running application vitanet on Server Instance DefaultServer...]
Uploading credentials.
---- Deployment started. ---- Oct 11, 2008 11:20:01 PM
Target platform is (Weblogic 10.3).
Running dependency analysis...
2008-10-11 23:20:02.25: Writing WAR file to C:\Programmer\oracle\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\vitanet\vitanet
2008-10-11 23:20:02.484: Wrote WAR file to C:\Programmer\oracle\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\vitanet\vitanet
2008-10-11 23:20:02.593: Writing EJB JAR file to C:\Programmer\oracle\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\vitanet\vitanet-model-ejb
2008-10-11 23:20:02.75: Wrote EJB JAR file to C:\Programmer\oracle\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\vitanet\vitanet-model-ejb
2008-10-11 23:20:05.328: Writing EAR file to C:\Programmer\oracle\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\vitanet
2008-10-11 23:20:05.359: Wrote EAR file to C:\Programmer\oracle\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\vitanet
Deploying Application...
<11-10-2008 23:20:07 BST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application vitanet is not versioned.>
11-10-2008 23:20:08 oracle.as.jmx.framework.PortableMBeanFactory setJMXFrameworkProviderClass
INFO: JMX Portable Framework initialized with platform SPI "class oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl"
<11-10-2008 23:20:10 BST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1223763607515' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(vitanet-model-ejb)
weblogic.application.ModuleException: Exception preparing module: EJBModule(vitanet-model-ejb)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
Truncated. see log file for complete stacktrace
java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
at javax.xml.parsers.DocumentBuilderFactory.setSchema(DocumentBuilderFactory.java:561)
at weblogic.xml.jaxp.RegistryDocumentBuilder.setupDocumentBuilderFactory(RegistryDocumentBuilder.java:393)
at weblogic.xml.jaxp.RegistryDocumentBuilder.getDefaultDocumentBuilderFactory(RegistryDocumentBuilder.java:359)
at weblogic.xml.jaxp.RegistryDocumentBuilder.getDocumentBuilder(RegistryDocumentBuilder.java:298)
at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:150)
Truncated. see log file for complete stacktrace
>
<11-10-2008 23:20:10 BST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'vitanet'.>
<11-10-2008 23:20:10 BST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(vitanet-model-ejb)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
Truncated. see log file for complete stacktrace
java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
at javax.xml.parsers.DocumentBuilderFactory.setSchema(DocumentBuilderFactory.java:561)
at weblogic.xml.jaxp.RegistryDocumentBuilder.setupDocumentBuilderFactory(RegistryDocumentBuilder.java:393)
at weblogic.xml.jaxp.RegistryDocumentBuilder.getDefaultDocumentBuilderFactory(RegistryDocumentBuilder.java:359)
at weblogic.xml.jaxp.RegistryDocumentBuilder.getDocumentBuilder(RegistryDocumentBuilder.java:298)
at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:150)
Truncated. see log file for complete stacktrace
>
[Deployer:149034]An exception occurred for task [Deployer:149026]deploy application vitanet on DefaultServer.: Exception preparing module: EJBModule(vitanet-model-ejb)
weblogic.application.ModuleException: Exception preparing module: EJBModule(vitanet-model-ejb)
#### Deployment incomplete. #### Oct 11, 2008 11:20:10 PM
oracle.jdeveloper.deploy.DeployException
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:247)
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.deployImpl(Jsr88RemoteDeployer.java:157)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:436)
at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
at oracle.jdevimpl.runner.adrs.AdrsStarter$4$1.run(AdrsStarter.java:1316)
Caused by: oracle.jdeveloper.deploy.DeployException
at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:413)
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:238)
... 11 more
Caused by: oracle.jdeveloper.deploy.DeployException: Deployment Failed
at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:395)
... 12 more
#### Cannot run application vitanet due to error deploying to DefaultServer.
[Application vitanet stopped and undeployed from Server Instance DefaultServer]
Is there anyone that can tell me what is wrong?
JakupHi!
I don't know exactly what is the cause, but I have a troubles migrating my project also.
I would pay attention to lines:
jakup wrote:
Truncated. see log file for complete stacktrace
java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
at javax.xml.parsers.DocumentBuilderFactory.setSchema(DocumentBuilderFactory.java:561)R1 and TP4 differs in many metadata files schema versions. It looks like R1 is very sensitive on this, so when you just "migrate" TP4 project it does't upgrade the schema/version info. You have to do that manualy. Be noted that besid JDevs metadata (pageDefs, taskflows,...) this refers also to your WSDLs and other xml files you created.
You can look for another my post Anyone succeeded migrating TP4 project to R1? and see the answers there.
Anyhow, I did the migration by creating new app and adding mostly my source files and letting the IDE to recreate all metadata again...
Regards,
PaKo
Maybe you are looking for
-
K7T Turbo Limited Edition HD Max
I currently am running this setup: K7T Turbo Limited Edition Motherboard, AMD Athlon XP 1800+ 1.53 Ghz, 384MB PC-133, 27.2 GB WD, 40GB Maxtor, Gigabyte 5900XT, MSI 52x Combo, Linksys 10/100 NIC, Sound Blaster Live Audigy2 Limited Edition I have been
-
Will Mountain Lion allow the transfer of photos from iPod to iMac?
Hi I'm aware that in previous versions of OS X, one can transfer photos actually taken on an iPod touch, but not those previously sent to the ipod by ones iMac. I'm wondering if this inability has been overcome in Mountain Lion. Advice welcomed. Btw,
-
How to increment counter for line items.
Hi, Please see the code below: LOOP AT T_MAT INTO W_MAT. perform bdc_dynpro using 'SAPMM07M' '0421'. perform bdc_field using 'BDC_CURSOR' 'MSEG-ERFMG(i)'. perform bdc_fi
-
X3-02 Sending and receiving mms messages
I got this phone for xmas and having problems sending and receiving photos, please could someone explain what I need to set. Thank you
-
Hello, What are you guys doing for Windows clients on your network? Right now I am looking through the server essentials book but looking at ideas. Can you only do mobile accounts where the data is just stored on the server or can you do a sync funct