• 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.

TDP R3 v6 versioning check on 1 indicative file TDP_VER

#1
Hello all,

While setting up a volume/versioning check for SAP TDP R3 nodes, i came across a type of file being backed up with each full database backup called "TDP_VER", i did not find this in v5 nodes, but only in nodes running v6.x clients.

Neither Google, nor the documentation i checked showed any mention of this file, however i feel it may be worth mentioning here, as it can greatly simplify versioning checks for SAP nodes on the TSM server side. (what i've seen so far, and planned to build was based on expected volumes, with tolerance margins).

Instead, i've set up a little administrative script that shows the SID of the instance, and the the TDP_VER versions with archive date.

SELECT CAST(node_name AS CHAR(25)) as "NODE_NAME",
cast(DESCRIPTION as char(7)) as "SAP_ID", archive_date from
archives where node_name like ucase('$1') and
LL_NAME='TDP_VER' order by DESCRIPTION, archive_date

I hope it's of help to you. If not to replace volume based checks, which are complicated and not always indicative of issues, then as a quick check to indicate if the nodes have any versioning issues, or old instance data.

Any confirmation if these files are present on other people's TDP R3 nodes too would be helpful.

Also any knowledge of similar indicative files present in other TDP's backups would be appreciated. :)

Thanks

Joost.
 

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: 9 18.0%
  • Keep using TSM for Spectrum Protect.

    Votes: 29 58.0%
  • Let's be formal and just say Spectrum Protect

    Votes: 8 16.0%
  • Other (please comement)

    Votes: 4 8.0%

Forum statistics

Threads
31,118
Messages
132,497
Members
21,308
Latest member
mujahikh
Top