NET (Agent, Installation)

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem after Upgrade Database Agent to 4.3 version

Highlighted
New Poster

Problem after Upgrade Database Agent to 4.3 version

Hi all

After having performed a database agent upgrade following the instructions in the next link:

 

https://docs.appdynamics.com/display/PRO43/Upgrade+the+Database+Agent

 

We have detected that two of the monitored databases are no reporting data to the controller.

 

  • For one of the database when we restart the agent, the controller report traffic data while 2 or three minutes, and after that the controller stops receving data from the database.

The reported error from the agent.log is:

14 jun 2018 14:11:43,639 ERROR [<CRM DB>-Transient-Event-Scheduler-2] ADBTransientOpDelegate:233 - Got exception with errorCode = 229, SQLState = S0005, time taken = 0ms, query = [xp_readErrorLog 0, 1, NULL, NULL, '20180607', NULL, 'ASC']
com.microsoft.sqlserver.jdbc.SQLServerException: The EXECUTE permission was denied on the object 'xp_readerrorlog', database 'mssqlsystemresource', schema 'sys'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:792)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:689)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement.java:616)
at com.singularity.ee.agent.dbagent.handler.delegate.relational.ADBTransientOpDelegate.getQueryResults(ADBTransientOpDelegate.java:200)
at com.singularity.ee.agent.dbagent.handler.delegate.relational.ADBTransientOpDelegate.getQueryResults(ADBTransientOpDelegate.java:275)
at com.singularity.ee.agent.dbagent.handler.delegate.relational.mssql.MsSqlObjectInspector.getErrorLog(MsSqlObjectInspector.java:65)
at com.singularity.ee.agent.dbagent.handler.delegate.relational.ADBObjectInspector.execute(ADBObjectInspector.java:72)
at com.singularity.ee.agent.dbagent.handler.delegate.relational.ADBObjectInspector.execute(ADBObjectInspector.java:18)
at com.singularity.ee.agent.dbagent.handler.executor.relational.ARelationalDBTransientOpExecutor.execute(ARelationalDBTransientOpExecutor.java:142)
at com.singularity.ee.agent.dbagent.handler.DBTransientOperationHandler.executeOperationSynchronously(DBTransientOperationHandler.java:64)
at com.singularity.ee.agent.commonservices.transientoperations.ATransientEventChannel.executeOperationInternal(ATransientEventChannel.java:312)
at com.singularity.ee.agent.commonservices.transientoperations.ATransientEventChannel.executeOperations(ATransientEventChannel.java:261)
at com.singularity.ee.agent.commonservices.transientoperations.ATransientEventChannel.access$000(ATransientEventChannel.java:43)
at com.singularity.ee.agent.commonservices.transientoperations.ATransientEventChannel$EventChannelPollingTask.handleOperations(ATransientEventChannel.java:378)
at com.singularity.ee.agent.commonservices.transientoperations.ATransientEventChannel$EventChannelPollingTask.run(ATransientEventChannel.java:343)
at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
at java.lang.Thread.run(Unknown Source)

 

  • For the another  database there are no trafic data, the agent.log file  is reporting::

4 jun 2018 15:56:28,644 ERROR [<SG01WPMTD01.grupoevo.corp>-Scheduler-2] ADBMonitorConfigResolver:133 - Failed to resolve DB topological structure [Oracle-Tecnocom].
java.sql.SQLSyntaxErrorException: ORA-00904: "UTL_INADDR"."GET_HOST_ADDRESS": identificador no válido

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1017)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:655)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:249)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:566)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:202)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:45)
at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:766)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:897)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1034)
at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1244)
at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:420)
at com.singularity.ee.agent.dbagent.task.resolver.OracleMonitorConfigResolver.resolveToptopologicalStructure(OracleMonitorConfigResolver.java:64)
at com.singularity.ee.agent.dbagent.task.resolver.ADBMonitorConfigResolver.run(ADBMonitorConfigResolver.java:127)
at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
at java.lang.Thread.run(Unknown Source)

 

Before the upgrade of the controller both databases were reporting data to the controller.

 

Please find attached, two files, error.log and agent.log from the agent installation directory

 

Any idea about what was wrong with the update?.

Best regards

Francisco

Problem after Upgrade Database Agent to 4.3 version