Server does not start because of full Database log.

There's a utility you can use to define another log volume. Check out the TSM admin. manuals for details.
 
There are a few ways to do this, certainly if you have the webadmin you can manage your database that way.



The concept is as follows:



1. define a space for the db or recovery log

2. tell TSM that this space is ready for use for the db or recovery log

3. run query db to verify that your db space has grown

____________________________________



"help define log" at a admin cmd line will give you the parameters but here is a specific example:



define logvol c:\tsmdata\server1\dbext1.dsm 24 wait=yes (I call it logext1.dsm to distinguish it)

extend log 24



What you've done here is tell tsm to define a dbvolume at filename-location c:\....\logext1.dsm with a size of 24 mb and then to wait until completion.



Then you used the extend command to extend the existing database.



Then query db to find out if it has been allocated.





Hope this helps....





swtoronto



<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Quote:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><BLOCKQUOTE>How do i solve this?? (TSM 5.1) :confused:

(I am a novice user to TSM) </BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>
 
Back
Top