Solution Manager 4.0 SR1 install stops at phase 34

Hi
Installing a Solution Manager 4.0 SR1 ABAP+Java central system and have used the new patch 75 kernel 700 DVD from SR2 shipment. O/S version is V5R4.
The server also has another SM 4.0 installed system that is defined as the SLD (system landscape directory), and an ECC 6.0 SR2 DEV system (both also ABAP+Java central systems).  JDBC driver is the Toolbox driver.
It stops at phase 34, and a retry does not succeed; also tried cancel, then shutdown of TMKSVR00 subsystem, deleted TMKSVR00 library, reload TMKSVR, restart sapinst.exe and continue install. This also fails at the same step.
Here is the error.  Waiting the SAP response still - they think it is to do with the following :
" The Scheduler consists of two parts: one is the Ejb and the other is a
Library.
The Ejb is the component 'tc/webadministrator/scheduler/ejb' on which
your deployment fails and the Library is in the component
'tc/webadministrator/solmandiag' where the Scheduler class is stored.
The error you currently get would mean that the installer tries to
deploy the Ejb before the Library breaking the deployment dependency"
The log file has:
ERROR
CJS-30156 SDM deployment failed for at least one of the components to
deploy.<br> SOLUTION:
Check 'X:\usr\sap/SAPinst/SOLMAN/SYSTEM/DB4/CENTRAL/AS/callSdmViaSapinst.log' for more information.
ERROR
FCO-00011 The step enableUsageTypes with step key
|NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|4|0|enableUsageTypes was executed with status ERROR
The log file has:
Jan 30, 2007 11:19:52... Info: End of log messages of the target system.
Jan 30, 2007 11:19:52... Info: ***** End of SAP J2EE Engine Deployment
(J2EE Application) *****
Jan 30, 2007 11:19:52... Error: Aborted: development
component 'tc/webadministrator/scheduler/ejb'/'sap.com'/'SAP
AG'/'7.0008.20060624010338.0000', grouped by software component 'LM-
SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.8.0.20060702013900':
Caught exception during application deployment from SAP J2EE Engine's
deploy service:
java.rmi.RemoteException: Cannot deploy application
sap.com/tcwebadministratorscheduler~ejb..
Reason: Exception during generation of components of application
sap.com/tcwebadministratorscheduler~ejb in container EJBContainer.;
nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException:
Exception during generation of components of application
sap.com/tcwebadministratorscheduler~ejb in container EJBContainer.
regards
Michael.

- Had to restart SMP system as the sapinst script would not do this on restart, then wait till the SERVER0 was Running - i.e. could login to http://<server>:50300 for instance 03 (Java/ABAP).  Then it went through phase 34 and completed successfully.

