db2_all Error - DB2 UDB V8.2 for AIX

Jay Reavill

db2_all Error - DB2 UDB V8.2 for AIX
(in response to Dan Tuck)
Hey everyone,

I'm executing the following command in a 2 server 8 partition
environment...

db2_all "db2 connect to dwp01 user dwpinst1 using *******; db2 list
tablespaces show detail; db2 connect reset"

And I'm getting the following error...

A remote host refused an attempted connect operation.

I'm new to supporting this app, but I'm fairly sure this has worked in the
past. One thing that has recently changed on the boxes is the shutting
down of port 23 and the ability to telnet in. Now SSH must be used. Could
this be the cause?

Any ideas why I would get this?

Thanks,
Jay

------------------------------------------------------------------
Jay Reavill
DBA
Fidelity National Information Services, Inc.
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
[login to unmask email]
------------------------------------------------------------------



------------------------------------------------------------------------------
This message contains information from Certegy, Inc which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e:mail [login to unmask email]
=====

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Jay Reavill

db2_all Error - DB2 UDB V8.2 for AIX (actually 8.1)
Hey Dave,

Thanks for the info. It would be exactly what I need, but I mistakenly
thought we were at 8.2, but as it turns out we are still 8.1 for this app.
Do you happen to know how it would be done with 8.1?

Thanks again. Sorry for the confusion.

------------------------------------------------------------------
Jay Reavill
DBA
Fidelity National Information Services, Inc.
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
[login to unmask email]
------------------------------------------------------------------




"David
Stritzinger" To: [login to unmask email]
<David.Stritzinger cc:
@KRAFT.COM> Subject: Re: [DB2-L] db2_all Error - DB2 UDB V8.2 for AIX
Sent by: "DB2 Data
Base Discussion
List"
<[login to unmask email]
RG>


09/20/2006 06:30
PM
Please respond to
"DB2 Database
Discussion list at
IDUG"





Jay,


db2_all is a script in sqllib/bin. It calls a script in the same
directory called rah. Rah set the rshcmd to rsh. My assumption here is that
with telnet shut down you may not be able to do a rsh. To verify this, try
something like this as the db2 instance owner id:



rsh wi1001 echo hello
or
db2_all echo hello


Where wi1001 is one of the nodes in your db2nodes.cfg file. If the
hello comes back OK, then it is something else.


Here is a link about setting up Open SSh with DB2


http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0506finnie/



Hope this helps,


Dave S


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf
Of Jay Reavill
Sent: Wednesday, September 20, 2006 5:55 PM
To: [login to unmask email]
Subject: [DB2-L] db2_all Error - DB2 UDB V8.2 for AIX


Hey everyone,


I'm executing the following command in a 2 server 8 partition
environment...


db2_all "db2 connect to dwp01 user dwpinst1 using *******; db2 list
tablespaces show detail; db2 connect reset"


And I'm getting the following error...


A remote host refused an attempted connect operation.


I'm new to supporting this app, but I'm fairly sure this has worked in the
past. One thing that has recently changed on the boxes is the shutting
down of port 23 and the ability to telnet in. Now SSH must be used. Could
this be the cause?


Any ideas why I would get this?


Thanks,
Jay


------------------------------------------------------------------
Jay Reavill
DBA
Fidelity National Information Services, Inc.
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
[login to unmask email]
------------------------------------------------------------------






------------------------------------------------------------------------------

This message contains information from Certegy, Inc which may be
confidential and privileged. If you are not an intended recipient, please
refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have
received this transmission in error, please notify by e:mail
[login to unmask email]


=====



---------------------------------------------------------------------------------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org
. The IDUG List Admins can be reached at [login to unmask email]
Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm





------------------------------------------------------------------------------
This message contains information from Certegy, Inc which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e:mail [login to unmask email]
=====

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Ian Bjorhovde

Re: db2_all Error - DB2 UDB V8.2 for AIX (actually 8.1)
(in response to Jay Reavill)
Jay,

You need to be on V8.1 Fixpack 9 (in case you don't know, 8.1 FP9 which is
the same thing as 8.2 FP 2) to use SSH instead of RSH.

If your system is not at this code level, then using RSH is a *requirement*
for DPF. This generally makes security types uncomfortable -- and it's been
my experience that they usually want an exception for this "hole."

The error you mentioned typically occurs when someone has disabled the
'login' service in /etc/inetd.conf. This would not be related to closing
Port 23 (which is used for telnet), but the admins may have also closed down
the


