START_J2EE_INITIAL phase error

hi,
i'm trying to upgrade dual stack system and i've got an error during the execution of the START_J2EE_INITIAL phase.
this is trouble ticket info:
Trouble Ticket Report
Upgrade to SAP NetWeaver'04s SR3
SID................: DWD
Hostname...........: fsczpga01519
Install directory..: /usr/sap/DWD
Upgrade directory..: /usr/sap/jupgrade
Database...........: Oracle
Operating System...: UNIX
JDK version........: 1.4.2 IBM Corporation
SAPJup version.....: 1.3.16
Source release.....: 630
Target release.....: 700
Current usages.....: AS;AAS
ABAP stack present.: true
The execution of UPGRADE/UPGRADE/START_J2EE_INITIAL ended in error.
Could not start J2EE Engine instance with name J2EE and number 10 of the standard system.
Could not start instance 10.
More information can be found in the log file /usr/sap/jupgrade/log/START_J2EE_INITIAL_TJI_03.LOG.
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Se
arch for OSS notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypeControlEngine
com.sap.sdt.ucp.phases.PhaseException
Could not start J2EE Engine instance with name J2EE and number 10 of the standard system.
START_J2EE_INITIAL_TJI_03.LOG is saying this:
#1.5#C0000A2ABA08000000000CEF62E2B88B000480E7B2CA7CD0#1267632532258#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/START_J2EE_INITIAL##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:834)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:834)#Java###Phase status is .#1#error#
and there is an error in std_server0.out:
Loading: ConfigurationManager returned false!
Kernel not loaded. System halted.
any help appreciated.
thanks,
martin

Hello Martin,
The defaultTrace of server0 might provide you with more information about the error.
The Kernel of the J2EE Engine is made by mostly libraries and therefore when it doesnu2019t start usually a bad deployment is the cause. Therefore if the information in the defaultTrace doesnu2019t help you to find the solution you could try to re-deploy with SDM the following SDA file that contains the J2EE Kernel:
SAPJEECOR[SP_Version].SCA. Select the option u201CUpdate SDAu2019s/SCAu2019s that have any versionu201D in the SDM GUI. Refer to the SDM documentation at SDM/program/doc for more information about SDM.
Regards,
Ventsi Tsachev
Technology Development Support (J2EE Engine)
SAP Labs, Palo Alto, Ca (USA)

