July 2018
M T W T F S S
« Jun    
 1
2345678
9101112131415
16171819202122
23242526272829
3031  

Categories

WordPress Quotes

I've learned that you shouldn't go through life with a catcher's mitt on both hands; you need to be able to throw something back.
Maya Angelou

Recent Comments

July 2018
M T W T F S S
« Jun    
 1
2345678
9101112131415
16171819202122
23242526272829
3031  

Short Cuts

2012 SERVER (64)
2016 windows (9)
AIX (13)
Amazon (30)
Ansibile (18)
Apache (125)
Asterisk (2)
cassandra (2)
Centos (208)
Centos RHEL 7 (254)
chef (3)
cloud (2)
cluster (3)
Coherence (1)
DB2 (5)
DISK (25)
DNS (9)
Docker (24)
Eassy (11)
EXCHANGE (3)
Fedora (6)
ftp (5)
GIT (3)
GOD (2)
Grub (1)
Hacking (10)
Hadoop (6)
horoscope (23)
Hyper-V (10)
IIS (15)
IPTABLES (15)
JAVA (6)
JBOSS (32)
jenkins (1)
Kubernetes (2)
Ldap (5)
Linux (189)
Linux Commands (167)
Load balancer (5)
mariadb (14)
Mongodb (4)
MQ Server (21)
MYSQL (82)
Nagios (5)
NaturalOil (13)
Nginx (29)
Ngix (1)
openldap (1)
Openstack (6)
Oracle (34)
Perl (3)
Postfix (19)
Postgresql (1)
PowerShell (2)
Python (3)
qmail (36)
Redis (12)
RHCE (28)
SCALEIO (1)
Security on Centos (29)
SFTP (1)
Shell (64)
Solaris (58)
Sql Server 2012 (4)
squid (3)
SSH (10)
SSL (14)
Storage (1)
swap (3)
TIPS on Linux (28)
tomcat (59)
Uncategorized (29)
Veritas (2)
vfabric (1)
VMware (28)
Weblogic (38)
Websphere (71)
Windows (19)
Windows Software (2)
wordpress (1)
ZIMBRA (17)

WP Cumulus Flash tag cloud by Roy Tanck requires Flash Player 9 or better.

Who's Online

23 visitors online now
6 guests, 17 bots, 0 members

Hit Counter provided by dental implants orange county

AMQ7017 queue manager log not available or corrupted

Problem
Your queue manager fails to start with the following error :

AMQ7017 Log not available

Cause
The qm.ini files had been altered and the LogPath entries were removed.

After making the change to qm.ini LogPath, the queue manager failed to start because S0000001.log was not available. The log file was present and the permissions appeared to be correct, but it seemed to be corrupted.

Solution
Edit the qm.ini file and specify the correct LogPath.

If the queue manager fails to start and you suspect a corrupted log file, then do the following:

Here are the steps to follow to recover from the damaged log file(s) in /var/mqm/log/qmgrname/active. The queue manager is referred to as TESTQMGR.

cd /var/mqm/qmgrs
mv TESTQMGR TEST.OLD

NOTE:This will rename the TESTQMGR directory to be TEST.OLD, effectively backing up all your queues and objects.
dltmqm TESTQMGR

Note: This command may not completely run and it may produce error messages. This is OK. At the end of this command there are 3 places to check to make sure everything is cleaned up from TESTQMGR and if it did not then you will need to manually remove
what is left.
There should not be a directory under /var/mqm/qmgrs by the name of TESTQMGR as it should have been renamed to TEST.OLD.
In /var/mqm/log there should not be a directory name TESTQMGR. If there is a directory left there, from /var/mqm/log issue the command rm -rf TESTQMGR to remove the old logs.
In /var/mqm there is a file called mqs.ini. Within file mqs.ini there will be QueueManager: stanzas for each queue manager defined on this box. There should no longer be a stanza referring to TESTQMGR. If there is a stanza for TESTQMGR, remove it; the whole
stanza (should be 4 lines.)
crtmqm TESTQMGR
cd /var/mqm/qmgrs
cp TESTQMGR/amqalchk.fil TEST.OLD

(This is to copy the new check point file over to the backup directory where you are saving our old queue manager files.)
rm -rf TESTQMGR

(This will remove the new qmgr files you just created so you can replace them with the files from the old queue manager that you had saved.)
mv TEST.OLD TESTQMGR

(This is where you just restored the old definitions. At this point you should have a new queue manager created with new logs but you should have our old queues and channels still there.)
strmqm TESTQMGR

(Start up the queue manager. Everything should be back to normal except there will be no attempt to recover any in-flight UOWs because you have nothing in the logs.)

another path ?

Failure recovery and the queue manager

After a full system failure and recovery, the queue manager might fail to start, displaying this message:

AMQ7017 Log not available.

This typically indicates that the log file is missing or damaged, or that the log path to the queue manager is inaccessible.
To remedy the problem, create a dummy queue manager and copy its header log file and transaction log files over to the actual queue manager. This will allow you to restart the queue manager.

 

 

When start being given AMQ7017 MQ queue manager: Log not available, the following example

$ strmqm

AMQ7017: Log not available.

For this problem solving process is more complex, as an example to the queue manager QM2 about the recovery process:

1, the backup queue manager QM2 objects

# su – mqm

$ cd /var/mqm/qmgrs

$ mv QM2 QM2_OLD

2, delete the queue manager QM2

$ dltmqm QM2

MQSeries queue manager deleted.

3, delete directory directory /var/mqm/log under the QM2

$ cd /var/mqm/log

$ rm -rf QM2

4? the file does not ensure /var/mqm/mqs.ini QM2 project, if it is deleted.

$ vi /var/mqm/mqs.ini

AllQueueManagers:

DefaultPrefix=/var/mqm

ClientExitPath:

ExitsDefaultPath=/var/mqm/exits

LogDefaults:

LogPrimaryFiles=3

LogSecondaryFiles=2

LogFilePages=1024

LogType=CIRCULAR

LogBufferPages=17

LogDefaultPath=/var/mqm/log

QueueManager:

Name=QM3

Prefix=/var/mqm

Directory=QM3

5? re-create the queue manager QM2

$ crtmqm QM2

MQSeries queue manager created.

Creating or replacing default objects for QM2.

Default objects statistics : 29 created. 0 replaced. 0 failed.

Completing setup.

Setup completed.

?? /var/mqm/mqs.ini ?????

$ vi /var/mqm/mqs.ini

AllQueueManagers:

DefaultPrefix=/var/mqm

ClientExitPath:

ExitsDefaultPath=/var/mqm/exits

LogDefaults:

LogPrimaryFiles=3

LogSecondaryFiles=2

LogFilePages=1024

LogType=CIRCULAR

LogBufferPages=17

LogDefaultPath=/var/mqm/log

QueueManager:

Name=QM3

Prefix=/var/mqm

Directory=QM3

QueueManager:

Name=QM2

Prefix=/var/mqm

Directory=QM2

6? Copy the new check point before the backup file to a directory in QM2_OLD

$ cd /var/mqm/qmgrs

$ cp QM2/amqalchk.fil QM2_OLD

7 Remove the new queue manager object directory /var/mqm/qmgrs/QM2

$ rm -rf QM2

8?the object manager object data backup to restore the directory to the directory QM2 QM2_OLD

$ mv QM2_OLD QM2

9 start the queue manager QM2, problems get.

$ strmqm QM2

MQSeries queue manager ‘QM2’ started.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

  

  

  

Blue Captcha Image
Refresh

*

Protected by WP Anti Spam