ORacle Rman Error

[Nobody's Hero]

I've been searching and searching for a thread on this error message, but no luck. Wondering if anyone has seen this b4. I am running rman for Oracle8i. Everytime I try to run a rman rolloff for our archive file I get this:

Failed at load time: Exec format error
shl_load: Exec format error
/app/oracle/local/rmanbin/run_rman[52]: 9752 Bus error(coredump)


The only thing that has changed on the box is our quarterly OS patch load of 80+ patches. Not sure if this is what caused the issue. The script has been running for 2 years.

[Steven E. Protter]

I regret to inform you that the quartery OS patch very much could have done this.

My suggestion is that you relink oracle. This might resolve the problem.

If you want to find the actual cause, look at the patch notes for those that effect the c++ compilers and their binaries.

Also run strings on the core file and see if it provides any insight. It may point out what application doesn't like what the executable is doing.

SEP

[Robert-Jan Goossens]

Hi Robert,

Could you chech if you have the ld(1) and linker tools cumulative patch intstalled ?

---

- JAGad30093: Severity: 5
shl_load causes an exec format error for libcl

----

http://www5.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.patchDetail{PHSS_28435,hpux:800:11:11}|&patchid=PHSS_28436&context=hpux:800:11:11

Best regards,
Robert-Jan

[Nobody's Hero]

This is the linker patch I have installed:

# PHSS_30049 1.0 ld(1) and linker tools cumulative patch
PHSS_30049.LINKER-HELP 1.0 B.11.11

[Nobody's Hero]

Steven, Thanks,

I did a strings on the core file. I can see some rman references in there but I can't make out anything. I am not sure what to look for. Any help is appreciated.

To resolve this problem, do you think I should back out the couple of patches that may be causing the problem. Or re-ignite the box prior to the patch load a forget about the 120 patches?

[Steven E. Protter · Accepted solution]

I would not reignite the box unless necessary.

Steps at this point:

1) Open a tar with Oracle. They may have seen this problem before and can tell you which patch to back out.

2) Open a software call with HP. Have them analyze the core dump(if they do that). They may have your error in their internal database and can tell you which patch blew you up.

3) swverify \* (did i already say this?) back out corrupt patches.

SEP