Tdm slow down program after some hours

hello

hi Gibbi
What version of labview are you using?
In labVIEW 8.2 the TDM's files are improved with TDMs(http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/ni_test_data_exchange/) wich are VIs that improved this behavior.
In the case you are using labview 8.20 here is a link where you can learn how to change the format of your tdm to tdms
http://zone.ni.com/reference/en-XX/help/371361B-01/glang/tdm_to_tdms/
In case you are not using LV 8.2 I need a little more information about your code in order to help you.
How many channels are you reading?
try to program TDM 's readings by channel groups not just channels
this arquitecture sometimes releases some resources of your computer
Also you can program a more efficient reading method to avoid the lattency.
If you need something else please post more info about your system.
Thanks for using National Instruments products
Erwin Franz R.

Similar Messages

After migration the MaxDB 7.6 down the performance after some hours of use

Hi,
After many tests i put the version of MaxDB 7.6 in production, after some hours of use, now i'm getting a strange slow down in performance of the database, looking at the knldiag file i cant find anything that can show me the reason.
any idea how to check what happen?
thanks
Clóvis

Hi, Oksana,
I think that notes are only for SAP customers, right? because i'm not a SAP customer, there is a way to you be more specific about what i need to check without having access to that notes?
look on wrk directory i discover that the files QUAL.dmp and comseg.dmp are updated when the system get slow, i checked the knldiag but dont have any error,
any idea because these files are generated?
best regards
Clovis

Printer loses wireless connection after some hours

Hello to all!
Printer is connected and I can see on the screen correct IP. Desktops with Win7 and Ubuntu are used. After switching on printer works properly, but several hours later its unreachable from both systems. Printer shows connection, I can see it in router web access tool, but it is unreachable. I have to switch off printer, reboot the router, then switch on printer - and it works. Not very comfort.
Does anybody know how to fix this bug?
This question was solved.
View Solution.

Hi @varspb,
Welcome to the HP Forums!
I noticed that your HP Deskjet Ink Advantage 6525 printer is losing wireless connection after some hours with Windows 7 and Ubuntu. I am happy to look into this connection issue for you!
For Linux support, please take a look at this website, http://hplip.sourceforge.net/.
Otherwise, please see the following guides:
HP Single-Function and Multifunction Printers - 'Printer is offline' Message Displays on the Compute....
HP Deskjet Ink Advantage 6520 e-All-in-One and HP Photosmart 6520 e-All-in-One Printer Series - Prin....
Tips for preventing wireless connection issues
The following tips can help prevent wireless connection issues:
Move the printer and the computer or access point (router) closer together.
Remove any metal objects between the printer and the computer or access point (router). Objects such as refrigerators or metal bookcases can interfere with wireless transmission.
Move any device that emits radio signals farther away from the printer. Devices such as microwaves and cordless telephones can interfere with wireless transmission.
Consult the router manufacturer for updates and configuration of your router.
Make sure that your computer is not connected through a VPN. You cannot access your printer on your wireless network while connected to a VPN.
Also, please take a look at this website, HP Wireless Printing Center - Troubleshooting Issues.
Hope this helps, and have a good day!
RnRMusicMan
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to say “Thanks” for helping!

Why all the errors appear after some hours on pc

Why all the errors appear after some hours on pc

Thanks for reply but the 2 HDD oki think the PS is 200 W that made that problem ?Or from TEMP ? i made it more able to flow the air & become better now

TDMS file error occurs after several hours

I have a compiled LabVIEW 2010 SP1 executable running on a Windows 7 PXI computer that is occasionally producing the following error message:
"LabVIEW: LabVIEW could not load the TDMS file component.
The top-level VI <my VI's name> was stopped at unknown on the block diagram of <my VI's name>"
This program is interfacing with equipment under test over a number of PXI cards and ethernet connections. It alters inputs to the system based on script commands, while receiving and displaying outputs. During testing, state changes are sent to a TDMS file. The system can run for hours but will usually produce the above error message... eventually.
The error seems to indicate that a LabVIEW file is missing, but the TDMS files are being created, so I may not be understanding the meaning of the error. Does anyone know what the actual cause(s) of this error message are?

