cancel
Showing results for 
Search instead for 
Did you mean: 

Error while patching J2EE Java Engine from SP15 - SP20

Former Member
0 Kudos

We are patching our Enterprise Portal J2EE Java engine from SP15 - SP20 and are getting the following error.

Dec 10, 2007 5:26:20 PM Info: 17:26:18 2007-12-10 ora-Info: compareTo NAME: column length 256 larger than length 100 of target column

Dec 10, 2007 5:26:20 PM Info: 17:26:18 2007-12-10 dbs-Info: BC_CPT_MODULE modify column NAME from type : VARCHAR,len : 256,dec : 0,not null : true,default : | |

Dec 10, 2007 5:26:20 PM Info: 17:26:18 2007-12-10 dbs-Info: BC_CPT_MODULE modify column NAME from type : VARCHAR,len : 256,dec : 0,not null : true,default : | |

Dec 10, 2007 5:26:20 PM Info: 17:26:18 2007-12-10 dbs-Info: BC_CPT_MODULE modify column NAME to type : VARCHAR,len : 100,dec : 0,not null : true,default : | |

Dec 10, 2007 5:26:20 PM Info: 17:26:18 2007-12-10 dbs-Info: BC_CPT_MODULE modify column NAME to type : VARCHAR,len : 100,dec : 0,not null : true,default : | |

Dec 10, 2007 5:26:20 PM Info: 17:26:18 2007-12-10 dbs-Info: Action: CONVERT

Dec 10, 2007 5:26:20 PM Info: 17:26:18 2007-12-10 dbs-Info: Action: CONVERT

Dec 10, 2007 5:26:20 PM Info: 17:26:18 2007-12-10 dbs-Info: Table has to be converted

Dec 10, 2007 5:26:20 PM Info: 17:26:18 2007-12-10 dbs-Info: Table has to be converted

Dec 10, 2007 5:26:20 PM Info:

Dec 10, 2007 5:26:20 PM Info: E R R O R ******* (DbModificationManager)

Dec 10, 2007 5:26:20 PM Info: 17:26:18 2007-12-10 dbs-Error: Table BC_CPT_MODULE: Conversion currently not possible

Dec 10, 2007 5:26:20 PM Info:

Dec 10, 2007 5:26:20 PM Info: E R R O R ******* (DbModificationManager)

Dec 10, 2007 5:26:20 PM Info: 17:26:18 2007-12-10 dbs-Error: Table BC_CPT_MODULE: Conversion currently not possible

Dec 10, 2007 5:26:20 PM Error: Aborted: development component 'com.sap.engine.cpt.dbschema'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308110647.0000'/'1', grouped by :

No further description found.

Dec 10, 2007 5:26:20 PM Info: Starting to save the repository

Dec 10, 2007 5:26:21 PM Info: Finished saving the repository

Dec 10, 2007 5:26:21 PM Info: Starting: Update: Selected software component 'SAP-JEECOR'/'sap.com'/'SAP AG'/'1000.6.40.20.0.20070416050349''/'1' updates currently deployed software component 'SAP-JEECOR'/'sap.com'/'SAP AG'/'1000.6.40.15.0.20051215060259''/'0'.

Dec 10, 2007 5:26:21 PM Error: Aborted: software component 'SAP-JEECOR'/'sap.com'/'SAP AG'/'1000.6.40.20.0.20070416050349''/'1':

Failed deployment of SDAs:

development component 'com.sap.engine.cpt.dbschema'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308110647.0000'/'1' : aborted

Please, look at error logs above for more information!

Dec 10, 2007 5:26:21 PM Info: Starting to save the repository

Dec 10, 2007 5:26:22 PM Info: Finished saving the repository

Dec 10, 2007 5:26:22 PM Error: -


At least one of the Deployments failed -


Dec 10, 2007 5:26:25 PM Info: Summarizing the deployment results:

Dec 10, 2007 5:26:25 PM Error: Aborted: /opt/PORTALDISKS/PATCHES/JAVA/SP20/J2EE-RUNT-CD/J2EE-ENG/OFFLINE/SAPJEECOR20_0.SCA

Dec 10, 2007 5:26:25 PM Error: Admitted: /opt/PORTALDISKS/PATCHES/JAVA/SP20/J2EE-RUNT-CD/J2EE-ENG/OFFLINE/JRFC.SDA

Dec 10, 2007 5:26:25 PM Error: Processing error. Return code: 4

Can anyone help me on this please.

Many Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Check the current JDK version. If it is less than 1.4.2_12, first upgrade it to either 1.4.2_12 or greater, before applying patch.

Regards

Srinivasan T

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Hristo

Thanks for the info regarding the two tables and I can confirm that the Patch deployment has been successfully applied.

Regards

Steve

Former Member
0 Kudos

Hi, Steven ,

You got the right descision . In these tables is stored information related with traces analyzed with EndToEnd trace plugin in NWA . The data is not vital for java engine .

The problem is that Database can not update the table when they have a rows inserted.

Best Regards Hristo Shekov

Former Member
0 Kudos

Thanks Srinivasan T

We had the same thought but cannot see why this would produce the fault shown in our log files.

The errors seem to be in 2 specific tables BC_CPT_ACTION and BC_CPT_MODULE being unable to convert a column size from 256 chars to 100 chars.

We did a lot of searching for various things and found a SAPnote 939108 which had a similar error in it and recommended deleting the data in the erroring table.

So we had a quick look at our QA/Test & production portals and these tables are both empty in both these other 2 systems. So we've decide to copy these 2 tables and then delete the data from the originals in our development portal database and restarted the patch deployment.

This time the patch deployment has successfully converted the tables and has moved passed the stage at which it was failing.

The patch deployment is still running so it'll be a while before we know for certain whether we've overcome the problem.

Many Thanks though for taking the time to try to solve my problem.

Regards

Steve