ADSM-L

Re: [ADSM-L] Moving archlog folder

2012-02-08 08:13:53
Subject: Re: [ADSM-L] Moving archlog folder
From: Erwann Simon <erwann.simon AT FREE DOT FR>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 8 Feb 2012 14:04:13 +0100
Hi Zoltan,

If you move the archlog from the old directory to the new one before the server has been restarted, you'll get a message saying that DBM cannot start because the directory is not empty upon restart.

Note that you may need to restart twice : one time to update the configuration, and the second time for real, and then you'll be able to move the archlog.

Best regards / Cordialement / مع تحياتي
Erwann SIMON


Le 08/02/2012 13:57, Zoltan Forray/AC/VCU a écrit :
One of my servers is having disk "issues" and it happens to be where the
tsmarchlog folder is.  The Linux Administrators Guide says to:

Moving only the archive log
You can move only the archive log from one directory to another.
1. Halt the server.
2. Create an new archive log directory. For example:         mkdir
/archivelog2
3. Update the dsmserv.opt option file for the new archive log directory.
For example:   archlogdir /archivelog2
4. Restart the server.
5. Move the archive logs from the old directory to the new directory.
Preserve any subdirectory structure. Use and verify a recursive copy
directory command. For  example:  cp -r /archivelog/* /archivelog2
6. Optional: Remove the old directory.

I am questioning that it says to "Restart the server" before copying the
contents of the "old directory"?????   I would have thought you needed the
old directory BEFORE starting up the server?  Or do I completely NOT
understand how this works (my suspicions) since I am not a DB2 person....


Zoltan Forray
TSM Software&  Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

<Prev in Thread] Current Thread [Next in Thread>