Similar Messages

  • Solution Manager 3.2 SR1 Install Problem

    Hello everybody,
    I'm having a hard time trying to install SAP SolMan 3.2 SR1 on Windows Server 2003 x86_64 with Oracle 10.2.
    I have installed the OS and Oracle 10.2.
    When I start the installation of CI of SolMan after couple of screens it gives me the error:
    CJS-00030  Assertion failed: No db client software version available in tORA_ClientVersion for client type AMD64
    I have searched for days google and other forums and couldn't find an answer.
    Any help would be very much appreciated.
    Thanks in advance.

    Hi Stanislav,
    The current Oracle 10.2.0.2 is at level patch-14 ( http://service.sap.com/swcenter-3pmain). So, that patch (10202_Patch14_MSWINX86-64.zip ) should be fine,
    Also there you will have Oracle Install client  OCL10264.SAR.
    But, I'm now thinking of the point Markus mentioned earlier about compatibity in 6.40 kernel and Oracle 10g. You might have a look at note 949116.
    In that case it might be you will have to go for SolMan 4.0 (based on WAS 7.00). If you are only using ABAP stack (no Solution Manager Diagnostics), they must be almost same.
    Cheers !!
    Satya.

  • Solution Manager 4.0 SR1 on iseries - Error on step CallOfflineCTC

    I'm installing a Solution Manager 4.0 SR1 on iseries using SAPinst/TMKSRV from Windows XP client.
    In the step Configure UME the installation stopped. As describe in SAP note 927734 I changed the control.xml in the SAPinst directory with the control.xml attached in this note.
    So, the installation continue with success.
    Then, in the phase 40 of 40 (the LAST!!!!), "Prepare to install minimal configuration", the installation stopped with the following error messages:
    <b>sapinst.log</b>
    Execution of the command "\usr\sap\S22\DVEBMGS08\j2ee\ctc\LaunchOfflinectc.sh" finished with return code 127. Output:
    /usr/sap/S22/DVEBMGS08/j2ee/ctc/LaunchOfflinectc.sh: 001-0014 Comando Z:/QIBM/ProdData/Java400/jdk14/bin/java non trovato.
    ERROR 2007-05-11 17:35:21
    CJS-00030  Assertion failed: in
    function NW_Call_Offline_CTC_ind_ind_ind_ind_SubComponentContainer_callOfflineCTC() {
        var nw = NWInstall.getSystem(context.get("sid"));
        var ctcDirFs = nw.getCI().getInstanceDir().concat("j2ee", "ctc");
        var ctcExeFile = installer.onWindows() ? "LaunchOfflinectc.bat" : "LaunchOfflinectc.sh";
        var ctcCall = ctcDirFs.concat(ctcExeFile);
        installer.writeTrace("CTC is in" + ctcCall);
        ASSERT(arguments.callee, ctcCall.isExisting(), "CTC executable cannot be found in " + ctcCall.toString());
        if (installer.onOS400()) {
            var ctcCallFile = ctcCall.getNode();
            ctcCallFile.saveVersion();
            var ctcCallStream = ctcCallFile.getFileStream("READ");
            var ctcCallStreamNew = new StringStream();
            ctcCallStreamNew.copy(ctcCallStream);
            ctcCallStream.close();
            ctcCallStream = ctcCallFile.getFileStream("TRUNCATE");
            for (var it = ctcCallStreamNew.getIterator(); !it.isDone(); it.next()) {
                ctcCallStream.putLine(it.get().replace(/\/bin\/csh/g, "/bin/sh"));
            ctcCallStream.close();
            ctcCallStreamNew.close();
        var pmgt = new ProcessMgt();
        var app = pmgt.createChildApplication(ctcCall, []);
        var userData = nw.getUsers().getAccountData(NWUsers.roles.SIDAdm);
        var user = (new AccountMgt()).getUser(userData.name);
        var env = pmgt.getProcessEnvironment();
        if (installer.onUnix()) {
            env.setUser(user);
        env.setWorkingDirectory(ctcDirFs.getNode());
        env.setEnvironmentVariable(new Property("JAVA_HOME", nw.getJavaHome().toString()));
        installer.writeTrace("For the Offline CTC Call, JAVA_HOME is set to " + env.getEnvironmentVariable("JAVA_HOME"));
        app.setEnvironment(env);
        var retval = app.run([], true);
        ASSERT(arguments.callee, retval == 0, "CTC retval is not 0 but " + retval);
        installer.writeTrace("CTC has been called in Offline Mode.");
    CTC retval is not 0 but 127
    ERROR 2007-05-11 17:35:21
    MUT-03025  Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
    ERROR 2007-05-11 17:35:21
    FCO-00011  The step callOfflineCTC with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0|callOfflineCTC was executed with status ERROR .
    <b>LaunchOfflinectc.sh.log</b>
    /usr/sap/S22/DVEBMGS08/j2ee/ctc/LaunchOfflinectc.sh: 001-0014 Command Z:/QIBM/ProdData/Java400/jdk14/bin/java not found.
    "Z:" is the drive letter in the client Microsoft XP that mapped the root on the iseries.
    The JAVA_HOME enviroment in the client Microsoft XP where I run the SAPINST is "C:\Programmi\Java\j2re1.4.2_03"
    Can you please help me to solve the problem??
    Thanks in advanced.
    Moreno

    The following Note is verey usfull to solve this issue.
    Note:1094628
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1094628&nlang=EN&smpsrv=https%3a%2f%2fwebsmp210%2esap-ag%2ede
    Best Regard

  • Solution Manager 4.0 SR1 installation error

    Hi there,
    I am getting eblow error for Solution Manager 4.0 SR1 installation on aix-ora.
    Any help much appreciated. Thanks.
    Regards
    Anil
    INFO       2008-05-19 14:15:56 [syuxccuren.cpp:119]
               CSyCurrentProcessEnvironmentImpl::removeEnvironmentVariable
    Removed environment variable SAPDATA_HOME from current process environment.
    INFO       2008-05-19 14:15:58 [iaxxgenimp.cpp:630]
               showDialog()
    Execute step PrepareOraCreateTablespace of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0.
    ERROR      2008-05-19 14:15:59 [iaxxejsbas.cpp:178]
               EJS_ErrorReporter
    FJS-00003  TypeError: sapdataNodeInfo[idx] has no properties (in script NW_Onehost|ind|ind|ind|ind, line 51567: ???)
    ERROR      2008-05-19 14:15:59 [iaxxgenimp.cpp:728]
               showDialog()
    FCO-00011  The step PrepareOraCreateTablespace with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|PrepareOraCreateTablespace was executed with status ERROR .

    Why not use SR3 release? It contains MANY more fixes and will prevent you from the need of installing a bunch of support packages after your installation...
    For your error: please check ora_sql_result.log
    Markus

  • SAP EHP1 for Solution Manager 7.0 - Post Install Procedure

    Hello Folks:
    I completed Sol Manager 7.0 EHP1 installation on Win 2008 R2 with MS SQL in a sandbox environment. This is the first time I ever installed SAP on my own and i am in the process of performing post installation steps from Installation Guide.
    In the install guide, there is no mention of creating a new client ex: 100. Could you please, provide a list of tasks that generally needed to perform after the installation is completed and before doing any configuration in Solution manager.
    I have some very basic idea on the Basis but while going thru Installation Guide I am not sure if there any steps that generally need to perform to complete the installation.  My goal is to complete the Sol Mgr installation first and then start preparing for ECC 6.0 Installation.
    Thanks a lot in Advance.

    Hi,
    First - the basic post installation steps are:
    1. sick t-code need to execute
    2. se06 --> Perform Post-Installation Actions
    3. RZ10 --> Utilities --> Import profiles --> Of active servers
    4. execute sgen T-code --> This will take some time
    5. setup STMS
    6. create client (If custom required)
    7. Take backup of the system
    For the solution manager client you could use the default created '001' client.
    Next you need to run the solman_setup template which 'sets up' the SolMan for usage.
    Follow config guide at: https://service.sap.com/~sapidb/011000358700000308502009E.PDF
    For installing the ECC system, only a install key(from SMSY) is to be generated from SolMan. But if you want to use the SolMan effectively, suggest you to run the entire solman_setup.
    Regards,
    Srikishan

  • Solution manager configuration for EHP4 install (Product Version Problem)

    Hi guys!
    I'm new on SAP and SDN is a help all days and this time i really need some help from you guys!
    Im installing EHP 4 and need the XML Stack file, so i go to the solution manager to generating them. But after configuring the logical components, make the associations, etc. on create maintenence transaction, the product version dropdownlist is empty...
    It is configured but it dont appears... Anyone had this problem before and could give me some help!
    I will appreciate that!
    My regards,

    Hi,
    In SMSY, the system should have product version as SAP ERP 6.0.
    Next the logical component created for ECC Server should also reflect this version.
    The solution you create in DWSP should include this logical component via the Solution Landscape definition. Here again the logical component should show the product version.
    If all above are in place, the MOPZ for the respective solution should have the product version list populated.
    Regards,
    Srikishan

  • Solution Manager key error when installing ECC6

    hi
    Iam installing ECC6 abap+java and facing a problem with the solution manager generated key.Each time iam putting in the key its says its the wrong one.
    i dont know where iam making a mistake.i managed to generate one before when upgarding to ECC6 and it work withou any problems.
    am i making a mistake somewhere?
    help appreciated

    Hi,
    Let me know your SID, Instance No, and Host name. Also write what SOLMAN Key you have entered. I can cross-check that is correct or not.
    Rgds,
    Mahesh Bansal

  • Is Solution Manager necessary for 2004S install?

    We are wanting to install this on a sandbox.  Do we have to install Solution Manager first or is this only related to the license key for the 2004S portal?
    Thanks

    Hi
    You need Solution Manager for the key as you mentioned.
    On the operation site it is recommended to have solution manager and especially diagnostics when using WebAS Java components like i.e. portal. SM Diagnostics comes with a good set of tools for root-cause-analysis and SAP support will also used them.
    On the implementation site I do not think that you absoultly need SM, but I think that tools in SM will help you speed up the implementation. But here an implementation consultant should answer!
    BR
    Tom Bo

  • NW04S SR1 installation stops in phase 26 - import MAXDB statistics

    Dear Forum,
    During the installation of Netweaver 2004S SR1 on a MS Windows Server 2003 64 bit environment, the installation stops in phase 26 - import MAXDB statistics.
    I looked in the XCMDOUT.LOG file and tried to recreate the index.
    I allready updated the database to 7.6.00.34 but this didn't help.
    Please do you have any suggestions,
    Robert Eijpe
    XCMDOUT.LOG
    Execute Command : d:\sapdb\programs\pgm\dbmcli.exe -n knowledge -d KP1 -u control,********
    Execute Session Command : sql_updatestat SAPKP1.*
    ERR
    -24988,ERR_SQL: SQL error
    -9407,System error: unexpected error
    9,Aborting statistics computation due to system error
    42,Error while collecting statistics for table 000000000000060a;  error bad_datapage
    Knldiag.err
    2006-12-06 22:10:47      0x418 ERR 20005 Kernel   Bad page - header and trailer not matching
    2006-12-06 22:10:47      0x418 ERR 20006 Kernel    +   Header [ 65499 - data - tab - checksumData - empty ]
    2006-12-06 22:10:47      0x418 ERR 20007 Kernel    +   Trailer[ 2097184 - data - nil - CHECKTYPE=32 - empty ]
    2006-12-06 22:10:47      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21930
    2006-12-06 22:10:47      0x418 ERR 20008 Data     Bad page - page type 'UNDEF' is invalid
    2006-12-06 22:10:47      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21924
    2006-12-06 22:10:47      0x418 ERR 20008 Data     Bad page - page type 'UNDEF' is invalid
    2006-12-06 22:10:47      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21928
    2006-12-06 22:10:48      0x418 ERR 20008 Data     Bad page - page type 'nil' is invalid
    2006-12-06 22:10:48      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21925
    2006-12-06 22:10:48      0x418 ERR 20008 Data     Bad page - page type 'UNDEF' is invalid
    2006-12-06 22:10:48      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21933
    2006-12-06 22:10:50      0x418 ERR 20005 Kernel   Bad page - header and trailer not matching
    2006-12-06 22:10:50      0x418 ERR 20006 Kernel    +   Header [ 65499 - data - tab - checksumData - empty ]
    2006-12-06 22:10:50      0x418 ERR 20007 Kernel    +   Trailer[ 2097184 - data - nil - CHECKTYPE=32 - empty ]
    2006-12-06 22:10:50      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21930
    2006-12-06 22:10:50      0x418 ERR 20008 Data     Bad page - page type 'UNDEF' is invalid
    2006-12-06 22:10:50      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21924
    2006-12-06 22:10:50      0x418 ERR 20008 Data     Bad page - page type 'UNDEF' is invalid
    2006-12-06 22:10:50      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21928
    2006-12-06 22:10:50      0x418 ERR 20008 Data     Bad page - page type 'nil' is invalid
    2006-12-06 22:10:50      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21925
    2006-12-06 22:10:51      0x418 ERR 20008 Data     Bad page - page type 'UNDEF' is invalid
    2006-12-06 22:10:51      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21933
    2006-12-06 22:10:52      0x418 ERR 20005 Kernel   Bad page - header and trailer not matching
    2006-12-06 22:10:52      0x418 ERR 20006 Kernel    +   Header [ 65499 - data - tab - checksumData - empty ]
    2006-12-06 22:10:52      0x418 ERR 20007 Kernel    +   Trailer[ 2097184 - data - nil - CHECKTYPE=32 - empty ]
    2006-12-06 22:10:52      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21930
    2006-12-06 22:10:52      0x418 ERR 20008 Data     Bad page - page type 'UNDEF' is invalid
    2006-12-06 22:10:52      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21924
    2006-12-06 22:10:52      0x418 ERR 20008 Data     Bad page - page type 'UNDEF' is invalid
    2006-12-06 22:10:52      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21928
    2006-12-06 22:10:52      0x418 ERR 20008 Data     Bad page - page type 'nil' is invalid
    2006-12-06 22:10:52      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21925
    2006-12-06 22:10:53      0x418 ERR 20008 Data     Bad page - page type 'UNDEF' is invalid
    2006-12-06 22:10:53      0x418 ERR 20026 IOMan    Bad page on data volume 1 blockno 21933
    2006-12-06 22:10:54      0x418 ERR 20039 IOMan    Bad data page - Requested pageno 65499 (perm) read pageno 65499
    2006-12-06 22:10:54      0x418 ERR 20020 Data     Bad data page 65499 belongs to root 108930 which is of filetype 'Table'
    2006-12-06 22:10:54      0x418 ERR 20039 IOMan    Bad data page - Requested pageno 139935 (perm) read pageno 2097184
    2006-12-06 22:10:54      0x418 ERR 20020 Data     Bad data page 139935 belongs to root 108930 which is of filetype 'Table'
    2006-12-06 22:10:54      0x418 ERR 20039 IOMan    Bad data page - Requested pageno 95280 (perm) read pageno 140
    2006-12-06 22:10:54      0x418 ERR 20020 Data     Bad data page 95280 belongs to root 108930 which is of filetype 'Table'
    2006-12-06 22:10:54      0x418 ERR 20039 IOMan    Bad data page - Requested pageno 110320 (perm) read pageno 5439489
    2006-12-06 22:10:54      0x418 ERR 20020 Data     Bad data page 110320 belongs to root 108930 which is of filetype 'Table'
    2006-12-06 22:10:55      0x418 ERR 20039 IOMan    Bad data page - Requested pageno 199662 (perm) read pageno 4522079
    2006-12-06 22:10:55      0x418 ERR 20020 Data     Bad data page 199662 belongs to root 108930 which is of filetype 'Table'
    2006-12-06 22:10:55      0x418 ERR 53021 B*TREE   Bad File: 108930 (Root)
    2006-12-06 22:10:55      0x418 ERR 53021 B*TREE   Bad File: 108930 (Root)
    2006-12-06 22:10:55      0x418 ERR 53021 B*TREE   Bad File: 108930 (Root)
    2006-12-06 22:10:55      0x418 ERR 53021 B*TREE   Bad File: 108930 (Root)
    2006-12-06 22:10:55      0x418 ERR 53021 B*TREE   Bad File: 108930 (Root)
    2006-12-06 22:10:55      0xF90 ERR    42 SrvTasks Error while collecting statistics for table 000000000000060a;  error bad_datapage
    2006-12-06 22:10:55      0xF90 ERR    42 SrvTasks  +   Error while collecting statistics for table 000000000000060a;  error bad_datapage
    2006-12-06 22:10:55      0xF90 ERR    42 SrvTasks  +   Error while collecting statistics for table 000000000000060a;  error bad_datapage
    2006-12-06 22:10:55      0xF90 ERR    42 SrvTasks  +   Error while collecting statistics for table 000000000000060a;  error bad_datapage
    2006-12-06 22:10:55      0xF90 ERR    42 SrvTasks  +   Error while collecting statistics for table 000000000000060a;  error bad_datapage
    2006-12-06 22:10:55      0xF90 ERR    42 SrvTasks  +   Error while collecting statistics for table 000000000000060a;  error bad_datapage
    2006-12-06 22:10:55      0xF90 ERR    42 SrvTasks  +   Error while collecting statistics for table 000000000000060a;  error bad_datapage
    2006-12-06 22:10:55      0xF90 ERR    42 SrvTasks  +   Error while collecting statistics for table 000000000000060a;  error bad_datapage
    2006-12-06 22:10:55      0xF90 ERR    42 SrvTasks  +   Error while collecting statistics for table 000000000000060a;  error bad_datapage
    2006-12-06 22:10:55      0xF90 ERR    42 SrvTasks  +   Error while collecting statistics for table 000000000000060a;  error bad_datapage
    2006-12-06 22:10:55      0xF90 ERR 51080 SYSERROR -9407 unexpected error
    2006-12-06 22:10:55      0xF90 ERR     9 Data     Aborting statistics computation due to system error
    2006-12-06 22:10:55      0xF90 ERR    42 SrvTasks  +   Error while collecting statistics for table 000000000000060a;  error bad_datapage
    2006-12-06 22:10:55      0xF90     19651 CONNECT  Connection released, T99

    Thanks Ashwath for your response, but because it was a new installation and I cannot restore the last good backup because i don't have one.
    I remove the installation a couple of times and reinstall the central installation but I got the same problem again. So I did a distributed installation and this was working well.
    with regards,
    Robert

  • Error while installing solution manager 7.1

    Hi All,
    I am installing SAP Solution Manager 7.1 SR1 i am facing below issue ,any one please suggest me how to proceed further.I am new to sybase .
    An error occurred while processing option SAP Solution Manager 7.1 Support Release 1 > SAP Systems > SAP ASE > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You can now:
    Choose Retry to repeat the current step.
    Choose Log Files to get more information about the error.
    Stop the option and continue with it later.
    Log files are written to C:\Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS.
    import_monitor.java log:
    java version "1.4.2_32"
    Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.016)
    SAP Java Server VM (build 4.1.016 1.6-b03, Dec 31 2011 00:41:53 - 41_REL - optU - windows amd64 - 6 - bas2:164914 (mixed mode))
    Import Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29.
    Loading of 'SAPNTAB' import package: ERROR
    Import Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29.
    import_monitor  Log:
    INFO: 2014-07-01 10:49:48
    Import Monitor is started.
    CONFIG: 2014-07-01 10:49:48
    Application options:
    dbCodepage=4103
    dbType=SYB
    extFiles=no
    importDirs=D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP2;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP3;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4
    installDir=C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS
    jobNum=8
    loadArgs=-c 99000000 -loadprocedure fast
    monitorTimeout=30
    orderBy=
    r3loadExe=D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2014-07-01 10:49:48
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2014-07-01 10:49:48
    List of packages with views: 'SAPVIEW'.
    TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is started.
    INFO: 2014-07-01 10:49:48 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is successfully completed.
    Primary key creation: after load.
    Index creation: after load.
    INFO: 2014-07-01 10:49:48
    Data codepage 1100 is determined using TOC file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
    INFO: 2014-07-01 10:49:48
    Version table 'SVERS' is found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
    INFO: 2014-07-01 10:49:48
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
    INFO: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
    Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29  Package Group  max threads: 1 current running threads : 0 processing package: SAPNTAB
    TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPNTAB' import package is started.
    TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPNTAB' import package into database:
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
    INFO: 2014-07-01 10:49:59 com.sap.inst.migmon.LoadTask run_report
    Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29  error processing of package SAPNTAB
    ERROR: 2014-07-01 10:49:59 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPNTAB' import package is interrupted with R3load error.
    Process 'D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPNTAB.log' file.
    Standard error output:
    sapparam: sapargv(argc, argv) has not been called!
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    WARNING: 2014-07-01 10:50:18
    Cannot continue import because not all import packages with data conversion tables are loaded successfully.
    WARNING: 2014-07-01 10:50:18
    1 error(s) during processing of packages.
    INFO: 2014-07-01 10:50:18
    Import Monitor is stopped.
    INFO: 2014-07-01 11:09:16
    Import Monitor is started.
    CONFIG: 2014-07-01 11:09:16
    Application options:
    dbCodepage=4103
    dbType=SYB
    extFiles=no
    importDirs=D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP2;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP3;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4
    installDir=C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS
    jobNum=8
    loadArgs=-c 99000000 -loadprocedure fast
    monitorTimeout=30
    orderBy=
    r3loadExe=D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2014-07-01 11:09:16
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2014-07-01 11:09:16
    List of packages with views: 'SAPVIEW'.
    TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is started.
    INFO: 2014-07-01 11:09:16 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is successfully completed.
    Primary key creation: after load.
    Index creation: after load.
    INFO: 2014-07-01 11:09:16
    Data codepage 1100 is determined using TOC file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
    INFO: 2014-07-01 11:09:16
    Version table 'SVERS' is found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
    INFO: 2014-07-01 11:09:16
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
    INFO: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
    Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29  Package Group  max threads: 1 current running threads : 0 processing package: SAPNTAB
    TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPNTAB' import package is started.
    TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPNTAB' import package into database:
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
    INFO: 2014-07-01 11:09:27 com.sap.inst.migmon.LoadTask run_report
    Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29  error processing of package SAPNTAB
    ERROR: 2014-07-01 11:09:27 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPNTAB' import package is interrupted with R3load error.
    Process 'D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPNTAB.log' file.
    Standard error output:
    sapparam: sapargv(argc, argv) has not been called!
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    WARNING: 2014-07-01 11:09:46
    Cannot continue import because not all import packages with data conversion tables are loaded successfully.
    WARNING: 2014-07-01 11:09:46
    1 error(s) during processing of packages.
    INFO: 2014-07-01 11:09:46
    Import Monitor is stopped.
    NOTE:
    The same issue has been solved in SCN Thread http://scn.sap.com/thread/3360385. As suggested in that note i am trying to look into the sap note
    Note 1716201 - SYB:Update control.xml files for installation: Sybase ASE
    in service market place but it is displaying as Document not released.
    Kindly can any one help me in provind the above mentioned note or help me how to resolve this issue.
    Regards,
    SURYA.

    HI Divyanshu,
    Below is the SAPNTAB.log:
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140630211543
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
    Compiled Dec  2 2011 03:21:30
    patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
    process id 1680
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -ctf I D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL SAPNTAB.TSK SYB -l SAPNTAB.log
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job completed
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140630211543
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140630211543
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
    Compiled Dec  2 2011 03:21:30
    patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
    process id 1904
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
    (DB) INFO: connected to DB
    (SQL) INFO: Searching for SQL file SQLFiles.LST
    (SQL) INFO: SQLFiles.LST not found
    (SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
    (SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
    (SQL) INFO: Searching for SQL file SDIC.SQL
    (SQL) INFO: SDIC.SQL not found
    (SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
    (SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
    (DB) INFO: SVERS created
    (IMP) INFO: import of SVERS completed (1 rows) #20140630211544
    (DB) INFO: SVERS~0 created
    (DB) INFO: DDNTF created
    (SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 99, table "DDNTF"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: ExeFastload: rc = 2
    (DB) INFO: DDNTF~0 created
    (DB) INFO: DDNTF_CONV_UC created
    (SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 99, table "DDNTF_CONV_UC"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: ExeFastload: rc = 2
    (DB) INFO: DDNTF_CONV_UC~0 created
    (DB) INFO: DDNTT created
    (SYB_IMP) ERROR: DbSlEndModify failed
      rc = 99, table "DDNTT"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: EndFastload: rc = 2
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE  INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
    DbSlExecute: rc = 99
      (SQL error 1505)
      error message returned by DbSl:
    [ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key.  Primary key is '""'
    (DB) INFO: DDNTT_CONV_UC created
    (SYB_IMP) ERROR: DbSlEndModify failed
      rc = 99, table "DDNTT_CONV_UC"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: EndFastload: rc = 2
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE  INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
    DbSlExecute: rc = 99
      (SQL error 1505)
      error message returned by DbSl:
    [ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key.  Primary key is '""'
    (DB) INFO: disconnected from DB
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140630211555
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701104948
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
    Compiled Dec  2 2011 03:21:30
    patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
    process id 2304
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
    (DB) INFO: connected to DB
    (DB) INFO: DDNTF deleted/truncated
    (SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 99, table "DDNTF"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: ExeFastload: rc = 2
    (DB) INFO: DDNTF_CONV_UC deleted/truncated
    (SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 99, table "DDNTF_CONV_UC"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: ExeFastload: rc = 2
    (DB) INFO: DDNTT deleted/truncated
    (SYB_IMP) ERROR: DbSlEndModify failed
      rc = 99, table "DDNTT"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: EndFastload: rc = 2
    (SQL) INFO: Searching for SQL file SQLFiles.LST
    (SQL) INFO: SQLFiles.LST not found
    (SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
    (SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
    (SQL) INFO: Searching for SQL file SDIC.SQL
    (SQL) INFO: SDIC.SQL not found
    (SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
    (SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
    (DB) ERROR: DDL statement failed
    (DROP INDEX "DDNTT"."DDNTT~0")
    DbSlExecute: rc = 103
      (SQL error 3701)
      error message returned by DbSl:
    [ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE  INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
    DbSlExecute: rc = 99
      (SQL error 1505)
      error message returned by DbSl:
    [ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key.  Primary key is '""'
    (DB) INFO: DDNTT_CONV_UC deleted/truncated
    (SYB_IMP) ERROR: DbSlEndModify failed
      rc = 99, table "DDNTT_CONV_UC"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: EndFastload: rc = 2
    (DB) ERROR: DDL statement failed
    (DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
    DbSlExecute: rc = 103
      (SQL error 3701)
      error message returned by DbSl:
    [ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE  INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
    DbSlExecute: rc = 99
      (SQL error 1505)
      error message returned by DbSl:
    [ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key.  Primary key is '""'
    (DB) INFO: disconnected from DB
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701104959
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701110916
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
    Compiled Dec  2 2011 03:21:30
    patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
    process id 2056
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
    (DB) INFO: connected to DB
    (DB) INFO: DDNTF deleted/truncated
    (SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 99, table "DDNTF"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: ExeFastload: rc = 2
    (DB) INFO: DDNTF_CONV_UC deleted/truncated
    (SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 99, table "DDNTF_CONV_UC"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: ExeFastload: rc = 2
    (DB) INFO: DDNTT deleted/truncated
    (SYB_IMP) ERROR: DbSlEndModify failed
      rc = 99, table "DDNTT"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: EndFastload: rc = 2
    (SQL) INFO: Searching for SQL file SQLFiles.LST
    (SQL) INFO: SQLFiles.LST not found
    (SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
    (SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
    (SQL) INFO: Searching for SQL file SDIC.SQL
    (SQL) INFO: SDIC.SQL not found
    (SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
    (SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
    (DB) ERROR: DDL statement failed
    (DROP INDEX "DDNTT"."DDNTT~0")
    DbSlExecute: rc = 103
      (SQL error 3701)
      error message returned by DbSl:
    [ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE  INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
    DbSlExecute: rc = 99
      (SQL error 1505)
      error message returned by DbSl:
    [ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key.  Primary key is '""'
    (DB) INFO: DDNTT_CONV_UC deleted/truncated
    (SYB_IMP) ERROR: DbSlEndModify failed
      rc = 99, table "DDNTT_CONV_UC"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: EndFastload: rc = 2
    (DB) ERROR: DDL statement failed
    (DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
    DbSlExecute: rc = 103
      (SQL error 3701)
      error message returned by DbSl:
    [ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE  INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
    DbSlExecute: rc = 99
      (SQL error 1505)
      error message returned by DbSl:
    [ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key.  Primary key is '""'
    (DB) INFO: disconnected from DB
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701110927
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701120231
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
    Compiled Dec  2 2011 03:21:30
    patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
    process id 2288
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
    (DB) INFO: connected to DB
    (DB) INFO: DDNTF deleted/truncated
    (SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 99, table "DDNTF"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: ExeFastload: rc = 2
    (DB) INFO: DDNTF_CONV_UC deleted/truncated
    (SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 99, table "DDNTF_CONV_UC"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: ExeFastload: rc = 2
    (DB) INFO: DDNTT deleted/truncated
    (SYB_IMP) ERROR: DbSlEndModify failed
      rc = 99, table "DDNTT"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: EndFastload: rc = 2
    (SQL) INFO: Searching for SQL file SQLFiles.LST
    (SQL) INFO: SQLFiles.LST not found
    (SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
    (SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
    (SQL) INFO: Searching for SQL file SDIC.SQL
    (SQL) INFO: SDIC.SQL not found
    (SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
    (SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
    (DB) ERROR: DDL statement failed
    (DROP INDEX "DDNTT"."DDNTT~0")
    DbSlExecute: rc = 103
      (SQL error 3701)
      error message returned by DbSl:
    [ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE  INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
    DbSlExecute: rc = 99
      (SQL error 1505)
      error message returned by DbSl:
    [ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key.  Primary key is '""'
    (DB) INFO: DDNTT_CONV_UC deleted/truncated
    (SYB_IMP) ERROR: DbSlEndModify failed
      rc = 99, table "DDNTT_CONV_UC"
      (SQL error 30128)
      error message returned by DbSl:
    [ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
    (IMP) ERROR: EndFastload: rc = 2
    (DB) ERROR: DDL statement failed
    (DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
    DbSlExecute: rc = 103
      (SQL error 3701)
      error message returned by DbSl:
    [ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE  INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
    DbSlExecute: rc = 99
      (SQL error 1505)
      error message returned by DbSl:
    [ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key.  Primary key is '""'
    (DB) INFO: disconnected from DB
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
    D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701120242

  • SAP Solution Manager SR1 with MSSQL on W2K3 IA32 - Problem with Kernel

    Hello,
    we are implementing a sandbox in order to test the SAP Solution Manager 4.0 SR1 with MSSQL on W2K3 IA32. Therefore we ordered the installation CD for the above mentioned configuration. Instead of getting the SAP NETWEAVER Kernel SR1 we got SR2. Now we have the problem, that the installation program SAPINST is requesting the SR1- Kernel.
    Unforunately the SR1-Kernel seems no longer available in the download section.
    It would be fine to get a suggestion how to solve the problem.
    Thanks
    Best regards
    Ralf Richter ([email protected])

    Hi Andreas,
    thanks for the hint, I have already checked the LABEL.ASC. I have no LABEL.ASC-Key for the SAP Netweaver 2004s SR1, so it would be a possibilty to substitue this key. But neverhteless, I think, there should be another official procedure in order to use the SR2 instead of the old SR1. I have contacted Klaus Billing at SAP as recommended in the OSS Note 918078. Best regards. Ralf R.

  • Solution Manager install

    Hi,
    I just wanted to double check with SAP regarding the installation of
    Solution Manager 3.2
    1. Is there a hard and fast rule that the Sloution Manager needs to be
    installed on a server with Fully Qualified domain name.
    2. Is it a requirement that Solution Manager needs to be installed on a
    seperate server and cannot be installed on a SAP development or
    production server or any other system with ECC installed.
    Please let me know
    Thanks
    Mikir
    98196-65821.

    Hi Mikir,
    Agree with Pascal, you probably should consider install SolMan 4.0 instead of 3.2.
    1. Yes, you need make sure to use FQDN everywhere possible. Many notes -- 677118, 434918 has stated on this.
    2. You can install SM on the same server with other instance. I just implemented a SolMan 4.0 production instance on one of our BW server. In one SQL Server instance, two separate databases. It seems no problem at all.
    Thanks,
    Yujun

  • Error 1314 in the Solution Manager Installation

    I'm installing Solution Manager 4.0 SR1 in Windows 2003 + Oracle 10g.
    In the second step of the "Task Progress", "Create users for SAP System"
    I've the error message :
    "ERROR 2007-03-15 18:07:29
    FSL-00001 System call failed. Error 1314 (A required privilege is not
    held by the client.
    ) in execution of system call 'LoadUserProfile' with parameter (thread
    token for FIG\smpadm, smpadm), line (706) in file (synxccuren.cpp)."
    I'm executing the installation with the domain administrator, and I
    review the local policies for this user (Act part of operating system,
    adjust memory quotas for a process and replace a process level token).
    Thank's in advanced
    Francesc Segura

    I am getting the same error. How do i resolve it?
    Thanks
    Pooja

  • EP 7 systems in Solution Manager 7 for EWA activation

    Dear Expert,
    Greetings from Partha.
    I need to include our EP 7 systems in Solution Manager 7 for EWA activation. Current lanscape scenario
    Solution Manger     7.00   Installed
    EP                          7.00   Installed
    No central SLD configured and all the system have local SLD.
    1. As per the installtion guide & SAP notes we need to install
    a> SM Diagnostics Agent & Wilo Introscope in Solution Manager (manging system).
    b> Diagnostics Agent in every manged system(s).
    For managing system we can download Diagnostics Agent installation DVDs from SAP Service Marketplace
    at: http://service.sap.com/swdc --> Download --> SAP Support Packages --> Entry by Application Group
    --> SAP Technology Components --> SAP SOLUTION MANAGER --> SAP SOLUTION MANAGER 7.0
    --> Entry by Component --> Agents for Managed systems --> DIAGNOSTICS AGENT 7.11
    --> <choose operating system of managed>
    Our Solution Manager 7 is already installed and @SPS 17. My question is
    1. Can we use the same file for SMD installtion in Solution Manger or we need to download it from some other area ?
    If it is different then kindly let me know what are the DVDs to be downloaded and from where?
    2. In our Managed System SMD installtion we have decided for
    --> Installation Strategy as Direct Solution Manager Registration
    But what strategy we should take for SMD installation on Sol Man 7 that is
    Local SLD (wrt Sol Man) Registration or Direct Solution Manager Registration
    3. What is the need for the SAP Host Agent Installattion ? Is it mandatory ?
    Help will be appreciated.
    Regards,
    Partha

    1. As per the installtion guide & SAP notes we need to install
    a> SM Diagnostics Agent & Wilo Introscope in Solution Manager (manging system).
    b> Diagnostics Agent in every manged system(s).
    For managing system we can download Diagnostics Agent installation DVDs from SAP Service Marketplace
    at: http://service.sap.com/swdc --> Download --> SAP Support Packages --> Entry by Application Group
    --> SAP Technology Components --> SAP SOLUTION MANAGER --> SAP SOLUTION MANAGER 7.0
    --> Entry by Component --> Agents for Managed systems --> DIAGNOSTICS AGENT 7.11
    --> <choose operating system of managed>
    Our Solution Manager 7 is already installed and @SPS 17. My question is
    1. Can we use the same file for SMD installtion in Solution Manger or we need to download it from some other area ?
    If it is different then kindly let me know what are the DVDs to be downloaded and from where?
    Check the pdf attached in note 1234387 - Inst. 7.1 EhP1 - Diagnostics Agent installation
    If you have SP17, you must follow note 1357812 and install Diagnostics Agent 7.01 SR1
    2. In our Managed System SMD installtion we have decided for
    --> Installation Strategy as Direct Solution Manager Registration
    But what strategy we should take for SMD installation on Sol Man 7 that is
    Local SLD (wrt Sol Man) Registration or Direct Solution Manager Registration
    It doesn't matter what strategy you'll decide. You could decide Direct Solution Manager registration
    3. What is the need for the SAP Host Agent Installattion ? Is it mandatory ?
    As you have solution Manager SP17, you can't install Saphostagent 7.11 and for this reason you can't use SAphostagent.
    Agent 7.01 => No Saphostagent
    Agent 7.11 => Must install saphostagent
    Agent 7.20 => Already have SAPhostagent installed

  • System Monitoring with Solution Manager Ehp1

    Hi,
    I'm Tomas Piqueres, and I'm working in a VAR SAP with Solution Manager.
    Recently, we installed Solution Manager Ehp1 and we are trying to configure it for System Monitoring. When I worked with Solution Manager SP17 I used to go to transaction RZ21 to add the system I wanted to monitoring and then put the SID and RFCs of the system.
    Now with Solution Manager Ehp1, when I create the system in transaction RZ21, first I have to set the Component Type to Be Monitored and then the SID, Message Server Logon Group, the client and user are set automatically, and the password I've set to user CSMREG.
    when I fill all the entries, I can see the RFCs used for the monitoring of the system. Those RFCs are set automatically:
    <SID>_RZ20_COLLECT
    <SID>_RZ20_ANALYZE
    I can't edit those RFCs, so I have to create it manually. I check that RFCs destination works fine and both pass the authorization test, so when I try to save the system at transaction RZ21, I see the following errors:
    <SID>_RZ20_COLLECT_123539Error when opening an RFC connection
    Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection
    Error during remote call of SALC function: Error when opening an RFC connection
    Error during remote call of RFC1 function: Error when opening an RFC connection
    I've been looking for information about those errors and how to monitoring with Solution Manager Ehp1, but I haven't found anything usefull.
    Please, Could you help me?
    Thanks and regards,
    Tomas.

    Tomas,
    I need to configure EWA from my Solman system and I completed the steps (defining and creation of RFC destinations to the target systems from my Solman system).  I downloaded the lates ccmsagent file from the market place based my target system configurations.
    Herewith attaching the logs while I'm trying to check the profile parameter.
    tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sappfpar check pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    ================================================================================
    ==   Checking profile:     /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    ================================================================================
    ***WARNING: Unexpected parameter: DIR_EPS =/usr/sap/trans/EPS/----
    ***WARNING: Unexpected parameter: SAPSECULIB =/usr/sap/TQA/SYS/exe/run/libsapsecu.o
    ***WARNING: Unexpected parameter: abap/buffersize_part1 =1200000
    ***WARNING: Unexpected parameter: auth/auth_number_in_userbuffer =5000
    ***WARNING: Unexpected parameter: dbs/io_buf_size =100000
    ***WARNING: Unexpected parameter: rsau/local/file =/usr/sap/TQA/DVEBMGS30/log/audit/audit_++++++++
    ***WARNING: Unexpected parameter: rsau/selector1/class =35
    ***WARNING: Unexpected parameter: rsau/selector1/severity =2
    ***WARNING: Unexpected parameter: rsdb/rclu/cachelimt =0
    ***ERROR: Size of shared memory pool 40 too small
    ================================================================
    SOLUTIONS: (1) Locate shared memory segments outside of pool 40
                   with parameters like: ipc/shm_psize_<key> =0
    SOLUTION: Increase size of shared memory pool 40
              with parameter: ipc/shm_psize_40 =1472000000
    Shared memory disposition overview
    ================================================================
    Shared memory pools
    Key:   10  Pool
                Size configured.....:   642000000 ( 612.3 MB)
                Size min. estimated.:   637597428 ( 608.1 MB)
                Advised Size........:   640000000 ( 610.4 MB)
    Key:   40  Pool for database buffers
                Size configured.....:  1048000000 ( 999.4 MB)
                Size min. estimated.:  1468229308 (1400.2 MB)
                Advised Size........:  1472000000 (1403.8 MB)
    Shared memories inside of pool 10
    Key:        1  Size:        2500 (   0.0 MB) System administration
    Key:        4  Size:      523648 (   0.5 MB) statistic area
    Key:        7  Size:       14838 (   0.0 MB) Update task administration
    Key:        8  Size:    67108964 (  64.0 MB) Paging buffer
    Key:        9  Size:   134217828 ( 128.0 MB) Roll buffer
    Key:       11  Size:      500000 (   0.5 MB) Factory calender buffer
    Key:       12  Size:     6000000 (   5.7 MB) TemSe Char-Code convert Buf.
    Key:       13  Size:   200500000 ( 191.2 MB) Alert Area
    Key:       16  Size:       22400 (   0.0 MB) Semaphore activity monitoring
    Key:       17  Size:     2672386 (   2.5 MB) Roll administration
    Key:       30  Size:       37888 (   0.0 MB) Taskhandler runtime admin.
    Key:       31  Size:     4806000 (   4.6 MB) Dispatcher request queue
    Key:       33  Size:    39936000 (  38.1 MB) Table buffer, part.buffering
    Key:       34  Size:    20480000 (  19.5 MB) Enqueue table
    Key:       51  Size:     3200000 (   3.1 MB) Extended memory admin.
    Key:       52  Size:       40000 (   0.0 MB) Message Server buffer
    Key:       54  Size:    20488192 (  19.5 MB) Export/Import buffer
    Key:       55  Size:        8192 (   0.0 MB) Spool local printer+joblist
    Key:       57  Size:     1048576 (   1.0 MB) Profilparameter in shared mem
    Key:       58  Size:        4096 (   0.0 MB) Enqueue ID for reset
    Key:       62  Size:    85983232 (  82.0 MB) Memory pipes
    Shared memories inside of pool 40
    Key:        2  Size:    31168040 (  29.7 MB) Disp. administration tables
    Key:        3  Size:   114048000 ( 108.8 MB) Disp. communication areas
    Key:        6  Size:  1064960000 (1015.6 MB) ABAP program buffer
    Key:       14  Size:    28600000 (  27.3 MB) Presentation buffer
    Key:       19  Size:    90000000 (  85.8 MB) Table-buffer
    Key:       42  Size:    13920992 (  13.3 MB) DB TTAB buffer
    Key:       43  Size:    43422392 (  41.4 MB) DB FTAB buffer
    Key:       44  Size:     8606392 (   8.2 MB) DB IREC buffer
    Key:       45  Size:     6558392 (   6.3 MB) DB short nametab buffer
    Key:       46  Size:       20480 (   0.0 MB) DB sync table
    Key:       47  Size:    13313024 (  12.7 MB) DB CUA buffer
    Key:       48  Size:      300000 (   0.3 MB) Number range buffer
    Key:       49  Size:     3309932 (   3.2 MB) Spool admin (SpoolWP+DiaWP)
    Shared memories outside of pools
    Key:       18  Size:     1792100 (   1.7 MB) Paging adminitration
    Key:       41  Size:    25010000 (  23.9 MB) DB statistics buffer
    Key:       63  Size:      409600 (   0.4 MB) ICMAN shared memory
    Key:       64  Size:     4202496 (   4.0 MB) Online Text Repository Buf.
    Key:       65  Size:     4202496 (   4.0 MB) Export/Import Shared Memory
    Key:     1002  Size:      400000 (   0.4 MB) Performance monitoring V01.0
    Key: 58900130  Size:        4096 (   0.0 MB) SCSA area
    Nr of operating system shared memory segments: 9
    Shared memory resource requirements estimated
    ================================================================
    Nr of shared memory descriptors required for
    Extended Memory Management (unnamed mapped file).: 64
    Total Nr of shared segments required.....:         73
    System-imposed number of shared memories.:       1000
    Shared memory segment size required min..: 1472000000 (1403.8 MB)
    System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)
    Swap space requirements estimated
    ================================================
    Shared memory....................: 2050.4 MB
    ..in pool 10  608.1 MB,   99% used
    ..in pool 40  999.4 MB,  140% used !!
    ..not in pool:   34.4 MB
    Processes........................:  716.8 MB
    Extended Memory .................: 8192.0 MB
    Total, minimum requirement.......: 10959.2 MB
    Process local heaps, worst case..: 1907.3 MB
    Total, worst case requirement....: 12866.5 MB
    Errors detected..................:    1
    Warnings detected................:    9
    After checking the profile parameter I tried to run sapccm4x in /run directory but got the below error and I'm not able tomove further.
    Pls have a look at these two and let me know what could I do to proceed further.
    tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    INFO: CCMS agent sapccm4x working directory is /usr/sap/TQA/DVEBMGS30/log/sapccm4x
    INFO: CCMS agent sapccm4x config file is /usr/sap/TQA/DVEBMGS30/log/sapccm4x/csmconf
    INFO: Central Monitoring System is [SMP]. (found in config file)
          additional CENTRAL system y/[n] ?   :
    INFO: found ini file /usr/sap/TQA/DVEBMGS30/log/sapccm4x/sapccmsr.ini.
    INFO:
          CCMS version  20040229, 64 bit, multithreaded, Non-Unicode
          compiled at   Jun 28 2010
          systemid      324 (IBM RS/6000 with AIX)
          relno         6400
          patch text    patch collection 2010/1, OSS note 1304480
          patchno       335
    INFO Runtime:
          running on    saptqa01 AIX 3 5 00069A8FD600
          running with profile   /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    INFO profile parameters:
          alert/MONI_SEGM_SIZE = 200000000
          alert/TRACE          = 1
          SAPSYSTEM            = 30
          SAPSYSTEMNAME        = TQA
          SAPLOCALHOST         = saptqa01
          DIR_CCMS             = /usr/sap/ccms
          DIR_LOGGING          = /usr/sap/TQA/DVEBMGS30/log
          DIR_PERF             = /usr/sap/tmp
    INFO:
          pid           4165682
    INFO: Attached to Shared Memory Key 13 (size 200141728) in pool 10
    INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application server saptqa01_TQA_30, created with version CCMS version 20040229, 64 bit single threaded, compiled at Oct  3 2008,  kernel 6400_20020600_254,  platform 324 (IBM RS/6000 with AIX)]
            segment status     ENABLED
            segment started at Tue Sep 14 09:35:56 2010
            segment version    20040229
    ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30
           Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.
           Please change configuration with profile parameters
               ipc/shm_psize_01 = -<different pool nr>
           xor
               ipc/shm_psize_13 = -<different pool nr>
    EXITING with code 1

Maybe you are looking for