Weblogic 10 Slow in prod after 1 - 2 weeks

Hello,
We are using weblogic 10. The systems becomes very slow after 1-2 weeks in production.
Restarting the servers solves the problems.
Our application need to remain up 24 x 7. In order to restore the performance we need to restart the servers which causes some downtime.
Is there any other solution to the problem? Do enterprises normally reatart their production servers on a regular interval?
Thanks,
Sastry.

Hi Raj,
This could be the symptom of a memory leak, building slowly over time. Please capture and share the following data:
- Before restarting your slow application, capture a JVM Thread Dump
- Turn on verbose GC (or use any other monitoring tool of your chioce) from your server Java process so you can monitor on a daily basis the Java heap + native (Perm Gen if Sun VM etc.)
Please provide the specifications of your environment so I can recommend you some troubleshooting tools you can use.
Regards,
P-H
http://javaeesupportpatterns.blogspot.com/

Similar Messages

File Server/AFP gets slow after a week or so

Hi all,
I manage a file server at our office here, with around 20-30 users, running 10.3.9 server. Users connect via AFP for general office duties, but also remote-desktop into a windows server using Rdesktop via X11. They use SMB to access their files from the windows side.
I find after a week or so that logins to the shares, and general file access gets incredibly slow, and grinds to a halt eventually, but comes good after the server is rebooted.
It is usually quick to authenticate in any case, but takes an age to bring up the list of shares that the users can pick from (probably 10-15 at most depending on their permissions). Even after a fresh reboot it takes about 10 seconds to bring up the list of shares to pick from. Is there any way to fix this?
I find that is someone has their computer set to calculate folder sizes on a server drive/share it can make the server grind to a standstill, but even with everyone set up correctly it still goes slowly all by itself after a few days/weeks of running. Logging in via Remote Desktop becomes slow at this point too.
I've tried some of the tips in this thread below with only limited success.
http://discussions.apple.com/thread.jspa?threadID=343979&tstart=15
Any help is greatly appreciated

As you upgraded the router's firmware,reset the router for 30 seconds and reconfigure the router from scratch.
On the router setup page,Under the Wireless tab,click on the Advanced Wireless Settings...Change the Beacon Interval to 75, Change the Fragmentation Threshold to 2304,Change the RTS Threshold to 2307 and Click on Save Settings...

My Macbook Pro is about 4 to 5 years old. I've noticed the last few months that speed was becoming much slower. It slowed to a crawl last week and won't even turn on now. Where do I take this to near Jackson, Michigan for service?.

My Macbook Pro is about 4 to 5 years old. I've noticed the last few months that speed was becoming much slower. It slowed to a crawl last week and won't even turn on now. Where can I take my Macbook Pro for service near Jackson, Michigan?.

