There are two distinct error-handling actions that RE Loader takes, depending on when the error occurs:

• If an error occurs while events are being loaded, the process is canceled and all events loaded in the session are deleted from the BRM database. The SQL loader errors are logged in a file (BRM_home/apps/pin_rel/file_name.bad) and a fatal error is recorded in the RE Loader log file (Processing_directory/rel.pinlog).

• If an error occurs while RE Loader is updating account balances, bill items, or journals, the loaded events are left in the database and an error is recorded in the RE Loader log file (Processing_directory/rel.pinlog). If RE Loader stops due to errors while updating account balances, bill items, or journals, correct the problem and run RE Loader again.

Some error messages are sent to standard BRM error handling. Check the rel.pinlog log file. See "Checking the RE Loader Log Files for Error Codes".

RE Loader checks for status in two places:

• The /batch/rel session status object.

  This object stores the status of the last RE Loader process. When you start RE Loader, it checks that status. If you try to reload a file that RE Loader has already successfully updated, the file is rejected because the session status indicates that the update for that file is complete.

• The REL_SUB_PROCESSES_T table.

  This tables stores information about loading errors that occurred during the preupdating stage. See "Checking for Errors that Occurred during the PreUpdate Process".

RE Loader uses the SQL Loader utility, sqlldr, to load events into the BRM database. The sqlldr process creates a new log file for each input file so that log files from a previous process are not overwritten.

The log files and the temporary files created during preprocessing incorporate the name of the input file in their file names, making it easier to debug if an error occurs.

Error codes follow the fully qualified error code (FQEC) scheme, which consists of a major code that represents the component and a minor code that represents the error number. All BRM-defined errors use a minor code from 0 through 99, and all custom errors use minor codes 100 and above.

For information on how to create custom error codes for RE Loader scripts and utilities, see "Creating Custom Error Codes".

The major and minor error codes for each RE Loader component are shown in Table 9-1.

Table 9-2 shows the BRM-defined error codes and messages, where value is the value returned in the error message:

Table 9-3 shows the BRM-defined failure script error codes.

Table 9-4 shows the BRM-defined transform script error codes.

Table 9-5 shows the BRM-defined preprocess script error codes.

Table 9-6 shows the BRM-defined load utility error codes.

Table 9-7 shows the BRM-defined insert stored procedure error codes.

Table 9-8 shows the BRM-defined preupdate stored procedure error codes.

Table 9-9 shows the BRM-defined update stored procedure error codes.

Table 9-10 shows the BRM-defined success script error codes.

Table 9-11 shows the BRM-defined database consistency check error codes.

Errors that occur during the preupdate stage of the loading process are stored in the REL_SUB_PROCESSES_T table. To check for values in the table, run SQL*Plus.

Table 9-12 shows the error codes stored in the REL_SUB_PROCESSES_T table:

To troubleshoot event loading errors, check the RE Loader log file BRM_home/apps/pin_rel/rel.pinlog, where BRM_home is the directory in which you installed BRM components. See "Checking the RE Loader Log Files for Error Codes".

At times, when RE Loader fails, the rel.pinlog file does not list the error. If this occurs, check the status column in the BATCH_T table in the BRM database for the status of the REL process. Table 9-13 lists the status entries (and the corresponding code attributes).

The correct troubleshooting effort for an event loading error depends upon the error scenario:

• RE Loader fails to start:

  The RE Loader log file (rel.pinlog) displays the error code 107.

  The error occurs if REL is not running.

  Start REL using the following command:

  rel<rated event file>

• Load failure:

  The RE Loader log file (rel.pinlog) displays the error code 5000. The status entry for the REL process in the BATCH_T table in the BRM database displays 1 (see Table 9-13).

  In this error scenario, RE Loader failed either before or during the loading of the events in the event file. The events are deleted from the event tables.

  To troubleshoot this error, reload the events normally by using the same command to process the original event file.

