Layer7 Access Management

Expand all | Collapse all

Test audit db connectivity

Jump to Best Answer
  • 1.  Test audit db connectivity

    Posted 04-12-2017 10:50 AM

    We are running 12.51 SiteMinder.  Moving our environment to new hardware.  Looks like we are having some issue with ODBC connection to audit DB.  I see in 12.52 there appears to be some type of test tool to help debug connectivity problems.  Wondering if there is anything similar for 12.51.  When I hit 'Test Connection' in the console, I just get a generic -1063 error.  Would like to debug it a little more.  I did add tracing to system_odbc.ini but no file is created so I'm thinking its not getting far enough to log anything.  And I can telnet to database server.

     

    Thanks



  • 2.  Re: Test audit db connectivity

    Posted 04-12-2017 11:04 AM

    Hi,

     

    Kindly check below details are entered properly or not?

    DataSource name in SMConsole?

    Hostname and port in DSN?

    Database name in DSN?

     

    Please refer below link for enabling ODBC trace.

    How to enable odbc trace in Windows 

    Using ODBC Tracing in SiteMinder Policy Server. 

     

    Thanks,

    Sharan



  • 3.  Re: Test audit db connectivity

    Posted 04-12-2017 11:10 AM

    We moved the environment (by cloning our VM's) so everything is exactly the same in the new server.  The only change was to IP addresses in system_odbc.ini.

     

    And as for tracing, as I said, I turned it on but no output.



  • 4.  Re: Test audit db connectivity

    Posted 04-13-2017 11:17 AM

    Hi,

     

    Did you check the below Kb article for the error?

    Unexpected error in database interface. . Error code -1063 When Connecting to ODBC User Store 

     

    What is the exact error coming in smps and smtrace log?

     

    Thanks,

    Sharan



  • 5.  Re: Test audit db connectivity
    Best Answer

    Posted 04-13-2017 11:24 AM

    Thanks.  Issue has been resolved.  We received incorrect connection info from our db team.  Glad that 12.52 has a test option but we're not there yet.