Hi Lance
I'm not sure that the APAR you have linked is actually connnected to your
problem. Your issue is that after the extend, a DB backup is triggered which
fails to read the database, while the APAR fails immedadiatly upon format. The
first APAR you linked is also about volume size over
OK, I hate to admit this but when purchasing 3592JB media, the question is
always asked, Do you want them initialized?
What exactly does initialized mean as far as 3592JB cartridges are concerned
and why would I want or not want them initialized?
I've searched online and cannot seem to find an
Short answer: ordering them initialized means you don't have to write the
internal label when you get them (label libv).
Long answer:
TSM requires a standard IBM tape (internal) label to be written at the
beginning of the tape before they are used the first time.
If you order the tapes
Based upon communal experience: Don't trust a tape vendor to properly
initialize tapes. We've experienced situations where we depended upon the
vendor having done so, when in fact they did not. And I would not want my very
expensive new tapes being subjected to unknown equipment handling at
Initialization shortly means software labeling. Initialized tapes do not
need to be labeled by TSM. They cat just be used as empty labeled cartridges
when checked in.
I'm looking for recommendations experiences on TSM SSL.
There is interest from our security group here in enabling SSL for TSM
sessions. Naturally, the easiest plan for the security folks would be to just
enable it for everything. There is guidance in the IBM documentation to only
use it
Can you mount the database? If so, perhaps you could perform some queries on
the database to confirm the mailbox is there. If it is there, see if you can
convince Exchange to move/restore it to another database. I have not tried to
restore an email account to a child domain. When backed up,
Hello everyone,
To date, I have not had any problems upgrading/patching my one production
6.1.x server - just getting ready to upgrade from 6.1.3.4 to 6.1.4.1
(anyone else do this on a Linux platform ? Any problems
- done yesterday on Redhat 5, no problems...
Personally, I installed more TSM
On Wed, Sep 08, 2010 at 08:26:16AM +0200, Daniel Sparrman wrote:
The first APAR you linked is also about volume size over
250GB, not the entire database. I'm guessing your database
voluimes are below 250GB.
...
Do you know if the volume /dev/rdsk/c0t7d0s4 was allocated
before the extend, or
Are you sure nothing else was possibly using that raw volume?
Wondering if this is the only instance of TSM on this server? I know in my past
experience with SUN systems that you can mistakenly grab raw volumes like this
that may have been in use by something else.
Do you have a q dbv, q logv,
On Wed, Sep 08, 2010 at 05:30:15PM +, Mike De Gasperis wrote:
Are you sure nothing else was possibly using that raw volume?
I have dedicated disks for each DB mirror. Nothing else
uses those disks.
Wondering if this is the only instance of TSM on this
server?
Yes, there's only one TSM
You are invited to attend the following IBM TSM Technical Exchange Webinar:
Wednesday, September 15, 2010 – 11:00ET / 10:00CT / 8:00PT
Fastback Overview with Updates for V6.1.1
Abstract:This session will cover a basic overview plus updates for the
following Fastback V6.1.1.0
On Sep 7, 2010, at 7:53 PM, Lance Nakata wrote:
I found IBM note
http://www-01.ibm.com/support/docview.wss?uid=swg21386330 which said
to do a SET MIRRORREAD VERIFY in dsmserv.opt and restart TSM.
However, that does not work:
You were probably frazzled by your situation...
The technote says
On Wed, Sep 08, 2010 at 02:40:27PM -0400, Richard Sims wrote:
I found IBM note
http://www-01.ibm.com/support/docview.wss?uid=swg21386330 which said
to do a SET MIRRORREAD VERIFY in dsmserv.opt and restart TSM.
However, that does not work:
You were probably frazzled by your situation...
14 matches
Mail list logo
