DX Application Performance Management

  • 1.  Team Center has no data

    Posted Mar 19, 2019 05:13 AM

    Hi Team,

     

    In team center I cant see any map view availble also when i try to create experience card  in filters i cannot see all the list of agents that are deployed on the applications.

    Tried running a transaction trace session in webview but didnt help

    Also i can see the frontend metrics are population on the investigator tab

     

    The team center automatically created the list of the agents or we have to do it manually

    Please guide me through this

     

    Thanks



  • 2.  Re: Team Center has no data

    Broadcom Employee
    Posted Mar 19, 2019 08:54 AM

    Dear Robert: 

       Are you using APM 10.70.0.45 or 10.7.0.90? If yes. Do you see the agents in Metric View under the Superdomain? If no, try upgrading to SP2 (.115)  The logs in DEBUG/VERBOSE should help. Also check your filters and account/user group permissions.

     

    Thanks

    Hal German

     

    Dear Community:

    Are there other suggestions that you can offer Robert? Thanks in advance.



  • 3.  Re: Team Center has no data

    Posted Mar 19, 2019 01:05 PM

    I am using 10.70.0.45 yes i can see the agents in metric view under superdomain..



  • 4.  Re: Team Center has no data

    Posted Mar 20, 2019 05:04 AM

    getting following error in APM

     

    3/20/19 04:41:00.284 PM MYT [ERROR] [Thread-ModelSynchronization] [Manager.AppMap] Unable to complete model synchronization with storage!
    org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [INSERT INTO appmap_attribs (vertex_id, start_time, end_time, fork, attrib_name, value)    VALUES (?, ?, ?, ?, ?, ?)]; SQL state [72000]; error code [1653]; ORA-01653: unable to extend table APMADMIN.APPMAP_ATTRIBS by 128 in tablespace APMDATA
    ; nested exception is java.sql.SQLException: ORA-01653: unable to extend table APMADMIN.APPMAP_ATTRIBS by 128 in tablespace APMDATA

     

            at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:84)
            at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81)
            at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81)
            at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:660)
            at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:909)
            at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:933)
            at org.springframework.jdbc.core.namedparam.NamedParameterJdbcTemplate.update(NamedParameterJdbcTemplate.java:313)
            at com.wily.introscope.appmap.em.model.dao.impl.gmt.GMTNamedParameterJdbcTemplate.update(GMTNamedParameterJdbcTemplate.java:250)
            at com.wily.introscope.appmap.em.model.dao.impl.AttributeOperationsDaoImpl.storeNormalizedAttributes(AttributeOperationsDaoImpl.java:236)
            at sun.reflect.GeneratedMethodAccessor228.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:498)
            at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
            at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)
            at com.sun.proxy.$Proxy130.storeNormalizedAttributes(Unknown Source)
            at sun.reflect.GeneratedMethodAccessor228.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:498)
            at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
            at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)
            at com.sun.proxy.$Proxy131.storeNormalizedAttributes(Unknown Source)
            at com.wily.introscope.appmap.em.model.dao.impl.CollectorOperationsDaoImpl.setVertexGathered(CollectorOperationsDaoImpl.java:317)
            at com.wily.introscope.appmap.em.model.dao.impl.CollectorOperationsDaoImpl.setVertex(CollectorOperationsDaoImpl.java:215)
            at com.wily.introscope.appmap.em.model.dao.impl.CollectorOperationsDaoImpl.setEdgeTransactional(CollectorOperationsDaoImpl.java:849)
            at com.wily.introscope.appmap.em.model.dao.impl.SubtransactionsDaoImpl.setEdgeTransactional(SubtransactionsDaoImpl.java:73)
            at sun.reflect.GeneratedMethodAccessor246.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:498)
            at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
            at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99)
            at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:281)
            at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
            at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)
            at com.sun.proxy.$Proxy121.setEdgeTransactional(Unknown Source)
            at com.wily.introscope.appmap.em.model.dao.impl.CollectorOperationsDaoImpl.setEdge(CollectorOperationsDaoImpl.java:1498)
            at com.wily.introscope.appmap.em.model.dao.impl.CollectorOperationsDaoImpl.setEdge(CollectorOperationsDaoImpl.java:498)
            at sun.reflect.GeneratedMethodAccessor226.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:498)
            at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
            at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)
            at com.sun.proxy.$Proxy139.setEdge(Unknown Source)
            at sun.reflect.GeneratedMethodAccessor226.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:498)
            at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
            at com.wily.introscope.appmap.em.model.dao.interceptor.ProfilingMethodInterceptor.invoke(ProfilingMethodInterceptor.java:54)
            at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
            at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)
            at com.sun.proxy.$Proxy140.setEdge(Unknown Source)
            at com.wily.introscope.appmap.em.ontology.ModelSynchronization.setEdge(ModelSynchronization.java:744)
            at com.wily.introscope.appmap.em.ontology.ModelSynchronization$5.call(ModelSynchronization.java:490)
            at com.wily.introscope.appmap.em.ontology.ModelSynchronization$5.call(ModelSynchronization.java:1)
            at java.util.concurrent.FutureTask.run(FutureTask.java:266)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
            at java.lang.Thread.run(Thread.java:745)
    Caused by: java.sql.SQLException: ORA-01653: unable to extend table APMADMIN.APPMAP_ATTRIBS by 128 in tablespace APMDATA

     

            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
            at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
            at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
            at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
            at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
            at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:208)
            at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1046)
            at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1336)
            at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3613)
            at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3694)
            at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1354)
            at com.zaxxer.hikari.pool.ProxyPreparedStatement.executeUpdate(ProxyPreparedStatement.java:61)
            at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.executeUpdate(HikariProxyPreparedStatement.java)
            at org.springframework.jdbc.core.JdbcTemplate$2.doInPreparedStatement(JdbcTemplate.java:916)
            at org.springframework.jdbc.core.JdbcTemplate$2.doInPreparedStatement(JdbcTemplate.java:909)
            at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)
            ... 58 more



  • 5.  Re: Team Center has no data
    Best Answer

    Broadcom Employee
    Posted Mar 20, 2019 07:29 AM

    Hi Robert,

     

    The Oracle ORA-01653 error meaning is as follows:

     

    ORA-01653: unable to extend table string. string by string in tablespace string

    Cause: Failed to allocate an extent of the required number of blocks for a table segment in the tablespace indicated.

     

    Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

     

    So you should check with your DBA as top whether there is a space issue and address as appropriate. If you feel the database is using excessive space then you may need to look at the data retention settings you are using as you may be able to tune this. The following KBs deal with database storage issues

     

    PostgreSQL Database file system space is filling u - CA Knowledge 

    APM database is growing fast - too many appmap_sta - CA Knowledge 

    How can we optimize our APM database that is growi - CA Knowledge 

     

    they are not Oracle specific and where they mention running a vacuum in postgres Oracle does not have an equivalent feature 

     

    Anyway - if the system is unable to update the database then that will affect the ability to populate the Team Center data

     

    thanks

    Mike



  • 6.  RE: Re: Team Center has no data

    Posted Jun 07, 2019 03:15 PM
    Hi Robert,

    Yes, if you are seeing that exception stack, then the agents that are parsing the traces are not able to write out the vertices to the database.  Without the vertices, team center has not base to start doing the analysis to display.

     The part of the stack that is of interest is:
    unable to extend table APMADMIN.APPMAP_ATTRIBS by 128 in tablespace APMDATA

    That is either a permission issue or a space issue.  Hopefully you have an Oracle DBA that can take a look to see which one it is.  

    Basically I agree with Michael Cook's response

    hope this helps,

    Billy


  • 7.  RE: Re: Team Center has no data

    Posted Jun 07, 2019 08:03 PM
    You have used all available space within your DB.  I recommend opening a Support request as there are 3 (maybe 4) tables pertaining to vertices within same that need to be deleted and rebuilt.  You'll also want to decrease your settings within the EM Cluster from 365 to something smaller -- say 60 days unless you want to substantially increase the size of the DB.

    ------------------------------
    David Barnes
    Sr. Services Architect
    HCL Technologies
    ------------------------------



  • 8.  RE: Re: Team Center has no data

    Posted Jun 07, 2019 08:15 PM
    Open a support incident.  If your DB is full, you've got 3 or 4 tables within TC pertaining to vertices, attribute that need to be cleaned out and rebuilt.  You've also got a setting within your EM Cluster settings that needs to decreased from 365 to something more reasonable -- perhaps 60 or so.  I've got a customer that dealt with the same situation just a week ago...

    Dave

    ------------------------------
    Sr. Services Architect
    HCL Technologies
    ------------------------------