EHP5 to EHP7 Upgrade Error in Phase MAIN_SWITCH/PARMVNT_XCNV

[Former Member]

Hi All,

I am upgrading ECC6 EHP5 to EHP7.

In Phase MAIN_SWITCH/PARMVNT_XCNV I am getting a below sql binding error for Nametab ADMI_RUN.

ERROR:
Detected the following errors:

# \usr\sap\trans\SUM\abap\log\PD000916.MED:
3 ETP000 INSERT INTO @XSQL VALUES
3 ETP000 (' sap_atomic_defaultbind ' ',
3 ETP000 'ADMI_RUN', 'ORIG_DOCUMENT' ')
3 ETP000
2WETP000 14:45:38: Retcode 1: error in DDL statement for "ADMI_RUN " - repeat
2EETP345 14:45:50: Retcode 1: SQL-error "15103-Cannot bind a default to a column created with or al
2EETP345 tered to have a default value." in DDL statement for "ADMI_RUN "
2 ETP000 --------------- DB-ROLLBACK() ---------------
2EETP334 14:45:50: error in DDL, nametab for "ADMI_RUN" not activated

Attached is the log files.

Thanks

Muthu

PD000916.MED.txt.zip

MVNTXCNV.ELG.txt.zip

[Former Member]

Hi,

After reset of the sum tool, I have manually activate the table ADMI_RUN on the shadow instance before the Phase MAIN_SWITCH/PARMVNT_XCNV and the Upgrade went successful.

Regards

Muthu

[Former Member]

Hi Reagan & Billy,

Thanks for the effort guys. Much Appriciated.

I have reset the SUM and restored the DB and started the upgrade.

Will update you on the outcome.

Many Thanks

Muthu

[Reagan]

Activate the table ADMI_RUN manually from Tx SE11

Regards

RB

[Former Member]

Hi Regan,

Shadow system and main system is down in this phase. Cant connect to either instance.

Any other way to get this table activated.

[Reagan]

What is the database and the version used here ?

Check whether the SAP note applies 1086375 - User ID/Schema ID inconsistency in SQL database

Also you can start the system and login to the system and then try activating it manually.

Regards

RB

[Former Member]

Hi Reagan,

DB: MSSQL 2008 (10.0.2531)

Checked the SAP Note and its not relevant for my DB version.

Tried starting the Shadow instance, Dispatcher died.

ERROR => DpHdlDeadWp: W0 (pid 9160) died (severity=0, status=0) [dpxxwp.c     1325]

DpWpRecoverMutex: recover resources of W0 (pid = 9160)

********** SERVER SNAPSHOT 1 (Reason: Workprocess 0 died)

Tried starting the Main instance, All green. When tried to logon got the below error message.

Error DBIF_RSQL_TABLE_UNKNOWN Occured. P1=ABAP-gen.

Any Suggestions to get the system up.

Thanks

Muthu

[Reagan]

Muthu,

Try updating TP and R3trans and see if that helps.

Also raise an OSS message and see what the support says. Not sure whether this has got something to do with the TATAF table.

Regards

RB

[Former Member]

Hi Reagan,

I updated the TP latest and checked the dev_w0 log of the shadow system and found that its a database binding error.

ERROR: -1 in function StartSelect (execute) [line 14544]

C  (208) [42S02] [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name 'med.DDNTT~'.

C  ERROR: -1 in function StartSelect (execute) [line 14544]

C  (4413) [42000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Could not use view or function 'DDNTT' because of binding errors.

C  Error 103 (dbcode 208) in StartSelect

C  StartSelect: stmt of NULL_STMTID

C  SELECT COMPCNT, UNICODELG FROM "DDNTT" WHERE TABNAME = 'SVERS'

The log files i attached on the first post is also binding error.

I stopped the SUM tool and restarted the DB service and the server, But still the Database binding error occurs.

Any suggestions?

Thanks

Muthu

[bxiv]

My team just finished with dealing with a SVERS issue with a SCM system using SUM 1.0 SP11; we ended up restoring the DB and resetting SUM.

I think the issue was due to a java paging issue within the SL Toolset, which I think happened due to team mates running the SUM gui on the server itself as SIDadm; when I upgraded SCM 7.0 ehp2 to ehp3 the first four times I never encountered this error.  This happened during the DDIC_UPG phase of SUM and to get things rolling again I had to reboot the app server and start SUM.