Online Tutorials & Training Materials | STechies.com
Register Login

Except 30708 Connection Error with liveCache after system copy

|| || 0

Except 30708 Connection Error with liveCache after system copy
Stechies

An error occurs when you call the liveCache. The error text of the database is tExcept 30708.

You want to access the liveCache from the application server. However, the system name does not match the one specified in the liveCache. This may happen after a homogeneous system copy.

Background:


If two APO systems (for example the production system and the test system) access the same liveCache instance at the same time, this may cause irreparable data inconsistencies. As of LCA Release 6.0 (ABAP component LCAPPS_2006_700, used in SCM 5.1, for example), the liveCache therefore ensures that only one system at the time can access the liveCache. For this purpose, the system name (SY-SYSID) is saved in the liveCache when you first call the liveCache after its initialization. For further liveCache calls, the system checks whether the name of the called system matches the save system name. If this is not the case, this triggers short dump mentioned above.

Troubleshooting procedure:

If, in the framework of a homogenous system copy, you used backup and restore to copy liveCache data to the target system, you may have to reset the system name in the liveCache. Follow the instructions below in the section "Resetting the system name in liveCache" only if this is the case.
If this is not the case, check that the correct integration data for the liveCache is set in transaction LC10. Use the SLCA_GET_SYSNAME report to determine which system name is defined in the liveCache.
If you use SCM 7.0, implement Note 1349272 before you use the report SLCA_GET_SYSNAME.
If by doing this you cannot make out any incorrect settings, contact SAP Support.

Resetting the system name in liveCache

Use Backup/Restore to make a homogenous system copy. This also copies the system name defined in the liveCache. If you want to access the liveCache from the new APO system (target system), you must reset first reset the system name in the liveCache.

Only execute the resetting if you are in the situation described above. Otherwise, the resetting may cause irreparable inconsistencies in the liveCache and you may have to carry out an initialization.

The system name is reset in two steps:

To determine the LCA release and the build version, call transaction /SAPAPO/OM04. The "Release" column contains the LCA release, and the "Build" column contains the version of the LCA build.


Note: When you call transaction /SAPAPO/OM04 and
a short dump occurs with the database error -7500, register
the LCA routines as follows:

  • Call transaction LC10.
  • Enter the value LCA in the "Database Connection" field.
  • Choose "liveCache: Monitoring".
  • In the navigation tree on the left-hand side, open the following

    path LCA -> Administration and double-click the entry Operating.
  • On the right-hand side, the system should now display the "Register LCApps" button.


1. Delete the old system name.

 Execute the following command depending on the LCA release in the SQL Studio:

  • LCA Release 6.0 to LCA Release 7.0 LCA Build 04

    DROP TABLE APPSYSNAME
  • LCA Release 7.0 as of LCA Build 05 and higher

    DROP TABLE APPSYSPARAM

    Alternatively, you can also delete the entry using the DBMCLI program. To do so, execute the following command depending on the LCA release:
  • LCA Release 6.0 to LCA Release 7.0 LCA Build 04

    dbmcli -d <LC Instanz> -n <LC Server> -u DBM,<Passwort> -uSQL sap<sid> ,<Passwort> sql_execute DROP TABLE APPSYSNAME
  • LCA Release 7.0 as of LCA Build 05 and higher

    dbmcli -d <LC Instanz> -n <LC Server> -u DBM,<Passwort> -uSQL sap<sid> ,<Passwort> sql_execute DROP TABLE APPSYSPARAM

 2. Restart the liveCache or OneDB.

Immediately afterwards, restart the liveCache or OneDB.

During the first liveCache call, the name of the new system is saved.


Related Articles

0.014 seconds.