• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Unexplained database growth on replication target

#1
Hi,

I have a TSM replication source/target pair running version 8.1.8 that has been running with a near constant backup volume for quite a while. Recently the database on the replication target has started to grow ever so slightly. The backup and replication volumes has stayed constant and the database size on the source server is also constant. If the growth continues, I will run out of space for the database in about a month.

The start of growth seems to coincide with some new error messages in dsmffdc.log.
Three messages like these occur every 10 minutes:

[05-19-2020 10:10:36.982][ FFDC_GENERAL_SERVER_ERROR ]: (sdrefcount.c:916) Encountered error 9973 processing range 2184654291979925338 to 2234952175654497472
[05-19-2020 10:10:40.224][ FFDC_GENERAL_SERVER_ERROR ]: (sdrefcount.c:916) Encountered error 9973 processing range -9223372036854775808 to 2234952175654497472
[05-19-2020 10:10:45.230][ FFDC_GENERAL_SERVER_ERROR ]: (sdrefcount.c:916) Encountered error 9973 processing range -9223372036854775808 to 2234952175654497472


Now those are from the servermon scripts and probably mostly harmless in themselves, but if, as they indicate, some 64bit counter has overflowed, maybe there are problems elsewhere.

My suspicion is that the normal database reorganization and cleanup is not running as intended.
Are there some way to manually trigger database cleanup?

Any ideas on where to look further would be appreciated!

thanks.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.8%
  • Keep using TSM for Spectrum Protect.

    Votes: 58 60.4%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.5%
  • Other (please comement)

    Votes: 8 8.3%

Forum statistics

Threads
31,634
Messages
134,818
Members
21,669
Latest member
sammiehung
Top