Morning Unix Guru's,
I have written a script which output the contents of a DB. No the DB is not clever to check this or flag and there is no command for the tool to flag this, which human intervention.
But i need to check to see if there are duplicate enteries in the file output and flag them.
So the example below there is duplicate enteries for actlni02 and allocd01.
I need your help please.
In a production system, i've seen many running process as follow:
sh -c ./pathname/shellname
what exactly the flag option -c is used for?
ive tried to look at the man page, but it doesnt say much.
ill appreciate yor help. Thanks (4 Replies)
Hello All,
I did very stupid mistake and lost all my crontab enteries on root prompt.
Please help me to solve this issue.
i did entry on root prompt like this.
crontab /home/back.cron
and enters
but when i enter crontab -l so its only showing 1 entry defined in back.cron
and all... (2 Replies)
Hi,
I would like to know if there's any option to use with the du command so that I can list only the files/directories on the current filesystem... I usually use
du -gs *But I'd like to see only the directories in the filesystem I am on, and not the mount point directory of other fss...
... (6 Replies)
#!/bin/bash
while :
do
./abc.sh PB
sleep 60
./abc.sh RA
sleep 60
./abc.sh GS
sleep 68400
done
Instead of making the script sleep for sometime, it doesn't work all the time as time may shift over a period.
How to make a script wake up every 30 seconds and check the current time, if... (2 Replies)
i am trying to patch a solaris 10 server using live upgrade.
issue is, when i create a new BE and activate it during reboot the file system that are mounted but doesnt have an entry in vfstab are automatically added in vfstab of new BE.
looks like live upgrade uses df -h output as reference... (0 Replies)
Hi,
In a file, I have to mark duplicate records as 'D' and the latest record alone as 'C'.
In the below file, I have to identify if duplicate records are there or not based on Man_ID, Man_DT, Ship_ID and I have to mark the record with latest Ship_DT as "C" and other as "D" (I have to create... (7 Replies)
Hi all,
We dont have access to aix source code and i have a doubt.
The flag SC_NO_RESERVE, is it got to do anything with the failover?
If the flag is set the paths are going to failed state. If flag is not set everything comes up fine after failover.
Thanks in advance for helping
... (2 Replies)
Hey, all!
Why is the "human readable" flag changing the behavior of du? And while I'm at it, can you make du only look at files, not directories. I often find myself wanting to find the largest file(s) in a dir or vol. Using 'find' itself, it seems you have to at least be able to guess the size of... (2 Replies)
Hello -
I have a file in the followig format
LINE TEXT 1
Line TEXT 2
TIMESTARTED=Fri Aug 16 15:20:23 EDT 2013
START-OF-DATA
123
123444
23232323
END-OF-DATA
Line TEXT 9
I need to get all the lines between the Start of Data and End of Data and pipe it to a file so output should be
... (5 Replies)
.... means multi line
ddd,bug fgdrg
dfdfsdfdfsd
fsdfdfdfd
fdfdsfdsfsd
.......
flag2
......
aaa,bug sfsfsfsfs
dfdfsdfdfsd
fsdfdfdfd
fdfdsfdsfsd
......
flag1
......
ddd,bug fgdrg
dfdfsdfdfsd (9 Replies)
Discussion started by: yanglei_fage
9 Replies
LEARN ABOUT OSX
db_upgrade
db_upgrade(1) BSD General Commands Manual db_upgrade(1)NAME
db_upgrade
SYNOPSIS
db_upgrade [-NsV] [-h home] [-P password] file ...
DESCRIPTION
The db_upgrade utility upgrades the Berkeley DB version of one or more files and the databases they contain to the current release version.
The options are as follows:
-h
Specify a home directory for the database environment; by default, the current working directory is used.
-N
Do not acquire shared region mutexes while running. Other problems, such as potentially fatal errors in Berkeley DB, will be ignored as
well. This option is intended only for debugging errors, and should not be used under any other circumstances.
-P
Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a
window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite
the memory containing the command-line arguments.
-s
This flag is only meaningful when upgrading databases from releases before the Berkeley DB 3.1 release.
As part of the upgrade from the Berkeley DB 3.0 release to the 3.1 release, the on-disk format of duplicate data items changed. To cor-
rectly upgrade the format requires that applications specify whether duplicate data items in the database are sorted or not. Specifying
the -s flag means that the duplicates are sorted; otherwise, they are assumed to be unsorted. Incorrectly specifying the value of this
flag may lead to database corruption.
Because the db_upgrade utility upgrades a physical file (including all the databases it contains), it is not possible to use db_upgrade to
upgrade files where some of the databases it includes have sorted duplicate data items, and some of the databases it includes have
unsorted duplicate data items. If the file does not have more than a single database, if the databases do not support duplicate data
items, or if all the databases that support duplicate data items support the same style of duplicates (either sorted or unsorted),
db_upgrade will work correctly as long as the -s flag is correctly specified. Otherwise, the file cannot be upgraded using db_upgrade, and
must be upgraded manually using the db_dump and db_load utilities.
-V
Write the library version number to the standard output, and exit.
It is important to realize that Berkeley DB database upgrades are done in place, and so are potentially destructive. This means that if the
system crashes during the upgrade procedure, or if the upgrade procedure runs out of disk space, the databases may be left in an inconsistent
and unrecoverable state. See Upgrading databases for more information.
The db_upgrade utility may be used with a Berkeley DB environment (as described for the -h option, the environment variable DB_HOME, or
because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a
Berkeley DB environment, db_upgrade should always be given the chance to detach from the environment and exit gracefully. To cause db_upgrade
to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT).
The db_upgrade utility exits 0 on success, and >0 if an error occurs.
ENVIRONMENT
DB_HOME If the -h option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as
described in DB_ENV->open.
SEE ALSO db_archive(1), db_checkpoint(1), db_deadlock(1), db_dump(1), db_load(1), db_printlog(1), db_recover(1), db_stat(1), db_verify(1)Darwin December 3, 2003 Darwin