Geoffrey,
In you situation you must first create a new log volume with the dsmfmt command. Remember the volume must be a multiple of 4MB plus 1 MB in size, i.e. 21MB or 101MB and so forth. Then you can use the "dsmserv extend log new.rec.log 20" to add a new 20MB(actually 21MB at the OS level) log volume to your server environment and now it should come up.
Now lets talk a little about how you got to where you are. The fact that you are stating that you have available space in your log volumes but the server crashed and will not start due to full logs is telling me you are not using the appropriate space triggers to help prevent this situation. You should look into these two commands "define dbbackuptrigger" and "define spacetrigger log" (there is also a "define spacetrigger db" that is useful). The first command can only be used if your log is in rollforward mode (this is the preferred mode except in rare situations) and it will automatically start a DB backup if the log crosses a certain threshold. Thereby, resetting the log so that you will now have ample space. The second command simply increases the size of the log when a threshold is met. It will first use available space to accomplish the task, but it will create additional volumes if need be. Obviously if it creates new volumes you as an administrator will need to take some subsequent actions to clean up afterward, i.e. create permanent volumes and get rid of the auto generated ones. One more tip, the maximum size of the recovery log is 13GB. You should never let your log go to that value! Always leave some space behind in case all other protective methods fail and you have to do what you are about to do now and use a "dsmserv extend log" procedure. Because, if your log was already at 13GB and this happened there would be no recovery other that restoring your DB to a "point in time" of the last DB backup.
I hope this helps you out.
-- Regards, Mark D. Rodriguez President MDR Consulting, Inc.
=============================================================================== MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===============================================================================
Gill, Geoffrey L. wrote:
Server is at 5.1.6.3
I am getting mixed messages from IBM on this and would like to see if there is someone who knows "exactly" how this works and where it is in the manual that says what it "will not" do. Here is the scenario. The log filled and the server would not come up. All log volumes are mirrored to same size log volumes. Total available space is 10.6GB, assigned capacity is 7.1GB, maximum extension shows 3.5GB. The question is can you extend the log "without" defining a new volume while the server is down? After all there is space available. Unfortunately it does not work and I want to make sure it is not supposed to.
Thanks,
Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062