• RE Loader fails during the loading:

  The RE Loader log file (rel.pinlog) does not display any error. The status entry for the REL process in the BATCH_T table in the BRM database displays 80 (see Table 9-13).

  In this error scenario, RE Loader failed during the loading of the events and RE Loader was unable to update the session status or execute the cleanup process.

  Use the -override option to start a new process to reload the events. For example:

  pin_rel -override event_file_name

  where event_file_name is the event file.

• Error occurs during the pre-update stored procedure:

  The RE Loader log file (rel.pinlog) displays pre-update stored procedure error codes starting at 7000 and below 8000. The status entry for the REL process in the BATCH_T table in the BRM database displays 8 (see Table 9-13).

  In this error scenario, RE Loader crashed during the execution of the pre-update stored procedure.

  To troubleshoot this error, reload the events normally by using the same command to process the original event file.

• RE Loader fails during the updating of events:

  The RE Loader log file (rel.pinlog) does not display any error. The status entry for the REL process in the BATCH_T table in the BRM database displays 8192 (see Table 9-13).

  In this error scenario, RE Loader crashed during the updating of the events and RE Loader was unable to update the session status or execute the cleanup process.

  To troubleshoot this error, reload the events normally by using the same command to process the original event file.

• Error occurs during the update stored procedure:

  The RE Loader log file (rel.pinlog) displays update stored procedure error codes starting at 8000 and below 9000. The status entry for the REL process in the BATCH_T table in the BRM database displays 2.

  In this error scenario, RE Loader successfully loaded the events but failed during the execution of the update stored procedure. The BATCH_REL_SUB_PROCESSES_T table lists the last commit, indicating the point at which the database update failed.

  Reload the events normally. The update starts from this point.

RE Loader customizations can sometimes cause data files and control files to become unsynchronized, resulting in SQL Loader failures. To help you debug these situations, use the pin_rel_enum_blk.pl script, which enumerates fields in your bulk-loadable files. You can then manually compare the data file entries to the control file.

To debug mismatches between your data files and control files, enter the following commands:

% cd BRM_home/apps/pin_rel
% pin_rel_enum_blk.pl file_name [Line_num]

where:

• file_name specifies the name of the bulk-loadable file. For example, test2.blk.

• Line_num specifies the line number of the bulk-loadable file that you want to enumerate. The default is 1.

You can configure BRM to process call detail records (CDRs) as ZIP files. The Rated Event Loader Manager (REL Manager) provides tools you can use to find, correct, and reload ZIP files that have errors. See "Rated Event Loader Manager Utility" for more information about how to use this utility.

The general process for handling ZIP files is:

1. Find the files that have errors using zip_detail.
2. Write the failed files to the file system using zip_file_write. Each ZIP file will be extracted to individual CDR files in a directory specific to the ZIP file.
3. If needed, find out what files you have extracted with zip_file_write using zip_file_search. You can also use zip_detail again to see which files have been extracted.
4. Correct the data as needed.
5. Load the modified ZIP file back into the BRM database using zip_file_reload.
6. Depending on the settings you used in zip_file_reload, the data is either reprocessed automatically, or you can reprocess the data using retry_session.

Table 9-14 provides the list of ZIP file error codes.

RELManager> zip_detail 2022-06-10
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
|         Poid | Mod Time            | Input Filename                                               | Status | State              |  Records | Zip Status | Zip State          | Zip Size(Mb) | Extracted? |
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
|    112539709 | 2022-06-10 08:47:18 | BRMCDR_GSM_2022-06-10T15:41:02Z_2022-06-10T15:41:12Z         |      0 | COMPLETE           |        4 |          0 | COMPLETE           |        0.006 | NO         |
|    112531503 | 2022-06-10 08:47:18 | BRMCDR_GSM_2022-06-10T15:40:52Z_2022-06-10T15:41:02Z         |      2 | LOAD_ERROR         |       12 |          0 | COMPLETE           |        0.007 | NO         |
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
|              |                     |                                                              |        |                    |       16 |            |                    |        0.013 |            |
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
2 rows processed.

RELManager> zip_file_write 112531503
Successfully written ZIP data for POID '112531503'
Wrote 1 of 1 POIDs provided
Files can be found in directory: /home/brmuser/data/unzipped

