Problems with 11iv3 Patch Bundle March 2011

[Sven Bergmann]

hi,

i've downloaded the latest patch bundle for 11.31 as zip-file and created a depot on the ignite server via "./create_depot_hpux.11.31 -d /ignite/depot/..."

in the INDEX file i've created a new cfg clause with the core release from september 2009 and this new patch release from march 2011.

this is my standard workflow and it works for years.

the installation of a client ends with a warning (at the step "run the sd configure scripts"). the log says, that several products from the core (!) have unresolved dependencies (phco_38048 & phco_39831). but these patches are superseeded in the QPK (phco_40292) & HWEnable (phco_41483) bundles from the patch release March 2011.

fact 1: the installation without the patch bundle march 2011 works fine

fact 2: the depended patches are superseeded by patches in the patch bundle

it's a little bit strange. i don't know why products from the core have this unresolved dependencies.

any idea????

[Sven Bergmann]

another striking feature is the created config from the downloaded patch bundle depot has no -xpatch_match_target=true entry in sw-source part of the ignite config (make_config).

this means that during the automated ignite installation the patch bundle is not installed!

after i set this line manually in the cfg (in the past this line was set automatically) the patch bundle is installed...but with the problem i posted in the post above.

[Michael Steele_2]

could you attach the swjog file please?

[Vivek_Pendse]

Hi,

After you run ./create_depot, you have to actually copy the depot with swcopy.

You need to add path of that swcopy in INDES file exactly in cfg (os) where it's needed.

It should run, bcoz, what happens_--> first the os will be installed & then the additional patch bundle will be installed.

Can you send the install.log of that client?

Thanks,
Vivek

[Sven Bergmann]

hi,

i don't think that i need the additional step to swcopy the patch bundle depot. i think a create_depot to the ignite depot destination is enough! and of course...the patch bundle cfg is in the right clause of the INDEX file.

have a look at the attached install.log. the patch bundle depot is /ignite/data/depots/Rel_B.11.31/patch_bundle_1103.

[Sven Bergmann]

...and now the swjob log

[Sven Bergmann]

and here's the proof that the superseeded patches are in the patch bundle depot.


# swlist -v -s /ignite/data/depots/Rel_B.11.31/patch_bundle_1103 | grep PHCO_40292
PHCO_40292 PHCO_40292,r=1.0,a=HP-UX_B.11.31_IA/PA,v=HP
contents PHCO_40292,r=1.0,a=HP-UX_B.11.31_IA/PA,v=HP
contents PHCO_40292,r=1.0,a=HP-UX_B.11.31_IA/PA,v=HP

# swlist -v -s /ignite/data/depots/Rel_B.11.31/patch_bundle_1103 | grep PHCO_41483
contents PHCO_41483,r=1.0,a=HP-UX_B.11.31_IA,v=HP
PHCO_41483 PHCO_41483,r=1.0,a=HP-UX_B.11.31_IA,v=HP

[Vivek_Pendse]

In which OE you are building these March2011 patches?

[Sven Bergmann]

11.31 DC OE...with newest patch bundle (march 2011)

[Vivek_Pendse]

Why can't you directly copy the March2011 patch bundle in to OE target & re-compile the config file (make_config).
So, it will clear your doubt while copying the depot of dependancies instead of scratching your head w/o direction.

[Sven Bergmann]

i think this is not a clean procedure. so every 6 months i copy a new patch bundle in the "old" patched core depot. after one or two years the core bundle includes several patch bundles and everytime i cross my fingers that the installation will work without problems.

as i wrote in the first post...this workflow (seperate depot for patch bundles) works for years without problems! until today. :(

but ok...i'll try your suggestion...

[Michael Steele_2]

a) You have not attached the swjob - This HP Software Manager run via Ignite

"sm job log -v 000001".

There should be a summary like this:

b) This is not SD-UX or SWA - You are deploying a new OS.

c) This is not a PATCH Update

d) OF COURSE YOU ARE UPDATING THE CORE WITH THIS APPLICATION - YOU ARE INSTALLING A NEW OS!

e) "...(at the step "run the sd configure scripts..."

sd configure scripts is a reference to the SD-UX utility. That would be swcopy, swinstall, swjob, swlist, NOT SOFTWARE MANAGER.

[Sven Bergmann]

@michael: your "sm job" syntax is not correct

@all:

i've tried vivek's suggestion and it works. the procedure in detail:

- swcopy core depot to a new one

swcopy -s /.../core_1009_dc \* @/.../core_1009_dc_1103


- swcopy the contents of the patch bundle to the new core depot

swcopy -s /.../HWEnable11i... \* @/.../core_1009_dc_1103
swcopy -s /.../FEATURE11i... \* @/.../core_1009_dc_1103
swcopy -s /.../QPK1131... \* @/.../core_1009_dc_1103


- swremove the old patch bundle from the new core depot (otherwise errors will occur)

swremove -d \QPKBASE,r=.... @/.../core_1009_dc_1103
swremove -d \QPKAPPS,r=.... @/.../core_1009_dc_1103
swremove -d \FEATURE11i,r=.... @/.../core_1009_dc_1103
swremove -d \HWEnable11i,r=.... @/.../core_1009_dc_1103

- make_config

- new INDEX clause


i don't know why my old workflow doesn't work anymore. but anyway...i've no problem with a new procedure.

so thanks to point me to right direction.