DB2 / PeopleSoft -904 problems creating indexes

Tracy Johnson

DB2 / PeopleSoft -904 problems creating indexes
Hello!
We are installing the PeopleSoft HR (v7.51) package (our first PeopleSoft
implementation) on our v5.1 (9907) system and are experiencing problems
trying to load the indexes. While creating a large number of indexes, we're
receiving the following errors:
The error in the job was ...
DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN
UNAVAILABLE RESOURCE. REASON 00D70017, TYPE OF RESOURCE

SDSF Log showed ...
DSNP012I + DSNPSCT0 - ERROR IN VSAM CATALOG LOCATE 522
FUNCTION FOR DBT1.DSNDBC.PSHRDB.PSRNDTRH.I0001.A001
CTLGRC=00000032
CTLGRSN=C5F00006
CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
LUW-ID=*

DSNP012I + DSNPCLO0 - ERROR IN VSAM CATALOG LOCATE 304
FUNCTION FOR DBT1.DSNDBD.PSHRD.PSRG1CNX.I0001.A001
CTLGRC=00000032
CTLGRSN=C5F20060
CONNECTION-ID=SERVER, CORRELATION-ID=psdmt.exe,
LUW-ID=GA18E09D.A005.991213234633=846
DSNP012I + DSNPDFN1 - ERROR IN VSAM CATALOG LOCATE 524
FUNCTION FOR DBT1.DSNDBD.PSHRDB.PSRNDTRH.I0001.A001
CTLGRC=00000032
CTLGRSN=C5F00006
CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
LUW-ID=*
LUW-ID=*
DSNP002I + DSNPDFN1 - DEFINE FAILED FOR 525
DBT1.DSNDBC.PSHRDB.PSRNDTRH.I0001.A001.
RC=00D70017
CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
LUW-ID=*
DSNP016I + DSNPCPS0 - CREATE FAILED FOR 526
PSHRDB.PSRNDTRH.I0001.
RC=00D70017
CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
LUW-ID=*

The volumes defined in the STOGROUP were initially under SMS control, but
have been removed from SMS' control now, and we still have the problem.
Also, early on there was a problem with the catalog VTOC running out of
space. That too, apparently, has been rectified by redefining the catalog
with a larger number of entries.
Our DBA is able to define indexes outside of the PeopleSoft database,
without experiencing this problem. Initially, approximately 3900 of 4700
were created before the errors occurred.
IBM's first response was that a volume in the STOGROUP is not mounted, or
does not exist. That does not appear to be the case, as we've tried
different testing and the volumes are there. We are running DIAGNOSIS
against the catalog to verify.
Any suggestions would be appreciated.

Thanks!
Tracy Johnson
GuideOne Insurance
515-267-5487



craig patton

Re: DB2 / PeopleSoft -904 problems creating indexes
(in response to Tracy Johnson)
Tracy,

Can you create the indexes outside of the long stream of DDL provided? In
the same Psoft DBs? The error message indicates an ICF problem or a DASD
volume problem. Make sure all DASD is ONLINE that WAS in the STOGROUP at
ANY TIME (Including when using SMS). Look in the MVS log to see if there
are any additional ICF error messages. In the past I have received this
error (yes with Psoft) and it was due to the volume containing the ICF
catalog was full and the ICF catalog needed to extend. I also ran into a
similar problem when loading the data and found that a volume in the
STOGROUP, when an index was defined, was varied offline and when building
the index it failed.

Your message seems related to simply defining the index vsam files and is
most likely NOT a DB2 problem. Keep looking to the ICF cataloging process.

HTH,
Craig Patton
DB2 DBA