Similar Messages

  • JSPM phase error : admin/user/SID does not exist

    Hi ,
    There is an error message while opening the JSPM
    Phase error report:
    "cannot read secure store properties .could not set up secure store.property admin/user/SID does not exist.msg.util.dyn.0003.com.sap.security.core.server.secstore.secstoreFS get string value
    com.sap.security.core.server.secstore.secstoreFS.Not found exception could not find a record key "admin/user/SID" in the store com.sap.security.core.server.secstore.secstorefs"
    checked the config tool secure store and found no entry maintained for /admin/user/SID.
    How to add the new entry in config tool and what is post entry procedure
    Thanks a ton

    Hello Daniel,
    You can maintain the Administrator user in secure storage using the config tool.
    By default, the value for this config tool property is user Administrator. However, when using the ABAP Engine for persistency, this user is J2EE_ADMIN.
    Following are the steps:
           1.      Start the Config Tool.
           2.      Select secure store.
                    The configuration for the secure storage in the file system appears.
           3.      Select the key admin/user/<SID>.
           4.      Enter J2EE_ADMIN in the Value: field and choose Add. 
           5.      Select the key admin/password/<SID>.
           6.      Enter the password for J2EE_ADMIN in the Value: field and choose Add.
           7.      Save the configuration.
    The corresponding link is mentioned below:
    http://help.sap.com/saphelp_nw04/helpdata/en/ae/b7ceff3e40fd42be3a6503236f9746/content.htm

  • Error number 207 error type SPECIFIC_CODE IMPORT ABAP phase error when install database instance

    IMPORT ABAP phase error when install database instance
    Error number 207 error type SPECIFIC_CODE.
    In phase   "Import ABAP" the installation halts with error. Can anyone please tell me what error should I search for and (possibly) what is the solution? 
    Thanks in advance
    synxcaccmg.cpp: 133: PSyUser CSyAccountMgtImpl::getUser(iastring sNameOrSID) const
    syxxccache.cpp: 267: CSyAccountCache::getUserImpl(name="IboSap-PC\nspadm", sid="", create=false)
    syxxccache.cpp: 276: CSyAccountCache::getUserImpl(name="IboSap-PC\nspadm", sid="", create=false, ISyProgressObserver* )
    synxcuser.cpp: 119: CSyUserImpl::CSyUserImpl(const CUserData&, bool)
    Account user="IboSap-PC\nspadm" does not exist.
    Failed action:  with parameters
    Error number 207 error type SPECIFIC_CODE

    It is not easy, really , it has taken many hours and at the End I got the problems,.
    so I have decided to pay 20 $ every month, and I can get an access IDES to SAP, ERP, ABAP.
    without any problem.  In ABAP, I have only Sflight ,SBOOK etc. but MARA, and others tables, dont exist, .
    I know, some students have not enough money, so what can we do? every one get problem with installaion and others after installaion, with server, 3 days work, and NSP becomes RED. Yellow, etc.
    anyway. thank you for all.
    Best Regards.

  • ECC 6.0  Import ABAP phase error

    Hi,
    I am facing the same problem as mentioned below thread with x64 bit 2003 windows on my p4 desktop machine  with 2 gb RAM.
    ECC 6.0 SR2 Import ABAP phase error 
    Pl. suggest does the it works  on my P4 machine , x64 bit windows 2k3 is working fine on desktop .
    means my desktop is supporting 64 bit version . is it ?
    or I have to use true IA64 Bit itenium based machine ?
    SQL> shutdown
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist .
    I have followed the thread , which is mentioned above .
    Thanks in advance .
    Edited by: sonal  saxena on Feb 23, 2009 8:04 AM

    Sonal,
    Refer to following link and hope it solves your problem.
    [http://www.dbmotive.com/oracle_error_codes.php?errcode=27101]
    Manoj Chintawar

  • Error in START_J2EE_INITIAL phase of PI7.1 Ehp1 Upgrade

    START_J2EE_INITIAL_TJI_02.LOG
    com.sap.sdt.j2ee.phases.PhaseTypeControlEngine com.sap.sdt.ucp.phases.PhaseException Could not start AS Java instance with name J2EE and number 03 of the standard system. START_J2EE_INITIAL DOWNTIME UPGRADE NetWeaver Upgrade SAPJup Java Upgrade
    dev_server0 log
    F [Thr 26215] Tue Dec  1 20:22:27 2009
    F  [Thr 26215] *** WARNING => SfCFramework::registerNatives: failed for com.sap.conn.rfc.driver.CpicDriver [sfxxifrw.hpp 165]

    M [Thr 21075] Tue Dec  1 20:22:46 2009
    M  [Thr 21075] ***LOG Q0I=> NiPConnect: 127.0.0.1:3305: connect (79: A remote host refused an attempted connect operation.) [nixxi.cpp 2777]
    M  [Thr 21075] *** ERROR => NiPConnect: SiConnect failed for hdl 25/sock 72
        (SI_ECONN_REFUSE/79; I4; ST; 127.0.0.1:3305) [nixxi.cpp    2777]
    std_server0.  log
    Service [com.sap.security.core.ume.service] start ================= ERROR =================
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: com.sap.conn.jco.JCoException: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
    Connection parameters: TYPE=A DEST=SAPJup ASHOST=localhost SYSNR=05 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner '127.0.0.1:3305' not reached
    TIME        Tue Dec  1 20:17:29 200
    RELEASE     711
    COMPONENT   NI (network interface)
    VERSION     39
    RC          -10
    MODULE      nixxi.cpp
    LINE        2777
    DETAIL      NiPConnect: 127.0.0.1:3305
    SYSTEM CALL connect
    ERRNO       79
    ERRNO TEXT  A remote host refused an attempted connect operation.
    COUNTER     3
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:446)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
         at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: com.sap.conn.jco.JCoException: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
    Connection parameters: TYPE=A DEST=SAPJup ASHOST=localhost SYSNR=05 PCS=1
    In this phase it is trying to starup the instance with 03 sys no, but std_server0 log shows that ume service is trying to connect
    to instance with sys-no 05 ( shadow).
    I also refered to the wiki link,
    https://wiki.sdn.sap.com/wiki/pages/viewpage.action?spaceKey=JSTSG&title=(SLTG)(SAPJUP)+Problems-P1&decorator=printable
    where it says the DDIC password needs to be same in both 000 and the ume store client ( eg 030), which i checked in our case
    and the DDIC password is the same,
    Experts please help, helpful answers will be fully rewarded with points.
    Thanks,
    Govind
    Edited by: Govind Prathi on Dec 2, 2009 5:24 PM
    Edited by: Govind Prathi on Dec 2, 2009 5:27 PM

    Hi Govind,
    please post the /work/dev_jcontrol trace file.
    maybe the following link helps you to analyze your problem regarding RFC_ERROR_COMMUNICATION
    http://help.sap.com/saphelp_nw70/helpdata/EN/20/361941edd5ef23e10000000a155106/content.htm
    Please have a look in dev_jrfc.trc files. These files are written by JRFC and can be found in the directories j2ee/cluster/server* of the J2EE Application Server Installation. The following document describes, how tracing can be switched on/off:
    http://help.sap.com/saphelp_nw70/helpdata/en/f6/daea401675752ae10000000a155106/content.htm
    Be sure that j2ee_admin user is not locked.
    Check /etc/services for '127.0.0.1:3305'
    please also be sure that the UME.Properties settings in com.sap.security.core.ume.service are correct:
    Please start offline configtool, goto cluster_data - server - cfg - services and check the property sheet
    com.sap.security.core.ume.service
    please also update ume.r3.connection.master.ashost with hostname of your portal server.
    then restart your JAVA instance.
    Is this dual stack (ABAP+JAVA) ?
    Does your system is running on High Availability server?
    Gerd
    Edited by: Gerd Schuster on Dec 2, 2009 5:09 PM
    Edited by: Gerd Schuster on Dec 2, 2009 5:20 PM

  • Execution of Reports phase error during SAP EHP4 upgrade with EHPi

    I started getting an error message in the "Execution of reports after put" phase
    (within the Downtime phase) during the SAP EHP4 upgrade with Enhancement
    Package Installer.
    ***** LIST OF ERRORS
    AND RETURN CODES *****
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPRB70104.OPQ
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1AETR012XProgram terminated (job: "RDDEXECL", no.: "09064300") Long
    text: Cause Program "&V#&", which was started in the background, was
    terminated abnormally. System Response The system created a job log for
    the terminated program. What to do Proceed as follows: Log onto the
    system in which the program was executed. The system is specified at the
    beginning of the transport log. Then call transaction SM37 to display the
    job log. Enter "&V#&" as job name and "DDIC" as user name. Restrict the
    starting date to the starting date specified in the transport log. For
    the other selection criteria, select only jobs with the status
    "cancelled". Then press <LS>Execute</>. A list of the jobs satisfying the
    selection criteria is displayed. You can display the log by pressing
    <LS>Job log</>. If the list contains several jobs, you can select the job
    with the ID " &V#&" with <LS>Display</> -> <LS>Job details</> or define
    further details for the selection criteria in the initial screen of
    transaction SM37. If the ABAP processor reports cancellation,
    double-clicking on the corresponding message in the job log branches to
    the display of the corresponding short dump. 1AEPU320 See job
    log"RDDEXECL""09064300""OPQ" 1 ETP111 exit code : "12" >>> PLEASE READTHE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<< XPRAs are
    application reports that run at the end of an upgrade.
    Most XPRA reportshave a report documentation that explains what the report does and how
    errors can be corrected. Call transaction se38 in the SAP system, enter
    the report name, select 'Documentation' and click the 'Display' button.
    >>> The problematic XPRAs are mentioned in messages of type PU132 above
    <<<
    I tried to follow the instructions in note 1269960, but the enhancement spot
    CLASSIFICATION_TOOL was already active. I activated it again and reran the phase
    but got the same error. Also, I couldn't implement the note using SNOTE because it is
    the middle of the upgrade process.
    I also found the following long text in ST22
    "Internal error during syntax check: ("//bas/710_REL/src/krn/gen/scsymb.c#11"
    Processing had to be terminated because an internal error
    occurred when generating the ABAP/4 program
    "CL_CLS_BADI_CHARACTERIZATION==CP".
    The internal system error cannot be fixed by ABAP means only."
    I am on a 64 bit System with CentOS Linux. 8 GB RAM, 250 GB HD with 20 GB free space.
    So far, I could not find any information on this. Any help would be greatly appreciated!
    Thanks,
    Victor

    Hi Victor,
    Go to SM37 and put in the username as DDIC and see the job log.
    Also check  Sm50 and see whether you have BTC processes available.
    Last but not the least check your filesystem space  usage too.
    Gerard

  • ABAP Import Phase error during Install

    Hi out there. I am installing an ERP system ECC 6.0 SR3 with just the AS ABAP and ECC components. It is now on the ABAP import phase and returns the error that certain ABAP objects are failing out of the 112 objects that is processing. Current examples are : -
    =============================================================================
    Loading of 'SAPSDIC_2' import package: ERROR
    (DB) ERROR: DDL statement failed
    (CREATE  INDEX "VRSX2~1" ON "VRSX2" ( "RELID" , "OBJNAME" , "VERSNO"  ) )
    DbSlExecute: rc = 99
      (SQL error -602)
      error message returned by DbSl:
    =============================================================================
    Loading of 'DD03L' import package: ERROR
    ERROR : Execute for create index SEOSUBCO~001 on SEOSUBCO failed (dbrc=99).
      (SQL error -602)
      error message returned by DbSl:
    SQL-Statement: CREATE  INDEX "SEOSUBCO~001" ON "SEOSUBCO" ( "CLSNAME" , "CMPNAME" , "SCOTYPE"  )
    =============================================================================
    Loading of 'SAPAPPL2_9' import package: ERROR
    ERROR : Execute for create index SEOSUBCO~001 on SEOSUBCO failed (dbrc=99).
      (SQL error -602)
      error message returned by DbSl:
    SQL-Statement: CREATE  INDEX "SEOSUBCO~001" ON "SEOSUBCO" ( "CLSNAME" , "CMPNAME" , "SCOTYPE"  )
    =============================================================================
    I wish to know how else can 1 work around this ABAP import phase with errors such as these? Is there a manual procedure I can perform for this phase during installations so to avoid these errors that come up. And then re-run the install that goes past this?
    Any help will be greatly appreciated.
    Thanks in advance.

    Hi
    Try increasing your shared pool size
    login to database level
    sqlplus "/as sysdba"
    >show parameter shared_pool_size;
    if the value is some thing aroung 150 to 200 MB increase it to 250MB
    >alter sytem set shared_pool_size=250M scope=both;
    Hope this will solve your problem
    Regards
    Uday

  • SAPup phase Error in EU_IMPORT

    Hi all,
    I am doing BW upgrade from 3.1 to 7.0. Now am in SAPup phase.
    As per prepare i create 8GB of tablespace for PSAPBAQ700
    Then i started the SAPup phase, it got stucked in EU_IMPORT1, then i checked logs it reported
    <b>" error message returned by DbSl:
    ORA-01658: unable to create INITIAL extent for segment in tablespace PSAPBAQ700
    DbSl Trace: ORA-1658 occurred when executing SQL statement (parse error offset=0)</b>
    <b>(DB) ERROR: DDL statement failed
    (CREATE TABLE "O2PAGINC~" ( "MASTERAPPL" VARCHAR2(30) DEFAULT ' ' NOT NULL , "MASTERPAGE" VA
    RCHAR2(70) DEFAULT ' ' NOT NULL , "INCLAPPL" VARCHAR2(30) DEFAULT ' ' NOT NULL , "INCLPAGE" V
    ARCHAR2(70) DEFAULT ' ' NOT NULL , "INDIRECT_USE" VARCHAR2(1) DEFAULT ' ' NOT NULL  ) TABLESP
    ACE PSAPBAQ700 STORAGE (INITIAL 0000000016K NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS
    2147483645 PCTINCREASE 0 ) )"</b>
    <b>DbSlExecute: rc = 99
      (SQL error 1658)</b>
    Then i extended tablespace to one more 8GB, now EU_IMPORT1 went without any problem, again it got stucked in EU_IMPORT2.
    Again i increased 5GB then EU_IMPORT2 phase went smoothly....now it got stucked in EU_IMPORT3 with same error.
    Pls give me some input on this
    Regards
    Karthik

    Hi,
    Refer to follownig link
    http://help.sap.com/saphelp_sm32/helpdata/en/35/28503fb088d25fe10000000a114084/content.htm
    Following two parameters may be useful
    File autoextend mode (autoextend)    -f tscreate -a|-autoextend
    File increment size in MB (incrsize)  -f tscreate -i|-incrsize (100 MB - 200 MB )
    Hope that helps.
    Regards
    Mr Kapadia

  • Install IDES ECC6- Abap Import phase error

    Hi all,
    I have seen many post on this error but I have not still understood why it happens.
    I have tried to install an IDES ECC6 on Windows 2003S 32 bit with 4gb of RAM on a VMWARE virtual machine.
    I have done all the preparation steps:
    1) adjust network performance
    2) set virtual memory as the installed RAM + 8GB
    3) set the HOSTS file with the IP address
    4) installed Java SDK with JAVA_HOME environment variable
    I have installed Oracle (delivered with the kit) and the patch and then started the SAPINST (under I386).
    In the APAB Import phase all the tasks (1 from 19) are stopped since Oracle is no more available.
    All the posts suggest to enlarge the shared_pool_size.
    But why this happens ?
    The install procedure should work without any Oracle parameter modification.
    Any idea ?
    Thank
    Andrea

    Hi
    Try increasing your shared pool size
    login to database level
    sqlplus "/as sysdba"
    >show parameter shared_pool_size;
    if the value is some thing aroung 150 to 200 MB increase it to 250MB
    >alter sytem set shared_pool_size=250M scope=both;
    Hope this will solve your problem
    Regards
    Uday

  • Xpra_execution phase error execution of report return code 12

    Hi,
    i am installing BI_CONT add on my ides system. 
    At phase xpra_execution its giving error "Execution of reports after put finished returncode 12". I have tried continuing 3 times.
    Program terminated (job: RDDEXECL, no.: 00174500
    See job log
    Execution of programs after import (XPRA)
    End date and time : 20081017002051
    job entries for RDDEXCEL:-
    Job started
    Step 001 started (program RDDEXECL, variant , user ID DDIC)
    All DB buffers of application server idesminda were synchronized
    Error Building the ENH TreeObject Type:XHObject Name:/POSDW/COND_TRANSBAL
    Function module CMMATGRP_O_WRITE_DOCUMENT deleted
    Saved
    ABAP/4 processor: CALL_FUNCTION_PARM_MISSING
    Job cancelled
    Along with that , it also giving an dump
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_MISSING', was
    not caught in
    procedure "OSOA_UPLOAD" "(FORM)", 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:
    When calling the function module "RSA1_DSOURCE_ALL_D_GET", one of the
    parameters
    needed according to the interface description was not specified.
    This parameter was "E_T_OHIECOM".
    Kindly provide the solution
    Regards
    Vikas

    Hi
    XPRA_EXECUTION terminates due to the following reasons:
    ○       TP_INTERFACE_FAILURE: The tp interface could not be called.
    ○       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
    ○       TP_STEP_FAILURE: tp step XPRA_EXECUTION could not be performed successfully. To find the cause of the error, read the method execution log. To view the cause of the error in the log, choose Goto ® Log ® Queue.
    ○       CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer file. For more information, read the SLOG log file.
    ○       CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding buffer file. For more information, read the SLOG log file.
    For more details on this,please refer to the link :
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/7e/c6c2ad98a711d2b429006094b9ea64/frameset.htm
    Alternately, you have to follow the following steps:
    unlock the shadow instance (cd /usr/sap/put/bin && ./SAPup unlockshd)
    logon as DDIC
    copy DDIC to a different user
    logon with the other user
    start transaction SE06 and make the system "changable"
    start transaction OSS1 -> Technical settings - Change - Save
    use SNOTE
    Apply SAP Note 1153235.
    Regards
    Chen

  • PREPARE_XPRA phase error during ST-PI upgrade

    Hi ,
    While upgrading the ST-PI from 2005_1_620 to 2008_1_620 patch 5 we are getting the error in the phase PREPARE_XPRA. The error text as below.
    Error in phase: PREPARE_XPRA
    Reason for error: TP_BUFFER_INCONSISTENCY
    Return code: 0008
    Error message: Pkgs. in queue don"t exist in the tp buffer (e.g.
    SAPKITLRB1)
    I have manually added the transports to buffer and re-tried the step again but no use. I have deleted the entries marked with '?' in PAT01, PAT03 tables and retried but no use again. The same process was successful in development system but giving error while doing in acceptance. Please help me in resolving the error.
    Regards,
    Anup

    Hi,
    In Se37,Use the function module OCS_RESET_QUEUE -> Single Test with the parameters IV_TOOL=3DSAINT, IV_FORCE=3DX
    Then delete all the files from \usr\sap\trans\tmp and make sure that there is no TP process process running in the system on OS level. If any process exist, please kill them.
    Then restart the import and you should be good to proceed.
    Also check if program RDDIMPDP and RDDNEWPP are scheduled and running.
    Hope this helps.
    Regards,
    Varun

  • System Copy -Solman 7.1 Adjust name table phase error

    Dear Experts,
    I am on way of performing the system copy for solman 7.1 from prod to dev system.We are encountering the error in the adjust name table phase .Below is the log :
    ERROR in initialization (can't get R/3-version)
    ERROR in initialization (can't get R/3-version)
    D:\usr\sap\\D00\log\SLOG00.LOG: No such file or directory
    rslgwr1(20): rstrbopen cannot open pre-existing SysLog file.
    D:\usr\sap\\D00\log\SLOG00.LOG: No such file or directory
    rslgwr1(11): rstrbopen cannot open SysLog file.
    SysLog:iE1020140515082322000000000000  this TTY           
          :                                                            0000
          :SCSA         4096                                              
    SysLog:hBZA20140515082322000000000000  this TTY           
          :                                                            0000
          :SVERS                                               dblink  1323
    OS:Windows 2008
    Database :Sybase Ase 15.7 ,and the weird thing is my SID is different .
    Appreciate your responses
    Thanks
    Asim

    Hi Asim,
    1.I was getting error at Abap phase load error .So i have merge the tsk & bak files by r3laod and manually set ign in tsk files .Should i change the ign status back to error.Is this could be the problem causing in adjusting table name phase.
    Status "ign" will ignore the object from being imported into the database. This may lead to inconsistency and loss of data.
    2.We have used abap export using Sap inst only .Will that not effect if using import by SWPM
    Actually SWPM also contains sapinst tool. But As I never never used this approach , I would suggest you to give a try and check.
    Else you may need to perform fresh export and then import using SWPM.
    Hope this helps.
    Regards,
    Deepak Kori

  • SAP NW04s: Import Abap Phase Error

    Hi
    i try to install sap nw04s with oracle 10g in Redhat 5 Environment.
    During Import Abap Phase: i got error:
    l attached the ERROR LOGS.
    SAPINST.DEV.LOG
    ERROR      2008-09-02 02:16:53
               CJSlibModule::writeError_impl()
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    TRACE      [iaxxejsbas.hpp:460]
               EJS_Base::dispatchFunctionCall()
    JS Callback has thrown unknown exception. Rethrowing.
    ERROR      2008-09-02 02:16:53 [iaxxgenimp.cpp:731]
               showDialog()
    FCO-00011  The step runMigrationMonitor 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|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    TRACE      [iaxxgenimp.cpp:719]
               showDialog()
    <html><head></head><body><p>An error occurred while processing service <b>SAP NetWeaver 2004s Support Release 2 > SAP Systems > Oracle > Central System > Central System Installation</b>. You may now</p><ul> <li>press <I>Retry</I> to repeat the current step.</li> <li>press the <I>View Log</I> button to get more information about the error.</li> <li>stop the task and continue with it later.</li></ul><p>Log files are written to <b>/tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS</b>.</p></body></html>
    TRACE      [iaxxgenimp.cpp:1155]
               showDialog()
    waiting for an answer from gui
    INFO       2008-09-02 02:17:21 [iaxxgenimp.cpp:782]
               showDialog()
    An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
    SAPINST.LOG
    WARNING 2008-09-02 02:16:53
    Execution of the command "/usr/java/j2sdk1.4.2_12/bin/java -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs /opt/sapdump/51032246_NW_exp/EXP1:/opt/sapdump/51032246_NW_exp/EXP2:/opt/sapdump/51032246_NW_exp/EXP3 -installDir /tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS -orderBy "" -r3loadExe /usr/sap/PBC/SYS/exe/run/R3load -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:
    java version "1.4.2_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
    Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
    Import Monitor jobs: running 1, waiting 1, completed 16, failed 0, total 18.
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 0, waiting 1, completed 16, failed 1, total 18.
    IMPORT.MONITOR.LOG
    WARNING 2008-09-02 02:16:53
    Execution of the command "/usr/java/j2sdk1.4.2_12/bin/java -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs /opt/sapdump/51032246_NW_exp/EXP1:/opt/sapdump/51032246_NW_exp/EXP2:/opt/sapdump/51032246_NW_exp/EXP3 -installDir /tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS -orderBy "" -r3loadExe /usr/sap/PBC/SYS/exe/run/R3load -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:
    java version "1.4.2_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
    Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
    Import Monitor jobs: running 1, waiting 1, completed 16, failed 0, total 18.
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 0, waiting 1, completed 16, failed 1, total 18.
    kinldy provide me solutions.........
    regards
    raghu

    hi!
    i attached SAPSSEXC.LOG
    (IMP) INFO: import of ENH_DY_SUBS completed (0 rows) #20080902010623
    (DB) INFO: ENH_DY_SUBS~0 created #20080902010623
    (DB) INFO: ENLFDIR created #20080902010623
    (RFF) ERROR: invalid checksum in data file "/opt/sapdump/51032246_NW_exp/EXP1/DATA/SAPSSEXC.001"
                 current table was "ENLFDIR"
    (DB) INFO: disconnected from DB
    /usr/sap/PBC/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/PBC/SYS/exe/run/R3load: END OF LOG: 20080902010623
    /usr/sap/PBC/SYS/exe/run/R3load: START OF LOG: 20080902014139
    /usr/sap/PBC/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    /usr/sap/PBC/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
    Compiled Aug 29 2006 07:46:52
    /usr/sap/PBC/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (DB) INFO: ENLFDIR deleted/truncated #20080902014139
    (RFF) ERROR: invalid checksum in data file "/opt/sapdump/51032246_NW_exp/EXP1/DATA/SAPSSEXC.001"
                 current table was "ENLFDIR"
    (DB) INFO: disconnected from DB
    /usr/sap/PBC/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/PBC/SYS/exe/run/R3load: END OF LOG: 20080902014139
    /usr/sap/PBC/SYS/exe/run/R3load: START OF LOG: 20080902020550
    /usr/sap/PBC/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    /usr/sap/PBC/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
    Compiled Aug 29 2006 07:46:52
    /usr/sap/PBC/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (DB) INFO: ENLFDIR deleted/truncated #20080902020551
    (RFF) ERROR: invalid checksum in data file "/opt/sapdump/51032246_NW_exp/EXP1/DATA/SAPSSEXC.001"
                 current table was "ENLFDIR"
    (DB) INFO: disconnected from DB
    /usr/sap/PBC/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/PBC/SYS/exe/run/R3load: END OF LOG: 20080902020551
    /usr/sap/PBC/SYS/exe/run/R3load: START OF LOG: 20080902020637
    /usr/sap/PBC/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    /usr/sap/PBC/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
    Compiled Aug 29 2006 07:46:52
    /usr/sap/PBC/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (DB) INFO: ENLFDIR deleted/truncated #20080902020637
    (RFF) ERROR: invalid checksum in data file "/opt/sapdump/51032246_NW_exp/EXP1/DATA/SAPSSEXC.001"
                 current table was "ENLFDIR"
    (DB) INFO: disconnected from DB
    /usr/sap/PBC/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/PBC/SYS/exe/run/R3load: END OF LOG: 20080902020637
    /usr/sap/PBC/SYS/exe/run/R3load: START OF LOG: 20080902021524
    /usr/sap/PBC/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    /usr/sap/PBC/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
    Compiled Aug 29 2006 07:46:52
    /usr/sap/PBC/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (DB) INFO: ENLFDIR deleted/truncated #20080902021525
    (RFF) ERROR: invalid checksum in data file "/opt/sapdump/51032246_NW_exp/EXP1/DATA/SAPSSEXC.001"
                 current table was "ENLFDIR"
    (DB) INFO: disconnected from DB
    /usr/sap/PBC/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/PBC/SYS/exe/run/R3load: END OF LOG: 20080902021525
    /usr/sap/PBC/SYS/exe/run/R3load: START OF LOG: 20080902021624
    /usr/sap/PBC/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    /usr/sap/PBC/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
    Compiled Aug 29 2006 07:46:52
    /usr/sap/PBC/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (DB) INFO: ENLFDIR deleted/truncated #20080902021624
    (RFF) ERROR: invalid checksum in data file "/opt/sapdump/51032246_NW_exp/EXP1/DATA/SAPSSEXC.001"
                 current table was "ENLFDIR"
    (DB) INFO: disconnected from DB
    /usr/sap/PBC/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/PBC/SYS/exe/run/R3load: END OF LOG: 20080902021625
    regards
    raghu

  • TEST IMPORT phase error?during importing the patches

    Dear All,
    i was importing the HR patches SAPKE60023,SAPKE60024,
    SAPKE60025,SAPKE60026.In between error display PHASE TEST IMPORT ?
    MESSAGE:
    Error occourred in TEST_IMPORT.
    All these 4 SP was in the queue.
    SAPKE60023:0004RC
    SAPKE60024:0004RC
    SAPKE60025:0008RC
    SAPKE60026:0004RC
    log files is attached.
    1 ETP199X######################################
    1 ETP152 TESTIMPORT
    1 ETP101 transport order     : "SAPKE60025"
    1 ETP102 system              : "MRP"
    1 ETP108 tp path             : "tp"
    1 ETP109 version and release : "372.04.29" "700"
    1 ETP198
    4 ETW000 R3trans.exe version 6.14 (release 700 - 14.04.08 - 10:31:00).
    4 ETW000 unicode enabled version
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 23.05.2008 - 03:54:38
    4 ETW000 control file:
    sappro\sapmnt\trans\tmp\SAPKKE60025.MRP
    4 ETW000 > #pid 6080 on sappro (APServiceMRP)
    4 ETW000 > testimport
    4 ETW000 > file='
    sappro\sapmnt\trans\data\RE60025.SAP'
    4 ETW000 > buffersync=no
    4 ETW000 >
    4 ETW000 R3trans was called as follows: R3trans.exe -w
    sappro\sapmnt\trans\tmp\SAPPE60025.MRP -u 1
    sappro\sapmnt\trans\tmp\SAPKKE60025.MRP
    4 ETW000 active unconditional modes: 1
    4 ETW000 Connected to DBMS = ORACLE --- dbs_ora_tnsname = 'MRP' --- SYSTEM = 'MRP'.
    4 ETW690 COMMIT "0" "0"
    4 ETW000  trace at level 1 opened for a given file pointer
    4 ETW000
    4 ETW000 ================== STEP 1 =====================
    4 ETW000 date&time        : 23.05.2008 - 03:54:39
    4 ETW000 function         : TESTIMPORT
    4 ETW000 data file        :
    sappro\sapmnt\trans\data\RE60025.SAP
    4 ETW000 buffersync       : NO
    4 ETW000 clients          : as exported
    4 ETW000 l.s.m.           : VECTOR
    4 ETW000 commit           : 100000
    4 ETW000 table cache      : dynamic
    4 ETW000
    4 ETW000 Character set on this machine : 2 byte unicode little endian.
    4 ETW000 Character set on the data file: ASCII (ISO 8859-1).
    4 ETW000 Data file is compressed with algorithm 'L'.
    4 ETW000 Export was executed on 20.12.2007 at 14:39:25 by c7eadm     
    3 ETW709 "700 "
    4 ETW000   with R3trans version: 20.07.06 - 17:34:00
    4 ETW000 Source System = AMD/Intel x86_64 with Linux on DBMS = ADABAS D --- DBNAME = 'C7E' --- SYSTEM = 'C7E'.
    4 ETW000
    4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd
    4 ETW000 lsm during export: ALL
    4 ETW000 texts in language i will be converted with codepage 1100
    4 ETW000 texts in language d will be converted with codepage 1401
    4 ETW000 texts in language c will be converted with codepage 1100
    4 ETW000 texts in language b will be converted with codepage 1100
    4 ETW000 texts in language a will be converted with codepage 1100
    4 ETW000 texts in language 8 will be converted with codepage 1500
    4 ETW000 texts in language 7 will be converted with codepage 1100
    4 ETW000 texts in language 6 will be converted with codepage 1401
    4 ETW000 texts in language 5 will be converted with codepage 1401
    4 ETW000 texts in language 4 will be converted with codepage 1401
    4 ETW000 texts in language 3 will be converted with codepage 8500
    4 ETW000 texts in language 2 will be converted with codepage 8600
    4 ETW000 texts in language 1 will be converted with codepage 8400
    4 ETW000 texts in language 0 will be converted with codepage 1500
    4 ETW000 texts in language W will be converted with codepage 1500
    4 ETW000 texts in language V will be converted with codepage 1100
    4 ETW000 texts in language U will be converted with codepage 1100
    4 ETW000 texts in language T will be converted with codepage 1610
    4 ETW000 texts in language S will be converted with codepage 1100
    4 ETW000 texts in language R will be converted with codepage 1500
    4 ETW000 texts in language Q will be converted with codepage 1401
    4 ETW000 texts in language P will be converted with codepage 1100
    4 ETW000 texts in language O will be converted with codepage 1100
    4 ETW000 texts in language N will be converted with codepage 1100
    4 ETW000 texts in language M will be converted with codepage 8300
    4 ETW000 texts in language L will be converted with codepage 1401
    4 ETW000 texts in language K will be converted with codepage 1100
    4 ETW000 texts in language J will be converted with codepage 8000
    4 ETW000 texts in language I will be converted with codepage 1100
    4 ETW000 texts in language H will be converted with codepage 1401
    4 ETW000 texts in language G will be converted with codepage 1700
    4 ETW000 texts in language F will be converted with codepage 1100
    4 ETW000 texts in language E will be converted with codepage 1100
    4 ETW000 texts in language D will be converted with codepage 1100
    4 ETW000 texts in language C will be converted with codepage 1401
    4 ETW000 texts in language B will be converted with codepage 1800
    4 ETW000 texts in language A will be converted with codepage 8700
    4 ETW000 trfunction = D (patch transport)
    3 ETW708 "000"
    4 ETW000 switching to selective language import
    4 ETW000 the following languages will be imported: DE
    4 ETW000 Used Commandfile SAPKE60025           (SAPUSER/1366)
    4 ETW000      ... ignoring such differences.
    4 ETW000   0 entries for E070 imported (SAPKE60025).
    4 ETW000      ... ignoring such differences.
    4 ETW000   0 entries for E071 imported (SAPKE60025          *).
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000 LANGSSFOHR_CMP_TCS lang R not imported.
    4 ETW000 E071-LOCKFLAGs 000002 - 000002 updated ('3', 1 entries).
    4 ETW690 COMMIT "128" "128"
    4 ETW000      ... ignoring such differences.
    4 ETW000      table STXFCONT: entry in DB is 32 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table REPOSRC: entry in DB is 176 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table REPOTEXT: entry in DB is 68 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table SEOCLASS: entry in DB is 32 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table SEOCLASSDF: entry in DB is 353 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table SEOCLASSEX: entry in DB is 88 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table SEOCOMPODF: entry in DB is 10548 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table SEOCOMPOEX: entry in DB is 88 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table SEOSUBCODF: entry in DB is 396 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table SEOSUBCOEX: entry in DB is 116 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table EUDB: entry in DB is 128 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table FUPARAREF: entry in DB is 228 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    2EETW165 Function "HRCCE_EXT_EMP_ATTR_CE (HRCCE_BI_CE|02)" does not fit into the existing function group "(HRCCE_CALENDAR_FUNCTIONS|05)".
    2 ETW167 Please transport the whole function group.
    2EETW165 Function "HRCCE_GET_EMP_ATTR_CE (HRCCE_BI_CE|03)" does not fit into the existing function group "(HRCCE_CALENDAR_FUNCTIONS|04)".
    2 ETW167 Please transport the whole function group.
    2EETW165 Function "HRCCE_GET_PERSONID (HRCCE_BI_CE|04)" does not fit into the existing function group "(HRCCE_CALENDAR_FUNCTIONS|06)".
    2 ETW167 Please transport the whole function group.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table SPROXDAT: entry in DB is 1036 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table SPROXHDR: entry in DB is 1640 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table SPROXLPT: entry in DB is 452 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table SOTR_HEAD: entry in DB is 185 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table CUS_ACTH: entry in DB is 65 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table CUS_ATRH: entry in DB is 61 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table ENHSPOTHEADER: entry in DB is 164 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table ENHSPOTCONTRACT: entry in DB is 160 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table STXL: entry in DB is 90 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table DSYS_PHCONT_CCD2: entry in DB is 76 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table DSYS_PHCONT_ECD2: entry in DB is 76 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table DSYS_PHCONT_ECI2: entry in DB is 76 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table ROOSFIELD: entry in DB is 124 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table VARID: entry in DB is 120 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table FPCONTEXT: entry in DB is 112 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table FPLAYOUT: entry in DB is 84 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table FPLAYOUTT: entry in DB is 64 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table TTREEP: entry in DB is 176 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table TTREE_APPL: entry in DB is 184 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T511: entry in DB is 87 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T512W: entry in DB is 184 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5G01: entry in DB is 25 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5G_NICLIM: entry in DB is 20 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5KTC: entry in DB is 25 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table LTDX: entry in DB is 144 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table OBJSL: entry in DB is 180 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T506D: entry in DB is 46 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T511K: entry in DB is 27 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T511P: entry in DB is 31 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    3WETW109 table "T52E_ARFC" does not exist in nametab.
    3WETW109 table "T52E_ARFCT" does not exist in nametab.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    3WETW109 table "T5BX2" does not exist in nametab.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5C2D: entry in DB is 44 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5G03: entry in DB is 17 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5G67: entry in DB is 19 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5GT2: entry in DB is 25 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5N1L: entry in DB is 32 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5N21: entry in DB is 31 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5N22: entry in DB is 24 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5N2O: entry in DB is 30 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T5S3N: entry in DB is 19 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T7IE3: entry in DB is 31 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T7IE4: entry in DB is 26 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      table T7KRTR: entry in DB is 5 bytes bigger than in file.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW000      ... ignoring such differences.
    4 ETW690 COMMIT "0" "128"
    4 ETW000 6801621 bytes read.
    4 ETW000 Transport overhead 27.5 %.
    4 ETW000 Data compressed to 9.2 %.
    4 ETW000 Duration: 3 sec (2267207 bytes/sec).
    3 ETW710 "0" "0"
    4 ETW000  [dev trc     ,00000]  Fri May 23 03:54:42 2008                         3256961  3.256961
    4 ETW000  [dev trc     ,00000]  Disconnecting from ALL connections:                   29  3.256990
    4 ETW000  [dev trc     ,00000]  Disconnecting from connection 0 ...                   35  3.257025
    4 ETW000  [dev trc     ,00000]  Closing user session (con_hdl=0,svchp=02283750,usrhp=022A9C88)
    4 ETW000                                                                             699  3.257724
    4 ETW000  [dev trc     ,00000]  Detaching from DB Server (con_hdl=0,svchp=02283750,srvhp=02294FC4)
    4 ETW000                                                                             854  3.258578
    4 ETW000  [dev trc     ,00000]  Now I'm disconnected from ORACLE                     774  3.259352
    4 ETW000  [dev trc     ,00000]  Disconnected from connection 0                       139  3.259491
    4 ETW000  [dev trc     ,00000]  statistics db_con_commit (com_total=3, com_tx=2)
    4 ETW000                                                                              64  3.259555
    4 ETW000  [dev trc     ,00000]  statistics db_con_rollback (roll_total=0, roll_tx=0)
    4 ETW000                                                                              66  3.259621
    4 ETW000 Disconnected from database.
    4 ETW000 End of Transport (0008).
    4 ETW000 date&time: 23.05.2008 - 03:54:42
    4 ETW000 3 warnings occured.
    4 ETW000 3 errors occured.
    1 ETP152 TESTIMPORT
    1 ETP110 end date and time   : "20080523035442"
    1 ETP111 exit code           : "8"
    1 ETP199 ######################################
    plz its urgent.....give me suggestion hoe to resolve this issue.

    Hi aadil mudassir .This known problem. Befor you applay SP you need to read -->
    Note 822379 - Known problems with Support Packages in SAP NW 2004s AS ABAP
    In this note for your problem :Symptom: If the Support Packages SAPKE60024 and SAPKE60025 are imported together in a queue, the TEST_IMPORT step returns an error for Support Package SAPKE60025. The test import log of SAPKE60025 displays the following error message:
    Function HRCCE_EXT_EMP_ATTR_CE (HRCCE_BI_CE 02) does not fit into the existing function group ((HRCCE_CALENDAR_FUNCTIONS 05))
               This error message recurs for two other function modules of the function groups HRCCE_BI_CE and HRCCE_CALENDAR_FUNCTIONS.
               Solution: You can ignore this error by choosing 'Extras'-> 'Ignore test-import error'.  The error will not occur during the later import.
    Regards.

  • JSPM phase error after JSPM SP update

    Good day
    I am experiencing the following problem.
    We want to upgrade JAVA SP5 to 7.
    1st step in JSPM is to update JSPM itself (ver 7.01.5.2  to  7.01.7.0). This happened without problem, and I restarted JSPM as instructed.
    Now, every time I start JSPM in order to load the remaining patches, it reports an error:
    An error occurred during the execution of the JSPM_MAIN phase.
    Cannot initialise application data. Could not determine if instance 53 on host solapp01 is running. Cannot find instance  with instance number 53 on host solapp01 in the cluster.
    The log file contains:
    Sep 24, 2010 4:26:22 PM [Info]: Checking status of instance 53 on host solapp01...
    Sep 24, 2010 4:26:22 PM [Error]: Exception has occurred during the execution of the phase.
    Sep 24, 2010 4:26:22 PM [Error]: Cannot find instance with instance number 53 on host solapp01 in the cluster.
    Sep 24, 2010 4:26:22 PM [Error]: Could not determine if instance 53 on host solapp01 is running.
    Sep 24, 2010 4:26:22 PM [Error]: Cannot initialize application data.
    Sep 24, 2010 4:26:22 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.
    Sep 24, 2010 4:26:22 PM [Info]: Start time: 2010/09/24 16:24:56.
    Sep 24, 2010 4:26:22 PM [Info]: End time: 2010/09/24 16:26:22.
    Sep 24, 2010 4:26:22 PM [Info]: Duration: 0:01:26.569.
    Sep 24, 2010 4:26:22 PM [Info]: Phase status is error.
    JSPM_MAIN_1_01.LOG: END
    The Java stack is up and running. System has been restarted just in case.
    Any ideas would be welcomed.
    Regards
    Derik

    Dear All,
    Please follow this procedure tosolve this problem and revert back with your feedback.
    Cannot initialise application data. Could not determine if instance 53 on host solapp01 is running. Cannot find instance with instance number 53 on host solapp01 in the cluster
    Actually this is happening because you production box is configured in cluster environment and inside your profile directory
    you have profiles(instance, default and startup) for cluster instance as well which is located at some other host and JSPM is searching but could not find.
    1. All you have to do to solve this is goto > cdpro > list all the files
    now carefully create one folder and move all the profiles related to DR server in that folder.
    Again start the JSPM and that prompt will not come.
    2. One more solution to this problem is apply patch using SDM.
    Hoipe it helps.
    Regards, Amber S

Maybe you are looking for

  • Canon CD Tray incompatible with Leopard?

    Hi, I'm a "happy" owner of Canon's iP4200 Pixma printer and I've occassionally used it's CD-Tray C for printing CD labels. This worked fine on my PC but ever since I got my Mac Mini with Leopard, I haven't been able to get it to work. Causal printing

  • How to share a folder with java? in netbios in windows

    hi. I want to write a programa that user can select a directory than click the share button and the directory will be shared to other pcs. the other pcs can acces this directory like \\servername\shareddirectory the question is this. how can i share

  • Spool generates empty pdf page?

    Hi all, I am writing to spool using new-page print on parameters p_parame after that I get the spool number for the generated spool and use the following function to generate a pdf file:     call function 'CONVERT_ABAPSPOOLJOB_2_PDF'          exporti

  • How do I run Win7 Startup Repair from USB to repair Bootcamp installation?

    I messed up my bootcamp partition after resizing the OSX partition to give it more space so I found this fix - http://mourougan.com/2013/06/22/repairing-boot-camp-after-creating-new-partition / The fix worked in that the windows partition now shows u

  • Otomatic set text and push button

    I want to ask one question about ASP.NET htmlparser. I want to go one url and i want to find textboxes and buton . After that i will set a value in this textbox and i will push the button.But i want to work this otomatically.I used agilepackage and i