Error during upgrade SPS9 using SUM

[Former Member]

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_member247883 · Accepted solution]

Dear Karolina:

Wich version of SUM are you ussing?  i recomend you the 1.0 SP13

on sybase please constantly review the file SID.log on the directory /sybase/MEP/ASE-15_0/install

this log file show if the database needs more locks, memory , open partitions, etc.

Try to check on the SE11 the table if exist on the database and if you can adjust.

Regards

[Former Member · Accepted solution]

Hello all,

I've tried all options which you described above and nothing was working 😕

That's why yesterday I decided that I will restart my upgrade of my consolidation system from scratch cause we had no idea what is wrong and how to solve that.
 

For now I can confirm that phase: RUN_CRR_LOGSTABS (which failed previously) now went successfully   I do not have any similar errors, upgrade is still running.

Propably the guilty of this issues was SUM. It is only explanation.
 

Thanks to everybody for your support.

regards,

Karolina

[Former Member]

Hello Yoga Pilla,

Thanks for your feedback.

So it means that you have had exactly the same issue with the tables as me.

As I wrote in the posts above after my checks and no new ideas I've decided to start upgrade from scratch cause I was afraid that I will not give back the system on time. After the restart I found out that it was good decision because upgrade could continue and finish successfully.

I am sure that this info will be helpful to other upgraders.

Good luck

regards,

Karolina Plebanek

[Former Member]

Dear Ms. Plebanek,

We were upgrading our sandbox ERP 6.0 EHP7  from SPS4 to SPS10, with SUM1.0 SP16 and selected nZDM (near-Zero Downtime Maintenance Technology) for upgrade.

We faced the same issue, got ST22 dumps in shadow instance and background job cancellation.  I searched in SCN and found this thread.

But in our case, we raised an OSS ticket to SAP. As per SAP's reply, there was a table named TTXVR which was having two versions. It was due to incomplete conversion of table TTXVR from POOLED to TRANSPARENT.

One version of this table is showing POOLED (which is active version) and other one is TRANSPARENT with inactive version.

As per SAP's suggestion, we reset the upgrade and then dropped the TRANSPARENT version of the table. Then restarted the SUM. Now our upgrade has finished successfully on our SANDBOX server.

This might be the reason, in your case too. Hope this post may helpful to other consultants, who may face this kind of issue in their upgrades.

Best Regards

Yogananda Kumar Pilla.

[Former Member]

Hello Karolina,

In your error you can see that there is an issue setting the identity property for column CRR_ID on table "/1CRR/LT00001387" which is the logging table related to table /ASU/SSMCONTENTP. I guess this is the way of linking this table back to what you see in crr_control.

Now what you need to determine is why the CRR_ID (incremental number) cannot be updated/set for "/1CRR/LT00001387".

1. As a cross check, ask your DBA to check the columns of table "/1CRR/LT00001386" and see what value is assigned to CRR_ID for this table. Logically (based on the assumption above) it would be 1386.

2. Ask you DBA to check the DB logs to see if anything is being logged during the failed creation of "/1CRR/LT00001387" In the SQL cache I would imagine you could see the SQL statement that was executed.

3. Even though I doubt it has anything to do with your problem, please check table /ASU/SSMCONTENTP with tx: SE11 and reactivate it if necessary.

4. Try repeating the phase with the INIT option (nothing to lose by trying).

5. In parallel, open a message with SAP. It's what you pay your license fee for.

KR,

Amerjit

[divyanshu_srivastava3]

Have you checked the job logs on what it says.

Please upload your SUM logs for this phase.

Also, share your system OS/DB version details.

Regards,

[Former Member]

Hello Divyanshu,

Yes I've checked the logs and as you can see I've added them already in post above. It seems that something is wrong with activating or creating of one the table but I am not sure.

Details of OS/DB:

Thanks for support.

Regards,

Karolina

[manumohandas82]

Hi Karolina ,

Please confirm your OS version

Thanks ,

Manu

[Former Member]

Hello Manu,

Our system is running on Linux so the problem exists not there.

Thanks for help.

regards,

Karolina

[former_member182657]

Hi Karolina,

Hope you followed mentioned SAP Note as suggested earlier.If possible could you share failed job log ?

Regards,

[Former Member]

Hello Gaurav,

I am attaching screenshot from CRR_CONTROL:

Logfile RSCRRLOG.ELG contains:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Generate logging tables for change recording ERRORS and RETURN CODE in RSCRRLOG.GTC

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

A4 ESCRR 208 Process "4"("asynchronously") completed at "13:47:52"("15.05.2015")

A4 ESCRR 208 Process "5"("asynchronously") completed at "13:47:52"("15.05.2015")

A4 ESCRR 208 Process "1"("asynchronously") completed at "13:47:53"("15.05.2015")

A4 ESCRR 216 RFC group "CRR" deleted

A4 ESCRR 056 Transition &2"ISU" failed for scenario &1"PREPARE_LOGTABS"

A2EESCRR 055 Parallel operation "CL_IUUC_CRE_CONTAINER" failed for scenario "ISU" (at least group "1" )

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Generate logging tables for change recording ERRORS and RETURN CODE in RSCRRLOG_1.GTC

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

A4 ESCRR 040 Parallel process "1" started with "CRR_PAR_OPERATION"

A4 ESCRR 114 Starting parallel operation "CL_IUUC_CRE_CONTAINER" for task "/ASU/SSMCONTENTP"

A4 ESCRR 041 Implementing class "CL_IUUC_CRE_LOGTAB_SYB" determined for "CL_IUUC_CRE_LOGTAB"

A4 ESCRR_IUUC 106 Dropping logging table "/1CRR/LT00001387"

A4 ESCRR_IUUC 103 Create logging table "/1CRR/LT00001387"

A2EESUPG 809 Invalid log message message with text '"Error while setting identity property for column C""RR_ID of logging table /1CRR/LT00001387"" "" "' raised

Please let me know if you will have any ideas.

Regards,

Karolina

[Former Member]

Hi Karolina,

Have you check the RFC group CRR in RZ12?

It should be assigned to the correct server.

Kindly paste the screenshot of rz12.

With Regards

Ashutosh Chaturvedi

[Former Member]

Hello Ashutosh,

I've checked RZ12 and it looks OK:

It refers to the shadow instance.

Regards,

Karolina

[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