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 experts,

I am trying to take a complete backup of one of my livecache database from DBA planning calender. It is failing with below error.

MEDIANAME 'Pre_index_rebuild'
*** SAVE/RESTORE request accepted:
OK 

*** SAVE/RESTORE result:
ERR
-24988,ERR_SQL: SQL error
-903,Host file I/O error
3,Data backup failed
113,Open medium on /sapdb/LCA/sapdata/DISKD0006 for READ failed
1,Open file /sapdb/LCA/sapdata/DISKD0006 failed, open(READ,EXISTING) returned 'Too many open files' (24)

*** SAVE/RESTORE request:
SAVE DATA CANCEL
*** SAVE/RESTORE request accepted:
OK

*** SAVE/RESTORE result:
ERR
-24988,ERR_SQL: SQL error
-104,DBM command impossible at this time

*** DBA Action ends:
Timestamp: 20150829225656   State

I have tried by creating new media template but the result is same. I am not able to find much useful logs in livecache log files. Please suggest.

Thanks

Amar.

Hi Experts,

We are planning to refresh one of our old test SCM system with production data. Versions are as below.

Target SCM - SCM 7 EHP2. Target LC - 7.7.07

Source SCM - SCM 7 EHP3. Source LC - 7.9.21

For SCM version part I think target will automatically get the source version after ABAP system refresh. But for LC according to note 457425 versions should be same on source & target. I am planning to install LC 7.9 on target server then upgrade patch to 7.9.21 & then restore the backup from production.

So if i follow this course of action still do I need to follow the step1 'Select the menu option Instance -> Install' from DBMGUI or I can directly go to backup restore from production.

Also I am taking a complete LC backup from production using db studio. So I think I need to restore it again using DB studio only. Note 457425 is giving steps for DBMGUI so can I get the simillar steps for dbstudio anywhere?

I am taking a complete backup of production. So is there any specific requirement while taking a backup for LC refresh to restore on other system than the same database.

Kindly let me know if you have any inputs on these queries as I am bit confused at this point for this refresh activity

Thanks

Amar.

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

Dear all,

We have SCM system since years. However, during recent discussion we realized that the mechanism for data saving from caches to data files on the disk is not very clear.

Could you please advise how the data from are stored on the disk? Is this periodically or it is permanently, asynchronous or any other way...?

Or it is one time during the system shutdown, but it seems to be not is not very logical because if there is a system hang up - the data will be lost.

Thank you in advance for your suggestions.

Best regards,

Detelin Nedev

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]

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

Dear Livecache Experts,

Need some expert advice regarding the SCM+Live cache Hetrogenous Migration.

We are planning to migration our SCM+Live cache from AIX to Linux. As this is Os Migration, we have refered the SAP note: 632357. Which Gives step by step information how to migrate the livecache.

Now the problem is that our livecache database size is 70GB and if we go as per the SAP note of migrating the data from live cache to Oracle master table. We don't know how much time it will take and we have very short downtime to do this migration. Is there any option to make this live cache migration from Live cache database to Oracle faster in source system and then target system migrate data from Oracle master table to Live cache database.

OR

I have heard we can install the fresh live cache without old database and whereas after making SCM system migration and not live cache ( Install fresh live cache), after some days again the data will get populated in live cache database ( CAN IT BE POSSIBLE, IT WILL SAVE OUR TIME OF MIGRATION). In such case we need to do only migration of SCM database and not Live Cache.

Regards,

Anil Bhandary

Hello World,

we just finished LC Upgrade phase of Step "Execution" during the upgrade of our APO+LC system (Target release: EHP3 FOR SAP SCM 7.0).

When compared with the (already successfully upgraded) Test system, all components (DB & SAP kernel, SAP Module Versions) match, and the SUM logs show no errors.

Yet when we try to rebuild the LC, by executing the ABAP report "/SAPAPO/OM_LC_UPGRADE_70", it gets stuck in step C3->Load Master Data.

If started, this action goes on forever, w/o ever finishing.

The DB fill level ever so slowly creeps up to ~5.2% (we had %50 freespace in the LC before the upgrade), and then nothing more happens.

We can see a WP being busy with *MATGEN* Jobs in SM50, but when checked that WP hardly writes anything to the DB (with roughly 125000 reads thus far).

There are no error entries in the WP trace files, and the LC database works just fine (version 7.9.08.16).

SAP Support (as unfortunately to be expected these days), has proven next to useless thus far.

They didn't even know how to use AL11 to review log files on their own (we did open up the service connection, yet they still demanded we send them those log files by mail)

This is our production box and Monday is approaching, so what to do nail down the root cause and fix it?

Thx in advance for any help

Hi ALL,
we have completed system Refresh & post - Activities now we are testing my system, while test mode my APO consultant facing an error,

while testing he tried different T-Codes and he received runtime error “DBIF_DSQL2_SQL_ERROR”.

The liveCache is NOT working and giving runtime errors.

Regards but when i cheked consistancy checck connection is ok

(livecache monitor and connectivity and server test connection)

can u please reply why iam facing this shot dumps

dump

Runtime Errors         DBIF_DSQL2_SQL_ERROR
Exception              CX_SY_NATIVE_SQL_ERROR
Date and Time          04/20/2012 19:08:30

Short text
     An SQL error occurred when executing Native SQL.

What happened?
     The error 600 occurred in the current database connection "LCA"

What can you do?
     Note down which actions and inputs caused the error.

     To process the problem further, contact you SAP system
     administrator.

     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.

