Supplemental documentation are expanded sections of the GemStone/S documentation, that provide more details than can be included in the main set of documentation, or are of specialized use, or provide general starting points for understanding and using a feature rather than a detailed and specific set of instructions.

Supplemental documentation is maintained and expected to work in the most recent product versions, but may contain output from older versions or not include newly implemented features.

Tech tips are guidelines and rules of thumb that apply to GemStone/S development and administration. These are not maintained but contain useful information.

Supplemental Documentation

Debugging

  • Object State Change Tracking using Tranlog Analysis

    GemStone’s transaction logs (tranlogs) hold the details of GemStone commits: which includes the full details of object creation and object modification. By analyzing transaction logs, you can determine which user and when a specific change in any object in your repository was made.
    This is an Appendix of the System Administration Guide in older version of GemStone/S 64 Bit

Optimization

  • Canonical Object Framework

    For objects that have a finite set of possible values (such as Dates), and which are used frequently within an application, it can be useful to canonicalize the instances, and so reduce the number of duplicate instances. The Canonical Object Framework provides a framework to implement canonicalization for instances in your application environment.

TechTips

Configuration

  • Tip: Netldi Port Use

    Describes how the netldi uses ports during the login process, and with advice for configuring port use to accomodate firewalls.

Performance and Tuning

  • Tip: Tuning the NotConnected Set

    In 32-bit GemStone/S, the NotConnectedSet avoids constraints on gem memory, at the risk of causing unexpected repository growth. This tip describes how to diagnose and avoid problems related to the NotConnectedSet. 32-bit GemStone/S only

Debugging

  • Tip: Diagnosing Out-of-Memory Errors

    In GemStone/S 64 Bit, it is a fatal error when a gem runs out of memory. You need to configure the amount of temporary memory per gem, and write your application to keep the memory requirements reasonable. This tip describes how to go about this.

  • Tip: How to Get a Stack Trace on Windows

    Diagnosing internal errors may require C level process stack traces. While UNIX platforms have built-in tools, Windows requires using WinDbg. This tip provides instructions on how to install WinDbg and get a server stack trace on Windows.

  • Tip: Debugging RPC Logins

    A step-by-step description of the interprocess communications involved in an RPC login, helpful when encountering errors during login. This document is somewhat out of date, (the PageManager now offloads some of the Stone’s tasks), but overall steps remain the same.

  • Tip: Remote Linked Logins

    A step-by-step description of the interprocess communications involved in a remote linked login, helpful when encountering errors during login. This document is somewhat out of date (the PageManager now offloads some of the Stone’s tasks), but overall steps remain the same.