Symantec Access Management

  • Private Community
 View Only

  • 1.  Using location based on IP (quova data) in riskauthentication

    Posted Sep 10, 2021 12:54 PM
    Hi.

    After having uploaded the quova data in the DB using the arrfupload tool, swapped the table  to the uploaded one, and restarted everything, I was expecting that the transaction attribute Country and State in the risk evaluation request should be set, but I still continue to see them empty.
    what could I miss?
    Is there a checklist where to check?

    In the log I don't see any reference expect the message:
    [COUNTRY] not found in transaction data


  • 2.  RE: Using location based on IP (quova data) in riskauthentication

    Posted Sep 11, 2021 07:08 AM
    Solved.
    the arrfupload tool did not upload all the quova data, even if it reported a 100% completed.
    Checking the arrfupload logs I found the SQL errors and checking the table I found lot of data missing.
    Original Message


  • 3.  RE: Using location based on IP (quova data) in riskauthentication

    Broadcom Employee
    Posted Sep 13, 2021 10:13 AM
    Great thanks Franco, will you be able to paste the error messages you saw, was that some space issue, permission issue?

    -Namish
    Original Message


  • 4.  RE: Using location based on IP (quova data) in riskauthentication

    Posted Sep 14, 2021 03:23 AM
    Namish,
    the error I got was:
    on Sep 13 17:09:09.167 2021 FATAL: pid 12792 tid 12792: 2: 0: Error: SQLExecute() did not return SQL_SUCCESS

    I was able to get the real error in the Oracle alert log.
    It was a size issue, I had to increase the size of my tablespace.

    regards
    Franco
    Original Message