How to correct the error
    Database error text........: "POS(1) Work rolled back: tExcept 30708 in
     APS_PLEN_RERS_"
    Database error code........: 600
    Triggering SQL statement...: "EXECUTE PROCEDURE "APS_PLEN_RERS_GET_ALL""
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).

    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:

    "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
    "/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU17"
    "/SAPAPO/OM_PLEN_RERS_GET_ALL"

    If you cannot solve the problem yourself and want to send an error

Hello,

we already test-migrated a SCM 7.0 including Livecache data with changing the platform from HPUX/Oracle to Windows/MSSQL.

LC data have been saved using report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD in the source system then LC has been installed on the target system and LC data then uploaded in the target system using /SAPAPO/OM_LC_DOWNLOAD_UPLOAD again.

Now we want to re-run the migration for cutover test and my question is whether it's possible to skip the new installation of the LC

and just upload the data after migration of SCM database into existing LC starting in section C of /SAPAPO/OM_LC_DOWNLOAD_UPLOAD at this point. Does LC initialization in step C2 do all the necessary cleanup steps in order to upload new data into existing LC again ?

Looking forward to your answers.

Thanks,

  Juergen

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

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

Hi,

I had restored the data of livecache version 7.7.07.45 on live cache system 7.7.07.40.

Even though the successful restore message, the target system livecache 7.7.07.40 is not coming up online.

An error occurred during the recovery.

-9407 system error ; unexpected error 3, Database state OFFLINE internal error code 6433 system error 20017,Restart File system with system error 20000 Assertion of state The software version is too old failed. The persistent version is 7.7.07.45.

The recovery was successfully completed.

If I upgrade the live cache to 7.9 , will it come up online..What could be the possible solution now to bring up the live cache.

Any help is much appreciated.

Thanks in advance

Hi ,

Please let me know the live cache log files and location of the same.

I would need them to analyze livecache issues during the upgrade and startup/performance related problems.

any help is much appreciated.

Thanks in advance

Hello Experts,

We have plan to Migrate of SCM DB2 DB from AIX to RHEL7.

Our LiveCache LC is on SUSE Linux & will not migrate to RHEL7 as per current design unless, otherwise this combination is not supported ( Exploring more on supportability aspects).

I have below questions:(based on assumptions that LC will not be migrated)

1 - Only exporting & importing SCM DB is sufficient? If Yes, can someone outline LC related steps that I still need to perform in this      scenario.?

2 - Since I am assuming here that LC will not be migrated do I still need to runreport /SAPAPO/OM_LC_DOWNLOAD_UPLOAD            before & after SCM DB Migration to download & upload LC Objects to & from SCM DB respectively?

3 - I am checking on PAM & with SAP, meanwhile if someone already know -  Is below combination of Target is supported ?:

SAP SCM application -- SUSE Linux

SCM DB2 DB -- RHEL7.1

SCM LC - SUSE Linux

Best Regards

Sachin

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,

A newbie question. I'm getting the following error when starting livecache. Please help

more lcinit.log

************************ START *****************************

liveCache SID (restart)

25.11.2015

03:41

------------------------------------------------------------

Installation path is /sapdb/SID/db

Operating system is SunOS

The liveCache state is OFFLINE

DBMServer 7.7.07   Build 045-123-247-303

Starting SID into ADMIN

Starting SID into ONLINE

Creating liveCache application procedures

ERR

-24964,ERR_EXECUTE: error in program execution

65280,/sapdb/SID/db/bin/sdbsysload -R /sapdb/SID/db -d SID -u superdba,*

 

 

----------Command----------------

USE USER superdba *  SERVERDB "SID"

-----------Error-----------------

ERR

-25005

User (SUPERDBA) logon to database SID failed: SQL error -4008 = Unknown user name/password combination (error position: 1)

 

 

---------------------------------

 

 

MaxDB Installer Runtime Error:

perl runtime error:

Can't call method "loaderCmd" on an undefined value at installib.pm line 574.

ERROR : liveCache SID not started

------------------------------------------------------------

25.11.2015

03:42

************************* END ******************************

Hi SCN.

We have a bemusing issue with a SCM 7.1 system migration.

As part of this migration between OS platforms we are downloading the liveCache into ORACLE pre-migration and then uploading back into a new liveCache instance on the target.

This is all done using SAP standard program /SAPAPO/OM_LC_DOWNLOAD_UPLOAD

For those who know this program it's split into 3 sections

A) Essentially prep and consistency checks - clearing out any old downloads

B) Download liveCache data in into ORACLE (or other rdbms)

C) Upload (re-initialise liveCache and upload data back into it)

However despite confirming in Section B on the source (section 5) that there is a confirmed download of data, once we get to the target, post-migration, we find that when we re-run this program it doesn't seem to think there is any data download available (i.e. Section B: 5 has turned red).

Now I've run this for other migrations and the download was still visible post migration.

Has anyone seen similar issues?

What would also be very useful would be if anyone knows what ORACLE level tables the download would be stored in so that we can check source & target databases to ensure the OS/DB migration included these in the mig process

Hi,

During SAP ECC6.0 installation(We are doing import) i am getting error at phase 11 of 27 for MaxDB database instance creation.

I am using RDBMS_MAXDB_7.7.04_Build_28 on HP-UX 11i V3 (11.31) Itanium blade server.

I tried finding knldiag but unable to find on the system.

ERR

-24994,ERR_RTE: Runtime environment error

20089,Check knldiag! Kernel died before reaching ADMIN state

Please let me know how to resolve this problem.

Thanks,

Narendra