EXPORT_TABLE_UPDATE_CONFLICT

[Former Member]

Hello All,

We are running Win 2003 on SQL Server 2005 on a Microsoft Cluster environment. During our high availability testing, we get this error "EXPORT_TABLE_UPDATE_CONFLICT" in ST22. We are logged in using App Server and are moving our SAP resources from Node A to Node B within the cluster administrator. Even though the GUI doesn't log us out, but it gives the above error and when we cancel the error, everything works normally.

Again when we move back from Node B to Node A, it gives the same error. SAP notes doesn't have any reference to this kind of error analysis.

Also, we are getting this same error in all of our SAP systems (ECC, BW, SRM,....) that are installed on clustered environment.

Below is the ST22 error dump:

Runtime Error EXPORT_TABLE_UPDATE_CONFLICT

Date and Time 27.07.2006 16:29:59

ShrtText

Problems found during the EXPORT to specified key in table.

What happened?

Error in ABAP application program.

The current ABAP program "SAPLSMTR_NAVIGATION_MODULES" had to be terminated

because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

is especially useful if you want to keep a particular message.

Error analysis

The table "INDX " does not contain any data records with the specified key.The system called the internal SAP database interface because it

expected to find such a key.

to correct the error

Probably the only way to eliminate the error is to correct the program.

-

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

---

"EXPORT_TABLE_UPDATE_CONFLICT" C

"SAPLSMTR_NAVIGATION_MODULES" or "LSMTR_NAVIGATION_MODULESU03"

"NAVIGATION_EXECUTE_OBJECT_HELP"

-

---

If you cannot solve the problem yourself and you wish to send

an error message to SAP, include the following documents:

1. A printout of the problem description (short dump)

To obtain this, select in the current display "System->List->

Save->Local File (unconverted)".

2. A suitable printout of the system log

To obtain this, call the system log through transaction SM21.

Limit the time interval to 10 minutes before and 5 minutes

after the short dump. In the display, then select the function

"System->List->Save->Local File (unconverted)".

3. If the programs are your own programs or modified SAP programs,

supply the source code.

Information on where terminated

The termination occurred in the ABAP program "SAPLSMTR_NAVIGATION_MODULES" in

"NAVIGATION_EXECUTE_OBJECT_HELP".

The main program was "SAPLSMTR_NAVIGATION ".

The termination occurred in line 56 of the source code of the (Include)

program "LSMTR_NAVIGATION_MODULESU03"

of the source code of program "LSMTR_NAVIGATION_MODULESU03" (when calling the

editor 560).

ANY RESPONSE WILL BE GREATLY APPRECIATED AND ALSO REWARDED WITH LOTS OF POINTS.

Thanks,

Fahad

[Former Member · Accepted solution]

well we have to have a look at the version you are using and what component is controlled by the SAP Resource.

up to netweaver 2004 the ABAP Central Instance was clustered. In case of an move from one node to the next one the CI was taken offline (shutdown), the basic resources moved to the next node and taken online again there. In this case central components will not be able to work during the failover and open transactions using resources in the CI will also fail in any way.

starting with NW 2004S the SAP resource group will normaly only contain the so called SAP Central Services (message server and standalone enqueue server). This instance is called SCS for the J2EE part and ASCS for the ABAP server.

For every SCS/ASCS instance there is one replication server on every clusternode which will enable a failover of the enque server without loosing the enqueue table.

And here comes the possible reason for the error you obtained, if running in an NW 2004S SCS/ASCS configuration:

Moving a resource group means taking the resource offline, move them to the next node and bringing them online again. Taking a resource offline will do a normal shutdown of the application.

If you want to move the SCS/ASCS SAP Resource to the next node in a cluster without loosing the enqueue table you have to enforce a failover by right clicking on the SAP Instance Resource and select <b>Initiate Failure</b>. In this case the SCS Instance will failover without loosing the enqueue table, because the enqueue server will not receive a normal stop request.

regards

Peter

Message was edited by: Peter Simon

Message was edited by: Peter Simon

[Former Member · Accepted solution]

Hello All,

Thanks for the response. We are on release NW 2004. We are still facing this problem. Our BW is ABAP only, ECC is ABAPJava and SRM is ABAPJava. We get the same error on all these 3 components when we initiate failure from cluster administrator.

As mentioned, for the HA testing purpose, we select the SAP resources and initiate failure. In the cluster administrator, the resources move to other Node.

During this failover, if we are logged on using CI, we are disconnected which should be normal. But when we are logged on using App Server, we shouldn't be disconnected. We are supposed to see some hour glass and the session should continue after some pause.(In this case we are getting the error Export_Data_Update_Conflict).

We don't understand where we are missing something.

Any more insight into this issue from you guys will be highly appreciated.

Thanks

Fahad

[Rudi_Wiesmayr]

Just found a documentation link in SDN:

SAP NetWeaver Application Server High Availability

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/89cb626b-0901-0010-d2b7-f5d...

Nice compilation...

[Rudi_Wiesmayr]

Hello Fahad!

Interesting topic. We did not know about the improvements in HA capabilities on Windows...

What release are you on? NW2004s?

Kind regards

Rudi