Things You Can Do To Keep Your Computer From Slowing Down
If your computer seems to be running slower here are some things you can do:
Boot into Safe Mode then repair your hard drive and permissions:
Repair the Hard Drive and Permissions Pre-Lion
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
Repair the Hard Drive - Lion
Boot from your Lion Recovery HD. When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu. Select Restart from the Apple menu.
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Restart your computer normally and see if this has helped any. Next do some maintenance:
Suggestions for OS X Maintenance
For situations Disk Utility cannot handle the best third-party utility is Disk Warrior; DW only fixes problems with the disk directory, but most disk problems are caused by directory corruption; Disk Warrior 4.x is now Intel Mac compatible.
OS X performs certain maintenance functions that are scheduled to occur on a daily, weekly, or monthly period. The maintenance scripts run in the early AM only if the computer is turned on 24/7 (no sleep.) If this isn't the case, then an excellent solution is to download and install a shareware utility such as Macaroni, JAW PseudoAnacron, or Anacron that will automate the maintenance activity regardless of whether the computer is turned off or asleep. Dependence upon third-party utilities to run the periodic maintenance scripts was significantly reduced since Tiger. These utilities have limited or no functionality with Snow Leopard or Lion and should not be installed.
OS X automatically defragments files less than 20 MBs in size, so unless you have a disk full of very large files there's little need for defragmenting the hard drive. As for virus protection there are few if any such animals affecting OS X. You can protect the computer easily using the freeware Open Source virus protection software ClamXAV. Personally I would avoid most commercial anti-virus software because of their potential for causing problems. For more about malware see Macintosh Virus Guide.
I would also recommend downloading a utility such as TinkerTool System, OnyX 2.4.3, or Cocktail 5.1.1 that you can use for periodic maintenance such as removing old log files and archives, clearing caches, etc.
For emergency repairs install the freeware utility Applejack. If you cannot start up in OS X, you may be able to start in single-user mode from which you can run Applejack to do a whole set of repair and maintenance routines from the command line. Note that AppleJack 1.5 is required for Leopard. AppleJack 1.6 is compatible with Snow Leopard. There is no confirmation that this version also works with Lion.
When you install any new system software or updates be sure to repair the hard drive and permissions beforehand.
Get an external Firewire drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
1. Carbon Copy Cloner
2. Data Backup
3. Deja Vu
4. SuperDuper!
5. SyncTwoFolders
6. Synk Pro
7. Synk Standard
8. Tri-Backup
Visit The XLab FAQs and read the FAQs on maintenance, optimization, virus protection, and backup and restore.
Additional suggestions will be found in Mac maintenance Quick Assist.
Referenced software can be found at CNet Downloads or MacUpdate.
Additional Hints
Be sure you have an adequate amount of RAM installed for the number of applications you run concurrently. Be sure you leave a minimum of 10% of the hard drive's capacity as free space.
Add more RAM. If your computer has less than 2 GBs of RAM and you are using OS X Leopard or later, then you can do with more RAM. Snow Leopard and Lion work much better with 4 GBs of RAM than their system minimums. The more concurrent applications you tend to use the more RAM you should have.
Always maintain at least 15 GBs or 10% of your hard drive's capacity as free space, whichever is greater. OS X is frequently accessing your hard drive, so providing adequate free space will keep things from slowing down.
Check for applications that may be hogging the CPU:
Open Activity Monitor in the Utilities folder. Select All Processes from the Processes dropdown menu. Click twice on the CPU% column header to display in descending order. If you find a process using a large amount of CPU time, then select the process and click on the Quit icon in the toolbar. Click on the Force Quit button to kill the process. See if that helps. Be sure to note the name of the runaway process so you can track down the cause of the problem.
Often this problem occurs because of a corrupted cache or preferences file or an attempt to write to a corrupted log file.

I am having a problem with very slow start up after expanding RAM on my 2009 Mac Pro.

I am having a problem with very slow start up after expanding RAM on my 2009 Mac Pro (8 Core 2.93GHz). When I run the Mac Pro with 2 x 2Gb RAM it takes 4 seconds before the gray screen, chime and spinning wheel appear.However when I expand the RAM to 20GB the grey screen and chimes appear after a long 20+ second black screen.
The RAM modules are paored 2 x 4GB Crucial CT51272BA1339.M18FMR and 6 x 2GB SAMSUNG M391B5673FH0-CH9, all DDR3 ECC.
Reading articles on the internet, I thought it may be damaged RAM modules, but I have completed memtest and all are okay. I have tried changing the pairs around and if I use any paired 2 modules the Mac Pro starts normally, only when I try running more than 2 modules the delayed start up happens. (black screen 20 Seconds)
I also have tried PRAM and SMU resets after changing the RAM setups, and the issues always occurs when I have more than 2 modules. As you can see I have 6 SAMSUNG modules and even with identical modules the issue happens, when increasing the RAM to more than 2 modules.
The Mac Pro runs fine after the start up screen and can see all the modules, but has anyone else come across this issue, or have any ideas as to why my Mac Pro is taking 20 seconds to start up with 20 GB RAM?

