11-19-2009
Quote:
Originally Posted by
harsh_mulay
Now i upgraded the system (5.3) to aix 6.1 and after upgradation i checked the lslpp o/p the it was showing the same filesets (which were in APPLIED state in 5.3) in COMMITED state.
That happens during each and every upgrade and works as designed
Quote:
Originally Posted by
harsh_mulay
Because of this i am not able to add new filesets even though using "OVERWRITE option which is set as YES."
Any pointers why this is happening ?
ideally the filesets should be in APPLIED state.
no matter if the previous packages are applied or committed, this will not prevent you from installing (apply OR commit) newer versions of existing software? I would rather think that your packages are checking for AIX 5 and don't find it and that prevents you from installing new packages?
Kind regards
zxmaus
10 More Discussions You Might Find Interesting
1. AIX
Hi guys
I have joined a new department and one of my tasks is to investigate the feasibility of upgrading our current AIX v 4.3 to V5.3.
I do not know anything about AIX and any actual work will be done by an outside consultant until such time as I have built up my own knowledge.
The system we... (3 Replies)
Discussion started by: JDM
3 Replies
2. UNIX for Dummies Questions & Answers
Hello everyone, I have to do a ML upgrade on AIX 5.2 from 01 to 09
this is the first time iam going to do it.
are there any command i have to keep in mind??
thanks! (1 Reply)
Discussion started by: karthikosu
1 Replies
3. UNIX for Dummies Questions & Answers
Does anyone know any gotcha's on upgrading AIX from 5.1 to 5.3? Any interim steps on needs to do or ??? (3 Replies)
Discussion started by: capeme
3 Replies
4. AIX
I have an IBM P520 that I need to upgrade from 5.2 to 5.3. My background in Unix is from 15 years ago so I don't remember much. IBM documentation is hard to find. Any help would be appreciated. (1 Reply)
Discussion started by: bashtonmcse
1 Replies
5. AIX
I have an AIX LPAR that is one half of a Oracle RAC cluster running over a GPFS filesystem.
The OS version in the LPAR was 5300-05-01
I ran an upgrade to 5300-07-05 (Apply only, Commit=NO and preserve old files).
The preview passed with no failures detected.
The actual upgrade failed... (5 Replies)
Discussion started by: morgan_g
5 Replies
6. AIX
Is there a way to install a newer TL and SP level to an alternate disk, then boot to that disk?
I've used adi to upgrade an os level but not just a tl or sp level.
When I tried the same way, I received an error saying I cant migrate from aix 5.3 to aix 5.3.
The other options I've found... (1 Reply)
Discussion started by: gravy26
1 Replies
7. AIX
Steps to upgrade AIX TL ( technology Level ) / Maintenance Level in AIX ( including Firmware HMC VIOS )
This article or post covers upgrades for
- Hardware Management Console ( HMC )
- Firmware ( also known as microcode )
- VIO ( Virtual I/O Server = PowerVM )
- AIX Version, Technology... (2 Replies)
Discussion started by: filosophizer
2 Replies
8. AIX
i upgrade aix ml 5.3.2.1 to 5.3.2.2 but when running commnd #oslevel -r
shows out put, again 5.3.2.1-- where should i chek???
2-can any one tell me when mknfs command run which files get updated?? (2 Replies)
Discussion started by: nayyer
2 Replies
9. AIX
Hi all,
I'm getting errors while booting AIX 7.1 after upgrade
I have used FLRT tool for the process with the following input values shown in the attached photo. titled FLRT
After reboot for the upgrade process system hangs and no response as shown in screenshot named AIX7.1-NormalBoot
I... (13 Replies)
Discussion started by: h@foorsa.biz
13 Replies
10. AIX
Hello Everyone.
I am trying to upgrade one of my servers which is AIX 7.1.0.3 to AIX 7.1.3.3. I have downloaded the fix packs and stored in /tmp/TL3SP3 directory.
I ran inutoc .; bffcreate -ad; inutoc .
then smitty installp
I get an error like this
Verifying requisites...
... (11 Replies)
Discussion started by: gorkhali
11 Replies
LEARN ABOUT DEBIAN
shell-quote
SHELL-QUOTE(1p) User Contributed Perl Documentation SHELL-QUOTE(1p)
NAME
shell-quote - quote arguments for safe use, unmodified in a shell command
SYNOPSIS
shell-quote [switch]... arg...
DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands
or files with embedded white space or shell globbing characters safely. Here are a few examples.
EXAMPLES
ssh preserving args
When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and
passes them to "$SHELL -c". This doesn't work as intended:
ssh host touch 'hi there' # fails
It creates 2 files, hi and there. Instead, do this:
cmd=`shell-quote touch 'hi there'`
ssh host "$cmd"
This gives you just 1 file, hi there.
process find output
It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to
split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote:
eval set -- `find -type f -print0 | xargs -0 shell-quote --`
debug shell scripts
shell-quote is better than echo for debugging shell scripts.
debug() {
[ -z "$debug" ] || shell-quote "debug:" "$@"
}
With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can.
save a command for later
shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command
you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are
things the user can't pass through), you can do something like this:
user_switches=
while [ $# != 0 ]
do
case x$1 in
x--pass-through)
[ $# -gt 1 ] || die "need an argument for $1"
user_switches="$user_switches "`shell-quote -- "$2"`
shift;;
# process other switches
esac
shift
done
# later
eval "shell-quote some-command $user_switches my args"
OPTIONS
--debug
Turn debugging on.
--help
Show the usage message and die.
--version
Show the version number and exit.
AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions.
AUTHOR
Roderick Schertler <roderick@argon.org>
perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)