augustus 2009 15:10
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: [ADSM-L] Windows TSM server 6.1.2.0 after clean install :
ANR2968E Database backup terminated. DB2 sqlcode: -2033.
The document describes this as being a problem using the Microsoft
management Console (MMC) plug-in for TSM. In the past
: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: [ADSM-L] Windows TSM server 6.1.2.0 after clean install :
ANR2968E Database backup terminated. DB2 sqlcode: -2033.
Stefan,
I was in the beta and I never got a database to backup because of the
api config
difficulties. Fortunately this is all handled now
augustus 2009 15:40
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: [ADSM-L] Windows TSM server 6.1.2.0 after clean install :
ANR2968E Database backup terminated. DB2 sqlcode: -2033.
Been there done that.
Go to www.ibm.com, in the search window put: *1390301*
**
That says what you need to do to get
Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Stefan Folkerts
Sent: Thursday, August 27, 2009 2:48 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Windows TSM server 6.1.2.0 after clean install : ANR2968E
Database backup terminated. DB2 sqlcode: -2033.
I was in the beta as well Bill. :)
But I am
:48 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Windows TSM server 6.1.2.0 after clean install : ANR2968E
Database backup terminated. DB2 sqlcode: -2033.
I was in the beta as well Bill. :)
But I am sorry to say IBM did not do a good job on the 6.1.2.0 Windows
release instance wizard, Wanda pointed me
@VM.MARIST.EDU
Subject: Re: Windows TSM server 6.1.2.0 after clean install : ANR2968E
Database backup terminated. DB2 sqlcode: -2033.
I was in the beta as well Bill. :)
But I am sorry to say IBM did not do a good job on the 6.1.2.0 Windows
release instance wizard, Wanda pointed me the problem
Folkerts
Sent: Wednesday, August 26, 2009 6:25 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Windows TSM server 6.1.2.0 after clean install :
ANR2968E Database backup terminated. DB2 sqlcode: -2033.
I have done a clean install of the 64bit windows version of 64bit TSM
6.1.2.0 on Windows 2008 DC
Been there done that.
Go to www.ibm.com, in the search window put: *1390301*
**
That says what you need to do to get the problem fixed.
What it omits to say, is that you must be logged in with the DB2 userid when
you do it.
**
On Wed, Aug 26, 2009 at 6:24 AM, Stefan Folkerts
