Skip to Content
J A

DB6 tablespace issue during EHP7

Hello everyone, I have the following situation:

I was performing an update to ECC 6.0 EHP7 with SUM. During PARMVNT_SHD phase I got error code "SQL0960C" for tablespace POOLD (more than 53000 objects), So I followed SAP note 1019242 by renaming tablespace POOLD/POOLI to POOL2D/POOL2I and creating a new one POOLD/POOLI.

For some other reasons I had to reset the SUM (It was before downtime so I didn't use a backup). After the reset process POOLD tablespace got no tables and POOL2D tablespace got like 40000 tables.

Then I started a new update process and after DBLONE phase the tablespaces POOL2D/ POOL2I got some new more objects, Why is this happing? Shouldn't these objects be created in POOLD/POOLI tablespaces? What should I do when I reach PARMVNT_SHD phase again and POOL2D/POOL2I are full again?

System Info:

  • Source System: ECC 6.0 / NW 7.0 SP26
  • Target System: ECC 6.0 EHP7 / NW 7.4 SP7
  • Platform: DB6 9.7 FP10 / AIX 7.1
  • SUM: SP18 PL

Best regards,

JA

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Nov 17, 2016 at 09:35 AM

    Hello,

    During the dbclone phase the cloned objects are created within the same tablespace as the source object. For this reason, simply renaming the tablespace is not sufficient. You will have to move some objects from the tablespace so that the DBCLONE phase can complete. This is detailed in note:

    1778732 - SQL0960C The maximum number of objects encountered in DBCLONE phase

    However, if you hit the SQL0960C during normal operation, then the rename of the tablespace will work to resolve this error. All tables created by SAP will then be created within the newly created tablespace POOLD.

    Hope this is helpful,

    David

    Add comment
    10|10000 characters needed characters exceeded