Homogeneous System Copy - Export Import of RFC's, ALE, Content Repositories

Good Morning,
I have a landscape with a Development and Production Systems with SAP R3 Enterprise 4.70 Ext 110, MaxDB 7.5, HP-UX 11.23. A Homogeneous System Copy is going to be done from Production to Development.
I have a idea to be able to recover the RFC's, ALE and Content Repositories Information after the Copy, which is to create a transport order with the structures which contain data for the RFC's definition, the ALE configurations and definitions and the Content Repositories configurations and definitions in Development and after the copy, transport the orders back to Development. The problem is that i don't know which structures should i use, and if my idea is viable?
For example, if i go to transaction oac0 and look at the content repositories and if i look at the Technical Information, i can see that the fileds with data are from Structure SCMS_SCREP, but my question is, inserting thsi structure in a transport order to import after the copy willbe enough? Aren't there more structures i need to insert in a transport order? And for RFCs and ALE?
Can anyone help me on this matter please?
Kind Regards,
Pedro Gaspar

Hi,
If the target system is being refreshed then first secure any information that you may require.
1) Backup user master and authorization data from each client where this data needs to be retained.
    Use transaction SCC8 to export this data.  Select profile SAP_USER and specify target system = TARGET_SID.
2) Backup RFC tables to restore destinations afterwards.
     the only below tables required to take backup.    
Call SE01 and create a new request of type = ""Transport of Copies"" with description = ""Export RFC destination tables prior to system refresh"".Make sure to specify a Target for the request or no data file will be created.
RFCATTRIB
RFCCHECK
RFCDES
RFCDESSECU
RFCDOC
3) ALE / Partner profiles.
  Call WE20 and select each partner profile.
Follow menu path ""Partners --> Check"" and obtain a list of tables used.
The only tables listed were the ones listed below.
These tables are client-dependant therefore you will have to logon to each client and call SE01 and create a new request of type = ""Transport of Copies"
  EDPP1
  EDP13
  EDP21
Also document the WE21 --> Ports --> Transactional RFC" section.
Run transaction BD64 and document each configured distribution model.  This information is client-dependent so make sure to record values for each required client. and also record RFC destinations for synchronous method calls in BD97.
I hope it will help you.
Regards,
Kiran .V

