BSAE and Antivirus software

It is not supported to have antivirus software in BSAE, because it has not been quality tested and certified by our research and development department. This applies to all BSAE versions currently in the market.


SAR/BSAE ORA-00942: table or view does not exist

Error messages similar to the following may be seen in the dataminer.log files:

2010-09-16T03:43:15.099Z – [] INFO – – – – – "Query Mine: for table SAS_VIRTUAL_CENTER_TYPE"

2010-09-16T03:43:15.101Z – [] FATAL – – – – – "java.sql.SQLException: ORA-00942: table or view does not exist – ORA-00942: table or view does not exist"

2010-09-16T03:43:15.101Z – [] FATAL – – – – – "From: table SAS_VIRTUAL_CENTER_TYPE with SELECT NULL AS INPUT0, SYSDATE AS INPUT1, typeops.virtual_mgr_srvc_type_name AS INPUT2, typeops.display_name AS INPUT3, typeops.version AS INPUT4, typeops.vendor AS INPUT5, typeops.description AS INPUT6 FROM truth.virtual_mgr_srvc_type typeops"

2010-09-16T03:43:15.101Z – [] FATAL – – – – – "query miner problem ORA-00942: table or view does not exist"

2010-09-16T03:43:15.160Z – [] INFO – – – – – "TASK-DMQueryMiner collected 40362 rows from 40362 examined data points in 0.0 seconds

2010-09-16T14:06:22.072Z – [] INFO – – – – – "Current ETL has aged, will check for updates"

2010-09-16T14:06:22.085Z – [] ERROR – – – – – "Cannot retrieve current ETL WSClient: getCurrentETL:156 Connection refused; nested exception is: Connection refused"

2010-09-16T14:06:22.085Z – [] WARN – – – – – "WebServices failed to provide etl, authorization or connection error

The most common cause of this problem is that the correct schema owner is not set in the dataminer configuration for the source database.

On the Business Service Automation Essentials (BSAE) application server perform the following task to correct this problem.

1. cd /opt/opsware/omdb/bin

2. ./ –list

1. You may be prompted for a password. If prompted the password will be the password of the CMDB_ADMIN user.

2. Write down the name of the dataminer experiencing the problem from the above list.

3. ./ –update –name {dataminer name noted in previous step} –settings EtlTableWonerOverride={Schema Owner}

Example. Let’s say the dataminer name is NA-75 and the schema owner for the NA data is NASADMIN. The update line would look like this:

./ –update –name NA-75 –settings EtlTableWonerOverride=NASADMIN

On the machine where the dataminer is installed complete these task to complete the correction.

1. cd to the dataminer installation directory (Default=/opt/opsware/dataminer)

2. ./ restart

3. Monitor the dataminer.log to confirm that the error message is no longer present.

Changing the JRE version used by BSAE WebIntelligence reports

Changing the JRE version used by BSAE WebIntelligence Reports is not supported.

If you check the file /opt/opsware/omdb/bo/setup/ProductID.txt , you will see that BSAE version 9.11 has SAP BO Enterprise XI 3.1 SP2.

The supported JRE for this version of BO is shipped as part of the product, /opt/opsware/omdb/bo/bobje/jdk .

Error: Digital Signature could not be validated

In BSAE (Business Service Automation Essentials), in the /var/opt/opsware/omdb/collect/failures directory, in one of the failures files, the following error can be seen:

2012-07-16 06:25:49,039 [omdb.loader] INFO Loader started

2012-07-16 06:25:49,542 [omdb.loader] ERROR Exception thrown while validating file: Digital Signaturx|e could not be validated

2012-07-16 06:25:49,542 [omdb.loader] INFO Validating File…failed

2012-07-16 06:25:49,549 [omdb.loader] INFO Loader failed

2012-07-16 06:25:49,555 [omdb.loader] INFO Loader finished

This happens when signature validation is not enabled in BSAE.

Signature validation can be enabled by adding omdb.loader.validatefiles=true to /etc/opt/opsware/omdb/ Setting the value to false will disable it.

ERROR: No data to retrieve in Query1

The Business Object report throws the following error when executed or when the data is refreshed:

No data to retrieve in Query1

There could be a number of issues with this error. Some potential issues follow:

Insufficient permissions. The user may have insufficient access rights to run this query.

The database/BSAE connection has been dropped in BO.

The specified data does not exist.

The following actions are a good starting point to deal with this kind of error.

a) Permissions: The execution should be attempted with admin rights, or the permissions should be readjusted.

b) It is possible the Business Objects (BO) connection to Automation Reporter core or database has been dropped.

Stop BO (/etc/init.d/bsae-bo stop)

Stop BSAE (/etc/init.d/opsware-omdb stop)

Start BO (/etc/init.d/bsae-bo start)

Start BSAE (/etc/init.d/opsware-omdb start)

BO should always be started before BSAE. The startup time is about 10-15 minutes, so enough time should be allowed to pass before the report testing takes place again.

c) It is possible that there was no data for that specific date selection. A wider date range should be attempted. In addition – to gain a better understanding of the data – one could view the SQL used in the "Edit Query" form and comment out some of the date conditions to see if any data gets returned when no date range is specified.

Another reason why the data does not exist is also when the data has not made it into BSAE yet. If the data is too recent then enough time should be allowed to pass for the data to be mined and, after they are mined, the Nightly Job should be executed.

/opt/opsware/omdb/contrib/ 5

The nightly job should be run through the JMX-console and not the command line. The command line does not work in all situations.

BSAE WebInterface displays HTTP Status 404 – /bsae/null

BSAE WebInterface displays the following error message after a user logs in:

HTTP Status 404 – /bsae/null

type Status report

message /bsae/null

description The requested resource (/bsae/null) is not available.

No reporting functionality is available, although the Administration tab works properly.

This is usually caused by the BO Cms not running on the BSAE core. The logfile /var/log/opsware/omdb/server.log can be consulted for further information:

ERROR [STDERR] com.crystaldecisions.enterprise.ocaframework.OCAFrameworkException$NotFoundInDirectory: Server not found or server may be down (FWM 01003) Connection refused

detail:Server not found or server may be down (FWM 01003) Connection refused

1. It may be BO Cms is indeed stopped. If this is the case, it needs to be started:

/etc/init.d/bsae-bo start

2. A second issue can be BO Cms is unable to start due to some other causes. In this case, /var/log/messages needs to be consulted as it will contain the exact error. Is most of the cases this is due to an incorrect password for the Oracle user bo_admin:

Oct 7 10:28:58 bsae01 boe_cmsd[32020]: The root server reported an error Initialization Failure. (Reason: BusinessObjects Enterprise CMS: Unable to connect to the CMS system database ""cmdb"". Reason: ORA-01017: invalid username/password; logon denied BusinessObjects Enterprise CMS: Unable to connect to the CMS system database ""cmdb"". Reason: ORA-01017: invalid username/password; logon denied CDatabase::Open failure. ).