The result of reducing the I/O contention after transferring a group of applications on a single hard disk will be that most applications will malfunction. This is due to lack of a batch file that is necessary to locate and start a program from the location it was initially installed. The fragmentation of files occurs when the computer disk files are broken into speckled parts and hence cause problems with getting access to the data stored in the disk files. The essence of fragmentation of disk is to rearrange files and to eliminate the unnecessary spaces created without stored files (Bocij, Greasley, & Hickie, 2009).
However, fragmentation causes a new data inclusion or exclusion of old important system files. Long delay of file opening, saving and deletion that are on a shared resource, error report messages when trying to connect to a shared source and temporal performance decrease are some additional problems associated with fragmentation. The additional measure that would be favorable in determining that fragmentation is the root cause of occurring system problem is through partition recovery of windows. The partition recovery is used to retrieve important system files before they are lost. Slow shut down time and response, slow boot-up time and response, and system crashing are observable features to note. These features are a sign that fragmentation is the cause of occurring system problems.
When trying to solve fragmentation setbacks, other problems may creep in while doing system evaluations. The most prevalent one that is usually caused by the system analyst is file deletion. The file deletions may be accidental or intentional but either way, most system analysts delete essential system files that are a necessity in the analysis of the re-occurring problem. Another notable problem that emerges from solving fragmentation problem is the antivirus protection that is used. Fraudulent ant-viruses tend to utilize lots of the system memory unnecessarily and therefore could crash system software or halt a number of programs running as a result.
A server with a low running percentage in application but high memory usage could have possible problem that is referred to as a memory leak. Memory leak is when a computer program consumes the memory space but is unable to release it back to the operating system of the computer. This eventually causes system or devices to stop working correctly, hence thrashing the system software.
Another possible cause of huge memory usage could be opening a number of unnecessary applications that are not being used by either the user or the system itself (Curtis & Cob ham, 2008). This in essence utilizes a huge amount of memory and thus causes the system performance to deteriorate. The deterioration slows down a number of other applications and causes the computer to be inefficient.
The additional measure that would be required to spot the exact problem is just through observation and testing of a number of applications. There is no definitive way to spot the exact problem when it comes to memory utilization. Diagnostics are essential to help reduce such occurrences in each start up and shut down encountered.
To solve an exceptionally slow response time in an ERP diagnostics is usually and necessarily of great importance. Keenness is also a key thing because an eventuality in an ERP could case more problems. SAP ERP system could have problems on several levels. Its complex structure could eliminate the security aspect required. ERP is mostly available in a closed world like a company and has different vulnerabilities on levels from the network to the application. Another aspect that causes problems in ERP is the rare update by the administrator. Different languages, technologies and platforms may also be another source of the problem.
The other source of a slow response time problem is the use of different architecture, different operating systems, different databases, different product versions and high amount of customization. To analyze and make a secure ERP system, five steps are necessary. These are development of secure software, secure implementation of the software, training the administrators, increment user awareness and finally control of the whole process (Wigand, Mertens, Bodendorf, König, Picot, & Schumann, 2003).
To solve the slow response time, the help desk personnel needs to monitor and analyze all the procedure involved. However, the help desk personnel as the administrator should check communication channel functionalities. He/she should diagnose the protocols efficiency in the entire system communication channel. Afterwards, he or she should check if their client-server protocols are in the third party technology. Then create a firewall on the vulnerability point that is on display. Finally, be on alert on any impending point of vulnerabilities. This will open up a broader perspective to eliminate any available weak point that will saddle the ERP.
When everyone has a slow response time the direct cause is the architecture. In architecture, the tight inter-dependencies linking different tiers insinuate that a problem in one tier can influence the other tiers. Consequently, causing an insignificant plunge in the performance on one of the application tiers can result in an administrator having a lot of trouble (Bocij, Chaffey, Hickie,& Greasley, 2006). The trouble sets the slow response time noted. In this scenario, the administrative challenge is how quickly to spot out the problem and resolve it quickly to ensure high uptime.
The other possible ways the administrator can try to solve the slow response time is to analyze the operating system’s response time. He or she should then check the buffer quality of each field with its dependant parameters involved. Another thing the administrator could do is to analyze the database response time, check the data buffer quality, and analyze the logical reads Ratio. The wait time, number of user calls, shared pool cache, sort usage and redo logging should have an optimum efficiency to enable al these diagnostics to take place.
All the computer problems diagnosed are eligibly workable for certain systems only. Reason being with the changing technological trend and upgrade of software, more problems will emerge that will require different approaches. Therefore, more hardware and software complexities are expected in the near future.
Bocij, P., Chaffey, D., Hickie, S., & Greasley, A. (2006). Business information systems: technology, development and management for the e-business. New York, NY: Financial Times/ Prentice Hall.
Bocij, P., Greasley, A., & Hickie, S. (2009). Business information systems: technology, development and management. New York, NY: Pearson Education, Limited.
Curtis, G., & Cob ham, D. (2008). Business Information Systems: Analysis, Design and Practice. New York, NY: Pearson Education
Wigand, R. T., Mertens, P., Bodendorf, F., König, W., Picot, A., & Schumann, M., (2003). Introduction to business information systems. Chicago, IL: Springer.