Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1856
Views
10
Helpful
28
Replies

Ani Server Failure Log

mironduplessis
Level 1
Level 1

‎06-26-2006 10:42 AM

Hi,

I have been trying to troubleshoot our Ciscoworks LMS 2.5 server.

I am unable to get the ANIServer process to start properly. I have followed the TAC notes about reinitialising the database with no luck. The ANI.log contains the following:

I= 0value *.*.*.*

I= 1value 6

I= 2value 1

2006/07/01 23:56:03 Thread-2 ani ERROR DBConnection$ConnectionCreator: Failed to establish DB connectivity because: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect

2006/07/01 23:56:03 main ani ERROR DBConnection: Failed to acquire metadata for connection because of null DB connection

2006/07/01 23:56:04 Thread-3 ani ERROR DBConnection$ConnectionCreator: Failed to establish DB connectivity because: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect

2006/07/01 23:56:04 main ani ERROR DBConnection: failed to connect to db via db-url jdbc:sybase:Tds:localhost:?SERVICENAME=aniDb

2006/07/01 23:56:04 main ani ERROR AniMain: failed to connect to db via db-url jdbc:sybase:Tds:localhost:?SERVICENAME=aniDb

ANI Server cannot connect to the database. Please stop and restart the System. If this does not work, please contact technical support.

Does anyone have any suggestions

Labels:
0 Helpful
28 Replies 28

mironduplessis
Level 1
Level 1
In response to Joe Clarke

‎07-04-2006 12:16 PM

I can confirm that in the ANI datasource is set as follows

HOST=localhost;DOBROADCAST=NO;ServerPort=43443

The extract below is from the DBServer.properties

The final line seems to be commented should I add that to the file and add :43443 after the px or at the top of the file next to the port reference

?

# "DBConnection.dataSourceUrl" should be [jdbc:sybase:Tds::].

# For example, if the dbos50 (open gateway server) is runnning on host "cawhite-ss20" and

# is listening to port 9999, then the datasource URL would be:

# [jdbc:sybase:Tds:cawhite-ss20:9999]

#

DBConnection.debugLevel=0

DBConnection.autoCommit=true

#DBConnection.jdbcDriver=sun.jdbc.odbc.JdbcOdbcDriver

#DBConnection.dataSourceUrl=jdbc:odbc:px

0 Helpful

mironduplessis
Level 1
Level 1
In response to mironduplessis

‎07-04-2006 12:20 PM

Apologies,

I saw what where you meant.

Ill let you know if that works.

0 Helpful

mironduplessis
Level 1
Level 1
In response to mironduplessis

‎07-04-2006 12:41 PM

Hmmmm,

The following is the contents of the file.

# (C) Copyright 1998 - 2002 Cisco Systems, Inc.

# All Rights Reserved

#

# The "DBServer.port" property specifies the port that the

# database service's module listens to for socket based

# requests.

DBServer.corbaName=dbservice

DBServer.debugLevel=0

DBServer.port=33333

DBServer.host=localhost

# Database services socket support debug levels.

DBServerSocket.debugLevel=0

DBServerSocketSelect.debugLevel=0

# The "DBSessionIPC.pingPeriod" is used by the RMI database client to

# periodically send a "I'm Alive" message so that the database

# session reaper will not deallocate the connection being used

# by the client.

#

# Ping period is set to 10800000 ms (3 hours) and the time out

# has been set to 21600000 (6 hours).

DBSession.debugLevel=0

DBSessionIPC.pingPeriod=10800000

DBSessionIPC.timeOut=21600000

# The database session reaper will check for timed out

# connections every "DBSessionReaper.sleepPeriod" milliseconds.

DBSessionReaper.debugLevel=0

DBSessionReaper.sleepPeriod=5000

DBConnectionPool.debugLevel=0

DBConnectionPool.poolSize=10

DBConnectionPool.softLimit=true

DBConnectionPool.maxConnections=30

# Driver can use two either the JDBC-ODBC Bridge driver

# or Sybase's jConnect JDBC driver

# . In order to use jConnect, you need to

# do the following:

#

# 1) Install the sybase CTLib libraries (for TDS protocol support).

