After migrating APO dev from one server to another LiveCache broke

[Former Member]

LiveCache and Oracle are on a DB server and SAP on another.

After migratng SAP from one server to a new one - LiveCache won't work.

In LC10 I get "SQL access not possible"

Version of LC: 7.7.04.28 running on HP-UX 11.31 IA64.

The LiveCache name and server did NOT change.

I can start / stop it from Administration -> operating

In syslog, is get:

Connect to the database with ID LCA failed

If I run /n/sapapo/om13 I get:

Runtime Errors DBIF_DSQL2_CONNECTERR

Except. CX_SY_NATIVE_SQL_ERROR

Thanks...Geoff

[Former Member]

Re-runing /SAPAPO/DELETE_LC_ANCHORS - it seems to have fixed our issue.

User was able to do the planning step.

[former_member229109]

-> Please read the SAP note !!!!!!

640107 Using program /sapapo/delete_lc_anchors in APO 3.0 or higher

-> "Program /sapapo/delete_lc_anchors deletes the contents of the anchor

tables for transaction data (production orders, purchase orders, sales

orders) and then loads all master data (resources, calendars, setup

matrices, peg areas and so on) into the liveCache.

Immediately before you execute program /sapapo/delete_lc_anchors,

initialize the liveCache. This ensures that the liveCache does not

