Hello Guys,

I'm getting an error in my system when I try to transfer data from ECC to APO system. When I CIF (after generating IM, when I activate it)  older data (master data created previously in system), I'm getting a short dump with mesage class 'XC', It says :

Diagnosis

    An internal condition was found during the

    the system to access a substandard program"

Trigger Location of Runtime Error

    Program                                 SAPLCSER

    Include                                 LCSERU02

    Row                                     101

    Module type                             (FUNCTION)

    Module Name                             CIF_SER_MESSAGE_SERIALIZE.

But when I create a new data and try to transfer it, it smoothly transfers into APO without any dump or error.

Similarly, when I pull the data in APO with CCR, I get short dump while iterating data:

Category               ABAP Programming Error

Runtime Errors         DBIF_RSQL_TABLE_UNKNOWN

ABAP Program           /SAPAPO/SAPLDM_LC_SQL

Application Component  BC-DB-LCA.

The current ABAP program "/SAPAPO/SAPLDM_LC_SQL" had to be terminated because

it has

come across a statement that unfortunately cannot be executed.

A table is referred to in an SAP Open SQL statement that either does not
exist or is unknown to the ABAP Data Dictionary.
The table involved is "/SAPAPO/ORDMAP" or another table accessed in the
statement.

I'm not much aware on LC technology, I have deactivated & activate LC once in LCA10. Also, checked consitency in OM17, it shown no inconsistency. Plus, when checked in OM13, all checks are showing green.

Can you please suggest what needs to be done?

Thanks,

AP.

Hi ,

I have upgraded the live cache to 7.9 from 7.7 and I could see a couple of errors and warnings on it.

1. Log management is set to "off" !!! error - even though the redolog management is activated and LOG WRITER is ON

2. Database analysis in red colur

3. Online without post processing - warning message.

Please help me to resolve the above issues.

Thanks in advance

Dear Experts,

We facing a liveCache error in our System.

Everytime we start in tx DB02 the liveCache error "liveCache lock server not accessible" appears.

I also check transaction LC10 and found a warning that "SQL access not possible"

Here is the Connection Test Log i made:

Application Server:  MDCSAP07_AP1_00                          ( Windows NT )

   1. Connect. test with "dbmcli db_state"                         Successful

   2. Connect. test with command mode "dbmrfc db_state"            Successful

   3. Connect. test with session mode "dbmrfc db_state"            Successful

   4. Connect. test with "native SQL"  ( LCA )                     No connection

      SQL Code:

      Error creating a secondary database connection

      Set up of a secondary connection to the database system failed. It is possible that the data required for setting up the con

      SQL code:

      For detailed information, see the developer trace for work process:           25

Here's the copy of the dev_25:

Thu Jul 25 13:57:46 2013
    OCIAttrSet(con=0, rc ln: 0 31, -1 32, 0 3, 0 8) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48

Thu Jul 25 13:57:49 2013
    OCIAttrSet(con=0, rc ln: 0 20, -1 32, 0 3, 0 8) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 20, -1 32, 0 2, 0 8) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 20, -1 32, 0 2, 0 8) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: -1 37, 0 22, 0 4, 0 10) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_CLIENT_INFO is greater than the maximum allowable length of 64
    OCIAttrSet(con=0, rc ln: -1 37, 0 22, 0 4, 0 10) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_CLIENT_INFO is greater than the maximum allowable length of 64
    OCIAttrSet(con=0, rc ln: -1 37, 0 22, 0 4, 0 10) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_CLIENT_INFO is greater than the maximum allowable length of 64
    OCIAttrSet(con=0, rc ln: -1 37, 0 22, 0 4, 0 10) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_CLIENT_INFO is greater than the maximum allowable length of 64

Thu Jul 25 13:57:50 2013
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48

Thu Jul 25 13:57:51 2013
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48

Thu Jul 25 13:57:54 2013

Thu Jul 25 13:57:54 2013
     OCIAttrSet(con=0, rc ln: 0 20, -1 32, 0 2, 0 8) failed with SQL error 24960:
     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48

Thu Jul 25 13:57:57 2013
     OCIAttrSet(con=0, rc ln: 0 27, -1 32, 0 3, 0 8) failed with SQL error 24960:
     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
  Loading DB library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll' ...
  *** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll")
Error 126 = "The specified module could not be found." [dlnt.c       255]
  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
  *** ERROR => Couldn't load library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll'
[dbcon.c      5672]
  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
  ***LOG BYG=> could not load library for database connection LCA        [dbds         862]
  ***LOG BZY=> unexpected return code 8192       calling DBDS       [dbacds       1536]

Hi

During Release of demand planning to supply network I got run time error :

Category               Installation Errors

Runtime Errors         DBIF_DSQL2_SQL_ERROR

