BSAE: schema information

Use the following URL in the browser:


Where hostname should be replaced with the hostname or IP address of the BSAE application server.

Be certain that there are no firewalls blocking connectivity from the client desktop to port 8443 on the BSAE server.

Which user to supply in dmconfig during BSAE 9.10 dataminer installation

During a Business Server Automation Essentials (BSAE) 9.10 installation, the script is run in order to configure a dataminer. During its execution, the script will prompt for a logon to be used for the dataminer. What is the appropriate user to supply in order for the script to execute properly?

When prompted for the user by the script, make sure to supply the oracle user that is configured on the Model Repository. Chapter 5 of the BSAE Installation Guide goes into the various methods of pre-registering users and their passwords for use by the script.

The default user is cmdb_admin. This user is defined in the /opt/opsware/omdb/bin/ file.

Oracle ARCHIVELOG mode creates excess activity / excess disk usage

In an SA (Server Automation) or BSAE (Business Service Automation Essentials) installation, on reviewing the Oracle activities/performance, you notice what appears to be excessive archiving of the redo log files.

You see this as a possible sign of incorrect SA / BSAE performance and/or as a threat to excessive use of system resources, such as disk usage which might lead it to exhausting the free space on a partition.

By default, neither SA nor BSAE require ARCHIVELOG mode to be enabled for product functionality. Certainly when using the included Oracle installer for SA (or for BSAE prior to v9.10), ARCHIVELOG is not enabled.

If it was enabled, then the most likely cause for this is that your organization’s DBA has a policy which requires ARCHIVELOG mode to be enabled. Again, this is not a requirement for SA / BSAE to function correctly.

We do understand that by enabling ARCHIVELOG mode that you will quite likely see a sudden increase in Oracle DB instance activity over what it was like prior to enabling ARCHIVELOG mode. This is normal and expected. No corrective action is required, although you might want to discuss with your DBA regarding ensuring that neither the database’s performance nor the database server’s free disk space is being pushed to critical limits.

If database performance or disk space utilization is a concern, please disable ARCHIVELOG mode.

To check whether your database instance is running in ARCHIVELOG mode, please run the following commands from the Oracle user shell:

$ sqlplus ‘/ as sysdba’

SQL> select log_mode from v$database;


Dataminer is not passing data to Service Automation Reporter

Error Messages from the dataminer.log file:

INFO – – – – – "Configuration Path = /opt/opsware/dataminer"

INFO – – – – – "Using configuration file /opt/opsware/dataminer/dataminer.conf"

INFO – – – – – "Initializing …"

INFO – – – – – "Running on Linux"

INFO – – – – – "Cached Configuration file has been updated, reloading"

INFO – – – – – "Data Miner is already active"

DEBUG – – – – -"Sleeping 180000ms"

DEBUG – – – – -"Sleeping 180000ms"

If SAR is reinstalled, the dataminer must be reconfigured as well or will become orphaned.

If the original dataminer registration was successful and SAR is reinstalled, the dataminer will have the requisite crypto, Extract, Transform and Load (ETL), and source information but will not function due to:

Data Mining suspended while is_active flag cleared

Follow these step-by-step instructions:

On the dataminer server:

1. /etc/init.d/opsware-dataminer stop

2. cd /opt/opsware/dataminer

3. rm -rf *.ser

4. rm -rf work/

5. rm -rf collect/

6. rm -rf

7. rm -rf dataminer.keystore

8. check that you have the correct “RegistrationToken=” setting in dataminer.conf

9. check that dmboot.pem exists

On the SAR/BSAE Server:

10. cd /opt/opsware/omdb/bin

11. to obtain the name: dmconfig -list

12. -reset -name <NAME> # where <NAME> is the correct name of the dataminer you wish to reset

On the dataminer server:

13. /etc/init.d/opsware-dataminer start

Query will not run/refresh data

While running a report in BSAE, the following oracle error appears:

"ORA-01013:user requested cancel of current operation (wis 10901)" when trying to refresh the information.

This is a known issue. The Business Objects (BO) reporting engine has a default setting that can cause this problem.

1.) Go the edit query screen and click on the properties pane there is an option to "Retrieve duplicate rows" that is checked by default, uncheck this box.

2.) Use a date filter. On the data pane under general there is a "Single Date Filter" and a "Date Range Filter". Depending on what users want from the report, they should use one of this filters to help BO make a good decision when it creates the SQL. The "Single Date Filter" is like saying show me the data that was current as of this date. This is what most reports want. The "Date Range Filter" is like saying show me the data that was current between these two dates.

Unable to find import util /opt/opsware/hpln/lnc/util/anr_policy_creator.pyc error

While importing the Live Network libraries using /opt/opsware/hpln/lnc/bin/live-network-connector, the following error is obtained:

Unable to find import util /opt/opsware/hpln/lnc/util/anr_policy_creator.pyc !.

From the HPLN User Guide:

"… security.cc_library stream is a prerequisite stream that enables all SA compliance streams".

If this stream isn’t imported properly, no SA compliance stream will succeed. This explains why A&R Dynamic Policy fails.

Alternative solution

copy the file from another HPLN installation


Please note all of the currently enabled streams (those with a value of one via: live-network-connector read-config and a value of 1, starting with either content.<stream name> or security.<stream name>).

Disable all of the existing streams, via:

live-network-connector write-config –stream=<stream, e.g. content.ms_patch_supp> –disable

Repeat this for all currently enabled streams. (Leave the product9s) enabled, however)

then execute:

live-network-connector download-import –reload –debug

This will effectively force a reload of ‘core LNc’ which will include the product specific profiles, content handlers, and the policy creator utility.

Save this log file off in the event this doesn’t get you through this issue.

Then go ahead and enable one of the problem streams (just this pair for now), e.g.

then try to do your import:

live-network-connector write-config –stream=security.cc_library –enable

live-network-connector write-config –stream=security.cc_pci_unix –enable

live-network-connector download-import –debug