r24 - 2013-07-06 - 15:07:11 - Main.gcovellYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > PerformanceTroubleshooting > PerformanceTroubleshootingSituationTemplate

Performance troubleshooting situation template

Authors: GrantCovell
Build basis: None

  • Directly under the header-title box, there should be a concise page description.
  • Remember that each page should be self-contained. Potential readers may arrive here by Internet search or via a link, and so the page should be reasonably self-explanatory.

Initial assessment

  • Be as specific as possible. These suggested sub-sections may not be relevant or appropriate for each situation. However, please try to specify: application, user role, platform, etc.


  • "When you do X, Y happens"

Impact / scope

  • Does it effect multiple users? A particular type of client?

Timing (when)

  • When did the problem start to occur?
  • Is the problem repeatable?

Environmental changes

  • What sort of things may have changed in the environment (outside the products) to have caused the problem?
  • Hardware / software / network / client

As amnifier technician, using all versions of the Turboencabulator after model H4500, when attempting to process retro-finned cordobite amnifiers with length in the range 2.4 to 7.4 cm, the main sub-control panel reports error -52X-3C immediately upon processing.

Recommended data gathering and subsequent analysis steps

  • Link to other, separate self-contained pages which offer concrete domain analysis (how to analyze AIX lpars, x86 virtualization, JVM heap); use parts of Tox' doc which provides high-level concepts of how things work (authentication, etc.); how to begin to look if you don't understand the whole process.

Understanding Turboencabulator errors of class -52X, Amnifier routines

Possible causes

  • Clearly identify possible causes for the problem.

1) Turboencabulator bearings on the reverse-transfold mechanisms often wear out after 36,000 revolutions, or 2) Main sub-control panel erroneously reports errors when bifold gateway requires updating to patch-level

Possible solutions

  • Clearly identify possible solutions to the problem.

1) Replace the oxoid geframitz chute and the obloid rotator mechanism, or 2) Install patch level or greater

  • Sometimes causes and solutions may go together especially if there's an evident cause and effect.

General comments about content (Ground Rules)

  • Ocean boiling is not allowed. Please be pragmatic. Please be aware that those contributing to this effort are knowledgeable, but this is not anyone's full time job.
  • Content needs to be accurate, true, useful, pragmatic, respectful.
  • All planning, status and wiki-related thoughts need to be done within this wiki. No outside emails, no slide decks, no external .pdfs. We want to use the wiki to demonstrate what we are doing and the best way to do that is to learn to the wiki itself as effectively as possible.
  • Content is in English.
  • Headings and titles should be in sentence case.
  • CLM 4.x is the minimum release version.
  • Be aware that everything added here, all edits and comments are visible and editable by everyone.

Related topics:

  • Performance Troubleshooting
  • Related topics must be ALWAYS part of the wiki; this section should only link to other pages on this wiki
  • ALWAYS link back to the parent Performance Troubleshooting page.
  • For more troubleshooting topics, refer to Performance Troubleshooting.

External links:

  • External links are all links outside the wiki, this includes other pages at jazz.net, ibm.com and all outside pages.
  • Use the format
  • IBM
  • Always be sure the links have http:// in them

Additional contributors: None

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r24 < r23 < r22 < r21 < r20 | More topic actions
Deployment.PerformanceTroubleshootingSituationTemplate moved from Deployment.PerformanceTroubleshootingScenarioTemplate on 2013-07-06 - 15:06 by Main.gcovell -
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.