05-26-2010
Quote:
Originally Posted by
kkeng808
Yes, the Nim resources are in rootvg
Of course you can go on with this, but i would take the opportunity of the migration to correct this. Create a new VG, create LVs/filesystems mirroring the old layout, copy all the data to the new FSes, umount the old NIM FSes and use "chlv"/"chfs" to change the mount points to the original ones. Then mount the new FSes to see if everything fits. Only then remove the old FSes with the NIM resources.
Quote:
Originally Posted by
kkeng808
Will share my experience once its done
Very good! I'm looking forward to that.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. AIX
I'am migrating from AIX 5.1 to 5.3 during migration installation a receive message enough space for dir /usr.
My question is : how i can resolve this problem ? i can't reboot my server i hope that there is a command to obtain a spece without go out from installation procedure pannel...
I'am... (0 Replies)
Discussion started by: tt155
0 Replies
2. AIX
Hi, I'a a new member here.
My company just bought p570 with 8 LPAR (previously we have p650 with 4 LPAR).
Did anyone have procedure how to setup NIM server (NIM LPAR) and how to install other new LPAR to use the NIM server (as client).
Appreciate your help and thank you very much.
Rgds,
David (0 Replies)
Discussion started by: dshg
0 Replies
3. AIX
I try to migrate a NIM server from one server to another.
I try to do a mksysb on NIM server
restore the NIM server's mksysb to a client through NIM installation
shutdown NIM server
start newly installed client as NIM server
Does anyone do this before? who can give me some suggestion? (1 Reply)
Discussion started by: yanzhang
1 Replies
4. AIX
Hi all,
I was wondering if anyone out there knew if it was possible to migrate users from AIX to Linux.
What we want to do is install OpenLDAP on a Linux machine and port all the users over to LDAP. I've googled around and could only find a few things, such as mrgpwd - but that only comes... (0 Replies)
Discussion started by: djcronos
0 Replies
5. AIX
Hi,
my requirement is to migrate easytrieve running on Z/OS to AIX platform.
can anyone let me know what changes should be made if we do such a migration. (0 Replies)
Discussion started by: rohit510
0 Replies
6. AIX
Can any one help.....
How will do migration through NIM server? (4 Replies)
Discussion started by: AIXlearner
4 Replies
7. AIX
Friends ,
In our production server , we are using oracle10g in IBM AIX 5.3 unix server. From last 7 days , I got the below error :
------------------------------
LABEL: TS_NIM_ERROR_STUCK_
IDENTIFIER: 864D2CE3
Date/Time: Mon Sep 7 19:34:38 NOVST 2009
Sequence Number:... (1 Reply)
Discussion started by: shipon_97
1 Replies
8. 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
9. AIX
Hi all,
I have this weird notion that upgrading the TL does not cause the machine to wipe, but upgrading a major version (from aix 6 to 7) means it's actually a fresh install and will wipe the date and i have to install the software again (TSM server, for instance). Trying to google it, i came... (3 Replies)
Discussion started by: tde3000
3 Replies
10. AIX
Hello,
I worked on setting up NFSv3 and NFSv4 (novice) shares separately. I was trying to find a way to migrate existing NFSv3 fileshares to NFSv4 as is.
I found a redbook online called "Securing NFS in AIX". It has good info.
I am able to create a new NFSv4 share, do not know how to... (4 Replies)
Discussion started by: System Admin 77
4 Replies
LEARN ABOUT SUNOS
asupgrade
asupgrade(1m) Application Server Utility asupgrade(1m)
NAME
asupgrade - migrates the configuration of a previously installed Sun Java System Application Server
SYNOPSIS
asupgrade [-c | --console] [-V --version] [-h | --help]-s | -source applicationserver7.x_installation -t --target application-
server8.x_installation [-d | --domain domain_name -n | --nsspwdfile NSS_password_filepath -j | --jkspwdfile JKS_password_filepath -p |
--capwdfile CA_password_filepath]
Use the asupgrade utility to migrate the server configration and its persisted state, J2EE services, and deployed J2EE applications. The
configuration of an installed Sun Java System Application Server 7 is migrated to the Sun Java System Application Server 8 Application
Server installation. If the domain contains information about a deployed application and the installed application components do not agree
with the configuration information, the configuration is migrated as is without any attempt to reconfigure the incorrect configurations.
asupgrade migrates the configuration and deployed applications of a previous version of the Application Server; however, the runtime bina-
ries of the server are not updated. Database migrations or conversions are beyond the scope of the asupgrade command.
Only those instances that do not use the Sun Java System Web Server specific features will be upgraded seamlessly. Configration files
related to HTTP path, CGI bin, SHTML, and NSAPI plugins will not be upgraded.
The upgrade process can also be initiated automatically at installation time using the Upgrade checkbox in the Application Server install-
er. After completion of the upgrade, use the Application Server 7 Uninstaller to remove the previous version of the Application Server.
Application archives (.ear) and component archives (.jar, .war, .rar) that are deployed in the Application Server 7 environment do not
require any modification to run on Application Server 8. However applications and components deployed in the source server are repackaged
into new J2EE archives in the target server's autodeploy directory and are deployed upon server startup. Applications that do not deploy
successfully, must use Migrationtool (asmigrate) on the application and then manually redeploy the application.
You must specify the source and target directories for the upgrade. If the upgrade includes certificates, you must also provide the pass-
words for the source PKCS12 file and the target JKS keyfile for each domain that contains certificates to be migrated. Since Application
Server 7 uses a different certificate store format (NSS) than Application Server 8 (JSSE), the migration keys and certificates are con-
verted to the new format. Upon successful upgrade, an upgrate report is generated listing successfully migrated items along with a list of
the items that could not be migrated.
OPTIONS
-c --console launches the upgrade command line utility.
-V--version displays the version of the UpgradeTool.
-h--help displays the arguments for launching the UpgradeTool.
-s--source identifies the installation directory for Sun Java System Application Server 7.
-t--target identifies the installation directory for Sun Java System Application Server 8.
-d--domain identifies the destination domain name for the migrated certificates.
-n--nsspwdfile identifies the path to the NSS password file.
-j--jkspwdfile identifies the path to the JKS password file.
-p--capwdfile identifies the path to the CA certificate password file.
EXAMPLES
Example 1: Using asupgrade
example% upgrade -s /home/sunas7 -t /home/sunas8
SEE ALSO
asmigrate(1M)
Sun Java System Application Server March 2004 asupgrade(1m)