FAQ: Error Running 64bit Commands

"There’s No Such Thing As A Silly Question" -- does the cliche sound familiar? In this part of pimp-my-rig reloaded, technical questions are answered. Mail them to me and I will post the answers here. If you have a better answer, by all means share it with us.

Q. I recently encountered an error that made me scratch my head. I knew I had encountered it before and had resolved the problem. Unfortunately, my notes were not available at work due to the security policies in place. But when I got home, the putty logs that I saved from before proved really useful.

Encountering weird errors like this one really makes its mark on your memory. To give you an idea what it is, see below. Simple commands like uptime will return errors, and will not run. In fact, all 64-bit executables refuse to run and will give the same error as below.

user@host > uptime
exec(): 0509-036 Cannot load program uptime because of the following errors:
        0509-033 Cannot run a 64-bit program until the 64-bit
        environment has been configured. See the system administrator.

A. Fortunately, I enabled logging on my putty and saved them for future review. And the time for reaping the benefits of that move paid out.

This was how I resolved that problem above. The command to run is "smitty load64bit" or "smit load64bit" (should be executed as root or a privileged user). After smit loads, select "Enable Now".

Once executed, 64bit commands will now run without hitch. No need to reboot the machine.

To my curiosity, I checked the output of smit.log and below is how it looks.

user@host > cat smit.log

[Apr 28 2010, 07:31:21]
    Starting SMIT

(Menu screen selected as FastPath,
        id          = "system",
        id_seq_num  = "220",
        next_id     = "load64bit",
        title       = "Enable 64-bit Application Environment".)

(Menu screen selected,
        FastPath    = "load64bit",
        id_seq_num  = "220",
        next_id     = "load64bit",
        title       = "Enable 64-bit Application Environment".)

(Dialogue screen selected,
        FastPath    = "run64now",
        id          = "run64now",
        title       = "".)

[Apr 28 2010, 07:31:33]

    Command_to_Execute follows below:
>> /etc/methods/cfg64

    Output from Command_to_Execute follows below:

---- start ----

---- end ----

[Apr 28 2010, 07:31:37]
    Exiting SMIT

From the output of smit.log above, you can deduce that if you will not be using smit you can instead use "/etc/methods/cfg64" to accomplish the same results.

You might also be interested in:


We at pimp-my-rig strive to keep on improving, help us reach that goal by leaving comments or constructive criticisms. Don't miss out on our next feature -- subscribe via RSS (What is RSS?).

Share This