cancel
Showing results for 
Search instead for 
Did you mean: 

Error while doing SP update on PI 7.1 dual stack

Former Member
0 Kudos

Hi All,

We are in process of doing support pack update for PI 7.1 to stack 19 using SUM on Win 2003 R2 server with Maxdb 7.9 db. We are stuck with a error in the execution phase and below is the error,

Deployment of archive D:\usr\sap\trans\EPS\in\ETPRJSCHEDULER19_0-10006469.SCA --> scheduler-dblayer-sda.sda for component redwood.com/scheduler-dblayer-sda aborted

Detailed message: 1. [ERROR CODE DPL.DBC.204] failed to deploy dbschemacontainer : scheduler-dblayer-sda.sda  D:\usr\sap\NPI\DVEBMGS00\j2ee\cluster\server0\temp\deploy\work\deploying\scheduler-dblayer-sda.sda1436281991203\scheduler-dblayer-sda.sda. Return code from dictionary library is ERROR.

  -> [ERROR CODE DPL.DBC.901] Deploy operation finished with ERROR code.

The following messages were collected by DBModificationController during deployment:

ERROR SUMMARY:

E R R O R ******* (DbSapTable dev 30.07.2013 13:00:00)

8:13:12 2015-07-07 sap-Error:  checkWidth JCS_JOBDEFPARAM0: total width(8514) greater than allowed maximum (8088)

E R R O R ******* (DbSapTable dev 30.07.2013 13:00:00)

8:13:13 2015-07-07 sap-Error:  checkWidth JCS_OPERMESSAGE0: total width(8183) greater than allowed maximum (8088)

More details can be found in the trace and log files.

See Deploy Controller log D:\usr\sap\SUM\sdt\log\SUM\deploy_api.0.log for details.

.

Kindly help me out.

Regards,

Nikilesh

Accepted Solutions (0)

Answers (3)

Answers (3)

0 Kudos

Hi Nikilesh,


did you face any solution to this? Today i run into same problem...


Thanks & kind regards,

Norman

Former Member
0 Kudos

Hi Norman,

No we were not able to find a solution for this error. So, we reinstalled our PI 7.1 on Maxdb 7.8 and tried to apply the same stack of 19, but we ran into same issue again. Hence now we are going to try with stack 20, I will let you know if it resolves the issue.

Regard,

Nikilesh

valeriocicchiel
Contributor
0 Kudos

Hello everyone,

did you apply note 1315944 - 32 KB width table in MaxDB for Java DDIC as written before?

The note tell to patch these software component to the level indicated to avoid the issue:

- J2EE ENGINE SERVERCORE 7.11

SP003

000000

- NW CE DEVELOPER STUDIO 7.11

SP003

000000

Regards,

Valerio

Former Member
0 Kudos

Hi Chicchiello,

I tried to apply the stack 20 but ran into the same issue.

How do we patch these software components to the level indicated?

-J2EE ENGINE SERVERCORE 7.11

SP003

000000

- NW CE DEVELOPER STUDIO 7.11

SP003

000000

Regards,

Nikilesh

JamesZ
Advisor
Advisor
0 Kudos

Hi Nikilesh,

The problem does not sound like a database issue, you may need to reach sap upgrade support team to solve this problem.

Best regards,

James

Former Member
0 Kudos

I have raised it with SAP. Will let you know if I receive anything.

Regards,

Nikilesh

valeriocicchiel
Contributor
0 Kudos

Hello Nikilesh,

this SAP note should apply:  1315944 - 32 KB width table in MaxDB for Java DDIC

Could you please double check the information provided too? In particular, MaxDB 7.9 is not supported under Windows 2003

Regards,

Valerio

Former Member
0 Kudos

Hello Valerio,

Thanks for the reply.

This was a working instance without any problems till the update was started. And the note provided is not that clear, can you please explain me what does it mean?

"

Solution


OpenSQL for Java 7.11 Support Package 3
OpenSQL for Java 7.20

MaxDB 7.7

"

Regards,

Nikilesh