RELManager> zip_file_search
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+---------------------+---------------------+--------+
|         Poid | Mod Time            | Input Filename                                               | Status | State              |  Records | Start Time          | End Time            | Is ZIP?|
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+---------------------+---------------------+--------+
|    112531503 | 2022-06-10 08:47:18 | BRMCDR_GSM_2022-06-10T15:40:52Z_2022-06-10T15:41:02Z         |      1 | LOAD_ERROR         |       12 | 2022-06-10 08:41:11 | 2022-06-10 08:41:11 | YES    |
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+---------------------+---------------------+--------+
1 rows processed.

RELManager> zip_detail 2022-06-10
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
|         Poid | Mod Time            | Input Filename                                               | Status | State              |  Records | Zip Status | Zip State          | Zip Size(Mb) | Extracted? |
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
|    112539709 | 2022-06-10 08:47:18 | BRMCDR_GSM_2022-06-10T15:41:02Z_2022-06-10T15:41:12Z         |      0 | COMPLETE           |        4 |          0 | COMPLETE           |        0.006 | NO         |
|    112531503 | 2022-06-10 08:47:18 | BRMCDR_GSM_2022-06-10T15:40:52Z_2022-06-10T15:41:02Z         |      1 | LOAD_ERROR         |       12 |          0 | COMPLETE           |        0.007 | YES        |
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
|              |                     |                                                              |        |                    |       16 |            |                    |        0.013 |            |
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
2 rows processed.

RELManager> zip_file_reload false 112531503
Successfully updated ZIP data for POID '112531503'
Updated 1 of 1 POIDs provided
Successfully loaded files have been renamed with suffix '.reloaded_<timestamp>' in directory: /scratch/ri-user-1/data/unzipped

RELManager> retry_session 112531503
Successfully submitted Poid[112531503] File[BRMCDR_GSM_2022-06-10T15:40:52Z_2022-06-10T15:41:02Z] for retry
Submitted 1 sessions for retry (0 failures)

RELManager> zip_detail 2022-06-10
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
|         Poid | Mod Time            | Input Filename                                               | Status | State              |  Records | Zip Status | Zip State          | Zip Size(Mb) | Extracted? |
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
|    112539709 | 2022-06-10 08:47:18 | BRMCDR_GSM_2022-06-10T15:41:02Z_2022-06-10T15:41:12Z         |      0 | COMPLETE           |        4 |          0 | COMPLETE           |        0.006 | NO         |
|    112531503 | 2022-06-10 09:02:58 | BRMCDR_GSM_2022-06-10T15:40:52Z_2022-06-10T15:41:02Z         |      0 | COMPLETE           |       12 |          5 | PROCESS_ERROR      |        0.007 | NO         |
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
|              |                     |                                                              |        |                    |       16 |            |                    |        0.013 |            |
+--------------+---------------------+--------------------------------------------------------------+--------+--------------------+----------+------------+--------------------+--------------+------------+
2 rows processed.

When processing usage files using the pin_rel utility, you may encounter an error due to a RE Loader session timing out. This issue arises when a RE Loader session is abruptly terminated, leaving its status in a Loading state, which prevents other RE Loader processes from running. Following is an example of the error:

Error 08/01/25 5:13:42:0007 AM ( 1690892022007 ) T:Thread-2 REL IREL 2:lhr-405:UnknownProgramName:0:Thread-2:4:1690891420:5:root.0.0.0.1::: 
   Error encountered in the REL Driver: 1028
The REL session has timed out waiting for another REL session to complete.
...
Debug 08/01/25 5:13:42:0032 AM ( 1690892022032 ) T:Thread-2 REL IREL 2:lhr-405:UnknownProgramName:0:Thread-2:4:1690891420:5:root.0.0.0.1:::
   Error file moved to the reject directory.

To resolve the issue, do the following:

1. Ensure that there are no other RE Loader processes currently running.

   You can check this by reviewing the active processes in the system.

2. Run the following command:

   pin_rel -override event_file_name

   where event_file_name is the name of the event file you want to load, including its extension.

   This loads the usage file with the option to start a new pin_rel process when pin_rel has stopped abnormally or been stopped manually.