07-15-2011
mq upgrade from version 6 to 7 in aix server
Hi
What are the steps to be followed when upgrading MQ version from 6 to 7 in aix server?
cbsdbprd01 [/] # oslevel -s
5300-10-01-0921
cbsdbprd01 [/] # lslpp -l | grep -i mq
mqm.base.runtime 6.0.2.1 COMMITTED WebSphere MQ Runtime for
mqm.base.samples 6.0.2.1 COMMITTED WebSphere MQ Samples
mqm.base.sdk 6.0.2.1 COMMITTED WebSphere MQ Base Kit for
mqm.client.rte 6.0.2.1 COMMITTED WebSphere MQ Client for AIX
mqm.java.rte 6.0.2.1 COMMITTED WebSphere MQ Java Client, JMS
mqm.keyman.rte 6.0.2.1 COMMITTED WebSphere MQ Support for GSKit
mqm.msg.en_US 6.0.2.1 COMMITTED WebSphere MQ Messages - U.S.
mqm.server.rte 6.0.2.1 COMMITTED WebSphere MQ Server
mqm.txclient.rte 6.0.2.1 COMMITTED WebSphere MQ Extended
mqsi61 6.1.0.7 COMMITTED IBM WebSphere Message Broker
mqsi61.brokerc 6.1.0.7 COMMITTED Broker Component
mqsi61.brokerf 6.1.0.7 COMMITTED Broker Feature
mqsi61.cfgmgrc 6.1.0.7 COMMITTED Config. Manager Component
mqsi61.cfgmgrf 6.1.0.7 COMMITTED Config. Manager Feature
mqsi61.core 6.1.0.7 COMMITTED Core Component
mqsi61.data 6.1.0.7 COMMITTED Data Component
mqsi61.datadirect 6.1.0.7 COMMITTED DataDirect Component
mqsi61.disthub 6.1.0.7 COMMITTED DistHub Component
mqsi61.is 6.1.0.7 COMMITTED Integration Services Component
mqsi61.itlm 6.1.0.7 COMMITTED ITLM Component
mqsi61.la 6.1.0.7 COMMITTED LA Component
mqsi61.links 6.1.0.7 COMMITTED Links Component
mqsi61.mrm 6.1.0.7 COMMITTED MRM Component
mqsi61.profiles 6.1.0.7 COMMITTED Profiles Component
mqsi61.samples 6.1.0.7 COMMITTED Samples Component
mqsi61.tsamples 6.1.0.7 COMMITTED Transformation Services
mqsi61.tsc 6.1.0.7 COMMITTED Transformation Services
mqsi61.tsf 6.1.0.7 COMMITTED Transformation Services
mqsi61.unsc 6.1.0.7 COMMITTED UNS Component
mqsi61.unsf 6.1.0.7 COMMITTED UNS Feature
mqm.base.runtime 6.0.2.1 COMMITTED WebSphere MQ Runtime for
mqm.man.en_US.data 6.0.2.1 COMMITTED WebSphere MQ Man Pages - U.S.
My aix server is a single node and not a hacmp node.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I use HP UNIX 11 now , as I know , the latest version is 11iv2 , ( correct me if i am wrong ) , I hv read the feature of this version , it is 15% performance improved and more secure , if it is truth , I want to upgarde it by myself , but i am too familiar with the OS upgarde , could suggest the... (2 Replies)
Discussion started by: ust
2 Replies
2. AIX
Hi all,
Sorry if this is in the wrong place but needed to make sure lots of people saw this so that hopefully someone will be able to help.
Basically i've upgraded a test server from 4.3 to 5.3 TL04.
The server has hdisk0 and 1 as rootvg locally but then has another vg setup on our ESS... (5 Replies)
Discussion started by: djdavies
5 Replies
3. Solaris
Dear all,
How to upgrade bash's version? which way should be easy between remove the old version first and upgrade it or upgrade without remove?
Please, tell me how to upgrade step by step because I'm newbie
thank in advance (4 Replies)
Discussion started by: unitipon
4 Replies
4. SCO
Dear All,
I have sco Unix release 5 and i was asked to Upgrade the current version of statd.
kindly guide
Regards (1 Reply)
Discussion started by: sak900354
1 Replies
5. 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
6. Solaris
hi i need to upgrade my solaris mysql version.. can u guide me the upgrade steps..
my current version is
4.0.31-log
i need to upgrade to 5.0
..
thanks..
---------- Post updated at 12:04 PM ---------- Previous update was at 11:28 AM ----------
my solaris version is 10..
----------... (2 Replies)
Discussion started by: senkerth
2 Replies
7. AIX
Am new to AIX please help me. I have AIX7 server. When ever the system reboots my script need to run automatically. This will help me to start my application automatically after the server reboot.
Thanks,
Prince Wells (9 Replies)
Discussion started by: prince1987
9 Replies
8. Solaris
Hi All,
I got a task to upgrade release version of Solaris-9. I need to upgrade from Solaris 9 (Update 7) to Solaris 9 (Update 9) . My current config is - root@tsdpt01:/# uname -a
SunOS tsdpt01 5.9 Generic_118558-06 sun4u sparc SUNW,Sun-Fire-V240
root@tsdpt01:/# cat /etc/release
... (2 Replies)
Discussion started by: solaris_1977
2 Replies
9. Solaris
did a solaris 10 from an older update version to s10u9...
it boots up clean..
one of the zfs pool comes up with this..older zfs version cannot be by new software..
try to do zpool import <name_of_zone>
cannot import 'zone': pool is formatted using a newer ZFS version
I know... (4 Replies)
Discussion started by: ppchu99
4 Replies
10. UNIX for Beginners Questions & Answers
What happens if we perform a Native AIX TL Upgrade on a VIO server? I mean instead of updateios I logged into oem_setup_env and ran a update_all to a new TL. (2 Replies)
Discussion started by: wibhore
2 Replies
LEARN ABOUT FREEBSD
set_transaction
SET
TRANSACTION(7) SQL Commands SET TRANSACTION(7)
NAME
SET TRANSACTION - set the characteristics of the current transaction
SYNOPSIS
SET TRANSACTION transaction_mode [, ...]
SET SESSION CHARACTERISTICS AS TRANSACTION transaction_mode [, ...]
where transaction_mode is one of:
ISOLATION LEVEL { SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ UNCOMMITTED }
READ WRITE | READ ONLY
DESCRIPTION
The SET TRANSACTION command sets the characteristics of the current transaction. It has no effect on any subsequent transactions. SET SES-
SION CHARACTERISTICS sets the default transaction characteristics for subsequent transactions of a session. These defaults can be overrid-
den by SET TRANSACTION for an individual transaction.
The available transaction characteristics are the transaction isolation level and the transaction access mode (read/write or read-only).
The isolation level of a transaction determines what data the transaction can see when other transactions are running concurrently:
READ COMMITTED
A statement can only see rows committed before it began. This is the default.
SERIALIZABLE
All statements of the current transaction can only see rows committed before the first query or data-modification statement was exe-
cuted in this transaction.
The SQL standard defines two additional levels, READ UNCOMMITTED and REPEATABLE READ. In PostgreSQL READ UNCOMMITTED is treated as READ
COMMITTED, while REPEATABLE READ is treated as SERIALIZABLE.
The transaction isolation level cannot be changed after the first query or data-modification statement (SELECT, INSERT, DELETE, UPDATE,
FETCH, or COPY) of a transaction has been executed. See in the documentation for more information about transaction isolation and concur-
rency control.
The transaction access mode determines whether the transaction is read/write or read-only. Read/write is the default. When a transaction is
read-only, the following SQL commands are disallowed: INSERT, UPDATE, DELETE, and COPY FROM if the table they would write to is not a tem-
porary table; all CREATE, ALTER, and DROP commands; COMMENT, GRANT, REVOKE, TRUNCATE; and EXPLAIN ANALYZE and EXECUTE if the command they
would execute is among those listed. This is a high-level notion of read-only that does not prevent all writes to disk.
NOTES
If SET TRANSACTION is executed without a prior START TRANSACTION or BEGIN, it will appear to have no effect, since the transaction will
immediately end.
It is possible to dispense with SET TRANSACTION by instead specifying the desired transaction_modes in BEGIN or START TRANSACTION.
The session default transaction modes can also be set by setting the configuration parameters default_transaction_isolation and
default_transaction_read_only. (In fact SET SESSION CHARACTERISTICS is just a verbose equivalent for setting these variables with SET.)
This means the defaults can be set in the configuration file, via ALTER DATABASE, etc. Consult in the documentation for more information.
COMPATIBILITY
Both commands are defined in the SQL standard. SERIALIZABLE is the default transaction isolation level in the standard. In PostgreSQL the
default is ordinarily READ COMMITTED, but you can change it as mentioned above. Because of lack of predicate locking, the SERIALIZABLE
level is not truly serializable. See in the documentation for details.
In the SQL standard, there is one other transaction characteristic that can be set with these commands: the size of the diagnostics area.
This concept is specific to embedded SQL, and therefore is not implemented in the PostgreSQL server.
The SQL standard requires commas between successive transaction_modes, but for historical reasons PostgreSQL allows the commas to be omit-
ted.
SQL - Language Statements 2010-05-14 SET TRANSACTION(7)