The code writes to the TDMS file using the "TDMS Write" VI from the TDM Streaming Palette. These write VIs are located in 12 different sub VIs in a program loop within my main VI. Every 50ms they execute, service the I/O, and write to the TDMS file if data in the particular sub VI has changed state. Some are writing floating point numbers, most are writing strings. There are about 750 total channels being written. I know that posting the code would be more usefull than describing it, but I think posting the source code would be frowned upon by my company. There are over a hundred custom VIs and external hardware connections that are required to effectively run this code anyway.
Regarding timing, there doesn't seem to be a particular amount of time that has to pass before this issue occurs. I was given a screenshot that shows the error occured after 11 hours of running. I was also told that the same error had occured about 6+ hours into a test once. I can say that this error doesn't seem to occur quickly, as in within the first hour or so. It seems to require long duration tests.

HP ENVY Phoenix h9-1420t CT slows down 100x after 30 minutes of startup, requires constant reboot

Windows 8, now Windows 8.1 does the same. After about 30 minutes everything is so slow.
For example: at first start, start up Control Panel is less than 1 second. After 30 minutres, Control panel takes 1Min 45 seconds to open. A Internet Explorer search goes from 1 second to over 1 minute.
Control Panel shows less than 3% total CPU and only a fraction of the total RAM is used. There are no strange applications running.
Running Paid version of Kaspersky. Run Microsoft Defender - no virus or registry errors.
Twice HP support instantly determines (with no facts) that it is a "virus" and had me install the Windows 8 OS from scratch. This didn't change anything either time. I am a little upset at all that time wasted because it requires installing all of the updates, then MS Office 2013. That is all we are trying to use on this machine. It is not a gaming or web surfing machine. We can't use it for MS Office because it failes to respond after about 30 minutes.
I have updated all the November drivers for motherboard, drive and others listed.
I manage over a dozen computers, this is a problem for the HP Envy Phoenix since day 1.
We are holding off on ordering any more HP in 1 qtr 2014 if this can't be fixed.
We won't accept it has a virus again unless HP can at least provide some proof or reasonable instructions.
We are very open to getting this fixec, but have spent over 100 hours of time and lost huge productvity. Our employee is working on an XP machine so they can stay more productive.

Hi Tesla3D,
One item of possible interest in your post is running both Kaspersky and Windows Defender.
You should turn off Defender in Control Panel.
That could be what is slowing down your system.
Note to self, check date of post!
Jaco
****I am not an HP employee****
Please give a" Kudos, Thumbs Up" if advice received is relevant or" Accept as Solution" to assist other forum users having a similar problem.
HP Products:
810-150se Desktop
17t-j000 Notebook
H8 1380t CTO Desktop
560z Desktop
Errare humanum est.

Crash of LabVIEW executeable after some hours

