Online Tutorials & Training Materials | STechies.com
Register Login

Indications exist for HANA garbage collection problems

Chandan Singh Parihar || 16 Jun 2015 1:37 pm || 1

Which indications exist for SAP HANA garbage collection problems?


Comments

  • 01 Jul 2015 12:17 pm Helpful Answer

    Garbage collection problems are often linked to long running transactions. The following indications can directly or indirectly point to problems in the garbage collection area.

    The following trace file entries indicate potential issues in the area of garbage collection:

    mvcc_anti_ager.cc(01291) : There are too many un-collected versions. ('number of versions > 1000000' or 'maximum number of versions per record > 100000')The cursor possibly block the garbage collection of HANA database.

    mvcc_anti_ager.cc(01291) : There are too many un-collected versions on table ""."" ('number of versions for one of the partitions > 1000000' or 'maximum number of versions per record > 100000')The transaction blocks the garbage collection of HANA database.

     

    mvcc_anti_ager.cc(01199) : long running uncommitted write transaction detected.

    mvcc_anti_ager.cc(01082) : The Connection is disconnected forcefully because it is blocking garbage collection for too long period.Statement.cc(03190) : session control command is performed by ..., user=SYSTEM, query=ALTER SYSTEM DISCONNECT SESSION ''

    mvcc_anti_ager.cc(00834) : long running cursor detected.The open cursor possibly blocks the garbage collection of HANA database. Please close a cursor in application or kill the connection by "ALTER SYSTEM DISCONNECT SESSION '' "