Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
We use a very old database on redhat 3 before , it works fine. We have just installed a Redhat 5 and try to run this database on it , it pop the following error .
"symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference"
I tried to set the follwoing on .bash_profile but do not work .
the error is as below :
"error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory"
Can advise how to fix it ?
Again, have you CONTACTED RED HAT SUPPORT????. You seem to be using RHEL, and this has been asked of you several times...if you're paying for RHEL, you have access to their support, and they can advise you on such things.
Also...copying libc files from one system to another is a VERY dangerous thing to do. You again provide next to no details (what KIND of database? program that's accessing it??), so it's hard to say. Best advice would be to back that database up, and import it into something current, so that you don't have these issues going forward.
Best advice would be to back that database up, and import it into something current, so that you don't have these issues going forward.
this, seriously this..
Even if you manage to cobble something together that 'works' it won't be supported by the relevant vendor(s) and is guaranteed to be unstable sooner or later.
contact red hat tech support
you ARE paying them for the tech support -- use it
a server license is NOT cheep - so use the support that you are paying for
have them help you migrate from an ancient rhel3
to the current RHEL
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.