This advises TIBCO ActiveMatrix BPM 2.x users on some implications of managing Oracle databases with separate "owner" and "user" accounts.

This advises TIBCO ActiveMatrix BPM 2.x users on some implications of managing Oracle databases with separate "owner" and "user" accounts.

book

Article ID: KB0086476

calendar_today

Updated On:

Products Versions
TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) -
Not Applicable -

Description

Description:
Description:
============
TIBCO ActiveMatrix BPM users can manage their Oracle databases using separate "owner" and "user" accounts.

Environment:
==========
TIBCO ActiveMatrix BPM 2.x on any supported platform, using an Oracle database.

Symptoms:
=========
If during installation you get errors in the log files stating components failed to start, it
indicates that one or more of the required objects are not accessible at runtime. For
example:

Caused by: com.tibco.n2.ec.core.exceptions.ECModelPersistException: {MODEL_PERSIST_ERROR} - Could not persist model ref [N2LF] for type
[com.tibco.n2.ec.core.persistence.model.N2LFComponentModel]!
at com.tibco.n2.ec.core.persistence.impl.orm.hibernate.N2LFHibernatePersistenceManager.persist(N2LFHibernatePersistenceManager.java:418)
at com.tibco.n2.ec.core.persistence.cache.N2LFCachedPersistenceManager.persist(N2LFCachedPersistenceManager.java:79)
at com.tibco.n2.ec.core.persistence.cache.N2LFCachedComponentManager.registerComponent(N2LFCachedComponentManager.java:37)
at com.tibco.n2.ec.services.impl.EventCollectorUpdateServiceImpl.registerComponent(EventCollectorUpdateServiceImpl.java:349)
... 29 more
Caused by: org.hibernate.exception.SQLGrammarException: could not get next sequence value

In this example, a sequence is missing.

Resolution:
=========
TIBCO ActiveMatrix BPM users may wish to manage their Oracle databases using separate "owner" and "user" accounts. For example there might be the following accounts:
• ActiveMatrix Administration Owner
• ActiveMatrix Administration User
• ActiveMatrix BPM Owner
• ActiveMatrix BPM User

This enables you to give the "owner" accounts greater privileges, for example allowing only "owners" but not "users" to create database objects. Once the system is set up and tested, the "owner" accounts can be locked during normal operational use.

Oracle synonyms allow users of the "ActiveMatrix BPM User" account (for example) to connect from the BPM application.

If you plan to take this approach, you must bear in mind the following points:
• The synonyms must allow the "user" accounts to connect to the default schema so that all database objects (such as tables, sequences,
    views, and so on) are accessible with any schema prefix. For example, they must be able to use requests such as:
    "select * from brm_work_items"
    rather than:
    "select * from owner.brm_work_items"
    TIBCO ActiveMatrix BPM does not provide these prefixes, relying rather on the default schema being correct.
• The "owner" accounts, normally locked, must be unlocked before upgrading TIBCO ActiveMatrix BPM.
Symptoms:

Cause:

Issue/Introduction

This advises TIBCO ActiveMatrix BPM 2.x users on some implications of managing Oracle databases with separate "owner" and "user" accounts.

Attachments

This advises TIBCO ActiveMatrix BPM 2.x users on some implications of managing Oracle databases with separate "owner" and "user" accounts. get_app