Limitation: Duplicate BSD transaction names in Oracle

The problem: Because of a known limitation with ARM calls in Oracle scripts, multiple BSD transactions with names in the form of OracleSend:connection<xx>.<xx> are grouped under a single transaction name in the Tivoli Enterprise Portal. This limitation does not distinguish between OracleSend:Connection and OracleRecvConnection transactions that have the same transaction name.

The solution: To differentiate between OracleSend:Connection and OracleRecv:Connection transactions that have the same transaction name, you must insert individual NCA calls in the transaction objects with unique transaction names to monitor them correctly.