Sponsored Content
Operating Systems Linux Red Hat Trouble with installed / not installed rpm unixODBC/libodbc.so.1 Post 302544164 by rkirsten on Wednesday 3rd of August 2011 05:22:00 AM
Old 08-03-2011
Trouble with installed / not installed rpm unixODBC/libodbc.so.1

Hey there,

i run 1: on my server (RHEL 6) and getting response that the libodbc is not installed. If i use yum for installation, it tells me, there is no package like this ( 2: ). Since in the description of Definiens is mentioned that the Run-time dependency is unixODBC (libodbc.so.1), I assume these libs are somehow equal. Is there any possibility to tell the Definiens-GRID rpm use the installed unixODBC ( 4: )? I really appreciate any answer. I searching since couple of days and found nothing...

Best,
Rob

1:
Code:
[barny@icarus tmp]$ rpm -i Definiens-GRID_Life-1.5-1765-i586.rpm 
error: Failed dependencies:
	libodbc.so.1 is needed by DefiniensGRID_Life-1.5-1765.i586

2:
Code:
[barny@icarus tmp]$ sudo yum install libodbc.so.1
Loaded plugins: refresh-packagekit, rhnplugin
Setting up Install Process
No package libodbc.so.1 available.
Error: Nothing to do

3:
Code:
[barny@icarus tmp]$ rpm -q libodbc.so.1
package libodbc.so.1 is not installed

4:

Code:
[barny@icarus tmp]$ rpm -q unixODBC
unixODBC-2.2.14-11.el6.x86_64

 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Two Oracle's installed

In my directory /u01/app/oracle/product I have two Oracle products installed. $ ls 8.1.7 817_http The application installed on the server is using PL/SQL procs to display webpages(not sure how) Now I have to create a similar server for development. Our sysadmin has built up a host... (1 Reply)
Discussion started by: rahulrathod
1 Replies

2. Shell Programming and Scripting

Check if rpm is installed

Hi all im hoping someone can help, i want to check if a rpm package is installed, if it is then display one text if not then another text, below is what i have got so far, im am very much a noob at this, as you can probably can see so if possible make it simple, and a big thankyou if you can help... (3 Replies)
Discussion started by: dave123
3 Replies

3. Linux

RPM used to installed to get a partcular command

Hi, I have a query in linux and please find the details of it I have a command in linux and i want to know which rpm has provided that command. ie: if we take ifconfig command ,i want to know what is the rpm package used to get that command. Regards Arun.Kakarla (3 Replies)
Discussion started by: Arun.Kakarla
3 Replies

4. AIX

OS Patches installed but they seem as not installed

Hello everyone: I've installed an OS patch into AIX 6.1 by running the following command: instfix -d /tmp/6100-02-03 -k "IZ41855" however it seem not installed instfix -i -k "IZ41855" There was no data for IZ41855 in the fix database. what am I doing wrong? (8 Replies)
Discussion started by: edgarvm
8 Replies

5. AIX

aioo seems to be not installed

Hi everyone: I've a server running AIX 6.1 which had initialy technology level =0, after an upgrade oslevel -s reports that it was increased to 6100-04-02, however after doing this the aioo command seems to be not present, what did I do wrong? edit: lslpp shows bos.rte.aio was installed: ... (1 Reply)
Discussion started by: edgarvm
1 Replies

6. Emergency UNIX and Linux Support

Problem when trying to remove a package using rpm command - error: package is not installed

Hello, i have installed a package by using the command sudo rpm -i filepackage.rpm package filepackage is already installed when i try to remove it, i get an error saying "is not installed": sudo rpm -e filepackage.rpm error: package filepackage is not installed How can... (4 Replies)
Discussion started by: g_p
4 Replies

7. Linux

rpm packaging issue for unixodbc driver manager

Hi All, I am trying to make rpm package for unixODBC driver manager 2.3.0 using below spec file. During rpmbuild i am getting the error. Can you pls advice how we can overcome this issue %define name unixODBC %define ver 2.3.0 %define prefix /usr %define sysconfdir /etc %define libdir... (2 Replies)
Discussion started by: kamauv234
2 Replies

