cancel
Showing results for 
Search instead for 
Did you mean: 

EhP 5 update error in Phase MAIN_SHDIMP/PARMVNT_SHD!

marc_saulnier
Participant
0 Kudos

Hi all, I hope somebody will be able to help on this one ... I am stick on a Severe error in phase MAIN_SHDIMP/PARMVNT_SHD! during EhP 5 update.

There is the result of the log MVMTSHD.ELG

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

MVNTABS ERRORS: ddlntabs and RETURN CODE in PD000928.SBX

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

2EETP345 14:16:33: Retcode 1: SQL-error "-670-SQL0670N The row length of the table exceeded a limi

2EETP345 t of "4005" bytes. (Table space "PSAPSTABD".) SQLSTATE=54010" in DDL statement for "ESH_

2EETP345 ADM_BIN_ERR "

2EETP334 14:16:33: error in DDL, nametab for "ESH_ADM_BIN_ERR" not activated

2EETP345 14:16:45: Retcode 1: SQL-error "-670-SQL0670N The row length of the table exceeded a limi

2EETP345 t of "4005" bytes. (Table space "PSAPBTABD".) SQLSTATE=54010" in DDL statement for "GLE_

2EETP345 FI_ITEM_MODF "

2EETP334 14:16:45: error in DDL, nametab for "GLE_FI_ITEM_MODF" not activated

2EETP345 14:16:57: Retcode 1: SQL-error "-670-SQL0670N The row length of the table exceeded a limi

2EETP345 t of "4005" bytes. (Table space "PSAPBTABD".) SQLSTATE=54010" in DDL statement for "GLE_

2EETP345 FI_ITEM_ORIG "

2EETP334 14:16:57: error in DDL, nametab for "GLE_FI_ITEM_ORIG" not activated

1 ETP111 exit code : "8"

It's look like the tables created in this Phase is too wide for a 4 KB tablespace.

Ok fine, This is what I try :

I followed the OSS note 1099936 with a newly created 16 K tablespaces associated with a 16 k bufferpoool and when I try to initialize the phase I had the same error message. It's look like EhP 5 does take in consideration my newly 16 K tablespaces. The script still use the 4 KB Tablespace "PSAPBTABD" in this case ....

Something else, It's look like the shadow system does not came up but I am not sure if it's normal or not at this Phase (MAIN_SHDIMP/PARMVNT_SHD) because the shadow system was working perfectly before that.

Thanks for help

Accepted Solutions (1)

Accepted Solutions (1)

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Since this phase comes after MAIN_SHDRUN/STOP_SHDI_LAST, so shadow instance will no more start.

Have you tried closing EHPI gui and start it again after implementing SAP note 1099936 ? Please also us know your DB version and OS.

Thanks

Sunny

marc_saulnier
Participant
0 Kudos

>>Have you tried closing EHPI gui and start it again after implementing SAP note 1099936 ? Please also us know your DB version and OS.

Hi Sunny, thanks for the reply. Yes I tried to close EHPI gui. In fact I restarted the whole computer. , there is the require informations.

root@sapsbx(/etc) # oslevel -s

AIX 6100-06-03-1048

db2sbx> db2level

DB21085I Instance "db2sbx" uses "64" bits and DB2 code release "SQL09057" with

level identifier "06080107".

Informational tokens are "DB2 v9.5.0.7", "s101129", "IP23136", and Fix Pack

"7".

Product is installed at "/opt/IBM/db2/V9.5".

marc_saulnier
Participant
0 Kudos

Hi, I asked clarification from SAP and I need to do the following thing :

1) Rename my 4 KB tablespace ex: PSAPBTABD => PSAPBTAB4KD

2) Create a new tablespace of 16 KB with the same name than before PSAPBTABD.

Regards

Answers (0)