10-13-2008
Applying TL8 to a TL6 machine caused all sorts of problems in my last project. The reason being that the procedure controlling the installation was quite "alpha", so to say. This was in late July/beginning of August. (I remember lots of unfulfilled dependencies and all sorts of nasty effects).
What definitely helped was to upgrade the machine to TL7 and only then upgrade it to TL8. This worked flawlessly.
If memory serves correctly a colleague told me there were no problems when upgrading from a 5.3-0 installation but i could remember wrongly.
Bottom line: TL8 is flagged "handle with extreme care" in my book, maybe they have sorted out the issues with the installation process in the meantime maybe they haven't. I wouldn't bet on IBM having taken care. Create a known-to-be-working backup before starting the upgrade, if you have a mirrored rootvg you might want to do an alternate disk migration.
Don't let petty users press you to hasten the installation process - take your time. If they have a problem with the downtime they should have bought more hardware (to allow takeover) in first place instead of pestering you.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Our firewall logs show strange entries and we had a strange
issue of a moved directory withour anybody knowing of it.
Are their log files on AIX where i can see who used the system
( logged on, move anything, ... )
Thanks (5 Replies)
Discussion started by: progressdll
5 Replies
2. Solaris
Hi Friends,
I am trying to execute rsh commands from Solaris 10 system to AIX system.
When I give;
Solaris10# rsh <hostname> ls -l , it gives me an error
rshd : 0826-826 The host name for your address is not known
At the same time,
Solaris10# rsh <hostname> ---- gives me remote shell of... (25 Replies)
Discussion started by: jumadhiya
25 Replies
3. AIX
hi my frieds, I´m from mexico and I was looking the SO Aix.
please help me. (4 Replies)
Discussion started by: puma056
4 Replies
4. AIX
AIX Printers need to be moved to another system
Guy's
We have two servers old AIX 5.2 and new AIX 6.1
the old server has more than 300 printers installed with different configurations
I'd like to move all the printers from the old server to the new server with fast steps
it's... (1 Reply)
Discussion started by: ITHelper
1 Replies
5. AIX
Hello Friends,
I had enabled the audit and configured for sysadmin user alone in audit config file. but the audit starts logging for root user alone.
Attached the conf file. I want the aduit to record only for sysadmin activities..
need your expertise and help in solving the issue. (1 Reply)
Discussion started by: kmvinay
1 Replies
6. Shell Programming and Scripting
Hi,
I have a problem with a SED script that works fine on AIX but does not work properly on a Solaris system.
The ksh script executes the SED and puts the output in HTML in tables.
But the layout of the output in HTML is not shown correctly(no tables, no color). Can anyone tell if there is... (7 Replies)
Discussion started by: Faith111
7 Replies
7. AIX
Using nimadm:
nimadm -j nimadmvg -c sap024 -s spot_6100 -l lpp_6100 -d "hdisk1" -Y
Initializing the NIM master.
Initializing NIM client sap024.
0505-205 nimadm: The level of bos.alt_disk_install.rte installed in SPOT
spot_6100 (6.1.3.4) does not match the NIM master's level (7.1.1.2).... (2 Replies)
Discussion started by: sciacca75
2 Replies
8. AIX
I have a following requirement in production
system 1 : LINUX
User: abcd
system 2: AIX (it is hosting a production DB)
Requirement
user abcd from system 1 should have read access on archive log files created by DB on system 2. The log files are created with permissions 540 by user ora ,... (2 Replies)
Discussion started by: amitnm1106
2 Replies
9. AIX
Hello.
An update of TL from TL7 to TL8 is ending with errors :
Requisite Failures
------------------
SELECTED FILESETS: The following is a list of filesets that you asked to
install. They cannot be installed until all of their requisite filesets
are also installed. See subsequent... (4 Replies)
Discussion started by: stephnane
4 Replies
10. UNIX for Beginners Questions & Answers
I am new to AIX but not new to unix.
I have an interview for an AIX systems admin position and I know they want someone who has knowledge of High Availability, Failover and LPARs
From my research so far, It appear powerha is used to setup high availability and failover on Power systems but is... (2 Replies)
Discussion started by: mathisecure
2 Replies
LEARN ABOUT MINIX
dh_installsystemd
DH_INSTALLSYSTEMD(1) Debhelper DH_INSTALLSYSTEMD(1)
NAME
dh_installsystemd - install systemd unit files
SYNOPSIS
dh_installsystemd [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [--no-enable] [--name=name] [unitfile...]
DESCRIPTION
dh_installsystemd is a debhelper program that is responsible for enabling, disabling, starting, stopping and restarting systemd unit files.
In the simple case, it finds all unit files installed by a package (e.g. bacula-fd.service) and enables them. It is not necessary that the
machine actually runs systemd during package installation time, enabling happens on all machines in order to be able to switch from
sysvinit to systemd and back.
For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_installsystemd quota.service and
dh_installsystemd --name=quotarpc quotarpc.service.
FILES
debian/package.service, debian/package@.service
If this exists, it is installed into lib/systemd/system/package.service (or lib/systemd/system/package@.service) in the package build
directory.
debian/package.tmpfile
If this exists, it is installed into usr/lib/tmpfiles.d/package.conf in the package build directory. (The tmpfiles.d mechanism is
currently only used by systemd.)
debian/package.target, debian/package@.target
If this exists, it is installed into lib/systemd/system/package.target (or lib/systemd/system/package@.target) in the package build
directory.
debian/package.socket, debian/package@.socket
If this exists, it is installed into lib/systemd/system/package.socket (or lib/systemd/system/package@.socket) in the package build
directory.
debian/package.mount
If this exists, it is installed into lib/systemd/system/package.mount in the package build directory.
debian/package.path, debian/package@.path
If this exists, it is installed into lib/systemd/system/package.path (or lib/systemd/system/package@.path) in the package build
directory.
debian/package.timer, debian/package@.timer
If this exists, it is installed into lib/systemd/system/package.timer (or lib/systemd/system/package@.timer) in the package build
directory.
OPTIONS
--no-enable
Disable the service(s) on purge, but do not enable them on install.
Note that this option does not affect whether the services are started. Please remember to also use --no-start if the service should
not be started.
--name=name
Install the service file as name.service instead of the default filename, which is the package.service. When this parameter is used,
dh_installsystemd looks for and installs files named debian/package.name.service instead of the usual debian/package.service.
Moreover, maintainer scripts are only generated for units that match the given name.
--restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
Note that this option does not affect whether the services are enabled. Please remember to also use --no-enable if the services should
not be enabled.
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
SEE ALSO
debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_INSTALLSYSTEMD(1)