ROOTVG

AIX => Administration => Topic started by: gz3xzf on May 21, 2008, 04:50:11 PM



Title: 0511-702 Cannot open or create - during alt_disk_install
Post by: gz3xzf on May 21, 2008, 04:50:11 PM
Gents

I am upgrading a 5.2 ML4 system to 5.3 TL6 SP3, during the alt disk install the installation failed in phase 5 with a: -

restore: 0511-702 Cannot open or create ./usr/bin/rksh: Cannot open or remove a file containing a ru
nning program.
0505-165 nimadm: Error during restore of base operating system.

Has anybody seen this?


Title: Re: 0511-702 Cannot open or create - during alt_disk_install
Post by: Michael on May 22, 2008, 02:33:06 PM
Unfortunately, with AIX 5.2 (forgot which ML, but quite old like yours) and nim alt_disk_install - I got the same failure - and while suggesting it as an improvement to the standard using CDs method during a class.
I sure felt foolish then. And I have been afraid to try it since.

Maybe updating to a newer version of AIX 5.2 will help - but it is probably a lot easier to just do the migration using CD's rather than nim. However, if you have a lot of systems to migrate I would suggest installing a test system with AIX 5.2, update that the latest AIX 5.2 ML (10 I believe) and try the nim based alt install and see if that works. If it does it may be worthwhile to do a update_all to your AIX 5.2 systems, and then perform the migrations.

btw: there are some tricky issues with updates toAIX 5.3 ML6 and ML7 (I recommend updating to ML7 since you are doing all the work anyway). Make sure your /tmp has at least 90M of free space so that the bosboot can be built.


Title: Re: 0511-702 Cannot open or create - during alt_disk_install
Post by: gz3xzf on May 22, 2008, 02:59:37 PM
Thanks for the reply Michael, I have separately updated the alt_disk_install version to 5.2.0.96 before starting the process. The other thing is that this is the last server in a enterprise of around 30 servers that needs to be upgraded, all the others went OK.

I have raised a ticket with IBM and they are awaiting a debug version of the install to complete so that we can see more detail on the error.

I have also taken the step of stopping the Tivoli TDP and TSM clients incase they were finding the files for backup whilst the NIM was trying to over-write.

I'll post some more when this round of testing comes to an end.