topic Re: Error exec(2): could not load a.out in HP-UX 11.11 in Operating System - HP-UX

Error exec(2): could not load a.out in HP-UX 11.11

KhanhLN — Mon, 01 Dec 2014 07:51:02 GMT

Dear all,

I got a problem while execute a script/program

# ./tnsping
exec(2): could not load a.out

I tried to using: #ulimit -s 131072

It's not worked.

How could I fix this problem?

Many thanks in advance.

P.S. This thread has been moevd from HP-UX > System Administration to HP-UX > databases. - Hp Forum Moderator

Re: Error exec(2): could not load a.out in HP-UX 11.11

Dennis Handly — Sat, 29 Nov 2014 00:59:48 GMT

>How could I fix this problem?

You need a better error message that tells you exactly what's wrong.

Where did you get tnsping? Is it suppose to work on 11.11?

What do these show:

file tnsping

chatr tnsping

ldd tnsping

You may need to talk to Oracle about this and make sure you have the right version.

Re: Error exec(2): could not load a.out in HP-UX 11.11

Eric Antunes — Fri, 05 Dec 2014 14:03:44 GMT

Hi,

It seems you are running tnsping without parameters and with the wrong credentials (root). Try again, as RDBMS or APPS user (oracle or applmgr):

$tnsping <SID>

Re: Error exec(2): could not load a.out in HP-UX 11.11

Dennis Handly — Sat, 06 Dec 2014 07:00:02 GMT

>It seems you are running tnsping without parameters and with the wrong credentials

While that may be true, I'm not sure how those could cause that loader error.

Re: Error exec(2): could not load a.out in HP-UX 11.11

Eric Antunes — Fri, 12 Dec 2014 15:21:50 GMT

Dennis,

I suppose the loader error is a permission issue of an Oracle executable being run by root...

Best Regards,

Eric

Re: Error exec(2): could not load a.out in HP-UX 11.11

Dennis Handly — Sat, 13 Dec 2014 01:53:48 GMT

>I suppose the loader error is a permission issue of an Oracle executable

I would expect a more specific permission error. It could be a not a PA-RISC executable?

Re: Error exec(2): could not load a.out in HP-UX 11.11

Eric Antunes — Mon, 15 Dec 2014 09:14:28 GMT

We may never know ;-)