Hi, all, I update it from 5.1.1.0 to 5.1.5.1, and restore db, but space is still not sufficient. so I format it: dsmserv format 1 log1.dsm 9 1 db1.dsm 50. and restore db succeed. I am not sure if ANR2958E will happen again.
Does V5 have database size problem? I don't have it on v4.2.1.0 at all. (ANR2958E SQL temporary table storage has been exhausted..) Maybe keeping on 4.2.1.0 is not a bad idea, right? Thanks, Tao Jiang Coban Research & Technologies www.cobantech.com 713-271-7888 ext. 207 ----- Original Message ----- From: "Fred Johanson" <[EMAIL PROTECTED]> To: "Tao Jiang" <[EMAIL PROTECTED]> Sent: Wednesday, October 30, 2002 1:42 PM Subject: Re: TSM 5.1.1.0 > The steps, from the command line of the server are: > > 1. Format a new logvolume with dsmfmt > 2. Add the new logvolume with dsmserv extend log > 3. Restart the system. > > > At 01:15 PM 10/30/2002 -0600, you wrote: > >No. I have to do that after initial configuration, right? > >Thanks, > >Tao > > > > > > > > > Did you format the log space first with the dsmfmt command?? > > > > > > > > > At 12:38 PM 10/30/2002 -0600, you wrote: > > > >Hi, > > > > > > > >My TSM 4.2.1/win2k NT worked well for a while. I upgraded it to 5.1.1.0. > >I > > > >did not restore database, and device configuration, opt files etc...but > >it > > > >worked fine. Recently I reinstall windows, install TSM 4.2.1 and install > > > >5.1.1.0, go through initializtion wizard. But I met the following > >problems: > > > >ANR9956E Unable to load procedure address from dynamic link library > > > >ADSMLICN.DLL. > > > > > > > >ANR2958E SQL temporary table storage has been exhausted.. > > > > > > > >I tried to extend db, but it does not work. > > > > > > > >ANR2436E EXTEND DB: Insufficient space to extend database by requested > > > >amount.. > > > > > > > >Thanks for any information. > > > > > > > > > > > > > > > >Tao Jiang > > > >Coban Research & Technologies > > > >www.cobantech.com > > > >713-271-7888 ext. 207 >
