ST02 shows multiple servers after heterogenous system copy

We're facing a strange behaviour in ST02 after a system copy using MaxDB backup/restore with SWPM (backup was from our production system). When we click on history, no data is shown:
We have to click on "-> Server", then the data is shown:
Does anyone know how to make history work?

Hello Alwina,
Thanks for the help.
Mine is EHP7 NW 7.4, standard system, cent serv instance(Mes Serv & Enqueue server), primary app server (Dia Bg Up Spo) runs on the single host along with Oracle DB 11.2.0.4.
In my rest of the systems also I have the same notations, server name its in upper case and hostname is in lower case (ofcourse they are of other netweaver release) for SM51.
niping results
Hostname/Nodeaddr verification:
===============================
Hostname of local computer: EUSAPADHR01                      (NiMyHostName)
FQHN of local computer: EUSAPADHR01.dfs                      (NiGetOwnFQDN)
Lookup of hostname: EUSAPADHR01                              (NiHostToAddr)
    --> IP-Addr.: 10.170.83.88
Lookup of IP-Addr.: 10.170.83.88                             (NiAddrToHost)
    --> Hostname: eusapadhr01.abc
Lookup of hostname: EUSAPADHR01                              (NiHostToAddr)
    --> IP-Addr.: 10.170.83.88
Lookup of IP-Addr.: 10.170.83.88                             (NiAddrToHost)
    --> Hostname: eusapadhr01.abc
Yes initially it gives 8 characters in the text.
But in the actual values it is like eusapadh_HRP_40..
Hope you understand my case.
Ok so implementing the note would fix this ST02 history issue - confirm?

