Upgrade from 11.0 to 11i usr/lib/dld.sl: Unresolved symbol

[Lisa Mauer]

Hi All;
I upgraded from 11.0 to 11i over the weekend and am seeing the following errors when I try and bring up some of our applications (32 bit):

usr/lib/dld.sl: Unresolved symbol: t_strmsgsz (storage) from insurance1
usr/lib/dld.sl: Unresolved symbol: t_strqlen (storage) from insurance1
usr/lib/dld.sl: Unresolved symbol: t_strctlsz (storage) from chgentry

From what I can see these are in usr/lib/libxti.2.

What I also see is:
We have 2 other servers running 11.0 and when I do "nm libxti.2 |grep t_strctlsz" I can see it (and the other 2 listed above) in the library. When I go to the box that is updated to 11i and run the same command it isn't there.
There are links that link back to libxti.2 dated the same day and time I was running the update.

This is in the swagent.log
* Installing fileset "Streams.STREAMS-MIN,r=B.11.11" (237 of
632).
* File "/usr/lib/libxti.2" could not be removed. It was renamed
and added to the cleanup file "/var/adm/sw/cleanupfile".
* Installing fileset "Streams.XTI-ENG-A-MAN,r=B.11.11" (238 of
632).

I have a call already into HP, but thgouht I would post this to see if anyone had similar problems....

[harry d brown jr]

Lisa,

When you say you "upgraded", did you do a fresh install of 11i or do an "upgrade"?

live free or die
harry

[Lisa Mauer]

I upgraded from 11.0 to 11i, I did not do a cold install.
Thanks
Lisa

[Deepak Extross]

Would suggest a cold install.
See this link http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x74f6f9beca68d511abcd0090277a778c,00.html

[Paula J Frazer-Campbell]

Hi Lisa

Sorry but normally the quickest way to resolve your problem is to save out your volume info (mnttab,inittab etc.

Unmount your non OS lvols.

Them do a clean install of the OS.

Patch.

Remount your volumes.

Test.

HTH

Paula

[Tom Dawson]

Lisa,

Are you by chance running Oracle on this server? If you are, you probably need to re-link Oracle. This is the error we get when we forget to re-link Oracle.

Tom

[Lisa Mauer]

A cold install isn't always the answer and isn't feasible for us or our customers. The upgrade went fine and we have the Oracle system with all of our apps running fine, this seems to be an issue with our 32 bit applications and Supra.

[Tanya_2]

lisa,

does your xti application is using these variables ?

tanya
-------------------

[Tanya_2]

lisa,

does your xti application is using these variables ?

tanya

[Lisa Mauer]

Actually we were just called this morning from HP, they need to do a site specific patch because we use MF Cobol and BEA Tuxedo and somewhere in the Tuxedo code they reference those symbols.

I can say though that we upgraded from 11.0 to 11i and if you do the research on how to do it and what patches you currently have that you may need in 11i - It is not a bad upgrade at all. I know a lot of people say cold install it, but if you can't and you decide that the research will take you less time then the reinstall of all applications, it's a pretty easy update.

[Tanya_2 · Accepted solution]

lisa

If you think some third party software (tuxedo) is using/generating these symbols, then what you could do is, just get all your object files (.o) and relink the same with tuexdo on 11.11 and I think it will work....

tanya

[Lisa Mauer]

That is true - but for us this is not feasible as then all of our customers will need to re-link which means us re-linking and then sending the new code to them as we only send out the executables (already linked). Then we would need to support 2 versions of everything here in house also to have what all our clients will have.... Re-linking was a thought - but also a last resort. Thanks for the info though!

[Tanya_2]

lisa,

some thoughs. see my comments.

That is true - but for us this is not feasible as then all of our customers will need to re-link which means us re-linking and then sending the new code to them as we only send out the executables (already linked).

tanya:

This is getting curious.... I didn't get why do you need to send new code ??? Customer (end user) only needs executables (unless otherwise they would like to tweak/enhance the code)

What I am trying to say is:

1. Have your .cbl files.
2. Recompile these files again with Tuxedo software (and anyother softwares) on 11.11 system.
3. Get the resulting executable and release this to your customers. I believe it will work on both 11.0 and 11.11.
(This doesn't require source code to be sent to the customer)

BTW, Are you using -U option?. As per manpage
-U means "dynamically resolve unresloved symbols". If you are using this option, do you think it is really required??

If -U option really not required, then could do the same exercise on 11.0 itself and in this you don't have to maintain 2 versions.

Hope this helps.

-tanya
<<<>>>

Then we would need to support 2 versions of everything here in house also to have what all our clients will have.... Re-linking was a thought - but also a last resort. Thanks for the info though!

[Lisa Mauer]

The problem is the "releasing" to customers. For us that would be a very big project as we have many customers who are on everything from 10.20 to 11i, with many different versions of middleware in between, plus different versions of our own application. For us to recompile or relink anything for an upgrade to 11i from 11.0 will cause us a great deal of development work and also support issues. We also need to maintain the exact same environments onsite to troubleshoot client problems.

The "-U" option is what we think is causing the problem, but is required by the middleware because we load our Cobol programs in at run-time. That is the default behavior of the buildserver command supplied by Tuxedo.
Believe me, we have tried to look at every angle.
Thanks!

[Tanya_2]

What I meant was:

If the cobol programs really don't need to use "-U option", then you could simply recompile and relink without -U option on 11.0 itself. So that unresoloved references will not be loaded dynamically. In that way you don't the error at run-time.

[Camel_1]

I am planning to upgrade OS from 11.00 to 11.11 next month, I will do the upgrade instead of cold install. Currently we are using MF COBOL 4.1.10 on HPUX 11.00, is this COBOL version support on HPUX11.11? Do I need to upgrade the COBOL when upgrading the OS?

Thanks.

[Dennis Raudenbush]

Lisa,
We're attempting a proof of concept transition of a critical app from 11.0 vclass to 11.11 rp8400 that was cold installed and we experienced the identical problem and used your case to get an emergency patch from HP. The patch replaced the missing t_str* guys and we got past this problem. We're also using MF/COBOL at of course later release and having problems of missing symbols (ex: _HPnewmFyn_entry for example that was in the old libcobol.1 but not in the new libcobol.1
Sorry I can't give you the exact patch number as my email MS Exchange Server (damm MS) is unavailable.

Poking around hp docs it seems newer MF/Merant Cobol removed Motif and perhaps a bigger issue, HP-UX DCE support. I'm not close to our app but it's low level 'C' middleware to higher level COBOL ProC/sql

Our Oracle 8.0.4 db comes up fine without needing to recompile. Any others out there have better luck?

john creighton

[Lisa Mauer]

There is finally a General Release Streams patch available for download from HP for this problem. It is PHNE_27703, has 2 dependency patches and requires a reboot.