User guide

Partitioning must be done at the element level
Symptoms
DataStage collector mapping configuration provides fine level of partitioning at the
subelement level. However, some subelements must be configured to the same
collector. Because this rule is not verified by the DataStage job, mistakes might be
introduced in the relation lookup configuration file.
Resolving the problem
To avoid this problem, you must create the partition at the element level only. You
must configure all family names for an element to a single set of collectors.
The CSV file name changes when you map another class that
does not correspond to its collector
Symptoms
On DataStage, the CSV file in the out directory is not correctly named. For
example, the provisoAccounting_2013.02.18-08.05.00_101.csv file is incorrectly
named as provisoPerformance_2013.02.18-08.05.00_101.csv.
Causes
This problem occurs when you map one more class that does not correspond to its
collector in the collector_mapping.csv file. For example, in the
collector_lookup.csv file, you set the 101 collector as Accounting. However, in the
collector_mapping.csv file, instead of the Accounting class, you map one or more
Performance classes to the 101 collector. As a result, the Accounting 101 collector
gets mixed with the Performance classes, and you find the
provisoPerformance_2013.02.18-08.05.00_101.csv file instead of
provisoAccounting_2013.02.18-08.05.00_101.csv file in the out directory.
The OAM data exists at the SAM server but is not transferred
to DataStage
Symptoms
The OAM data exists at the SAM server in the xml_ouput directory. However, this
data is not transferred to DataStage at DS/done.
Diagnosing the problem
To identify the cause of the problem, follow these steps:
1. Run this command to verify if the registerSasLogToFile requests are sent to
the SAM server:
$ grep -q "^registerSasLogToFile" ./data/responsexmls.csv && echo "yes, there is a response for
the request!"
2. Run this command to identify if an exception has occurred:
$ grep "^registerSasLogToFile" ./data/responsexmls.csv | grep -i "exception"
$
# None - all ok
3. Check if the logFileAvailable message is received from the SAM JMS for these
sasLogToFile:
$ grep "/oam/" ./logs/sam-jms-daemon.log
$
# None - No message is received.
Note: /oam/ is the parent directory for these classes.
4. Check if there is a problem with the register sasLogToFile:
Chapter 11. Troubleshooting Alcatel-Lucent 5620 SAM LogToFile Technology Pack 79