Except.                CX_SY_NATIVE_SQL_ERROR

Date and Time          06.03.2016 23:39:54

Short text

     SQL error 600 occurred when executing Native SQL.

What happened?

     The error 600 occurred in the current database connection "LCA".

     Error Text of Database: "POS(1) Work rolled back: DbpError: DbpError -4004

      errorK"

     SQL Statement Responsible:"EXECUTE PROCEDURE "APS_CUS_ORDER_CHANGE1""

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR', was not

caught in

procedure "/SAPAPO/OM_CUS_ORDER_CHANGE" "(FUNCTION)", nor was it propagated by

a RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

Error Text of the Database: "POS(1) Work rolled back: DbpError: DbpError -4004

errorK"

Please Advise how to solve

Regards

Hello,

Are there any restriction about install Livecache server and SCM on the same server?

The OS is windows.

Regards.

Hello,

We have a SCM 7.0 system with EHP 3 with a liveCache (MaxDB 7.9.08) .

If I click the button "liveCache Monitoring with DBA Cockpit" in the TX LC10, I get the following error for each database connection (LCA, LDA and LEA) :

In the TX SM21 you can see the error message below:

     Database error -10709 at CON

     > Connection failed (RTE:[1] cannot connect to server socket)

Im Trace-File dev_w0 I found the following:

     Connect to LCA as SAPLCD with <IP-Address>-LCD

     Try to connect as SAPLCD/<pwd>@<IP-Address>-LCD on connection 1 ...

     *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:[1] cannot conn

     bmaxsql.cpp 607]

     {root-id=54217256A7094810E1008000AC110048}_{conn-id=00000000000000000000000000000000}_0

     ***LOG BY2=> sql error -10709 performing CON [dbds         919]

     ***LOG BY0=> Connection failed (RTE:[1] cannot connect to server socket) [dbds         919]

I would like to mention, that I have maintained the liveCache Integration as follows:

     Name of Database Connection: LCA (or LDA or LEA)

     liveCache Name: LDA

     liveCache Server: here I tried with the IP-address and also with the physical hostname, but none of them worked

     DBM User:

          User Name: CONTROL

          Password:    xxx

      Standard liveCache User:

          User Name: SAPLCD

          Password:    xxx

Furthermore, I have checked at database-level, the liveCache is up and running and the passwords are correct:

     dbmcli -d LCD -u control,<password> db_state

     OK

     State

     ONLINE

     dbmcli -d LCD -u saplcd,<password>

     dbmcli on LCD>

But in the TX LC10 the buttons "Start liveCache" and "Stop liveCache" are watermarked.

I have already tried to restart the liveCache and the SCM-system, but without success.

In my opinion the cause is, that the liveCache cannot be reached from the SCM-system.

Could you please advise?

Thanks a lot in advance.

Kind regards,

Noémi

Hello Experts,

Whenever i execute LC10, i see 3 DB connections - LCA, LDA and LEA.

I do have some basic questions which i couldnt find answers for:

1. How to find out which DB connection is used in the system - LCA, LDA or LEA.

Or all the three will be used for LC to be functional?

2. If only LCA is used, how to uninstall or remove the connections for others?

Thanks,

Subbu

Hi,

I am seeing below error message in /sapapo/om13 for LC sessions to the liveacache 7.9.

"

There are not enough liveCache sessions.

The number of liveCache sessions should at least be equal to the number
of work processes * 3 + 4.

Maintain the liveCache parameter MAXUSERTASKS.

"

Current the no of wok processes in 372

and LC seesion is 300

How to resolve this issue and how the concept works here..Please help

Thanks in advance

Hi,

We are having abap dumps in APO system related to above DBIF_DSQL2_CONNECTSTR_ERROR

Details:

Runtime Errors         DBIF_DSQL2_CONNECTSTR_ERROR

ABAP Program           CL_RSDRS_SQL_QUERY============CP

Application Component  BW-BEX-OT

Short Text

    The connection identifier is not known.

What happened?

    The connection identifier points to data in table DBCON that is

    required to create a database connection for multiconnect. No entry has

    been defined with key " " however.

Error analysis

    Triggering ABAP statement: Connect to " "

