Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2106203.1
Update Date:2016-02-22
Keywords:

Solution Type  Problem Resolution Sure

Solution  2106203.1 :   PIC Sessions Running on External Data Warehouse are Stopped  


Related Items
  • Oracle Communications Performance Intelligence Center (PIC) Software
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
  •  




In this Document
Symptoms
Cause
Solution


Created from <SR 3-12074210031>

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 6.6.4 and later
Tekelec

Symptoms

Sessions stored under an external Data Warehouse are not updating. Under ProTrace, the End Time of the impacted sessions is showing "ERROR".

Cause

The following two different issues have been identified:

  • Store processes are not able to connect to the external Data Warehouse.
  • ProTrace connection to the external Data Warehouse is failing.

In the listener logs of the external Data Warehouse, we distinguish the following error entries:

  • For the store processes' connections:
    27-JAN-2016 13:37:20 * (CONNECT_DATA=(SERVICE_NAME=DTO.xxxx.com)(CID=(PROGRAM=IxpStore)(HOST=ixp0001-1c)(USER=cfguser))) * (ADDRESS=(PROTOCOL=tcp)(HOST=1.1.1.1)(PORT=11111)) * establish * DTO.xxxx.com * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
  • For the ProTrace requests:
    27-JAN-2016 13:42:39 (CONNECT_DATA=(SID=DTO.xxxx.com)(CID=(PROGRAM=)(HOST=__jdbc__)(USER=tekelec))) (ADDRESS=(PROTOCOL=tcp)(HOST=1.1.1.1)(PORT=22222)) establish DTO.xxxx.com * 12505
    TNS-12505: TNS:listener does not currently know of SID given in connect descriptor

Solution

The above listener logs show clearly that IXP store processes and ProTrace (jdbc) are not connecting to the external Data Warehouse in the same way:The store processes are using the Service Name in the connection chain (SERVICE_NAME=DTO.xxxx.com), while the ProTrace application (jdbc) is connecting through the SID [Instance Name] (SID=DTO.xxxx.com).

However, in the external Data Warehouse configuration menu on the NSP (Mediation -> Site -> DWH -> DTO_Pool -> Servers), in addition to the login, password and port, there is only one parameter (called "Service Name") which will be used by both store processes and ProTrace during the connection to the external database: Store processes will use it as a Service Name and the ProTrace application will use it as an Instance Name (SID).

Consequently, on the external Data Warehouse, Service Name and Instance Name (SID) must be exactly identical.

Since the modification of the Service name is much more simple than modifying the Instance Name (SID):

  1. Ask the external Data Warehouse administrator to configure a Service Name identical to the Instance Name (Be careful with the db_domain parameter).
  2. Once modification is done on the external Data Warehouse, add the newly configured name in the "Service Name" parameter of the the external Data Warehouse configuration menu on the NSP (Mediation -> Site -> DWH -> DTO_Pool -> Servers).
  3. Apply changes on all IXP subsystems.

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback