This chapter contains information on error handling behavior for the NRTT CC and DMS-MSC Collection Cartridge for Offline Mediation Controller Nortel GSM/UMTS AMA cartridge pack.
When there is invalid data in the AMA input file, the CC raises a critical alarm and information about the error type and location are written to an error file. The AMA input file is then moved to the configured "bad file" directory.
There are three types of invalid data:
Invalid Block Descriptor Word (BDW): this error occurs when the block size does not match the content of the block. When the CC detects this error, the remaining information in the file is no longer readable. In this case, the CC processes the AMA DIRP file up to the position where the error was detected.
The CC cannot process the remainder of the file and will output the following alarm:
"Critical; Invalid Data; Invalid input data; An error occurred while processing file <filename>, a copy of this file has been placed in OMC_Home/amadirpei/2s4dgk-99f-e00sohaf/badAmaFilesDir: Error detected in the AMA DIRP file structure at offset:<0(block no: 1 , record no: 0)> Invalid Block Descriptor Word"
An error report file will be created in the node's configured "bad file" directory. The name of the error report file has the format <AMA DIRP closed filename>_error_report.txt. The error report identifies the position of the BDW error.
Invalid Record Descriptor Word (RDW): this error occurs when the record size does not match the content of the record. When the CC detects this error, the remaining information in the file is no longer readable. In this case, the CC processes the AMA DIRP file up to the position where the error was detected.
The CC cannot process the remainder of the file and will output the following alarm:
"Critical; Invalid Data; Invalid input data; An error occurred while processing file <filename>, a copy of this file has been placed in OMC_Home/amadirpei/2s4dgk-99f-00sohaf/badAmaFilesDir: Error detected in the AMA DIRP file structure at offset: <offset number>(block no: <block number>, record no:<record number>) Invalid Record Descriptor Word"
An error report file will be created in the node's configured "bad file" directory. The name of the error report file has the format <AMA DIRP closed filename>_error_report.txt. The error report identifies the position of the RDW error.
An error within an AMA record: for example, an unknown module code index. When the CC detects this error, it stops processing the record. The remaining information in the AMA DIRP file is still reliable, so the CC continues processing, starting with the next AMA record.
The CC outputs the following alarm:
"Critical; Invalid Data; Invalid input data; An error occurred while processing file <filename>, a copy of this file has been placed in OMC_Home/amadirpei/2s4dgk-99f-00sohaf/badAmaFilesDir>: Unable to process the AMA record at block: <block number>, record number: <record number>, fileOffset: <offset number>, recordSize: <record size><error specific information>"
An error report file will be created in the node's configured "bad file" directory. The name of the error report file has the format <AMA DIRP closed filename>_error_report.txt. The error report identifies the position(s) of the invalid data error.
When the NRTT CC and the DMS MSC CC point to different "bad file" directories, then if the NRTT CC encounters an error while processing the active file, it creates an error report in its configured "bad file" directory. If there is a loss of communication between the DMS SDM device and Offline Mediation Controller, and if the SDM rotates the active file to a closed state, the DMS MSC CC will process the closed file. If the DMS MSC CC encounters an error, it will write an error report in its configured "bad file" directory. So in this case there will be one error report file in each directory with the same "closed" file name prefix.
If the "bad file" directory is the same for both the NRTT CC and the DMS MSC CC, then if the NRTT CC encounters an error while processing the active file, it creates an error report with the name of the "closed" file in its configured "bad file" directory. If there is a loss of communication between the DMS SDM device and Offline Mediation Controller, and if the SDM rotates the active file to a closed state, the DMS MSC CC will process the closed file. If the DMS MSC CC encounters an error, it appends the error log in the report created by the NRTT CC. In this case there will be a single error report file with all the errors in it.
In all cases, occasionally there may be duplicate log entries in the error report file, which can be safely ignored. This situation can occur when there is a BDW or RDW error in the active file.
The following behaviors explain how errors are handled in various 1:1 file matching situations.
Scenario 1 - Input AMA file is corrupted
If the FTIR is corrupted or missing from an input file, the CC will continue to process the rest of the file.
The DC will:
generate an output file
create a copy of this file and place it in the Bad File directory (configured in the DC).
raise an alarm
Major
Invalid Data; Missing mandatory data; FTIR is missing in the file U021031154105gcdr. A copy of this file is created in badfile directory configured in the Node.
If the file header/first block descriptor word is corrupted, the CC will move the corrupted file to the Bad File directory (configured in the CC). An alarm will be raised by the CC and there will be no output from the DC for this corrupted file as there is no records received from CC. See Invalid AMA input file on page 80.
If any record other than the FTIR is corrupted, the CC will move the corrupted file to the Bad File directory (configured in the CC). An alarm will be raised. See Invalid AMA input file on page 80.
The DC will:
generate an output file
create a copy of this file and place it in the Bad File directory (configured in the DC).
raise an alarm
Major
Invalid Data; Missing mandatory data; There might be loss of data. Record Count is not matching with FTOR in the file U021031154105gcdr. A copy of this file is created in badfile directory configured in the Node.
If the AMA record count contained in the FTOR does not match the number of records received, the DC will:
generate an output file
create a copy of this file and place it in the Bad File directory (configured in the DC).
raise an alarm:
Major
Invalid Data; Missing mandatory data; There might be loss of data. Record Count is not matching with FTOR in the file U021031154105gcdr. A copy of this file is created in badfile directory configured in the Node.
If the FTOR is not received for a particular file ( it is decided if records of next input file is received when waiting for FTOR of current file), the DC will:
generate an output file
create a copy of this file and place it in the Bad File directory (configured in the DC).
raise an alarm:
Major
Invalid Data; Missing mandatory data; FTOR is missing in the file U031118200303. A copy of this file is created in badfile directory configured in the Node.
Scenario 2 - NAR data corruption within the cartridge chain
If the NAR data is corrupted:
NAR are written to the .badarch file in the scratch directory of that cartridge.
All valid NARs prior to the corrupted NAR will be transmitted to the DC.
In this instance, the DC will:
Generate an output file
Create a copy of this file and place it in the Bad File directory (configured in the DC).
Raise an alarm:
Major
Invalid Data; Missing mandatory data; There might be loss of data. Record Count is not matching with FTOR in the file U021031154105gcdr. A copy of this file is created in badfile directory configured in the Node.