Skip to Content
0
Former Member
Jun 16, 2012 at 11:47 AM

Error during the DBCLONE phase in EHP2 upgrade(SCM)

127 Views

Dear Friends,

I need your great help in resolving my error. Now we are doing the SCM patch upgrade to EHP2 from EHP1 using SUM tool

Ours is DB2 9.7 FP3 and AIX 61.

Let me explain the scenario

1, We have done system copy from P60 (production) to S60 (sandbox). It completed successfully and all tablespaces are converted to S60#*........

But unfortunately it is still under the SAPNODEGRP_P60

SAPNODEGRP_P60

2. Without noticing this i have started doing the SCM patch upgrade to EHP2 from EHP1 using SUM tool. In one phase , it has asked me to create the 3 tablespaces ( S60#EL731D, S60#EL731I, S60#ES731D) and there was script in the log file..

I have run the log file.. it created three tablespaces in SAPNODEGRP_S60.

3. In actuall DBCLONE phase,we faced below issues in MAIN_SHDCRE/SUBMOD_SHDDBCLONE/DBCLONE phase.

rows: 124. Number of copied rows: 124.

5 ETGCLN /SAPDMC/LSCSTEPT done in 0 seconds

3 ETGCLN START AAB_ID_PROPT -> AAB_ID_PROPT~

3 ETGCLN Primary key strategy for current table is 0

3 ETGCLN CREATE TABLE "AAB_ID_PROPT~" ("LANGU" SAPDB6CHAR(000001) DEFAULT ' ' NOT NULL, "NAME" SAPDB6CHAR(000030) DEFAULT ' ' NOT NULL, "DESCRIPT" SAPDB6C HAR(000080) DEFAULT ' ' NOT NULL) IN "S60#ES731D" INDEX IN "S60#ES701I" LONG IN "S60#ES731D" COMPRESS NO

1EETGCLN SQL1754N The index table space or long table space is not in the same database partition group as the primary table space. SQLSTATE=42838

1EETGCLN AAB_ID_PROPT

1EETGCLN Error when cloning table structure

I have realized now that.. there are SAPNODEFRP_P60 and SAPNODEGRP_S60 and

S60#*701* tablespaces are pointing to P60 Nodegroup

S60#*731* pointing to S60 Node group.

I have woraround:

1. Need to alter the existing (original) TB which are under P60 node group to another name(duplicate)

2. Create the existing(original) TB under the S60 node group

3.Move the tables from the duplicate TB to original TB of S60 Node group.

For the above three steps, I need DB commands to move further.

Otherwise, Please suggest any other solution to address the issue.

Regards,