|
|
|
Accumulation of files effecting system performance Over the last week or so I have surveyed approximately, 200 S64 sites with SRS. I have attempted to find out how much attention needs to be paid to the accumulation of unnecessary files on the C:\ drive and in some cases the D:\ drive. Of the approximately 200 S64s surveyed, 44 of them had some form of file issue. These issues ran the gamut from, hiberfil.sys files, to a large accumulation of IRSLOGs, as well as .ar files.
The other location that can produce a large number of files is, C:\WINNT\system32\logfiles\W3SVC1, a logfile is produced daily and placed here, they can very greatly in size from 2k to 2meg, they can accumulate to 1Gig or more. Any of the files located here labeled ex(date stamp).log can be deleted.
In a few cases I was not able to view the C:\TEMP directory, the system would count to 7000+ files and continue to parse for a long time, never displaying the contents of the file. This would tend to indicate that, most probably,a large number of .tmp or other files residing here that need to be dealt with before a problem arises.
Finally, on the D:\ drive, we now have a new opportunity for file accumulation. There is a Dynamic Backup that is generated on the newer software levels (VB30, VA11), this backup is stored on the D:\ drive. If the system operates properly, when a Dynamic Backup is made, it is put on the D:\ drive, the oldest Dynamic Backup should be automatically deleted, leaving only a maximum of 3 of these backups on the D:\ drive at any one time. On some systems, there is a glitch in the delete function that causes these files to accumulate, instead of deleting them. These are large files and can accumulate quickly causing the same issues, system slow down, etc, that we run into with a clogged up C:\ drive.
I know that some of you are already checking the systems routinely for accumulation of unwanted files, when you use SRS, keep up the good work. I would recommend that, as a rule, anytime you access a system (E16 with IRS3, S10,16, 40, 64, Def) that you check the systems for excess files.
If you are going to, or have changed a computer in the IRS, please be aware that the possibility exists that the IRSLOG files may, in fact, be transferred to the C:\Somaris\service\extract file.
I have been able to correlate the presence of these files with the replacement of an IRS computer using theservice calls in SAP. In other instances, it seems that the files are randomly dumped, with the only indication being the "low memory" message or "transferring IRS logs" in the EVENT LOG. You can proactively delete the IRSLOGs remotely, by using the File and Image Tools in the
Service platform and identify other potential file issues that may exist on the system. The more proactive we can be with this the greater the impact on, yes, I am going to say it, customer satisfaction.
|
|
发表于 2016-11-18 07:12:16
发表于 2017-3-7 14:58:08
