Hi Yashwanth,
param_getvolsall outputs all volumes including the ones i added just before the problems started.
sdbregview -l shows all components upgraded.
xinstinfo sid did not report any problems either.
The problem as i see is at the end of the server patch are 3 pending steps
1) attach/detach all volumes)
2) load system tables
3) verify catalog.
steps 2 and 3 will be successfull if step 1 were to run fine.
step1 fails at detaching volumes 17,18 and 19 which are the newly created volumes. The volumes perse are created as dbm.prt output shows return code zero when executing volume creation steps. The volumes are visible in complete from OS level and from DBM. Somehow this is not reflecting in the config file i am guessing due to corruption and other reasons and that may be the reason for not being able to detach new volumes or so I think.
I can restore previous config file and can run param_directput to manually update config file to reflect the volumes correctly. I just need sap/scn team to validate this so I can try this and have support from sap just incase things go south Image may be NSFW.
Clik here to view.
As to the backups, i have 2 good backups. I am worried if the problem occurs again, i want to be in control so restore would be the last resort for me.
Regards
Kalyan
