synchronization of log file event

Similar Questions

• Expectations extended on synchronization of log file while the parallel writing journal is fine

  We have 9.2.0.8 as experiences of long waits on the database log file sync (average waiting time = 46 ms) while waiting for the log file write Parallels is very good (average waiting time is less than 1 millisecond).

  The application is of type middleware, it connects to several other applications. A single user in a single application action train several requests to send back through this middleware, so he needs response time of db in milliseconds.

  The database is quite simple:

  -It has a few config tables that the application reads but rarely updated

  -She has table TRANSACTION_HISTORY: the application inserts records into this table using Insert einreihig (about 100 lines per second); each insert is followed by a validation.

  Records are kept for several months and then purged. The table has only column VARCHAR2/NUMBER/DATE, no LOBS, LONG, etc. The table has 4 non-unique single-column index.

  The average line length is 100 bytes.

  The load profile does not appear something unusual, the main figures: 110 transactions per second average transaction = 1.5 KB size.

  The data below are to 1 hour interval (purge wasn't running during this interval), physical reads or writes physical rate is low:

  Load profile

  ~ ~ ~ Per second per Transaction

  ---------------       ---------------

  Size: 160,164.75 1,448.42

  Logical reads: 521,58 57 675,25

  Block changes: 934,90 8.45

  Physical reads: 76,27 0.69

  Physical writings: 86,10 0.78

  Calls of the user: 491,69 4.45

  Analysis: 321,24 2.91

  Hard analysis: 0.09 0.00

  Kinds: 126.96 1.15

  Logons: 0.06 0.00

  Runs: 17.70 1 956,91

  Operations: 110,58

  
  

  Top 5 events are dominated by the synchronization of log file:

  Top 5 timed events

  ~~~~~~~~~~~~~~~~~~                                                     % Total

  Event expects Ela time (s)

  -------------------------------------------- ------------ ----------- --------

  401 608 18 448 59.94 file synchronization log

  db file parallel write 124 044 3 404 11.06

  CPU time                                                        3,097    10.06

  Enqueue 10 476 2 916 9.48

  DB file sequential read 261 947 2 435 7.91

  
  

  Section events:
  

  AVG

  Total wait wait wait

  Hour of wait time wait for the event (s) (ms) /txn

  ---------------------------- ------------ ---------- ---------- ------ --------

  Synchronize 0 401 608 46 18 448 1.0 file log

  db file parallel write 124 044 0 3 404 27 0.3

  Enqueue 10 476 277 2 916 278 0.0

  DB file sequential read 261 947 0 2 435 9 0.7

  buffer busy waits 11 467 67 173 15 0.0

  SQL * Net more data to the client 1 565 619 0 79 0 3.9

  lock row cache 2 800 0 52 18 0.0

  control file parallel write 1 294 0 45 35 0,0

  Log end of switch file 261 0 36 138 0.0

  latch free 2 087 1 446 24 12 0.0

  PL/SQL 1 1 20 19531 0,0 lock timer

  log file parallel write 0 143 739 17 0.4 0

  db file scattered read 1 644 0 17 10 0.0

  sequential log file read 636 0 8 13 0.0

  
  

  Log buffer is about 1.3 MB. We could increase the log buffer, but there is no log buffer space waits, so I doubt this will help.

  
  

  Newspapers in recovery have their own file systems, not shared with the data files. This explains the difference between waiting avg on parallel writing of log (less than 1 ms) file and db file parallel write (27 ms).

  Restoring logs is 100 MB, there are about 120 journal switches per day.

  
  

  What has changed: the pads/validations rate grew. Several months ago there were 25 inserts/validations per second in the TRANSACTION_HISTORY table, now get us 110 inserts/validation per second.

  
  

  What problem it causes application: due to slow down the reaction of the basis of the application (Java-based) requires discussions more and more.

  
  

  MOS documents on synchronization of log file (for example, 1376916,1 waits for troubleshooting "log file sync") recommend to compare the average waiting time on synchronization of log file and the log file parallel write.

  If the values are close (for example log file sync = 20 ms and log file parallel write = 10 ms) so expectations are caused by nits IO. However, it is not the case here.

  
  

  There was a bug (2669566) in 9.2 which resulted in underreporting lgwr parallel time of writing to the log file. I was talking about September 2005, during which the bug was present in 9.2.0.6, reported 10.1 fixed in: file parallel journal written (JL Comp) it is possible that your problem IS written to the log file.

  Concerning

  Jonathan Lewis

• synchronization of log file much larger than log file parallel write

  Hi all

  average of log file sync wait is 30 ms log file parallel write is only 10 ms, this mean? What are the main reasons for this difference?

  Sincerely yours.

  A. U.

  Hello

  average of log file sync wait is 30 ms log file parallel write is only 10 ms, this mean? What are the main reasons for this difference?

  Essentially, when newspaper writer writes, several session may be waiting. During 10 ms of time, you can have a written lgwr and sessions of 3 user waiting on the 'log file sync '.

  Kind regards

  Franck.

• Events of waiting "log file parallel write" / "log file sync", in CREATE INDEX

  Hello guys,.
  my current project I'm running a few tests of performance for oracle data guard. The question is "How LGWR SYNC transfer influence the performance of the system?"
  For the performance of the values, that I can compare I just built a normal oracle database in the first step.
  
  Now I perform various tests such as creating index 'broad', massive parallel inserts/validations, etc to get the marks.
  
  My database is an oracle 10.2.0.4 with multiplexed on AIX log files.
  
  I create an index on a table of "normal"... I have run "dbms_workload_repository.create_snapshot ()" before and after the CREATE INDEX for an equivalent period for the AWR report.
  Once the index is built (round about 9 GB), I made an awrrpt.sql for the AWR report.
  
  And now take a look at these values of the AWR

                                                                     Avg
                                               %Time  Total Wait    wait     Waits
  Event                                 Waits  -outs    Time (s)    (ms)      /txn
  ---------------------------- -------------- ------ ----------- ------- ---------
  ......
  ......
  log file parallel write              10,019     .0         132      13      33.5
  log file sync                           293     .7           4      15       1.0
  ......
  ......

  How can it be possible?
  
  With regard to the documentation
  
  -> synchronization of log file: http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm#sthref3120

  Wait Time: The wait time includes the writing of the log buffer and the post.

  -> log file parallel write: http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm#sthref3104

  Wait Time: Time it takes for the I/Os to complete. Even though redo records are written in parallel, the parallel write is not complete until the last I/O is on disk.

  This was also my understanding... "log file sync" wait time should be higher than the 'parallel log writing' timeout, because of, it includes the e/s and the response time for the user's session.
  I could accept it, if the values are near each other (perhaps around 1 second about altogether)... but the difference between 132 and 4 seconds is too visible.
  
  Is the behavior of the log file sync/write different when you do a DOF as CREATE INDEX (maybe async... like you can influence it with COMMIT_WRITE initialization parameter?)?
  You have no idea how these values born?
  
  
  Ideas/thoughts are welcome.
  
  Thanks and greetings
  

• "redo the write time" includes "log file parallel write".

  IO performance Guru Christian said in his blog:
  
  http://christianbilien.WordPress.com/2008/02/12/the-%E2%80%9Clog-file-sync%E2%80%9D-wait-event-is-not-always-spent-waiting-for-an-IO/
  
  Waiting for synchronization of log file can be divided into:
  1. the 'writing time again': this is the total elapsed time of the writing of the redo log buffer in the log during recovery (in centisecondes).
  2. the 'parallel log writing' is actually the time for the e/s of journal writing complete
  3. the LGWR may have some post processing to do, signals, then the foreground process on hold that Scripture is complete. The foreground process is finally awake upward by the dispatcher of system. This completes pending "journal of file synchronization.
  
  In his mind, there is no overlap between "redo write time" and "log file parallel write.
  
  But in the metalink 34592.1:
  
  Waiting for synchronization of log file may be broken down into the following:
  1 awakening LGWR if idle
  2 LGWR gathers again to be written and issue the e/s
  3. the time for the IO journal writing complete
  4 LGWR I/O post processing
  ...
  
  Notes on adjustment according to log file sync component breakdown above:
  Steps 2 and 3 are accumulated in the statistic "redo write time". (that is found in the SEO Title Statspack and AWR)
  Step 3 is the wait event "log file parallel write. (Note.34583.1: "log file parallel write" reference Note :) )
  
  MetaLink said there is overlap as "remake the writing time" include steps 2 and and "log file parallel write" don't understand step 3, so time to "log file parallel write" is only part of the time of 'redo write time. Won't the metalink note, or I missed something?
  

• log files synchronization problem

  Oracle 11.2.0.1
  IBM AIX - 6.1 and 7 power machine with 64 GB of memory.
  32 processors logical and 8 more physical...
  
  Here is the excerpt of 20 minutes AWR report, DB time is 132,95 (mins).
  

  Top 5 Timed Foreground Events
  
  
  Event                  Waits               Time(s)      Avg wait (ms)     % DB time              Wait Class 
  log file sync       1,769,997              3,939                    2            52.38                   Commit 

  Machine is not exchanging the process... From what I understand, the log file parallel write should offset a significant part of the time for synchronization of the log file.
  
  Currently the log file sync take a total of 3 939 seconds while the log file parallel write takes a total of seconds 299.
  
  
  I went thro different blogs on this event, checked the CPU use/machine Swap/memeory etc... All thoughts to settle this one because I'm out of ideas.
  
  
  Thanks for your time...

  It might be useful to define the 'batch validation' on. If you accept the possible risk of course...

• Mail creation of massive log files and stop the synchronization with the server

  Since the upgrade to El Capitan (10.11.1), Mail presents two problems persist:

  (1) it generates massive log files, e.g. 2015-12 - 03_IMAPSyncActivity.log these files regularly exceed 10 GB and block Mail and freeze the Mac. Mail can be over 8 GB of RAM. Once removed, Mail recreates the file and fills again, ends up doing more massive files that must also delete.

  (2) mail stop sync with my different IMAP e-mail servers. The only solution I've found that it completely delete the or the e-mail accounts and reinstalls the account. It works for a day (or even a few hours) before it just stops the synchronization, even if a connection test shows he connects with the server. This problem seems to occur on two e-mail accounts separately on two different servers / hosting companies, but not on my Gmail accounts.

  These two problems occur on both my iMac (21.5 ", mid-2011, 2.5 GHz Intel Core i5, 8 GB RAM) and MacBookPro (13', mid-2011, 2.5 GHz Intel core i5, 4 GB RAM).

  Full of ideas gratefully received!

  Thank you!

  Please take these steps to remove the mail folders 'sandbox '.

  Step 1

  Back up all data.

  Triple-click anywhere in the line below on this page to select this option:

  ~/Library/Containers/com.apple.mail

  Right-click or Ctrl-click on the highlighted line and select

  Services ▹ Reveal

  the contextual menu.* A Finder window should open up with a folder named "com.apple.mail" selected. If this is the case, move the selected folder - not only its content - on the desktop. Open the window Finder for now.

  Restart the computer. Launch Mail and test. If the problem is resolved, you may have to re-create some of your e-mail settings. Any writing paper custom that you created may be lost. Ask for instructions if you want to keep these data. You can then delete the folder that you moved and close Finder.

  CAUTION: If you change the content of the sandbox, but leave the folder itself in place, Mail may hang or starts any. Remove the tray to sand everything will be rebuilt automatically.

  Step 2

  If step 1 does not resolve the problem, repeat with this line:

  ~/Library/Containers/com.apple.MailServiceAgent

  * If you do not see the item context menu copy the selected text in the Clipboard by pressing Control-C key combination. In the Finder, select

  Go ▹ go to the folder...

  from the menu bar and paste it into the box that opens by pressing command + V. You won't see what you pasted a newline being included. Press return.

• Try to collect events to a log file and the Agent installed Linux and work - need help.

  I modified liagent.ini by documentation... If I understand well it... actually I changed so many times my eyes hurt.

  Here it is:

  ; Configuration of the Agent of VMware Log Insight. Please save it in UTF-8 format if you use non-ASCII names / values!

  ; The actual configuration is this file that is associated with the server settings to form animal - effective .ini

  ; Note: The agent is not necessary to restart after making a configuration change

  ; Note: It may be more efficient to configure Server Agents page!

  [Server]

  hostname = 192.168.88.89

  ; Name of host or IP of your Server Log Insight / load balancing cluster. By default:

  ; hostname = LOGINSIGHT

  ; Protocol can be cfapi (Log Insight REST API), syslog. By default:

  proto = cfapi

  ; Server port connect Insight to connect to you. Default ports for protocols (TCP all):

  ; syslog: 514; syslog with ssl: 6514; cfapi: 9000; cfapi with ssl: 9543. By default:

  port = 9000

  ; Use SSL. By default:

  SSL = no.

  ; Example of configuration with the certification authority:

  ; SSL = yes

  ; ssl_ca_path=/etc/PKI/TLS/certs/CA.PEM

  ; Time in minutes to force the reconnection to the server.

  ; This option reduces the imbalances caused by the long lifetime as TCP connections. By default:

  Reconnect = 30

  [record]

  ; Logging detail level: 0 (no debug messages), 1 (essentials), 2 (verbose with more impact on performance).

  ; This option should always be 0 in normal conditions. By default:

  debug_level = 1

  [storage]

  ; Local max storage expiration (data + logs) in the valid range MBs.: 100-2000 MB.

  max_disk_buffer = 2000

  ; Uncomment the appropriate section to collect log files

  ; The recommended method is to activate the content pack Linux server LI

  [filelog | bro]

  Directory = / data/bro/newspapers/2015-03-04

  ; include = * .log

  parser = auto

  
  

  
  

  I post it here, I have created a support pack?

  
  

  Post edited by: I added a screenshot of the status of the personnel of kevinkeeneyjr

  Post edited by: kevinkeeneyjr added liagent.ini

  Ah! Yes, the agent is to collect real-time events. If no new event is written then it won't work. If you want to collect logs that have been generated before you use the importer of Log insight which was published with LI 3.3. I hope this helps!

• Questions looking for events from a log file

  I have the windows agent installed on some servers to monitor log files and run into problems trying to find specific events.  I can see the events under HERE if I do a host name contains the name of the server, but if I then try to filter or search who, following the events specific to find I get no results.  Also even when I'm filtered by host name and can view event I want to if I highlight and select "Contains: the data I want" she returned with no results.

  Another experience that or I do something wrong?

  Okay, after review, it appears that the journal file is in UCS - 2 format. By default, the agent LI uses UTF - 8. The agent also supports UTF-16, which is the most recent version of THE of UCS - 2 (which has been deprecated in 1996). In the filelog liagent.ini you try to add:

  charset = UTF16 - THE

  Let me know if you have any additional questions! If your question is answered can you please mark as answer?

• Check alert event ends in error, the log file has no error message

  Hello
  
  We are 11.5.10 in 12.1.3 reclassification. Check alert event ends in error, the log file does not have any information. This alert is on. oe_order_headers_all alert works well in 11i.
  
  12.1.3
  Database 10g
  
  Enjoy all the entries.
  
  I noticed that the operating unit parameter is passed as NULL, don't know if this is causing the problem.
  
  K

  926765 wrote:
  Hello

  We are 11.5.10 in 12.1.3 reclassification. Check alert event ends in error, the log file does not have any information. This alert is on. oe_order_headers_all alert works well in 11i.

  12.1.3
  Database 10g

  Enjoy all the entries.

  I noticed that the operating unit parameter is passed as NULL, don't know if this is causing the problem.

  K

  Please see if (OE_ORDER_HEADERS_ALL (check event Alert) ends in error for all orders introduced [1322052.1 ID]) help.

  Thank you
  Hussein

• long log file sync waits

  Hello
  
  I am trying to improve the performance of a 10.2.0.5 database who is suffering from the high value of the log file sync wait. AWR reports show that it is almost never less than 20% of the time of database, normally it is 20-30%, and it is consistently above not-idle wait event. Many sessions he takes 80-90% of the time or more.
  
  Log file parallel write is an order of magnitude lower, probably isn't an I/O problem. The database performs about 100 commits per second, the ratio of user-call-to-commit is about 20, again generated 500 k/s, log buffer is big 14 MB. There are about 6-7 journal file switches per hour on average.
  
  There are several oddities on log file sync wait here and I'd appreciate any help unravel them:
  
  1) there are almost two file sync wait events in the log by a posting on average (number of parallel expectations of log file is about the same number of validations). Why?
  (2) according to the ASH, nearly half of log file sync waits take near Ms. 97.7 is something special reason for this pic?
  (3) approximately 0.5% of the log file sync waits captured by ASH see the multisecond wait times. No idea where they may come from or how to diagnose this kind of problem?
  
  Some parts of an AWR report below, please let me know if anything else is needed.
  
  Best regards
  Nikolai
  

  Cache Sizes
  ~~~~~~~~~~~                       Begin        End
                               ---------- ----------
                 Buffer Cache:    44,592M    44,672M  Std Block Size:        16K
             Shared Pool Size:     3,104M     3,024M      Log Buffer:    14,288K
  
  Load Profile
  ~~~~~~~~~~~~                            Per Second       Per Transaction
                                     ---------------       ---------------
                    Redo size:            545,833.77              6,659.29
                Logical reads:            225,711.23              2,753.73
                Block changes:              1,788.11                 21.82
               Physical reads:              1,195.98                 14.59
              Physical writes:                119.02                  1.45
                   User calls:              2,368.64                 28.90
                       Parses:                737.35                  9.00
                  Hard parses:                 94.58                  1.15
                        Sorts:                261.75                  3.19
                       Logons:                  5.93                  0.07
                     Executes:              1,796.12                 21.91
                 Transactions:                 81.97
  
  Top 5 Timed Events                                         Avg %Total
  ~~~~~~~~~~~~~~~~~~                                        wait   Call
  Event                                 Waits    Time (s)   (ms)   Time Wait Class
  ------------------------------ ------------ ----------- ------ ------ ----------
  CPU time                                         23,580          19.8           
  log file sync                       491,840      21,976     45   18.5     Commit
  db file sequential read           1,902,069      12,604      7   10.6   User I/O
  read by other session               743,414       4,159      6    3.5   User I/O
  log file parallel write             220,772       3,069     14    2.6 System I/O
  
            -------------------------------------------------------------       
  
  Instance Activity Stats            ******************
  
  Statistic                                     Total     per Second     per Trans
  -------------------------------- ------------------ -------------- -------------
  Cached Commit SCN referenced                 11,130            3.1           0.0
  Commit SCN cached                                 3            0.0           0.0
  DB time                                  12,547,531        3,483.3          42.5
  DBWR checkpoint buffers written             145,437           40.4           0.5
  DBWR checkpoints                                  6            0.0           0.0
  ...
  IMU CR rollbacks                              2,566            0.7           0.0
  IMU Flushes                                  36,411           10.1           0.1
  IMU Redo allocation size                187,480,124       52,045.3         635.0
  IMU commits                                 255,350           70.9           0.9
  IMU contention                               11,998            3.3           0.0
  IMU ktichg flush                                 11            0.0           0.0
  IMU pool not allocated                        4,295            1.2           0.0
  IMU recursive-transaction flush                 175            0.1           0.0
  IMU undo allocation size              2,029,937,952      563,519.5       6,875.1
  IMU- failed to get a private str              4,295            1.2           0.0
  ...
  background checkpoints completed                  6            0.0           0.0
  background checkpoints started                    6            0.0           0.0
  background timeouts                          11,400            3.2           0.0
  ...
  change write time                             9,398            2.6           0.0
  cleanout - number of ktugct call             54,233           15.1           0.2
  cleanouts and rollbacks - consis              9,436            2.6           0.0
  cleanouts only - consistent read              2,028            0.6           0.0
  ...
  
  Instance Activity Stats            *******************
  
  Statistic                                     Total     per Second     per Trans
  -------------------------------- ------------------ -------------- -------------
  commit batch performed                           61            0.0           0.0
  commit batch requested                           61            0.0           0.0
  commit batch/immediate performed                 94            0.0           0.0
  commit batch/immediate requested                 94            0.0           0.0
  commit cleanout failures: block                  51            0.0           0.0
  commit cleanout failures: buffer                 14            0.0           0.0
  commit cleanout failures: callba              8,632            2.4           0.0
  commit cleanout failures: cannot             10,575            2.9           0.0
  commit cleanouts                            991,186          275.2           3.4
  commit cleanouts successfully co            971,914          269.8           3.3
  commit immediate performed                       33            0.0           0.0
  commit immediate requested                       33            0.0           0.0
  commit txn count during cleanout             61,737           17.1           0.2
  ...
  redo blocks written                       4,078,889        1,132.3          13.8
  redo buffer allocation retries                  177            0.1           0.0
  redo entries                              1,924,106          534.1           6.5
  redo log space requests                         174            0.1           0.0
  redo log space wait time                      2,333            0.7           0.0
  redo ordering marks                           4,553            1.3           0.0
  redo size                             1,966,229,700      545,833.8       6,659.3
  redo subscn max counts                       38,227           10.6           0.1
  redo synch time                           2,233,166          619.9           7.6
  redo synch writes                           352,935           98.0           1.2
  redo wastage                             56,259,980       15,618.0         190.5
  redo write time                             316,495           87.9           1.1
  redo writer latching time                        19            0.0           0.0
  redo writes                                 220,866           61.3           0.8
  rollback changes - undo records                 134            0.0           0.0
  rollbacks only - consistent read             11,242            3.1           0.0
  ...
  
  ...
  transaction rollbacks                            94            0.0           0.0
  transaction tables consistent re                 25            0.0           0.0
  transaction tables consistent re              8,704            2.4           0.0
  undo change vector size               1,176,156,772      326,506.2       3,983.5
  user I/O wait time                        2,039,881          566.3           6.9
  user calls                                8,532,422        2,368.6          28.9
  user commits                                295,139           81.9           1.0
  user rollbacks                                  122            0.0           0.0
  ...
            -------------------------------------------------------------       

  High "log file synchronization" waits arise also when LGWR is unable to get the CPU to republish on the boy that the log write is complete. The boy expected this event until LGWR may be a sign but if LGWR is unable to get the CPU, it is unable to signal quite quickly.

  8 processors for 1 hour is 28 800 seconds. 7 UC is an odd number. This is equivalent to 25 200 seconds available. Your AWR shows that Oracle has represented time seconds 23 580 CPU. So, your server is probably encounter situations where processes are unable to get the CPU.

  You can pin or renice LGWR - but you need to check with Oracle Support if this is doable on your platform or supported.

  What you need to do is to adjust the sessions that make very high logical reads (a simple rule is 10 k blocks per CPU per second and you hit 225 K blocks for 7 processors!) to reduce the logical reads and CPU consumption.
  OR add more CPU.

  Hemant K Collette
  http://hemantoracledba.blogspot.com

  Hemant K Collette

• Question about a config/95 G log file: LabView_32_11.0_Lab.Admin_cur.txt

  Hello world

  One of our lab computers running Labview has been reported to be running out of storage and asked me to figure out why. I scratched through some windows folders to find the culprit, specifically folder: c:\users\Lab.Admin\AppData\Local\Temp where I found a 95 G file titled LabView_32_11.0_Lab.Admin_cur.txt, I noticed that the Lab.Admin is the user name and is also included in the name of the file, so I guess it's sort of config/log file for the current user.

  The file was too large for me to open and watch with no matter what program I had available so I just renamed, restarted Labview to check that it might be recreated then removed the bloated file. The newly created file has the following inside the itt:

  ####
  #Date: Wednesday, June 13, 2012 14:49
  #OSName: Windows 7 Professional
  #OSVers: 6.1
  #OSBuild: 7600
  #AppName: LabVIEW
  #Version: 11.0 32-bit
  #AppKind: FDS
  #AppModDate: 22/06/2011 18:12 GMT
  Base address of #LabVIEW: 0x00400000

  Can someone tell me the purpose of this file and what might have caused to grow to 95 G. I'm only interested in learning how to prevent it happening again.

  See you soon,.

  Alex

  Do you mean 95 gigabytes?  95 GB?

  I think that it's a crash dump file in the event where LabVIEW detects an error.  Could you have had a recent accident (perhaps several) where some large scale applications have been involved?

  You can use LabVIEW to open the file.  Write a small VI to open the text file, then just read a smaller number of bytes and display it in an indicator of the chain.

  I have several of these files in my temp directory from to the slightly different versions of LabVIEW installed.  But they are tiny, about 1 KB.

• log file curious growing on rt-target

  Hello community,

  I have a pxi-time real-system that automatically records the events our network multicast and creates a log file that grows every minute.

  The file is named packetsIn.log and appears under/or-rt/system/ethernet.

  The content of the file is

  Source Mac:...

  Dest Mac:...

  PacketSize:...

  The mac addresses that appear in the file are not of my controller but some switches or multicast-addresses of our network.

  If you delete the file, it appears again a few seconds after the action. The file grows too, if no labview applications are running on the system.

  A that someone has noticed similar behaviour? What could cause the creation of this file?

  We use LabVIEW 2009 SP1 and the curious, it's, it appears only in one of our controllers.

  Hope someone could help me

  Ayoub

  Hi ayoub,.

  Please try opening the nor - rt.ini and the following entry set:

  [DEBUG]
  RTPacketParsingEnbled = FALSE

  After that the file should stop more.

  Best regards

  Lam

• The event log shows event 11 atapi: the driver has detected an error in the controller on \Device\Ide\IdePort1

  Intermittent crashes. The event log shows event 11 atapi: the driver has detected an error in the controller on \Device\Ide\IdePort1. How can I find this device? This is probably a hardware problem?

  I look at intermittent crashes, where my cursor becomes an hourglass and the system does not yet meet the ctrl-alt-delete.  In the case of a newspaper, I find

  Event 11 atapi: the driver has detected an error in the controller on \Device\Ide\IdePort1.

  How can I determine which physical devices this is associated?  This indicates a hardware problem, or driver or firmware may be the source? The system has worked very well for a few years.  I'm not aware of any change in software that took place recently, although I have had by force, remove and reinstall iTunes earlier.

  I run SMART on all players controls and run diagnostics.  I ran chkdsk on the one I found the culprit, but not mistakes.

  Just in case it was a deadlock linked to memory, I tried to use the Diagnostics memory Microsoft on floppy, but it would not write on the disk (even if I could format and copy the files freely).

  Hello

  Go to your configuration and see which drive is for each port; 1,2,3,4...

  Then go to the Device Manager and look at how many SATA controller you have and how many ports for each, then start count from 0 to IdePort0, 1, 2, etc. for each SATA controller, so if you have 4 ports for each SATA controller, here is how you came from:

  IdePort0 1 -, 2 - IdePort1, 3 car - IdePort2 and road 4 - IdePort3 in the order of road by car

  I hope it helps

• Yahoo messinger does not start, he said: "the application failed to start because its side-by-side configuration is incorrect. Check the log of events applications for more details. » __

  Yahoo messinger does not start, he said: "the application failed to start because its side-by-side configuration is incorrect. Check the log of events applications for more details. »

  UM. I have no idea what that means, I never had that in my 20s I was using a computer.  Please help, someone!

  You can get the Chkdsk to run in the General Windows interface by following these instructions?

  Try running ChkDsk to check your drive for errors. Right click on your drive icon / properties / tools / error checking. Try first by checking do not each box (that it will run in read-only mode) to see if it reports any problems file or hard drive. If so, restart it by checking both boxes and restart to allow him to attempt to fix any problems found.

  Your command prompt Mode works without failure or a boot?

  Startup options (including safe mode)
  http://Windows.Microsoft.com/en-us/Windows7/advanced-startup-options-including-safe-mode

  How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
  http://support.Microsoft.com/default.aspx/KB/929135

  It works if you test with another user, you will need to create one to test with?

  System Restore and the System File Checker is able to fix anything?

  How to repair the operating system and how to restore the configuration of the operating system to an earlier point in time in Windows Vista (or 7)
  http://support.Microsoft.com/kb/936212/#appliesTo

  How to use the System File Checker tool to fix the system files missing or corrupted on Windows Vista or Windows 7
  http://support.Microsoft.com/kb/929833

  How to analyze the entries in the log file generating the program Checker (SFC.exe) resources of Microsoft Windows in Windows Vista
  http://support.Microsoft.com/kb/928228#appliesTo

  Have you tested malware?  I see a lot of recommendations here for programs such as -

  Malwarebytes' Anti-Malware
  http://www.Malwarebytes.org/products/malwarebytes_free

  SuperAntispyware
  http://SUPERAntiSpyware.com/