IBM Support

IV37187: SYBASE SENSOR FAILS ON SYSTEM WITH MULTIPLE NETWORK INTERFACES.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When Sybase sensor connects to discovered database it uses the
IP address from the seed. If system has multiple network
interfaces and the sensor was initiated from a different
IP than database is listening, then sensor will fail.
Similar information to the below can be found in the
Sybase sensor logs:

2013-02-08 21:55:40,692 DiscoverManager [DiscoverWorker-35]
SybaseSensor-1.2.3.4-4100 DEBUG cdb.SybaseSensor -
getConnection: about
to connect to server: SYBDB, jdbc:sybase:Tdx:1.2.3.5:4100,
as
user:taddmusr
2013-02-08 21:55:40,723 DiscoverManager [DiscoverWorker-35]
SybaseSensor-1.2.3.4-4100 DEBUG cdb.SybaseSensor -
getConnection: unable
to connect w/conn string:jdbc:sybase:Tdx:1.2.3.5:4100, ex:
java.sql.SQLException: JZ006: Caught IOException:
java.net.ConnectException: Connection refused
2013-02-08 21:55:40,723 DiscoverManager [DiscoverWorker-35]
SybaseSensor-1.2.3.4-4100 WARN cdb.SybaseSensor -
[SybaseAgent.W.1]
Sybase instance down, or connection failed to:
jdbc:sybase:Tdx:1.2.3.5:4100
...
2013-02-08 21:55:54,892 DiscoverManager [DiscoverWorker-35]
SybaseSensor-1.2.3.4-4100 WARN engine.AgentRunner -
[AgentRunner.W.1]
AgentException thrown in agent
com.collation.discover.agent.AgentException: CTJTD0632E The
application
cannot connect to any Sybase servers on the following host:
1.2.3.5 .
 at
com.ibm.cdb.discover.app.db.sybase.sensor.SybaseSensor.discover(
SybaseSe
nsor.java:377)
 at
com.collation.discover.engine.AgentRunner.doRegularDiscovery(Age
ntRunner
.java:351)
 at
com.collation.discover.engine.AgentRunner.run(AgentRunner.java:2
70)
 at
com.collation.discover.engine.DiscoverEngine.processWorkItem(Dis
coverEng
ine.java:1419)
 at
com.collation.discover.engine.DiscoverEngine$DiscoverWorker.proc
essWorkI
temWithMetrics(DiscoverEngine.java:557)
 at
com.collation.discover.engine.DiscoverEngine$DiscoverWorker.run(
Discover
Engine.java:621)

Local fix

  • Run the sensor for the same IP address that Sybase is started.

Problem summary

  • When Sybase sensor connects to discovered database it uses the
IP address from the seed. If system has multiple network
interfaces and the sensor was initiated from a different
IP than database is listening, then sensor will fail.
Similar information to the below can be found in the
Sybase sensor logs:

2013-02-08 21:55:40,692 DiscoverManager [DiscoverWorker-35]
SybaseSensor-1.2.3.4-4100 DEBUG cdb.SybaseSensor -
getConnection: about
to connect to server: SYBDB, jdbc:sybase:Tdx:1.2.3.5:4100,
as
user:taddmusr
2013-02-08 21:55:40,723 DiscoverManager [DiscoverWorker-35]
SybaseSensor-1.2.3.4-4100 DEBUG cdb.SybaseSensor -
getConnection: unable
to connect w/conn string:jdbc:sybase:Tdx:1.2.3.5:4100, ex:
java.sql.SQLException: JZ006: Caught IOException:
java.net.ConnectException: Connection refused
2013-02-08 21:55:40,723 DiscoverManager [DiscoverWorker-35]
SybaseSensor-1.2.3.4-4100 WARN cdb.SybaseSensor -
[SybaseAgent.W.1]
Sybase instance down, or connection failed to:
jdbc:sybase:Tdx:1.2.3.5:4100
...
2013-02-08 21:55:54,892 DiscoverManager [DiscoverWorker-35]
SybaseSensor-1.2.3.4-4100 WARN engine.AgentRunner -
[AgentRunner.W.1]
AgentException thrown in agent
com.collation.discover.agent.AgentException: CTJTD0632E The
application
cannot connect to any Sybase servers on the following host:
1.2.3.5 .
 at
com.ibm.cdb.discover.app.db.sybase.sensor.SybaseSensor.discover(
SybaseSe
nsor.java:377)
 at
com.collation.discover.engine.AgentRunner.doRegularDiscovery(Age
ntRunner
.java:351)
 at
com.collation.discover.engine.AgentRunner.run(AgentRunner.java:2
70)
 at
com.collation.discover.engine.DiscoverEngine.processWorkItem(Dis
coverEng
ine.java:1419)
 at
com.collation.discover.engine.DiscoverEngine$DiscoverWorker.proc
essWorkI
temWithMetrics(DiscoverEngine.java:557)
 at
com.collation.discover.engine.DiscoverEngine$DiscoverWorker.run(
Discover
Engine.java:621)

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
packages:
| Fix Pack | 7.2.1-TIV-ITADDM-FP0005

Check the IBM Software Support web site for availability of the
above maintenance packages.

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IV37187
    • 

  • Reported component name
    APP DEPENDENCY
    • 

  • Reported component ID
    5724N5500
    • 

  • Reported release
    721
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2013-02-26
    • 

  • Closed date
    2013-04-17
    • 

  • Last modified date
    2013-04-17
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    • 



Fix information


    

  • Fixed component name
    APP DEPENDENCY
    • 

  • Fixed component ID
    5724N5500
    • 



Applicable component levels


    

  • R721  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"721","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            17 April 2013
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback