Computer Associates SQLSTQ99000600 Diagnostics Guide - Page 27

A Change in the Environment, Identify Potential Causes, Basic Troubleshooting - review

Get Computer Associates SQLSTQ99000600 - Unicenter SQL-Station 6.0.0 PDF manuals and user guides
UPC - 757943257441
View all Computer Associates SQLSTQ99000600 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

Identify Potential Causes A Change in the Environment When you identified your environment, you should have listed both the version level and most recently applied patch level for both the affected software and operating system. Review this list and identify what might have changed or what should have changed. This includes: „ Recent upgrades to the operating system, hardware, or software. Verify that the new version is supported by your version of Unicenter. „ Inconsistent patch application. If upgrade patches were applied to two out of three machines, does the problem correspond to the pattern patch application? In other words, if the problem affects only the machine without the patches and not the updated machines, it is likely that applying the missing patch will fix the problem. „ Incorrect patch application. If there are a number of functional and nonfunctional machines that are on the same patch level, the machines displaying the problem may not have the patch correctly applied. Note: If you installed software patches using the applyptf utility, you can also use that utility to list all patches added to the system. This is true for both Windows and UNIX. Tips on locating and reading the applyptf history file can be found in the "Tools" chapter. „ Inconsistent version levels. Are you running multiple releases of the same software on different components? „ Deleted, new, or newly renamed machines. For example, if you have changed the name of the Scalability Server machine you will need to run either the umsetw16.exe or unmsetdos.exe command in order to update this information for the agents which ordinarily connect to that sector. Changes to any part of your enterprise can affect other areas in ways that you may not expect. Therefore, you need to find out what changed and when. In addition to hardware, software, and operating system changes you should identify changes to the following: „ Component profiles (such as users, users groups, computers and computer groups „ Configuration files „ Security and access rights „ Other software that recently has been installed (for example, virus scanning software or security software) „ OS configuration (such as registry changes or anything reported in a winmsd report) Chapter 4: Basic Troubleshooting 4-5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
Identify Potential Causes
A Change in the Environment
When you identified your environment, you should have listed both the version
level and most recently applied patch level for both the affected software and
operating system. Review this list and identify what might have changed or
what should have changed. This includes:
Recent upgrades to the operating system, hardware, or software. Verify
that the new version is supported by your version of Unicenter.
Inconsistent patch application. If upgrade patches were applied to two out
of three machines, does the problem correspond to the pattern patch
application? In other words, if the problem affects only the machine
without the patches and not the updated machines, it is likely that
applying the missing patch will fix the problem.
Incorrect patch application. If there are a number of functional and non-
functional machines that are on the same patch level, the machines
displaying the problem may not have the patch correctly applied.
Note:
If you installed software patches using the applyptf utility, you can
also use that utility to list all patches added to the system. This is true for
both Windows and UNIX.
Tips on locating and reading the applyptf history
file can be found in the “Tools” chapter.
Inconsistent version levels. Are you running multiple releases of the same
software on different components?
Deleted, new, or newly renamed machines. For example, if you have
changed the name of the Scalability Server machine you will need to run
either the umsetw16.exe or unmsetdos.exe command in order to update
this information for the agents which ordinarily connect to that sector.
Changes to any part of your enterprise can affect other areas in ways that you
may not expect. Therefore, you need to find out what changed and when. In
addition to hardware, software, and operating system changes you should
identify changes to the following:
Component profiles (such as users, users groups, computers and computer
groups
Configuration files
Security and access rights
Other software that recently has been installed (for example, virus
scanning software or security software)
OS configuration (such as registry changes or anything reported in a
winmsd report)
Chapter 4: Basic Troubleshooting
4–5