This is affecting /SAPAPO/* loads, I believe this is related to livecache, but unfortunately the SAPnotes I have checked were all pointing to description of issue "... defined with key "LCA"" or with "LCA", this does not.

Anyone has experience with this issue and resolution?

Thanks

Hi,

we are in the situation where we will move our APO system from an inhouse server, to a server provided by an external vendor.

A question/issue has come up regarding live cache. We are on an old release 4.6 and live cache version 20, according to SAP newest version is 50 and they do not recommend to go lower than version 32.

The idea is to move APO and forget the current live cache and rebuild it with the new version. For transactional data, can this be done by simply transferring data again from connected ERP systems or will we face new problems?

Thanks,

Lars

Hi Experts,

We are planning to do SCM 7.0 EHP2 upgrade from SCM 7.0.

I have few questions regarding upgrade of SCM and Livecache 7.7 to 7.9 .

1. Is it possible to upgrade the SCM alone with out livecache upgrade .Or is it mandatory to upgrade livecache too with SCM upgrade .

2. Whether livecache should be upgraded before or after SCM 7.02 upgrade .

3.how to do Parallel upgrade of SCM and Livecache . things to do for parallel upgrade .

4. Which upgrade is best , Livecache upgrade after SCM upgrade or parallel upgrade of Livecache and SCM.

5.As per upgrade guide there are two method for livecache upgrade one is extract/load & another is inplace upgrade, which one we need to follow.

Please help me to clarify this things .

Thanks

Alok

Hi,

We are testing migration of SCM to SCM on HANA with integrated LiveCache in our lab box & now migrating

external LiveCache to Integrated LiveCahce migration.We have done all the steps upto step 5 as specified in the note 1825703. Not able to validate step number 6. We dont see APS_ORDER_GET_DATA under "Catalog => Public Synonyms" in the SAP HANA Studio and also we dont see role AFL__SYS_AFL_LCAPPS_EXECUTE. The LC installation step number 5 completed successfully without any error. The HANA DB connection (created in step 4) from DBACOCKPIT is working fine LCA,LDA and LEA.

Thanks

Vipin

Hi Expert,

I will be migrating my SCM(APO) system from Oracle to Sybase. The migration will take place on the same server. Currently, the SCM is attached to a Livecache running on MaxDB.

My question is, should I re-install the LiveCache on the new Sybase system? How can I make sure the new Sybase SCM system is connected to the existing LiveCache?

Hope to get ideas and feedback.

Thanks,

SS

Hi community,

I am wondering if it is possible to install and run MaxDB x32 package on a x64 Windows 7 installation? Or at least install the x32 MaxDB ODBC drivers on a x64 machine?

The reason why I am asking is because I want to establish an ADO connection to a MaxDB x64 installation with Embarcadero Delphi XE3.

The problem is that the regarding Visual Component coming with Delphi (TADOConnection) is just able to handle x32 ODBC Data Sources and there seems no way to switch this. Unfortunately I am "forced" to use Delphi XE3 and now I am a little bit stuck. Hope you can help me out here.

Thanks guys!

Dear Experts,

I'm having an error everytime I start liveCache stating "lock Server not accessible"

I also checked the connection LCA in tx LC10. It displays a green light but a warning that says
"SQL access not possible". Same goes with tx DB59, there's an error while performing the test. See details below.

DB59 - Connection test:

General Connection Data
   Connection Name....: LCA
   Database Name......: LC1
   Database Server....: 10.206.110.72
   tp Profiles........: no_longer_used
   DBM User...........: CONTROL

   Test Scope
   1. Execute an external operating system command (DBMCLI)
   2. Determine status using TCP/IP connection SAPDB_DBM (DBMRFC command mode)
   3. Determine status using TCP/IP connection SAPDB_DBM_DAEMON (DBMRFC session mode)
   4. Test the SQL connection (Native SQL at CON_NAME)

Application Server:  MDCSAP07_AP1_00                          ( Windows NT )
   1. Connect. test with "dbmcli db_state"                         Successful
   2. Connect. test with command mode "dbmrfc db_state"            Successful
   3. Connect. test with session mode "dbmrfc db_state"            Successful
   4. Connect. test with "native SQL"  ( LCA )                     No connection
      SQL Code:
      Error creating a secondary database connection
      Set up of a secondary connection to the database system failed. It is possible that the data required for setting up the con
      SQL code:
      For detailed information, see the developer trace for work process:           23

work proccess Dev_23:

B  Loading DB library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll' ...
M  *** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll")
  Error 126 = "The specified module could not be found." [dlnt.c       255]
M  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
B  *** ERROR => Couldn't load library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll'
[dbcon.c      5672]
B  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
B  ***LOG BYG=> could not load library for database connection LCA        [dbds         862]
C     OCIAttrSet(con=0, rc ln: 0 15, -1 32, 0 3, 0 8) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
C
C Thu Jul 25 14:21:53 2013
C     OCIAttrSet(con=0, rc ln: 0 32, -1 32, 0 3, 0 10) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
C     OCIAttrSet(con=0, rc ln: 0 32, -1 32, 0 4, 0 10) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
C
C Thu Jul 25 14:22:45 2013
C     OCIAttrSet(con=0, rc ln: 0 20, -1 32, 0 3, 0 8) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
C
C Thu Jul 25 14:22:49 2013
C     OCIAttrSet(con=0, rc ln: 0 27, -1 32, 0 3, 0 8) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
B  Loading DB library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll' ...
M  *** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll")
  Error 126 = "The specified module could not be found." [dlnt.c       255]
M  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
B  *** ERROR => Couldn't load library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll'
[dbcon.c      5672]
B  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
B  ***LOG BYG=> could not load library for database connection LCA        [dbds         862]
B  ***LOG BZY=> unexpected return code 8192       calling DBDS       [dbacds       1536]
C
C Thu Jul 25 14:22:50 2013
C     OCIAttrSet(con=0, rc ln: 0 32, -1 32, 0 2, 0 10) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48

I am trying to perform the SAP SCM migration from AnyDB to HANA DB.

During the import configuration I get the below error popup.

"AFL__SYS_AFL_LCAPPS_EXECUTE , AFL Role does not exist. This role is automatically created during the installation of SAP liveCache Applications (SAP LCA). Proceed with the installation of SAP liveCache Applications following the description in the guide 'Installation and Upgrade Information SAP HANA Installation Guide with Unified Installer', chapter 'Installing SAP liveCache Applications (SAP LCA) on a SAP HANA System'. This guide is available on SAP Service Marketplace at http://help.sap.com/hana_appliance,under 'Installation and Upgrade Information SAP HANA Installation Guide with Unified Installer'. "

I have deployed the LCAPP LiveCache component as described in the SAP HANA GUIDE " SAP HANA Update and Configuration Guide"

Steps :

1. 1.Open the SAP HANA lifecycle manager user interface.
2. 2.Choose Add LiveCache Applications (LCApps).
3. 3.Specify the required entries by following the instructions in the wizard.

I am unable to overcome this issue and go ahead with the integrated LiveCache scenario.

Current HANA DB Version : 1,0 SP06 Rev 66

LCAPP component deployed  : IMDB_LCAPPS100_70_1-20010426

Kindly let me know how i could resolve this issue and proceed with the system migration.

Hi Friends,

Could anyone send me DBMCLI commands for regular usage.

Regards

suresh

Hi Experts,

I am facing an issue with Live Cache connection to SCM system. In DB59, when I am doing connection test for LCA, I am getting following output:

Application Server:  atldapr_DAP_03                           ( HP-UX      )                                 

   1. Connect. test with "dbmcli db_state"                         Successful                                

   2. Connect. test with command mode "dbmrfc db_state"            Successful                                

   3. Connect. test with session mode "dbmrfc db_state"            Successful                                

   4. Connect. test with "native SQL"  ( LCA )                     No connection                             

      For detailed information, see the developer trace for work process:           1                        

The developer trace of work process 1 dev_w1 has following entries regarding this error:

B Fri Jan  4 07:42:48 2013                                                                                  

B  Connect to LCA as SAPR3 with atldalr-DAL                                                                 

C  INFO : SQLOPT (set by environment) =                                                                     

C  INFO : SQLOPT= -I 0 -t 0 -F SAPDB.9529.pct                                                               

C  Precompiler Runtime : C-PreComp 7.4.3    Build 042-122-121-563                                           

C  Precompiler runtime is SAP DB 7.4.3.042                                                                  

C  Try to connect as SAPR3/<pwd>@atldalr-DAL on connection 1 ...                                            

C  *** ERROR => CONNECT failed : sqlcode=-807 (Connection down, session released (protocol error))          

[dbadautl.c   311]                                                                                         

B  ***LOG BY2=> sql error -807       performing CON        [dbds#4 @ 1056] [dbds    1056 ]                  

B  ***LOG BY0=> Connection down, session released (protocol error) [dbds#4 @ 1056] [dbds    1056 ]         

Please help.

Regards,

Sharad

Hi All,

We have recently installed SAP APO 7.0 system with LiveCache 7.7.07.

Please provide your suggestion for below queries -

1) OMS Data and Data Cache hit ratio was 90% in my LiveCache so we have increased Cache Memory Size(10GB now) and OMS Max Heap Size( 8 GB ).

but now my worry is what other parameters we should consider for good performance in Live Cache System as we have not done any parameter tuning after LiveCache install and it is running on default values of installation.

2) We also see several time Data loading jobs get fail due to lock entry in Live Cache and that lock does not get release till we restart Live Cache Application, Please suggest can we set any paremeter (RequestTimeout parameter is 180 Sec now) or do we have any place like SM12 in ABAP system from where we can remove these Live Cache locks. Under LC10->SQL and OMS lock, We do not see any lock that time.

Please provide your input.

Thanks in Advance.

Shivam

Hi Experts,

Can anyone please tell me how to use live cache in Ms Sql Database....Is it possible to use live cache in Ms sql if so, It will be very helpful for me if you send any documents or links.

Thanks in advance...

Regards,
Krishna.M