Usage of R3ta during Database Export

Hi everyone,
I have some questions about the usage of R3ta to split some tables during an export/import process.
I'm doing a Unicode migration of a ECC 6.0 system running on Oracle 10g / Win2003 x86_64.
I have done the Table Split Preparation step via sapinst and it finished ok. This step created a subdirectory DATA in my export directory and created numerous .WHR files and a whr.txt file.
After that I started the export process once again via sapinst. I choosed to split the STR files, extracting the 250 largest tables with a package size of 1 GB. I checked the parameter split predefined tables and mentioned the file whr.txt created in the first step as the file containing the tables to be split.
But in the end, the tables in the files whr.txt are still exported sequentially (but are well split into 1GB pieces)
Did I forget something during the process ?
I am using the latest R3ta, R3load, dboraslib.dll, R3szchk and R3ldctl.

Hi Michael,
indeed, I did not tell about the number of R3load processes used. There were 6 of them in parallel.
The last table (and the one that takes most of the time to be exported) should have been handled in parallel but only 1 R3Load was active at the time (6 before)

Similar Messages

  • Unable to retrieve nametab info for logic table BSEG during Database Export

    Hi,
    Our aim is to Migrate to New hardware and do the Database Export of the existing System(Unicode) and Import the same in the new Hardware
    I am doing Database Export on SAP 4.7 SR1,HP-UX ,Oracle 9i(Unicode System) and during Database Export "Post Load Processing phase" got the error as mentioned in SAPCLUST.log
    more SAPCLUST.log
    /sapmnt/BIA/exe/R3load: START OF LOG: 20090216174944
    /sapmnt/BIA/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20
    $ SAP
    /sapmnt/BIA/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 13 2007 16:20:31
    /sapmnt/BIA/exe/R3load -ctf E /nas/biaexp2/DATA/SAPCLUST.STR /nas/biaexp2/DB/DDLORA.T
    PL /SAPinst_DIR/SAPCLUST.TSK ORA -l /SAPinst_DIR/SAPCLUST.log
    /sapmnt/BIA/exe/R3load: job completed
    /sapmnt/BIA/exe/R3load: END OF LOG: 20090216174944
    /sapmnt/BIA/exe/R3load: START OF LOG: 20090216182102
    /sapmnt/BIA/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20
    $ SAP
    /sapmnt/BIA/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 13 2007 16:20:31
    /sapmnt/BIA/exe/R3load -datacodepage 1100 -e /SAPinst_DIR/SAPCLUST.cmd -l /SAPinst_DI
    R/SAPCLUST.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (GSI) INFO: dbname   = "BIA20071101021156                                                                               
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "tinsp041                                                    
    (GSI) INFO: sysname  = "HP-UX"
    (GSI) INFO: nodename = "tinsp041"
    (GSI) INFO: release  = "B.11.11"
    (GSI) INFO: version  = "U"
    (GSI) INFO: machine  = "9000/800"
    (GSI) INFO: instno   = "0020293063"
    (EXP) TABLE: "AABLG"
    (EXP) TABLE: "CDCLS"
    (EXP) TABLE: "CLU4"
    (EXP) TABLE: "CLUTAB"
    (EXP) TABLE: "CVEP1"
    (EXP) TABLE: "CVEP2"
    (EXP) TABLE: "CVER1"
    (EXP) TABLE: "CVER2"
    (EXP) TABLE: "CVER3"
    (EXP) TABLE: "CVER4"
    (EXP) TABLE: "CVER5"
    (EXP) TABLE: "DOKCL"
    (EXP) TABLE: "DSYO1"
    (EXP) TABLE: "DSYO2"
    (EXP) TABLE: "DSYO3"
    (EXP) TABLE: "EDI30C"
    (EXP) TABLE: "EDI40"
    (EXP) TABLE: "EDIDOC"
    (EXP) TABLE: "EPIDXB"
    (EXP) TABLE: "EPIDXC"
    (EXP) TABLE: "GLS2CLUS"
    (EXP) TABLE: "IMPREDOC"
    (EXP) TABLE: "KOCLU"
    (EXP) TABLE: "PCDCLS"
    (EXP) TABLE: "REGUC"
    myCluster (55.16.Exp): 1557: inconsistent field count detected.
    myCluster (55.16.Exp): 1558: nametab says field count (TDESCR) is 305.
    myCluster (55.16.Exp): 1561: alternate nametab says field count (TDESCR) is 304.
    myCluster (55.16.Exp): 1250: unable to retrieve nametab info for logic table BSEG   
    myCluster (55.16.Exp): 8033: unable to retrieve nametab info for logic table BSEG   
    myCluster (55.16.Exp): 2624: failed to convert cluster data of cluster item.
    myCluster: RFBLG      *003**IN07**0001100000**2007*
    myCluster (55.16.Exp): 318: error during conversion of cluster item.
    myCluster (55.16.Exp): 319: affected physical table is RFBLG.
    (CNV) ERROR: data conversion failed.  rc = 2
    (RSCP) WARN: env I18N_NAMETAB_TIMESTAMPS = IGNORE
    (DB) INFO: disconnected from DB
    /sapmnt/BIA/exe/R3load: job finished with 1 error(s)
    /sapmnt/BIA/exe/R3load: END OF LOG: 20090216182145
    /sapmnt/BIA/exe/R3load: START OF LOG: 20090217115935
    /sapmnt/BIA/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20
    $ SAP
    /sapmnt/BIA/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 13 2007 16:20:31
    /sapmnt/BIA/exe/R3load -datacodepage 1100 -e /SAPinst_DIR/SAPCLUST.cmd -l /SAPinst_DI
    R/SAPCLUST.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (GSI) INFO: dbname   = "BIA20071101021156                                                                               
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "tinsp041                                                    
    (GSI) INFO: sysname  = "HP-UX"
    (GSI) INFO: nodename = "tinsp041"
    (GSI) INFO: release  = "B.11.11"
    (GSI) INFO: version  = "U"
    (GSI) INFO: machine  = "9000/800"
    (GSI) INFO: instno   = "0020293063"
    myCluster (55.16.Exp): 1557: inconsistent field count detected.
    myCluster (55.16.Exp): 1558: nametab says field count (TDESCR) is 305.
    myCluster (55.16.Exp): 1561: alternate nametab says field count (TDESCR) is 304.
    myCluster (55.16.Exp): 1250: unable to retrieve nametab info for logic table BSEG   
    myCluster (55.16.Exp): 8033: unable to retrieve nametab info for logic table BSEG   
    myCluster (55.16.Exp): 2624: failed to convert cluster data of cluster item.
    myCluster: RFBLG      *003**IN07**0001100000**2007*
    myCluster (55.16.Exp): 318: error during conversion of cluster item.
    myCluster (55.16.Exp): 319: affected physical table is RFBLG.
    (CNV) ERROR: data conversion failed.  rc = 2
    (RSCP) WARN: env I18N_NAMETAB_TIMESTAMPS = IGNORE
    (DB) INFO: disconnected from DB
    SAPCLUST.l/sapmnt/BIA/exe/R3load: job finished with 1 error(s)
    /sapmnt/BIA/exe/R3load: END OF LOG: 20090217115937
    og (97%)
    The main eror is "unable to retrieve nametab info for logic table BSEG "  
    Your reply to this issue is highly appreciated
    Thanks
    Sunil

    Hello,
    acording to this output:
    /sapmnt/BIA/exe/R3load -datacodepage 1100 -e /SAPinst_DIR/SAPCLUST.cmd -l /SAPinst_DI
    R/SAPCLUST.log -stop_on_error
    you are doing the export with a non-unicode SAP codepage. The codepage has to be 4102/4103 (see note #552464 for details). There is a screen in the sapinst dialogues that allows the change of the codepage. 1100 is the default in some sapinst versions.
    Best Regards,
    Michael

  • Transaction Status during Database Export through DataPump

    Hi,
    I've q question and need clarification. We have 120GB Database ( Version 11GR1 ) which has a single application schema other than standard schemas (Like ststem,sysaux, example etc). The object containg in the application schema will be round about 110~115 GB and the rest size of other standard schemas object. The application users that made transaction through front end J2EE application that hit to application's schema objects.
    We usually expdp that schema. Now my question is when we export the schema when the users are performing transactions what will be the status of that transactions that were made during export process ? what that be reflected in the dump or not? What is that Oracle Actual mechanism for that type of transactions in case of Datapup export.
    Regards,
    Kamran

    Let's say you have 3 tables
    table a
    table b
    table c with partition 1
    table c with partition 2
    Now let's say all of these tables are being exported and while the export is happening, users are adding/dropping rows to these tables/partitions. This is what Data Pump will do if you don't specify flashback_time or flashback_scn;
    Since table a and table b are not partitioned, they will be exported with the scn that is current when the unload of that table is scheduled. So,
    table a gets scheduled to be unloaded when the scn is 12345. The data in the dumpfile for this table will be consistent with 12345. If rows were modified before 12345, the data in the dumpfile will have those rows. If rows were added after 12345, they would not be in the dumpfiles.
    Table b gets scheduled to be unloaded when the scn is 23456. The data in the dumpfile for this table will be consistent with 23456. If rows were modified before 23456, the data in the dumpfile will have those rows. If rows were added after 23456, they would not be in the dumpfiles. If you had ref constraints from table a to table b, you could hit a problem.
    Table c partition 1 gets scheduled at 34567. All of the data in the dumpfile will be consistent with 34567. Just like above
    Here is the exception to the rule!
    Table c partition 2 gets scheduled at 45678. The difference is that partition 1 of this table got scheduled at 34567, so the data in this partition will also be
    consistent with 34567. All partitions of a table will use the same SCN as the first partition that is scheduled.
    If you want a consistent dumpfile, use either
    flashback_time='some date' you can use flashback_time=sysdate if you want to put it in a script and not have to update the date in the script.
    or
    flashback_scn='some_scn'
    Hope this explains what you wanted to know.
    Dean

  • Update Database Statistics during System Export

    hi All,
    I am getting following error on step (Update Database Statistics ) during system export.
    WARNING 2011-06-17 15:13:35
    Execution of the command "E:\usr\sap\PRD\SYS\exe\uc\NTAMD64\
    brconnect.exe -u / -c -o summary -f stats -o SAPSR3 -t all -m +I -s
    P10 -f allsel,collect,method,precision,space,keep -p 4"
    finished with return code 5.
    Output: BR0801I BRCONNECT 7.00 (31)BR0805I Start of BRCONNECT processing:
    cegczbfe.sta 2011-06-17 15.12.02BR0484I BRCONNECT log file:
    G:\oracle\PRD\sapcheck\cegczbfe.sta
    ERROR 2011-06-17 15:13:35
    CJS-30023  Process call 'E:\usr\sap\PRD\SYS\exe\uc\NTAMD64\
    brconnect.exe -u / -c -o summary -f stats -o SAPSR3 -t all -m +I -s P10
    -f allsel,collect,method,precision,space,keep -p 4'
    exits with error code 5. For details see log file(s) brconnect.log.
    there is small part of brconnect.log is:
    BR0204I Percentage done: 27.88%, estimated end time: 15:16
    BR0001I **************____________________________________
    BR0280I BRCONNECT thread 2: time stamp: 2011-06-17 15.13.31
    BR0301E SQL error -20003 in thread 2 at location stats_tab_collect-20, SQL statement:
    'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BEV3/CHCL_STAT"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => TRUE, NO_INVALIDATE => FALSE); END;'
    ORA-20003: Specified bug number (5099019) does not exist
    ORA-06512: at "SYS.DBMS_STATS", line 14830
    ORA-06512: at "SYS.DBMS_STATS", line 14851
    ORA-06512: at line 1
    BR0886E Checking/collecting statistics failed for table SAPSR3./BEV3/CHCL_STAT
    BR0280I BRCONNECT thread 2: time stamp: 2011-06-17 15.13.31
    BR0301E SQL error -20003 in thread 2 at location stats_tab_collect-20, SQL statement:
    'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BEV3/CHCL_STATT"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => TRUE, NO_INVALIDATE => FALSE); END;'
    ORA-20003: Specified bug number (5099019) does not exist
    ORA-06512: at "SYS.DBMS_STATS", line 14830
    ORA-06512: at "SYS.DBMS_STATS", line 14851
    ORA-06512: at line 1
    BR0886E Checking/collecting statistics failed for table SAPSR3./BEV3/CHCL_STATT
    BR0280I BRCONNECT thread 2: time stamp: 2011-06-17 15.13.31
    BR0301E SQL error -20003 in thread 2 at location stats_tab_collect-20, SQL statement:
    'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BEV3/CHCMVWOBJ"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => TRUE, NO_INVALIDATE => FALSE); END;'
    ORA-20003: Specified bug number (5099019) does not exist
    ORA-06512: at "SYS.DBMS_STATS", line 14830
    ORA-06512: at "SYS.DBMS_STATS", line 14851
    ORA-06512: at line 1
    BR0886E Checking/collecting statistics failed for table SAPSR3./BEV3/CHCMVWOBJ
    BR0280I BRCONNECT thread 2: time stamp: 2011-06-17 15.13.31
    BR0301E SQL error -20003 in thread 2 at location stats_tab_collect-20, SQL statement:
    'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BEV3/CHCMVWOBPR"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => TRUE, NO_INVALIDATE => FALSE); END;'
    ORA-20003: Specified bug number (5099019) does not exist
    ORA-06512: at "SYS.DBMS_STATS", line 14830
    BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BEV3/CHCTLVAR"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => TRUE, NO_INVALIDATE => FALSE); END;'
    ORA-20003: Specified bug number (5099019) does not exist
    ORA-06512: at "SYS.DBMS_STATS", line 14830
    ORA-06512: at "SYS.DBMS_STATS", line 14851
    ORA-06512: at line 1
    ORA-06512: at line 1
    BR0886E Checking/collecting statistics failed for table SAPSR3./BEV3/CHCTMSTFUB
    BR0280I BRCONNECT thread 2: time stamp: 2011-06-17 15.13.34
    BR0844E 100 errors occurred in thread 2 - terminating processing of the thread...
    BR0280I BRCONNECT time stamp: 2011-06-17 15.13.34
    BR0848I Thread 2 finished with return code -1
    BR0280I BRCONNECT time stamp: 2011-06-17 15.13.34
    BR0879I Statistics checked for 0 tables
    BR0878I Number of tables selected to collect statistics after check: 0
    BR0880I Statistics collected for 639/0 tables/indexes
    BR0889I Structure validated for 0/749/0 tables/indexes/clusters
    BR1308E Collection of statistics failed for 68292/0 tables/indexes
    BR0806I End of BRCONNECT processing: cegczbfe.sta 2011-06-17 15.13.34
    BR0280I BRCONNECT time stamp: 2011-06-17 15.13.35
    BR0804I BRCONNECT terminated with errors
    how can I resolve this issue?
    Regards,
    majamil

    hi SM,
    I have applied these patches with Opatch which successfully applied.
    is it ok or i had to use the MOpatch for these?
    one more thing for your information , when i execute Delete Harmful Statistics  under Database Statistics in brtools then i got following
    BR0280I BRCONNECT time stamp: 2011-06-30 08.10.53
    BR0818I Number of tables found in DBSTATC for owner SAPSR3: 390
    BR0280I BRCONNECT time stamp: 2011-06-30 08.10.53
    BR0807I Name of database instance: PRD
    BR0808I BRCONNECT action ID: cegfjniv
    BR0809I BRCONNECT function ID: dst
    BR0810I BRCONNECT function: stats
    BR0812I Database objects for processing: HARMFUL
    BR0852I Number of tables to delete statistics: 0
    BR0856I Number of indexes to delete statistics: 0
    BR0863W No tables/indexes found to update/delete statistics or validate structur
    e
    BR0806I End of BRCONNECT processing: cegfjniv.dst 2011-06-30 08.10.53
    BR0280I BRCONNECT time stamp: 2011-06-30 08.10.53
    BR0803I BRCONNECT completed successfully with warnings
    BR0292I Execution of BRCONNECT finished with return code 1
    BR0668I Warnings or errors occurred - you can continue to ignore them or go back
    to repeat the last action
    BR0280I BRTOOLS time stamp: 2011-06-30 08.10.53
    BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
    c
    why i am getting this return code 1?
    Regards,
    Edited by: majamil on Jun 30, 2011 8:20 AM

  • ORA-29540 during full database export

    Hi,
    Anyone encounter this error ORA-29540 during full database export. Have check out the web site for solution. Have check that the init file compatible is set to 8.1.0, the public synonym dba_java is been removed. However after the above remedies, the problem still occured. My database version is 8.1.5. Please let me know if there is other solution to this problem.
    Thank You ...
    regards,
    lbs

    Hi,
    Thanks...Any idea how to check whether the installation for the initjvm.sql is successful. cos I just took over from the previous DBA and he too have no idea...
    Thank You..

  • Error while database export in package SAPDODS_33 (Unicode conversion)

    Hello,
    I am performing Unicode conversion on an upgraded BI 7.0 system. This is running on AIX/DB2.
    When I take database export for conversion, one package fails (SAPDODS_33) with error "The file system is full". In fact, df -k doesn't show that any file system is full.
    I am taking the export to the following location: /db2/BWS/sapdata/EXPORT_DIR
    There are 3 system-managed temporary tablespaces: PSAPTEMP, PSATEMP16 & SYSTOOLSTMPSPACE which were residing in /db2/BWS/saptemp1/NODE0000. This was getting full during the export. Now these temp.tablespaces have been relocated to a new file system of size 15GB.
    But still the package SAPDODS_33 doesn't get exported. Could you please let me know how to solve this issue?
    Thanks a lot!
    Sundar.
    =====================================================================================
    SAPDODS_33.log
    (DB) INFO: connected to DB
    (rscpsumg) Please look also into "SAPDODS_33012.xml".
    (rscpMC) Warn: env I18N_NAMETAB_TIMESTAMPS = IGNORE
    (rscpMC) Warn: UMGCONTAINER has 1 problems.
    (rscpMC) Warn: Global fallback code page = 1160
    (rscpMC) Warn: Common character set is  not  7-bit-ASCII
    (rscpMC) Warn: Collision resolution method is 'fine'
    (rscpMC) Warn: R3trans code pages = Normal
    (rscpMC) Warn: EXPORT TO ... code pages = Normal
    (rscpMC) Warn: Source is 'MDMP'
    (rscpMC) Warn: I18N_NAMETAB_NORM_ALLOW = 0
    (rscpMC) Warn: I18N_NAMETAB_NORM_LOG   = 0
    (rscpMC) Warn: I18N_NAMETAB_ALT_ALLOW  = 0
    (rscpMC) Warn: I18N_NAMETAB_ALT_LOG    = 0
    (rscpMC) Warn: I18N_NAMETAB_OLD_ALLOW  = 0
    (rscpMC) Warn: I18N_NAMETAB_OLD_LOG    = 0
    (GSI) INFO: dbname   = "BWS
    (GSI) INFO: vname    = "DB6                             "
    (GSI) INFO: hostname = "UNKNOWN
    (GSI) INFO: sysname  = "AIX"
    (GSI) INFO: nodename = "itmlartdev01x"
    (GSI) INFO: release  = "3"
    (GSI) INFO: version  = "5"
    (GSI) INFO: machine  = "002417CA4C00"
    (GSI) INFO: instno   = "0020169337"
    (EXP) ERROR: DbSlExeRead failed
      rc = 99, table "/BIC/B0000786000"
      (SQL error -968)
      error message returned by DbSl:
    SQL0968C  The file system is full.  SQLSTATE=57011
    (DB) INFO: disconnected from DB
    /usr/sap/BWS/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/BWS/SYS/exe/run/R3load: END OF LOG: 20071211053119
    p/sapinst/sapinst_instdir/NW04S/LM/COPY/DB6/EXP/CENTRAL/AS-ABAP/EXP #

    Hi Sundar,
    if the problem is due to a high temp space usage. The root cause is typically the
    sort during export. If the table is large, the sort spills to temp.
    You can avoid the sort by doing an unsorted export or tweak the DB2 optimizer to use the primary key to do the sort.
    Before DB2 9, you can reduce the OVERHEAD tablespace parameter to zero. Return this value to its previous value after the successful export. This is a indirect hint to the optimizer that random IOs are cheap. This might not help.
    With DB2 9, this should not happen, because the  DB2_OPT_MAX_TEMP_SIZE=10240 registry variable is set under DB2_WORKLOAD=SAP which limits the temp space usage to 10GB if possible. You can reduce this parameter further if necessary. Another problem could be that the optimizer has chosen the wrong temp space. The optimizer choses the temp space with the largest amount of pages (not size).
    Regards, Jens

  • ORA-39126 during an export of a partition via dbms_datapump

    Hi ,
    i did export using datapump in command line everything went fine but while exporting via dbms_datapump i got this:
    ORA-39126 during an export of a partition via dbms_datapump
    ORA-00920
    'SELECT FROM DUAL WHERE :1' P20060401
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
    ORA-06512: at "SYS.KUPW$WORKER", line 6228
    the procedure is:
    PROCEDURE pr_depura_bitacora
    IS
    l_job_handle NUMBER;
    l_job_state VARCHAR2(30);
    l_partition VARCHAR2(30);
    v_sql VARCHAR2(2000);
    BEGIN
    -- Create a user-named Data Pump job to do a "table:partition-level" export
    -- Local
    select 'P'|| to_char((select min(STP_LOG_DATE) from SAI_AUDITBITACORA),'YYYYMM')||'01'
    into l_partition
    from user_tab_partitions
    where table_name = 'SAI_AUDITBITACORA'
    and rownum = 1;
    l_partition := rtrim (l_partition,' ');
    l_job_handle:= DBMS_DATAPUMP.OPEN
    operation=>'EXPORT',
    job_mode =>'TABLE',
    job_name =>'EXPORT_ORACLENSSA'
    -- Schema filter
    DBMS_DATAPUMP.METADATA_FILTER
    handle => l_job_handle,
    name => 'SCHEMA_EXPR',
    value => 'IN (''ORACLENSSA'')'
    DBMS_OUTPUT.PUT_LINE('Added filter for schema list');
    -- Table filter
    DBMS_DATAPUMP.METADATA_FILTER
    handle => l_job_handle,
    name => 'NAME_EXPR',
    value => '=''SAI_AUDITBITACORA'''
    DBMS_OUTPUT.PUT_LINE('Added filter for table expression');
    -- Partition filter
    DBMS_DATAPUMP.DATA_FILTER
    handle => l_job_handle,
    name => 'PARTITION_EXPR',
    value => l_partition,
    table_name => 'SAI_AUDITBITACORA'
    DBMS_OUTPUT.PUT_LINE('Partition filter for schema list');
    DBMS_DATAPUMP.ADD_FILE
    handle => l_job_handle,
    filename => 'EXP'||l_partition||'.DMP',
    directory => 'EXP_DATA_PUMP',
    filetype => 1
    DBMS_DATAPUMP.ADD_FILE
    handle => l_job_handle,
    filename => 'EXP'||l_partition||'.LOG',
    directory => 'EXP_DATA_PUMP',
    filetype => 3
    DBMS_DATAPUMP.START_JOB
    handle => l_job_handle,
    skip_current => 0
    DBMS_DATAPUMP.WAIT_FOR_JOB
    handle => l_job_handle,
    job_state => l_job_state
    DBMS_OUTPUT.PUT_LINE('Job completed - job state = '||l_job_state);
    DBMS_DATAPUMP.DETACH(handle=>l_job_handle);
    END;
    I've already drop and recreate the directory, granted read, write to public and to user, grant create session, create table, create procedure, exp_full_database to user, restart the database and the listener with the var LD_LIBRARY pointing first to $ORACLE_HOME/lib, and add more space to temporary tablespace.

    The basic problem is:
    Error: ORA 920
    Text: invalid relational operator
    Cause: A search condition was entered with an invalid or missing relational
    operator.
    Action: Include a valid relational operator such as =, !=, ^=, <>, >, <, >=, <=
    , ALL, ANY, [NOT] BETWEEN, EXISTS, [NOT] IN, IS [NOT] NULL, or [NOT]
    LIKE in the condition.
    Obviously this refers to the invalid statement 'SELECT FROM DUAL ...'. I also recommend, you should contact Oracle Support, because it happens inside an Oracle provided package.
    Werner

  • Problems found during the EXPORT to specified keyin table.

    Hi
    I am getting this error in sending iDOC system( We have iDOC-XI-iDOC Scenario.) I tried to reregister the queues but still nothing is passing thru XI.
    Thanks,
    Manish

    Acutally I am getting this DUMP in ST22.
    <i><b>ShrtText                                                                                |
    Problems found during the EXPORT to specified key in table.
    What happened?
    Error in ABAP application program.
    The current ABAP program "CL_XMS_PERSIST================CP" had to be
    terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    The table " " does not contain any data records with the specified key.
    The system called the internal SAP database interface because it
    expected to find such a key.
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "EXPORT_TABLE_UPDATE_CONFLICT" C
    "CL_XMS_PERSIST================CP" or "CL_XMS_PERSIST================CM00W"
    "INSERT_MSG_ALL"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    Information on where terminated
    The termination occurred in the ABAP program "CL_XMS_PERSIST================CP"
    in "INSERT_MSG_ALL".
    The main program was "SAPMSSY1 ".
    The termination occurred in line 302 of the source code of the (Include)
    program "CL_XMS_PERSIST================CM00W"
    of the source code of program "CL_XMS_PERSIST================CM00W" (when
    calling the editor 3020).
    Source Code Extract
    Line
    SourceCde
    272
    IF lv_switch_mode = 2.
    273
    IF export_to_db_optimized = co_true.
    274
    CALL FUNCTION 'SXMB_EXPORT_TO_DB'
    275
    EXPORTING
    276
    iv_kind        = 'P'
    277
    it_prop        = lt_prop
    278
    iv_switch_mode = lv_switch_mode
    279
    iv_msgguid     = clustkey-msgguid
    280
    iv_pid         = clustkey-pid
    281
    iv_vers        = clustkey-vers.
    282
    ELSE.
    283
    EXPORT lt_prop FROM lt_prop
    284
    TO DATABASE sxmsclup2(is) FROM wa_clup ID clustkey.
    285
    ENDIF.
    286
    ELSE.
    287
    IF export_to_db_optimized = co_true.
    288
    CALL FUNCTION 'SXMB_EXPORT_TO_DB'
    289
    EXPORTING
    290
    iv_kind        = 'P'
    291
    it_prop        = lt_prop
    292
    iv_switch_mode = lv_switch_mode
    293
    iv_msgguid     = clustkey-msgguid
    294
    iv_pid         = clustkey-pid
    295
    iv_vers        = clustkey-vers.
    296
    ELSE.
    297
    EXPORT lt_prop FROM lt_prop
    298
    TO DATABASE sxmsclup(is) FROM wa_clup ID clustkey.
    299
    ENDIF.
    300
    ENDIF.
    301
    >>>>>
    IF sy-subrc <> 0.                                         "#EC *
    303
       m_syserr_raise 'PERSIST' 'MSGGUID_EXISTING'
    304
                      clustkey-msgguid clustkey-pid
    305
                      clustkey-vers ''.
    306
    lv_p1 = clustkey-msgguid.
    307
    lv_p2 = clustkey-pid.
    308
    lv_p3 = clustkey-vers.
    309
    310
    RAISE EXCEPTION TYPE cx_xms_syserr_persist
    311
    EXPORTING id = cx_xms_syserr_persist=>co_id_msgvers_existing
    312
    p1 = lv_p1
    313
    p2 = lv_p2
    314
    p3 = lv_p3.
    315
    316
    ENDIF.
    317
    318
    319
    320
    table SXMSPRES (resources)
    321
    table SXMSPXRES (X-resources)
    Internal notes
    The termination occurred in the function "expOutDb" of the SAP
    Basis System, specifically in line 3748 of the module
    "//bas/640_REL/src/krn/runt/abexpo.c#8".
    The internal operation just processed is "cmpr".
    The internal session was started at 20060724051049.
    Internal call code.........: " "
    Key..................: " "
    It is very likely that a constellation similar to the following applies:
    Process 1:                               Process 2:
    UPDATE x.   ==> NOT_FOUND
    UPDATE x. ==> NOT_FOUND
    INSERT x.   ==> ok
    INSERT x. ==> DUPLICATE KEY
    DELETE x.   ==> ok
    UPDATE x. ==> NOT FOUND
    + DUMP
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    [0] DoStack2 ( 0x105a4f7c0, 0x0, 0x2d1b000, 0x100000000, 0x1, 0x0 ), at 0x100471a60
    [1] CTrcStack2 ( 0x105a4f7c0, 0x0, 0x100000000, 0x2d1ac00, 0x2, 0x102d1ada4 ), at 0x100471610
    [2] __1cQrabax_CStackSave6F_v_ ( 0x10303b400, 0x303b400, 0x103874d10, 0x101fcfce8, 0x100000000, 0x
    [3] ab_rabax ( 0x1, 0x2d1ac00, 0x0, 0x100000000, 0x3873800, 0x100000000 ), at 0x100a7fa04
    [4] __1cIexpOutDb6FppCpLLInJEXPO_MODE__i_ ( 0x2, 0xe82, 0xffffffffffffffff, 0x101f97a90, 0x2, 0x38
    [5] __1cTwrite_data_compress6FkpnICONNE_WR_C_i_ ( 0xffffffff7fffb038, 0x1070, 0x1000, 0x10095fa9c,
    [6] __1cMab_connwrite6FIIpHIpFp0pIppnHAB_DATA_ppv_ipFppCpLLInJEXPO_MODE__i_i_ ( 0x0, 0x4, 0x10302a
    [7] __1cLexpo_export6F_v_ ( 0x0, 0x960000, 0x95f800, 0x0, 0x103847980, 0x1 ), at 0x10095aa20
    [8] __1cIab_jexpo6F_v_ ( 0x0, 0x5b52800, 0xd0, 0x100000000, 0x1, 0x0 ), at 0x100952df4
    [9] __1cIab_extri6F_i_ ( 0x100000000, 0x5a37800, 0x2f0, 0x1, 0x0, 0x5e ), at 0x10068ccf8
    </b></i>

  • Error on oracle database export ORA-04045 and ora-00600

    Hi
    I am getting following errors on database export
    EXP-00008: ORACLE error 4045 encountered
    ORA-04045: errors during recompilation/revalidation of CHEALTH1.oracle/gss/util/NLSLocale005
    ORA-00600: internal error code, arguments: [26599], [1], [225], [], [], [], [], []
    EXP-00000: Export terminated unsuccessfully
    we have recently run initxml.sql for XML after upgrading from 9.2.0.1.0 to 9.2.0.4.0
    any suggestions
    kedar

    Yes, you are in the wrong forum, but it sounds like you have your environment variable (or registry entry) for ORA_NLS33 pointing at the wrong directory.
    Steve

  • R3load system copy: Error on database export

    Hello all,
    I am trying to do a system copy via r3load - Export and then import on a WAS 640 oracle Netweaver based system which has both ABAP and JAVA stack. The source and target system are on the same win2000 host. I am getting below errors in the export stage of the system copy. I am following the sap doc: Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP Web AS ABAP 6.40 SR1 .pdf
    As per the doc the below are the main steps
    1) Generate DLL-statements [Page 55] (Call transaction SE38 and run the program SMIGR_CREATE_DDL...Execute the program. The DDL statements are generated and are written to thespecified directory.)
    2) Run SAPinst to export the database [Page 48].
    3) Set up the target system [Page 60].
    I am stuck at 2) with the below errors during the export.
    For step 2, the sapinst asked me to enter
    source <SID>
    Source <DBSID>
    Source schema: I gave this as SAP<SID>
    no of process and alphabetic load.
    Afer this...
    R3ldctlExport.log reports the below errors
    WARNING: no technical settings for table "WFQUE" in SAP data dictionary - defaults used
    WARNING: no technical settings for table "WFSTO" in SAP data dictionary - defaults used
    WARNING: value for DD28S.CONSTANTS not in quotes, view "COVMVSVW"
    WARNING: value for DD28S.CONSTANTS not in quotes, view "DVTOPAY"
    WARNING: value for DD28S.CONSTANTS not in quotes, view "V_LTDX"
    WARNING: value for DD28S.CONSTANTS not in quotes, view "W3TEMPLATE"
    DbSl Trace: ORA-24508 occured when executing SQL statement (parse error offset = 29)
    ERROR: ExeRead for get_loc_table_inf failed
    ORA-24508: Message 24508 not found;  product=RDBMS; facility=ORA
    Error generating DDLINF.TPL
    (UPT) Info: Preparing tables and tablespace entries.
    (UPT) Info: Distributing tables and tablespace entries.
    (WLL) Info:  finished writing location lists
    And sapinst reports several of the below errors...
    ERROR 2007-06-17 17:24:14
    MSC-01015  Process finished with error(s), check log file D:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\EXP/SAPUSER.log
    ERROR 2007-06-17 17:22:44
    MSC-01015  Process finished with error(s), check log file D:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\EXP/SAPDODS.log
    ERROR 2007-06-17 17:22:44
    MSC-01015  Process finished with error(s), check log file D:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\EXP/SAPPOOL.log
    ERROR 2007-06-17 17:22:44
    MSC-01015  Process finished with error(s), check log file D:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\EXP/SAPSDIC.log
    ...etc
    *.TSK files are being created.
    For example, if I describe for one particular package...
    SAPSSEXC.TSK has entries like the below
    D DM45T E ok
    D DM46S E ok
    D DOKCLU E err
    D DOKHL E xeq
    D DOKIL E xeq
    D DSYST E xeq
    D DYNPSOURCE E xeq
    D ENLFDIR E xeq
    D EUDB E xeq
    D EUGUITEXT E xeq
    D EUOBJ E xeq
    D EUOBJEDIT E xeq
    A log file SAPSSEXC.log exists which notes the termination of the r3load export process.
    EXP) TABLE: "DM42S"
    (EXP) TABLE: "DM42T"
    (EXP) TABLE: "DM43T"
    (EXP) TABLE: "DM45L"
    (EXP) TABLE: "DM45T"
    (EXP) TABLE: "DM46S"
    (NT)  Error:  DOKCLU                        : normal NameTab from 20041108162211 younger than alternate NameTab from 20010201171049!
    Syslog: k CQF : DOKCLU                        &20010201171049&2004110rscpgdio 47myCluster (55.13.Exp): 874: received return code 64 from rscpCheckNTTimeStamps.
    myCluster (55.13.Exp): 875: suspicious create timestamp of alternate nametab encountered.
    myCluster (55.13.Exp): 879: create timestamps of nametab: 20041108162211; alternate nametab: 20010201171049.
    myCluster (55.13.Exp): 297: error when retrieving physical nametab for table DOKCLU.
    (CNV) ERROR: code page conversion failed
                 rc = 2
    .--============.|                              RSCP - Error                            || Error from:             Codepage handling (RSCP)                   3 || code:   64  RSCPECALL    Illegal mixture of procedure calls.         || Altername NameTab too old                                            || module: rscpgdio no:   47 line:  2876                    T100: TS007 || TSL01: CQF  p3: DOKCLU                        &20010201171049&2004110||                                                                      |`--
    '(rscpMC) Warn: env I18N_NAMETAB_TIMESTAMPS not set
    (DB) INFO: disconnected from DB
    I:\usr\sap\VIK\SYS\exe\run/R3load.exe: job finished with 1 error(s)
    I:\usr\sap\VIK\SYS\exe\run/R3load.exe: END OF LOG: 20070617185123
    Also some of the other log files for other packages terminate with:" disconnected from db" in the middle of the export.
    What I tried: I tried putting in the latest patch level for r3ldctl, r3load and r3szchk kernel files. It was at kernel patch 43. I upgraded to latest 175 from market place. And restarted sapinst again to start the export again. Again I face the same problem. Sapinst aborts at this stage again. I basically took the whole sapexedb patch 175 and yupdated the kernel but it did not help.
    If any of you out there can lead me in the right direction so that I can get over this stumbling block, would be grateful.
    Many Thanks, Vikram
    [email protected]

    Could anybody  please tell what is the required codepage for oracle?
    Our system has NLS_LANG=AMERICAN_AMERICA.WE8DEC
    Thanks a lot!

  • ERROR EXP-00003 During an Export!

    Hi, I have a question. During an export I am getting an error:
    C:\oracle\ora92\bin>exp radsql@image_try file=c:\radsql.dmp tables=ANAG
    Export: Release 9.2.0.7.0 - Production on Mon Nov 19 01:08:06 2007
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Password:
    Connect to: Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
    With the OLAP and Oracle Data Mining options
    JServer Release 9.2.0.7.0 - Production
    .Exporting Table ANAG
    EXP-00003: no storage definition found for segment (4, 267)
    Any ideas on what to do?
    Thank you!

    Normally this error is due to mismatch in versions of export utility and database. Since you are running this (probably) from the database server (since the versions are the same), I guess you need to contact support as indicated in error documentation.
    EXP-00003: no storage definition found for segment(number, number)
    Cause: Export could not find the storage definitions for a cluster, index, or table.
    Action: Record the accompanying messages and report this as an Export internal error to customer support.
    Besides, upgrade to 9.2.0.8 or higher might be a solution.

  • Error during Database Instance Installation

    Hi,
    We are installing SAP CRM 4.0.Central Instance Installation is over without problem.However during Database Instance Installation we are getting an Error which says :
    "The node E:\sap\DATA does not exist".
    I created this folder manually.Then is gave another error saying
    "Node C:\Program Files\sapinst_instdir\CRM_40SR1_ABAP_UC\DB\CRM\DATA does not exist."
    I created this again.Then it gave another Error saying :
    "Node C:\Program Files\sapinst_instdir\CRM_40SR1_ABAP_UC\DB\4.0\DATA does not exist."
    Why is this error coming up again and again and any solution to this problem?
    Thanks,
    Suparna

    This is happening because installation program is checking the existence of DB Export directories which you specified to the installation program. It has to do with the installation screen where you specify the location of your DB Export CD/DVD during installation of Database instance. Usually what helps is if you copy the DB Export CD's to a directory in your hard disk and specify that as the target for copy. Just check what you are specifying DB Export parameter screen.
    Cheers,
    Sanjeev

  • Performance optimization during database selection.

    hi gurus,
    pls any explain about this...
    Strong knowledge of performance optimization during database selection.
    regards,
    praveen

    Hi Praveen,
    Performance Notes 
    1.Keep the Result Set Small 
    You should aim to keep the result set small. This reduces both the amount of memory used in the database system and the network load when transferring data to the application server. To reduce the size of your result sets, use the WHERE and HAVING clauses.
    Using the WHERE Clause
    Whenever you access a database table, you should use a WHERE clause in the corresponding Open SQL statement. Even if a program containing a SELECT statement with no WHERE clause performs well in tests, it may slow down rapidly in your production system, where the data volume increases daily. You should only dispense with the WHERE clause in exceptional cases where you really need the entire contents of the database table every time the statement is executed.
    When you use the WHERE clause, the database system optimizes the access and only transfers the required data. You should never transfer unwanted data to the application server and then filter it using ABAP statements.
    Using the HAVING Clause
    After selecting the required lines in the WHERE clause, the system then processes the GROUP BY clause, if one exists, and summarizes the database lines selected. The HAVING clause allows you to restrict the grouped lines, and in particular, the aggregate expressions, by applying further conditions.
    Effect
    If you use the WHERE and HAVING clauses correctly:
    •     There are no more physical I/Os in the database than necessary
    •     No unwanted data is stored in the database cache (it could otherwise displace data that is actually required)
    •     The CPU usage of the database host is minimize
    •     The network load is reduced, since only the data that is required by the application is transferred to the application server.
      Minimize the Amount of Data Transferred 
    Data is transferred between the database system and the application server in blocks. Each block is up to 32 KB in size (the precise size depends on your network communication hardware). Administration information is transported in the blocks as well as the data.
    To minimize the network load, you should transfer as few blocks as possible. Open SQL allows you to do this as follows:
    Restrict the Number of Lines
    If you only want to read a certain number of lines in a SELECT statement, use the UP TO <n> ROWS addition in the FROM clause. This tells the database system only to transfer <n> lines back to the application server. This is more efficient than transferring more lines than necessary back to the application server and then discarding them in your ABAP program.
    If you expect your WHERE clause to return a large number of duplicate entries, you can use the DISTINCT addition in the SELECT clause.
    Restrict the Number of Columns
    You should only read the columns from a database table that you actually need in the program. To do this, list the columns in the SELECT clause. Note here that the INTO CORRESPONDING FIELDS addition in the INTO clause is only efficient with large volumes of data, otherwise the runtime required to compare the names is too great. For small amounts of data, use a list of variables in the INTO clause.
    Do not use * to select all columns unless you really need them. However, if you list individual columns, you may have to adjust the program if the structure of the database table is changed in the ABAP Dictionary. If you specify the database table dynamically, you must always read all of its columns.
    Use Aggregate Functions
    If you only want to use data for calculations, it is often more efficient to use the aggregate functions of the SELECT clause than to read the individual entries from the database and perform the calculations in the ABAP program.
    Aggregate functions allow you to find out the number of values and find the sum, average, minimum, and maximum values.
    Following an aggregate expression, only its result is transferred from the database.
    Data Transfer when Changing Table Lines
    When you use the UPDATE statement to change lines in the table, you should use the WHERE clause to specify the relevant lines, and then SET statements to change only the required columns.
    When you use a work area to overwrite table lines, too much data is often transferred. Furthermore, this method requires an extra SELECT statement to fill the work area. Minimize the Number of Data Transfers 
    In every Open SQL statement, data is transferred between the application server and the database system. Furthermore, the database system has to construct or reopen the appropriate administration data for each database access. You can therefore minimize the load on the network and the database system by minimizing the number of times you access the database.
    Multiple Operations Instead of Single Operations
    When you change data using INSERT, UPDATE, and DELETE, use internal tables instead of single entries. If you read data using SELECT, it is worth using multiple operations if you want to process the data more than once, other wise, a simple select loop is more efficient.
    Avoid Repeated Access
    As a rule you should read a given set of data once only in your program, and using a single access. Avoid accessing the same data more than once (for example, SELECT before an UPDATE).
    Avoid Nested SELECT Loops
    A simple SELECT loop is a single database access whose result is passed to the ABAP program line by line. Nested SELECT loops mean that the number of accesses in the inner loop is multiplied by the number of accesses in the outer loop. You should therefore only use nested SELECT loops if the selection in the outer loop contains very few lines.
    However, using combinations of data from different database tables is more the rule than the exception in the relational data model. You can use the following techniques to avoid nested SELECT statements:
    ABAP Dictionary Views
    You can define joins between database tables statically and systemwide as views in the ABAP Dictionary. ABAP Dictionary views can be used by all ABAP programs. One of their advantages is that fields that are common to both tables (join fields) are only transferred once from the database to the application server.
    Views in the ABAP Dictionary are implemented as inner joins. If the inner table contains no lines that correspond to lines in the outer table, no data is transferred. This is not always the desired result. For example, when you read data from a text table, you want to include lines in the selection even if the corresponding text does not exist in the required language. If you want to include all of the data from the outer table, you can program a left outer join in ABAP.
    The links between the tables in the view are created and optimized by the database system. Like database tables, you can buffer views on the application server. The same buffering rules apply to views as to tables. In other words, it is most appropriate for views that you use mostly to read data. This reduces the network load and the amount of physical I/O in the database.
    Joins in the FROM Clause
    You can read data from more than one database table in a single SELECT statement by using inner or left outer joins in the FROM clause.
    The disadvantage of using joins is that redundant data is read from the hierarchically-superior table if there is a 1:N relationship between the outer and inner tables. This can considerably increase the amount of data transferred from the database to the application server. Therefore, when you program a join, you should ensure that the SELECT clause contains a list of only the columns that you really need. Furthermore, joins bypass the table buffer and read directly from the database. For this reason, you should use an ABAP Dictionary view instead of a join if you only want to read the data.
    The runtime of a join statement is heavily dependent on the database optimizer, especially when it contains more than two database tables. However, joins are nearly always quicker than using nested SELECT statements.
    Subqueries in the WHERE and HAVING Clauses
    Another way of accessing more than one database table in the same Open SQL statement is to use subqueries in the WHERE or HAVING clause. The data from a subquery is not transferred to the application server. Instead, it is used to evaluate conditions in the database system. This is a simple and effective way of programming complex database operations.
    Using Internal Tables
    It is also possible to avoid nested SELECT loops by placing the selection from the outer loop in an internal table and then running the inner selection once only using the FOR ALL ENTRIES addition. This technique stems from the time before joins were allowed in the FROM clause. On the other hand, it does prevent redundant data from being transferred from the database.
    Using a Cursor to Read Data
    A further method is to decouple the INTO clause from the SELECT statement by opening a cursor using OPEN CURSOR and reading data line by line using FETCH NEXT CURSOR. You must open a new cursor for each nested loop. In this case, you must ensure yourself that the correct lines are read from the database tables in the correct order. This usually requires a foreign key relationship between the database tables, and that they are sorted by the foreign key. Minimize the Search Overhead 
    You minimize the size of the result set by using the WHERE and HAVING clauses. To increase the efficiency of these clauses, you should formulate them to fit with the database table indexes.
    Database Indexes
    Indexes speed up data selection from the database. They consist of selected fields of a table, of which a copy is then made in sorted order. If you specify the index fields correctly in a condition in the WHERE or HAVING clause, the system only searches part of the index (index range scan).
    The primary index is always created automatically in the R/3 System. It consists of the primary key fields of the database table. This means that for each combination of fields in the index, there is a maximum of one line in the table. This kind of index is also known as UNIQUE.
    If you cannot use the primary index to determine the result set because, for example, none of the primary index fields occur in the WHERE or HAVING clause, the system searches through the entire table (full table scan). For this case, you can create secondary indexes, which can restrict the number of table entries searched to form the result set.
    You specify the fields of secondary indexes using the ABAP Dictionary. You can also determine whether the index is unique or not. However, you should not create secondary indexes to cover all possible combinations of fields.
    Only create one if you select data by fields that are not contained in another index, and the performance is very poor. Furthermore, you should only create secondary indexes for database tables from which you mainly read, since indexes have to be updated each time the database table is changed. As a rule, secondary indexes should not contain more than four fields, and you should not have more than five indexes for a single database table.
    If a table has more than five indexes, you run the risk of the optimizer choosing the wrong one for a particular operation. For this reason, you should avoid indexes with overlapping contents.
    Secondary indexes should contain columns that you use frequently in a selection, and that are as highly selective as possible. The fewer table entries that can be selected by a certain column, the higher that column’s selectivity. Place the most selective fields at the beginning of the index. Your secondary index should be so selective that each index entry corresponds to at most five percent of the table entries. If this is not the case, it is not worth creating the index. You should also avoid creating indexes for fields that are not always filled, where their value is initial for most entries in the table.
    If all of the columns in the SELECT clause are contained in the index, the system does not have to search the actual table data after reading from the index. If you have a SELECT clause with very few columns, you can improve performance dramatically by including these columns in a secondary index.
    Formulating Conditions for Indexes
    You should bear in mind the following when formulating conditions for the WHERE and HAVING clauses so that the system can use a database index and does not have to use a full table scan.
    Check for Equality and Link Using AND
    The database index search is particularly efficient if you check all index fields for equality (= or EQ) and link the expressions using AND.
    Use Positive Conditions
    The database system only supports queries that describe the result in positive terms, for example, EQ or LIKE. It does not support negative expressions like NE or NOT LIKE.
    If possible, avoid using the NOT operator in the WHERE clause, because it is not supported by database indexes; invert the logical expression instead.
    Using OR
    The optimizer usually stops working when an OR expression occurs in the condition. This means that the columns checked using OR are not included in the index search. An exception to this are OR expressions at the outside of conditions. You should try to reformulate conditions that apply OR expressions to columns relevant to the index, for example, into an IN condition.
    Using Part of the Index
    If you construct an index from several columns, the system can still use it even if you only specify a few of the columns in a condition. However, in this case, the sequence of the columns in the index is important. A column can only be used in the index search if all of the columns before it in the index definition have also been specified in the condition.
    Checking for Null Values
    The IS NULL condition can cause problems with indexes. Some database systems do not store null values in the index structure. Consequently, this field cannot be used in the index.
    Avoid Complex Conditions
    Avoid complex conditions, since the statements have to be broken down into their individual components by the database system. 
    Reduce the Database Load 
    Unlike application servers and presentation servers, there is only one database server in your system. You should therefore aim to reduce the database load as much as possible. You can use the following methods:
    Buffer Tables on the Application Server
    You can considerably reduce the time required to access data by buffering it in the application server table buffer. Reading a single entry from table T001 can take between 8 and 600 milliseconds, while reading it from the table buffer takes 0.2 - 1 milliseconds.
    Whether a table can be buffered or not depends its technical attributes in the ABAP Dictionary. There are three buffering types:
    •     Resident buffering (100%) The first time the table is accessed, its entire contents are loaded in the table buffer.
    •     Generic buffering In this case, you need to specify a generic key (some of the key fields) in the technical settings of the table in the ABAP Dictionary. The table contents are then divided into generic areas. When you access data with one of the generic keys, the whole generic area is loaded into the table buffer. Client-specific tables are often buffered generically by client.
    •     Partial buffering (single entry) Only single entries are read from the database and stored in the table buffer.
    When you read from buffered tables, the following happens:
    1.     An ABAP program requests data from a buffered table.
    2.     The ABAP processor interprets the Open SQL statement. If the table is defined as a buffered table in the ABAP Dictionary, the ABAP processor checks in the local buffer on the application server to see if the table (or part of it) has already been buffered.
    3.     If the table has not yet been buffered, the request is passed on to the database. If the data exists in the buffer, it is sent to the program.
    4.     The database server passes the data to the application server, which places it in the table buffer.
    5.     The data is passed to the program.
    When you change a buffered table, the following happens:
    1.     The database table is changed and the buffer on the application server is updated. The database interface logs the update statement in the table DDLOG. If the system has more than one application server, the buffer on the other servers is not updated at once.
    2.     All application servers periodically read the contents of table DDLOG, and delete the corresponding contents from their buffers where necessary. The granularity depends on the buffering type. The table buffers in a distributed system are generally synchronized every 60 seconds (parameter: rsdisp/bufreftime).
    3.     Within this period, users on non-synchronized application servers will read old data. The data is not recognized as obsolete until the next buffer synchronization. The next time it is accessed, it is re-read from the database.
    You should buffer the following types of tables:
    •     Tables that are read very frequently
    •     Tables that are changed very infrequently
    •     Relatively small tables (few lines, few columns, or short columns)
    •     Tables where delayed update is acceptable.
    Once you have buffered a table, take care not to use any Open SQL statements that bypass the buffer.
    The SELECT statement bypasses the buffer when you use any of the following:
    •     The BYPASSING BUFFER addition in the FROM clause
    •     The DISTINCT addition in the SELECT clause
    •     Aggregate expressions in the SELECT clause
    •     Joins in the FROM clause
    •     The IS NULL condition in the WHERE clause
    •     Subqueries in the WHERE clause
    •     The ORDER BY clause
    •     The GROUP BY clause
    •     The FOR UPDATE addition
    Furthermore, all Native SQL statements bypass the buffer.
    Avoid Reading Data Repeatedly
    If you avoid reading the same data repeatedly, you both reduce the number of database accesses and reduce the load on the database. Furthermore, a "dirty read" may occur with database tables other than Oracle. This means that the second time you read data from a database table, it may be different from the data read the first time. To ensure that the data in your program is consistent, you should read it once only and then store it in an internal table.
    Sort Data in Your ABAP Programs
    The ORDER BY clause in the SELECT statement is not necessarily optimized by the database system or executed with the correct index. This can result in increased runtime costs. You should only use ORDER BY if the database sort uses the same index with which the table is read. To find out which index the system uses, use SQL Trace in the ABAP Workbench Performance Trace. If the indexes are not the same, it is more efficient to read the data into an internal table or extract and sort it in the ABAP program using the SORT statement.
    Use Logical Databases
    SAP supplies logical databases for all applications. A logical database is an ABAP program that decouples Open SQL statements from application programs. They are optimized for the best possible database performance. However, it is important that you use the right logical database. The hierarchy of the data you want to read must reflect the structure of the logical database, otherwise, they can have a negative effect on performance. For example, if you want to read data from a table right at the bottom of the hierarchy of the logical database, it has to read at least the key fields of all tables above it in the hierarchy. In this case, it is more efficient to use a SELECT statement.
    Work Processes 
    Work processes execute the individual dialog steps in R/3 applications. The next two sections describe firstly the structure of a work process, and secondly the different types of work process in the R/3 System.
    Structure of a Work Process
    Work processes execute the dialog steps of application programs. They are components of an application server. The following diagram shows the components of a work process:
    Each work process contains two software processors and a database interface.
    Screen Processor
    In R/3 application programming, there is a difference between user interaction and processing logic. From a programming point of view, user interaction is controlled by screens. As well as the actual input mask, a screen also consists of flow logic. The screen flow logic controls a large part of the user interaction. The R/3 Basis system contains a special language for programming screen flow logic. The screen processor executes the screen flow logic. Via the dispatcher, it takes over the responsibility for communication between the work process and the SAPgui, calls modules in the flow logic, and ensures that the field contents are transferred from the screen to the flow logic.
    ABAP Processor
    The actual processing logic of an application program is written in ABAP - SAP’s own programming language. The ABAP processor executes the processing logic of the application program, and communicates with the database interface. The screen processor tells the ABAP processor which module of the screen flow logic should be processed next. The following screen illustrates the interaction between the screen and the ABAP processors when an application program is running.
    Database Interface
    The database interface provides the following services:
    •     Establishing and terminating connections between the work process and the database.
    •     Access to database tables
    •     Access to R/3 Repository objects (ABAP programs, screens and so on)
    •     Access to catalog information (ABAP Dictionary)
    •     Controlling transactions (commit and rollback handling)
    •     Table buffer administration on the application server.
    The following diagram shows the individual components of the database interface:
    The diagram shows that there are two different ways of accessing databases: Open SQL and Native SQL.
    Open SQL statements are a subset of Standard SQL that is fully integrated in ABAP. They allow you to access data irrespective of the database system that the R/3 installation is using. Open SQL consists of the Data Manipulation Language (DML) part of Standard SQL; in other words, it allows you to read (SELECT) and change (INSERT, UPDATE, DELETE) data. The tasks of the Data Definition Language (DDL) and Data Control Language (DCL) parts of Standard SQL are performed in the R/3 System by the ABAP Dictionary and the authorization system. These provide a unified range of functions, irrespective of database, and also contain functions beyond those offered by the various database systems.
    Open SQL also goes beyond Standard SQL to provide statements that, in conjunction with other ABAP constructions, can simplify or speed up database access. It also allows you to buffer certain tables on the application server, saving excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. Buffers are partly stored in the working memory of the current work process, and partly in the shared memory for all work processes on an application server. Where an R/3 System is distributed across more than one application server, the data in the various buffers is synchronized at set intervals by the buffer management. When buffering the database, you must remember that data in the buffer is not always up to date. For this reason, you should only use the buffer for data which does not often change.
    Native SQL is only loosely integrated into ABAP, and allows access to all of the functions contained in the programming interface of the respective database system. Unlike Open SQL statements, Native SQL statements are not checked and converted, but instead are sent directly to the database system. Programs that use Native SQL are specific to the database system for which they were written. R/3 applications contain as little Native SQL as possible. In fact, it is only used in a few Basis components (for example, to create or change table definitions in the ABAP Dictionary).
    The database-dependent layer in the diagram serves to hide the differences between database systems from the rest of the database interface. You choose the appropriate layer when you install the Basis system. Thanks to the standardization of SQL, the differences in the syntax of statements are very slight. However, the semantics and behavior of the statements have not been fully standardized, and the differences in these areas can be greater. When you use Native SQL, the function of the database-dependent layer is minimal.
    Types of Work Process
    Although all work processes contain the components described above, they can still be divided into different types. The type of a work process determines the kind of task for which it is responsible in the application server. It does not specify a particular set of technical attributes. The individual tasks are distributed to the work processes by the dispatcher.
    Before you start your R/3 System, you determine how many work processes it will have, and what their types will be. The dispatcher starts the work processes and only assigns them tasks that correspond to their type. This means that you can distribute work process types to optimize the use of the resources on your application servers.
    The following diagram shows again the structure of an application server, but this time, includes the various possible work process types:
    The various work processes are described briefly below. Other parts of this documentation describe the individual components of the application server and the R/3 System in more detail.
    Dialog Work Process
    Dialog work processes deal with requests from an active user to execute dialog steps.
    Update Work Process
    Update work processes execute database update requests. Update requests are part of an SAP LUW that bundle the database operations resulting from the dialog in a database LUW for processing in the background.
    Background Work Process
    Background work processes process programs that can be executed without user interaction (background jobs).
    Enqueue Work Process
    The enqueue work process administers a lock table in the shared memory area. The lock table contains the logical database locks for the R/3 System and is an important part of the SAP LUW concept. In an R/3 System, you may only have one lock table. You may therefore also only have one application server with enqueue work processes.
    Spool Work Process
    The spool work process passes sequential datasets to a printer or to optical archiving. Each application server may contain several spool work process.
    The services offered by an application server are determined by the types of its work processes. One application server may, of course, have more than one function. For example, it may be both a dialog server and the enqueue server, if it has several dialog work processes and an enqueue work process.
    You can use the system administration functions to switch a work process between dialog and background modes while the system is still running. This allows you, for example, to switch an R/3 System between day and night operation, where you have more dialog than background work processes during the day, and the other way around during the night.
    ABAP Application Server 
    R/3 programs run on application servers. They are an important component of the R/3 System. The following sections describe application servers in more detail.
    Structure of an ABAP Application Server
    The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server.
    The following diagram shows the structure of an application server:
    The individual components are:
    Work Processes
    An application server contains work processes, which are components that can run an application. Work processes are components that are able to execute an application (that is, one dialog step each). Each work process is linked to a memory area containing the context of the application being run. The context contains the current data for the application program. This needs to be available in each dialog step. Further information about the different types of work process is contained later on in this documentation.
    Dispatcher
    Each application server contains a dispatcher. The dispatcher is the link between the work processes and the users logged onto the application server. Its task is to receive requests for dialog steps from the SAP GUI and direct them to a free work process. In the same way, it directs screen output resulting from the dialog step back to the appropriate user.
    Gateway
    Each application server contains a gateway. This is the interface for the R/3 communication protocols (RFC, CPI/C). It can communicate with other application servers in the same R/3 System, with other R/3 Systems, with R/2 Systems, or with non-SAP systems.
    The application server structure as described here aids the performance and scalability of the entire R/3 System. The fixed number of work processes and dispatching of dialog steps leads to optimal memory use, since it means that certain components and the memory areas of a work process are application-independent and reusable. The fact that the individual work processes work independently makes them suitable for a multi-processor architecture. The methods used in the dispatcher to distribute tasks to work processes are discussed more closely in the section Dispatching Dialog Steps.
    Shared Memory
    All of the work processes on an application server use a common main memory area called shared memory to save contexts or to buffer constant data locally.
    The resources that all work processes use (such as programs and table contents) are contained in shared memory. Memory management in the R/3 System ensures that the work processes always address the correct context, that is the data relevant to the current state of the program that is running.  A mapping process projects the required context for a dialog step from shared memory into the address of the relevant work process. This reduces the actual copying to a minimum.
    Local buffering of data in the shared memory of the application server reduces the number of database reads required. This reduces access times for application programs considerably. For optimal use of the buffer, you can concentrate individual applications (financial accounting, logistics, human resources) into separate application server groups.
    Database Connection
    When you start up an R/3 System, each application server registers its work processes with the database layer, and receives a single dedicated channel for each. While the system is running, each work process is a user (client) of the database system (server). You cannot change the work process registration while the system is running. Neither can you reassign a database channel from one work process to another. For this reason, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. This has important consequences for the programming model explained below.
    Dispatching Dialog Steps
    The number of users logged onto an application server is often many times greater than the number of available work processes. Furthermore, it is not restricted by the R/3 system architecture. Furthermore, each user can run several applications at once. The dispatcher has the important task of distributing all dialog steps among the work processes on the application server.
    The following diagram is an example of how this might happen:
           1.      The dispatcher receives the request to execute a dialog step from user 1 and directs it to work process 1, which happens to be free. The work process addresses the context of the application program (in shared memory) and executes the dialog step. It then becomes free again.
           2.      The dispatcher receives the request to execute a dialog step from user 2 and directs it to work process 1, which is now free again. The work process executes the dialog step as in step 1.
           3.      While work process 1 is still working, the dispatcher receives a further request from user 1 and directs it to work process 2, which is free.
           4.      After work processes 1 and 2 have finished processing their dialog steps, the dispatcher receives another request from user 1 and directs it to work process 1, which is free again.
           5.      While work process 1 is still working, the dispatcher receives a further request from user 2 and directs it to work process 2, which is free.
    From this example, we can see that:
    •        A dialog step from a program is assigned to a single work process for execution.
    •        The individual dialog steps of a program can be executed on different work processes, and the program context must be addressed for each new work process.
    •        A work process can execute dialog steps of different programs from different users.
    The example does not show that the dispatcher tries to distribute the requests to the work processes such that the same work process is used as often as possible for the successive dialog steps in an application. This is useful, since it saves the program context having to be addressed each time a dialog step is executed.
    Dispatching and the Programming Model
    The separation of application and presentation layer made it necessary to split up application programs into dialog steps. This, and the fact that dialog steps are dispatched to individual work processes, has had important consequences for the programming model.
    As mentioned above, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. The contents of the database must be consistent at its beginning and end. The beginning and end of a database LUW are defined by a commit command to the database system (database commit). During a database LUW, that is, between two database commits, the database system itself ensures consistency within the database. In other words, it takes over tasks such as locking database entries while they are being edited, or restoring the old data (rollback) if a step terminates in an error.
    A typical SAP application program extends over several screens and the corresponding dialog steps. The user requests database changes on the individual screens that should lead to the database being consistent once the screens have all been processed. However, the individual dialog steps run on different work processes, and a single work process can process dialog steps from other applications. It is clear that two or more independent applications whose dialog steps happen to be processed on the same work process cannot be allowed to work with the same database LUW.
    Consequently, a work process must open a separate database LUW for each dialog step. The work process sends a commit command (database commit) to the database at the end of each dialog step in which it makes database changes. These commit commands are called implicit database commits, since they are not explicitly written into the application program.
    These implicit database commits mean that a database LUW can be kept open for a maximum of one dialog step. This leads to a considerable reduction in database load, serialization, and deadlocks, and enables a large number of users to use the same system.
    However, the question now arises of how this method (1 dialog step = 1 database LUW) can be reconciled with the demand to make commits and rollbacks dependent on the logical flow of the application program instead of the technical distribution of dialog steps. Database update requests that depend on one another form logical units in the program that extend over more than one dialog step. The database changes associated with these logical units must be executed together and must also be able to be undone together.
    The SAP programming model contains a series of bundling techniques that allow you to group database updates together in logical units. The section of an R/3 application program that bundles a set of logically-associated database operations is called an SAP LUW. Unlike a database LUW, a SAP LUW includes all of the dialog steps in a logical unit, including the database update.
    Happy Reading...
    shibu

  • How can I include Java objects in a 'Database Export'?

    I am running a 'Database Export' to produce a DDL script for all objects in the schema.
    I have some objects of type JAVA SOURCE and JAVA CLASS in my schema, but they are not included in the DDL script. Is there a way to get them included?
    Version is 3.0.04.
    Thanks,
    Mike

    Any suggestions on this?
    Thanks,
    Mike

  • Database export stops with the following warnings.

    Hello,
    I am doing a Database Export/Import Activity. My DB is MS SQL server 2000 and SAP R/3 (4.6C SR2 , 4.6D kernel).
    When i try to do a DB export with option split STR and EXT files, my export stops abruptly without giving any erorrs but with a whole list of warnings.
    My splitting procedure is using SPLITSTR.PL perl script. I am not using the latest java based split.
    For your reference i am pasting the whole DBEXPORT.log file.
    (sorry its bit large,,, i hope you dont mind ) )
    INFO 2008-03-29 14:36:21 CommandFileController SyFileVersionSave:736
        Saving original content of file
        C:\Users\prdadm\Install\DBEXPORT.R3S ...
    INFO 2008-03-29 14:36:21 CommandFileController SyFileCopy:676
        Copying source file C:\Users\prdadm\Install\DBEXPORT.R3S to
        target file C:\Users\prdadm\Install\DBEXPORT.R3S.1 ...
    INFO 2008-03-29 14:36:21 CommandFileController SyPermissionSet:2207
        Changing permission for file C:\Users\prdadm\Install\DBEXPORT.R3S
        from 777 to 666.
    INFO 2008-03-29 14:36:21 Main
        Preparation successfully completed.
    INFO 2008-03-29 14:36:23 DBEXPORTINSTANCE_NT_IND DefValForKey_OS:0
        R3Setup found the share 'SAPLOC' on drive E:.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:37:17 DBEXPSERVER_NT_IND InternalColdKeyCheck:0
        The CD CDEXPORT1 will not be copied.
    INFO 2008-03-29 14:37:36 DBEXPORTINSTANCE_NT_IND CheckValueForKey:0
        The installation phase is starting now. Please look in the log
        file for further information about current actions.
    INFO 2008-03-29 14:37:36
        Requesting Export Details
    INFO 2008-03-29 14:37:36
        Requesting Export Details
    INFO 2008-03-29 14:37:36 DBEXPCOMMONDBENV_NT_MSS SyCoprocessCreate:931
        Creating coprocess osql.exe ...
    INFO 2008-03-29 14:37:36 DBEXPCOMMONDBENV_NT_MSS SyCoprocessExecute:171
        The process osql.exe puts out:
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
        Version String read from MS SQL Server: Microsoft SQL Server
        2000 - 8.00.2039 (Intel X86)       May  3 2005 23:18:38       Copyright
        (c) 1988-2003 Microsoft Corporation      Enterprise Edition on
        Windows NT 5.2 (Build 3790: Service Pack 2)
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
        Major Version read from MS SQL Server: 800
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
        Minor Version read from MS SQL Server: 2039
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS SyCoprocessCreate:931
        Creating coprocess osql.exe ...
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS SyCoprocessExecute:171
        The process osql.exe puts out:
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS InternalInstallationDo:0
        You have a correctly configured MS SQL Server with charset cp850
        and sortorder bin_cp850!
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS InternalInstallationDo:0
    ooo MSGERR Wrong type of Parameter: area:74, id:1, typeofParam:4, char:d
    ooo MSGERR Dump of parameter with valid type:
    ooo MSGWAR MsgAreaName:SY_AREA_RI_MSGL, MsgIdName:RI_MSGL_MIN_MAJORVERSION
    ooo MSGERR --- SYLOGDATA:ParaNr: 1, Typ:4
    ooo MSGERR --- SYLOGDATA:ParaNr: 2, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 3, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 4, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 5, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 6, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 7, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 8, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 9, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr:10, Typ:1, long=0
    ooo MSGERR Wrong type of Parameter: area:74, id:1, typeofParam:4, char:d
    ooo MSGERR Dump of parameter with valid type:
    ooo MSGWAR MsgAreaName:SY_AREA_RI_MSGL, MsgIdName:RI_MSGL_MIN_MAJORVERSION
    ooo MSGERR --- SYLOGDATA:ParaNr: 1, Typ:4
    ooo MSGERR --- SYLOGDATA:ParaNr: 2, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 3, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 4, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 5, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 6, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 7, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 8, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 9, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr:10, Typ:1, long=0    Your actual major version of MS SQL Server is
    INFO 2008-03-29 14:37:37
        Requesting Export-Specific Parameters
    INFO 2008-03-29 14:37:37
        Testing the Database Connect
    INFO 2008-03-29 14:37:37 DBDBSLTESTCONNECT_NT_IND InternalInstallationDo:0
        See logfile dev_dbsl for further information.
    INFO 2008-03-29 14:37:37 DBEXPSERVER_NT_IND InternalWarmKeyCheck:0
        The CD CDEXPORT1 will not be copied.
    INFO 2008-03-29 14:37:37
        Requesting Information on CD-ROMs
    INFO 2008-03-29 14:37:37
        Creating the Export Directories
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB. If it does not
        exist creating it with user NULL_POINTER, group NULL_POINTER and
        permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\ORA. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\ORA from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\INF. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\INF from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\ADA. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\ADA from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\MSS. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\MSS from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\DB2. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\DB2 from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\DB4. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\DB4 from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\DB6. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\DB6 from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DATA. If it does not
        exist creating it with user NULL_POINTER, group NULL_POINTER and
        permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DATA from 777 to 7.
    INFO 2008-03-29 14:37:37
        Creating the R3load Control Files
    INFO 2008-03-29 14:37:37 R3LDCTL_NT_IND R3ldctlDo:0
        C:\Users\prdadm\Install\R3LDCTL.EXE -p C:\Users\prdadm\Install
    INFO 2008-03-29 14:37:37 R3LDCTL_NT_IND SyCoprocessCreate:931
        Creating coprocess C:\Users\prdadm\Install\R3LDCTL.EXE ...
    INFO 2008-03-29 14:37:38 R3LDCTL_NT_IND R3ldctlDo:0
        WARNING: no technical settings for table "A055" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "A056" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "A064" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "A065" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "AABLG" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "AANK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "AANL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMON" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMONA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMONO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMONQ" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANAR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANEV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANGA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLW" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "APQD" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "APQI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ATAB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "B015" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "B060" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BGPROT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BKORA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BKORR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BPHIER" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BSIW" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCEVTJOB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCJSTAT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCOPTIONS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCSED" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCSEV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCUEV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BUXPRA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BVOR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATCU" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATDB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CBPL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CCCFINI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0BAS4VI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0BAS5VI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0MC5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0T200TAB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0T210TAB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0TBSH001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CDCLS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE1S001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE2S001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE3S001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE4S_CP_FLAG" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "CF003" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CF005" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CFIS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CHGRP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKHT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKKS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKKT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKPP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKPS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKPT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CLRK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CLU4" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CNTLREM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "COKAA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "COOI_PI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "COSPP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRHH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRID" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRS_BLOCKS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRVP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CSLT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CSSK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVEP1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVEP2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER4" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DD02ALL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DEBI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DELM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DLIX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKALTLANG" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKCL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKID" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKSH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKSI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOSSH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOSSI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYCR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYLI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYLT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYSX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DVERS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DVPOOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DVPOOLTEXT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "E070N" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EANQ" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EBSEG" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EBUB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDFIL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDI30C" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDI40" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDIDOC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDIE5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDMAP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EIPA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EKAN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EKPB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EKUB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EPIDXB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EPIDXC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EREF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EREN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ERET" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST07" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST0B" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST0D" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST0F" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EWUCUSA2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EWUCUSAK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FEBKEY" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FINPL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FINS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FINV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FLAPP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FLEMP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FMCFSI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FMCOPI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FMGEBER" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FOH01" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FREF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GCLIENTS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLOO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLOO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLPO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLPO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLPO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLS2CLUS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLT0" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTPC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GSBLCA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GWFEODE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HLPNA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRARCENQ" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRMS_BIW_PPDELTA" in
        SAP data dictionary - defaults used
        WARNING: no technical settings for table "HRPMPROT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRPMSIM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRPY_RGDIR_TEMP" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "IMPREDOC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "INDX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "INETX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "INHB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "IXDIT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "IXTYP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "IXTYT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "JVT1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "J_1AWITNR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "J_1BCBTAXPROC" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "J_1BITEMTYPES" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "K002" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KALK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KAPE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KAPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KBPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KCPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KDPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KEPOOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KGPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNAS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNB5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNC1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNC3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNMTK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNOB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVD" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOCLU" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KONAIND" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOND" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KONR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTD001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE002" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE003" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE004" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE005" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTG002" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTG003" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KRED" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LDAN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LDKO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFAS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFB5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFC1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFC3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LISA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LISPLF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MASE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MAT1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBAN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBMP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBPR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBRK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCEKS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCVSRFP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCY1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEIK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEIN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEKK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEOR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MHNDO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MHNKA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MKLK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MKUB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MLIB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MODSAP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MOFF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MPRP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSAK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSEGO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSET" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSOA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSPOOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSTA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_ADMC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_ADRC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_ADRP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_AKTE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_CF01" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_CKKA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_CLFN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_DARL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_DGMI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_HORD" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IBEW" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IFLM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IIMA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IRLM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_J1BA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_J1IA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_J1IB" in SAP data
        dictionary - defaults used

    Hello,
    The version of perl is correct.
    Anayways i have solved the problem!
    there was problem with the DBEXPORT.R3S file. i referred a SAP note for the same.(Installation of 4.6c on windows). In this check the section for post installation activity.
    I hope this can be a input for other experts who may face such problem!!!
    Regards,
    Shridhar!!!!

Maybe you are looking for