Error during upgrade SPS9 using SUM

[#1]

Hello all,

During NetWeaver 7.4 upgrade from SPS5 to SPS9 on our consolidation system in step 5.5 Pre-processing, I've got below error:

I've tried to repeat that action but it did not help. In previous week I've finished exactly the same upgrade on development system and I did not have any

problems. For now I have no clue why it is does work. If it is upgrade fault or might be problem on sybase side.

In logs I've seen something weird:

"Error while setting identity property for column C""RR_ID of logging table /1CRR/LT00001387"" "" "' raised".

It seems that table above can not be activated, I've spoke with our DBA's and they claimed that for them DB looks OK .....

If someone will have any solution I will be grateful.

Thanks in advance for your support.

Regards,

Karolina Plebanek

[former_member182657]

Hi Karolina,

Batchjob RSUPG_ISU_CRR on shadow system failed.

For the issue i would suggest you to refer SAP Note  1678564 - Restrictions, Database-specific Settings, and Troubleshooting of nZDM for SUM

Hope this will help you.

Good luck !!

[manumohandas82]

Hi Karolina ,

Have you increase the no of parallel process as it is QA ?

In addition to the note specified by Gaurav , Please also check the following if you are in AIX

This value (maxuproc) can be checked using the command 'lsattr -El sys0 -a maxuproc' and is often set too low at 128. You should use the command 'chdev -l sys0 -a maxuproc=1024' to set the value to at least 1024

1972803 - SAP on AIX: Recommendations

As suggested earlier specify your OS, Also the import logs

Thanks ,

Manu

[Former Member]

Hello Gourav,

I've tried in CRR_control to restart that job strictly follow SAP note which you mentioned above. Job was finished with success but still we see severe issue.

Any idea ?

Regards,

Karolina

[former_member182657]

Hi,

Are you getting same issue or any other ? If possible share the updated issue & related log files to support you .

Thanks,

[Former Member]

Hello Gaurav,

Still I am getting the same error, nothing has changed. Our DBA's were looking on the DB but they have not seen anything.. But they agreed  that the "Activation of the table" can be the guilty. Maybe it is the direction to solve our issue ? I am not expert in Sybase so I have no clue.
I've added two posts below logs where we can see the error.

Regards,

Karolina