10 More Discussions You Might Find Interesting
1. Emergency UNIX and Linux Support
Hello Team,
Am trying to upgrade the AIX 6.1 TL 7 to TL 8. My rootvg is mirrored so i have unmirrored and taken out the secondary disk and trying to install the update via smitty alt_clone.
The filesets has been installed and finally when making the updated disk as bootable bosboot... (6 Replies)
Discussion started by: gowthamakanthan
6 Replies
2. AIX
Dear Guys ..
I'm going to Upgrade one of the servers AIX 6.1
I want to stop rootvg mirror to save the mirror then upgrade to AIX 6.1 this is to help me in rollback if something goes wrong but ..
can anyone help me how to make sure that system is relay mirrored and how to know that second... (10 Replies)
Discussion started by: top.level
10 Replies
3. 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
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. AIX
Hello Folks,
i am facing some weired issues.
case is like this :-
initially i was on AIX 5.3
i have installed filesets related to my application and those were in APPLY state.(COMMIT is set as NO)
Then i have taken lslpp -l| grep -i <apps name>
in that i confirmed whether the filesets are... (1 Reply)
Discussion started by: harsh_mulay
1 Replies
6. Programming
Hi ,
We are migrating our database from DB2 z/os to DB2 UDB on UNIX.
and cobol on mainframes to AIX cobol on UNIX.
We have some cobol Db2 programs that are accessing different Databases
how do we code such type of programs in AIX cobol.
Do we need to Establish connection for accessing... (0 Replies)
Discussion started by: nal.satish
0 Replies
7. 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
8. 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
9. 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
10. 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
pki-upgrade(8) PKI Upgrade Tool pki-upgrade(8)
NAME
pki-upgrade - Tool for upgrading system-wide configuration for Certificate System.
SYNOPSIS
pki-upgrade [OPTIONS]
DESCRIPTION
There are two parts to upgrading Certificate System: upgrading the system configuration files used by both the client and the server pro-
cesses and upgrading the server configuration files.
When upgrading Certificate System, the existing system configuration files (e.g. /etc/pki/pki.conf) may need to be upgraded because the
content may have changed from one version to another. The configuration upgrade is executed automatically during RPM upgrade. However, in
case there is a problem, the process can also be run manually using pki-upgrade.
The system upgrade process is done incrementally using upgrade scriptlets. The upgrade process and scriptlet execution is monitored in
upgrade trackers. A counter shows the latest index number for the most recently executed scriptlet; when all scriptlets have run, the com-
ponent tracker shows the updated version number.
The scriptlets are stored in the upgrade directory:
/usr/share/pki/upgrade/<version>/<index>-<name>
The version is the system version to be upgraded. The index is the script execution order. The name is the scriptlet name.
During upgrade, the scriptlets will back up all changes to the filesystem into the following folder:
/var/log/pki/upgrade/<version>/<index>
The version and index values indicate the scriptlet being executed. A copy of the files and folders that are being modified or removed will
be stored in oldfiles. The names of the newly-added files and folders will be stored in newfiles.
The system upgrade process is tracked using this file:
/etc/pki/pki.version
The file stores the current configuration version and the last successful scriptlet index.
OPTIONS
General options
--silent
Upgrade in silent mode.
--status
Show upgrade status only without performing the upgrade.
--revert
Revert the last version.
-X Show advanced options.
-v, --verbose
Run in verbose mode.
-h, --help
Show this help message.
Advanced options
The advanced options circumvent the normal component tracking process by changing the scriptlet order or changing the tracker information.
WARNING: These options may render the system unusable.
--scriptlet-version <version>
Run scriptlets for a specific version only.
--scriptlet-index <index>
Run a specific scriptlet only.
--remove-tracker
Remove the tracker.
--reset-tracker
Reset the tracker to match the package version.
--set-tracker <version>
Set the tracker to a specific version.
OPERATIONS
Interactive mode
By default, pki-upgrade will run interactively. It will ask for a confirmation before executing each scriptlet.
% pki-upgrade
If there is an error, it will stop and show the error.
Silent mode
The upgrade process can also be done silently without user interaction:
% pki-upgrade --silent
If there is an error, it will stop and show the error.
Checking upgrade status
It is possible to check the status of a running upgrade process.
% pki-upgrade --status
Troubleshooting
If there is an error, rerun the upgrade in verbose mode:
% pki-upgrade --verbose
Check the scriptlet to see which operations are being executed. Once the error is identified and corrected, the upgrade can be resumed by
re-running pki-upgrade.
It is possible to rerun a failed script by itself, specifying the instance and subsystem, version, and scriptlet index:
% pki-upgrade --scriptlet-version 10.0.1 --scriptlet-index 1
Reverting an upgrade
If necessary, the upgrade can be reverted:
% pki-upgrade --revert
Files and folders that were created by the scriptlet will be removed. Files and folders that were modified or removed by the scriptlet will
be restored.
FILES
/usr/sbin/pki-upgrade
AUTHORS
Ade Lee <alee@redhat.com>, Ella Deon Lackey <dlackey@redhat.com>, and Endi Dewata <edewata@redhat.com>. pki-upgrade was written by the
Dogtag project.
COPYRIGHT
Copyright (c) 2013 Red Hat, Inc. This is licensed under the GNU General Public License, version 2 (GPLv2). A copy of this license is avail-
able at http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt.
version 1.0 Jul 22, 2013 pki-upgrade(8)