>From: "Johnson, Tracy" <[login to unmask email]>
>Reply-To: DB2 Data Base Discussion List <[login to unmask email]>
>To: [login to unmask email]
>Subject: DB2 / PeopleSoft -904 problems creating indexes
>Date: Wed, 15 Dec 1999 10:18:12 -0600
>
>Hello!
>We are installing the PeopleSoft HR (v7.51) package (our first PeopleSoft
>implementation) on our v5.1 (9907) system and are experiencing problems
>trying to load the indexes. While creating a large number of indexes,
>we're
>receiving the following errors:
>The error in the job was ...
>DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN
> UNAVAILABLE RESOURCE. REASON 00D70017, TYPE OF RESOURCE
>
>SDSF Log showed ...
>DSNP012I + DSNPSCT0 - ERROR IN VSAM CATALOG LOCATE 522
>FUNCTION FOR DBT1.DSNDBC.PSHRDB.PSRNDTRH.I0001.A001
> CTLGRC=00000032
> CTLGRSN=C5F00006
> CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
> LUW-ID=*
>
>DSNP012I + DSNPCLO0 - ERROR IN VSAM CATALOG LOCATE 304
>FUNCTION FOR DBT1.DSNDBD.PSHRD.PSRG1CNX.I0001.A001
> CTLGRC=00000032
> CTLGRSN=C5F20060
> CONNECTION-ID=SERVER, CORRELATION-ID=psdmt.exe,
> LUW-ID=GA18E09D.A005.991213234633=846
>DSNP012I + DSNPDFN1 - ERROR IN VSAM CATALOG LOCATE 524
>FUNCTION FOR DBT1.DSNDBD.PSHRDB.PSRNDTRH.I0001.A001
> CTLGRC=00000032
> CTLGRSN=C5F00006
> CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
> LUW-ID=*
> LUW-ID=*
> DSNP002I + DSNPDFN1 - DEFINE FAILED FOR 525
> DBT1.DSNDBC.PSHRDB.PSRNDTRH.I0001.A001.
> RC=00D70017
> CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
> LUW-ID=*
> DSNP016I + DSNPCPS0 - CREATE FAILED FOR 526
> PSHRDB.PSRNDTRH.I0001.
> RC=00D70017
> CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
> LUW-ID=*
>
>The volumes defined in the STOGROUP were initially under SMS control, but
>have been removed from SMS' control now, and we still have the problem.
>Also, early on there was a problem with the catalog VTOC running out of
>space. That too, apparently, has been rectified by redefining the catalog
>with a larger number of entries.
>Our DBA is able to define indexes outside of the PeopleSoft database,
>without experiencing this problem. Initially, approximately 3900 of 4700
>were created before the errors occurred.
>IBM's first response was that a volume in the STOGROUP is not mounted, or
>does not exist. That does not appear to be the case, as we've tried
>different testing and the volumes are there. We are running DIAGNOSIS
>against the catalog to verify.
>Any suggestions would be appreciated.
>
>Thanks!
>Tracy Johnson
>GuideOne Insurance
>515-267-5487
>
>
>
>
>

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com



James Jones

Re: DB2 / PeopleSoft -904 problems creating indexes
(in response to craig patton)
Hi Tracy,

The reason code indicates an ICF catalog error. On our first PeopleSoft install, we ran out of space on both VTOC's, and the ICF catalog. If you're sure you've got VTOC space, check the
ICF catalog. Unfortunately, I don't remember the details, we've been on PS for three years.

HTH,

"Johnson, Tracy" wrote:

> Hello!
> We are installing the PeopleSoft HR (v7.51) package (our first PeopleSoft
> implementation) on our v5.1 (9907) system and are experiencing problems
> trying to load the indexes. While creating a large number of indexes, we're
> receiving the following errors:
> The error in the job was ...
> DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN
> UNAVAILABLE RESOURCE. REASON 00D70017, TYPE OF RESOURCE
>
> SDSF Log showed ...
> DSNP012I + DSNPSCT0 - ERROR IN VSAM CATALOG LOCATE 522
> FUNCTION FOR DBT1.DSNDBC.PSHRDB.PSRNDTRH.I0001.A001
> CTLGRC=00000032
> CTLGRSN=C5F00006
> CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
> LUW-ID=*
>
> DSNP012I + DSNPCLO0 - ERROR IN VSAM CATALOG LOCATE 304
> FUNCTION FOR DBT1.DSNDBD.PSHRD.PSRG1CNX.I0001.A001
> CTLGRC=00000032
> CTLGRSN=C5F20060
> CONNECTION-ID=SERVER, CORRELATION-ID=psdmt.exe,
> LUW-ID=GA18E09D.A005.991213234633=846
> DSNP012I + DSNPDFN1 - ERROR IN VSAM CATALOG LOCATE 524
> FUNCTION FOR DBT1.DSNDBD.PSHRDB.PSRNDTRH.I0001.A001
> CTLGRC=00000032
> CTLGRSN=C5F00006
> CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
> LUW-ID=*
> LUW-ID=*
> DSNP002I + DSNPDFN1 - DEFINE FAILED FOR 525
> DBT1.DSNDBC.PSHRDB.PSRNDTRH.I0001.A001.
> RC=00D70017
> CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
> LUW-ID=*
> DSNP016I + DSNPCPS0 - CREATE FAILED FOR 526
> PSHRDB.PSRNDTRH.I0001.
> RC=00D70017
> CONNECTION-ID=BATCH, CORRELATION-ID=$PPGMIX3,
> LUW-ID=*
>
> The volumes defined in the STOGROUP were initially under SMS control, but
> have been removed from SMS' control now, and we still have the problem.
> Also, early on there was a problem with the catalog VTOC running out of
> space. That too, apparently, has been rectified by redefining the catalog
> with a larger number of entries.
> Our DBA is able to define indexes outside of the PeopleSoft database,
> without experiencing this problem. Initially, approximately 3900 of 4700
> were created before the errors occurred.
> IBM's first response was that a volume in the STOGROUP is not mounted, or
> does not exist. That does not appear to be the case, as we've tried
> different testing and the volumes are there. We are running DIAGNOSIS
> against the catalog to verify.
> Any suggestions would be appreciated.
>
> Thanks!
> Tracy Johnson
> GuideOne Insurance
> 515-267-5487
>
>
>
Attachments

  • jim.jones.vcf (<1k)