Hi to all,
I'm developing a LabVIEW program for a long term monitoring
application of serial (RS232) devices. On the target system the
program runs as executable. At start-up everything runs fine. After
several hours (usually 1..3) the application crashes with an access
violation. I did a lot of "debugging" on executable level, because the
error seems not to occur in the development environment. I found out,
that the fault has nothing to do with the serial communication,
because it occurs also in a "demo mode", where no communication with
devices is performed. I studied the Dr.Watson log files and found out,
that the fault occurs always at the same code position. (See below for
details.) The fault occurs under LabVIEW 6.0, 6.0.2 and also 6.1,
(resp. the according runtime). At the moment The Dr.Watson log
suggests, that the LabVIEW internal function "CancelOnOccur" performs
a jump to address 0x00000000, what of course will cause a GPF. The
symbol for this function can be found in the runtime DLL's as well as
the LabVIEW.exe. The development system and the target are Win2k
machines with all available patches/updates including SP4. Here are
some interesting parts from the Dr.Watson Log (sorry its in german):
Anwendungsausnahme aufgetreten:
Anwendung: (pid=832)
Wann: 27.03.2004 @ 12:02:28.522
Ausnahmenummer: c0000005 (Zugriffsverletzung)
*----> Systeminformationen <----*
Computername: - removed for privacy -
Benutzername: - removed for privacy -
Prozessoranzahl: 1
Prozessortyp: x86 Family 6 Model 8 Stepping 6
Windows 2000-Version: 5.0
Aktuelles Build: 2195
Service Pack: 4
Aktueller Typ: Uniprocessor Free
Firma: - removed for privacy -
Besitzer: - removed for privacy -
Statusabbild f�r Threadkennung 0x4a0
eax=00ca6830 ebx=00000003 ecx=00014988 edx=00ca6830 esi=00000000
edi=f1d00001
eip=00000000 esp=01fcff14 ebp=01fcff30 iopl=0 nv up ei ng nz
ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000
efl=00000296
Funktion:
FEHLER ->00000000 ???
00000001 ???
00000002 ???
00000003 ???
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
01FCFF10 3023F32E F1D00001 00000001 00D30368 00000000 !
01FCFF30 300797D2 7FB84F88 7FE5AEA8 00000001 7FEC01B8 !CancelOnOccur
01FCFF50 300C5AAC 7FE5B0D8 00000001 7FEC01B8 00000001 !GetSetLVInfo
01FCFF88 30075DEE 7FEC01B8 00000001 77E9BFF2 00CC0DF8 !ImaqReturnIDs
01FCFFA0 3026E759 7FEC01B8 30352068 0012E0EC 01FCFFEC !ConfigExec
01FCFFB4 77E7B382 00CC0DF8 30352068 0012E0EC 00CC0DF8 !GetTextRect
01FCFFEC 00000000 3026E730 00CC0DF8 00000000 00505A4D
kernel32!lstrcmpiW
*----> Raw Stack Dump <----*
01fcff14 2e f3 23 30 01 00 d0 f1 - 01 00 00 00 68 03 d3 00
...#0........h...
01fcff24 00 00 00 00 30 68 ca 00 - 88 67 93 7f 50 ff fc 01
.....0h...g..P...
01fcff34 d2 97 07 30 88 4f b8 7f - a8 ae e5 7f 01 00 00 00
....0.O..........
01fcff44 b8 01 ec 7f 00 00 00 00 - 01 00 00 00 88 ff fc 01
01fcff54 ac 5a 0c 30 d8 b0 e5 7f - 01 00 00 00 b8 01 ec 7f
..Z.0............
01fcff64 01 00 00 00 b8 01 ec 7f - f8 0d cc 00 10 2d cb 7f
01fcff74 94 3d c4 7f 00 00 00 00 - 00 00 00 00 00 00 00 00
..=..............
01fcff84 00 00 00 00 a0 ff fc 01 - ee 5d 07 30 b8 01 ec 7f
..........].0....
01fcff94 01 00 00 00 f2 bf e9 77 - f8 0d cc 00 b4 ff fc 01
........w........
01fcffa4 59 e7 26 30 b8 01 ec 7f - 68 20 35 30 ec e0 12 00 Y.&0....h
50....
01fcffb4 ec ff fc 01 82 b3 e7 77 - f8 0d cc 00 68 20 35 30
........w....h 50
01fcffc4 ec e0 12 00 f8 0d cc 00 - 00 80 fd 7f 05 00 00 c0
01fcffd4 c0 ff fc 01 60 fb fc 01 - ff ff ff ff b4 1b ec 77
.....`..........w
01fcffe4 f0 2a e7 77 00 00 00 00 - 00 00 00 00 00 00 00 00
..*.w............
01fcfff4 30 e7 26 30 f8 0d cc 00 - 00 00 00 00 4d 5a 50 00
0.&0........MZP.
01fd0004 02 00 00 00 04 00 0f 00 - ff ff 00 00 b8 00 00 00
01fd0014 00 00 00 00 40 00 1a 00 - 00 00 00 00 00 00 00 00
01fd0024 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
01fd0034 00 00 00 00 00 00 00 00 - 00 01 00 00 ba 10 00 0e
01fd0044 1f b4 09 cd 21 b8 01 4c - cd 21 90 90 54 68 69 73
.....!..L.!..This
Any ideas fromm other users?
Is there someone at NI who can support this issue?
If there is more information needed, I can provide it.
Thanks in advance!
Best Regards

Thanks for your comments.
NI germany has offerd me to get a test version of LabVIEW 7.0
(including application builder). This will be my next try. As I
mentioned in the posting before, I already do testing with the
executable with multithreading disabled (ESys.StdNParallel=0). At the
moment the system runs in this configuration for about 24 hours, but
its to early to say "I've got it!". Anyway, most of the application is
straight LabVIEW. There are some minor calls to DLL's, but these have
been prooven in other applications over years. I don't use ActiveX
controls. So my opinion still is, that the problem is related to
LabVIEW (runtime) itself. And additionally it can't be a solution for
the future to disable multithreading to get a stable application
. And
at the end, that the crash always occurs at the same LabVIEW internal
code position is an indicator for me, that my opinion can't be so
wrong. Is'nt there anybody in Austin who can take a look at source
code of the internal function "CancelOnOccur" to help tracking down
the problem. I hope that NI is interested in increasing its products
quality...

System has slowed down considerably after updates from Apple. Is SyncServer the culprit?

I use MacBook with preinstalled OS Leopard since April 2009. I have also regulalry updated my computer system using the Software Update application. However, since my last update on 12th Aug 2011, I have noticed that my system has slowed down. There is long pause between every character I type, delay in switching applications, battery dries out quicker, slow response to every command.
I have started facing this problem after updating following software like iTunes 10.4, Safari 5.0.6, Migration Assistant Update for MAC OS Leopard & Quick Time 7.7 from Software Updater. Although, my OS is still leopard.
I noticed on the Activity Monitor that syncserver is using majority of my RAM and reappers even if I stop the process. Some of its subprocess like AddressBookSync also appears and consumes lot of memory. Is this the problem? Though, I never noticed earlier what size it consumed.
I use Microsoft Office suite for Mac and have also checked and deselected all sync services. Yet, the Process (PID 305) continues to appear in Activity Monitor.
I am no techie, and would appreciate quick help to resolve this issue.
Thanks!

I was just about to write the same problem, but I don't have VMware; my laptop is late 2008 was running Snow Leopard (uptodate version).
I've scientific softwares so probably would require a clean re-installation of ML. I MUST MENTION HERE that those software which were written for PPC will NOT work on ML. Just found out that one of my important softwares version won't work on ML; need $500 to upgrade that software .
Therefore, I'd also want to know how can I go back to SL.
I'll let you know how clean re-installation has worked.

Screen Sharing slows down dramatically after RDP upgrade from 2 to 3

For some reason once we upgraded from RDP 2 to RDP 3 our Screen Sharing has gotten increasingly slow. We are using it in a school environment where the teacher will share their screen with the students, and as we add more students to the share the sharing slows down to become unusable. This problem is intermittent (otherwise I would go though the logs and run a control test), and has only started upon upgrading to RDP 3. Anyone else experience this behavior? I believe we are all running 10.5.x on the OS side.

I also know someone that is having this issue; it was fine with the previous ARD version they were using in the computer lab, but after upgrading screen sharing have slowed down. It's not really that of an issue when its just one computer, but when they put all 30 computers the FPS drops down.
Keep in mind that they were not having the issues before upgrading. I've also been told that, currently, they got a 5 MB connection. I ran a network test and everything seemed fine (or more like I didn't know what was going to tell me that something was wrong, but all the numbers were very low).

Macbook shuts down unexpectedly after an hour of use

I've had my MacBook since 2006, and I've had some minor problems now and then.
But since few days ago, my mac shuts down unexpectedly after I use it for about an hour.
at first I thought that maybe it's the fan, cause I've never cleaned the fan since the day I've bought it and my mac gets pretty hot after a while. but it used to work just fine when it got even hotter.
now I'm guessing maybe it's the battery? I've also never replaced the battery to a new one, cause I've almost always used power adapter instead of using battery alone. but I think I've heard it somewhere that the battery still dies even when you only use power adapter. is this true?
I usually just turn mac right back on when it shuts down, and it goes well for about 30 mins and then it shuts down again.
could anyone please be kind enough to tell me if it is the battery that's causing this such a frustrating problem? I don't know if this would help figure out the problem, but this is what battery info says,
Battery Information:
Battery Installed: Yes
First low level warning: No
Full Charge Capacity (mAh): 3674
Remaining Capacity (mAh): 3648
Amperage (mA): 0
Voltage (mV): 12443
Cycle Count: 105

Thank you so much for answering! I've actually read your answer to other similar forum, and have just installed iStatPro. it says that my fan is "exhaust" and at 0rpm. do i HAVE to replace the fan to a new one? can I just open up my mac and clean out the fan? if so, would you recommend this instead of buying a new fan? one last thing, if I buy a new fan, is it easy for me to replace it by myself? again, thank you so much for your answer.

Shut down WLAN after business hours

Hello,
We have recently deployed a vWLAN controller (AIR-CTVM-K9) and AIR-CAP2602I-A-K9 access points at all our sites. Since we are a retail operation I want to make the WLAN unavailable after business hours. The Cisco sales promo material mentions this as a capability but I can't find any supporting documentation.
How would I set this up?

There are several methods to achieve this and this depends on how your network is setup and how much technical skills you have:
1. MS AD: You can specify time and dates when authentication happens;
2. Cisco EnergyWise: You can specify what time of day(s) to enable the Cisco switch to provide PoE to the AP. When specified, the switch will disable power to the port.
3. You can enable time-based ACL to disable the dynamic interface of your AP. Your AP will still be able to broadcast the SSID but it will NOT accept any clients (or the clients will get 169.X.X.X IP addresses).
Finally,
4. If you have WCS/NCS or Prime Infrastructure, you can specify the time and date when the radio of the APs go up or down.

N73 got shuts down automatically after some time

hi,
my n73 music edition gets shut down after some time autmatically please can anybody tell me the reason.

The reason is that nokia phones have many bugs and problems.
A common cause of this problem is 3G. If the phone is in a weak 3G area the loss of 3G signal can cause the phone to reboot. It's an old problem thats been affecting nokia's for years. Disabling 3G can stop the random shutdowns.
It may also be worth updating the phones firmware but this is a fairly risky procedure that can cause more problems than it solves.

Wouldn't jvm slow down programs?

Hey, I have a question? Wouldn't the virtual machine slow down the program you are writing...because the code has to go through a whole nother layer instead of being compiled straight to assembly like C...

Hey, I have a question? Wouldn't the virtual machine
slow down the program you are writing...because the
code has to go through a whole nother layer instead
of being compiled straight to assembly like C...It's not that simple.
* That layer can be made very thin, so that in most cases the overhead is negligible.
* Modern JVMs use runtime optimization. Compiling C code to native executable means all the optimization will be done at compile time, without the ability to adapt to the runtime environment, execution patterns, etc.
"Is Java slower than C" is a very broad and meaningless question. In the very, very general sense, yes, native code will execute slightly faster than code run by a VM. However, there are many other factors involved, and most of the time the performance difference in either direction is too small to be worth considering.

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

3 month old iMac has slowed down considerably after installing ML

I bought my iMac 3 months ago and installed Mountain Lion last night. Now everything on my Mac has slowed down considerably. From opening the System Settings to opening a page in Safari.
I have MS Word, Excel, Outlook and PowerPoint installed and also VMware Fusion. I have software (CorelDraw) that only runs on Windows (the one I have) therefor the virtual harddrive.
Is this what is causing the problem? If so, how can i uninstall ML to get my computer back to it's previous state.
I am very new to Mac so I don't quite know where to go and how to fix it.

I was just about to write the same problem, but I don't have VMware; my laptop is late 2008 was running Snow Leopard (uptodate version).
I've scientific softwares so probably would require a clean re-installation of ML. I MUST MENTION HERE that those software which were written for PPC will NOT work on ML. Just found out that one of my important softwares version won't work on ML; need $500 to upgrade that software .
Therefore, I'd also want to know how can I go back to SL.
I'll let you know how clean re-installation has worked.

Tdm slow down program after some hours

Similar Messages

Maybe you are looking for