[SOLVED] How to remove pkg from zone in newly created boot environment?
fyi, I already have SR opened with Oracle.
We are looking to upgrade from S11.3 to S11.4 with the latest SRU.
Create new BE; success
Mount new BE; success
the updating of the global went fine until it touched local zone.
I already attempted to uninstall the package from the newly created
boot environment but that didn't work. I did it with the command below;
Any suggestions, I'll give you a piece of candy
Last edited by samthewildone; 05-24-2019 at 01:53 PM..
Reason: Solved
Hi Friends,
I have to create a new log file everyday and append it with content based on some keywords found in another log file.
Here is what I have tried so far...
grep Error /parentfolder/someLogFile.log >> /parentfolder
/Archive/"testlogfile_error_`date '+%d%m%y'`.txt"
grep error... (6 Replies)
I 'm having a weired situation my system has 8 zones, running fine on solaris x86_u4. I installed the live upgrade bundle patch and did a live upgrade. The new BE was created but it missed one of the zone and now if i mount the new BE i do not see that zone in the environment so my question is how... (3 Replies)
Hi,
I need to create new directory by increasing the number by 1 of extracted lastly created directory.
e.g.
Log\out_log_1\
Log\out_log_2\
Log\out_log_3\
become
Log\out_log_1\
Log\out_log_2\
Log\out_log_3\
Log\out_log_4\
Can anyone help how to do it in c-shell... (3 Replies)
Hi,
We have a sftp server which creates files daily and keeps 6 months of files on the server. We are creating a daily job to get the files and load into database. My problem is "how to get ONLY those files which got created after my last get". Let me provide some more details to it.
Below... (15 Replies)
Hi all,
In linux how to create a directory with specified size, so that it can be used only up to the mentioned size.
Actually my question is, whether we can do directory quota in linux.
mounting the directory in a partiton will do that, but do we have any other option... (1 Reply)
hello,
i am an oracle DBA and trying to scan a newly created LUN of 200 GB on fiber channel by SAN admin.we have solaris 10 and SANtoolkit is installed.i tried following to get the new LUN at my machine. go /opt/Netapp/Santoolkit/bin and then ./sanlun lun show but i see only the existing... (12 Replies)
hello everyone,
I am new to perl script and trying to develop a script as follows.
I am trying to Create an array for storing all file names. I am trying to copy $libs into "scratch". however i am unable to do so. Please suggest..
#!/usr/bin/perl
use File::Copy;
#use... (5 Replies)
Hi ,
I have created one new lun in my SAN storage and make it visible to my HP servers , but the fdisk -l output is somehow confusing. Do not know what to do next ----------
fdisk -l /dev/sdo1
Disk /dev/sdo1 (Sun disk label): 64 heads, 32 sectors, 10238 cylinders
Units =... (7 Replies)
Hi Solaris Experts,
The pkg utility on one of my non-global zones has stopped working, it's trying to connect to port 1008 at pkg.oracle.com
I was using pkg successfully from this zone, but now it's showing this error: lzone1 $ pkg search xterm
pkg: Some repositories failed to respond... (4 Replies)
AIX 7.1
New to WPAR, hopefully just missing something simple here.
Creating the WPAR like this.....
(The box where the WPAR is hosted does have an iscsi protocol device)
mkwpar -h wpar08 -l -n wpar08 -N interface=en0 address=xxx.xx.xx.xxx netmask=255.255.255.0 -D devname=/dev/iscsi0 -D... (0 Replies)
Discussion started by: TomR
0 Replies
LEARN ABOUT CENTOS
yumdb
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)