Overview

The customer may report an issue with provisioning a subscriber in the database. Sometimes the error encountered during the provisioning process may be relevant to the ELITEAAA.#BLRADIUSCUSTOMER_U01 trigger of the AAA database. The error message may also indicate an ORA-00001 error and may provide additional details about the trigger and its execution.

Solution

1. Verify User Existence:
   • Check the existence of the user in the tblradiuscustomer table by executing the following query:

     SELECT * FROM tblradiuscustomer WHERE username = '<Problematic User>';

   • Confirm if any rows are returned by the query. If no rows are fetched, it indicates that the user does not exist in the tblradiuscustomer table.
2. Validate the Table:
   • Ensure that the table referenced in the error message, tblcustomer, is the correct table for the provisioning process. If there is any discrepancy between the mentioned table and the searched table, consult with the database administrator (DBA) team or review the AAA database deployment to clarify the table structure and mapping.
3. Delete User Identity Record:
   • If the user exists in the tblradiuscustomer table but encounters a unique constraint violation during provisioning, the issue may be due to an existing record in another table.
   • Access the ETPLPROV schema and locate the T_SUBSCRIBER table.
   • Delete the user's identity record from the T_SUBSCRIBER table to resolve the unique constraint violation issue.
4. Test Provisioning Process:
   • After deleting the user identity record, ask customer to provision the subscriber again using the appropriate provisioning method or API.
   • Monitor the provisioning process