Similar Messages

  • Homogeneous system copy using export/import on WIn/Ora

    Dear experts,
    i need to know the homogeneous system copy procedure using export/import method for following scenario as we are in the process of Data center migration of SAP systemsfrom location to another location.
    Source system:
    ECC6/BI7/APO(ABAP stack)
    OS:WIndows 2003
    D:B:Oracle 10g
    Target System: New hardware installed on Virtual environment(VMware)
    No change of SID
    ECC6/BI//APO
    OS:WINDOWS2008
    D:B: Oracle 11g
    It would be great if anyone can share the documentu2019s/links (Not SAP homogeneous system copy guide) which you have prepared for the homog. system copy using export/import on Windows/oracle  as i have done the system copy using backup/restore for ABAP stack and export/import for Java stack so far.
    Therefore i am not sure about this procedure/prerequisites/checklist needs to prepare as i have gone through the SAP guide but it is not step by step document.
    Cheers

    There are two approacahes for your  project
    1) First wether to use Oracle11g on target database
    2) Continue with Database Oracle 10.2 on traget database
    If you want to use Oracle11.2 on your target database you have to search the installers which are supported for 11.2 database. If the installers are available then only you can install your target database using Oracle11.2.Other wise t use Oracle10.2.0.4 is supported on Win2008r2. You can use this version of Oracle database to build ur target database.It works fine . Absolutely no problem.
    Later on you can upgrade the Oracle10.2 to 11.2 Onwards.
    If installers are avialble you can use Oracle11.2 also. There is absolutely no problem.
    As per my knowledge installers are available and supported with Oracle11.2.Also check the PAM before arriving on any deciscion.

  • Error in phase import Homogeneous system copy from a BI 7.3 dual stack ABAPJAVA

    Hi
    I'm doing a Homogeneous system copy from a BI 7.3 dual stack ABAP+JAVA system with an Oracle DB (11g version, 11.2.0.3.0 patch level) with AIX ibm OS.
    Before starting export I've executed in the source system the report SMIGR_CREATE_DDL, as described in sap note 888210, and I generated *.SQL files.
    After, during the import in the target system I get the following error message:
    vi /expdb2/tmpDB0/sapinst_instdir/NW730/ORA/ORA/COPY/ORA/SYSTEM/STD/AS/import_monitor.log
    INFO: 2014-03-08 00:21:57 com.sap.inst.migmon.LoadTask run_report
    Monitor jobs: running 0, waiting 1, completed 60, failed 5, total 66  finish processing of package SAP0000
    You can see below the detail of the 5 packages in error:
    SAPAPPL0_1_5
    DbSlExecute: rc = 99
      (SQL error 2216)
      error message returned by DbSl:
    ORA-02216: tablespace name expected
    (DB) INFO: disconnected from DB
    /usr/sap/DB2/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
    /usr/sap/DB2/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140307141347
    SAPZPSA
    DbSlExecute: rc = 99
      (SQL error 2216)
      error message returned by DbSl:
    ORA-02216: tablespace name expected
    (DB) INFO: disconnected from DB
    SAPDODS
    DbSlExecute: rc = 99
      (SQL error 922)
      error message returned by DbSl:
    ORA-00922: missing or invalid option
    (DB) INFO: disconnected from DB
    SAPDFACT
    DbSl Trace: Error 1741 in exec_immediate() from oci_execute_stmt(), orpc=0
    DbSl Trace: ORA-01741 occurred when executing SQL stmt (parse error offset=8126464)
    (DB) ERROR: DDL statement failed
    (  ALTER TABLE "/BI0/F0TCT_C01"    ADD PARTITION "/BI0/F0TCT_C010000001131" VALUES LESS THAN ( 0000001131  )    TABLESPACE "" )
    DbSlExecute: rc = 99
      (SQL error 1741)
      error message returned by DbSl:
    ORA-01741: illegal zero-length identifier
    (DB) INFO: disconnected from DB
    SAPZOSO
    DbSl Trace: Error 922 in exec_immediate() from oci_execute_stmt(), orpc=0
    DbSl Trace: ORA-00922 occurred when executing SQL stmt (parse error offset=242024448)
    (DB) ERROR: DDL statement failed
    (CREATE TABLE "/BIC/B0000989000"    ("REQUEST" VARCHAR2 (000090)      DEFAULT ' ' NOT NULL,    "DATAPAKID" VARCHAR2 (000018)      DEFAULT '000000' NOT NULL,    "PART
    NO" NUMBER (000010)      DEFAULT 0 NOT NULL,    "RECORD" NUMBER (000010)      DEFAULT 0 NOT NULL,    "PLANT" VARCHAR2 (000012)      DEFAULT ' ' NOT NULL,    "MATERIA
    L" VARCHAR2 (000054)      DEFAULT ' ' NOT NULL,    "RPA_CURUOM" VARCHAR2 (000015)      DEFAULT ' ' NOT NULL,    "RPA_MVF" NUMBER (000017, 000002)      DEFAULT 0 NOT N
    ULL,    "PRICE_UNIT" NUMBER (000017, 000003)      DEFAULT 0 NOT NULL,    "RPA_QTYUOM" VARCHAR2 (000009)      DEFAULT ' ' NOT NULL,    "RT_SSMFGR" VARCHAR2 (000024)
        DEFAULT '00000000' NOT NULL,    "BASE_UOM" VARCHAR2 (000009)      DEFAULT ' ' NOT NULL,    "FRE_PLNPUR" VARCHAR2 (000036)      DEFAULT ' ' NOT NULL,    "FRE_MINS
    TK" NUMBER (000017, 000003)      DEFAULT 0 NOT NULL,    "FRE_SERLEV" NUMBER (000017, 000003)      DEFAULT 0 NOT NULL,    "FRE_SELCLS" VARCHAR2 (000003)      DEFAULT '
    0' NOT NULL,    "FRE_REPLST" VARCHAR2 (000006)      DEFAULT ' ' NOT NULL,    "ABCKEY" VARCHAR2 (000003)      DEFAULT ' ' NOT NULL,    "RECORDMODE" VARCHAR2 (000003)
        DEFAULT ' ' NOT NULL,    "RT_SERVLEV" VARCHAR2 (000003)      DEFAULT ' ' NOT NULL,    "RT_SUPS" VARCHAR2 (000003)      DEFAULT ' ' NOT NULL,    "VAL_TYPE" VARCH
    AR2 (000030)      DEFAULT ' ' NOT NULL,    "PUR_GROUP" VARCHAR2 (000009)      DEFAULT ' ' NOT NULL,    "RT_VPNEU" NUMBER (000017, 000002)      DEFAULT 0 NOT NULL,
    "CURRENCY" VARCHAR2 (000015)      DEFAULT ' ' NOT NULL,    "RT_VRKPE" NUMBER (000017, 000003)      DEFAULT 0 NOT NULL,    "DISMM" VARCHAR2 (000006)      DEFAULT ' '
    NOT NULL,    "SALES_UNIT" VARCHAR2 (000009)      DEFAULT ' ' NOT NULL,    "RT_VP_BT" NUMBER (000017, 000002)      DEFAULT 0 NOT NULL,    "RT_VPE_BT" NUMBER (000017,
    000003)      DEFAULT 0 NOT NULL,    "RT_VP_NT" NUMBER (000017, 000002)      DEFAULT 0 NOT NULL,    "RT_VPE_NT" NUMBER (000017, 000003)      DEFAULT 0 NOT NULL,    "R
    T_VWAERBT" VARCHAR2 (000015)      DEFAULT ' ' NOT NULL,    "RT_VWAERNT" VARCHAR2 (000015)      DEFAULT ' ' NOT NULL,    "RT_VPMEIBT" VARCHAR2 (000009)      DEFAULT '
    ' NOT NULL,    "RT_VPMEINT" VARCHAR2 (000009)      DEFAULT ' ' NOT NULL,    "LOC_CURRCY" VARCHAR2 (000015)      DEFAULT ' ' NOT NULL,    "UNIT" VARCHAR2 (000009)
      DEFAULT ' ' NOT NULL,    "CM_MCATDIV" VARCHAR2 (000054)      DEFAULT ' ' NOT NULL,    "CM_CDT1" VARCHAR2 (000054)      DEFAULT ' ' NOT NULL,    "CM_CDT2" VARCHAR2
    (000054)      DEFAULT ' ' NOT NULL,    "CM_CDT3" VARCHAR2 (000054)      DEFAULT ' ' NOT NULL,    "CM_CDT4" VARCHAR2 (000054)      DEFAULT ' ' NOT NULL,    "CM_HIEID"
    VARCHAR2 (000006)      DEFAULT ' ' NOT NULL,    "CPSTLC" NUMBER (000017, 000002)      DEFAULT 0 NOT NULL,    "CPSVLC" NUMBER (000017, 000002)      DEFAULT 0 NOT NULL
    ,    "STOCK_VAL" NUMBER (000017, 000002)      DEFAULT 0 NOT NULL,    "STOCK_QTY" NUMBER (000017, 000003)      DEFAULT 0 NOT NULL,    "RT_SEASON" VARCHAR2 (000012)
      DEFAULT ' ' NOT NULL,    "RT_SEASYR" VARCHAR2 (000012)      DEFAULT '0000' NOT NULL,    "CALDAY" VARCHAR2 (000024)      DEFAULT '00000000' NOT NULL,    "CALWEEK"
    VARCHAR2 (000018)      DEFAULT '000000' NOT NULL,    "RF_BNDID" VARCHAR2 (000012)      DEFAULT ' ' NOT NULL,    "/BIC/ZCATTR3" VARCHAR2 (000006)      DEFAULT ' ' NOT
    NULL,    "/BIC/ZCSTYLE" VARCHAR2 (000006)      DEFAULT ' ' NOT NULL,    "/BIC/ZCIMAGE" VARCHAR2 (000006)      DEFAULT ' ' NOT NULL,    "/BIC/ZCBRNDTYP" VARCHAR2 (000
    003)      DEFAULT ' ' NOT NULL,    "/BIC/ZCGROUPE" VARCHAR2 (000054)      DEFAULT ' ' NOT NULL)    PCTFREE 10    PCTUSED 00    INITRANS 001    TABLESPACE    STORAGE (
    INITIAL    0000000016 K            NEXT        0000001024 K            MINEXTENTS  0000000001            MAXEXTENTS  2147483645            PCTINCREASE 0000
        FREELISTS  001            FREELIST GROUPS 01)      PARTITION BY RANGE ("PARTNO")      (      PARTITION "/BIC/B00009890000000000002" VALUES LESS THAN      (00000
    00002)      NOCOMPRESS      ) )
    DbSlExecute: rc = 99
      (SQL error 922)
      error message returned by DbSl:
    ORA-00922: missing or invalid option
    (DB) INFO: disconnected from DB

    hello,
    Before anything update DB shared lib, R3load, R3ldctl and R3szchk in the target system. Also Check in source system if you have any tables o index missing in db02 transaction, If this system wa upgraded from a previous release please check TAORA and IAORA tables in source system and check all the tablespaces named in those tables are created in the target system.
    let me know how it goes.
    Regards,
    Michael

  • Homogeneous system copy db-specific procedure,  Incorrect Migration Export?

    Hello,
    I am still attempting to perform a homogeneous system copy of a NW2004s WebAS Java EP portal system using database-specific system copy with Oracle. OS is Suze 9 Linux.
    I am on the very last step of sapinst on the target system and I have the error message: 
    You entered: /oracle/CEP/sapdata1/systemcopyout/JAVA Found the label SAP:JMIG:700:::* but need the label SAP:MIGSDM:700:::*
    I'm pretty sure I followed the correct procedures to export the source system, using the database-specific procedure but it appears that only the JAVA portion was exported while the import is looking for SDM.
    Does anyone have any suggestions?
    Thanks,
    Judith Leitner

    Hi Judith,
    In my experience please use SAPINST to export your JAVA system as well, as because the J2EE Engine not only keeps information from in the JAVA Database but also on the file system (e.g. the ones from SDM).
    Thus, please do the following:
    1. Export your source database using SAPINST (which in turn calls JLoad).
    2. Import into your target system using SAPINST (which in turn calls JLoad).
    This is proven and should help.
    Regards, Dibya

  • Homogeneous System copy of ABAP+JAVA stack ( PI )

    Hi everyone,
    I am planing to do Homogeneous system copy of our existing NW 7.0 SR3 PI System ( ABAP + JAVA).
    Can anyone help me with step by step details to do in source system and target system?
    Thanks..

    Hi,
    You should follow the system copy guide for the different option while doing the system copy
    - database dependent
    - R3load based (export/import)
    The following document you can use as a reference, (note -this has been done on database dependent method)
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f055cbd0-97f1-2a10-c09a-907b811de000
    Regards,
    Debasis

  • Homogeneous system copy on the same hardware and OS

    Hi!
    When I installed our Q system I was given the wrong user, a local admin instead of a domain admin. Now we can not perform backup with our backup tool, HP dataprotector, because of authorization issues.
    My solution is to "move" the system to the domain and to do that I need to do a Homogeneous system copy.
    Our system is a 64-bit CRM 7.0 ABAP and J2EE on Windows 2008 with Oracle 10.2
    I've read note 676468, 1238351 and the System Copy Guide - System Copy for SAP Systems Based on SAP NetWeaver 7.0 and from this I can see the following ways to do it
    1. using SAPinst for export and import
    2. using an offline backup
    3. copy database files
    What are your experiences with the different methods and what would you recommend?
    rollo

    > that seems to me a bit overdosed for just a user mismatch...
    It is not "just" a user mismatch, the full environment is wrong (wrong user ID).
    Windows stores users not as usernames but as UIDs (see HKEY\USERS in the registry). All permissions and ACLs and registry access permissions are using that UID - including the enviornmental settings, DCOM configurations etc.
    Therefore I would go for system copy as stated in
    Note 1233320 - Domain migration for SAP system
    Technically it may work on the first look, problems may arise later. <sid>adm has to have some special permissions/policies that are not visible (like 'locking pages in memory' or 'act as part of the operating system' or 'run as batch') etc.
    Markus

  • Homogeneous System Copy on Windows/Oracle.

    Hi!
    I have to start a project on Homogeneous System Copy on Windows/Oracle.
    I have gone through the System Copy documents by SAP and also verious SAP note (spl. 659509 ). But still I am not really clear about the whole process.
    As per my understanding, as follows :
    1. Export the Database from Source Host. <b>But HOW? Wheather I have to use any System Tool from SAP ?  </b>
    <b>Copy that to Target Host.</b>
    2. <b>Install the CI in Target Host. As I am working on SAP 4.7 1.10 (SR1) with Kernel 6.20  (NU).</b>
    3. At the time of installation of DI in Target Host give the path of Exoprt fileset.
    My question :
    <b>1. Wheather my plan is right or needs change?</b>
    2. What type of copy it will be :
    a) Homogeneous System Copy using Online / Offline Database Backup.
    b) Homogeneous System Copy using R3LOAD Procedure.
    c) Homogeneous System Copy using R3COPY Procedure.
    <b>3. Do I really need to download/order any system copy tool from SAP?</b>
    My Source :
    SAP 4.7 on Windows 2000 with Oracle 8.1.7 with noarchivelog mode.
    Terget :
    SAP 4.7 on Windows 2003 with Oracle9.2.0.8
    All Kernel : 620 (NU)
    Looking for an urgent solution.
    With Kind Regards,
    Pratip Bhattacharyya

    Hi! Umesh,
    I have found 2 errore .
    1)  ORA-01652: unable to extend temp segment by 2560 in tablespace PSAPTEMP
    2)  DbSl Trace: ORA-1403 when accessing table SAPUSER
    Two things I want to mention here.
    1.  I donot know the passwd of datadase users of Source . I have used different passwd for Target DB userd.
    2. Used defferent SAP SID. Source : ID4 and Target : IDN
    Is that cause any harm?
    Here is the detail logs of those two files.
    <b><i>SAPSSEXC.log</i></b>
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222010532
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe -ctf I G:\Export/DATA/SAPSSEXC.STR C:\SAPinst ORACLE SAPINST_di/DDLORA.TPL C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.TSK ORA -l C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.log
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: job completed
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: END OF LOG: 20061222010532
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222010539
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.cmd -l C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.log -stop_on_error
    DbSl Trace: Got ORACLE_HOME=D:\oracle\idn\928 from environment
    DbSl Trace: Client NLS settings: AMERICAN_AMERICA.WE8DEC
    DbSl Trace: Logon as OPS$-user to get SAPIDN's password
    DbSl Trace: Connecting as /@IDN on connection 0 ...
    DbSl Trace: Attaching to DB Server IDN (con_hdl=0,svchp=0146C57C,svrhp=0146E82C)
    DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
    DbSl Trace: Now I'm connected to ORACLE
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    DbSl Trace: Disconnecting from connection 0 ...
    DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
    DbSl Trace: Now I'm disconnected from ORACLE
    DbSl Trace: Try to connect with default password
    DbSl Trace: Connecting as SAPIDN/<pwd>@IDN on connection 0 ...
    DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
    DbSl Trace: Now I'm connected to ORACLE
    DbSl Trace: Database NLS settings: AMERICAN_AMERICA.WE8DEC
    DbSl Trace: Database instance idn is running on DLWSDV10 with ORACLE version 9.2.0.8.0 since 20061222
    Fri Dec 22 01:05:39 2006
    ***LOG BZA=> table SVERS      does not exist on database [dblink#1 @ 1292] [dblink  1292 ]
    (DB) INFO: connected to DB
    (GSI) INFO: dbname   = "IDN20061222121231                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "DLWSDV10                                                        "
    (GSI) INFO: sysname  = "Windows NT"
    (GSI) INFO: nodename = "DLWSDV10"
    (GSI) INFO: release  = "5.2"
    (GSI) INFO: version  = "3790 Service Pack 1"
    (GSI) INFO: machine  = "8x Intel 801586 (Mod 4 Step 9)"
    (DB) INFO: BCACT created
    (IMP) INFO: import of BCACT completed (0 rows)
    (DB) INFO: BCACT~0 created
    (DB) INFO: BCCOM created
    (IMP) INFO: import of BCCOM completed (0 rows)
    (DB) INFO: BCCOM~0 created
    (DB) INFO: BCEXC created
    (IMP) INFO: import of BCEXC completed (0 rows)
    (DB) INFO: BCEXC~0 created
    (DB) INFO: BCRES created
    (IMP) INFO: import of BCRES completed (0 rows)
    (DB) INFO: BCRES~0 created
    (DB) INFO: BCSPO created
    (IMP) INFO: import of BCSPO completed (0 rows)
    (DB) INFO: BCSPO~0 created
    (DB) INFO: BCTOU created
    (IMP) INFO: import of BCTOU completed (0 rows)
    (DB) INFO: BCTOU~0 created
    (DB) INFO: BRATEXT created
    (IMP) INFO: import of BRATEXT completed (914265 rows)
    (DB) INFO: BRATEXT~0 created
    (DB) INFO: BTCSED created
    (IMP) INFO: import of BTCSED completed (623 rows)
    (DB) INFO: BTCSED~0 created
    (DB) INFO: CD0T000 created
    (IMP) INFO: import of CD0T000 completed (0 rows)
    (DB) INFO: CD0T000~0 created
    (DB) INFO: CD0T120TAB created
    (IMP) INFO: import of CD0T120TAB completed (0 rows)
    (DB) INFO: CD0T120TAB~0 created
    (DB) INFO: CD0T130TAB created
    (IMP) INFO: import of CD0T130TAB completed (0 rows)
    (DB) INFO: CD0T130TAB~0 created
    (DB) INFO: CD0T140TAB created
    (IMP) INFO: import of CD0T140TAB completed (0 rows)
    (DB) INFO: CD0T140TAB~0 created
    (DB) INFO: CD0T500TAB created
    (IMP) INFO: import of CD0T500TAB completed (0 rows)
    (DB) INFO: CD0T500TAB~0 created
    (DB) INFO: CD2APP0 created
    (IMP) INFO: import of CD2APP0 completed (0 rows)
    (DB) INFO: CD2APP0~0 created
    (DB) INFO: CD2HV1PTAB created
    (IMP) INFO: import of CD2HV1PTAB completed (0 rows)
    (DB) INFO: CD2HV1PTAB~0 created
    (DB) INFO: CD2HV2FTAB created
    (IMP) INFO: import of CD2HV2FTAB completed (0 rows)
    (DB) INFO: CD2HV2FTAB~0 created
    (DB) INFO: CNTLWARN created
    (IMP) INFO: import of CNTLWARN completed (0 rows)
    (DB) INFO: CNTLWARN~0 created
    (DB) INFO: D010INC created
    (IMP) INFO: import of D010INC completed (3599971 rows)
    (DB) INFO: D010INC~0 created
    (DB) INFO: D010INC~1 created
    (DB) INFO: D010TAB created
    (IMP) INFO: import of D010TAB completed (11017270 rows)
    DbSl Trace: ORA-1652 occured when executing SQL statement (parse error offset = 35)
    DbSl Trace: sc_p=013ED590,no=20,idc_p=00000000,con=0,act=0,slen=187,smax=256,#vars=0,stmt=01E1A0C8,table=
    DbSl Trace: CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (\
    DbSl Trace: INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) ;
    <b>(DB) ERROR: DDL statement failed
    (CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
    DbSlExecute: rc = 99
      (SQL error 1652)
      error message returned by DbSl:
    ORA-01652: unable to extend temp segment by 2560 in tablespace PSAPTEMP
    DbSl Trace: Disconnecting from connection 0 ...</b>
    DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
    DbSl Trace: Detaching from DB Server (con_hdl=0,svchp=0146C57C,srvhp=0146E82C)
    DbSl Trace: Now I'm disconnected from ORACLE
    (DB) INFO: disconnected from DB
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: job finished with 1 error(s)
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: END OF LOG: 20061222011210
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222023556
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.cmd -l C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.log -stop_on_error
    DbSl Trace: Got ORACLE_HOME=D:\oracle\idn\928 from environment
    DbSl Trace: Client NLS settings: AMERICAN_AMERICA.WE8DEC
    DbSl Trace: Logon as OPS$-user to get SAPIDN's password
    DbSl Trace: Connecting as /@IDN on connection 0 ...
    DbSl Trace: Attaching to DB Server IDN (con_hdl=0,svchp=0146C57C,svrhp=0146E82C)
    DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
    DbSl Trace: Now I'm connected to ORACLE
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    DbSl Trace: Disconnecting from connection 0 ...
    DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
    DbSl Trace: Now I'm disconnected from ORACLE
    DbSl Trace: Try to connect with default password
    DbSl Trace: Connecting as SAPIDN/<pwd>@IDN on connection 0 ...
    DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
    DbSl Trace: Now I'm connected to ORACLE
    DbSl Trace: Database NLS settings: AMERICAN_AMERICA.WE8DEC
    DbSl Trace: Database instance idn is running on DLWSDV10 with ORACLE version 9.2.0.8.0 since 20061222
    (DB) INFO: connected to DB
    (GSI) INFO: dbname   = "IDN20061222121231                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "DLWSDV10                                                        "
    (GSI) INFO: sysname  = "Windows NT"
    (GSI) INFO: nodename = "DLWSDV10"
    (GSI) INFO: release  = "5.2"
    (GSI) INFO: version  = "3790 Service Pack 1"
    (GSI) INFO: machine  = "8x Intel 801586 (Mod 4 Step 9)"
    (DB) ERROR: DDL statement failed
    (DROP INDEX "D010TAB~0")
    DbSlExecute: rc = 103
      (SQL error 1418)
      error message returned by DbSl:
    ORA-01418: specified index does not exist
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    DbSl Trace: ORA-1652 occured when executing SQL statement (parse error offset = 35)
    DbSl Trace: sc_p=013ECFEC,no=1,idc_p=00000000,con=0,act=0,slen=187,smax=256,#vars=0,stmt=01E06DA8,table=
    DbSl Trace: CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (\
    DbSl Trace: INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) ;
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
    DbSlExecute: rc = 99
      (SQL error 1652)
      error message returned by DbSl:
    ORA-01652: unable to extend temp segment by 2560 in tablespace PSAPTEMP
    DbSl Trace: Disconnecting from connection 0 ...
    DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
    DbSl Trace: Detaching from DB Server (con_hdl=0,svchp=0146C57C,srvhp=0146E82C)
    DbSl Trace: Now I'm disconnected from ORACLE
    (DB) INFO: disconnected from DB
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: job finished with 1 error(s)
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: END OF LOG: 20061222023612
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222031914
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.cmd -l C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.log -stop_on_error
    DbSl Trace: Got ORACLE_HOME=D:\oracle\idn\928 from environment
    DbSl Trace: Client NLS settings: AMERICAN_AMERICA.WE8DEC
    DbSl Trace: Logon as OPS$-user to get SAPIDN's password
    DbSl Trace: Connecting as /@IDN on connection 0 ...
    DbSl Trace: Attaching to DB Server IDN (con_hdl=0,svchp=0146C57C,svrhp=0146E82C)
    DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
    DbSl Trace: Now I'm connected to ORACLE
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    DbSl Trace: Disconnecting from connection 0 ...
    DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
    DbSl Trace: Now I'm disconnected from ORACLE
    DbSl Trace: Try to connect with default password
    DbSl Trace: Connecting as SAPIDN/<pwd>@IDN on connection 0 ...
    DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
    DbSl Trace: Now I'm connected to ORACLE
    DbSl Trace: Database NLS settings: AMERICAN_AMERICA.WE8DEC
    DbSl Trace: Database instance idn is running on DLWSDV10 with ORACLE version 9.2.0.8.0 since 20061222
    (DB) INFO: connected to DB
    (GSI) INFO: dbname   = "IDN20061222121231                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "DLWSDV10                                                        "
    (GSI) INFO: sysname  = "Windows NT"
    (GSI) INFO: nodename = "DLWSDV10"
    (GSI) INFO: release  = "5.2"
    (GSI) INFO: version  = "3790 Service Pack 1"
    (GSI) INFO: machine  = "8x Intel 801586 (Mod 4 Step 9)"
    (DB) ERROR: DDL statement failed
    (DROP INDEX "D010TAB~0")
    DbSlExecute: rc = 103
      (SQL error 1418)
      error message returned by DbSl:
    ORA-01418: specified index does not exist
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    DbSl Trace: ORA-1652 occured when executing SQL statement (parse error offset = 35)
    DbSl Trace: sc_p=013ECFEC,no=1,idc_p=00000000,con=0,act=0,slen=187,smax=256,#vars=0,stmt=01E06DA8,table=
    DbSl Trace: CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (\
    DbSl Trace: INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) ;
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
    DbSlExecute: rc = 99
      (SQL error 1652)
      error message returned by DbSl:
    ORA-01652: unable to extend temp segment by 2560 in tablespace PSAPTEMP
    DbSl Trace: Disconnecting from connection 0 ...
    DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
    DbSl Trace: Detaching from DB Server (con_hdl=0,svchp=0146C57C,srvhp=0146E82C)
    DbSl Trace: Now I'm disconnected from ORACLE
    (DB) INFO: disconnected from DB
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: job finished with 1 error(s)
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: END OF LOG: 20061222031938
    <b><u>SAPAPPL0.log</u></b>
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222010528
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe -ctf I G:\Export/DATA/SAPAPPL0.STR C:\SAPinst ORACLE SAPINST_di/DDLORA.TPL C:\SAPinst ORACLE SAPINST_di/SAPAPPL0.TSK ORA -l C:\SAPinst ORACLE SAPINST_di/SAPAPPL0.log
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: job completed
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: END OF LOG: 20061222010530
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222010539
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
    D:\usr\sap\IDN\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst ORACLE SAPINST_di/SAPAPPL0.cmd -l C:\SAPinst ORACLE SAPINST_di/SAPAPPL0.log -stop_on_error
    DbSl Trace: Got ORACLE_HOME=D:\oracle\idn\928 from environment
    DbSl Trace: Client NLS settings: AMERICAN_AMERICA.WE8DEC
    DbSl Trace: Logon as OPS$-user to get SAPIDN's password
    DbSl Trace: Connecting as /@IDN on connection 0 ...
    DbSl Trace: Attaching to DB Server IDN (con_hdl=0,svchp=0146C57C,svrhp=0146E82C)
    DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
    DbSl Trace: Now I'm connected to ORACLE
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    DbSl Trace: Disconnecting from connection 0 ...
    DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
    DbSl Trace: Now I'm disconnected from ORACLE
    DbSl Trace: Try to connect with default password
    DbSl Trace: Connecting as SAPIDN/<pwd>@IDN on connection 0 ...
    DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
    DbSl Trace: Now I'm connected to ORACLE
    DbSl Trace: Database NLS settings: AMERICAN_AMERICA.WE8DEC
    DbSl Trace: Database instance idn is running on DLWSDV10 with ORACLE version 9.2.0.8.0 since 20061222
    Fri Dec 22 01:05:39 2006
    ***LOG BZA=> table SVERS      does not exist on database [dblink#1 @ 1292] [dblink  1292 ]
    (DB) INFO: connected to DB
    (GSI) INFO: dbname   = "IDN20061222121231                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "DLWSDV10                                                        "
    (GSI) INFO: sysname  = "Windows NT"
    (GSI) INFO: nodename = "DLWSDV10"
    (GSI) INFO: release  = "5.2"
    (GSI) INFO: version  = "3790 Service Pack 1"
    (GSI) INFO: machine  = "8x Intel 801586 (Mod 4 Step 9)"
    (DB) INFO: /1SAP1/FC_TFG200 created
    (IMP) INFO: import of /1SAP1/FC_TFG200 completed (3 rows)
    (DB) INFO: /1SAP1/FC_TFG200~0 created
    (DB) INFO: /1SAP1/FC_TFG201 created
    (IMP) INFO: import of /1SAP1/FC_TFG201 completed (2 rows)
    (DB) INFO: /1SAP1/FC_TFG201~0 created
    (DB) INFO: /1SAP1/FC_TFG300 created
    (IMP) INFO: import of /1SAP1/FC_TFG300 completed (3 rows)
    (DB) INFO: /1SAP1/FC_TFG300~0 created
    (DB) INFO: /1SAP1/FC_TFG301 created
    (IMP) INFO: import of /1SAP1/FC_TFG301 completed (4 rows)
    (DB) INFO: /1SAP1/FC_TFG301~0 created
    (DB) INFO: /SAPDMC/LSCDOCU created
    (IMP) INFO: import of /SAPDMC/LSCDOCU completed (25 rows)
    (DB) INFO: /SAPDMC/LSCDOCU~0 created
    (DB) INFO: /SAPDMC/LSCDOCUT created
    (IMP) INFO: import of /SAPDMC/LSCDOCUT completed (200 rows)
    (DB) INFO: /SAPDMC/LSCDOCUT~0 created
    (DB) INFO: /SAPDMC/LSCRULE created
    (IMP) INFO: import of /SAPDMC/LSCRULE completed (15 rows)
    (DB) INFO: /SAPDMC/LSCRULE~0 created
    (DB) INFO: /SAPDMC/LSCRULET created
    (IMP) INFO: import of /SAPDMC/LSCRULET completed (119 rows)
    (DB) INFO: /SAPDMC/LSCRULET~0 created
    (DB) INFO: /SAPDMC/LSCSTEPS created
    (IMP) INFO: import of /SAPDMC/LSCSTEPS completed (62 rows)
    (DB) INFO: /SAPDMC/LSCSTEPS~0 created
    (DB) INFO: /SAPDMC/LSCSTEPT created
    (IMP) INFO: import of /SAPDMC/LSCSTEPT completed (495 rows)
    (DB) INFO: /SAPDMC/LSCSTEPT~0 created
    (DB) INFO: /SAPDMC/LSCVERSN created
    (IMP) INFO: import of /SAPDMC/LSCVERSN completed (19 rows)
    (DB) INFO: /SAPDMC/LSCVERSN~0 created
    (DB) INFO: /SAPDMC/LSGBDCA created
    (IMP) INFO: import of /SAPDMC/LSGBDCA completed (74 rows)
    (DB) INFO: /SAPDMC/LSGBDCA~0 created
    (DB) INFO: /SAPDMC/LSGBDCS created
    (IMP) INFO: import of /SAPDMC/LSGBDCS completed (74 rows)
    (DB) INFO: /SAPDMC/LSGBDCS~0 created
    (DB) INFO: /SAPDMC/LSGBDCT created
    (IMP) INFO: import of /SAPDMC/LSGBDCT completed (74 rows)
    (DB) INFO: /SAPDMC/LSGBDCT~0 created
    (DB) INFO: /SAPDMC/LSGCUST created
    (IMP) INFO: import of /SAPDMC/LSGCUST completed (0 rows)
    (DB) INFO: /SAPDMC/LSGCUST~0 created
    (DB) INFO: /SAPDMC/LSGSUB created
    (IMP) INFO: import of /SAPDMC/LSGSUB completed (166 rows)
    (DB) INFO: /SAPDMC/LSGSUB~0 created
    (DB) INFO: /SAPDMC/LSGUSDFI created
    (IMP) INFO: import of /SAPDMC/LSGUSDFI completed (16 rows)
    (DB) INFO: /SAPDMC/LSGUSDFI~0 created
    (DB) INFO: /SAPDMC/LSMCUST created
    (IMP) INFO: import of /SAPDMC/LSMCUST completed (0 rows)
    (DB) INFO: /SAPDMC/LSMCUST~0 created
    (DB) INFO: /SAPDMC/LSOALG created
    (IMP) INFO: import of /SAPDMC/LSOALG completed (1250 rows)
    (DB) INFO: /SAPDMC/LSOALG~0 created
    (DB) INFO: /SAPDMC/LSOATT created
    (IMP) INFO: import of /SAPDMC/LSOATT completed (269 rows)
    (DB) INFO: /SAPDMC/LSOATT~0 created
    (DB) INFO: /SAPDMC/LSOLOG created
    (IMP) INFO: import of /SAPDMC/LSOLOG completed (461 rows)
    (DB) INFO: /SAPDMC/LSOLOG~0 created
    (DB) INFO: /SAPDMC/LSOPAR created
    (IMP) INFO: import of /SAPDMC/LSOPAR completed (1421 rows)
    (DB) INFO: /SAPDMC/LSOPAR~0 created
    (DB) INFO: /SAPDMC/LSOREC created
    (IMP) INFO: import of /SAPDMC/LSOREC completed (56 rows)
    (DB) INFO: /SAPDMC/LSOREC~0 created
    (DB) INFO: /SAPDMC/LSOTXT created
    (IMP) INFO: import of /SAPDMC/LSOTXT completed (455 rows)
    (DB) INFO: /SAPDMC/LSOTXT~0 created
    (DB) INFO: /SAPDMC/LSRATT created
    (IMP) INFO: import of /SAPDMC/LSRATT completed (304 rows)
    (DB) INFO: /SAPDMC/LSRATT~0 created
    (DB) INFO: /SAPDMC/LSRTXT created
    (IMP) INFO: import of /SAPDMC/LSRTXT completed (308 rows)
    (DB) INFO: /SAPDMC/LSRTXT~0 created
    (DB) INFO: /SAPDMC/LSUCUST created
    (IMP) INFO: import of /SAPDMC/LSUCUST completed (22 rows)
    (DB) INFO: /SAPDMC/LSUCUST~0 created
    (DB) INFO: /SAPDMC/LSUMENU created
    (IMP) INFO: import of /SAPDMC/LSUMENU completed (0 rows)
    (DB) INFO: /SAPDMC/LSUMENU~0 created
    (DB) INFO: /SAPDMC/LSUPROF created
    (IMP) INFO: import of /SAPDMC/LSUPROF completed (19 rows)
    (DB) INFO: /SAPDMC/LSUPROF~0 created
    (DB) INFO: /SAPNEA/MR3_SODT created
    (IMP) INFO: import of /SAPNEA/MR3_SODT completed (0 rows)
    (DB) INFO: /SAPNEA/MR3_SODT~0 created
    (DB) INFO: /SAPSLL/ECPPA created
    (IMP) INFO: import of /SAPSLL/ECPPA completed (0 rows)
    (DB) INFO: /SAPSLL/ECPPA~0 created
    (DB) INFO: /SAPSMOSS/STAT created
    (IMP) INFO: import of /SAPSMOSS/STAT completed (9 rows)
    (DB) INFO: /SAPSMOSS/STAT~0 created
    (DB) INFO: /SAPSMOSS/STATT created
    (IMP) INFO: import of /SAPSMOSS/STATT completed (171 rows)
    (DB) INFO: /SAPSMOSS/STATT~0 created
    (DB) INFO: /SAPSMOSS/TURL created
    (IMP) INFO: import of /SAPSMOSS/TURL completed (4 rows)
    (DB) INFO: /SAPSMOSS/TURL~0 created
    (DB) INFO: /SAPTRX/APARPRF created
    (IMP) INFO: import of /SAPTRX/APARPRF completed (0 rows)
    (DB) INFO: /SAPTRX/APARPRF~0 created
    (DB) INFO: /SAPTRX/APARPRFT created
    (IMP) INFO: import of /SAPTRX/APARPRFT completed (0 rows)
    (DB) INFO: /SAPTRX/APARPRFT~0 created
    (DB) INFO: /SAPTRX/ASFCTEV created
    (IMP) INFO: import of /SAPTRX/ASFCTEV completed (40 rows)
    (DB) INFO: /SAPTRX/ASFCTEV~0 created
    (DB) INFO: /SAPTRX/ASFCTEVT created
    (IMP) INFO: import of /SAPTRX/ASFCTEVT completed (88 rows)
    (DB) INFO: /SAPTRX/ASFCTEVT~0 created
    (DB) INFO: /SAPTRX/ASFCTPAR created
    (IMP) INFO: import of /SAPTRX/ASFCTPAR completed (305 rows)
    (DB) INFO: /SAPTRX/ASFCTPAR~0 created
    (DB) INFO: /SAPTRX/ASFCTPAT created
    (IMP) INFO: import of /SAPTRX/ASFCTPAT completed (671 rows)
    (DB) INFO: /SAPTRX/ASFCTPAT~0 created
    (DB) INFO: /SAPTRX/ASPARDC created
    (IMP) INFO: import of /SAPTRX/ASPARDC completed (0 rows)
    (DB) INFO: /SAPTRX/ASPARDC~0 created
    (DB) INFO: /SAPTRX/ASPARDCT created
    (IMP) INFO: import of /SAPTRX/ASPARDCT completed (0 rows)
    (DB) INFO: /SAPTRX/ASPARDCT~0 created
    (DB) INFO: /SAPTRX/SCSOMAP created
    (IMP) INFO: import of /SAPTRX/SCSOMAP completed (0 rows)
    (DB) INFO: /SAPTRX/SCSOMAP~0 created
    (DB) INFO: /SAPTRX/SOLUTN created
    (IMP) INFO: import of /SAPTRX/SOLUTN completed (0 rows)
    (DB) INFO: /SAPTRX/SOLUTN~0 created
    (DB) INFO: /SAPTRX/SOLUTNT created
    (IMP) INFO: import of /SAPTRX/SOLUTNT completed (0 rows)
    (DB) INFO: /SAPTRX/SOLUTNT~0 created
    (DB) INFO: /SDF/STGLTRAN created
    (IMP) INFO: import of /SDF/STGLTRAN completed (0 rows)
    (DB) INFO: /SDF/STGLTRAN~0 created
    (DB) INFO: /SOMO/INPUTTAB created
    (IMP) INFO: import of /SOMO/INPUTTAB completed (12 rows)
    (DB) INFO: /SOMO/INPUTTAB~0 created
    (DB) INFO: A000 created
    (IMP) INFO: import of A000 completed (0 rows)
    (DB) INFO: A000~0 created
    (DB) INFO: A002 created
    (IMP) INFO: import of A002 completed (68 rows)
    (DB) INFO: A002~0 created
    (DB) INFO: A008 created
    (IMP) INFO: import of A008 completed (0 rows)
    (DB) INFO: A008~0 created
    (DB) INFO: A011 created
    (IMP) INFO: import of A011 completed (28 rows)
    (DB) INFO: A011~0 created
    (DB) INFO: A013 created
    (IMP) INFO: import of A013 completed (68 rows)
    (DB) INFO: A013~0 created
    (DB) INFO: A014 created
    (IMP) INFO: import of A014 completed (62 rows)
    (DB) INFO: A014~0 created
    (DB) INFO: A020 created
    (IMP) INFO: import of A020 completed (2 rows)
    (DB) INFO: A020~0 created
    (DB) INFO: A027 created
    (IMP) INFO: import of A027 completed (16 rows)
    (DB) INFO: A027~0 created
    (DB) INFO: A029 created
    (IMP) INFO: import of A029 completed (0 rows)
    (DB) INFO: A029~0 created
    (DB) INFO: A031 created
    (IMP) INFO: import of A031 completed (0 rows)
    (DB) INFO: A031~0 created
    (DB) INFO: A033 created
    (IMP) INFO: import of A033 completed (8 rows)
    (DB) INFO: A033~0 created
    (DB) INFO: A034 created
    (IMP) INFO: import of A034 completed (0 rows)
    (DB) INFO: A034~0 created
    (DB) INFO: A035 created
    (IMP) INFO: import of A035 completed (56 rows)
    (DB) INFO: A035~0 created
    (DB) INFO: A036 created
    (IMP) INFO: import of A036 completed (56 rows)
    (DB) INFO: A036~0 created
    (DB) INFO: A037 created
    (IMP) INFO: import of A037 completed (56 rows)
    (DB) INFO: A037~0 created
    (DB) INFO: A038 created
    (IMP) INFO: import of A038 completed (56 rows)
    (DB) INFO: A038~0 created
    (DB) INFO: A039 created
    (IMP) INFO: import of A039 completed (56 rows)
    (DB) INFO: A039~0 created
    (DB) INFO: A040 created
    (IMP) INFO: import of A040 completed (454 rows)
    (DB) INFO: A040~0 created
    (DB) INFO: A041 created
    (IMP) INFO: import of A041 completed (0 rows)
    (DB) INFO: A041~0 created
    (DB) INFO: A042 created
    (IMP) INFO: import of A042 completed (0 rows)
    (DB) INFO: A042~0 created
    (DB) INFO: A043 created
    (IMP) INFO: import of A043 completed (0 rows)
    (DB) INFO: A043~0 created
    (DB) INFO: A048 created
    (IMP) INFO: import of A048 completed (0 rows)
    (DB) INFO: A048~0 created
    (DB) INFO: A050 created
    (IMP) INFO: import of A050 completed (2 rows)
    (DB) INFO: A050~0 created
    (DB) INFO: A057 created
    (IMP) INFO: import of A057 completed (1364 rows)
    (DB) INFO: A057~0 created
    (DB) INFO: A066 created
    (IMP) INFO: import of A066 completed (4 rows)
    (DB) INFO: A066~0 created
    (DB) INFO: A067 created
    (IMP) INFO: import of A067 completed (1 rows)
    (DB) INFO: A067~0 created
    (DB) INFO: A068 created
    (IMP) INFO: import of A068 completed (0 rows)
    (DB) INFO: A068~0 created
    (DB) INFO: A069 created
    (IMP) INFO: import of A069 completed (0 rows)
    (DB) INFO: A069~0 created
    (DB) INFO: A070 created
    (IMP) INFO: import of A070 completed (0 rows)
    (DB) INFO: A070~0 created
    (DB) INFO: A071 created
    (IMP) INFO: import of A071 completed (70 rows)
    (DB) INFO: A071~0 created
    (DB) INFO: A072 created
    (IMP) INFO: import of A072 completed (0 rows)
    (DB) INFO: A072~0 created
    (DB) INFO: A073 created
    (IMP) INFO: import of A073 completed (159 rows)
    (DB) INFO: A073~0 created
    (DB) INFO: A074 created
    (IMP) INFO: import of A074 completed (0 rows)
    (DB) INFO: A074~0 created
    (DB) INFO: A075 created
    (IMP) INFO: import of A075 completed (0 rows)
    (DB) INFO: A075~0 created
    (DB) INFO: A076 created
    (IMP) INFO: import of A076 completed (0 rows)
    (DB) INFO: A076~0 created
    (DB) INFO: A077 created
    (IMP) INFO: import of A077 completed (0 rows)
    (DB) INFO: A077~0 created
    (DB) INFO: A078 created
    (IMP) INFO: import of A078 completed (10 rows)
    (DB) INFO: A078~0 created
    (DB) INFO: A079 created
    (IMP) INFO: import of A079 completed (84 rows)
    (DB) INFO: A079~0 created
    (DB) INFO: A080 created
    (IMP) INFO: import of A080 completed (0 rows)
    (DB) INFO: A080~0 created
    (DB) INFO: A081 created
    (IMP) INFO: import of A081 completed (1128 rows)
    (DB) INFO: A081~0 created
    (DB) INFO: A082 created
    (IMP) INFO: import of A082 completed (0 rows)
    (DB) INFO: A082~0 created
    (DB) INFO: A083 created
    (IMP) INFO: import of A083 completed (0 rows)
    (DB) INFO: A083~0 created
    (DB) INFO: A084 created
    (IMP) INFO: import of A084 completed (0 rows)
    (DB) INFO: A084~0 created
    (DB) INFO: A085 created
    (IMP) INFO: import of A085 completed (0 rows)
    (DB) INFO: A085~0 created
    (DB) INFO: A086 created
    (IMP) INFO: import of A086 completed (0 rows)
    (DB) INFO: A086~0 created
    (DB) INFO: A087 created
    (IMP) INFO: import of A087 completed (10 rows)
    (DB) INFO: A087~0 created
    (DB) INFO: A088 created
    (IMP) INFO: import of A088 completed (0 rows)
    (DB) INFO: A088~0 created
    (DB) INFO: A089 created
    (IMP) INFO: import of A089 completed (0 rows)
    (DB) INFO: A089~0 created
    (DB) INFO: A090 created
    (IMP) INFO: import of A090 completed (42 rows)
    (DB) INFO: A090~0 created
    (DB) INFO: A091 created
    (IMP) INFO: import of A091 completed (0 rows)
    (DB) INFO: A091~0 created
    (DB) INFO: A092 created
    (IMP) INFO: import of A092 completed (0 rows)
    (DB) INFO: A092~0 created
    (DB) INFO: A093 created
    (IMP) INFO: import of A093 completed (0 rows)
    (DB) INFO: A093~0 created
    (DB) INFO: A094 created
    (IMP) INFO: import of A094 completed (0 rows)
    (DB) INFO: A094~0 created
    (DB) INFO: A095 created
    (IMP) INFO: import of A095 completed (0 rows)
    (DB) INFO: A095~0 created
    (DB) INFO: A096 created
    (IMP) INFO: import of A096 completed (41 rows)
    (DB) INFO: A096~0 created
    (DB) INFO: A097 created
    (IMP) INFO: import of A097 completed (56 rows)
    (DB) INFO: A097~0 created
    (DB) INFO: A098 created
    (IMP) INFO: import of A098 completed (2 rows)
    (DB) INFO: A098~0 created
    (DB) INFO: A099 created
    (IMP) INFO: import of A099 completed (2 rows)
    (DB) INFO: A099~0 created
    (DB) INFO: A100 created
    (IMP) INFO: import of A100 completed (0 rows)
    (DB) INFO: A100~0 created
    (DB) INFO: A101 created
    (IMP) INFO: import of A101 completed (0 rows)
    (DB) INFO: A101~0 created
    (DB) INFO: A102 created
    (IMP) INFO: import of A102 completed (0 rows)
    (DB) INFO: A102~0 created
    (DB) INFO: A103 created
    (IMP) INFO: import of A103 completed (0 rows)
    (DB) INFO: A103~0 created
    (DB) INFO: A104 created
    (IMP) INFO: import of A104 completed (150 rows)
    (DB) INFO: A104~0 created
    (DB) INFO: A105 created
    (IMP) INFO: import of A105 completed (192 rows)
    (DB) INFO: A105~0 created
    (DB) INFO: A106 created
    (IMP) INFO: import of A106 completed (0 rows)
    (DB) INFO: A106~0 created
    (DB) INFO: A107 created
    (IMP) INFO: import of A107 completed (0 rows)
    (DB) INFO: A107~0 created
    (DB) INFO: A108 created
    (IMP) INFO: import of A108 completed (0 rows)
    (DB) INFO: A108~0 created
    (DB) INFO: A109 created
    (IMP) INFO: import of A109 completed (0 rows)
    (DB) INFO: A109~0 created
    (DB) INFO: A110 created
    (IMP) INFO: import of A110 completed (0 rows)
    (DB) INFO: A110~0 created
    (DB) INFO: A112 created
    (IMP) INFO: import of A112 completed (15 rows)
    (DB) INFO: A112~0 created
    (DB) INFO: A113 created
    (IMP) INFO: import of A113 completed (0 rows)
    (DB) INFO: A113~0 created
    (DB) INFO: A114 created
    (IMP) INFO: import of A114 completed (0 rows)
    (DB) INFO: A114~0 created
    (DB) INFO: A115 created
    (IMP) INFO: import of A115 completed (0 rows)
    (DB) INFO: A115~0 created
    (DB) INFO: A116 created
    (IMP) INFO: import of A116 completed (0 rows)
    (DB) INFO: A116~0 created
    (DB) INFO: A117 created
    (IMP) INFO: import of A117 completed (0 rows)
    (DB) INFO: A117~0 created
    (DB) INFO: A118 created
    (IMP) INFO: import of A118 completed (12 rows)
    (DB) INFO: A118~0 created
    (DB) INFO: A119 created
    (IMP) INFO: import of A119 completed (0 rows)
    (DB) INFO: A119~0 created
    (DB) INFO: A120 created
    (IMP) INFO: import of A120 completed (0 rows)
    (DB) INFO: A120~0 created
    (DB) INFO: A121 created
    (IMP) INFO: import of A121 completed (0 rows)
    (DB) INFO: A121~0 created
    (DB) INFO: A122 created
    (IMP) INFO: import of A122 completed (0 rows)
    (DB) INFO: A122~0 created
    (DB) INFO: A123 created
    (IMP) INFO: import of A123 completed (0 rows)
    (DB) INFO: A123~0 created
    (DB) INFO: A124 created
    (IMP) INFO: import of A124 completed (0 rows)
    (DB) INFO: A124~0 created
    (DB) INFO: A125 created
    (IMP) INFO: import of A125 completed (73 rows)
    (DB) INFO: A125~0 created
    (DB) INFO: A126 created
    (IMP) INFO: import of A126 completed (0 rows)
    (DB) INFO: A126~0 created
    (DB) INFO: A127 created
    (IMP) INFO: import of A127 completed (0 rows)
    (DB) INFO: A127~0 created
    (DB) INFO: A128 created
    (IMP) INFO: import of A128 completed (0 rows)
    (DB) INFO: A128~0 created
    (DB) INFO: A129 created
    (IMP) INFO: import of A129 completed (0 rows)
    (DB) INFO: A129~0 created
    (DB) INFO: A130 created
    (IMP) INFO: import of A130 completed (0 rows)
    (DB) INFO: A130~0 created
    (DB) INFO: A131 created
    (IMP) INFO: import of A131 completed (0 rows)
    (DB) INFO: A131~0 created
    (DB) INFO: A132 created
    (IMP) INFO: import of A132 completed (0 rows)
    (DB) INFO: A132~0 created
    (DB) INFO: A133 created
    (IMP) INFO: import of A133 completed (0 rows)
    (DB) INFO: A133~0 created
    (DB) INFO: A134 created
    (IMP) INFO: import of A134 completed (0 rows)
    (DB) INFO: A134~0 created
    (DB) INFO: A135 created
    (IMP) INFO: import of A135 completed (0 rows)
    (DB) INFO: A135~0 created
    (DB) INFO: A136 created
    (IMP) INFO: import of A136 completed (8 rows)
    (DB) INFO: A136~0 created
    (DB) INFO: A137 created
    (IMP) INFO: import of A137 completed (0 rows)
    (DB) INFO: A137~0 created
    (DB) INFO: A138 created
    (IMP) INFO: import of A138 completed (0 rows)
    (DB) INFO: A138~0 created
    (DB) INFO: A139 created
    (IMP) INFO: import of A139 completed (0 rows)
    (DB) INFO: A139~0 created
    (DB) INFO: A140 created
    (IMP) INFO: import of A140 completed (2 rows)
    (DB) INFO: A140~0 created
    (DB) INFO: A141 created
    (IMP) INFO: import of A141 completed (0 rows)
    (DB) INFO: A141~0 created
    (DB) INFO: A142 created
    (IMP) INFO: import of A142 completed (0 rows)
    (DB) INFO: A142~0 created
    (DB) INFO: A143 created
    (IMP) INFO: import of A143 completed (0 rows)
    (DB) INFO: A143~0 created
    (DB) INFO: A144 created
    (IMP) INFO: import of A144 completed (0 rows)
    (DB) INFO: A144~0 created
    (DB) INFO: A145 created
    (IMP) INFO: import of A145 completed (0 rows)
    (DB) INFO: A145~0 created
    (DB) INFO: A146 created
    (IMP) INFO: import of A146 completed (0 rows)
    (DB) INFO: A146~0 created
    (DB) INFO: A147 created
    (IMP) INFO: import of A147 completed (0 rows)
    (DB) INFO: A147~0 created
    (DB) INFO: A148 created
    (IMP) INFO: import of A148 completed (0 rows)
    (DB) INFO: A148~0 created
    (DB) INFO: A149 created
    (IMP) INFO: import of A149 completed (0 rows)
    (DB) INFO: A149~0 created
    (DB) INFO: A152 created
    (IMP) INFO: import of A152 completed (0 rows)
    (DB) INFO: A152~0 created
    (DB) INFO: A153 created
    (IMP) INFO: import of A153 completed (0 rows)
    (DB) INFO: A153~0 created
    (DB) INFO: A154 created
    (IMP) INFO: import of A154 completed (0 rows)
    (DB) INFO: A154~0 created
    (DB) INFO: A155 created
    (IMP) INFO: import of A155 completed (0 rows)
    (DB) INFO: A155~0 created
    (DB) INFO: A156 created
    (IMP) INFO: import of A156 completed (0 rows)
    (DB) INFO: A156~0 created
    (DB) INFO: A160 created
    (IMP) INFO: import of A160 completed (7 rows)
    (DB) INFO: A160~0 created
    (DB) INFO: A161 created
    (IMP) INFO: import of A161 completed (0 rows)
    (DB) INFO: A161~0 created
    (DB) INFO: A162 created
    (IMP) INFO: import of A162 completed (0 rows)
    (DB) INFO: A162~0 created
    (DB) INFO: A173 created
    (IMP) INFO: import of A173 completed (0 rows)
    (DB) INFO: A173~0 created
    (DB) INFO: A174 created
    (IMP) INFO: import of A174 completed (0 rows)
    (DB) INFO: A174~0 created
    (DB) INFO: A175 created
    (IMP) INFO: import of A175 completed (0 rows)
    (DB) INFO: A175~0 created
    (DB) INFO: A176 created
    (IMP) INFO: import of A176 completed (0 rows)
    (DB) INFO: A176~0 created
    (DB) INFO: A177 created
    (IMP) INFO: import of A177 completed (0 rows)
    (DB) INFO: A177~0 created
    (DB) INFO: A178 created
    (IMP) INFO: import of A178 completed (0 rows)
    (DB) INFO: A178~0 created
    (DB) INFO: A179 created
    (IMP) INFO: import of A179 completed (0 rows)
    (DB) INFO: A179~0 created
    (DB) INFO: A180 created
    (IMP) INFO: import of A180 completed (0 rows)
    (DB) INFO: A180~0 created
    (DB) INFO: A185 created
    (IMP) INFO: import of A185 completed (0 rows)
    (DB) INFO: A185~0 created
    (DB) INFO: A190 created
    (IMP) INFO: import of A190 completed (0 rows)
    (DB) INFO: A190~0 created
    (DB) INFO: A191 created
    (IMP) INFO: import of A191 completed (0 rows)
    (DB) INFO: A191~0 created
    (DB) INFO: A192 created
    (IMP) INFO: import of A192 completed (0 rows)
    (DB) INFO: A192~0 created
    (DB) INFO: A193 created
    (IMP) INFO: import of A193 completed (0 rows)
    (DB) INFO: A193~0 created
    (DB) INFO: A194 created
    (IMP) INFO: import of A194 completed (0 rows)
    (DB) INFO: A194~0 created
    (DB) INFO: A195 created
    (IMP) INFO: import of A195 completed (13 rows)
    (DB) INFO: A195~0 created
    (DB) INFO: A196 created
    (IMP) INFO: import of A196 completed (0 rows)
    (DB) INFO: A196~0 created
    (DB) INFO: A197 created
    (IMP) INFO: import of A197 completed (5 rows)
    (DB) INFO: A197~0 created
    (DB) INFO: A198 created
    (IMP) INFO: import of A198 completed (0 rows)
    (DB) INFO: A198~0 created
    (DB) INFO: A215 created
    (IMP) INFO: import of A215 completed (0 rows)
    (DB) INFO: A215~0 created
    (DB) INFO: A291 created
    (IMP) INFO: import of A291 completed (0 rows)
    (DB) INFO: A291~0 created
    (DB) INFO: A292 created
    (IMP) INFO: import of A292 completed (0 rows)
    (DB) INFO: A292~0 created
    (DB) INFO: A293 created
    (IMP) INFO: import of A293 completed (0 rows)
    (DB) INFO: A293~0 created
    (DB) INFO: A300 created
    (IMP) INFO: import of A300 completed (0 rows)
    (DB) INFO: A300~0 created
    (DB) INFO: A301 created
    (IMP) INFO: import of A301 completed (0 rows)
    (DB) INFO: A301~0 created
    (DB) INFO: A304 created
    (IMP) INFO: import of A304 completed (3414 rows)
    (DB) INFO: A304~0 created
    (DB) INFO: A305 created
    (IMP) INFO: import of A305 completed (54 rows)
    (DB) INFO: A305~0 created
    (DB) INFO: A306 created
    (IMP) INFO: import of A306 completed (0 rows)
    (DB) INFO: A306~0 created
    (DB) INFO: A307 created
    (IMP) INFO: import of A307 completed (0 rows)
    (DB) INFO: A307~0 created
    (DB) INFO: A310 created
    (IMP) INFO: import of A310 completed (0 rows)
    (DB) INFO: A310~0 created
    (DB) INFO: A311 created
    (IMP) INFO: import of A311 completed (0 rows)
    (DB) INFO: A311~0 created
    (DB) INFO: A312 created
    (IMP) INFO: import of A312 completed (0 rows)
    (DB) INFO: A312~0 created
    (DB) INFO: A315 created
    (IMP) INFO: import of A315 completed (0 rows)
    (DB) INFO: A315~0 created
    (DB) INFO: A316 created
    (IMP) INFO: import of A316 completed (0 rows)
    (DB) INFO: A316~0 created
    (DB) INFO: A317 created
    (IMP) INFO: import of A317 completed (0 rows)
    (DB) INFO: A317~0 created
    (DB) INFO: A320 created
    (IMP) INFO: import of A320 completed (0 rows)
    (DB) INFO: A320~0 created
    (DB) INFO: A321 created
    (IMP) INFO: import of A321 completed (0 rows)
    (DB) INFO: A321~0 created
    (DB) INFO: A325 created
    (IMP) INFO: import of A325 completed (0 rows)
    (DB) INFO: A325~0 created
    (DB) INFO: A326 created
    (IMP) INFO: import of A326 completed (0 rows)
    (DB) INFO: A326~0 created
    (DB) INFO: A330 created
    (IMP) INFO: import of A330 completed (0 rows)
    (DB) INFO: A330~0 created
    (DB) INFO: A331 created
    (IMP) INFO: import of A331 completed (0 rows)
    (DB) INFO: A331~0 created
    (DB) INFO: A335 created
    (IMP) INFO: import of A335 completed (0 rows)
    (DB) INFO: A335~0 created
    (DB) INFO: A336 created
    (IMP) INFO: import of A336 completed (0 rows)
    (DB) INFO: A336~0 created
    (DB) INFO: A340 created
    (IMP) INFO: import of A340 completed (0 rows)
    (DB) INFO: A340~0 created
    (DB) INFO: A341 created
    (IMP) INFO: import of A341 completed (0 rows)
    (DB) INFO: A341~0 created
    (DB) INFO: A342 created
    (IMP) INFO: import of A342 completed (0 rows)
    (DB) INFO: A342~0 created
    (DB) INFO: A343 created
    (IMP) INFO: import of A343 completed (0 rows)
    (DB) INFO: A343~0 created
    (DB) INFO: A344 created
    (IMP) INFO: import of A344 completed (0 rows)
    (DB) INFO: A344~0 created
    (DB) INFO: A345 created
    (IMP) INFO: import of A345 completed (0 rows)
    (DB) INFO: A345~0 created
    (DB) INFO: A346 created
    (IMP) INFO: import of A346 completed (0 rows)
    (DB) INFO: A346~0 created
    (DB) INFO: A347 created
    (IMP) INFO: import of A347 completed (0 rows)
    (DB) INFO: A347~0 created
    (DB) INFO: A348 created
    (IMP) INFO: import of A348 completed (0 rows)
    (DB) INFO: A348~0 created
    (DB) INFO: A349 created
    (IMP) INFO: import of A349 completed (0 rows)
    (DB) INFO: A349~0 created
    (DB) INFO: A350 created
    (IMP) INFO: import of A350 completed (0 rows)
    (DB) INFO: A350~0 created
    (DB) INFO: A352 created
    (IMP) INFO: import of A352 completed (0 rows)
    (DB) INFO: A352~0 created
    (DB) INFO: A353 created
    (IMP) INFO: import of A353 completed (0 rows)
    (DB) INFO: A353~0 created
    (DB) INFO: A354 created
    (IMP) INFO: import of A354 completed (0 rows)
    (DB) INFO: A354~0 created
    (DB) INFO: A355 created
    (IMP) INFO: import of A355 completed (0 rows)
    (DB) INFO: A355~0 created
    (DB) INFO: A356 created
    (IMP) INFO: import of A356 completed (0 rows)
    (DB) INFO: A356~0 created
    (DB) INFO: A357 created
    (IMP) INFO: import of A357 completed (0 rows)
    (DB) INFO: A357~0 created
    (DB) INFO: A358 created
    (IMP) INFO: import of A358 completed (0 rows)
    (DB) INFO: A358~0 created
    (DB) INFO: A359 created
    (IMP) INFO: import of A359 completed (0 rows)
    (DB) INFO: A359~0 created
    (DB) INFO: A362 created
    (IMP) INFO: import of A362 completed (0 rows)
    (DB) INFO: A362~0 created
    (DB) INFO: A363 created
    (IMP) INFO: import of A363 completed (0 rows)
    (DB) INFO: A363~0 created
    (DB) INFO: A364 created
    (IMP) INFO: import of A364 completed (0 rows)
    (DB) INFO: A364~0 created
    (DB) INFO: A365 created
    (IMP) INFO: import of A365 completed (0 rows)
    (DB) INFO: A365~0 created
    (DB) INFO: A366 created
    (IMP) INFO: import of A366 completed (0 rows)
    (DB) INFO: A366~0 created
    (DB) INFO: A367 created
    (IMP) INFO: import of A367 completed (0 rows)
    (DB) INFO: A367~0 created
    (DB) INFO: A368 created
    (IMP) INFO: import of A368 completed (0 rows)
    (DB) INFO: A368~0 created
    (DB) INFO: A369 created
    (IMP) INFO: import of A369 completed (0 rows)
    (DB) INFO: A369~0 created
    (DB) INFO: A371 created
    (IMP) INFO: import of A371 completed (0 rows)
    (DB) INFO: A371~0 created
    (DB) INFO: A372 created
    (IMP) INFO: import of A372 completed (0 rows)
    (DB) INFO: A372~0 created
    (DB) INFO: A373 created
    (IMP) INFO: import of A373 completed (0 rows)
    (DB) INFO: A373~0 created
    (DB) INFO: A374 created
    (IMP) INFO: import of A374 completed (0 rows)
    (DB) INFO: A374~0 created
    (DB) INFO: A375 created
    (IMP) INFO: import of A375 completed (0 rows)
    (DB) INFO: A375~0 created
    (DB) INFO: A376 created
    (IMP) INFO: import of A376 completed (0 rows)
    (DB) INFO: A376~0 created
    (DB) INFO: A382 created
    (IMP) INFO: import of A382 completed (0 rows)
    (DB) INFO: A382~0 created
    (DB) INFO: A390 created
    (IMP) INFO: import of A390 completed (4 rows)
    (DB) INFO: A390~0 created
    (DB) INFO: A392 created
    (IMP) INFO: import of A392 completed (0 rows)
    (DB) INFO: A392~0 created
    (DB) INFO: A393 created
    (IMP) INFO: import of A393 completed (0 rows)
    (DB) INFO: A393~0 created
    (DB) INFO: A394 created
    (IMP) INFO: import of A394 completed (0 rows)
    (DB) INFO: A394~0 created
    (DB) INFO: A395 created
    (IMP) INFO: import of A395 completed (5 rows)
    (DB) INFO: A395~0 created
    (DB) INFO: A396 created
    (IMP) INFO: import of A396 completed (0 rows)
    (DB) INFO: A396~0 created
    (DB) INFO: A397 created
    (IMP) INFO: import of A397 completed (0 rows)
    (DB) INFO: A397~0 created
    (DB) INFO: A399 created
    (IMP) INFO: import of A399 completed (0 rows)
    (DB) INFO: A399~0 created
    (DB) INFO: A441 created
    (IMP) INFO: import of A441 completed (0 rows)
    (DB) INFO: A441~0 created
    (DB) INFO: A502 created
    (IMP) INFO: import of A502 completed (58 rows)
    (DB) INFO: A502~0 created
    (DB) INFO: A503 created
    (IMP) INFO: import of A503 completed (7 rows)
    (DB) INFO: A503~0 created
    (DB) INFO: A504 created
    (IMP) INFO: import of A504 completed (4 rows)
    (DB) INFO: A504~0 created
    (DB) INFO: A506 created
    (IMP) INFO: import of A506 completed (10 rows)
    (DB) INFO: A506~0 created
    (DB) INFO: A507 created
    (IMP) INFO: import of A507 completed (0 rows)
    (DB) INFO: A507~0 created
    (DB) INFO: A510 created
    (IMP) INFO: import of A510 completed (0 rows)
    (DB) INFO: A510~0 created
    (DB) INFO: A511 created
    (IMP) INFO: import of A511 completed (0 rows)
    (DB) INFO: A511~0 created
    (DB) INFO: A518 created
    (IMP) INFO: import of A518 completed (0 rows)
    (DB) INFO: A518~0 created
    (DB) INFO: A599 created
    (IMP) INFO: import of A599 completed (0 rows)
    (DB) INFO: A599~0 created
    (DB) INFO: A601 created
    (IMP) INFO: import of A601 completed (3 rows)
    (DB) INFO: A601~0 created
    (DB) INFO: A755 created
    (IMP) INFO: import of A755 completed (0 rows)
    (DB) INFO: A755~0 created
    (DB) INFO: A800 created
    (IMP) INFO: import of A800 completed (1 rows)
    (DB) INFO: A800~0 created
    (DB) INFO: A801 created
    (IMP) INFO: import of A801 completed (0 rows)
    (DB) INFO: A801~0 created
    (DB) INFO: A805 created
    (IMP) INFO: import of A805 completed (0 rows)
    (DB) INFO: A805~0 created
    (DB) INFO: A810 created
    (IMP) INFO: import of A810 completed (0 rows)
    (DB) INFO: A810~0 created
    (DB) INFO: A815 created
    (IMP) INFO: import of A815 completed (0 rows)
    (DB) INFO: A815~0 created
    (DB) INFO: A816 created
    (IMP) INFO: import of A816 completed (1 rows)
    (DB) INFO: A816~0 created
    (DB) INFO: A817 created
    (IMP) INFO: import of A817 completed (0 rows)
    (DB) INFO: A817~0 created
    (DB) INFO: A818 created
    (IMP) INFO: import of A818 completed (6 rows)
    (DB) INFO: A818~0 created
    (DB) INFO: A819 created
    (IMP) INFO: import of A819 completed (0 rows)
    (DB) INFO: A819~0 created
    (DB) INFO: A900 created
    (IMP) INFO: import of A900 completed (250 rows)
    (DB) INFO: A900~0 created
    (DB) INFO: A902 created
    (IMP) INFO: import of A902 completed (0 rows)
    (DB) INFO: A902~0 created
    (DB) INFO: A903 created
    (IMP) INFO: import of A903 completed (11 rows)
    (DB) INFO: A903~0 created
    (DB) INFO: A933 created
    (IMP) INFO: import of A933 completed (0 rows)
    (DB) INFO: A933~0 created
    (DB) INFO: A940 created
    (IMP) INFO: import of A940 completed (0 rows)
    (DB) INFO: A940~0 created
    (DB) INFO: A941 created
    (IMP) INFO: import of A941 completed (0 rows)
    (DB) INFO: A941~0 created
    (DB) INFO: A942 created
    (IMP) INFO: import of A942 completed (0 rows)
    (DB) INFO: A942~0 created
    (DB) INFO: A972 created
    (IMP) INFO: import of A972 completed (0 rows)
    (DB) INFO: A972~0 created
    (DB) INFO: A973 created
    (IMP) INFO: import of A973 completed (0 rows)
    (DB) INFO: A973~0 created
    (DB) INFO: A974 created
    (IMP) INFO: import of A974 completed (0 rows)
    (DB) INFO: A974~0 created
    (DB) INFO: A976 created
    (IMP) INFO: import of A976 completed (0 rows)
    (DB) INFO: A976~0 created
    (DB) INFO: A977 created
    (IMP) INFO: import of A977 completed (0 rows)
    (DB) INFO: A977~0 created
    (DB) INFO: A994 created
    (IMP) INFO: import of A994 completed (0 rows)
    (DB) INFO: A994~0 created
    (DB) INFO: A997 created
    (IMP) INFO: import of A997 completed (0 rows)
    (DB) INFO: A997~0 created
    (DB) INFO: A998 created
    (IMP) INFO: import of A998 completed (1 rows)
    (DB) INFO: A998~0 created
    (DB) INFO: A999 created
    (IMP) INFO: import of A999 completed (0 rows)
    (DB) INFO: A999~0 created
    (DB) INFO: AAA_KEYS created
    (IMP) INFO: import of AAA_KEYS completed (0 rows)
    (DB) INFO: AAA_KEYS~0 created
    (DB) INFO: AAA_ROLES created
    (IMP) INFO: import of AAA_ROLES completed (0 rows)
    (DB) INFO: AAA_ROLES~0 created
    (DB) INFO: AAA_ROLES2 created
    (IMP) INFO: import of AAA_ROLES2 completed (0 rows)
    (DB) INFO: AAA_ROLES2~0 created
    (DB) INFO: AAA_USERS created
    (IMP) INFO: import of AAA_USERS completed (0 rows)
    (DB) INFO: AAA_USERS~0 created
    (DB) INFO: AAA_VALUES created
    (IMP) INFO: import of AAA_VALUES completed (0 rows)
    (DB) INFO: AAA_VALUES~0 created
    (DB) INFO: AAB_ID_ACT created
    (IMP) INFO: import of AAB_ID_ACT completed (0 rows)
    (DB) INFO: AAB_ID_ACT~0 created
    (DB) INFO: AAB_VAR_ID created
    (IMP) INFO: import of AAB_VAR_ID completed (6 rows)
    (DB) INFO: AAB_VAR_ID~0 created
    (DB) INFO: AAB_VAR_ID~ID1 created
    (DB) INFO: AAB_VAR_PROP created
    (IMP) INFO: import of AAB_VAR_PROP completed (9 rows)
    (DB) INFO: AAB_VAR_PROP~0 created
    (DB) INFO: AAB_VAR_PROPT created
    (IMP) INFO: import of AAB_VAR_PROPT completed (18 rows)
    (DB) INFO: AAB_VAR_PROPT~0 created
    (DB) INFO: AAF_ROLES created
    (IMP) INFO: import of AAF_ROLES completed (0 rows)
    (DB) INFO: AAF_ROLES~0 created
    (DB) INFO: AAT_ROLES created
    (IMP) INFO: import of AAT_ROLES completed (0 rows)
    (DB) INFO: AAT_ROLES~0 created
    (DB) INFO: AAT_USERS created
    (IMP) INFO: import of AAT_USERS completed (0 rows)
    (DB) INFO: AAT_USERS~0 created
    (DB) INFO: AAT_VALUES created
    (IMP) INFO: import of AAT_VALUES completed (0 rows)
    (DB) INFO: AAT_VALUES~0 created
    (DB) INFO: AAUSVAR created
    (IMP) INFO: import of AAUSVAR completed (0 rows)
    (DB) INFO: AAUSVAR~0 created
    (DB) INFO: ABAPHTML created
    (IMP) INFO: import of ABAPHTML completed (859 rows)
    (DB) INFO: ABAPHTML~0 created
    (DB) INFO: ABAPTREE created
    (IMP) INFO: import of ABAPTREE completed (487 rows)
    (DB) INFO: ABAPTREE~0 created
    (DB) INFO: ABAPTREET created
    (IMP) INFO: import of ABAPTREET completed (7814 rows)
    (DB) INFO: ABAPTREET~0 created
    (DB) INFO: ABDOCMODE created
    (IMP) INFO: import of ABDOCMODE completed (78 rows)
    (DB) INFO: ABDOCMODE~0 created
    (DB) INFO: ACAC_OBJECTS created
    (IMP) INFO: import of ACAC_OBJECTS completed (0 rows)
    (DB) INFO: ACAC_OBJECTS~0 created
    (DB) INFO: ACAC_OBJECTS~1 created
    (DB) INFO: ACCRBD created
    (IMP) INFO: import of ACCRBD completed (0 rows)
    (DB) INFO: ACCRBD~0 created
    (DB) INFO: ACCRBD~1 created
    (DB) INFO: ACCRFI created
    (IMP) INFO: import of ACCRFI completed (0 rows)
    (DB) INFO: ACCRFI~0 created
    (DB) INFO: ACEDSASSGMT created
    (IMP) INFO: import of ACEDSASSGMT completed (0 rows)
    (DB) INFO: ACEDSASSGMT~0 created
    (DB) INFO: ACEDSOH created
    (IMP) INFO: import of ACEDSOH completed (0 rows)
    (DB) INFO: ACEDSOH~0 created
    (DB) INFO: ACEDSOI created
    (IMP) INFO: import of ACEDSOI completed (0 rows)
    (DB) INFO: ACEDSOI~0 created
    (DB) INFO: ACEDSOP created
    (IMP) INFO: import of ACEDSOP completed (0 rows)
    (DB) INFO: ACEDSOP~0 created
    (DB) INFO: ACEOBJ created
    (IMP) INFO: import of ACEOBJ completed (0 rows)
    (DB) INFO: ACEOBJ~0 created
    (DB) INFO: ACEOBJ~001 created
    (DB) INFO: ACE_SOP_DESTINTN created
    (IMP) INFO: import of ACE_SOP_DESTINTN completed (0 rows)
    (DB) INFO: ACE_SOP_DESTINTN~0 created
    (DB) INFO: ACE_SOP_FFVERSNS created
    (IMP) INFO: import of ACE_SOP_FFVERSNS completed (1 rows)
    (DB) INFO: ACE_SOP_FFVERSNS~0 created
    (DB) INFO: ACE_SOP_FFVRSTXT created
    (IMP) INFO: import of ACE_SOP_FFVRSTXT completed (18 rows)
    (DB) INFO: ACE_SOP_FFVRSTXT~0 created
    (DB) INFO: ACE_SOP_INVERSNS created
    (IMP) INFO: import of ACE_SOP_INVERSNS completed (0 rows)
    (DB) INFO: ACE_SOP_INVERSNS~0 created
    (DB) INFO: ACE_SOP_INVRSTXT created
    (IMP) INFO: import of ACE_SOP_INVRSTXT completed (0 rows)
    (DB) INFO: ACE_SOP_INVRSTXT~0 created
    (DB) INFO: ACE_SOP_REFKEY created
    (IMP) INFO: import of ACE_SOP_REFKEY completed (0

  • Homogeneous System Copy using DB6 specific procedure

    Hello all,
    I'd like to do homogeneous system copy from source system(hostname: host01) to target system(hostname: host02) using DB2 backup/restore procedure.
    Because SAP database has some tables related their hostname, I think it cause some conflicts between target system's hostname(host02) and the records in the new database on target system(it still remains "host01"). 
    Can I avoid this conflicts if I use DB6 redirected restore method?
    Or do I have to do R3load export/import like hetero system copy?
    I know I can start SAP system when I set SAPLOCALHOST=host01 in instance profile on host02, but is there any other good workaround?
    I wonder how you will do if you face this situation.
    Any comments would be appreciated.
    Regards, Ikue

    Hi dirk,
    Thank you for your reply.
    As you mentioned, System copy often brings changing hostname, so the post processing in the SAP's Guide should cover all of influences.
    I had thought SAP database does not contain hostname entries anymore, but, I found one table which contains DBHOST name in ECC database: SAP<SID>.DB6NAVSYST
    ex) SID=ST8, hostname=athens
    athens:db2st8 66> db2 "select DBHOST from SAPST8.DB6NAVSYST"
    DBHOST
    athens
      1 record(s) selected.
    Can I believe these entries will be adjusted during System Copy operation along SAP's Guide(both DB2 backup/restore and R3load)?
    If Yes, when does adjusting occur? (at post processing or during SAPinst?)
    I have very negative impression of changing hostname of SAP system since I read Note 8307...
    Does SAP support change hostname if I do System Copy?
    Best regards,
    Ikue

  • Homogeneous system copy ( sapinst or db specific method )

    I want to make homogeneous system copy ( NW7 ) of ECC6 from PRD to make a QA system on HPUX/Oracle environment. I am wondering which of the following method is better way to go
    System copy with the help of sapinst
    or
    Database specific method
    What are the steps of each method?
    Please help, your help will be highly appreciated.
    Best Regards,
    -Al

    Hi Al,
    Using sapinst is the supported method by SAP but it takes much longer as you'll need to export/import the data and doing this affects availability of your PRD system.  Most companies perform DB backup/restore as it is much quicker and does not require an outage of your PRD system (if you have online backups).  Different databases have different tools for this operations.  Since it only a QA system, I would suggest you do a DB backup/restore.
    Regards,
    Thomas Pham

  • Homogeneous system copy for 4.7.x.1.1 windows/oracle 9.2.0.3.0

    I plan Homogeneous system copy for 4.7.x.1.1 windows/oracle at a
    customer
    downloaded tools(do I have to put extracted files on the sorce machine
    in kernel directory?):
    MIGMON_2-20001410
    MIGMON_2-20001410.SAR
    MIGTIME_2-20001410
    MIGTIME_2-20001410.SAR
    ORABRCOPY_2-20001410
    ORABRCOPY_2-20001410.SAR
    SAPCAR_5-10002026
    SAPCAR_5-10002026.EXE
    SPLIT_2-20001410
    SPLIT_2-20001410.SAR
    I would have additional questions.
    1. In note 516246(System copy for SAP Systems based on SAP Web AS 6.20)
    it is mentioned to download the latest version of R3LDCTL and apply it
    to the system. I have following questions:
    under service.sap.com/patches
    i found only
    R3LDCTL
    Support Package SAP KERNEL 4.5B 32-BIT Windows Server on IA32 32bit
    ORACLE
    Is this file ok?(I will perform a homogeneous system copy of an 4.7x1.1
    system)
    If the file is ok what is meant as apply?(put it in kernel directory?)
    2. Very similar question applies to file R3szchk
    under service.sap.com/patches I found only
    R3szchk
    Support Package SAP KERNEL 4.6C 32-BIT Windows Server on IA32 32bit
    ORACLE
    Is this file ok?(I will perform a homogeneous system copy of an 4.7x1.1
    system)
    3.In same note(516246) the SAPinst CD is mentioned. How could I get it?
    4.On the Source system I have kernel 640. I guess I have to copy the
    content of this directory to the target system also. But in which phase?

    hi,
    first my question GGG
    -> by which means do you plan to copy? brbackup/brrestore? r3copy? r3load?
    ad 1.
    SAPNet -> Patches -> Add. Components -> SAP Kernel -> 32 BIT (uni oder non-uni depending on your environment) -> SAP Kernel 6.40 32-bit -> Windows Srv -> Oracle -> R3ldctl_6-20000185.SAR (13.07.2006) is the right file (your kernel is 6.40!!!)
    ad 2.
    SAPNet -> Patches -> Add. Components -> SAP Kernel -> 32 BIT (uni oder non-uni depending on your environment) -> SAP Kernel 6.40 32-bit -> Windows Srv -> Oracle -> R3szchk_12-20000185.SAR is the right file (your kernel is 6.40!!!)
    ad 3.
    SAPNet -> SWDC (= Downloads) -> Download -> Inst. and Upgrades -> Entry by applic. group -> SAP Applic. Components -> SAP R/3 Enterprise -> Ent. 47X110 -> Installation -> Windows Server -> Oracle -> CD SAP R3E 4.7x1.10 SR1 SAPINST ORACLE (CD N° 51019679)
    ad 4.
    not really....it depends on the strategy (see my question above)...you first install the database software (oracle), then the central instance using sapinst, afterwards you will install the database instance using sapinst as well; while installing the db instance you have to chose db copy (or homogeneous copy, system copy) as the "database installation method" if you choose to copy the database files or did a backup if you choose to use the export/import method (using standard r3load) you will use the SystemCopy method as well but you will point (later on) to the directory where you (source) db export lies.
    brrestore or copy method:
    =========================
    sapinst will popup at the appropriate point that the db load has to be done and depending on your strategy you have either to restore or copy files...
    by the way: did you already export/backup/copy your source system?
    if any further questions arise feel free to post
    GreetZ, AH

  • Homogeneous System Copy Doubts

    Hi,
    We are planning for the ECC 5.0 Installation on MSCS.
    And we have some doubts over it.
    we need to Install the System in the Cluster Environment of 64 bit OS and Oracle 10g. Where as we have the existing system having OS 32 bit and database Oracle 9i. We need to do a Homogeneous System Copy.
    Do we need to update the Kernel Patch level to the Latest on both the system?
    Is there anyother specific steps to be carried out for this scenario????
    Please Help Me!!!
    Regards
    Kasi

    -> plz check out sapnote n° 960.769 - Windows: Migration fronm 32-bit to 64-bit (x86_64)
    -> ECC 50 -> kernel 6.40, which should be fully supported according to the above mentioned sapnote :-D
    -> plz get installation guides (both: system copy AND installation guide für ECC50/ERP2004) and the relevant sapnotes
    -> export of database on oracle 9i and import into 10g is supported and possible when using r3load mechanism
    GreetZ, AH

  • Homogeneous system copy ECC 6.0 EHP4 dual stack system

    Hello ,
       I have a requirement of homogeneous system for the below Source system
    Source system :
    ECC6.0 EHP1 ABAP+java dual stack system with DB2 AIX
    Required Target system:
    ECC 6.0 EHP1 (same as target system except single stack java not required)
    1 .I was trying to use db specific homogeneous system copy method wiht redirected restore script
    2. Not possible to get downtime on source system hense it's a production system , then i used target system installaion with homogeneous system copy database specific mehthod
    Problem is - it's asking migration export while creating the target system ,  but i don't have any migration export since i have not exported from source system .
    please help us to proceed further.
    Thanks in Advance.

    2. Not possible to get downtime on source system hense it's a production system , then i used target system installaion with homogeneous system copy database specific mehthod
    What did you choose to do in database specific method - DB2 backup/restore ?
    //Backup Restore
    Homegeneous system copy(database specific method)
    Target -
    As I understand, you have started IMPORT using SAPinst for target system installation. During IMPORT, what target system installation (only ABAP or what ?) you chose ?
    //I took ABAP+JAVA
    'Problem is - it's asking migration export while creating the target system , but i don't have any migration export since i have not exported from source system .'
    This is because the source system is ABAP+Java, and now during target system installation, then IMPORT procedure is asking for Java Export dump.
    Thanks

  • Homogeneous System copy -  NW2004s

    I am trying to perform a homogeneous system copy of NW2004s ECC6 system using sapinst.
    Platform info:
    OS - HPUX
    DB - Oracle
    I am using DB specific (oracle) method to restore an offline backup.
    When I run the sapinst to import, I get past preliminary information screens and when I select "Homogeneous System Copy (backup/restore)", I am prompted for the location of LABEL.ASC for the migration.
    The documentation in the guide "Homogeneous System Copy  of NW2004s" is poor and does not address this issue.
    I suspect there is a bug in sapinst.
    Has anyone come across this issue before?
    Thanks,
    Sai

    Steps for homogeneus copy :
    1. Export of source system using sapinst ( R3load )
    2. transfer the file over to target system
    3. Do new installation of he system by using the transfered file as you export file.
    I gues the menu in sapinst would be additional lifecycle task .

  • Portal Homogenous system copy

    Hello Portal Gurus,
    I have just made a system copy of my PRD portal to a sandbox portal using the homogenous system copy menthod. sapinst export and sapinst import.
    Now we have a lot of systems connected to the portal, for eg ECC , BI for reports , APO for reports. Alsowe have trex and content management and KM connected to this portal.
    When i bring up this portal , all the connections point to the old place, which means the sandbox portal now tries to connect to the ECC PRD system , since the EP PRD was originally connected to the ECC PRD system.
    Does one of you have a consolidated list of things that need to be fixed on the portal after a system copy, including procedures on where these things toneed to be fixed ? for eg , how do i removed the ECC connecttion from ECC PRD and point it to ECC TRN ?
    Regards
    Shirish Joshi

    Hi Shirish,
    There are 2 importan things which need to be consider after doing SAP portal system copy.
    1. Change all the system object points the production system.
    2. Change all the jco setting which points to the production system.
    Thanks
    Anil

  • Db2 homogenous system copy using DB specific tools.

    Hi,
    I'm currently doing a homogenous system copy using db specific tools option (DB2). I did an offline backup of the source system using db2 backup database command, then ran SAPinst (NW70SR2) on the source system to go through the export phase, no problem. On the destination system, I ran SAPinst (NW70SR3) to do the import phase and reached a point where SAPinst asked me to restore the database using db2 tools. I running command:
    RESTORE DATABASE <SID> FROM "E:\backup_folder" TAKEN AT 20090617164332 TO "Q:" INTO <SID> NEWLOGPATH "F:\" WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 WITHOUT PROMPTING;
    After running this command I get SQL0902C  A system error (reason code = "") occurred.  Subsequent
    SQL statements cannot be processed.
    sqlcode: -902
    sqlstate: 58005
    Some background information: I'm running this procedure to do a migrate the database from a 32 bit to 64 bit.
    Am I doing something wrong? Do I need to run any other commands or prep on the detination system before running the restore command?

    One other thing you might have wanted to check was the physical memory on the target machine. Does the target have the same amount of memory as the source? If it is much smaller, sometimes there can be issues with starting up the database on the smaller machine. There is an instance level registry setting you can use to reduce the amount of bufferpool memory the database wants to use.
    Another issue I have seen is that you may want to restore a 32-bit backup to a 32-bit instance. You can then upgrade then instance and database to 64-bit.
    EDIT: Sorry, I didn't realize this thread was 2 months old.
    Edited by: Derek Barrett on Aug 18, 2009 4:39 AM

Maybe you are looking for

  • Transaction code for Depricitation Report

    Hi, we have asset accouting with WDV Method & maintaing our books as per F.Y. April to March But, due to foreign investor's investment, we have need to closed our books, twicely, i.e.  IFRS - F.Y.-Jan to Dec / ( US gap ) & Indian gap, FY. April to Ma

  • SQ01, SQ02 & SQ03

    Hi, I am creating user groups (SQ03), infosets (SQ02) and reports (SQ01) for different departments which may access the same infosets but have their own reports. The trouble I'm having is that no matter what user logs in to SQ01 they have access to r

  • Adobe Reader recent files!!! Important!!!

    Does the recent file in the adobe reader le 1.5 to be specific adds up or consumes the space of your memory? if not then its ok. but if it does, how can i CLEAR ALL the RECENT FILE or DELETE THE RECENT FILE IN the adobe reader le 1.5!?!?!?!?!?! thank

  • What makes a file unreadable or readable when trying to move it into the library

    What makes a file unreadable or readable when trying to move it into the library

  • ITunes Video Playlist

    Finally, itunes now has video play list that automatically plays all the Movies on the list (on the computer). How can I get this to work on Apple TV, I have lots of short home videos that I want to play one after the other automatically (like songs