Good luck,


On 9/21/06, Jay Reavill <[login to unmask email]> wrote:
>
> Hey Dave,
>
> Thanks for the info. It would be exactly what I need, but I mistakenly
> thought we were at 8.2, but as it turns out we are still 8.1 for this app.
> Do you happen to know how it would be done with 8.1?
>
> Thanks again. Sorry for the confusion.
>
> ------------------------------------------------------------------
> Jay Reavill
> DBA
> Fidelity National Information Services, Inc.
> 11601 Roosevelt Blvd.
> St. Petersburg, FL. 33716
> Office (727) 227-2144
> [login to unmask email]
> ------------------------------------------------------------------
>
>
>
>
> "David
> Stritzinger" To:
> [login to unmask email]
> <David.Stritzinger cc:
> @KRAFT.COM> Subject: Re: [DB2-L]
> db2_all Error - DB2 UDB V8.2 for AIX
> Sent by: "DB2 Data
> Base Discussion
> List"
> <[login to unmask email]
> RG>
>
>
> 09/20/2006 06:30
> PM
> Please respond to
> "DB2 Database
> Discussion list at
> IDUG"
>
>
>
>
>
> Jay,
>
>
> db2_all is a script in sqllib/bin. It calls a script in the same
> directory called rah. Rah set the rshcmd to rsh. My assumption here is
> that
> with telnet shut down you may not be able to do a rsh. To verify this, try
> something like this as the db2 instance owner id:
>
>
>
> rsh wi1001 echo hello
> or
> db2_all echo hello
>
>
> Where wi1001 is one of the nodes in your db2nodes.cfg file. If the
> hello comes back OK, then it is something else.
>
>
> Here is a link about setting up Open SSh with DB2
>
>
>
> http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0506finnie/
>
>
>
> Hope this helps,
>
>
> Dave S
>
>
> -----Original Message-----
> From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf
> Of Jay Reavill
> Sent: Wednesday, September 20, 2006 5:55 PM
> To: [login to unmask email]
> Subject: [DB2-L] db2_all Error - DB2 UDB V8.2 for AIX
>
>
> Hey everyone,
>
>
> I'm executing the following command in a 2 server 8 partition
> environment...
>
>
> db2_all "db2 connect to dwp01 user dwpinst1 using *******; db2 list
> tablespaces show detail; db2 connect reset"
>
>
> And I'm getting the following error...
>
>
> A remote host refused an attempted connect operation.
>
>
> I'm new to supporting this app, but I'm fairly sure this has worked in the
> past. One thing that has recently changed on the boxes is the shutting
> down of port 23 and the ability to telnet in. Now SSH must be
> used. Could
> this be the cause?
>
>
> Any ideas why I would get this?
>
>
> Thanks,
> Jay
>
>
> ------------------------------------------------------------------
> Jay Reavill
> DBA
> Fidelity National Information Services, Inc.
> 11601 Roosevelt Blvd.
> St. Petersburg, FL. 33716
> Office (727) 227-2144
> [login to unmask email]
> ------------------------------------------------------------------
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
>
> This message contains information from Certegy, Inc which may be
> confidential and privileged. If you are not an intended recipient, please
> refrain from any disclosure, copying, distribution or use of this
> information and note that such actions are prohibited. If you have
> received this transmission in error, please notify by e:mail
> [login to unmask email]
>
>
>
> ======
>
>
>
>
> ---------------------------------------------------------------------------------
>
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
> home
> page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
> select
> "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org
> . The IDUG List Admins can be reached at [login to unmask email]
> Find out the latest on IDUG conferences at
> http://conferences.idug.org/index.cfm
>
>
>
> ---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
> home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
> select "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. The IDUG List Admins can be reached at
> [login to unmask email] Find out the latest on IDUG conferences
> at
> http://conferences.idug.org/index.cfm
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> This message contains information from Certegy, Inc which may be
> confidential and privileged. If you are not an intended recipient, please
> refrain from any disclosure, copying, distribution or use of this
> information and note that such actions are prohibited. If you have received
> this transmission in error, please notify by e:mail [login to unmask email]
> .
>
> ======
>
>
> ---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
> home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
> select "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. The IDUG List Admins can be reached at
> [login to unmask email] Find out the latest on IDUG conferences
> at http://conferences.idug.org/index.cfm
>

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Jay Reavill

