Known Problems and Unsupported Features

OPE Release Notes

Known Problems and Unsupported Features

OPE Analyzer

8698

The OPE Analyzer (and Server Monitor) display the following message when starting up:
	osopea Warning: locale not supported by C library, 
	locale unchanged
This message can safely be ignored. It disappears completely if the environment variable LC_CTYPE is set to a supported value.

9751

If the X resource borderWidth is set to a value greater than 0 on UNIX/X Windows, the Analyzer does not display various drawing areas correctly.

To work around this problem, set the following variables in your .Xdefaults file:
	osopeax*borderWidth: 0

	osopesx*borderWidth: 0
This can only occur if the OPE configuration (osopesetup config) did not complete successfully; osopesetup installs X application defaults, including borderWidth.

10536

The OpenWindows product, shipped with SunOS 4.1.3, supplies the OpenLook window manager (olwm) and an X server (xnews). The OpenWindows X server, xnews, is started automatically with the openwin command. (You can use the ps auxw command to check whether xnews is running.)

OPE requires an X11R4 or X11R5 X Window server. It does not work with xnews. (The X server that OPE uses is the one running on the computer specified in the DISPLAY environment variable.)

OPE does work with the OpenLook Window manager.

If you attempt to run OPE on an AIX computer and set the DISPLAY environment variable to a SunOS machine on which an xnews server is running, OPE appears to work, but all pop-up dialog boxes will be empty and there will be other problems.

If you do not have an X11R4 or X11R5 X server, you can obtain it by contacting OPE Support (ope-support@odi.com). (Note: the latest version of SunOS, called SunOS 5.4 or Solaris 2, does not include the xnews server that is shipped with SunOS 4.1.3 (and that does not work with OPE). Rather, SunOS 5.4/Solaris 2 includes the X11R5 version of the Xsun server, and it does work with OPE (it is the same server included with OPE in the directory $OS_OPE_ROOTDIR/etc/X11 ).

10344

Running against an X server on SunOS, the Show crosshair item on the Options menu of the OPE Analyzer Page State Diagram does not work.

10692

Under certain circumstances, the OPE retriever shipped with Releases 4.0.0.B or earlier of ObjectStore creates trace files that cannot be formatted. In these circumstances, the formatting process exits due to insufficient memory. For example, the error message on Windows NT is
> osopef -q -ps trace.trf
 	Miscellaneous ObjectStore Error
 	Out of virtual memory: Failed to allocate 1543539395. bytes (err_misc)
This error is caused by an invalid event in the OPE trace file. There is no workaround other than using the OPE Retriever shipped with ObjectStore Release 4.0.0.C (or later).

10721

On Solaris 2, if the X resource fontlist is not defined, the OPE Analyzer and Server Monitor will crash with an X Error:
> osopea
 X Error of failed request:  BadAlloc (insufficient resources for operation)
 	Major opcode of failed request:  45 (X_OpenFont)
 	Serial number of failed request:  56
 	Current serial number in output stream:  57
This can only occur if the OPE configuration (osopesetup config) did not complete successfully; osopesetup installs X application defaults, including fontlist.

11635

Old trace files (from Retrievers shipped with ObjectStore releases earlier than Release 4.0.0.C.) might let the formatter die due to extra \0 characters in the trace file.

12295

On Windows NT/98 the use of a crosshair on the PageState diagram might generate black spots on the Storage area. The next refresh removes these spots.

OPE Server Monitor

10149

In the OPE Server Monitor, there is no meter showing the active clients in the Clients category of the OPE Select Server Meters dialog. As a workaround, you can see the number of active clients with the ossvrstat tool, and also via the API (see ostore/include/dbutil.hh).

OPE Miscellaneous

8686

It is not possible to change the font used by the OPE online help system.

9132

In the online help for the OPE Server Monitor and the OPE Analyzer, if you select a link, the specific help text associated with the link is displayed. If you then go back to the previous screen, either by selecting the << button or Previous Topic, the previously selected link text might be whited out. Although this text is invisible, it can still be selected.

10577

The menu item Help | Using Help in the online help of the OPE Analyzer and OPE Server Monitor does not work.

OPE Documentation

(none)

OPE Retriever

8944

On OS/2, if os_ope::start() is used for the manual trace mode of the OPE Retriever, os_ope::stop() has to be called before the application terminates. Otherwise, an unhandled exception for err_event_info will occur.

9517

If your ObjectStore client application is running on SunOS 4.1.3 (you can determine the SunOS version number with the uname -a command), and it tries to activate the OPE Retriever library, the following exception occurs during the initialization of the client at the beginning of the first transaction:
 <err-0012-0040>Shared library "libosope.so.4.0" could not be loaded due 
to "ld.so: conflicting usage of dlopen'ed dependents" (err_misc)
This happens due to a bug in the loader run time of the SunOS operating system.

The workaround is either to upgrade to SunOS4.1.3_U1, or to dynamically link with the OPE Retriever library (libosope, libosopec), instead of dynamically loading it. Refer to the OPE guide, OPE Retriever API, for information on how to do this.

9840

On PC platforms, the first timestamp in the OPE trace file is inaccurate. On Windows NT, the first gettimeofday() only has an accuracy of 10 msec. On OS/2, the accuracy is only 1 sec. Therefore, if trace files are retrieved concurrently on multiple machines, they cannot be exactly aligned in the OPE Analyzer.

9869

If a database is created as a result of a os_database::open() call, the OPE Retriever records duplicate events for the opening of the database. As a result, in the OPE Analyzer's TimeLine diagram, if Database has been selected in the Select Events dialog, two before and two after events for database open are shown instead of one.

9947

On most UNIX platforms (except AIX), the OPE Retriever shared library (libosope.so) is loaded via the dlopen() system call, which is defined in the system library /usr/lib/libdl.so.1.0.

If /usr/lib:/lib is not in your LD_LIBRARY_PATH environment variable and the OPE Retriever is enabled (that is, the environment variable OS_OPE_TRACE is set), your application exits with a system error:
 dlopen: stub interception failed IOT trap
This is because the loader cannot find the dlopen() system call. If this happens, make sure that your LD_LIBRARY_PATH environment variable contains /usr/lib:/lib.