# 2) Install the SQLAnywhere Open Gateway Server (dbos50)

# 3) Run the open gateway server (dbos50 listens on a specific port).

#

# NOTE: setAutoCommit(), commit() and rollback() database operations do not work

# with jConnect. Essentially, auto commit is turned on and can't be

# turned off thru jConnect without raising an exception.

#

# JDBC-ODBC Bridge Driver:

# ------------------------

# "DBConnection.dataSourceUrl" should be [jdbc:odbc:]. In

# CRM 1.x, the datasource name is "px", therefore the datasource URL is:

# [jdbc:odbc:px]

#

# jConnect Driver:

# ----------------

# "DBConnection.dataSourceUrl" should be [jdbc:sybase:Tds::].

# For example, if the dbos50 (open gateway server) is runnning on host "cawhite-ss20" and

# is listening to port 9999, then the datasource URL would be:

# [jdbc:sybase:Tds:cawhite-ss20:43443]

#

DBConnection.debugLevel=0

DBConnection.autoCommit=true

#DBConnection.jdbcDriver=sun.jdbc.odbc.JdbcOdbcDriver

#DBConnection.dataSourceUrl=jdbc:odbc:px

# Corba client properties.

corba.DBClient.corbaNoImplSleepPeriod=5000

corba.DBClient.corbaNoImplMaxAttempts=15

# jconnect tuning parameters.

DBConnection.PACKETSIZE=4096

DBConnection.REPEAT_READ=false

# STREAM_CACHE_SIZE limits only jconnect memory requirement; no performance chg

# DBConnection.STREAM_CACHE_SIZE=1000000

Any comments??

0 Helpful

Joe Clarke
Cisco Employee
Cisco Employee
In response to mironduplessis

‎07-04-2006 12:46 PM