Re: db2_all Error - DB2 UDB V8.2 for AIX (actually 8.1)
(in response to Ian Bjorhovde)
Thanks for clarifying the versioning Ian. Looks like we're going to have
to either upgrade or document an exception for the risk.

Thanks again.

------------------------------------------------------------------
Jay Reavill
DBA
Fidelity National Information Services, Inc.
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
[login to unmask email]
------------------------------------------------------------------




"Ian Bjorhovde"
<[login to unmask email] To: [login to unmask email]
AIL.COM> cc:
Sent by: "DB2 Subject: Re: [DB2-L] db2_all Error - DB2 UDB V8.2 for AIX (actually 8.1)
Data Base
Discussion List"
<[login to unmask email]
ORG>


09/25/2006 04:06
AM
Please respond to
"DB2 Database
Discussion list
at IDUG"





Jay,

You need to be on V8.1 Fixpack 9 (in case you don't know, 8.1 FP9 which is
the same thing as 8.2 FP 2) to use SSH instead of RSH.

If your system is not at this code level, then using RSH is a *requirement*
for DPF. This generally makes security types uncomfortable -- and it's
been my experience that they usually want an exception for this "hole."

The error you mentioned typically occurs when someone has disabled the
'login' service in /etc/inetd.conf. This would not be related to closing
Port 23 (which is used for telnet), but the admins may have also closed
down the


Good luck,


On 9/21/06, Jay Reavill <[login to unmask email]> wrote:
Hey Dave,

Thanks for the info. It would be exactly what I need, but I mistakenly
thought we were at 8.2, but as it turns out we are still 8.1 for this
app.
Do you happen to know how it would be done with 8.1 ?

Thanks again. Sorry for the confusion.

------------------------------------------------------------------
Jay Reavill
DBA
Fidelity National Information Services, Inc.
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
[login to unmask email]
------------------------------------------------------------------




"David
Stritzinger" To:
[login to unmask email]
<David.Stritzinger cc:
@KRAFT.COM> Subject: Re: [DB2-L]
db2_all Error - DB2 UDB V8.2 for AIX
Sent by: "DB2 Data
Base Discussion
List"
<[login to unmask email]
RG>


09/20/2006 06:30
PM
Please respond to
"DB2 Database
Discussion list at
IDUG"





Jay,


db2_all is a script in sqllib/bin. It calls a script in the same
directory called rah. Rah set the rshcmd to rsh. My assumption here is
that
with telnet shut down you may not be able to do a rsh. To verify this,
try
something like this as the db2 instance owner id:



rsh wi1001 echo hello
or
db2_all echo hello


Where wi1001 is one of the nodes in your db2nodes.cfg file. If
the
hello comes back OK, then it is something else.


Here is a link about setting up Open SSh with DB2


http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0506finnie/





Hope this helps,


Dave S


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf
Of Jay Reavill
Sent: Wednesday, September 20, 2006 5:55 PM
To: [login to unmask email]
Subject: [DB2-L] db2_all Error - DB2 UDB V8.2 for AIX


Hey everyone,


I'm executing the following command in a 2 server 8 partition
environment...


db2_all "db2 connect to dwp01 user dwpinst1 using *******; db2 list
tablespaces show detail; db2 connect reset"


And I'm getting the following error...


A remote host refused an attempted connect operation.


I'm new to supporting this app, but I'm fairly sure this has worked in
the
past. One thing that has recently changed on the boxes is the shutting
down of port 23 and the ability to telnet in. Now SSH must be used.
Could
this be the cause?


Any ideas why I would get this?


Thanks,
Jay


------------------------------------------------------------------
Jay Reavill
DBA
Fidelity National Information Services, Inc.
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
[login to unmask email]
------------------------------------------------------------------






------------------------------------------------------------------------------


This message contains information from Certegy, Inc which may be
confidential and privileged. If you are not an intended recipient,
please
refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have
received this transmission in error, please notify by e:mail
[login to unmask email]


======




---------------------------------------------------------------------------------


Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select
"Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org
. The IDUG List Admins can be reached at [login to unmask email]
Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm


---------------------------------------------------------------------------------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at
http://conferences.idug.org/index.cfm





------------------------------------------------------------------------------

This message contains information from Certegy, Inc which may be
confidential and privileged. If you are not an intended recipient,
please refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have
received this transmission in error, please notify by e:mail
[login to unmask email]
======


---------------------------------------------------------------------------------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm



------------------------------------------------------------------------------
This message contains information from Certegy, Inc which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e:mail [login to unmask email]
=====

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

steve howe

DB2 V8 for AIX
(in response to Jay Reavill)

I recently took over support of an application using DB2 V8.2 on AIX. I'm
a little puzzled on the Database Logs. The DB CFG Config is below and the
list of LOGs currently in the LOG Directory below that. It appears to me
that there is some mirroring going on based on the update date/timestamp
(see below in Red) however the Database in not configured for that. Can
someone offer any advice on why that is occurring?



The DB CFG Log Config Settings are:



Log retain for recovery status = RECOVERY

Number of primary log files (LOGPRIMARY) = 10

Number of secondary log files (LOGSECOND) = 10

Changed path to log files (NEWLOGPATH) =

Overflow log path (OVERFLOWLOGPATH) =

Mirror log path (MIRRORLOGPATH) =

First active log file = S0001080.LOG

Block log on disk full (BLK_LOG_DSK_FUL) = NO

Percent of max active log space by transaction(MAX_LOG) = 0

Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0

Log retain for recovery enabled (LOGRETAIN) = RECOVERY

User exit for logging enabled (USEREXIT) = OFF

First log archive method (LOGARCHMETH1) = LOGRETAIN

Options for logarchmeth1 (LOGARCHOPT1) =

Second log archive method (LOGARCHMETH2) = OFF

Options for logarchmeth2 (LOGARCHOPT2) =



-rw------- 1 ttserver db2iadm1 20488192 Oct 11 05:07 S0001070.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 11 05:29 S0001071.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 11 05:44 S0001072.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 12 13:57 S0001073.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 12 14:47 S0001074.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 13 05:48 S0001075.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 13 06:01 S0001076.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 13 06:29 S0001077.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 13 09:17 S0001078.LOG

-rw------- 1 ttserver db2iadm1 13090816 Oct 17 17:23 S0001079.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 17 17:33 S0001080.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 11 05:44 S0001081.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 11 05:53 S0001082.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 12 14:03 S0001083.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 12 14:56 S0001084.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 13 06:01 S0001085.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 13 06:08 S0001086.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 13 06:39 S0001087.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 13 09:18 S0001088.LOG

-rw------- 1 ttserver db2iadm1 20488192 Oct 17 17:24 S0001089.LOG



Thanks in Advance.



Steve Howe

Database Services

[login to unmask email]

The information contained in this communication is highly confidential and
is intended solely for the use of the individual(s) to whom this
communication is directed. If you are not the intended recipient, you are
hereby notified that any viewing, copying, disclosure or distribution of
this information is prohibited. Please notify the sender, by electronic mail
or telephone, of any unintended receipt and delete the original message
without making any copies.

Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
nonprofit corporations and independent licensees of the Blue Cross and Blue
Shield Association.


----------------------------------------------------------------------------
----- Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm


The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies.

Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Dan Tuck

Re: DB2 V8 for AIX
(in response to steve howe)
The significant indicator is the log file name, for example "S0001088.LOG"
Also, a new log is created under many circumstances. Like when a log fills
or a backup finishes or the database is inactivated.


On 10/17/06, Howe, Steve <[login to unmask email]> wrote:
>
> I recently took over support of an application using DB2 V8.2 on AIX.
> I'm a little puzzled on the Database Logs. The DB CFG Config is below and
> the list of LOGs currently in the LOG Directory below that. It appears to
> me that there is some mirroring going on based on the update date/timestamp
> (see below in Red) however the Database in not configured for that. Can
> someone offer any advice on why that is occurring?
>
>
>
> The DB CFG Log Config Settings are:
>
>
>
> Log retain for recovery status = RECOVERY
>
> Number of primary log files (LOGPRIMARY) = 10
>
> Number of secondary log files (LOGSECOND) = 10
>
> Changed path to log files (NEWLOGPATH) =
>
> Overflow log path (OVERFLOWLOGPATH) =
>
> Mirror log path (MIRRORLOGPATH) =
>
> First active log file = S0001080.LOG
>
> Block log on disk full (BLK_LOG_DSK_FUL) = NO
>
> Percent of max active log space by transaction(MAX_LOG) = 0
>
> Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0
>
> Log retain for recovery enabled (LOGRETAIN) = RECOVERY
>
> User exit for logging enabled (USEREXIT) = OFF
>
> First log archive method (LOGARCHMETH1) = LOGRETAIN
>
> Options for logarchmeth1 (LOGARCHOPT1) =
>
> Second log archive method (LOGARCHMETH2) = OFF
>
> Options for logarchmeth2 (LOGARCHOPT2) =
>
>
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 11 05:07 S0001070.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 11 05:29 S0001071.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 11 05:44 S0001072.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 12 13:57 S0001073.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 12 14:47 S0001074.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 13 05:48 S0001075.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 13 06:01 S0001076.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 13 06:29 S0001077.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 13 09:17 S0001078.LOG
>
> *-rw------- 1 ttserver db2iadm1 13090816 Oct 17 17:23 S0001079.LOG*
>
> *-rw------- 1 ttserver db2iadm1 20488192 Oct 17 17:33 S0001080.LOG*
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 11 05:44 S0001081.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 11 05:53 S0001082.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 12 14:03 S0001083.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 12 14:56 S0001084.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 13 06:01 S0001085.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 13 06:08 S0001086.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 13 06:39 S0001087.LOG
>
> -rw------- 1 ttserver db2iadm1 20488192 Oct 13 09:18 S0001088.LOG
>
> *-rw------- 1 ttserver db2iadm1 20488192 Oct 17 17:24 S0001089.LOG*
>
>
>
> Thanks in Advance.
>
>
>
> Steve Howe
>
> Database Services
>
> [login to unmask email]
> The information contained in this communication is highly confidential
> and is intended solely for the use of the individual(s) to whom this
> communication is directed. If you are not the intended recipient, you are
> hereby notified that any viewing, copying, disclosure or distribution of
> this information is prohibited. Please notify the sender, by electronic mail
> or telephone, of any unintended receipt and delete the original message
> without making any copies.
>
> Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
> nonprofit corporations and independent licensees of the Blue Cross and Blue
> Shield Association.
>
> ---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
> page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
> select "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. The IDUG List Admins can be reached at
> [login to unmask email] Find out the latest on IDUG conferences
> at http://conferences.idug.org/index.cfm The information contained in
> this communication is highly confidential and is intended solely for the use
> of the individual(s) to whom this communication is directed. If you are not
> the intended recipient, you are hereby notified that any viewing, copying,
> disclosure or distribution of this information is prohibited. Please notify
> the sender, by electronic mail or telephone, of any unintended receipt and
> delete the original message without making any copies.
>
> Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
> nonprofit corporations and independent licensees of the Blue Cross and Blue
> Shield Association.
> ---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
> page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
> select "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. The IDUG List Admins can be reached at
> [login to unmask email] Find out the latest on IDUG conferences
> at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Mark Baskerville

Re: db2_all Error - DB2 UDB V8.2 for AIX
(in response to Jay Reavill)
I would first verify that you have a valid '.rhosts' file in your home
directory on each node in your db2 environment.
If you are using ssh, you'll have to set the 'DB2RSHCMD' registry variable
(on AIX the ssh executable is in '/usr/bin/ssh', and make sure that 'root'
has configured the 'ssh_config' file to allow db2 remote login commands.


On Wed, 20 Sep 2006 17:55:02 -0400, Jay Reavill <[login to unmask email]> wrote:

>Hey everyone,
>
>I'm executing the following command in a 2 server 8 partition
>environment...
>
> db2_all "db2 connect to dwp01 user dwpinst1 using *******; db2 list
>tablespaces show detail; db2 connect reset"
>
>And I'm getting the following error...
>
> A remote host refused an attempted connect operation.
>
>I'm new to supporting this app, but I'm fairly sure this has worked in the
>past. One thing that has recently changed on the boxes is the shutting
>down of port 23 and the ability to telnet in. Now SSH must be used. Could
>this be the cause?
>
>Any ideas why I would get this?
>
>Thanks,
>Jay
>
>------------------------------------------------------------------
> Jay Reavill
> DBA
> Fidelity National Information Services, Inc.
> 11601 Roosevelt Blvd.
> St. Petersburg, FL. 33716
> Office (727) 227-2144
> [login to unmask email]
>------------------------------------------------------------------
>
>
>
>------------------------------------------------------------------------------
>This message contains information from Certegy, Inc which may be
confidential and privileged. If you are not an intended recipient, please
refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have received
this transmission in error, please notify by e:mail [login to unmask email]
> =====
>
>---------------------------------------------------------------------------------
>Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
The IDUG List Admins can be reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm
>
>---------------------------------------------------------------------------------
>Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
The IDUG List Admins can be reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm