Architect Known Issues

This Readme document contains late-breaking issues related to the Architect component.

Note: The Architect component is not used with Cognos 8.

Look here for readme information about closely related components:

• Installation Known Issues
• Configuration Manager Known Issues
• Data Access (UDA) Known Issues
• Cognos Application Firewall Known Issues
• Deployment Manager Known Issues
• Impromptu Known Issues
• PowerPlay Known Issues
• Upfront Known Issues

The Readme document also contains information about Features No Longer Supported in this release and those that will not be supported in subsequent releases.

To see Readme updates and information about deploying Cognos Enterprise Business Intelligence products, go to the Cognos support site (http://support.cognos.com).

ObjectStore VirtualAlloc Failure on Windows XP

If there is insufficient storage space for the ObjectStore, you will see the following error message when you try to start Architect or Transformer Versions 7.3, 7.1, or 7.0 on Windows XP:

ObjectStore internal error.

VirtualAlloc failed to allocate at any address - not enough storage is available to process this command (8)

The problem does not seem to arise with Impromptu Web Reports, although it also uses ObjectStore.

If you experience the problem, we recommend that you do the following:

1. From the Control panel, click System and, on the Advanced tab, click Environment Variables.
2. Ensure that OS_AS_START is not defined among the environment variables. That allows the system to determine an optimal PSR (Persistent Storage Region) for the client address space. The default range is from 0x30000000 to 0x38000000.
3. If there is not already a system environment variable called OS_AS_SIZE, create one.
4. Set the OS_AS_SIZE environment variable to a value that is lower than the default:
   • In Architect Version 7.3, the default OS_AS_SIZE environment variable value for the ObjectStore is 0x20000000 (512 MB).
   • In Architect Versions 7.1 and 7.0, it is 0x08000000 (128 MB).

The required environment variable setting depends on the amount of memory on your computer, as well as on your operating system and component version. For example, when running Transformer 7.3 on Windows XP SP1, we recommend a setting of 0x08000000.

Note: To translate the hexadecimal value 0x20000000 into its equivalent in megabytes, cut 5 trailing zeroes to divide by 0x100000 (which represents a megabyte). The result is the number of megabytes in hexadecimal notation.

For example, 0x20000000 divided by 0x100000 equals 0x200, which in decimal notation represents (2x16x16) =512 MB.

5. Reduce the value of the OS_AS_SIZE environment variable, in small steps, and retest until the problem no longer arises.

444518; 459228

Working in a Multiple Modeler Environment

If your work environment contains more than one Architect modeler, you must ensure that they co-ordinate their modeling activities. If more than one modeler is working on a model at the same time, only one of them can import metadata, build the business layer, create packages, or do any other type of automated refinement at a time. If both modelers try to import or generate model objects at the same time, one modeler may be temporarily locked out.

You must also ensure that only one user, the administrator, is logged in to the model when security changes are made, particularly if the security changes involve restricting access to a User Class.

nbna

DB2 Replicated Tables are Not Displayed in Architect

DB2 replicated tables are not displayed in Architect because they are not imported into Architect. The replicated tables are not imported because the table type is not recognized. In the ODBC/DB2 gateway, a table request is implemented as ODBC SQLTables call. SQLTables call returns a list of table, catalog, or schema names, and table types, that are stored in a specific data source.

ODBC SQLTables defines replicated table as type "TABLE". Therefore, calling SQLTables with type "TABLES" should return the replicated tables, however it doesn't. Thus this is why replicated tables do not get imported into Architect. IBM Support was able to reproduce the problem and it has been logged as defect report PMR 20235,519.

324202

Right-to-Left Characters Displayed Incorrectly

Due to technical limitations - that have been reported to Microsoft - right-to-left characters such as Hebrew or Arabic may not appear correctly in an English left-to-right environment.

This problem has been identified by Microsoft as their defect number SRZ011011000550.

339043