Hi there. Thanks for your comments.
I have tried all the different combinations of RAM setup, and as stated in my initial topic, the Mac Pro boot up time only slows when I have more that 2 modules. Where I place these does not seem to make a difference.
I have taken the Mac Pro to an Apple Reseller technician yesterday and they where not able to find any RAM errors. Apparently the boot up time is within Apple's acceptable parameters for this set up.
Could anyone that is running a Mac Pro 2009 with more that 4 modules of RAM, please let me know if the boot up time is normal. ( the time it takes from pressing the power button to seeing the gray screen around 16 - 20 seconds)
Or is anyone else having the same issues?
thanks for your responce

Slow down Database after upgrading to 10.2.0.5

Hi
I am having performance problems after upgrading to 10.2.0.5
At the beginning I thought the problem was sga too smalle ( ini: 598M , now 1408M ) but even after recreating the database with the new value the problem remains.
I am sending reports so that someone could give me an idea.
Thanks in advance!
DETAILED ADDM REPORT FOR TASK 'TASK_240' WITH ID 240
Analysis Period: 22-JUN-2011 from 08:34:06 to 16:00:13
Database ID/Instance: 2462860799/1
Database/Instance Names: DXT/DXT
Host Name: thoracle
Database Version: 10.2.0.5.0
Snapshot Range: from 71 to 78
Database Time: 6726 seconds
Average Database Load: .3 active sessions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FINDING 1: 38% impact (2540 seconds)
SQL statements consuming significant database time were found.
RECOMMENDATION 1: SQL Tuning, 26% benefit (1763 seconds)
ACTION: Investigate the SQL statement with SQL_ID "30rku9qg2y30j" for
possible performance improvements.
RELEVANT OBJECT: SQL statement with SQL_ID 30rku9qg2y30j and
PLAN_HASH 2734400036
select a.owner, a.object_name, INSTR(a.object_type, :"SYS_B_00"),
:"SYS_B_01" from sys.all_objects a where a.object_type IN
(:"SYS_B_02",:"SYS_B_03") and a.status = :"SYS_B_04" and a.owner
like:"SYS_B_05"escape:"SYS_B_06" and a.object_name
like:"SYS_B_07"escape:"SYS_B_08" union all select c.owner,
c.synonym_name, INSTR(a.object_type, :"SYS_B_09"), :"SYS_B_10" from
sys.all_objects a, sys.all_synonyms c where c.table_owner = a.owner
and c.table_name = a.object_name and a.object_type IN
(:"SYS_B_11",:"SYS_B_12") and a.status = :"SYS_B_13" and c.owner
like:"SYS_B_14"escape:"SYS_B_15" and c.synonym_name
like:"SYS_B_16"escape:"SYS_B_17" union all select distinct b.owner,
CONCAT(b.package_name, :"SYS_B_18" || b.object_name),
min(b.position), max(b.overload) from sys.all_arguments b where
b.package_name IS NOT NULL and b.owner
like:"SYS_B_19"escape:"SYS_B_20" and b.package_name
like:"SYS_B_21"escape:"SYS_B_22" group by b.owner,
CONCAT(b.package_name, :"SYS_B_23" || b.object_name) union all select
distinct c.owner, CONCAT(c.synonym_name, :"SYS_B_24" ||
b.object_name), min(b.position), max(b.overload) from
sys.all_arguments b, sys.all_synonyms c where c.table_owner = b.owner
and c.table_name = b.package_name and b.package_name IS NOT NULL and
c.owner like:"SYS_B_25"escape:"SYS_B_26" and c.synonym_name
like:"SYS_B_27"escape:"SYS_B_28" group by c.owner,
CONCAT(c.synonym_name, :"SYS_B_29" || b.object_name) union all select
distinct c.owner, c.synonym_name, min(b.position), max(b.overload)
from sys.all_arguments b, sys.all_synonyms c where c.owner = b.owner
and c.table_owner=b.package_name and c.table_name=b.object_name and
c.owner like:"SYS_B_30"escape:"SYS_B_31" and c.synonym_name
like:"SYS_B_32"escape:"SYS_B_33" group by c.owner, c.synonym_name
RATIONALE: SQL statement with SQL_ID "30rku9qg2y30j" was executed 12270
times and had an average elapsed time of 0.036 seconds.
RATIONALE: Waiting for event "cursor: pin S wait on X" in wait class
"Concurrency" accounted for 7% of the database time spent in
processing the SQL statement with SQL_ID "30rku9qg2y30j".
RECOMMENDATION 2: SQL Tuning, 23% benefit (1550 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"7yv1ba0c8y86t".
RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
RATIONALE: SQL statement with SQL_ID "7yv1ba0c8y86t" was executed 47
times and had an average elapsed time of 32 seconds.
RECOMMENDATION 3: SQL Tuning, 14% benefit (926 seconds)
ACTION: Use bigger fetch arrays while fetching results from the SELECT
statement with SQL_ID "7yv1ba0c8y86t".
RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
FINDING 2: 37% impact (2508 seconds)
Time spent on the CPU by the instance was responsible for a substantial part
of database time.
RECOMMENDATION 1: SQL Tuning, 26% benefit (1763 seconds)
ACTION: Investigate the SQL statement with SQL_ID "30rku9qg2y30j" for
possible performance improvements.
RELEVANT OBJECT: SQL statement with SQL_ID 30rku9qg2y30j and
PLAN_HASH 2734400036
select a.owner, a.object_name, INSTR(a.object_type, :"SYS_B_00"),
:"SYS_B_01" from sys.all_objects a where a.object_type IN
(:"SYS_B_02",:"SYS_B_03") and a.status = :"SYS_B_04" and a.owner
like:"SYS_B_05"escape:"SYS_B_06" and a.object_name
like:"SYS_B_07"escape:"SYS_B_08" union all select c.owner,
c.synonym_name, INSTR(a.object_type, :"SYS_B_09"), :"SYS_B_10" from
sys.all_objects a, sys.all_synonyms c where c.table_owner = a.owner
and c.table_name = a.object_name and a.object_type IN
(:"SYS_B_11",:"SYS_B_12") and a.status = :"SYS_B_13" and c.owner
like:"SYS_B_14"escape:"SYS_B_15" and c.synonym_name
like:"SYS_B_16"escape:"SYS_B_17" union all select distinct b.owner,
CONCAT(b.package_name, :"SYS_B_18" || b.object_name),
min(b.position), max(b.overload) from sys.all_arguments b where
b.package_name IS NOT NULL and b.owner
like:"SYS_B_19"escape:"SYS_B_20" and b.package_name
like:"SYS_B_21"escape:"SYS_B_22" group by b.owner,
CONCAT(b.package_name, :"SYS_B_23" || b.object_name) union all select
distinct c.owner, CONCAT(c.synonym_name, :"SYS_B_24" ||
b.object_name), min(b.position), max(b.overload) from
sys.all_arguments b, sys.all_synonyms c where c.table_owner = b.owner
and c.table_name = b.package_name and b.package_name IS NOT NULL and
c.owner like:"SYS_B_25"escape:"SYS_B_26" and c.synonym_name
like:"SYS_B_27"escape:"SYS_B_28" group by c.owner,
CONCAT(c.synonym_name, :"SYS_B_29" || b.object_name) union all select
distinct c.owner, c.synonym_name, min(b.position), max(b.overload)
from sys.all_arguments b, sys.all_synonyms c where c.owner = b.owner
and c.table_owner=b.package_name and c.table_name=b.object_name and
c.owner like:"SYS_B_30"escape:"SYS_B_31" and c.synonym_name
like:"SYS_B_32"escape:"SYS_B_33" group by c.owner, c.synonym_name
RATIONALE: SQL statement with SQL_ID "30rku9qg2y30j" was executed 12270
times and had an average elapsed time of 0.036 seconds.
RATIONALE: Waiting for event "cursor: pin S wait on X" in wait class
"Concurrency" accounted for 7% of the database time spent in
processing the SQL statement with SQL_ID "30rku9qg2y30j".
RATIONALE: Average CPU used per execution was 0.036 seconds.
RECOMMENDATION 2: SQL Tuning, 23% benefit (1550 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"7yv1ba0c8y86t".
RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
RATIONALE: SQL statement with SQL_ID "7yv1ba0c8y86t" was executed 47
times and had an average elapsed time of 32 seconds.
RATIONALE: Average CPU used per execution was 32 seconds.
RECOMMENDATION 3: SQL Tuning, 5.8% benefit (390 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"cbtd2nt52qn1c".
RELEVANT OBJECT: SQL statement with SQL_ID cbtd2nt52qn1c and
PLAN_HASH 2897530229
Select DAE_.ROWID, DAE_.*, HAE_.*
From THPR.GACCENTRYD DAE_, THPR.GACCENTRY HAE_ Where ((HAE_.TYP_0(+)
= DAE_.TYP_0) AND (HAE_.NUM_0(+) = DAE_.NUM_0))
And HAE_.CPY_0 = :1 And HAE_.ACCDAT_0 >= :2 And HAE_.ACCDAT_0 <= :3
And DAE_.ACC_0 = :4 And HAE_.FCY_0 >= :5 And HAE_.FCY_0 <= :6
Order by DAE_.BPR_0,DAE_.CUR_0,DAE_.ACC_0
RATIONALE: SQL statement with SQL_ID "cbtd2nt52qn1c" was executed 12980
times and had an average elapsed time of 0.03 seconds.
RATIONALE: Average CPU used per execution was 0.029 seconds.
RECOMMENDATION 4: SQL Tuning, 2.1% benefit (138 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"33t7fszkr29gy".
RELEVANT OBJECT: SQL statement with SQL_ID 33t7fszkr29gy and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
(((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7)))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
RATIONALE: SQL statement with SQL_ID "33t7fszkr29gy" was executed 1
times and had an average elapsed time of 136 seconds.
RATIONALE: Average CPU used per execution was 138 seconds.
FINDING 3: 15% impact (1008 seconds)
SQL statements with the same text were not shared because of cursor
environment mismatch. This resulted in additional hard parses which were
consuming significant database time.
RECOMMENDATION 1: Application Analysis, 15% benefit (1008 seconds)
ACTION: Look for top reason for cursor environment mismatch in
V$SQL_SHARED_CURSOR.
ADDITIONAL INFORMATION:
Common causes of environment mismatch are session NLS settings, SQL
trace settings and optimizer parameters.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Hard parsing of SQL statements was consuming significant
database time. (20% impact [1336 seconds])
SYMPTOM: Contention for latches related to the shared pool was
consuming significant database time. (2% impact [135
seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
database time.
SYMPTOM: Wait class "Concurrency" was consuming significant
database time. (2.3% impact [154 seconds])
FINDING 4: 8.5% impact (570 seconds)
Wait class "User I/O" was consuming significant database time.
NO RECOMMENDATIONS AVAILABLE
ADDITIONAL INFORMATION:
Waits for I/O to temporary tablespaces were not consuming significant
database time.
The throughput of the I/O subsystem was not significantly lower than
expected.
FINDING 5: 5.3% impact (355 seconds)
The SGA was inadequately sized, causing additional I/O or hard parses.
RECOMMENDATION 1: DB Configuration, 3.2% benefit (215 seconds)
ACTION: Increase the size of the SGA by setting the parameter
"sga_target" to 1740 M.
ADDITIONAL INFORMATION:
The value of parameter "sga_target" was "1392 M" during the analysis
period.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Hard parsing of SQL statements was consuming significant
database time. (20% impact [1336 seconds])
SYMPTOM: Contention for latches related to the shared pool was
consuming significant database time. (2% impact [135
seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
database time.
SYMPTOM: Wait class "Concurrency" was consuming significant
database time. (2.3% impact [154 seconds])
SYMPTOM: Wait class "User I/O" was consuming significant database time.
(8.5% impact [570 seconds])
INFO: Waits for I/O to temporary tablespaces were not consuming
significant database time.
The throughput of the I/O subsystem was not significantly lower
than expected.
FINDING 6: 4.2% impact (281 seconds)
Cursors were getting invalidated due to DDL operations. This resulted in
additional hard parses which were consuming significant database time.
RECOMMENDATION 1: Application Analysis, 4.2% benefit (281 seconds)
ACTION: Investigate appropriateness of DDL operations.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Hard parsing of SQL statements was consuming significant
database time. (20% impact [1336 seconds])
SYMPTOM: Contention for latches related to the shared pool was
consuming significant database time. (2% impact [135
seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
database time.
SYMPTOM: Wait class "Concurrency" was consuming significant
database time. (2.3% impact [154 seconds])
FINDING 7: 4% impact (266 seconds)
Waits on event "log file sync" while performing COMMIT and ROLLBACK operations
were consuming significant database time.
RECOMMENDATION 1: Host Configuration, 4% benefit (266 seconds)
ACTION: Investigate the possibility of improving the performance of I/O
to the online redo log files.
RATIONALE: The average size of writes to the online redo log files was
26 K and the average time per write was 2 milliseconds.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "Commit" was consuming significant database time.
(4% impact [266 seconds])
FINDING 8: 2.9% impact (192 seconds)
Soft parsing of SQL statements was consuming significant database time.
RECOMMENDATION 1: Application Analysis, 2.9% benefit (192 seconds)
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: DB Configuration, 2.9% benefit (192 seconds)
ACTION: Consider increasing the maximum number of open cursors a session
can have by increasing the value of parameter "open_cursors".
ACTION: Consider increasing the session cursor cache size by increasing
the value of parameter "session_cached_cursors".
RATIONALE: The value of parameter "open_cursors" was "800" during the
analysis period.
RATIONALE: The value of parameter "session_cached_cursors" was "20"
during the analysis period.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Contention for latches related to the shared pool was consuming
significant database time. (2% impact [135 seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of database
time.
SYMPTOM: Wait class "Concurrency" was consuming significant database
time. (2.3% impact [154 seconds])
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ADDITIONAL INFORMATION
Wait class "Application" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" 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.
The analysis of I/O performance is based on the default assumption that the
average read time for one database block is 10000 micro-seconds.
An explanation of the terminology used in this report is available when you
run the report with the 'ALL' level of detail.

user12023161 wrote:
I have upgraded 10.2.0.3.0 to 10.2.0.5.0 and facing same issue. The database is slow in general after upgrade compared to 10.2.0.3.0.Try setting OPTIMIZER_FEATURE_ENABLE parameter to 10.2.0.3.
Refer following link:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams142.htm

My Iphone 5c was brand new and haven't been dropped or anything,after a week or so my Iphone 5c presented a blue screen and shut down .....I restarted it like people said but it doesn't work.And now my Iphone 5c doesn't turn on at aLL

My Iphone 5c was brand new and i got it for my birthday.After a week it began giving me blue screens.I searched online and restarted it ,retored it and etc.Now after 10 tries my Iphone5c does not turn on at all.Now I am freaking out.There is no Apple store close by so Im screwed....I really need help

Hi mgarcia3,
If you are having an issue with
As someone who uses my iPhone almost constantly I can certainly understand how you would be upset to have it not be able to even turn on. Let's see if we can get you back up and running.
I would suggest that you troubleshoot using the steps in this article -
iOS: Not responding or does not turn on - Apple Support
Be sure to note the last step -
If the above steps do not resolve the issue, contact Apple.
Thanks for using Apple Support Communities.
Best,
Brett L

Podcast not showing up in itunes search after 1 week

i submitted my podcast with one episode and it was accepted on 17 july. i am able to get to it in the itunes store by using the url as provided in the email.
iTunes Store Welcome
Dear Podcast Owner
Your podcast, located at [ http://feeds.feedburner.com/meterdown ], has been approved. You should expect to see it in iTunes within the next few hours. When it's available, you will be able to access it with the URL below.
http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=260194221
i have put an icon with that url in my blog (meterdown.wordpress.com) and that works fine. people are taken to the podcast in the itunes store and can subscribe.
however when i search the store, my podcast is not turning up either by podcast name (meter down) or by author/artist name (kabi) or by keyword (taxi, bombay, hindi).
I can ping using the podcast ID (id=nnn) and it returns the podcast feed url (http://feeds.feedburner.com/meterdown) and the podcast ID.
it doesn't list an episode however. is it supposed to?
my main question is "why am i not showing up in the search?"
is there something wrong in my xml? I host at switchpod and run it thru feedburner and I use the feedburner feed.
i have read and read the forums here, feedburner, podcast alley and also am emailing switchpod support. still can't figure it out.
thanks
kabi
macbook pro Mac OS X (10.4.10)
macbook pro Mac OS X (10.4.10)

ssukotto,
Thanks for the information. What you mention is boilerplate that is automatically sent when a new podcast is approved. I also quoted it like scripture before diving deeper into researching this issue.
The research into this problem suggests that there is a minimum number of podcasts in order to be included in the search index (or at least the search results) whether it's undocumented or unintentional.
Case in point, Meter Down posted his first complaint that his podcast hadn't shown up in the search even after a week (far outside the 24-48 hours you mention and that is documented)..that was a week ago. A total of at least two weeks that his podcast could not be found by searching by the exact title. His podcast showed up search within a day after adding his second episode (yesterday).
Jerry Pine posted July 17 that his podcast "Everything Algae" had been approved July 13 but couldn't be found by searching...even by name. July 28th, he added a second episode as a test...and his podcast became searchable.
There are several others who went for days or weeks without being listed in search results by even searching for their exact podcast title...common trait between all of them was that they only had one episode. They added a second episode and within the day they show up in search results.
There are others that had newly submitted podcasts whose podcasts showed up within the 24-48 hours timeframe...but they had at least two episodes.
I'm just providing the facts...could be coincidence that they just happened to be searchable just after posting a second episode.
I'd invite you to read through and share with the iTunes podcast developers the several thread from various people who have reported problems with having a searchable podcasts and draw your own conclusions.
Erik

My phone wouldn't back up with iCloud because it ran out of storage . I purchased more iCloud storage after a week and after doing an iTunes backup and now it won't backup with the cloud

My phone ran out of iCloud storage. After a week I did an iTunes backup then bought more iCloud storage and now it won't back up with the iCloud.

Do you have sufficient storage now? And did you turn on iCloud backup in Settings>iCloud>Storage & Backup?

Solution to install Windows 7 on Macbook Air MID-2013 after 3 weeks of test, make with ISO image a usb key 2.0, It works!

Solution to install Windows 7 on Macbook Air MID-2013 after 3 weeks of test, make with ISO image a usb key 2.0, It works!

1. Select Partition4: Bootcamp. You should see advanced Options.
2. Click Format and convert the partition to NTFS.
3. Click Next.
Reference - http://manuals.info.apple.com/MANUALS/1000/MA1636/en_US/boot_camp_install-setup_ 10.8.pdf
See Page 6.

I just plugged in my Iphone after 4 weeks of downloading music and adding contacts around 400 to be excact and it whipped all my data out and I have no photos nothing reset to factory defult and I cannot even listen to music I purchased because it skips

I just plugged in my Iphone after 4 weeks of downloading music and adding contacts around 400 to be excact. When I plugged it in my computer it started to sync with iTunes and it whipped all my data out. I have no photos contacts nothing, so I then in a rage reset to factory defult and I cannot even listen to music I purchased because it skips. I just want my phone back

Was this the very first time you ever plugged the phone into that computer?
Did you pay attention to the prompts you were given when you plugged it in?
Did you have iCloud backups turned on before you did this? I hope so... If you did, restore the phone from the last iCloud backup from before you wiped it. If not, then the photos, etc. are gone. Apps and music can be re-downloaded.

I bought my iphone less a month, with a week warranty to be replaced should there be any problem, after a week, while im talking or using any of its softwares, the screen just disappear and i had to restart all over before i can operate it. Please help.

I bought my iphone on 23 June 2011, a week after the warranty period, I noticed that, each time I am on line or using it's software, the screen just disappear and offline just like that, and I had to re-start my iphone.
I have been facing this problem numeral times and not sure what is wrong with it.
Went back to Celcom to report, they asked me to deposit to their technical department and to come back after 2 weeks. (2 weeks) is way too long to wait.
Please help.
Thank you.

Do you live near an Apple Store? If so, pop in and see a Genius, if they discover a fault they may replace the phone there and then, for free as part of your 1-year warranty.

[WARNING] fglrx invalid map error killed my system after 3 weeks

Hi! I had to re-install my entire archinstall 64bit after 3 weeks of usage. I noticed when my system froze during a reboot the /var/log it self were going over 9GB!!!!!!!!!!! And that was because the kernel generated tons of errors concering catalyst 9.4-9.5.
I couldn't check the xorg log since my system died trying to start X (kde4), but it was blank. 9GB that's insane if you ask me, and all the errorrs were related to catalyst "fglrx fireq invalid map handle".
I tried running cat/nano on the error logs but that also generated in a massive hardware freeze (fans spins down) no wonder since the logs were filled with tons of errors.
Is there a way to tell the kernel or w/e to shut the hell up? No seriously, I don't want to re-install my laptop in less then a month.
I know amd/ati doesnt support the 2.29-30 kernel yet but is there a way to silence the errors?
Last edited by greenfish (2009-05-24 19:41:34)

Hi! I had to re-install my entire archinstall 64bit after 3 weeks of usage. I noticed when my system froze during a reboot the /var/log it self were going over 9GB!!!!!!!!!!! And that was because the kernel generated tons of errors concering catalyst 9.4-9.5.
I couldn't check the xorg log since my system died trying to start X (kde4), but it was blank. 9GB that's insane if you ask me, and all the errorrs were related to catalyst "fglrx fireq invalid map handle".
I tried running cat/nano on the error logs but that also generated in a massive hardware freeze (fans spins down) no wonder since the logs were filled with tons of errors.
Is there a way to tell the kernel or w/e to shut the hell up? No seriously, I don't want to re-install my laptop in less then a month.
I know amd/ati doesnt support the 2.29-30 kernel yet but is there a way to silence the errors?
Last edited by greenfish (2009-05-24 19:41:34)

I got this new Ipad. After a month my charger broke. So what I did is got a new charger that is not from Apple company it was from a different company. After 3 week it doesn't work anymore. What do I do. HELP ME PLEASE!!!!!!!!!!!

I got this new Ipad. After a month my charger broke. So what I did is got a new charger that is not from Apple company it was from a different company. After 3 week it doesn't work anymore. What do I do. HELP ME PLEASE!!!!!!!!!!!

Not normal. Take it (iPad, cable & charger) to an Apple Store for evaluation.
Make a Genius Bar Reservation
http://www.apple.com/retail/geniusbar/
 Cheers, Tom

Any one has problem with notes getting deleted after a week ?

After upgrade to iOs 7, my new notes that I wrote on icloud or email are deleted after a week. I have to take note again and again, first i did not notice because i thought i was accidently deleted, but then a week later i lost the new notes again. All old notes are ok, it just happen to new notes after iOs 7. Pls help

try SUS and reinstall it again

Domain did not find after 2 weeks

Hello everyone
We have both Macs and PCs with 1 Mac Server 10.4.8. The PCs have to join the domain. We created PDC with domain: MEDIER. It was working good. But new PCs could not find MEDIER after 2 weeks. So I have to stop service and restart service, then it will work again. I dont know what problem it is. Hope someone can help. Thanks
Regards
Tri
( Server Admin-Computers & Services-Windows-Settings-General)

At the beginning, we upgraded from OS Server 10.3.9 to Server 10.4.8. it did not work good at all. We decided to install new, fresh installation Server 10.4.8, and then updated to 10.4.10 now. Lookup and forward DNS are working: internal.loc = 192.168.1.3.
I tried to join MEDIER, it said that "the domain could not find domain bla bla bla, contact the administrator...". If I stop and restart the service, it could find the domain: MEDIER, and then PCs could join MEDIER without any problem. The problem is, I have to stop and restart the service after 2 weeks
Is the problem related to DNS or how to stop MEDIER from sleeping?
Thanks again

Weblogic 10 Slow in prod after 1 - 2 weeks

Similar Messages

Maybe you are looking for