WIS 10901 Error When Attempting to Refresh a BSAE Report

When refreshing an existing report or creating a new one as run query and refresh, the following error message or pop up with the text is seen:

A database error occurred. The database error text is: SQL statement to execute cannot be empty or null. (WIS 10901)

The inability to refresh a report could be caused by BSAE Business Objects services having been started and connecting to the BSAE JBoss service. Also, if the BSAE JBoss service is restarted without restarting the Business Objects service, the error may also occur.

To work around the problem, perform the following steps:

1. Stop both the Business Objects and JBoss services.

/etc/init.d/opsware-omdb stop

/etc/init.d/bsae-bo stop

2. Start the Business Objects service.

/etc/init.d/bsae-bo start

3. Start the JBoss service.

/etc/init.d/opsware-omdb start

Advertisements

Dataminer error: java.lang.OutOfMemoryError: Java heap space

The BSAE 9.2 dataminer can show a Java OOM (Out of Memory) error on the DMTransactionMiner when processing a large SA (Server Automation) transaction from the lcrep table:

Exception in thread "Timer-1" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2882)
at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
at java.lang.StringBuffer.append(StringBuffer.java:224)
at com.opsware.cmdb.dataminer.DMMultiMasterTruthImpl.applyValueAndScope(DMMultiMasterTruthImpl.java:973)
at com.opsware.cmdb.dataminer.DMMultiMasterTruthImpl.collectClob(DMMultiMasterTruthImpl.java:931)
at com.opsware.cmdb.dataminer.DMMultiMasterTruthImpl.collectData(DMMultiMasterTruthImpl.java:735)
at com.opsware.cmdb.dataminer.DMMultiMasterTruthImpl.processTransaction(DMMultiMasterTruthImpl.java:103)
at com.opsware.cmdb.dataminer.DMMultiMasterTruthImpl.processTransaction(DMMultiMasterTruthImpl.java:41)
at com.opsware.cmdb.dataminer.DMTransactionMiner.loadTransactions(DMTransactionMiner.java:411)
at com.opsware.cmdb.dataminer.DMTransactionMiner.mineData(DMTransactionMiner.java:176)
at com.opsware.cmdb.dataminer.DMTransactionMiner.run(DMTransactionMiner.java:94)
at com.opsware.cmdb.dataminer.DataMiner$6.run(DataMiner.java:1304)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

This error can be seen on the DMTransactionMiner when processing a large SA transaction from the lcrep table.

To move past this problem is by lowering the number of transactions in an XML file. This is done using the DataFileChunkSize parameter in the dataminer. It defaults to 1500, and setting it lower might get past this problem. Determining a working value will probably be an iterative process. To change it, use ./dmconfig.sh on the BSAE server:

./dmconfig.sh –update –name <SA dataminer name> –settings DataFileChunkSize=<chunk size>

You can see the value it is currently set to with:

./dmconfig.sh –listsettings –name <SA dataminer name>

If it’s not listed then it is the default value, 1500.

BSAE: How to determine version

To determine the installed version of Business Automation Service Essentials (BSAE) or Service Automation Reporter (SAR)

1. cd /etc/opt/opsware/omdb

2. cat omdb.info

The process changes from major version to major version.

For SAR 7.x you look at the "omdb_core.build" value.

· 7.5 = omdb_core.build=opsware_34.c.2868.0

· 7.8 = omdb_core.build=opsware_34.c.20090505.0

For SAR 7.8.1 patch versions should match the following value.

· md5 /opt/opsware/omdb/deploy/cmdb-data-model.jar

· MD5 (cmdb-data-model.jar) = c07c017da7ac8a839bdb66306d057366

· md5 /opt/opsware/omdb/deploy/cmdb-data-model.sar

· MD5 (cmdb-data-model.sar) = 3229f5fb09bc3f622e61999c55936436

For BSAE 2.x you look at the "version" value.

· 2.0 = version=34f*

· 2.0.1 = version=34g.0.0.14

The file containing the updated version information changed in 9.10. The old references were updated for 9.10, but not for 9.11.

For BSAE follow this procedure:

1. cd /opt/HP/BSAE

2. cat BSAEssentials-version

For BSAE 9.x you look at the "BSAE_PRODUCT_VERSION_NUMBER" value.

· 9.10 = 9.1.0.x

· 9.11 = 9.11x