06-01-2010
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
Installing a new version of PROGRESS DB software 9.1c requires us to upgrade AIX to Level Update 4320-02_AIX_ML
( http://techweb.progress.com/kbase/19779 )
How would a do this savely.
This is what i have already.
1) take a system backup.
2) find the level we are on right now.
#... (1 Reply)
Discussion started by: progressdll
1 Replies
2. AIX
Hello. Im attempting to install Oracle 11g, but my current AIX is a bit too old. Oracle 11g require TV 5300-05-06, and my current AIX TV is:
% oslevel -s
5300-05-00
So what would be the best way to update TV? Thanks. (6 Replies)
Discussion started by: bsddaemon
6 Replies
3. Solaris
what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 Replies
4. 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
5. Solaris
Hi All,
Recently I'm being request by customer to upgrade firmware for one of the disk but not from storage and is from server it self.
The patch no is 116370-15, when I found it, I only see instructions on how to download for storage disks but not for server disks.
All guru here please... (0 Replies)
Discussion started by: mailbox80
0 Replies
6. Solaris
I have two physical servers, with zones that mount local storage.
We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point).
It failed to mount on every boot because the directory existed in the zone.
I... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies
7. Red Hat
We have a RHEL 5.8 server at the production level and we have a Java application on this server. I know of the SSL certificate generation at the OS (RHEL) level but it is implemented on the Java application by our development team using the Java keytool. My doubt is that is the SSL generation can... (3 Replies)
Discussion started by: RHCE
3 Replies
8. Shell Programming and Scripting
copying daily changes from serverA to serverB using rsync(solaris8, v2.6.2) at root folder level.
serverA: cd /
rsync -a -vv --delete --checksum --sparse --stats --dry-run --exclude /tmp/ --exclude /proc/ --exclude /devices/ . root@<IP of ServerB>:/
This is generating mainly three debug... (0 Replies)
Discussion started by: kchinnam
0 Replies
9. AIX
Hello,
Can you please give some info on how to upgrade the SSH/SSL on AIX LPARs?
we've the below version on our servers.
/>lslpp -l | grep -i ssh
openssh.base.client 5.8.0.6102 COMMITTED Open Secure Shell Commands
openssh.base.server 5.8.0.6102 COMMITTED Open Secure... (1 Reply)
Discussion started by: System Admin 77
1 Replies
LEARN ABOUT LINUX
lurename
lurename(1M) System Administration Commands lurename(1M)
NAME
lurename - change the name of a boot environment
SYNOPSIS
/usr/sbin/lurename -e BE_name -n new_name [-l error_log] [-o outfile] [-X]
DESCRIPTION
The lurename command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See
live_upgrade(5) for a description of the Live Upgrade feature.
The lurename command renames the boot environment (BE) BE_name to new_name.
The string new_name must not exceed 30 characters in length and must consist only of alphanumeric characters and other ASCII characters
that are not special to the Unix shell. See the "Quoting" section of sh(1). The BE name can contain only single-byte, 8-bit characters. It
cannot contain whitespace characters. Also, new_name must be unique on the system.
A BE must have the status "complete" before you rename it. Use lustatus(1M) to determine a BE's status. Also, you cannot rename a BE that
has file systems mounted with lumount(1M) or mount(1M).
Renaming a BE is often useful when you upgrade the BE from one Solaris release to another. For example, following an operating system
upgrade, you might rename the BE solaris7 to solaris8.
The lurename command requires root privileges.
OPTIONS
The lurename command has the options listed below.
-e BE_name Name of the BE whose name you want to change.
-l error_log Error and status messages are sent to error_log, in addition to where they are sent in your current environment.
-n new_name New name of the BE. new_name must be unique on a given system.
-o outfile All command output is sent to outfile, in addition to where it is sent in your current environment.
-X Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where
<num> is the version number of the DTD file.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
FILES
/etc/lutab
list of BEs on the system
/usr/share/lib/xml/dtd/lu_cli.dtd.<num>
Live Upgrade DTD (see -X option)
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWluu |
+-----------------------------+-----------------------------+
SEE ALSO
lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), lucurr(1M), ludelete(1M), ludesc(1M), lufslist(1M), lumake(1M),
lumount(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5)
SunOS 5.10 24 Jan 2002 lurename(1M)