NFM upgrade job DSNTIJNF failed

JITINDER CHOUDHARY

NFM upgrade job DSNTIJNF failed

Hi All,

After running the NFM migration job DSNTIJNF job we are getting below error. Could anyone help regarding this.

 

DSNG007I -DBN1 DB2 CATALOG LEVEL (1110) CODE LEVEL (1110) MODE (EN)
DSNT537I -DBN1 DSNIRTSU REAL-TIME STATISTICS
EXTERNALIZATION HAS BEEN DISABLED

IXL014I IXLCONN REBUILD REQUEST FOR STRUCTURE DSNDBN0_SCA
WAS SUCCESSFUL. JOBNAME: DBN1MSTR ASID: 0099
CONNECTOR NAME: DB2_DBN1 CFNAME: ERCFN0S
ADDITIONAL STATUS INFORMATION:
REBUILD IS IN PROGRESS
IXL015I REBUILD NEW STRUCTURE ALLOCATION INFORMATION FOR
STRUCTURE DSNDBN0_SCA, CONNECTOR NAME DB2_DBN1,
CONNECTIVITY=DEFAULT
CFNAME ALLOCATION STATUS/FAILURE REASON
-------- ----------------------------------------
ERCFN0S STRUCTURE ALLOCATED A4000800
ERCFN0K PREFERRED CF ALREADY SELECTED A4000800
PREFERRED CF HIGHER IN PREFLIST
DSN7508I -DBN1 DSN7LRW1
ACCESS TO THE SCA STRUCTURE DSNDBN0_SCA FAILED.
MVS IXLLIST RETURN CODE = 0000000C,
MVS IXLLIST REASON CODE = 0C1C0C17.
DSN7504I -DBN1 DSN7LST2
SCA STRUCTURE DSNDBN0_SCA REBUILD UNSUCCESSFUL. REASON CODE = 8.
IEA043I SVC DUMP REACHED MAXSPACE LIMIT - MAXSPACE=00000500 MEG
IEA794I SVC DUMP HAS CAPTURED:
DUMPID=002 REQUESTED BY JOB (DBN1MSTR)
DUMP TITLE=DBN1,ABND=04E-00F70601,U=SYSOPR ,M=E ,C=111.ASMC-D
SNVEUS3,M=DSNVEUS3,LOC=DSN7LLM1.DSN7LXR1+109A
DSNT537I -DBN1 DSNIRTSU REAL-TIME STATISTICS
EXTERNALIZATION HAS BEEN ENABLED

Quick response is much appreciated

Todd Burrell

NFM upgrade job DSNTIJNF failed
(in response to JITINDER CHOUDHARY)
Please show us the output for the following display:

D XCF,STR,STRNAME=DSNDBN0_SCA

I believe there are some jobs that you cannot run if your structure is in DUPLEX mode?


From: JITINDER CHOUDHARY [mailto:[login to unmask email]
Sent: Monday, October 30, 2017 11:45 AM
To: [login to unmask email]
Subject: [DB2-L] - NFM upgrade job DSNTIJNF failed


Hi All,

After running the NFM migration job DSNTIJNF job we are getting below error. Could anyone help regarding this.



DSNG007I -DBN1 DB2 CATALOG LEVEL (1110) CODE LEVEL (1110) MODE (EN)
DSNT537I -DBN1 DSNIRTSU REAL-TIME STATISTICS
EXTERNALIZATION HAS BEEN DISABLED

IXL014I IXLCONN REBUILD REQUEST FOR STRUCTURE DSNDBN0_SCA
WAS SUCCESSFUL. JOBNAME: DBN1MSTR ASID: 0099
CONNECTOR NAME: DB2_DBN1 CFNAME: ERCFN0S
ADDITIONAL STATUS INFORMATION:
REBUILD IS IN PROGRESS
IXL015I REBUILD NEW STRUCTURE ALLOCATION INFORMATION FOR
STRUCTURE DSNDBN0_SCA, CONNECTOR NAME DB2_DBN1,
CONNECTIVITY=DEFAULT
CFNAME ALLOCATION STATUS/FAILURE REASON
-------- ----------------------------------------
ERCFN0S STRUCTURE ALLOCATED A4000800
ERCFN0K PREFERRED CF ALREADY SELECTED A4000800
PREFERRED CF HIGHER IN PREFLIST
DSN7508I -DBN1 DSN7LRW1
ACCESS TO THE SCA STRUCTURE DSNDBN0_SCA FAILED.
MVS IXLLIST RETURN CODE = 0000000C,
MVS IXLLIST REASON CODE = 0C1C0C17.
DSN7504I -DBN1 DSN7LST2
SCA STRUCTURE DSNDBN0_SCA REBUILD UNSUCCESSFUL. REASON CODE = 8.
IEA043I SVC DUMP REACHED MAXSPACE LIMIT - MAXSPACE=00000500 MEG
IEA794I SVC DUMP HAS CAPTURED:
DUMPID=002 REQUESTED BY JOB (DBN1MSTR)
DUMP TITLE=DBN1,ABND=04E-00F70601,U=SYSOPR ,M=E ,C=111.ASMC-D
SNVEUS3,M=DSNVEUS3,LOC=DSN7LLM1.DSN7LXR1+109A
DSNT537I -DBN1 DSNIRTSU REAL-TIME STATISTICS
EXTERNALIZATION HAS BEEN ENABLED

Quick response is much appreciated

-----End Original Message-----



This email transmission and any accompanying attachments may contain CSX privileged and confidential information intended only for the use of the intended addressee. Any dissemination, distribution, copying or action taken in reliance on the contents of this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please immediately delete it and notify sender at the above CSX email address. Sender and CSX accept no liability for any damage caused directly or indirectly by receipt of this email.

Mahmood Wadee

RE: NFM upgrade job DSNTIJNF failed
(in response to JITINDER CHOUDHARY)

Check link - http://www-01.ibm.com/support/docview.wss?uid=isg1II14807 .. Hope it helps !

Mahmood Wadee

RE: NFM upgrade job DSNTIJNF failed
(in response to Mahmood Wadee)

From the retain site .. PMR on this issue reported before.
Seems to explain your problem

"

Printable view   Return to hit list   New search   Rate this page   Save to favorites   View or add comments   < Previous   |   hit 6 of 115   |   Next >    


Category: PMRStatus: CL1L2Create date: 2017-07-05Last modified: 2017-07-06Rating: not yet ratedHarmful:No
IBM Confidential RETAIN view | Organized view

PMR 01589,004,000

 

NFM SCA REASON CODE = 0C1C0C17

SRID: USR3S87L4KR Stat: CL1L2 PMR: 01589,004,000 Entitle: N __ Rqst: SOFTWARE SubRqst: SOFTWARE DEFECT SUPPORT Queu: DB2PS Ctr: 117 S2 P2 __ Con: Ronald Head ________________ Comp: 5740XYR00 __ Rel: B10 ConPh: 254-771-7258 ______ SC: 75 RtID: ___________ Lvl: 2 GenPh: 254 771 7500 ______ Cat: XSR PID#: ______ VRM: __ NxtQ: _____ NxtCtr: __ PA: _____ Cust: 5644205 MCLANE CO INC CPU: 0000 ______ XCL SP: N Cmts: NFM SCA REASON CODE = 0C1C0C17 _______________________ Ar: 10 _______________________________________________________________ Ent: __:__/__ _____ Dly: __ : __ / __ APAR: ______ BU: USA O17/07/05 07:03 Dsp: __:__/__ _____ T/D: ECT: ________ Ter: 346 A17/07/06 11:39 Req: __:__/__ _____ ESN: ____________ Sysdown: Surv: _ FUP/07/07 Own: GANNON, PATRICK ______ OwnID: O785485 SWBO/Cty: S004000 Res: GANNON, PATRICK ______ ResID: R785485 EMail: [login to unmask email] Service Options: 390 390 AIX AS4 RSC __ __ CritSit: _____________ KW1: _________________ KW2: ________ KW3: ______________
+TIVOLI 20 -5740XYR00 -L117/DB2PS -P2S2-17/07/05-07:03--CE
*** Electronic submission by customer via SR tool, version 3.4.7
*** Preferred contact method: Email-address.
*** Customer contact full name: Ronald Head
*** Telephone: 254-771-7258
*** Alt. telephone: 254-771-7258
*** Mobile phone: 254-813-7321
*** Email: [login to unmask email]

.
Problem Details
.
Product or Service: DB2 Base z/OS 11.1.0
Component ID: 5740XYR00
.
Operating System: z/OS
.
Problem title
NFM SCA REASON CODE = 0C1C0C17
.
Problem description and business impact
Using DB2 for z/OS 11.1.0 on z/OS 02.02.00, DB2 is issuing DSN7508I
(MVS IXLLIST REASON CODE = 0C1C0C17) when running NFM job DSNTIJNF or
when DB2 is being started.  How do we need to adjust our Coupling
Facility settings for the SCA for the offending DB2 subsystem?  Two DB2
subsystems were put into NFM mode without any issues.  We need to
resolve this issue so we can move forward with NFM for 5 (2 production,
3 test) more DB2 subsystems." 
.

Solutions

---------------
"

Due to the increase in SCA size needed for NFM in order to accommodate
the expanded RBA increase from 6 to 10 bytes, most customers have needed
 a minimum of 7M initially in order to start DB2 under V11 NFM.
 Please increase the SCA size to a minimum of 7M INITSIZE.
.
A DISPLAY GROUP periodically will show what percentage of the current
size of your SCA is being used. Also, a good rule of thumb is that the
SIZE of the SCA be double that of the INITSIZE to allow for some room
to grow. There are some suggestions for SCA sizes listed in Table 1.
Estimating storage for the SCA at URL:
http://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/com.ibm.db2z11.
doc.inst/src/tpc/db2z_scasizeds.dita?lang=en
My suggestion then would be to see what percentage of the SCA is in
use, and then make sure that you have double that available to grow into
and you should be good to go. The other option would be to change the
structure to ALLOWAUTOALT YES so that it would adjust itself but that is
not always something that is allowed in some shops that wish for tighter
controls."

JITINDER CHOUDHARY

RE: NFM upgrade job DSNTIJNF failed
(in response to Todd Burrell)

Hi Todd,

 

Please find the requested details as below.

STRNAME: DSNDBN0_GBP0
STATUS: REASON SPECIFIED WITH REBUILD START:
POLICY-INITIATED
DUPLEXING REBUILD
METHOD: USER-MANAGED
PHASE: DUPLEX ESTABLISHED
EVENT MANAGEMENT: POLICY-BASED
TYPE: CACHE
POLICY INFORMATION:
POLICY SIZE : 8000 K
POLICY INITSIZE: 6000 K
POLICY MINSIZE : 0 K
FULLTHRESHOLD : 80
ALLOWAUTOALT : NO
REBUILD PERCENT: N/A
DUPLEX : ENABLED

STRNAME: DSNDBN0_GBP16K0
STATUS: REASON SPECIFIED WITH REBUILD START:
POLICY-INITIATED
DUPLEXING REBUILD
METHOD: USER-MANAGED
PHASE: DUPLEX ESTABLISHED
EVENT MANAGEMENT: POLICY-BASED
TYPE: CACHE
POLICY INFORMATION:
POLICY SIZE : 8000 K
POLICY INITSIZE: 6000 K
POLICY MINSIZE : 0 K
FULLTHRESHOLD : 80
ALLOWAUTOALT : NO
REBUILD PERCENT: N/A
DUPLEX : ENABLED
ALLOWREALLOCATE: YES
PREFERENCE LIST: ERCFN0K ERCFN0S
ENFORCEORDER : NO
EXCLUSION LIST IS EMPTY

STRNAME: DSNDBN0_GBP32K
STATUS: REASON SPECIFIED WITH REBUILD START:
POLICY-INITIATED
DUPLEXING REBUILD
METHOD: USER-MANAGED
PHASE: DUPLEX ESTABLISHED
EVENT MANAGEMENT: POLICY-BASED
TYPE: CACHE
POLICY INFORMATION:
POLICY SIZE : 10000 K
POLICY INITSIZE: 6000 K
POLICY MINSIZE : 0 K
FULLTHRESHOLD : 80
ALLOWAUTOALT : NO
REBUILD PERCENT: N/A
DUPLEX : ENABLED
ALLOWREALLOCATE: YES
PREFERENCE LIST: ERCFN0K ERCFN0S
ENFORCEORDER : NO
EXCLUSION LIST IS EMPTY

STRNAME: DSNDBN0_GBP8
STATUS: NOT ALLOCATED
POLICY INFORMATION:
POLICY SIZE : 4000 K
POLICY INITSIZE: 3000 K
POLICY MINSIZE : 0 K
FULLTHRESHOLD : 80
ALLOWAUTOALT : NO
REBUILD PERCENT: N/A
DUPLEX : ENABLED
ALLOWREALLOCATE: YES
PREFERENCE LIST: ERCFN0K ERCFN0S
ENFORCEORDER : NO
EXCLUSION LIST IS EMPTY

STRNAME: DSNDBN0_GBP8K0
STATUS: REASON SPECIFIED WITH REBUILD START:
POLICY-INITIATED
DUPLEXING REBUILD
METHOD: USER-MANAGED
PHASE: DUPLEX ESTABLISHED
EVENT MANAGEMENT: POLICY-BASED
TYPE: CACHE
POLICY INFORMATION:
POLICY SIZE : 8000 K
POLICY INITSIZE: 4000 K
POLICY MINSIZE : 0 K
FULLTHRESHOLD : 80
ALLOWAUTOALT : NO
REBUILD PERCENT: N/A
DUPLEX : ENABLED

JITINDER CHOUDHARY

RE: NFM upgrade job DSNTIJNF failed
(in response to JITINDER CHOUDHARY)

Hi All,

Here do we need to change the size as below to come out from this issue.

From

STRNAME: DSNDBN0_SCA              

 STATUS: ALLOCATED                

 EVENT MANAGEMENT: POLICY-BASED   

 TYPE: LIST                       

 POLICY INFORMATION:              

  POLICY SIZE    : 12000 K        

  POLICY INITSIZE: 6000 K         

 

TO

STRNAME: DSNDBN0_SCA              

 STATUS: ALLOCATED                

 EVENT MANAGEMENT: POLICY-BASED   

 TYPE: LIST                       

 POLICY INFORMATION:              

  POLICY SIZE    : 24000 K        

  POLICY INITSIZE: 12000 K         

Thanks in advance.

Olle Brostrom

NFM upgrade job DSNTIJNF failed
(in response to JITINDER CHOUDHARY)
Hi,
Use this tool: http://m.ibm.com/http/www-947.ibm.com/systems/support/z/cfsizer/index.html


Best Regards

Olle Broström

From: JITINDER CHOUDHARY [mailto:[login to unmask email]
Sent: den 1 november 2017 06:50
To: [login to unmask email]
Subject: [DB2-L] - RE: NFM upgrade job DSNTIJNF failed


Hi All,

Here do we need to change the size as below to come out from this issue.

From

STRNAME: DSNDBN0_SCA

STATUS: ALLOCATED

EVENT MANAGEMENT: POLICY-BASED

TYPE: LIST

POLICY INFORMATION:

POLICY SIZE : 12000 K

POLICY INITSIZE: 6000 K



TO

STRNAME: DSNDBN0_SCA

STATUS: ALLOCATED

EVENT MANAGEMENT: POLICY-BASED

TYPE: LIST

POLICY INFORMATION:

POLICY SIZE : 24000 K

POLICY INITSIZE: 12000 K

Thanks in advance.

-----End Original Message-----

JITINDER CHOUDHARY

RE: NFM upgrade job DSNTIJNF failed
(in response to Mahmood Wadee)

Hi Mahmood,

We have increased the SCA   STRUCTURE SIZE:    12288 KB.

Do we need to also increase the SIZE and INITSIZE also.as below or increase in SCA size is enough.

From

STRNAME: DSNDBN0_SCA              

 STATUS: ALLOCATED                

 EVENT MANAGEMENT: POLICY-BASED   

 TYPE: LIST                       

 POLICY INFORMATION:              

  POLICY SIZE    : 12000 K        

  POLICY INITSIZE: 6000 K         

 

TO

STRNAME: DSNDBN0_SCA              

 STATUS: ALLOCATED                

 EVENT MANAGEMENT: POLICY-BASED   

 TYPE: LIST                       

 POLICY INFORMATION:              

  POLICY SIZE    : 24000 K        

  POLICY INITSIZE: 12000 K         

Mahmood Wadee

RE: NFM upgrade job DSNTIJNF failed
(in response to JITINDER CHOUDHARY)

Hi ,

I cannot comment on the sufficiency of the size allocations but I would recommend that you change the INITSIZE and SIZE parameters when you change the SCA size.

The size parameter is theoretical maximum so it should be > the size which you used in your ALTER.

As far as I recall the SCA allocates memory for the BSDS, LOGS of the members and exceptions on database objects. You can look at these entries and make a decision.