While Starting OSM Application, Getting Errors Db_env_policy Error

(Doc ID 2340940.1)

Last updated on JANUARY 04, 2018

Applies to:

Oracle Communications Order and Service Management - Version 7.3.5.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 7.3.5.0.0 version, Database

Getting errors like db_env_policy error when starting OSM.


**************************************************************************************************************************************************************
Order and Service Management System Health Policy Check
Fail Threshold: WARNING
OSM will fail to start if any policy checks fail with a severity greater than the above configured threshold.
Supported threshold values include VALID, WARNING, ERROR, CRITICAL
**************************************************************************************************************************************************************
Policy Name Health Result Messages
-------------------------------------------------------------------------- -------- ------------- -----------------------------------------------------------
db_env_policy - Check database version & environment ERROR Failed Info: Checks database version, database driver version,
  application schema version, and application version for
  compatibility.

  Error: XPath function instance('om_parameter') failed.

  Error: XPath function instance('om_parameter') failed.


server_env_policy - Check server environment parameters WARNING Passed Info: Checks the maximum memory allocated for OSM.

  Warning: Insufficient memory has been allocated to this
  server.
  Please ensure max heap size set correctly in WebLogic
  startup scripts (-Xmx parameter).
  The recommended max heap size for OSM is at least 3GB for
  production environments (e.g. -Xmx3072m).
  Development environments can be allocated less memory
  (between 1000mb and 2000mb).
  - Max heap size is currently set to 956 megabytes
  Note: Recommended heap sizes above assumes OSM is the only
  application deployed to the WebLogic server and should be
  adjusted upward if other applications are also deployed.


datasource_config_policy - Check data source configuration OK Passed Info: Checks the Weblogic MultiDataSource algorithm type.


partitioning_realm_config_policy - Check partitioning realm configuration ERROR Failed Info: Validates the database partitioning realm
  configuration

  Error: XPath function instance('partitioningRealmValidator')

ERROR
-----------------------
 Error: XPath function instance('om_parameter') failed.
  Error: XPath function instance('partitioningRealmValidator')

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms