DB2 LUW V8.2 Tablespace Unavailable

Jeffrey Schade

DB2 LUW V8.2 Tablespace Unavailable
I have a weekly database backup which fails sometimes because the
catalog tablespace is in an unavailable status. By the time I log in and
check the errors the status has cleared and I am having trouble
identifying the culprit. Is there some catalog table I can access which
will show me the utilities that have been run against the catalogs (i.e.
similar to SYSCOPY in the DB2 for Z/Os environment)? I plan on setting
up a job that will run if my backup fails which will do a LIST
APPLICATIONS and LIST TABLESPACES SHOW DETAIL to try an id the task. Is
there a better way of accomplishing this?



Jeff

_________________________________________
Jeffrey Schade

Systems Consultant, Technology Engineering


ISO
545 Washington Boulevard
Jersey City, NJ 07310
Voice: (201) 469-3738

FAX: (201) 748-1500
[login to unmask email] <mailto:[login to unmask email]>

This email is intended for the recipient only. If you are not the intended recipient please disregard, and do not use the information for any purpose.

_____________________________________________________________________

* IDUG North America * Tampa, Florida, * May 10-14 2010 * http://IDUG.ORG/NA *
_____________________________________________________________________

http://www.idug.org/db2-videos.html has hundreds of video presentations!
Did you miss out on attending an IDUG conference?
Many of the presentations were recorded and are available on our website!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's DB2-L

Gregory Palgrave

Re: DB2 LUW V8.2 Tablespace Unavailable
(in response to Jeffrey Schade)
Jeff,

You can try LIST HISTORY ALL SINCE <timestamp>, or check in the db2diag.log file for info/error messages.
Perhaps you can add LIST TABLESPACES SHOW DETAIL and LIST UTILITIES (or db2pd -uti) to the start/end of the weekly backup job as well?

Cheers

Greg

From: IDUG DB2-L [mailto:[login to unmask email] On Behalf Of Schade, Jeffrey
Sent: Monday, 7 December 2009 9:56 PM
To: [login to unmask email]
Subject: [DB2-L] DB2 LUW V8.2 Tablespace Unavailable

I have a weekly database backup which fails sometimes because the catalog tablespace is in an unavailable status. By the time I log in and check the errors the status has cleared and I am having trouble identifying the culprit. Is there some catalog table I can access which will show me the utilities that have been run against the catalogs (i.e. similar to SYSCOPY in the DB2 for Z/Os environment)? I plan on setting up a job that will run if my backup fails which will do a LIST APPLICATIONS and LIST TABLESPACES SHOW DETAIL to try an id the task. Is there a better way of accomplishing this?

Jeff
_________________________________________
Jeffrey Schade
Systems Consultant, Technology Engineering

ISO
545 Washington Boulevard
Jersey City, NJ 07310
Voice: (201) 469-3738
FAX: (201) 748-1500
[login to unmask email]<mailto:[login to unmask email]>

This email is intended for the recipient only. If you are not the intended recipient please disregard, and do not use the information for any purpose.

________________________________



The IDUG DB2-L Listserv is only part of your membership in IDUG. If you are not already an IDUG member, please register here. < http://www.idug.org/register >

_____________________________________________________________________

* IDUG North America * Tampa, Florida, * May 10-14 2010 * http://IDUG.ORG/NA *
_____________________________________________________________________

http://www.idug.org/events/index.html is your DB2 Events calendar! RUG meetings,
Webcasts, Conferences- what is going on next?
RUG leaders- get your events on the calendar today!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's DB2-L

Frederik Engelen

Re: DB2 LUW V8.2 Tablespace Unavailable
(in response to Gregory Palgrave)
You can also try db2pdcfg to get more information what's happening
when this specific error occurs.

Kind regards,

Frederik

On Tue, Dec 8, 2009 at 2:19 AM, Gregory Palgrave
<[login to unmask email]> wrote:
>
> Jeff,
>
>
>
> You can try LIST HISTORY ALL  SINCE <timestamp>, or check in the db2diag.log  file for info/error messages.
>
> Perhaps you can add LIST TABLESPACES SHOW DETAIL and LIST UTILITIES (or db2pd -uti)  to the start/end of the weekly backup job as well?
>
>
>
> Cheers
>
>
>
> Greg
>
>
>
> From: IDUG DB2-L [mailto:[login to unmask email] On Behalf Of Schade, Jeffrey
> Sent: Monday, 7 December 2009 9:56 PM
> To: [login to unmask email]
> Subject: [DB2-L] DB2 LUW V8.2 Tablespace Unavailable
>
>
>
> I have a weekly database backup which fails sometimes because the catalog tablespace is in an unavailable status. By the time I log in and check the errors the status has cleared and I am having trouble identifying the culprit. Is there some catalog table I can access which will show me the utilities that have been run against the catalogs (i.e. similar to SYSCOPY in the DB2 for Z/Os environment)? I plan on setting up a job that will run if my backup fails which will do a LIST APPLICATIONS and LIST TABLESPACES SHOW DETAIL to try an id the task. Is there a better way of accomplishing this?
>
>
>
> Jeff
>
> _________________________________________
> Jeffrey Schade
>
> Systems Consultant, Technology Engineering
>
> ISO
> 545 Washington Boulevard
> Jersey City, NJ 07310
> Voice: (201) 469-3738
>
>   FAX: (201) 748-1500
> [login to unmask email]
>
>
>
> This email is intended for the recipient only. If you are not the intended recipient please disregard, and do not use the information for any purpose.
>
>
>
> ________________________________
>
>
>
> The IDUG DB2-L Listserv is only part of your membership in IDUG. If you are not already an IDUG member, please register here.
>
> ________________________________
>
> The IDUG DB2-L Listserv is only part of your membership in IDUG. If you are not already an IDUG member, please register here.

_____________________________________________________________________

* IDUG North America * Tampa, Florida, * May 10-14 2010 * http://IDUG.ORG/NA *
_____________________________________________________________________

http://www.idug.org/events/index.html is your DB2 Events calendar! RUG meetings,
Webcasts, Conferences- what is going on next?
RUG leaders- get your events on the calendar today!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's DB2-L

Jeffrey Schade

Re: DB2 LUW V8.2 Tablespace Unavailable
(in response to Frederik Engelen)
Hi Greg,



The LIST HISTORY worked perfectly and I identified the other task that
was causing the issue. I also took your suggestion for adding the LIST
TABLESPACES and LIST UTILITIES commands to my backup script.



Thank You



Jeff

_________________________________________
Jeffrey Schade

Systems Consultant, Technology Engineering


ISO
545 Washington Boulevard
Jersey City, NJ 07310
Voice: (201) 469-3738

FAX: (201) 748-1500
[login to unmask email] <mailto:[login to unmask email]>

From: IDUG DB2-L [mailto:[login to unmask email] On Behalf Of Gregory
Palgrave
Sent: Monday, December 07, 2009 8:19 PM
To: [login to unmask email]
Subject: Re: [DB2-L] DB2 LUW V8.2 Tablespace Unavailable



Jeff,



You can try LIST HISTORY ALL SINCE <timestamp>, or check in the
db2diag.log file for info/error messages.

Perhaps you can add LIST TABLESPACES SHOW DETAIL and LIST UTILITIES (or
db2pd -uti) to the start/end of the weekly backup job as well?



Cheers



Greg



From: IDUG DB2-L [mailto:[login to unmask email] On Behalf Of Schade,
Jeffrey
Sent: Monday, 7 December 2009 9:56 PM
To: [login to unmask email]
Subject: [DB2-L] DB2 LUW V8.2 Tablespace Unavailable



I have a weekly database backup which fails sometimes because the
catalog tablespace is in an unavailable status. By the time I log in and
check the errors the status has cleared and I am having trouble
identifying the culprit. Is there some catalog table I can access which
will show me the utilities that have been run against the catalogs (i.e.
similar to SYSCOPY in the DB2 for Z/Os environment)? I plan on setting
up a job that will run if my backup fails which will do a LIST
APPLICATIONS and LIST TABLESPACES SHOW DETAIL to try an id the task. Is
there a better way of accomplishing this?



Jeff

_________________________________________
Jeffrey Schade

Systems Consultant, Technology Engineering


ISO
545 Washington Boulevard
Jersey City, NJ 07310
Voice: (201) 469-3738

FAX: (201) 748-1500
[login to unmask email] <mailto:[login to unmask email]>



This email is intended for the recipient only. If you are not the
intended recipient please disregard, and do not use the information for
any purpose.



________________________________



The IDUG DB2-L Listserv is only part of your membership in IDUG. If you
are not already an IDUG member, please register here.
< http://www.idug.org/register >



________________________________

IDUG - The Worldwide DB2 User Community!
< http://www.idug.org/db2-north-america-conference/index.html >

The IDUG DB2-L Listserv is only part of your membership in IDUG. If you
are not already an IDUG member, please register here.
< http://www.idug.org/register >

This email is intended for the recipient only. If you are not the intended recipient please disregard, and do not use the information for any purpose.

_____________________________________________________________________

* IDUG North America * Tampa, Florida, * May 10-14 2010 * http://IDUG.ORG/NA *
_____________________________________________________________________

http://www.idug.org/events/index.html is your DB2 Events calendar! RUG meetings,
Webcasts, Conferences- what is going on next?
RUG leaders- get your events on the calendar today!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's DB2-L