SUM sp 17 missing repository switch tablespace

[robertom]

Dears,

during an upgrade from PI 711 to PI 740 a strange thing happen:

the SUM did not requested the creation of the new tablespaces.

No errors, but simply the SUM takes  the tablespaces PSAPE*640 still present into the tablespace layout.

Yes the layout contains *640 tsp, no trace of the 7* tablespaces despite the system is already in 711 release; In TADB6 I found the table data class mapped to the *640 tablespaces.

No Idea about how the previous upgrade to 711 worked, but obviously the *640 tablespaces were used also at that time.

So the SUM went ahead without errors, ready to go in Execution phase.

But the question is :

how the SUM is supposed to work during the execution phase if the repository swich tablespaces are missing ?

Someone of you encontered the same situation ?

regards

[former_member189797]

Hi Roberto,

1. Reason for not asking to create the tablespace could be that tablespace in systems might not be correct even before starting the upgrade. For eg. you have a 740 source release system and dont have any 740 specific tablespace then it might not ask. You should make sure that these are correct before starting the upgrade.

2. In system switch upgrade, the switch of tables happens with rename command. You can find more details in EUSWITCH log files. You will see command like "rename <table>~ to <table>" so tablespace are not involved in switch or command.

3. Normally,If your source release and target release is same then it will add/delete 'X' at the end of release specific tablespace.

example: A series of  sp update will cause the below changes. Lets assume my current release is 740 and I have tablespace PSAPSR3740 then it would change as below

First SP update: PSAPSR3740 -> PSAPSr3740X
Second SP update PSAPSR3740X -> PSAPSR3740
Third SP update PSAPSR3740 -> PSAPSR3740X
.
.
and so on.

4. if your source release and target release are different then it would ask to create the tablespace with target release specific name but this would depend on correctness of your source system.

5. In any case you can correct the tablespace details after the upgrade with the help of your DBA. I think this point can be better explained by someone who have more knowledge about the database which you use.

Best Regards,
Gaurav

[Reagan]

As the first step, list all the tablespaces and check the space usage and also list the objects in the tablespaces from the database level. Not sure how the DB2 handles tablespaces during upgrade/update but for Oracle it will prompt for the tablespace creation using the BR*Tools. If there is already a tablespace which matches the release ID of the system then a tablespace with the similar name with an X at the end will be suggested on Oracle.

[former_member185239]

Hi Roberto,

The previous upgrade has not been done properly and the reason might be the same.

It will not affect your upgrade but if you want to plan next upgrade then you to move all the tables from the old tablespace to new tablespace. before upgrade to 711 or after the upgrade to 740.

With Regards

Ashutosh Chaturvedi