This looks like the orig version of this file (found in NMSROOT\www\classpath\com\cisco\nm\cmf\dbservice\orig. If this is the only copy of the file you have, and you do not have a good backup, you will have to reinstall CiscoWorks from scratch. All of your databases are missing.

0 Helpful

mironduplessis
Level 1
Level 1
In response to Joe Clarke

‎07-04-2006 12:56 PM

Hi,

This the copy of the file in folder:

Sorry I didnt notice it before.

NMSROOT\www\classpath\com\cisco\nm\cmf\dbservice

Preview file
5 KB
0 Helpful

Joe Clarke
Cisco Employee
Cisco Employee
In response to mironduplessis

‎07-04-2006 01:04 PM

This looks good. ANI clients should be trying to connect to port 43443. If this is Windows 2003, you can use netstat -a -b -o to track down if the PID for ANIDbEngine is properly listening on TCP port 43443. If you're using Windows 2000, you'd have to use a tool such as TCPView from http://www.sysinternals.com to do this.

0 Helpful

mironduplessis
Level 1
Level 1
In response to Joe Clarke

‎07-04-2006 01:22 PM

Hi,

Using TCPView port 43443 is not listed at all.

0 Helpful

mironduplessis
Level 1
Level 1
In response to mironduplessis

‎07-04-2006 01:24 PM

dbsrv9.exe:4744 TCP eagle:43455 localhost:26158 ESTABLISHED

dbsrv9.exe:4744 TCP eagle:43455 localhost:26186 ESTABLISHED

dbsrv9.exe:4744 TCP eagle:43455 localhost:26213 ESTABLISHED

dbsrv9.exe:4744 TCP eagle:43455 localhost:26216 ESTABLISHED

dbsrv9.exe:4744 TCP eagle:43455 localhost:26243 ESTABLISHED

dbsrv9.exe:4744 TCP eagle:43455 localhost:26248 ESTABLISHED

dbsrv9.exe:4744 TCP eagle:43455 localhost:26254 ESTABLISHED

dbsrv9.exe:4744 TCP eagle:43455 localhost:26326 ESTABLISHED

dbsrv9.exe:4744 TCP eagle:43455 localhost:26538 ESTABLISHED

dbsrv9.exe:4744 TCP eagle:43455 localhost:26653 ESTABLISHED

dbsrv9.exe:4744 TCP eagle:43455 localhost:26993 ESTABLISHED

dbsrv9.exe:5408 TCP eagle:43447 localhost:29007 ESTABLISHED

dbsrv9.exe:5408 TCP eagle:43447 localhost:29017 ESTABLISHED

dbsrv9.exe:5408 TCP eagle:43447 localhost:29600 ESTABLISHED

dbsrv9.exe:5408 TCP eagle:43447 localhost:30165 ESTABLISHED

dbsrv9.exe:5408 TCP eagle:43447 localhost:30166 ESTABLISHED

dbsrv9.exe:5408 TCP eagle:43447 localhost:30167 ESTABLISHED

dbsrv9.exe:5556 TCP eagle:43446 localhost:26025 ESTABLISHED

dbsrv9.exe:5556 TCP eagle:43446 localhost:26165 ESTABLISHED

dbsrv9.exe:5556 TCP eagle:43446 localhost:26185 ESTABLISHED

dbsrv9.exe:5556 TCP eagle:43446 localhost:26619 ESTABLISHED

dbsrv9.exe:5556 TCP eagle:43446 localhost:26634 ESTABLISHED

dbsrv9.exe:5556 TCP eagle:43446 localhost:26636 ESTABLISHED

dbsrv9.exe:5556 TCP eagle:43446 localhost:26639 ESTABLISHED

dbsrv9.exe:5556 TCP eagle:43446 localhost:26640 ESTABLISHED

dbsrv9.exe:5556 TCP eagle:43446 localhost:26928 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26101 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26152 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26178 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26194 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26203 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26302 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26456 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26468 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26479 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26488 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26779 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:26781 ESTABLISHED

dbsrv9.exe:5788 TCP eagle:43441 localhost:27143 ESTABLISHED

0 Helpful

Joe Clarke
Cisco Employee
Cisco Employee
In response to mironduplessis

‎07-04-2006 05:53 PM

Looks my last reply got dropped. I had asked to see if this process is listening on any TCP ports. The above output only shows dbsrv9 processes and their established connections.

Additionally, please check your CiscoWorks services to make sure no one has altered the startup parameters (i.e. changed services from Manual to Automatic). See this thread for a guide: http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=Network%20Management&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddb858d

Finally, if the services check out, try this. Set CiscoWorks Daemon Management to Manual, then reboot. When the server comes back, run the following as a local Administrator:

C:\PROGRA~1\CSCOpx\bin\perl C:\PROGRA~1\CSCOpx\bin\dbRestoreOrig.pl dsn=ani dmprefix=ANI

That should complete successfully. When it does, set CiscoWorks Daemon Management back to Automatic, then reboot again. ANIServer should hopefully be able to connect to the database now.

0 Helpful

mironduplessis
Level 1
Level 1
In response to Joe Clarke

‎07-04-2006 11:45 PM

List of Process is attached.

Preview file
28 KB
0 Helpful

mironduplessis
Level 1
Level 1
In response to Joe Clarke

‎07-04-2006 11:51 PM

Hi,

According to the link above I should have:

CiscoWorks ANI database engine : Manual

However that process isnt listed instead i have

CiscoWorks CMF data Engine : Manual

Is this the same process?

0 Helpful

Joe Clarke
Cisco Employee
Cisco Employee
In response to mironduplessis

‎07-05-2006 07:39 AM

No. They are two different things. If you do not have the ANI Database engine service registered, you should probably try uninstalling Campus Manager, then reinstalling it.

0 Helpful

mironduplessis
Level 1
Level 1
In response to Joe Clarke

‎07-06-2006 12:59 AM

Hi,

I have uninstalled and reinstalled campus manager and have the process functioning correctly again.

Thanks for all your help

Miron

0 Helpful

mironduplessis
Level 1
Level 1
In response to Joe Clarke

‎07-05-2006 12:50 AM

Response when runing the command.

"C:\PROGRA~1\CSCOpx\bin\dbRestoreOrig.pl dsn=ani dmprefix=ANI

"

Usage:

Format1: dbRestoreOrig.pl dsn=odbc_datasource dmprefix=dmprefixname

Format2: dbRestoreOrig.pl dsn=odbc_datasource dmprefix=dmprefixname npwd=newpass

word

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents