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-71-2094243.1
Update Date:2016-01-05
Keywords:

Solution Type  Technical Instruction Sure

Solution  2094243.1 :   Diagnose Empty File Exported by Datafeed  


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
Goal
Solution
 No data in session
 Datawarehouse in urgent purge
 IXP clobber
 Further analyzes
References


Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 4.1 and later
Information in this document applies to any platform.

Goal

This document describe how to troubleshoot the "empty file" issue with Datafeed (data feed) application.

Solution

No data in session

Most common cause is the exported session is not up to date and has at least 6 hours delay.

To verify that, assuming exported session name and datawarehouse (DWS) which is storing it is known, simply verify that it can be queried in ProTrace application and that it contains fresh data (Look at End time field of xDR). This query must be done with same filter as the filter used in the feed as it is possible that no xDR might match the filter.

Datawarehouse in urgent purge

When a DWS is in urgent purge, session duration can be shortened up to being empty. When this is happening, in ProTrace, start date field is in the future (usually last hour of the day).

Look at 2047078.1 for more information on troubleshooting urgent purge.

IXP clobber

prod.clobber command on an IXP server hosting a feed require some actions prior to issue the command. These are:

  • Stop the feed(s) hosted by the IXP server
  • Write down time of last export
prod.clobber must be avoided as it can cause big problems and no root cause can be found as all logs are deleted.
Only Oracle support is supposed to use this command for specific problems where no other solutions exist.

If this was not done, datafeed will try to export data from the feed creation date which can be several monthes or even years. This can be checking in Statistical Status of the feed in Start/End period field.

Solution consist of recreating the feed and adapting start date and time to the date and time of the last exported file.

Alternatively, if prod.clobber was issue or upgrade just happened, 1908657.1 Datafeed Export not Working after System Upgrade or IXP Clobber can be read.

Further analyzes

DataFeed log are stored in /var/TKLC/log/dataexport.

References

<NOTE:1908657.1> - Datafeed Export not Working after System Upgrade or IXP Clobber
<NOTE:2047078.1> - DWS Pool Urgent Purge Troubleshooting

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