8. Red Hat

How to create an rpm from installed files?

i would like to package up an rpm from pre-installed files, say i have a program called "widget" installed under "/opt/widget" /opt/widget/bin/* /opt/widget/lib/* /opt/widget/etc/* /opt/widget/log/* and i want to create an rpm from those already installed files, what would the spec file... (2 Replies)
Discussion started by: melixir
2 Replies

9. UNIX for Beginners Questions & Answers

Bash find version of an installed application but if none is found set variable to App Not Installed

Hello Forum, I'm issuing a one line bash command to look for the version of an installed application and saving the result to a variable like so: APP=application --version But if the application is not installed I want to return to my variable that the Application is not installed. So I'm... (2 Replies)
Discussion started by: greavette
2 Replies
yumdb(8)																  yumdb(8)

NAME
yumdb - query and alter the Yum database SYNOPSIS
yumdb [command] [packages ...] DESCRIPTION
This command is used to query and alter the yum database, which is a simple key value store used in conjunction with the rpm database. Any installed package can have arbitrary data in the yum database, however the main use case is to store extra data about packages as they are installed. yumdb commands are: yumdb get <key> [pkg-wildcard]... This command will get the value for the given key, limiting to any specified packages. yumdb set <key> <value> [pkg-wildcard]... This command will set the value for the given key, to the given value, limiting to any specified packages. yumdb del <key> [pkg-wildcard]... This command will delete the given key, limiting to any specified packages. yumdb rename <old-key> <new-key> [pkg-wildcard]... This command will rename the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, noth- ing happens. yumdb rename-force <old-key> <new-key> [pkg-wildcard]... This command will rename the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, new- key is deleted. yumdb copy <old-key> <new-key> [pkg-wildcard]... This command will copy the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, nothing happens. yumdb copy-force <old-key> <new-key> [pkg-wildcard]... This command will copy the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, new-key is deleted. yumdb search <key> <wildcard>... This command will search all packages for the given key, against any of the given wildcard values. yumdb exist <key> [pkg-wildcard]... This command will print any packages which have the given key, limiting to any specified packages. yumdb unset <key> [pkg-wildcard]... This command will print any packages which do not have the given key, limiting to any specified packages. yumdb info [pkg-wildcard]... This command will display all the data stored in the yumdb, limiting to any specified packages. yumdb sync [pkg-wildcard]... This command will add any missing data to the yumdb from the repositories, limiting to any specified packages. This is useful to run if you have had any aborted transactions (and thus. missing yumdb data). Note that "yumdb sync" cannot know all the information that would have been put into the yumdb at the time. yumdb sync-force [pkg-wildcard]... This command will replace any data in the yumdb from the repositories, limiting to any specified packages. EXAMPLES
List all the packages which don't have a from_repo key/value: yumdb unset from_repo List all the packages which were installed as dependencies: yumdb search reason dep WELL KNOWN KEYS
Note that there is no limit to the number of keys that can be created or what they may contain (for installed packages only). However this is a list of well known keys, and what they store. checksum_data checksum_type These keys store the createrepo checksum, and it's type, of the available package yum installed. Note that these are used by "yum version" to calculate the rpmdb version. command_line This key stores the entire command line, of the yum command (if it was called). from_repo from_repo_revision from_repo_timestamp These keys take values from the available package yum installed, and store the repo id, it's revision and timestamp. reason This key stores either "user" or "dep", currently. To mark if the user requested the package to be installed, or if it was brought in automatically as a dependency. Note that this is kept over updates. releasever This key stores the value of releasever, when the package was installed. installonly If this attribute has the value "keep" then this package will not be removed automatically by the installonly process (and does not count towards the installonly_limit). SEE ALSO
yum (8) rpm (8) AUTHORS
James Antill <james.antill@redhat.com>. James Antill 8 April 2010 yumdb(8)
All times are GMT -4. The time now is 04:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy