Release Notes › Policy Server Release Notes › Known Issues › Unsupported Features › Administrative UI Installer may use Incorrect WebLogic Domain Folder

Administrative UI Installer may use Incorrect WebLogic Domain Folder

If the WebLogic domain folder that was specified during the Administrative UI installation is not located under the default WebLogic installation folder, the installer may not use the specified folder. Rather, the installer may use an incorrect domain folder.

Oracle RAC Propagation Window Results in SiteMinder Errors

Symptom:

The Oracle RAC nodes propagate changes within 7 seconds. SiteMinder could read and write objects to a policy store, user store, session store, or audit store more often. As a result, the default Oracle RAC propagation window can result in SiteMinder errors. These SiteMinder errors occur because the write operation was made into one node and the read operation was made to another node.

Solution:

Configure the following setting in the Oracle RAC cluster:

MAX_COMMIT_PROPAGATION_DELAY=0

Note: For more information about configuring this setting, see the Oracle documentation.

Policy Server may Fail to Insert Audit Events into the Audit Database

Symptom:

Under heavy load, the Policy Server may fail to insert queued audit events into the audit store. If the failure occurs, the SiteMinder Policy Server log (smps.log) displays the following error:

[INFO] Failed attempt to bulk insert audit message: Code: -1044. DB Code: 2

Solution:

Two registry keys determine when the Policy Server inserts audit events into the audit database: SQLBulkInsertFlushInterval and SQLBulkInsertFlushRowCount:

• SQLBulkInsertFlushInterval determines the frequency in which the Policy Server inserts queued audit events into the audit database. The default value of this registry key is 60 seconds. If 60 seconds elapses before the value defined by the SQLBulkInsertFlushRowCount is reached, the Policy Server inserts all queued audit events into the audit database.
• SQLBulkInsertFlushRowCount determines how many audit events occur before the Policy Server inserts audit events into the audit database. The default value of this registry key is 1,000. If 1,000 audit events are queued before the value defined by SQLBulkInsertFlushInterval is reached, the Policy Server inserts all queued audit events into the audit database.

Modify the SQLBulkInsertFlushRowCount registry key to resolve the error message.

To modify the registry key

1. Access the Policy Server host system and do one of the following:
   • (Windows) Open the Registry Editor and navigate to HKEY_LOCAL_MACHINE\Software\Netegrity\SiteMinder\CurrentVersion\Reports\NamespaceProviders.
   • (UNIX) Open the sm.registry file. The default location of this file is siteminder_home/registry.

     siteminder_home

     Specifies the Policy Server installation path.

2. Increase the value of the SQLBulkInsertFlushRowCount registry key.

   Increase the value to be at least twice as large as the number of audit events that were created, per second, when the error appeared in the SiteMinder Policy Server log.

   Example: If 1,500 audit events occurred when the error appeared, increase the value to 3,000.

3. Do one of the following:
   • (Windows) Save the registry key and exit the Registry Editor.
   • (UNIX) Save the sm.registry file.
4. Restart the Policy Server.