Similar Messages

  • Heterogeneous system copy. Error in SMIGR_CREATE_DDL

    Hello!
    I perform a heterogeneous system copy of RHEL5/Oracle11/ERP6/0 > RHEL6/MaxDB/ERP6.0
    I use the "System Copy Guide for SAP Systems Based on NW 7.0 SR3 ABAP + Java". At the stage "4.2 Generating DDL" statements is a problem. I'm doing "Call transaction SE38 and run the program SMIGR_CREATE_DDL."
    But i get error:
    Runtime Errors         DATASET_NOT_OPEN
    Exception              CX_SY_FILE_OPEN_MODE
    Date and Time          20.09.2011 12:16:01
    Short text
         File "/EXPORT_DDL/SQLFiles.LST" is not open.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "CL_SMIGR_DDL==================CP" had to be
          terminated because it has
         come across a statement that unfortunately cannot be executed.
    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
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_FILE_OPEN_MODE', was not
         caught in
        procedure "WRITE_DDL_TO_FILE" "(METHOD)", 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 accessing the file "/EXPORT_DDL/SQLFiles.LST", the system recognized that
         this file is
        not open. Therefore, the file cannot be accessed.
    How to correct the error
        Before the first access, the file must be opened using the ABAP language
         element "OPEN DATASET '/EXPORT_DDL/SQLFiles.LST'" and after the last access,
         it must be
        closed using the language element "CLOSE DATASET '/EXPORT_DDL/SQLFiles.LST'".
        If the error occurred in your own ABAP program or in an SAP
        program you modified, try to remove the error.
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "DATASET_NOT_OPEN" "CX_SY_FILE_OPEN_MODE"
       "CL_SMIGR_DDL==================CP" or "CL_SMIGR_DDL==================CM003"
       "WRITE_DDL_TO_FILE"
       If you cannot solve the problem yourself and want to send an error
       notification to SAP, include the following information:
       1. The description of the current problem (short dump)
          To save the description, choose "System->List->Save->Local File
       (Unconverted)".
    I forgot something to do?

    >      File "/EXPORT_DDL/SQLFiles.LST" is not open.
    Make sure the user <sid>adm is permitted to write to that directory.
    Markus

  • Activating data in DSO got dump SAPSQL_EMPTY_TABNAME after BW system copy

    Hi all,
    We had an issue after system copy.
    After a system copy the data in the standard DSOs(all of them) cannot be activated. The DOSs themselves are active, the transformations are active but if one attempts to load data and activate u2013 it does not work. The job terminates with shortdump SAPSQL_EMPTY_TABNAME.
    Found the issue is caused by u201Cmore than one versionu201D of the change log.
    We tried the Program RSAR_RSTSODS_CHANGELOG_VRS but it didn't work.
    We had the solution like this:
    After activating the DSO itself(the object) using RSDG_ODSO_ACTIVATE the issue disappears and the data can be activated. Issue also disappears. BUT Drawback: Activating the DSO causes the transformations to deactivate.Then we used the program RSDG_TRFN_ACTIVATE to activate all transformations. And then the issue disappeared.
    Want to know what the root cause for this. From some SDN threads, mentioned BDLS job in the post refresh steps are not correctly done during system copy may cause this issue. How did the BDLS run wrongly cause this issue? And what is the exact correct way? We ran BDLS for each source systems inlcuding the target refreshed BW system itself by the default selection - conversion of Client-Dependent and Client-Independent Tables; because we used database copy
    for the system refresh.
    We also restored all source systems in RSA1 inlcuding the refreshed BW system own in the post-refresh steps.
    Thank you very much for your information and suggestion.
    Heming

    Hi Arun, as you say two change log tables it´s strange. In fact in my opinion it´s not right but the problem is that the second change log table appears after executing std SAP report RSDG_ODSO_ACTIVATE in order to be able to activate the DSO. So the solution provided by SAP it works but i´m not sure if the right one. Besides this the original change log table is full of data while the second one is empty... for new loads which are gonna a be filled  by the activation process ? I suppose the second one... will this have some impact with the data stored in the first one... not in theory but.... i do not feel confortable with the consequences of this report.
    And the most important, it seems that the reason why the DSO and the change log table had problems is due to a some problems or missing steps after executing the BDLS after BW system refresh but nobody can confirm this point...
    So, i´ve been able to solve the issue but now i have two change log tables for the same DSO.
    Anybody has the same situation after executing the above mentioned SAP std report ?
    Regards,
    Joaquin Casas Baca-Castex

  • Error during Heterogeneous System Copy -  Phase 18 Import ABAP

    Hello gurus,
    I´m facing an error during the Target Installation in a Heterogeneous System Copy (Migration). The system SAP is a SAP ECC 6.0 SR3 (Unicode and Abap+Java).
    Source server:
    Operation System:  Windows 2003 Server x64
    Database: SQL Server 2008 SP01
    Target server:
    Operation System:  Red Hat Enterprise Linux (RHEL) X64
    Database: Oracle DB 10.2g (10.2.0.4)
    I already did the all procedures in export database and all that looks fine!
    At this point I´m running the system copy procedure through SAPInst on target server (RHEL / Oracle) but in phase 18 - Import ABAP the sapinst stops... (by the way in procedure bar, I can see "Import Monitor jobs: running 0, waiting 1, completed 0, failed 18, total 19")
    I checked three log files (sapinst_dev.log ; sapinst.log ; SAPSDIC.log):
    SAPSDIC.log:
    /usr/sap/QAS/SYS/exe/run/R3load: START OF LOG: 20100820145140
    /usr/sap/QAS/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
    /usr/sap/QAS/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
    Compiled Jan 23 2008 17:39:05
    /usr/sap/QAS/SYS/exe/run/R3load -ctf I /software/export_preparation/ABAP/DATA/SAPSDIC.STR /tmp/sapinst_instdir/NW04S/LM/COPY/ORA/SYSTEM/CENTRAL/AS/DDLORA.TPL SAPSDIC.TSK ORA -l SAPSDIC.log
    (TPL) ERROR: unknown template variable "compress"
    /usr/sap/QAS/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/QAS/SYS/exe/run/R3load: END OF LOG: 20100820145140

    Hi Volker,
    > (TPL) ERROR: unknown template variable "compress"
    > This message looks like the DDLORA.TPL contains stuff that should not belong there.
    > Can you attach the DDLORA.TPL.
    > There are some bugs with SMIGR_CREATE_DDL, but they are mostly not related to oracle.
    prikey: AFTER_LOAD ORDER_BY_PKEY
    seckey: AFTER_LOAD
    cretab: CREATE TABLE &tab_name&
            ( /{ &fld_name& &fld_desc& /-, /} )
            TABLESPACE &tablespace&
            &compress&
            &lob_cache&
            STORAGE (INITIAL     &init&
                     NEXT        &next&
                     MINEXTENTS  &minext&
                     MAXEXTENTS  &maxext&
                     PCTINCREASE &pctinc& )
    drptab: DROP TABLE &tab_name&
    crepky: CREATE UNIQUE INDEX &pri_key&
            ON &tab_name&
            ( &key_fld& /-, )
            TABLESPACE &tablespace&
            STORAGE (INITIAL     &init&
                     NEXT        &next&
                     MINEXTENTS  &minext&
                     MAXEXTENTS  &maxext&
                     PCTINCREASE &pctinc& )
                     NOLOGGING
                     COMPUTE STATISTICS ;
            ALTER INDEX &pri_key& LOGGING
    drppky: DROP INDEX &pri_key&
    creind: CREATE &unique& INDEX &ind_name&
            ON &tab_name&
            ( /{ &fld_name& /-, /} )
            TABLESPACE &tablespace&
            STORAGE (INITIAL     &init&
                     NEXT        &next&
                     MINEXTENTS  &minext&
                     MAXEXTENTS  &maxext&
                     PCTINCREASE &pctinc& )
                     NOLOGGING
                     COMPUTE STATISTICS ;
            ALTER INDEX &ind_name& LOGGING
    drpind: DROP INDEX &ind_name&
    crevie: CREATE VIEW &view_name&
            ( /{ &fld_name& /-, /} )
            AS &query&
    drpvie: DROP VIEW &view_name&
    trcdat: TRUNCATE TABLE &tab_name&
    deldat: DELETE FROM &tab_name& &where&
    negtab: LICHECK MLICHECK
    negdat: LICHECK MLICHECK
    negind: LICHECK0 MLICHECK0 LICHECK0 MLICHECK0
    negvie:
    negcpr:ARFCSSTATE ARFCSDATA ARFCRSTATE TRFCQDATA TRFCQIN TRFCQOUT TRFCQSTATE QRFCTRACE QRFCLOG
    table storage parameters
    loc: APPL0 PSAPSR3                 0000
         APPL1 PSAPSR3                 0000
         APPL2 PSAPSR3                 0000
         CLUST PSAPSR3                 0000
         DDIM  PSAPSR3                 0000
         DFACT PSAPSR3                 0000
         DODS  PSAPSR3                 0000
         POOL  PSAPSR3                 0000
         SDIC  PSAPSR3                 0  
         SDOCU PSAPSR3                 0000
         SLDEF PSAPSR3700              0000
         SLEXC PSAPSR3700              0000
         SLOAD PSAPSR3                 0000
         SPROT PSAPSR3                 0000
         SSDEF PSAPSR3700              0000
         SSEXC PSAPSR3700              0000
         SSRC  PSAPSR3                 0000
         TEMP  PSAPSR3                 0000
         USER  PSAPSR3USR              0000
         USER1 PSAPSR3USR              0000
    sto: 0  0000000016K 0000000040K 0000000001 2147483645
         1  0000000016K 0000000160K 0000000001 2147483645
         10 0000000016K 0000655360K 0000000001 2147483645
         11 0000000016K 0001310720K 0000000001 2147483645
         12 0000000016K 0002621440K 0000000001 2147483645
         13 0000000016K 0005242880K 0000000001 2147483645
         14 0000000016K 0010485760K 0000000001 2147483645
         2  0000000016K 0000000640K 0000000001 2147483645
         3  0000000016K 0000002560K 0000000001 2147483645
         4  0000000016K 0000010240K 0000000001 2147483645
         5  0000000016K 0000020480K 0000000001 2147483645
         6  0000000016K 0000040960K 0000000001 2147483645
         7  0000000016K 0000081920K 0000000001 2147483645
         8  0000000016K 0000163840K 0000000001 2147483645
         9  0000000016K 0000327680K 0000000001 2147483645
    index storage parameters
    loc: APPL0 PSAPSR3                 0000
         APPL1 PSAPSR3                 0000
         APPL2 PSAPSR3                 0000
         CLUST PSAPSR3                 0000
         DDIM  PSAPSR3                 0000
         DFACT PSAPSR3                 0000
         DODS  PSAPSR3                 0000
         POOL  PSAPSR3                 0000
         SDIC  PSAPSR3                 0  
         SDOCU PSAPSR3                 0000
         SLDEF PSAPSR3700              0000
         SLEXC PSAPSR3700              0000
         SLOAD PSAPSR3                 0000
         SPROT PSAPSR3                 0000
         SSDEF PSAPSR3700              0000
         SSEXC PSAPSR3700              0000
         SSRC  PSAPSR3                 0000
         TEMP  PSAPSR3                 0000
         USER  PSAPSR3USR              0000
         USER1 PSAPSR3USR              0000
    sto: 0  0000000016K 0000000040K 0000000001 2147483645
         1  0000000016K 0000000080K 0000000001 2147483645
         10 0000000016K 0000163840K 0000000001 2147483645
         11 0000000016K 0000327680K 0000000001 2147483645
         12 0000000016K 0000655360K 0000000001 2147483645
         13 0000000016K 0001310720K 0000000001 2147483645
         14 0000000016K 0002621440K 0000000001 2147483645
         2  0000000016K 0000000160K 0000000001 2147483645
         3  0000000016K 0000000640K 0000000001 2147483645
         4  0000000016K 0000002560K 0000000001 2147483645
         5  0000000016K 0000005120K 0000000001 2147483645
         6  0000000016K 0000010240K 0000000001 2147483645
         7  0000000016K 0000020480K 0000000001 2147483645
         8  0000000016K 0000040960K 0000000001 2147483645
         9  0000000016K 0000081920K 0000000001 2147483645

  • Symbolic link error when exporting during heterogeneous system copy

    My enviroment is ECC6.0/Oracle 10.2.0.2/SUN Solaris 10 . I'm performing  heterogeneous system copy to Oracle 10.2.0.2/AIX 6.1 enviroment.
    I've succesfully exported & imported two systems ie DEV & Solutin Manager , but PRD system has an OS problem with symbolic links ie Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS
    I want to export both ABAP & JAVA stack but only the java stack is getting  picked.
    Below  is part of the resultng sapinst.log 
    Thanks
    INFO 2011-09-05 10:44:30.573
    Execute step verifyJavaHome of component |NW_Export|ind|ind|ind|ind|0|0|NW_getJavaHome|ind|ind|ind|ind|2|0
    INFO[E] 2011-09-05 10:44:33.851
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/._), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:44:33.851
    FSL-02061  Link /._ is invalid: Unable to link a link to itself.
    INFO 2011-09-05 10:44:46.118
    Execution of the command "/usr/j2sdk1.4.2_09/bin/java -classpath /tmp/sapinst_exe.29247.1315208256/JAR/ins-j2ee.jar com.sap.ins.j2ee.GetSystemProperty" finished with return code 0. Output: #
    #Mon Sep 05 10:44:45 EAT 2011
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    sun.boot.library.path=/usr/j2sdk1.4.2_09/jre/lib/sparc
    java.vm.version=1.4.2_09-b05
    java.vm.vendor=Sun Microsystems Inc.
    java.vendor.url=http\://java.sun.com/
    path.separator=\:
    java.vm.name=Java HotSpot(TM) Client VM
    file.encoding.pkg=sun.io
    user.country=US
    sun.os.patch.level=unknown
    java.vm.specification.name=Java Virtual Machine Specification
    user.dir=/oracle/PRD/INSTDIR/sapinst_dir
    java.runtime.version=1.4.2_09-b05
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.endorsed.dirs=/usr/j2sdk1.4.2_09/jre/lib/endorsed
    os.arch=sparc
    java.io.tmpdir=/var/tmp/
    line.separator=\n
    java.vm.specification.vendor=Sun Microsystems Inc.
    os.name=SunOS
    sun.java2d.fontpath=
    java.library.path=/usr/j2sdk1.4.2_09/jre/lib/sparc/client\:/usr/j2sdk1.4.2_09/jre/lib/sparc\:/usr/j2sdk1.4.2_09/jre/../lib/sparc\:/tmp/sapinst_exe.29247.1315208256\:/usr/openwin/lib\:/usr/lib
    java.specification.name=Java Platform API Specification
    java.class.version=48.0
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    os.version=5.10
    user.home=/
    user.timezone=Africa/Nairobi
    java.awt.printerjob=sun.print.PSPrinterJob
    file.encoding=ISO8859-1
    java.specification.version=1.4
    java.class.path=/tmp/sapinst_exe.29247.1315208256/JAR/ins-j2ee.jar
    user.name=root
    java.vm.specification.version=1.0
    java.home=/usr/j2sdk1.4.2_09/jre
    sun.arch.data.model=32
    user.language=en
    java.specification.vendor=Sun Microsystems Inc.
    java.vm.info=mixed mode
    java.version=1.4.2_09
    java.ext.dirs=/usr/j2sdk1.4.2_09/jre/lib/ext
    sun.boot.class.path=/usr/j2sdk1.4.2_09/jre/lib/rt.jar\:/usr/j2sdk1.4.2_09/jre/lib/i18n.jar\:/usr/j2sdk1.4.2_09/jre/lib/sunrsasign.jar\:/usr/j2sdk1.4.2_09/jre/lib/jsse.jar\:/usr/j2sdk1.4.2_09/jre/lib/jce.jar\:/usr/j2sdk1.4.2_09/jre/lib/charsets.jar\:/usr/j2sdk1.4.2_09/jre/classes
    java.vendor=Sun Microsystems Inc.
    file.separator=/
    java.vendor.url.bug=http\://java.sun.com/cgi-bin/bugreport.cgi
    sun.io.unicode.encoding=UnicodeBig
    sun.cpu.endian=big
    sun.cpu.isalist=sparcv9vis2 sparcv9vis sparcv9 sparcv8plusvis2 sparcv8plusvis sparcv8plus sparcv8 sparcv8-fsmuld sparcv7 sparc
    INFO 2011-09-05 10:44:47.076
    Execution of the command "/usr/j2sdk1.4.2_09/bin/java -classpath /tmp/sapinst_exe.29247.1315208256/JAR/ins-j2ee.jar:/tmp/sapinst_exe.29247.1315208256/JAR/sapxmltoolkit.jar -d64 com.sap.ins.j2ee.TestClassLoader" finished with return code 0. Output: CORRECT
    INFO 2011-09-05 10:44:47.572
    Execute step verifyPolicy of component |NW_Export|ind|ind|ind|ind|0|0|NW_getJavaHome|ind|ind|ind|ind|2|0
    INFO 2011-09-05 10:44:47.715
    Execute step setNWOption of component |NW_Export|ind|ind|ind|ind|0|0|NW_getJavaHome|ind|ind|ind|ind|2|0
    WARNING 2011-09-05 10:44:47.944
    Could not determine a valid JAVA_HOME directory from the environment.
    INFO 2011-09-05 10:44:48.86
    Execute step assignUsersToSapinstGroup of component |NW_Export|ind|ind|ind|ind|0|0
    INFO 2011-09-05 10:44:48.890
    Account sapinst already exists.
    INFO 2011-09-05 10:44:48.894
    Account prdadm already exists.
    INFO 2011-09-05 10:44:48.917
    Account oraprd already exists.
    INFO 2011-09-05 10:44:49.73
    Execute step useDatabaseMethod of component |NW_Export|ind|ind|ind|ind|0|0
    INFO 2011-09-05 10:44:49.217
    Execute step setDatabaseMethodOra of component |NW_Export|ind|ind|ind|ind|0|0
    INFO 2011-09-05 10:44:49.341
    Execute step setDatabaseMethodDB6 of component |NW_Export|ind|ind|ind|ind|0|0
    INFO 2011-09-05 10:44:49.480
    Execute step mainExportParameters of component |NW_Export|ind|ind|ind|ind|0|0
    INFO[E] 2011-09-05 10:44:52.251
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/._), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:44:52.252
    FSL-02061  Link /._ is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.760
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/cntrl), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.761
    FSL-02061  Link /oracle/PRD/cntrl is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.762
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/._), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.762
    FSL-02061  Link /oracle/PRD/._ is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.763
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/sdubhibq), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.764
    FSL-02061  Link /oracle/PRD/sdubhibq is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.765
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/sduccayx), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.765
    FSL-02061  Link /oracle/PRD/sduccayx is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.766
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/inventory), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.767
    FSL-02061  Link /oracle/PRD/inventory is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.768
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/OPatch), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.768
    FSL-02061  Link /oracle/PRD/OPatch is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.769
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/assistants), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.770
    FSL-02061  Link /oracle/PRD/assistants is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.771
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/bin), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.772
    FSL-02061  Link /oracle/PRD/bin is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.773
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/clone), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.773
    FSL-02061  Link /oracle/PRD/clone is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.774
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/crs), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.775
    FSL-02061  Link /oracle/PRD/crs is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.776
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/css), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.777
    FSL-02061  Link /oracle/PRD/css is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.778
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/ctx), line (346) in file (syuxclink.cpp).
    INFO[E] 2011-09-05 10:45:01.778
    FSL-02061  Link /oracle/PRD/ctx is invalid: Unable to link a link to itself.
    INFO[E] 2011-09-05 10:45:01.779
    FSL-00001  System call failed. Error 90 (Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS) in execution of system call 'realpath' with parameter (/oracle/PRD/dbs), line (346) in file (syuxclink.cpp).

    Hi,
    In PRD system, u might have craeted many symbolic links in /oracle/PRD fileystem . This should be avoided. Symbolic link should not be created in /oracle/PRD ...
    Please check why symbolic links are created and get help from System Operation team . Please becareful to unlink symbolic links that are created by non-SAP. Make sure to perform full  offline backup .
    Please get the help from Unix System Operation team. Also it does not makes any sense to increase value of Unix parameter for maximum symbolic links.
    Regards
    APR

  • How to stop jobs after a system copy

    Hi All,
    After doing a system copy from the Production system to some test system, all the jobs that are supposed to be triggered in the production server will also trigger in the test system which is not good.
    For example, If we have a payroll running every month. After i do a system copy the same payroll will also be triggered in the test server which is un acceptable.
    How do we go about it and what are all the steps that we need to follow after a system copy?
    Points will be rewarded.
    Thanks
    Vijay

    Hello Vijay,
    you surely need background processes in a running system.
    But you can start a SAP system without any background processes.
    When the system is up you go to sm37 and delete (or de-release) all the jobs you don't need in the target system. Then set the number of batch processes to the amount you want and restart the system.
    Alternatively you can prepare your source system accordingly with the SAP System Copy Guide - Section 3.2 Technical Preparations:
    "Set all released jobs from Released to Scheduled:
    Tools -> CCMS -> Background Processing -> Jobs - Overview and Administration (transaction SM37)
    You also need to do this for jobs that must run periodically (see SAP Note 16083).
    Select all jobs (include start after event) as follows:
    Job -> Released -> Scheduled"
    I think the best way for you is to read this guide!
    Everything is explained very well there.
    Goto:
    https://service.sap.com/systemcopy
    In the left tree select:
    -> SAP Netweaver
    -> SAP Netweaver in Detail
    -> Software Life-Cycle Management
    -> System Copy & Migration
    -> Media Library
    There are all the Guides for the current releases.
    Regards, Michael
    Message was edited by:
            Michael Teubner

  • Possible migration(Heterogeneous system copy) combination

    Dear all
    Currently we're planning to do Heterogeneous system copy
    from the following source(current system) and target.
    Source : R/3 4.6C + Oracle 8.1.7 on AIX 4.3.3
    Target : R/3 4.6C + Oracle 10.2 on Windows 2003
    For the target system, i checked the PAM in Service Marketplace
    and it seems that R/3 4.6C + Oracle 10.2 on Windows 2003 is supported.
    But i'm not sure whether this source - target combination is possible
    in Heterogeneous system copy.
    To summarize, here are 2 questions.
    1) Where can i find Heterogeneous system copy combination?
    (OS/DB combination which supports Heterogeneous system copy in R/3 4.6C)
    2) Is the above Source - Target combination is possible?
    Best Regards.
    Ahn

    > Source : R/3 4.6C + Oracle 8.1.7 on AIX 4.3.3
    > Target : R/3 4.6C + Oracle 10.2 on Windows 2003
    Yes - this is possible and supported. But keep in mind:
    - you must have a certified migration consultant doing the migration. If you do it on your own, you'll loose support for problems during the migration and for the target system --> SAP will bill help (see http://service.sap.com/osdbmigration --> FAQ)
    - 4.6c is out of general support; you may need to buy extended support to get the migration kit
    Markus

  • Heterogeneous system copy from MSSQL to Oracle

    Dear Experts,
    I have performed ABAP+JAVA system copy R3load based from Oracle to Oracle and MSSQL to MSSQL platform.
    Homogeneous system copy many times.
    But this is first time i am perfoming an Export from MSSQL source system with r3load Export method .....My Target system is havign Oracle 10.2.0.2 software installed along with installation prerequisites.
    But while Importing the same MSSQL Export ...I am not getting any option for heterogeneous system copy.
    I am running on ECC6.0 windows platform and i also have generated Migartion KEY.
    But where should i put this key.
    I have gone through system copy guide many times but unable to understand Exact options to follow to Migrate to Oracle target system. Appreciate if anyone can give me detail steps i need to carry on Target system
    Best Regards,
    AjitR

    Markus,
    Thanks for the help, i have done Export with mentioned way and this time DBSIZE.xml file got created under ORA directory ....i started installation at target system....It went smooth until phase Import java Dump Done. .....But during Post load activities It gave error...
    When i tried connectivity to Oracle database it works fine and
    R3trans -d gives below mentioned error....Looks like table does not exist....all ENV variables are also got set at target machine.....
    Error as below
    Now 'SAPSR3/<pwd>@TST' is connected (con_hdl 0, nls_hdl 0).
    4 ETW000                                                                             389  0.171885
    4 ETW000  [dev trc     ,00000]  Database NLS settings: AMERICAN_AMERICA.UTF8       23682  0.195567
    4 ETW000  [dev trc     ,00000]  Database instance TST is running on CSSLDELL-3 with ORACLE version 10.2.0.2.0 since 20080522
    4 ETW000                                                                            4056  0.199623
    4 ETW000  [dev trc     ,00000]  Connection 0 opened (DBSL handle 0)                14523  0.214146
    4 ETW000  [dblink      ,01299]  ***LOG BZA=>table SVERS      does not exist on database            [dblink#3 @ 1299]
    4 ETW000                                                                            8145  0.222291
    4 ETW000  [dev trc     ,00000]  NTAB: SELECT COMPCNT FROM DDNTT FAILED              1021  0.223312
    4 ETW000  [dev trc     ,00000]  NTAB: SELECT VERSION FROM DDNTT FAILED               520  0.223832
    4 ETW000  [dbntab.c    ,00000]  *** ERROR => NTAB: SELECT VERSION/DBASE FROM DDNTT FAILED
    4 ETW000                                                                             505  0.224337
    4 ETW000  [dbntab      ,01273]  ***LOG BZY=>unexpected return code 103        calling NTAB       [dbntab#3 @ 12737]
    Please help...Points rewarded anyways.....

  • Downtime for Heterogeneous System Copy Export of Source DB2 LUW

    Hello,
    What is the downtime required for a heterogeneous system copy export of a source database on AIX with DB2 LUW?  Here are the following details of the data itself:
    DB size: 120 GB used of 240 GB.
    Physical server: IBM Power5 quad-core 1.65GHz virtualized
    RAM: 9.5GB

    > What is the downtime required for a heterogeneous system copy export of a source database on AIX with DB2 LUW?  Here are the following details of the data itself:
    I suggest you just "try it out" as a test run. It's quite impossible to give estimates based on database sizes. It's possible to migrate roughly 1 TB/hour with appropriate hardware, mostly your harddisks will be the bottleneck.
    There are also a number of other factors like number of R3load processes, table splitting or not, parallel export/import etc.
    I highly suggest to run the migration a few times before you do the "live" migration.
    Markus

  • Homogeneous/heterogeneous system copy

    In the homogeneous/heterogeneous system copy guide, I'm told to delete all entries in the tables DBSTATHORA, DBSTAIHORA, DBSTAIORA and DBSTATTORA.
    Why do I need to delete all the entries in these tables? What are the entries in these tables for? What happens if I don't delete the entries from these tables?

    Hi Jamal,
    I believe you are talking about the tables DBSTATHORA, DBSTAIHORA,
    DBSTATIORA, DBSTATTORA. These tables contain statistical
    data (like performance) from the source system. Since that is of no use
    in your new system you can delete it with the following command in
    SQL*Plus as user sapr3 (or sap<sid> when using Basis >=610)
    delete from DBSTATHORA;
    Repeat this command for the other tables
    or execute being in SQL> prompt
    truncate <Tablename>
    Hope this helps you to understand the pupose and how to delete them.
    Regards
    Sekhar

  • Homogeneous and Heterogeneous System Copy

    Hello Guru's
    Greeting ! . .  .
    I wanted some help regarding Homogeneous and Heterogeneous System Copy.
    It would be helpful if you can guide me for an Step by Step procedure  for Homogeneous and Heterogeneous System copy. As i have to carry out both of the activity.
    Homogeneous:- AIX5.3/Oracle10 to AIX5.3/Oracle10
    Heterogeneous:- AIX5.3/Oracle10 to Windows2003/Oracle10
    Thanks & Best Regards
    Ashish

    Hello Ashish,
    You can find the guides here in this location.
    https://websmp203.sap-ag.de/systemcopy
    If you have complete backup then you start you SAPInst on the system on which you want to have systemcopied.
    Then when you are starting DB instance then instead of using the Export DVD you need provide the Database which is backed up. There are screens where it will ask you for editing SID you need to specify that during DB instance.
    For further processes you can download the corressponding guide from above link.
    Thanks & Regards
    Vivek

  • DB is inconsistent after the heterogenous system copy

    Hi!
    I have currently serios problems working with SAP ERP 2005 (SAP DB on Windows) that was installed via heterogenous system.
    Entering into db-relevant tcodes such as DB13, etc. retrieves a dump "ITAB_DUPLICATE_KEY".
    Furthermore it is not possible to execute the patch in tcode SPAM, because the patch is hanging in the phase "IMPORT_PROPER" (the DD structure seems to be inconsistent).
    Can someone describe the procedure with technical steps to solve the problem?
    Thank you very much!
    regards
    Thom

    Please check this note if it helps.
    Note 940878 - DB02N collector: ITAB_DUPLICATE_KEY
    Import_Improper
    You can do one thing if you are not able to proceed with patching.
    You can go to pat01 and pat03 .
    You try to rest the staus of patch in table pat03 to N
    and start the same patch again.
    update table sapr3.pat03 status='N' where patch='SAPKA46D04';
    or get abaper to reset the value from abap.
    Hope it helps
    Amit Asthana

  • DB13 SQL error -942  after homogenous system copy

    Dear all,
    I've performed hpmogenous system copy from the productiion system running on ECC 6.0 Oracle 10.2.0.4 and HP-UX 11.31.
    Then after finishing all post homogenous system copy activites I've tried to start check db in DB13 and I got this error message.
    In sqlplus from the server I checked this SELECT and it shows the appropriate rows. But from DB13 there is the error message.
    Job started
    Step 001 started (program RSDBAJOB, variant &0000000000360, user ID RPO)
    Execute logical command BRCONNECT On host sapds
    Parameters: -u / -jid CHECK20111024152519 -c -f check
    BR0801I BRCONNECT 7.00 (52)
    BR0477I Oracle pfile /oracle/TST/102_64/dbs/initTST.ora created from spfile /oracle/TST/102_64/dbs/spfileTST.ora
    BR0280I BRCONNECT time stamp: 2011-10-24 15.25.24
    BR0301E SQL error -942 at location BrLicCheck-51,SQL statement:
    'SELECT COUNT(*), NVL(SUM(BLOCKS), 0) FROM SYS.SEG$ WHERE USER# = 28'
    ORA-00942: table or view does not exist
    BR0806I End of BRCONNECT processing: cehbjvyf.chk2011-10-24 15.25.24
    BR0280I BRCONNECT time stamp: 2011-10-24 15.25.25
    BR0804I BRCONNECT terminated with errors
    External program terminated with exit code 3
    BRCONNECT returned error status E
    Job finished
    Does anyone knows why?
    Thanks in advance.
    Ruzica

    Solved
    sapdba_role needed to be performed again
    sqlplus /nolog @sapdba_role R3
    This solves the problem
    Ruzica

  • "Table VSEOPARENT is not in the database" after SolMan system copy to x64

    Hi SDNners,
    We've just completed a system copy of our SolMan 3.1 system onto a new
    (Xeon x64 based) server. This system copy is part of the process of
    moving SolMan 3.1 from an old server onto 64bit hardware and then
    upgrading it to SolMan v4 and Oracle 10G.
    Although the system appears to start properly in the MMC, we are unable
    to log into the system through SAPGUI - we get a SYNTAX_ERROR window
    instead of a logon screen.
    I've checked the SysLog from within the MMC and noticed a number of
    errors stating:
    Database: Table VSEOPARENT is not in the database
    Database: Table VSEOIFIMPL is not in the database
    Database: Table VSEOIFCOMP is not in the database
    I tried running SQL command 'select * from "SAPSOL"."VSEOPARENT"; and
    it confirmed that the table didn't exist. I then ran the same command
    on the source SolMan system and it showed that VSEOPARENT DID exist. I
    don't understand how these VSEO* tables could have gone missing between
    the source and target systems.
    I've searched OSS for VSEO* and cannot find anything. Please help!
    Thanks,
    Arwel.

    We have 640 kernel, ECC 5.0 and BASIS patch 23.
    For me the problem was with SAPVIEW table wasnt imported from source to target becuase SAPVIEW.STR file was 0 byte. STR files gets created in export preparation phase.
    It did happen because on source side master DVD, there was no option for export preparation. I had only option for tablesplit and export db.
    I did use ECC 5.0 SR2 Master DVD which had option for export preparation phase and that created SAPVIEW.STR file.
    Using migration monitor I did re-export and re-import and this time all views are imported in target.
    Regards,
    Mamadi.

  • No username of Source system is avbl after livecache system copy

    Hi Experts
    I have done a livecache system copy from the source system to target system. Here the steps are
    Assume my Source SYstem Livecache is RP1 and Target System livecache is RS1.
    1. Taken Source system livecache DATA and LOG Area backup RP1.
    2. Defined the same source system backup medium name in Target System (RS1 and moving the Source system Liveacache backuped files to Target system and defined the medium name as per that)
    3. put the livecache db_admin mode
    4. db_activate RECOVER <medium_name>.
    5. recover_start <log_medium_name> LOG <nnn>
    6. db_online.
    Here we faced that
    ERR
    -24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
    -24907,ERR_DBAWRONG: Wrong database system administrator
    -24988,ERR_SQL: SQL error
    -4008,Unknown user name/password combination
    So we activated the SUPERDBA as " db_activate SUPERDBA,<password>
    then it came to online. and afterwards we have used the load_systab command to load the tables.
    BUT we could not find any Source System name like "RP1ADM" in the tables of the livecache database. Only there are CONTROL,SUPERDBA username availbale. Usually there will be also the source admin name . I dont know why it is missing
    Before a month we have done livecahe restore same as now in that time we got the source system name admin also. ( RP1ADM) and also tables which owned by RP1ADM. alos i could find APPSYSPARAM table and the instance also registered.
    But now in this restore we could not find the above.
    We followed the same procedure and there is no change in the steps also.
    Could anyone help me...
    Regards
    bala

    Hello Bala,
    1. As I wrote you already, the notes:
    886103 System Landscape Copy for SAP SCM
    877203     Post steps after the Homogenous liveCache copy using backup/
    457425     Homogenous liveCache copy using backup/restore
    has all recommended steps to do, when you will run the u201CSystem Landscape Copy for SAP SCMu201D
    2. If you run the u201CHomogenous liveCache copy using backup/restoreu201D you should pay attention to the note 457425. After you imported the complete data backup < step 2. > you need to update the system tables.
    To update the system tables you need to know the correct database SYSDBA user & password.
    After you restored the databackup of the source database, start the database online & run u201Cselect * from usersu201D SQL command to see the SYSDBA user. Then check that you know the DBA user ( DataBase Administrator ) & password of the source database instance => Open the SQL session with this
    user & password.
    Example:
    after db_activate recover <medium_name>
    login as control,password
    db_online
    sql_execute select * from users
    sql_connect  superdba,<password of source system>
    If you didnu2019t get error with the last command, then you could update the system tables with the superdba,<password of source system> using load_systab command.
    The system tables will be updated & the correct SYSDBA user & password will be updated in *.UPC file.
    3.     
    user_sysdba:
    You make the database system administrator known to Database Manager. It is only necessary to use this DBM command if the database administrator is not known or is incorrectly known to Database Manager.
    u201CI have tried like this
    after db_activate recover <medium_name>
    login as control,password
    db_admin
    user_sysdba superdba,<password of source system>
    db_onlineu201D
    You could update the .upc files with the wrong SYSDBA user password u2026
    You was lucky, that you knew the correct SYSDBA user and password of the source database.
    Example  < NLK is my local database >:
    A.     I could update the .upc file with wrong password of SYSDBA user:
    dbmcli -d NLK -u control,control
    dbmcli on NLK>user_sysdba superdba,test
    OK
    dbmcli on NLK>db_online
    OK
    dbmcli on NLK>load_systab
    ERR
    -24909,ERR_DBAUNKNOWN: SYSDBA unknown
    dbmcli on NLK>exit
    B.  I could update the .upc file with wrong SYSDBA user:
    dbmcli -d NLK -u control,control
    dbmcli on NLK>user_sysdba test,test
    OK
    dbmcli on NLK> user_get test
    OK
    u2026
    dbmcli on NLK>sql_connect test,test
    ERR
    -24988,ERR_SQL: SQL error
    -4008,Unknown user name/password combination
    dbmcli on NLK> dbmcli on NLK>sql_connect superdba,admin
    OK
    I could connect as test,test; but the test user is NOT SYSDBA user u2026
    dbmcli -d NLK -u test,test
    dbmcli on NLK>
    Itu2019s recommended to user the load_systab command, so the .upc files will be updated with the correct SYSDBA user/password or
    you will get error.
    4. http://maxdb.sap.com/doc/7_7/86/68627a1bc642e6a6f73d3bc7a55fe1/content.htm
    You got error:
    ERR
    -24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
    -24907,ERR_DBAWRONG: Wrong database system administrator
    -24988,ERR_SQL: SQL error
    -4008,Unknown user name/password combination
    The automatically updating the system tables, according to the default value, is switched on.
    After you will run the update system tables with the correct SYSDBA user & password the *.UPC file will be updated,
    and with the next liveCache restart you will not get this error.
    5. See more information in the MAXDB library:
    http://maxdb.sap.com/doc/7_7/45/11cbd6459d7201e10000000a155369/content.htm
    Thank you and best regards, Natalia Khlopina
    Edited by: Natalia Khlopina on May 19, 2010 2:58 PM

Maybe you are looking for