PI 7.1 EHP1 Upgrade

Hi,
I was trying to find a guide that can help me with the installation or upgrade of a PI 7.1 SAP System to EHP1 PI 7.1 (I beilve that its 7.11 for EHP1)
I tired to find guide / notes for this but was in vain. My search is on ...Please let me know if you have any links documents anything regarding this topic
Rgds
aditya

Hi i was able to find the links here are they
https://websmp101.sap-ag.de/~sapidb/011000358700002005622008E Installation Guide
SAP Enhancement Package Installation for SAP NetWeaver
Process Integration 7.1
and
https://websmp101.sap-ag.de/~sapidb/011000358700002021642008E Installation GuideSAP Enhancement Package InstallationUsing SAP Enhancement Package Installer (SAPehpi)
hence closing the thread
Rgds
aditya

Similar Messages

  • Reporting authorization issue after BI 701 05 EHP1 upgrade

    Hello,
    We have recently upgraded our BI 7.0 to BI 701 EHP1 with 05 patch level. After this we had a problem with reporting authorizations for a report (query), which has created under Virtual Infoprovider.
    Earlier the report use to be execute perfectly with authorizations S_RS_ICUBE object with Act 03, Subobject DATA, but after upgrade to EHP1, while executing report its throwing a error pasted below.
    =============================================================================================
    "Diagnosis
    Errors occured while reading a VirtualProvider outside the BI system. Check whether the previous error messages contains any information about the possible cause of this error.
    It is possible that the error message can not be displayed because the error message class does not exist in the BI system. If this is the case, only the name of the error class and the message number are displayed. View the error class in the source system of the VirtualProvider.
    System Response
    Procedure
    Since the error is not necessarily in the BI system, there is no specific procedure for resolving it. With VirtualProviders, problems often occure with the connection to the system; these can lead to system termination. If the code for the VirtualProvider is not from the SAP, contact the relevant person to help resolve the issue.
    If an SQL error is listed in the previous message, see the procedure for SQL errors."
    ===============================================================================================
    After running st01 trace we identified the missing authorization is S_RS_ICUBE with Act 03, subobject DEFINATION.
    Here please tell why is the subobject check is performed to execute a report (query), as this is happening after EHP1 upgrade, so let me know if anyone had any clue on this ...
    Thanks

    Hi Martin,
    Thanks for reply.
    The assumption what you made are correct, but these are the possible reasons only. Is there any specific note or any info from sap that these changes came due to the new release change, so that i can tell my manager clearly.
    And I am not sure whether this is impacting the reports which using the VirtualProviders (Virtual CUBE) in place. If you could get bit more information that will be helpful...Thanks in advance.
    Sridhar

  • EHP1 upgrade of solution manager-any effects in landscape due to common SLD

    Hello All,
    We have ECC,BI,SRM,XI,EP,MAM and BD in our setup and yes of course Solution Manager dev and prod
    We have our SLD installed on solution manager production which is common for all the systems of the landscape
    Now we have performed EHP1 upgrade if Solution manager dev and now we are planning on solution manager production
    So just want to know,do you forsee any issues after we upgrade the solution manager production to EHP1 in respect to SLD or can there be any issues in the landscape because of this upgrade?
    Please let me know your suggestions
    Rohit

    > So just want to know,do you forsee any issues after we upgrade the solution manager production to EHP1 in respect to SLD or can there be any issues in the landscape because of this upgrade?
    The SLD is not affected.
    However, SolMan EHP1 requires a LOT of separate notes to be applied.
    Note 1172948 - SAP Solution Manager - Basic functions
    Depending on what scenarios you use, you will also need to upgrade ST-PI in the external systems before EWAs will be again correctly created.
    Markus

  • Hierarchy expand issue after EHP1 upgrade

    Hi,
    We had EHP1 upgrade in our BI system. After upgrade, when we are trying to open the hierarchy of period.
    it should open from TOTAL to Q1, Q2, Q3 and Q4. Also when we should try to open Q1 then it should open Jan, Feb and Mar.
    When i am trying to open the Q1, Insted of opening another column for Jan, Feb and Mar. It disappear the Q1 column from WB.
    I tried to execute the query separately and it is working fine. Created a another new WB and it is also working fine.
    Is there any one have such issue then please let me know whould could bea solution or any SAP Note ect?
    Regards
    Pankaj

    Hi Pankaj,
    I have also done the EHP1 upgrade and found the same issue....
    Please run the program SAP_DROP_TMPTABLES and delete the hierarchy temporary tables.....It will definately solve your problem...
    Please let me know in case of further clarifications...
    Thanks,
    Amit Kr.

  • EHP1 upgrade error in PREP_INPUT..phase

    Hello,
    I am doing EHP1 upgrade and getting error in EHPI during the PREP_INPUT/KX_CPYORG! phase.
    Below is the error:
    Severe error(s) occured in phase PREP_INPUT/KX_CPYORG!
    Last error code set: Cannot open '/usr/sap/<SID>/SYS/exe/run/dbatoolsora.lst': No such file or directory
    It complains about dabtoolsora.lst file not existing in /SYS/exe/run Dir. This is because our DB is in separate machine/host and the CI is in separate. Hence the file mentioned above only exist in */SYS/exe/run Dir of DB host.
    Can anyone please suggest what steps should be taken to resolve this issue? Do i need to copy that file manually to the CI host's */SYS/exe/run Directory and then repeat the EHPI steps again?
    Any help would be greatly appreciated. Thanks.

    I know this answer is too late for your question, but it's still the top google hit for this message, so I'm leaving this here for others.
    SUM still has this behavior as of 1.0 SP6.  One workaround is to copy dbatoolsora.lst from your DB server kernel directory, and create wrapper scripts which will SSH from the CI to the DB and run the brtools commands that SUM would want to run.
    Here's an example of such a script, for brtools:
    #!/bin/csh
    ssh $SAPDBHOST brtools $*
    So, you'd have a script like this for brarchive, brbackup, and the other br* tools mentioned in dbatoolsora.lst, each containing the name of the command to run on the db server.
    Be sure to look in dbatoolsora.lst for a list of other files it may expect to find.

  • SAP Components required for EHP1 Upgrade

    Hi Experts,
    I have started the process of downloading files for an EHP1 upgrade of our current BI System (ABAP Stack only, Netweaver 7), with a Target Stack of SPS07.
    Using the Maintenance Optimizer, I have selected the appropriate Kernel, SPAM Version and BI Content Patches and Iu2019m now in a position to download the SAP Components.
    I am a little confused as to the list of SAP Components that have been presented via the Maintenance Optimizer, which provides the following list:
    SAP BASIS
    File Name     Description     Version                         
    KB70015.SAR     Basis Support Package 15 for 7.00     SAP BASIS 7.00                         
    KB70016.SAR     Basis Support Package 16 for 7.00     SAP BASIS 7.00                         
    SAP BASIS
    File Name     Description     Version                         
    SAP_BASIS701.SAR     Attribute Change Package 04 for SAP_BASIS 701     SAP BASIS 7.01                         
    KB70107.SAR     Basis Support Package 0007 for 7.01     SAP BASIS 7.01                         
    KB70101.SAR     Basis Support Package 01 for 7.01     SAP BASIS 7.01                         
    KB70102.SAR     Basis Support Package 02 for 7.01     SAP BASIS 7.01                         
    KB70103.SAR     Basis Support Package 03 for 7.01     SAP BASIS 7.01                         
    KB70104.SAR     Basis Support Package 04 for 7.01     SAP BASIS 7.01                         
    KB70105.SAR     Basis Support Package 05 for 7.01     SAP BASIS 7.01                         
    KB70106.SAR     Basis Support Package 06 for 7.01     SAP BASIS 7.01                         
    K-701DHINSAPBASIS.SAR     SAP_BASIS 701 Upgrade     SAP BASIS 7.01                         
    SAP ABA
    File Name     Description     Version                         
    KA70107.SAR     ABA Support Package 0007 for 7.01     SAP ABA 7.01                         
    KA70101.SAR     ABA Support Package 01 for 7.01     SAP ABA 7.01                         
    KA70102.SAR     ABA Support Package 02 for 7.01     SAP ABA 7.01                         
    KA70103.SAR     ABA Support Package 03 for 7.01     SAP ABA 7.01                         
    KA70104.SAR     ABA Support Package 04 for 7.01     SAP ABA 7.01                         
    KA70105.SAR     ABA Support Package 05 for 7.01     SAP ABA 7.01                         
    KA70106.SAR     ABA Support Package 06 for 7.01     SAP ABA 7.01                         
    K-701DHINSAPABA.SAR     SAP_ABA 701 Upgrade     SAP ABA 7.01                         
    SAP BW
    File Name     Description     Version                         
    KW70107.SAR     BW Support Package 0007 for 7.01     SAP BW 7.01                         
    KW70101.SAR     BW Support Package 01 for 7.01     SAP BW 7.01                         
    KW70102.SAR     BW Support Package 02 for 7.01     SAP BW 7.01                         
    KW70103.SAR     BW Support Package 03 for 7.01     SAP BW 7.01                         
    KW70104.SAR     BW Support Package 04 for 7.01     SAP BW 7.01                         
    KW70105.SAR     BW Support Package 05 for 7.01     SAP BW 7.01                         
    KW70106.SAR     BW Support Package 06 for 7.01     SAP BW 7.01                         
    K-701DHINSAPBW.SAR     SAP_BW 701 Upgrade     SAP BW 7.01                         
    PI_BASIS
    File Name     Description     Version                         
    K-701DHINPIBASIS.SAR     PI_BASIS 701 Upgrade     PI_BASIS 7.01                         
    K-70107INPIBASIS.SAR     PI_BASIS Support Package 0007 for 7.01     PI_BASIS 7.01                         
    K-70101INPIBASIS.SAR     PI_BASIS Support Package 01 for 7.01     PI_BASIS 7.01                         
    K-70102INPIBASIS.SAR     PI_BASIS Support Package 02 for 7.01     PI_BASIS 7.01                         
    K-70103INPIBASIS.SAR     PI_BASIS Support Package 03 for 7.01     PI_BASIS 7.01                         
    K-70104INPIBASIS.SAR     PI_BASIS Support Package 04 for 7.01     PI_BASIS 7.01                         
    K-70105INPIBASIS.SAR     PI_BASIS Support Package 05 for 7.01     PI_BASIS 7.01                         
    K-70106INPIBASIS.SAR     PI_BASIS Support Package 06 for 7.01     PI_BASIS 7.01                         
    ST-PI
    File Name     Description     Version                         
    KITLRDA.SAR     ST-PI 2008_1_700: Add-On Installation     ST-PI 2008_1_700                         
    KITLRD1.SAR     ST-PI 2008_1_700: SP 0001     ST-PI 2008_1_700                         
    KITLRD2.SAR     ST-PI 2008_1_700: SP 0002     ST-PI 2008_1_700                         
    KITLRD3.SAR     ST-PI 2008_1_700: SP 0003     ST-PI 2008_1_700                         
    My confusion is that it doesnu2019t appear to be a full list, which is based on the assumption that I would have had to upgrade to the Latest SPu2019s, as viewed in the SLD first (see list below for reference)?
    Is there a requirement to upgrade to the latest set of SPu2019s first, or can I upgrade to EHP1 SPS07 just using the list provided via the Maintenance Optimizer?
    Our current SP levelu2019s:
    In BOLD -        Current SP/PL ,   Latest SP
    BI CONT 7.03                       8                  16
    6*PI_BASIS 2006_1_700            4            11
    SAP ABA 7.00          14          21
    SAP BASIS 7.00          14          21
    SAP BW 7.00          16          23
    ST-PI 2008_1_700          1          1
    VIRSANH 520_700          12          15
    Any help, much appreciated,
    Chris

    Hi,
    No it is not necessary to upgrade to the latest SPS of the current version first (NW 7.0) before upgrading to 7.01.
    All what it requires is a minimum SP/SPS level & you are already on that & MOPZ has therefore proposed only the files for 7.01
    SPS.
    - Regards, Dibya

  • Messages take a long time to open after EHP1 upgrade

    hi,
    We have recently upgraded our PI 7.0 to EHP1 and we find that it takes unusually long time in sxmb_moni to open up(view) messages, has anyone seen this before .
    Thank you
    Jonu Joy

    I'd suggest tracing system activity when this long runtime issue occurs, so you could know where this time is spent (db access ? etc) ... a plain SM50 call in parallel could do the trick if runtime is long enough !
    Chris

  • Error encountered in phase SHDINST_DB_PREP - EHP1 upgrade using EHPI.

    Hi Experts,
    I am currently in the configuration phase of Enterprise Portal upgrade from 700 to EHP1 then i got this error in phase SHDNST_DB_PREP, I am using OS platform Windows Server 2003; here is the message:
    On the EHPi GUI:
    Decide how you want to continue
    Checks after phase PREP_INSTALL/SHDINST_DB_PREP were negative!
    Last error code set: Process 'brconnect' exited with 5, see 'D:\EHPI\abap\log\SHDUSRCRE.LOG' for detai
    Trouble Ticket Generation
    A trouble ticket and an archive with all relevant log files have been generated. Trouble ticket: "D:\EHPI\abap\log\SAPehpi_troubleticket.log" Log archive: "D:\EHPI\abap\log\SAPehpi_troubleticket_logs.sar"
    Choose Action:
    Repeat phase SHDNST_DB_PREP to continue at the point it stopped.
    Restart the current module from the beginning
    Exit this program
    for SHDUSRCRE.LOG:
    SAPehpi> Starting subprocess brconnect with id 13588 at 20100816143027
    Environment: CLASSPATH=C:\oracle\CUSDEV01\102\jdbc\lib\ojdbc14.jar;
    Environment: JAVA_HOME=C:\j2sdk1.4.2_13-x64
    Environment: NLS_LANG=AMERICAN_AMERICA.UTF8
    Environment: ORACLE_HOME=C:\oracle\EP1\102
    Environment: ORACLE_SID=EP1
    Environment: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
    Environment: Path=E:\oracle\CUSPRD01\102\bin;C:\oracle\CUSDEV01\102\bin;C:\oracle\EP1\102\BIN;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Dell\SysMgt\oma\bin;C:\usr\sap\EP1\SYS\exe\uc\NTAMD64;C:\Program Files (x86)\Dell\SysMgt\oma\bin
    Environment: auth_shadow_upgrade=0
    Environment: dbms_type=ora
    Environment: dbs_ora_schema=SAPEP1
    Environment: dbs_ora_tnsname=EP1
    BR0801I BRCONNECT 7.00 (42)
    BR0280I BRCONNECT time stamp: 2010-08-16 14.30.28
    BR0301E SQL error -28003 at location crown_main-1, SQL statement:
    '/* BRCONNECT */ CREATE USER "SAPEP1SHD" IDENTIFIED BY "kXZvHmKI.42aB"'
    ORA-28003: password verification for the specified password failed
    ORA-20003: Password should contain at least one \
                  digit, one character and one punctuation
    BR1336I Creating database owner SAPEP1SHD failed
    BR0280I BRCONNECT time stamp: 2010-08-16 14.30.28
    BR0804I BRCONNECT terminated with errors
    Process with ID 15076 terminated with status 5
    Did you encounter this error? How can i solve it?
    Thanks a lot!
    Regards,
    Tony

    Hello Experts,
    I already solved the issue, just creating the user manually at command promp,
    the problem is that the password that SAP generated was not compatible or not acceptble to the system that is why i manually created the user:
    SQL> CREATE USER SAPEP1SHD IDENTIFIED BY kXZvHmKI_42aB;   - > correct one
    SQL> CREATE USER SAPEP1SHD IDENTIFIED BY kXZvHmKI.42aB;    - > incorrect; generated by the system
    Thanks & Regards,
    Tony

  • SAINT hanging after EHP1 upgrade

    Hi All,
    one more issue i am seeing that, i am unable to run SAINT after EHP1 updagrade, i called SAINT tcode and when i click on START then its hanging,, please suggest on this.
    thanks
    Venkata

    Hello Venkata, Have you executed SGEN post support pack upgrade ? if yes could you please do a quick check if some components and objects are still remaining which needs to be re-generated ?
    Hope it helps.
    Regards, Amber S
    Infosys Technologies Limited.
    Edited by: Amber S on Feb 23, 2010 10:41 AM

  • Job E2E_HK_CONTROLLER getting canceled daily after EHP1 upgrade

    Hi, All,
    We upgraded solman system to EHP1.Since then; this job is getting canceled daily with following error:
    Job Log:
    Job started
    Step 001 started (program E2E_HK_CONTROLLER, variant , user ID SMD_RFC)
    Internal session terminated with a runtime error (see ST22)
    Job cancelled
    ST22 Dump log shows time out dump
    Current patch level is 04
    Kindly suggest how can this be solved

    Hi,
    Details are:
    Runtime Errors         TIME_OUT
    Date and Time          07.01.2010 01:30:54
    Short text
         Time limit exceeded.
    What happened?
         The program "SAPLRRSI" has exceeded the maximum permitted runtime without
         interruption and has therefore been terminated.
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.
         Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
         keep them for a long time.
    Error analysis
        After a specific time, the program is terminated to make the work area
        available to other users who may be waiting.
        This is to prevent a work area being blocked unnecessarily long by, for
        example:
        - Endless loops (DO, WHILE, ...),
        - Database accesses with a large result set
        - Database accesses without a suitable index (full table scan)
        The maximum runtime of a program is limited by the system profile
        parameter "rdisp/max_wprun_time". The current setting is 3600 seconds. If this
    Roll.... 16192
    EM...... 594970672
    Heap.... 0
    Page.... 16384
    MM Used. 585663104
    MM Free. 9274032
    r and Transaction
    Client.............. 100
    User................ "SMD_RFC"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "4B446D5B2E061DFFE10000003630905C"
    Program............. "SAPLRRSI"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "PS1"
    Database Release.... 701
    Kernel Release...... 701
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "

  • Solman EHP1 upgrade Stack 20 - cannot log in to system

    Hi all,
    I am currently doing a patch of Stack 20 for solman EHP1.  I was able to create the queue, was able to continue until import proper phase 2. After a while, i cannot log on the system.
    CX_WB_ED_SYNTAX_ERROR is unknown. abap program SAPMSYST had to be terminated. status LIVE of the user interface SAPLSRABAX_EXC missing.
    also we found a deadlock in the ora alert trace file.
    here are the logs:
    SLOG0944.log
    ERROR SAPK-701DRINSAPBASIS SOL I 0012 20091027160822 SAPBASISUSER SAPBASIS     cbcsapsolm 20091027142413047  
    STOP  MAIN IMPORT          SOL I      20091027160831              SAPBASIS     cbcsapsolm 20091027142413047  
    ERROR: stopping on error 12 during MAIN IMPORT
    START INFORM SAP-SYSTEM OF SOL Q      20091027160831              SAPBASIS     cbcsapsolm 20091027142413047  
    START tp_getprots          SOL Q      20091027160831              SAPBASIS     cbcsapsolm 20091027142413047  
    WARNING: System SOL. Warning.        20091027161236 :
    WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.
          Please check that the R/3 system is running.
          Please check the system. Use transactions SM21, SM37, SM50.
    WARNING:       (This warning is harmless if no further warnings follow.)
    WARNING: System SOL. Warning.        20091027170810 :
    ERROR:       The following call returned with exit code -100:
    ERROR:         sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=SOL
    ERROR:       Background jobs cannot be started.
    ERROR:       Please check trace file dev_evt.
    WARNING:       (This warning is harmless if no further warnings follow.)
    STOP  imp all              SOL   7006 20091027170857              SAPBASIS     cbcsapsolm 20091027142413047  
    ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
    dev_evt
    Tue Oct 27 17:08:08 2009
    Trace File of External Event Raiser (Level=2, Append=0)
    EventID: SAP_TRIGGER_RDDIMPDP
    SAP message server host: cbcsapsolm
    SAP message server service (new): 3900
    SAP message server service (old): sapmsSOL
    MsIAttachEx: connect to cbcsapsolm / 3900
    NiIInit: allocated nitab (2048 at 0000000002980080)
    NiHsLInit: alloc host/serv bufs (100/100 entries)
    NiPGetNodeAddrList: got 1 interface(s) from operating system
              [0] IP-Address: 172.20.20.128
    NiHsLGetNodeAddr: got hostname 'cbcsapsolm' from operating system
    HN='cbcsapsolm.cbcmain.cbc.chinabank.ph'; Add[0]=172.20.20.128
    NiIGetNodeAddr: hostname 'cbcsapsolm' = addr 172.20.20.128
    NiIGetServNo: servicename '3900' = port 0F.3C/3900
    NiICreateHandle: hdl 0 state NI_INITIAL
    NiIInitSocket: set default settings for new hdl 0 / sock 1812 (I4; ST)
    NiIBlockMode: set blockmode for hdl 0 FALSE
    NiITraceByteOrder: CPU byte order: little endian, reverse network, low val .. high val
    NiIConnectSocket: hdl 0 is connecting to 172.20.20.128:3900 (timeout=5000)
    Tue Oct 27 17:08:09 2009
    SiPeekPendConn: connection of sock 1812 broke (10061-WSAECONNREFUSED: Connection refused)
    ***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2835]
    ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 / sock 1812
        (SI_ECONN_REFUSE/10061; I4; ST; 172.20.20.128:3900) [nixxi.cpp    2835]
    NiICloseHandle: closing initial hdl 0
    ERROR => MsIAttachEx: NiBufConnect to cbcsapsolm/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
    ERROR ***: MsAttach (host=cbcsapsolm, serv=3900), rc = -100
    MsIAttachEx: connect to cbcsapsolm / sapmsSOL
    NiHsLGetNodeAddr: found hostname 'cbcsapsolm' in cache
    NiIGetNodeAddr: hostname 'cbcsapsolm' = addr 172.20.20.128
    NiHsLGetServNo: got service name 'sapmsSOL' from operating system
    SN='sapmsSOL'; Port=0E.10/3600; PC=tcp
    NiIGetServNo: servicename 'sapmsSOL' = port 0E.10/3600
    NiICreateHandle: hdl 0 state NI_INITIAL
    NiIInitSocket: set default settings for new hdl 0 / sock 1800 (I4; ST)
    NiIBlockMode: set blockmode for hdl 0 FALSE
    NiIConnectSocket: hdl 0 is connecting to 172.20.20.128:3600 (timeout=5000)
    Tue Oct 27 17:08:10 2009
    SiPeekPendConn: connection of sock 1800 broke (10061-WSAECONNREFUSED: Connection refused)
    NiHsLGetServName: found port number 0E.10/3600 in cache
    NiIGetServName: port 0E.10/3600 = servicename 'sapmsSOL'
    ***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2835]
    ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 / sock 1800
        (SI_ECONN_REFUSE/10061; I4; ST; 172.20.20.128:3600) [nixxi.cpp    2835]
    NiICloseHandle: closing initial hdl 0
    ERROR => MsIAttachEx: NiBufConnect to cbcsapsolm/sapmsSOL failed (rc=NIECONN_REFUSED) [msxxi.c      652]
    ERROR ***: MsAttach (host=cbcsapsolm, serv=sapmsSOL), rc = -100
    alert_sol
    Tue Oct 27 16:08:17 2009
    ORA-00060: Deadlock detected. More info in file f:\oracle\sol\saptrace\usertrace\sol_ora_5280.trc.
    Tue Oct 27 16:08:20 2009
    Completed checkpoint up to RBA [0x5e7.2.10], SCN: 17756362
    Tue Oct 27 16:08:22 2009
    ORA-00060: Deadlock detected. More info in file f:\oracle\sol\saptrace\usertrace\sol_ora_188.trc.
    hope you can help!
    Many thanks!
    Edited by: Jeb Barrios on Oct 28, 2009 3:11 AM
    Edited by: Jeb Barrios on Oct 28, 2009 3:13 AM
    Edited by: Jeb Barrios on Oct 28, 2009 3:15 AM

    Hi,
    Based on my checks,  in my opinion its best to open an OSS msg, as most of the time it will require the message processor on SAP side to apply some internal tool to resolve this. Since it is a matter with package stuck scenario.
    You may want to open under BC-UPG-OCS
    Hope this helps.
    Cheers
    SH

  • 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 
    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

  • Upgrade from PI 7.0 SP18 to PI 7.1 EHP1

    Hi all,
                                                                                    I'm performing an Upgrade from Netweaver PI 7.0 SP18 to PI 7.1 EHP1.
    I've checked all the notes ragarding any known issuses about the process BUT....
    Here's the problem: in Phase TR_CMDIMPORT_PREPARE ( during the Support Package Import ) the upgrade stops with this error:
    ERROR: 339 errors detected during TR_CMDIMPORT_PREPARE.
           Errors are accumulated in file PCMDIMP.ELG.
    PCMDIMP.ELG shows problems related to R3trans version, but, as you can see, my version is newer:
    "2EETW000 import of new package definition (note 1089083 needs at least R3trans version 6.18, this is 6.19."
    What could possibly be wrong?
    Notice that in my download directory I've put:
    the latest Upgrade Correction ( NW711_19-10007578.SAR ).
    the latest Kernel ( 711 46 )
    the latest EHP1 Support Package ( 03 )
    the latest SAPup: 7.10/5 29.003 ( as suggested by note 1156185. I know it's 7.10, not 7.11 but the note it's clear on that. Anyway i tried, unsuccessfully, without the SUPup, so.... )
    I use the following media:
    NW PI 7.1 EHP1 Upgrade Master 51036470
    NW 7.11 IM/Kernel/TREX WIN x64, IA64 51036476
    NW AS ABAP 7.1 EHP1 Language 51036707
    I even tried to use the original Kernel from the DVD...
    Any suggestion?
    Thanks and Regards,
    Andrea
    P.S. Partial PCMDIMP.ELG  file :
      LIST OF ERRORS AND RETURN CODES  *******
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CMDFILE IMPORT ERRORS and RETURN CODE in SAPL-71101INPIBASIS.JIM
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "4"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CMDFILE IMPORT ERRORS and RETURN CODE in SAPL-71102INPIBASIS.JIM
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "4"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CMDFILE IMPORT ERRORS and RETURN CODE in SAPL-71103INPIBASIS.JIM
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2EETW000 import of new package definition (note 1089083 needs at least R3trans version 6.18, this is 6.19.
    2EETW000 import of new package definition (note 1089083 needs at least R3trans version 6.18, this is 6.19.
    2EETW000 import of new package definition (note 1089083 needs at least R3trans version 6.18, this is 6.19.
    2EETW000 import of new package definition (note 1089083 needs at least R3trans version 6.18, this is 6.19.
    1 ETP111 exit code           : "8"
    Edited by: Andrea Campo on Sep 23, 2009 2:37 PM
    Edited by: Andrea Campo on Sep 23, 2009 2:38 PM

    This is part of SAPL-71103INPIBASIS.JIM:-------
    4 EPU201XBEGIN OF SECTION BEING ANALYZED
    1 ETP199X######################################
    1 ETP179 CREATE COFILE FROM DATAFILE
    1 ETP101 transport order     : "SAPK-71103INPIBASIS"
    1 ETP102 system              : "JIM"
    1 ETP108 tp path             : "E:\usr\sap\JIM\upg\abap\exe\tp.EXE"
    1 ETP109 version and release : "375.32.47" "711"
    1 ETP198
    4 ETW000 E:\usr\sap\JIM\upg\abap\exe\R3trans.exe version 6.19 (release 711 -
    22.01.09 - 11:27:00).
    4 ETW000 unicode enabled version
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 23.09.2009 - 12:47:46
    4 ETW000 control file: E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
    4 ETW000 > #pid 4904 on srvsvi-w037v (APServiceJIM)
    4 ETW000 > createcofile
    4 ETW000 > file='E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP'
    4 ETW000 >
    4 ETW000 R3trans was called as follows: E:\usr\sap\JIM\upg\abap\exe\R3trans.exe -w
    E:\usr\sap\JIM\upg\abap\tmp\SAPL-71103INPIBASIS.JIM
    E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
    4 ETW000  trace at level 1 opened for a given file pointer
    4 ETW000
    4 ETW000 ================== STEP 1 =====================
    4 ETW000 date&time        : 23.09.2009 - 12:47:46
    4 ETW000 function         : CREATECOFILE
    4 ETW000 data file        : E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP
    4 ETW000 buffersync       : NO
    4 ETW000 clients          : default
    4 ETW000 commit           : -1
    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: 2 byte unicode big endian.
    4 ETW000 Data file is compressed with algorithm 'L'.
    4 ETW000 Export was executed on 01.07.2009 at 14:30:19 by k7dadm     
    3 ETW709 "711 "
    4 ETW000   with R3trans version: 22.01.09 - 11:27:00
    4 ETW000 Source System = Solaris on SPARCV9 CPU on DBMS = DB6 --- DB2DBDFT = 'K7D'
    --- SYSTEM = 'K7D'.
    4 ETW000
    4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd
    4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd (ISO-
    ZHTHKOROSLHRUKARHECSDEENFRELHUITJADAPLZFNLNOPTSKRUESTRFISVBGCASH)
    4 ETW000 lsm during export: ALL
    4 ETW000 datafile was created with 'langdeletions=no'.
    4 ETW000 trfunction = D (patch transport)
    3 ETW692 "SAPK-71103INPIBASIS "
    3 ETW708 "000"
    3 ETW695 "D"
    3 ETW694 "SAP       "
    3 ETW693 "SAP         "
    3 ETW696 "20090609"
    3 ETW713 "PI_BASIS Support Package 03 for 7.11                        "
    3 ETW691 "CORRMERGMERGEINFO PI_BASIS K7D 20090609 133924                           
    3 ETW707 "CORRMERGMERGEINFO PI_BASIS K7D 20090609 133924                           
    3 ETW691 "LIMUCLSD/SCMB/CA_DF_ATTR_QTY                                                                               
    3 ETW707 "R3TRCLAS/SCMB/CA_DF_ATTR_QTY"
    4 ETW000 809204 bytes read.
    4 ETW000 Transport overhead 17.1 %.
    4 ETW000 Data compressed to 7.0 %.
    4 ETW000 Duration: 0 sec (809204 bytes/sec).
    3 ETW710 "0" "0"
    4 ETW000 End of Transport (0000).
    4 ETW000 date&time: 23.09.2009 - 12:47:46
    1 ETP179 CREATE COFILE FROM DATAFILE
    1 ETP110 end date and time   : "20090923124746"
    1 ETP111 exit code           : "0"
    1 ETP199 ######################################
    1 ETP199X######################################
    1 ETP176 IMPORT OF COMMANDFILE ONLY
    1 ETP101 transport order     : "SAPK-71103INPIBASIS"
    1 ETP102 system              : "JIM"
    1 ETP108 tp path             : "E:\usr\sap\JIM\upg\abap\exe\tp.exe"
    1 ETP109 version and release : "375.32.47" "711"
    1 ETP198
    4 ETW000 E:\usr\sap\JIM\upg\abap\exe\R3trans.exe version 6.19 (release 711 -
    22.01.09 - 11:27:00).
    4 ETW000 unicode enabled version
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 23.09.2009 - 12:49:20
    4 ETW000 control file: E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
    4 ETW000 > #pid 7740 on srvsvi-w037v (jimadm)
    4 ETW000 > import
    4 ETW000 > buffersync=no
    4 ETW000 > file='E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP'
    4 ETW000 > continuation='E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS_#.SAP'
    4 ETW000 > client cascade yes
    4 ETW000 > repeatimport=yes
    4 ETW000 > importtruncated = yes
    4 ETW000 > including 'NOTHING'
    4 ETW000 R3trans was called as follows: E:\usr\sap\JIM\upg\abap\exe\R3trans.exe -u
    26 -w E:\usr\sap\JIM\upg\abap\tmp\SAPL-71103INPIBASIS.JIM
    E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
    4 ETW000 active unconditional modes: 26
    4 ETW000 Connected to DBMS = MSSQL ---  SERVER = 'SRVSVI-W037V' DBNAME = 'JIM' ---
    SYSTEM = 'JIM'.
    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.09.2009 - 12:49:20
    4 ETW000 function         : IMPORT
    4 ETW000 data file        : E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP
    4 ETW000 Continuation     : E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS_#.SAP
    4 ETW000 buffersync       : NO
    4 ETW000 clients          : cascade
    4 ETW000 repeatimport     : YES (corresponds to unconditional mode 1)
    4 ETW000 repeatclimport   : NO
    4 ETW000 c.s.i.           : NO
    4 ETW000 importtruncated  : YES (imported data may be destroyed!)
    4 ETW000 charsetadapt     : YES
    4 ETW000 def. charset     : WEUROPEAN
    4 ETW000 commit           : 100000
    4 ETW000 table cache      : dynamic
    4 ETW000 INCLUDING        : 'NOTHING'
    4 ETW000
    4 ETW000 rejected clients : 066
    4 ETW000
    4 ETW000 client cascade to: 000, 001
    4 ETW000 Character set on this machine : 2 byte unicode little endian.
    4 ETW000 Character set on the data file: 2 byte unicode big endian.
    4 ETW000 Data file is compressed with algorithm 'L'.
    4 ETW000 Export was executed on 01.07.2009 at 14:30:19 by k7dadm     
    3 ETW709 "711 "
    4 ETW000   with R3trans version: 22.01.09 - 11:27:00
    4 ETW000 Source System = Solaris on SPARCV9 CPU on DBMS = DB6 --- DB2DBDFT = 'K7D'
    --- SYSTEM = 'K7D'.
    4 ETW000
    4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd
    4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd (ISO-
    ZHTHKOROSLHRUKARHECSDEENFRELHUITJADAPLZFNLNOPTSKRUESTRFISVBGCASH)
    4 ETW000 lsm during export: ALL
    4 ETW000 datafile was created with 'langdeletions=no'.
    4 ETW000 trfunction = D (patch transport)
    4 ETW000 switching to selective language import
    4 ETW000 the following languages will be imported: DEI
    4 ETW000 Used Commandfile SAPK-71103INPIBASIS  (SAPUSER/140)
    4 ETW000 This is a patch transport.
    4 ETW000   1 entry for E070 updated  (SAPK-71103INPIBASIS).
    4 ETW000 140 entries for E071 inserted (SAPK-71103INPIBASIS *).
    4 ETW000   1 entry for E071K inserted (SAPK-71103INPIBASIS *).
    4 ETW000   1 entry for E071KF inserted (SAPK-71103INPIBASIS *).
    4 ETW000   1 entry for E070C inserted (SAPK-71103INPIBASIS).
    4 ETW000   1 entry for E07T updated  (SAPK-71103INPIBASIS *).
    4 ETW690 COMMIT "103098" "103098"
    3WETW000 different nametabs for table ENHOBJ (field ENHOBJTYPE).
    3WETW000 key field truncated
    3WETW000   Key field is not in NTAB.
    4 ETW000      table ENHOBJ: entry in DB is 2 bytes smaller than in file.
    4 ETW000      ... ignoring such differences.
    3WETW000 different nametabs for table TRDIR (field TROBJECT_TYPE).
    4 ETW000       Field is not in NTAB.
    3WETW000 different nametabs for table TRDIR (field TROBJECT_NAME).
    3WETW000 different nametabs for table SPROXREG (field IFR_IDEMPOTENT).
    [u2026]
    4 ETW000       Field is not in NTAB.
    4 ETW000      table SPROXREG: entry in DB is 2 bytes smaller than in file.
    4 ETW000      ... ignoring such differences.
    3 ETW677 "R3TRCLAS/SCMB/CL_DF_ARCH_ADD_TABLE" not imported in this step.
    2EETW000 import of new package definition (note 1089083 needs at least R3trans
    version 6.18, this is 6.19.
    [u2026]
    4 ETW000 no entries for PAK_RUNTIME_ENV will be imported in this step.
    3 ETW677 "R3TRDEVC/SCMB/FLOW" not imported in this step.
    2EETW000 import of new package definition (note 1089083 needs at least R3trans
    version 6.18, this is 6.19.
    3 ETW677 "R3TRDEVC/SCMB/FLOW_NET" not imported in this step.
    3 ETW677 "R3TRDSYSSIMGASC0TSAI" not imported in this step.
    3WETW000 different nametabs for table ENHLOG (field ENHTOOLTYPE).
    4 ETW000       Field is not in NTAB.
    4 ETW000      table ENHLOG: entry in DB is 20 bytes smaller than in file.
    4 ETW000      ... ignoring such differences.
    3 ETW677 "R3TRENHO/SCMB/ARC_DOCFLOW_ADD_TABLE" not imported in this step.
    3 ETW677 "R3TRFUGR/SCMB/DF_ARCHIVE" not imported in this step.
    3 ETW677 "R3TRFUGRRSC2" not imported in this step.
    2EETW000 import of new package definition (note 1089083 needs at least R3trans
    version 6.18, this is 6.19.
    4 ETW109 table "PAK_INTF_CONTENT" does not exist in nametab.
    4 ETW000 no entries for PAK_INTF_CONTENT will be imported in this step.
    3 ETW677 "R3TRPINF/SCMB/FLOW_API_DOCUMENT" not imported in this step.
    2EETW000 import of new package definition (note 1089083 needs at least R3trans
    version 6.18, this is 6.19.
    3 ETW677 "R3TRPINF/SCMB/FLOW_API_NET" not imported in this step.
    4 ETW000 SAPK-71103INPIBASIS  touched.
    4 ETW690 COMMIT "128" "103226"
    4 ETW000 809204 bytes read.
    4 ETW000 Transport overhead 17.1 %.
    4 ETW000 Data compressed to 7.0 %.
    4 ETW000 Duration: 0 sec (809204 bytes/sec).
    3 ETW710 "0" "0"
    4 ETW000
    4 ETW000 Summary:
    4 ETW000
    4 ETW000   1 COMML imported.
    4 ETW000   1 COMMT imported.
    4 ETW000 Totally 2 Objects imported.
    4 ETW000
    4 ETW000 103226 bytes modified in database.
    4 ETW000  [dev trc     ,00000]  Disconnecting from ALL connections:              
    264239  0.264239
    4 ETW000  [dev trc     ,00000]  Disconnected from connection 0                     
    4041  0.268280
    4 ETW000  [dev trc     ,00000]  statistics db_con_commit (com_total=3, com_tx=3)
    4 ETW000                                                                               
    31  0.268311
    4 ETW000  [dev trc     ,00000]  statistics db_con_rollback (roll_total=0,
    roll_tx=0)
    4 ETW000                                                                               
    23  0.268334
    4 ETW000 Disconnected from database.
    4 ETW000 End of Transport (0008).
    4 ETW000 date&time: 23.09.2009 - 12:49:20
    4 ETW000 34 warnings occured.
    4 ETW000 4 errors occured.
    1 ETP176 IMPORT OF COMMANDFILE ONLY
    1 ETP110 end date and time   : "20090923124920"
    1 ETP111 exit code           : "8"
    1 ETP199 ######################################
    1 ETP199X######################################
    1 ETP176 IMPORT OF COMMANDFILE ONLY
    1 ETP101 transport order     : "SAPK-71103INPIBASIS"
    1 ETP102 system              : "JIM"
    1 ETP108 tp path             : "E:\usr\sap\JIM\upg\abap\exe\tp.exe"
    1 ETP109 version and release : "375.32.47" "711"
    1 ETP198
    4 ETW000 E:\usr\sap\JIM\upg\abap\exe\R3trans.exe version 6.19 (release 711 -
    22.01.09 - 11:27:00).
    4 ETW000 unicode enabled version
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 23.09.2009 - 13:57:11
    4 ETW000 control file: E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
    4 ETW000 > #pid 5540 on srvsvi-w037v (jimadm)
    4 ETW000 > import
    4 ETW000 > buffersync=no
    4 ETW000 > file='E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP'
    4 ETW000 > continuation='E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS_#.SAP'
    4 ETW000 > client cascade yes
    4 ETW000 > repeatimport=yes
    4 ETW000 > importtruncated = yes
    4 ETW000 > including 'NOTHING'
    4 ETW000 R3trans was called as follows: E:\usr\sap\JIM\upg\abap\exe\R3trans.exe -u
    26 -w E:\usr\sap\JIM\upg\abap\tmp\SAPL-71103INPIBASIS.JIM
    E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
    4 ETW000 active unconditional modes: 26
    4 ETW000 Connected to DBMS = MSSQL ---  SERVER = 'SRVSVI-W037V' DBNAME = 'JIM' ---
    SYSTEM = 'JIM'.
    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.09.2009 - 13:57:11
    4 ETW000 function         : IMPORT
    4 ETW000 data file        : E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP
    4 ETW000 Continuation     : E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS_#.SAP
    4 ETW000 buffersync       : NO
    4 ETW000 clients          : cascade
    4 ETW000 repeatimport     : YES (corresponds to unconditional mode 1)
    4 ETW000 repeatclimport   : NO
    4 ETW000 c.s.i.           : NO
    4 ETW000 importtruncated  : YES (imported data may be destroyed!)
    4 ETW000 charsetadapt     : YES
    4 ETW000 def. charset     : WEUROPEAN
    4 ETW000 commit           : 100000
    4 ETW000 table cache      : dynamic
    4 ETW000 INCLUDING        : 'NOTHING'
    4 ETW000
    4 ETW000 rejected clients : 066
    4 ETW000
    4 ETW000 client cascade to: 000, 001
    4 ETW000 Character set on this machine : 2 byte unicode little endian.
    4 ETW000 Character set on the data file: 2 byte unicode big endian.
    4 ETW000 Data file is compressed with algorithm 'L'.
    4 ETW000 Export was executed on 01.07.2009 at 14:30:19 by k7dadm     
    3 ETW709 "711 "
    4 ETW000   with R3trans version: 22.01.09 - 11:27:00
    4 ETW000 Source System = Solaris on SPARCV9 CPU on DBMS = DB6 --- DB2DBDFT = 'K7D'
    --- SYSTEM = 'K7D'.
    4 ETW000
    4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd
    4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd (ISO-
    ZHTHKOROSLHRUKARHECSDEENFRELHUITJADAPLZFNLNOPTSKRUESTRFISVBGCASH)
    4 ETW000 lsm during export: ALL
    4 ETW000 datafile was created with 'langdeletions=no'.
    4 ETW000 trfunction = D (patch transport)
    [u2026]
    roll_tx=0)
    4 ETW000                                                                               
    23  0.228932
    4 ETW000 Disconnected from database.
    4 ETW000 End of Transport (0008).
    4 ETW000 date&time: 23.09.2009 - 13:57:11
    4 ETW000 34 warnings occured.
    4 ETW000 4 errors occured.
    1 ETP176 IMPORT OF COMMANDFILE ONLY
    1 ETP110 end date and time   : "20090923135712"
    1 ETP111 exit code           : "8"
    1 ETP199 ######################################
    4 EPU202XEND OF SECTION BEING ANALYZED

  • EP7 upgrade to EHp1

    Hi Experts,
    Currently we have EP7.0(JAVA stack) with SP15 landscape. We are planning to upgrade EHP1 on current system.I went to the SAP standard EHP1 upgrade document but I did not get exact.Do you have an experiance how to upgrade and steps
    What are the prerequisites?
    How can i upgrade steps and etc..?
    - Jim

    Hi Jim,
    I understand that performing EHP upgrade for the first time can seem a tricky job, but believe me it is not such a difficult job.
    First, ensure you have the EHP guides:
    http://service.sap.com/instguides --> SAP Netweaver --> SAP Netweaver 7.0 (2004s) --> Installation --> Enhancement Package Installation on SAP NW 7.0 Systems. From this page, download "SAP Enhancement Package Installation on Java Systems (using SAPehpi) " for your OS and DB combination.
    Download the EHP material DVDs as well as the EHP installer package. The DVDs are listed either in the EHP installation guiide or in the master guide for 7.0 EHP1 Also, download all the latest available Support pack files from service marketplace for 7.0 EHP1 components.
    As per the guide, simply follow the preparation steps and the installation steps. These are not difficult and can be performed easily. The guides are very good and hardly any doubts can come up.
    Make sure your DB has sufficient free space (given in guide), extract the packages, etc. and start the ehpi installer. All these steps are given in the guide and are well explained.
    Regards,
    Shitij

  • Solution Manager Upgrade to EHP1 7.01

    Hi
    Need some help. Could you please share  upgrade doc/exp with me, we are planning for upgrade solution manager from sp17 to sp19.
    Stack level 18 or 19 is the part of  EHP1 of Solution Manager version 7.01.
    What is the process to upgrade the support pack to sp level 19? i have no exp to upgrade to EHP1 level..Any difference ?
    Thanks in advance
    Amar

    Hi Amarjit,
    Solution manager upgrade to EHP1 is same like other stack upgrade. You can do it using SAINT/JSPM. But only thing you need is good preparation.
    Check upgrade guide on http://service.sap.com/solutionmanager.
    Also, check SAP  Note 1276895 - Add. info. about Upgrading to SAP Solution Manager 7.0 EHP1 and SAP Note 1169247 - Enhancements to Solution Manager 7.0 EHP1 upgrade
    Thanks
    Sunny

Maybe you are looking for

  • How to use java code in my forms.................

    Hi All, I want to use the below java code in my form 6i ..but don't know how???????? related function is also given below.......... Any idea .......Please Thanks Harry..... import java.awt.*; import javax.swing.*; import java.awt.event.*; import java

  • Multicolored Wheel and iMac Frozen

    Hi! I've bought a new iMac on May 2014. I've made a complete migration from my previous iMac with which I've never had any problem. My new iMac ( 21.5 " with 16Go RAM ) sometimes blocks completely after the Multicolored wheel appears. I never seen th

  • Missing podcast files in iTunes

    I probably didn't do this right, but I changed a video file into a podcast by right clicking and choosing info and changing the media kind to podcast (from movie). It does not show up and is completely missing now in itunes including trying to re-imp

  • Backing up during import with Vista

    When I import my images and enable the ":backup to second location"  feature, the backup always fails.  The import to the main disk is just fine, but afterwards I get a message saying "the following files could not be backed up...."   all of them.  I

  • X-Fi Mode switch

    Anyone know if there's a command line you can add when launching a program so it will automatically switch modes? For instance, when i run iTunes it'll switch to Entertainment mode and when i play a game it'll switch to Game mode.