cancel
Showing results for 
Search instead for 
Did you mean: 

Support Packages - DDIC ACTIVATION TAKE LONG TIME

jorge_velasquez
Contributor
0 Kudos

Hi Experts,

I am updating my PI System from 731 BASIS Level 0 to Level 10.


Its taken to much time in DDIC ACTIVATION PHASE also Transaction Logs are getting FULL.


No logs are overwritten since yesterday in trans directory.



SO: Windows

DB: MSSQL Server 2012


Any clue?

Accepted Solutions (1)

Accepted Solutions (1)

former_member185239
Active Contributor
0 Kudos

Hi jorge,

Check the SAP Note 1892988 - DDIC_ACTIVATION phase takes too long in transaction SPAM/SAINT

Just take the manual backup of transaction log and you can add one more transaction log .

once the transaction log is clear , then stop the patching and restart it again .

With Regards

Ashutosh Chaturvedi

jorge_velasquez
Contributor
0 Kudos

Hi,

The note 1892988 - DDIC_ACTIVATION phase takes too long in transaction SPAM/SAINT is exactly what is happening to me.

What should I do if still running?

Regards

former_member185239
Active Contributor
0 Kudos

Hi Jorge,

Checked the sapnote

1. First, SAP Note 1672480 - Runtime error COMPUTE_INT_PLUS_OVERFLOW in RADIXCHK;

2. And then, SAP Note 1678047 - COMPUTE_INT_PLUS_OVERFLOW during activation;

3. Release related transport request.

You can follow the suggestion as he was always correct

Involve the developer too.

With Regards

Ashutosh Chaturvedi

Answers (2)

Answers (2)

Reagan
Advisor
Advisor
0 Kudos

Hello

Unfortunately you haven't provided the logs for the issue you are facing.

First check whether you are observing COMPUTE_INT_PLUS_OVERFLOW dumps in the system.

If yes check this SAP Note:

Note 1678047 - COMPUTE_INT_PLUS_OVERFLOW during activation

Call Tx SE38 - SDB1FHDB

Select Source Code and Display

Switch to edit mode and replace:

limit-secindcnt = 2147483647.

with

limit-secindcnt = 1023.

You will need an object key to do this.

If the above mentioned suggestion is not your case then provide the logs.

Good Luck

RB

Sriram2009
Active Contributor
0 Kudos

Hi Jorge

You can do the two things anyway  SAP system down due to log db full

1. If possible to add the expand the disk space in log folder

2. Do the truncate the Log and then retry the Same phase

BR

SS