contain any requests. (If orders are stored in the liveCache, you could

not establish a consistent status after /sapapo/delete_lc_anchors is

run. Then there would be orders which are in the liveCache, but which

are not stored in the APO database.

We therefore recommend that you use transaction LC10 because it automatically calls the /sapapo/delete_lc_anchors program immediately after the liveCache was initialized. (Program /sapapo/delete_lc_anchors does not initialize the liveCache !!) " .....

[Former Member]

Thanks for the answers so far - but it is none of those...

I went into st11 and looked at work process dev_w0 and saw the following:

B ***LOG BYI=> connect failed for connection LCA [dbds#1 @ 1052] [dbds 1052 ]

B Connect to LCA as SAPVLC with PC1012-VLC

C *** ERROR => Couldn't connect with 'SAPVLC/<pwd>@PC1012-VLC'

[dbsdbutl.cpp 757]

**C *** ERROR => Max. number of open SAP DB connections (32) exceeded**

*[dbsdbutl.cpp 758]*

C The following sessions are already connected :

C 01: -, since=20090309144526, ABAP= SAPLSADB (11801)

C 02: -, since=20090309144527, ABAP= SAPLSADX (585)

C 03: -, since=20090309144527, ABAP= SAPLSADD (97998)

C 04: -, since=20090309144543, ABAP= SAPLSADB (11801)

C 05: -, since=20090309144644, ABAP= SAPLSADB (11801)

C 06: -, since=20090309144811, ABAP= SAPLSADB (11801)

C 07: -, since=20090309144812, ABAP= SAPLSADX (585)

C 08: -, since=20090309144812, ABAP= SAPLSADD (97998)

C 09: -, since=20090309145130, ABAP= SAPLSADB (11801)

C 10: -, since=20090309145130, ABAP= SAPLSADX (585)

C 11: -, since=20090309145130, ABAP= SAPLSADD (97998)

C 12: -, since=20090309145218, ABAP= /SAPAPO/SAPLOM_CORE (4763)

C 13: -, since=20090309145321, ABAP= SAPLSADB (11801)

C 14: -, since=20090309145537, ABAP= SAPLSADB (11801)

C 15: -, since=20090309145537, ABAP= SAPLSADX (585)

C 16: -, since=20090309145537, ABAP= SAPLSADD (97998)

C 17: -, since=20090309145750, ABAP= SAPLSADB (11801)

C 18: -, since=20090309145754, ABAP= SAPLSADB (11801)

C 19: -, since=20090309145759, ABAP= SAPLSADB (11801)

C 20: -, since=20090309145806, ABAP= SAPLSADB (11801)

C 21: -, since=20090309145809, ABAP= SAPLSADB (11801)

C 22: -, since=20090309150547, ABAP= SAPLSLCA (11168)

C 23: -, since=20090309151533, ABAP= SAPLSADB (11801)

C 24: -, since=20090309151533, ABAP= SAPLSADX (585)

C 25: -, since=20090309151533, ABAP= SAPLSADD (97998)

C 26: -, since=20090309152935, ABAP= SAPLSADB (11801)

C 27: -, since=20090309153149, ABAP= SAPLSADB (5446)

C 28: -, since=20090309153339, ABAP= SAPLSADB (11801)

C 29: -, since=20090309153339, ABAP= SAPLSADX (585)

C 30: -, since=20090309153339, ABAP= SAPLSADD (97998)

C 31: -, since=20090309153935, ABAP= SAPLSADB (11801)

B ***LOG BYI=> connect failed for connection LCA [dbds#1 @ 1052] [dbds 1052 ]

Looks like LiveCache isn't releasing connections and/or we need to increase the max amount????

[former_member229109]

Hello Geoffrey Wild,

-> What note or document you used to run the system copy steps?

-> Did you run you run Homogenous system copy?

-> Please post the output of the following commands running on the liveCache server PC1012:

x_cons VLC show active

-> What is the name of the target liveCache instance? Is it VLC on PC1012?

-> Connect to the liveCache using DBMGUI & check if you have the LOG_FULL or DB_FULL issues.

-> Please take a look at the SAP notes 577991 and 833216 < MAXUSERTASKS>. The APO workprocess could not open more than 3 connections to liveCache.

-> Check if you have the WPs are opening more as 3 connections : go to LC10, Tools , dbmcli and execute:

sql_execute SELECT APPL_PROCESS APPL_PID, COUNT(*) NUM_CONNECTIONS FROM

SYSMON_TASK_DETAIL WHERE APPL_PROCESS > 0 GROUP BY APPL_PROCESS HAVING

count(*) > 3

If you will see a list of the application processes and the # of open connections to liveCache more as 3

==>

Need to check what application opened those connections.

The SAP Note 764359 explains that the solution is to execute a COMMIT WORK before and after the ABAP command SUBMIT, for example.

-> It will be helpful to login to your system & check the status of the issue via OSS. As SAP customer you have the option to create the OSS ticket on this issue, we could login to the system to review the problem & discuss the issue in

more details.

Thank you and best regards, Natalia Khlopina

[Former Member]

We didn't do a "system copy" - we physically moved the SCM from one Unix server to another.

The DB and LC servers stayed the same.

We have re-installed the MAXDB client.

We have just recycled APO and are monitoring - so far we don't have the SQL error nor out of connections...

Even when we were out of connections - in MAXDB it said we were only using 6 out of 60.

Why SAP said "Max. number of open SAP DB connections (32) exceeded" is unknown...

Currently user tried to test but got:

Error in COM routine usining application program (return code 40.134).

Rgds...Geoff

[former_member229109]

"Currently user tried to test but got:

Error in COM routine usining application program (return code 40.134)."

COM error :: 40134 Key figure does not exist

"Key figure does not exist":

Message no. /SAPAPO/OM_TS134

Diagnosis::

A key figure operation tried, via a key figure anchor,

to dereference a key figure object that does not exist in the liveCache.

This problem is due to master data inconsistency in the application.

==>>

Open an OSS message in accordance with SAP Note 167280.

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi,

Please check whether your X_Server is running - withour which you wont be able to access the maxdb/liveCache database from your SAP Server. Details below:

http://help.sap.com/saphelp_nw70/helpdata/en/1e/6e424089ff2571e10000000a155106/frameset.htm

- Regards, Dibya

[former_member229109]

Hello Geoffrey Wild,

->As SAP customer you have the option to create the OSS ticket on this issue,

we could login to the system to review the problem & discuss the issue in

more details.

-> What note or document you used to run the system copy steps?

-> If you run Homogenous liveCache copy procedure, please check if you follow the notes:

77203 Post steps after the Homogenous liveCache copy usi

886103 System Landscape Copy for SAP SCM

-> Check the errors in the system log /nsm21 & corresponding dev log.

Thank you and best regards, Natalia Khlopina