Road to Linux Red Hat.

mig28mx · #1 27th November 2008, 17:39

Hello all,
The prhase, You have to cut maintainance fees. Are a well known phrase for all of us, IT professionals.
To do this my company have decided not to upgrade our existing HP9000 servers. The quotations for do that was excessive. So, we look up for Linux on Intel Servers.

After a long trip to migrate HP-UX HP9000 servers to Xeon-Red Hat ES, (around 10 days), Im thinking to post a document where it contains the problems and solutions founded on this adventure. Me and the Infor's consultor, spend hours, even in weekends, in surfing Internet forums to see if someone have found a solution for a specific problems.

I believe that the effort pays the deal. The performance was greately improved. Just to give an expample, the dump of our company 0 tooks around 2 hours to generate and it have a 1.4 gb of size. To upload that file in the new servers, it tooks 15 minutes.

Hope this helps.

Han Brinkman · #2 27th November 2008, 22:51

Did you asked your questions also on this forum? One of us could probably have helped....

mig28mx · #3 27th November 2008, 23:30

Hello Han,
Yes, I have post one question regarding, shmvalues.

The weird thing is: Suposedly, Infor have all the knowledge and how's to make a succesfull migration... but when the consultant begins to say, Hey, why you don't reinstall the servers and put it on 32 bits?, or Hey, you should have choosed windows servers for your migration... the things going bad. And have to act quickly.

Thank you..

instant000 · #4 3rd December 2008, 16:57

Quote:

Originally Posted by mig28mx

After a long trip to migrate HP-UX HP9000 servers to Xeon-Red Hat ES, (around 10 days), Im thinking to post a document where it contains the problems and solutions founded on this adventure. Me and the Infor's consultor, spend hours, even in weekends, in surfing Internet forums to see if someone have found a solution for a specific problems.

mig28mx:

Please post what you found. I would like it, if only for the sake of having the documentation available, when we do our own migrations.

mig28mx · #5 3rd December 2008, 17:38

Hello,
I´m processing that document!
As soon as I finished I will upload as promise.

Regards.

Thamarai · #6 5th February 2009, 06:25

hi mig,
Could you please post the document, if you would have processed it. We are in the process of installing BaanIV in linux, but we are facing problem in connecting through BW client.

Thanks in advance,
Thamarai

mig28mx · #7 5th February 2009, 17:16

Hello,
I didn´t finalized the promised document. But I will glad to help you.
What kind of error do you have?
Can you post it?
Me or any other member of the board can help you.

I´m expecting post the promised document by the end of february.

Sorry for the delay.

Thamarai · #8 6th February 2009, 06:13

Hi mig,
Thanks for your Reply. We have installed BaanIVc on RHEL5.0 with Oracle10gR2 standard. The installation was successfull. While opening through ba6.1 the system works fine. But while connecting through BW client even with latest version, we are getting error as REXEC failed to host. Error in ipc_boot6.1. We have installed the porting set 6.1c.7.20.
Please advice us where to make changes to connect for BW client.

Thanks in advance,
Thamarai

grzegorz · #9 6th February 2009, 14:15

Quote:

Originally Posted by Thamarai

But while connecting through BW client even with latest version, we are getting error as REXEC failed to host. Error in ipc_boot6.1.

I've seen that before. There was a known problem with rexec on some operating systems. First try to put your workstation IP number to /etc/hosts file on the server. If it helps for one workstation, you may put all IP's to /etc/hosts or you may consider BaanLogin instead.

p.cole · #10 6th February 2009, 15:20

I'd recommend BaanLogin. Rexec is insecure, and transmits passwords in plain text over the network!

mig28mx · #11 6th February 2009, 22:09

Hello,
This problem is caused due to Red hat has not enabled REXEC service by defalut. So, if you choose to connect your clients by this service you must enable it before.

The steps are:
1.- Install RPM rsh-server, included with Red Hat.
2.- Execute ntsysv and enable rexec. Here you can also enable rsh and rlogin.
3.- Restart xinetd using /sbin/service xinetd restart

Hope this helps.

Thamarai · #12 16th February 2009, 10:00

Hi Mig,
Thanks for your reply. Somehow we managed to login through Baanlogin from the client. But, now the root login is not getting logged through BW client. It says username & password is not correct. Any Suggestions Please...

Thanks in advance,
Thamarai

Andreas · #13 16th February 2009, 10:42

Hi Thamarai,
don't know if it's related to your problem, but we had issues with BaanLogin when the BaanLogin Deamon was started on server and the environement variable USER was set on OS (root in our case). In that case we were not able to login through BaanLogin (on porting set 7.1d.13).
So we had to stop the BaanLogin daemon, unset the USER variable in shell and afterwards start the Login deamon again.

Maybe you can give that a try,

Andreas

mig28mx · #14 11th September 2009, 00:41

Hello All,
As I promised a long time ago, I finished the document.
Here is. Any comment or suggestion will be appreciated.

Hope this helps and good luck on your migration process.

Regards.