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

Is there a way to delete TSM node or nodes from db2?

moon-buddy

ADSM.ORG Moderator
#1
For one reason or another, I cannot remove a node from within the TSM server.

Is there a way (or, has someone done this) to remove (drop the node) the node from DB2? This means doing the node drop activity using DB2 tools.
 

marclant

ADSM.ORG Moderator
#2
The short answer is yes.

The long answer is that it may not delete other references to the node in other tables and may end up with inconsistencies in the database. I'd recommend pursuing the problem with remove node instead.
 

moon-buddy

ADSM.ORG Moderator
#3
I agree that 'remove node' would be the best option but I cannot figure out why TSM cannot delete the filespace for the node. Running a 'delete filespace' finishes with no errors but running a 'remove node' after (even after a day), the TSM server says inventory exist. The node has been decommissioned a long time ago.

As you know, if inventory exist, removing the node is not possible.

Do you know the procedure to do this from the DB2 side, i.e., delete the filespace and delete the node?
 

moon-buddy

ADSM.ORG Moderator
#5
'q occupancy <node_name> f=d' is not a valid command (f=d part).

Anyways, it shows the data - system state remaining:

Code:
Node Name      Type     Filespace      FSID     Storage         Number of        Physical         Logical
                        Name                    Pool Name            Files          Space           Space
                                                                                 Occupied        Occupied
                                                                                      (MB)            (MB)
----------     ----     ----------     ----     ----------     -----------     -----------     -----------
NODE1          Bkup     NODE1    -        1     WINTEL         102,077,914      299,290.78      297,285.78
                         \SystemS-
                         tate\NUL-
                         L\System
                         State\Sy-
                         stemState
For system state - this size is NOT normal. By the way, no dedup.
 

marclant

ADSM.ORG Moderator
#6
So, no dedup data. I wanted to rule that out because the first node to do a backup will own the extents created. If a 2nd node does a backup and some extents are common to the 1st node, they are referenced. So when you delete the filespace for the 1st node, Q OCC still shows it, but as DELETED. That's because the node can't be deleted if it owns extents referenced by other nodes. This is NOT your case, so let's move on.

I'd try to delete that filespace again. Don't need to target that one specifically, just: DEL FI NODE1 *
 

moon-buddy

ADSM.ORG Moderator
#7
So, no dedup data. I wanted to rule that out because the first node to do a backup will own the extents created. If a 2nd node does a backup and some extents are common to the 1st node, they are referenced. So when you delete the filespace for the 1st node, Q OCC still shows it, but as DELETED. That's because the node can't be deleted if it owns extents referenced by other nodes. This is NOT your case, so let's move on.

I'd try to delete that filespace again. Don't need to target that one specifically, just: DEL FI NODE1 *
I ran multiple 'delete filespace <node> *' and the deletion process completes BUT the filespaces still remains. I even tried to be FSID specific for this remaining filespace but the same result.

I went even further as to unload and reload the TSM DB to no avail.

Really puzzled as this is happening to just this node.
 

chad_small

ADSM.ORG Moderator
#12
Have you tried deleting the objects directly using the

delete object 0 <object_id>

process like many have done for orphaned Oracle data?

select 'del object 0', object_id from backups where node_name=<NODE_NAME>
 

marclant

ADSM.ORG Moderator
#13
Try to decommision the node in Spectrum Protect, before you decommision it, create a new domain that only has a default management class, and set the retention to 1 day. That way it should expire quick. Actually you could move to a new domain after decommissioning too.
 

moon-buddy

ADSM.ORG Moderator
#14
Try to decommision the node in Spectrum Protect, before you decommision it, create a new domain that only has a default management class, and set the retention to 1 day. That way it should expire quick. Actually you could move to a new domain after decommissioning too.
I was thinking of doing this before I do Chad's suggestion - had done this before and worked well.

Stay tuned.
 

moon-buddy

ADSM.ORG Moderator
#15
Update:

Changed retention for the node in question to 1 day, run expire inventory against the node and then delete filespace to be sure.

Did a q filespace and node shows the FSID with ZERO capacity; and still cannot delete the node since inventory still exists!

Dumbfounded by this!
 

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

    Votes: 23 52.3%
  • Let's be formal and just say Spectrum Protect

    Votes: 8 18.2%
  • Other (please comement)

    Votes: 4 9.1%

Forum statistics

Threads
31,080
Messages
132,333
Members
21,277
Latest member
jbtepinier
Top