DB2 zOS database export tips & tricks

Does anyone have compiled or know of the existence of a list of tips, pointers, tricks, etc. for the process of exporting a DB2 zOS database (for use in a later import into a DB2 LUW system)?
Most appreciated any help you may provide.
Regards,
Julio Porras.

I just uploaded a document with the steps that I followed for the DB2 z/OS database export.
Mind I did this back in October, 2008 (see my original post date).
You can find the document here:
http://scn.sap.com/docs/DOC-45835
I hope you find it helpful.
Regards,
JP.

Similar Messages

  • Database Export with DB2 Version 9.5

    Folks,
    Has anybody ran a Database Export with ECC 6.0 or Solution Manager 7.0 etc  ( AIX ) and DB2 Version 9.5 ?
    When we have run it, it runs successfully ( so it says ) in seconds but obviously produces no dump file. My gut feel is that the Installation Master ( SR3 ) is prob okay it is some specific kernel components.
    If anybody has any ideas it would be much appreciated.
    Regards Russell

    We got to the bottom of the problem it was associated with Virtual Hostnames. It wasn't picking up the Virtual Hostname and therefore didn't think there was anything to do. With the correct SAPINST_USE_HOSTNAME it connects in correctly and runs through.
    Regards Russell

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

  • 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

  • Database Export exporting data does not export time of date columns

    Hi,
    I'm trying to export some data using Database Export and for the date columns the resulting scripts truncates dates showing only the date part not the time one. If export from a query result the resulting script include all the information (date and time).
    Does anyone has an idea on how to export all the date information using database export.
    thanks

    Yep, as Jim said, under Tools / Preferences / Database / NLS Parameters I changed Date Format to DD-MON-YYYY HH24:MI:SS
    Seems to have done the trick. What's the significance of DD-MON-RR versus DD-MON-YY?

  • Database export problem

    Hello DB2 guru's,
    we are performing a AIX 4.3 DB2 V7 database extract using R3LOAD. (DBEXPORT.R3S)
    The database size is 350GB. (with a table of 50GB, and 8x 20GB)
    The challange is that we only have 3 days to perform the export.
    This is already the 3th try and still nog luck.
    13 of 15 processes finish succesfully but he 2 left keep on running it seems.
    Allthough the TEMPSPACE tablespaces keep growing, so I can imagine it is exporting the 50GB table.
    Is there a way to determine which table it is processing, and maybe to have an indication of completion time ?
    If found a java tool : MIGMON but have no experience in that.
    All help or comments are welcome...
    Thank you for your time
    Hans

    Hi guys,
    thank you for your feedback.
    We get to 83% in the export process. 13 of the 15 processes completed.
    If I then check the TEMP tablespaces I see them growing to 50 a 60GB.
    And then they are emptied and I loose connection and can start over again.
    My assumption is that the (1X50GB, 10X20GB tables are the cause)
    What can you advice specifically to solve the problem with those big tables.
    Can anyone give an example of the MIGMON / SPLIT tool ? Or another advice ?
    very much appreciated !!!
    thanks
    Hans

  • OracleWorld broken links - Tips,Tricks,Techniques

    I get a broken-link error when attempting to retrieve either of these files:
    OracleWorld 2003: Top 10 Most Popular Sessions
    4. Oracle Database: Tips, Tricks, and Techniques
    40118_sgeorge_Tips and tricks for DBA V2.ppt
    40118 - sgeorge Tips and tricks whitepaper 2003.doc

    Hi Ronald,
    Apologies for the delay in responding to you.
    The Documentation Feedback forum is for issues relating only to the OTN Documentation pages at:
    http://otn.oracle.com/documentation/index.html
    Perhaps you could try the Member Feedback forum instead at: Community Feedback (No Product Questions)
    Regards,
    Les

  • Did you know-? Animation Tips & Tricks

    Did you  know that you can animate any object you create in Project ROME – and  that it's easy to do too? Just follow these quick steps (and be sure to  have your timeline showing – View > Show Timeline):
    1.Select the object you want to animate
    2.Click on the stop watch in the upper left of the timeline
    3.Drag the top arrow within the timeline to indicate how long you want the animation to talk place (e.g., 10 seconds)
    4.Animate!
    You can drag the selected object to create an animation path, change the object's color or even transparency. Check out this latest video on more about creating animation: http://bit.ly/9m4ug4. Let us know how this works for you and if you have any suggestions or questions along the way!
    Thanks again for your feedback!
    Sarah
    Sarah
    Forum Moderator

    Hi Romans,
    Did you all get a chance to experiment  with the tips & tricks we posted yesterday? If you did, what did you  think? Did you discover anything interesting or find something you  didn't like? What tips & trick can you share? Please keep providing  us with your feedback. It's great to hear everyone's concerns, praises  and suggestions, and it's immensely valuable! 
    And for those of you who haven't experimented yet….get rolling and try it out now!
    Thanks,
    Sarah
    Sarah
    Forum Moderator

  • 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

  • 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

  • Overclocking the i7 in Tips & Tricks

    Harm Millaard, the hardware guru from the PrPro forum has just posted a LINK to his overclocking the i7 guide, in the Tips & Tricks sub-forum.
    If you're considering doing this, you might want to give it a read.
    Good luck,
    Hunt

    My i7 rig is with a socket 1156 board, an Asus P7P55D mobo, and an 860 CPU. I know the Corsair DDR3 memory @ its stock 1.65v simply doesn't run at 1600mhz like it says on its box - 1333mhz seems to be its stability wall.
    I upgraded my Q6600 and Asus P5B deluxe rig because so many people said to never consider overclocking on an editing rig. Was that over-cautious advice?

  • Elgato EyeTV Hybrid tips & tricks

    I didnt know where else to put this so im posting this here. I'm looking for any tips & tricks or whatever you want to call it with the Elgato EyeTV Hybrid for Mac. Reason this being is because im using an Xbox 360 with this and i feel my experience could be much better, with quality and responce time.
    I know all the Converting/Encoding whichever is all being done by the iMac so i suppose id have to live with the response time but is there anything i can do to the settings for quality? Anything you want to suggest please do, id be happy to try it and give feedback.
    Thanks

    There is no interface with the Eyetv to the Dish receiver that would permit channels to return. Your Eyetv is only as good as the channel the reciever is set to. In other words, your Eyetv will retrieve any channels that are not regulated by a reciever to interpolate them, ie: "Over the air" and/or a "straight cable connection" without a set top box. Whether it be a Dish network or a local cable company, any circumstance of a set top box will not be compatible with Eyetv for the lack of it's abilty to change the channels on that box. The only circumstance I have ever seen is when a viewing/recording device has an IR blaster that transmits the channel selection to that set top box and changes the channels much the same as you would with a remote. That being said, there is still the issue of that particular device knowing the IR codes to your particular box.
    Your Eyetv is good for "Over the Air" and/or a straight Cable coax connection only. Sorry.
    Mac Mini   Mac OS X (10.4.8)  
    Mac Mini   Mac OS X (10.4.8)  

  • Business Workplace - "Tips & Tricks"

    I've just noticed a very, very cool feature in Business Workplace. When you go to your Inbox, and you hover over "Tips & Tricks," something appears, a bit like a Windows tooltip, except far more useful and far less annoying.
    Does anyone know how I can get such a feature into an ABAP programme I write myself? It looks like it should be easy - probably something like set a property on an object and watch it happen. But I can't work it out, I think I must be looking in the wrong place...

    Hi Robert,
    The Preview Pane utilizes HTML controls. A new item for the "Tips & Tricks" is selected every time you click on a different workitem or deadline message. Function module SIN_WI_PREVIEW_TIPS gets the tip and builds the HTML.
    Cheers,
    Ramki Maley.

  • Tips & Tricks to manage time to contribute in SCN

    Hi SCN Mates,
                 The question of managing time to contribute in SCN and be in the top list of contributors is always a challenge, I wonder how other guys are managing it along with project work and personal life.
    Through this thread I would like to ask all top contributors to share few tips on how do you manage your time to contribute in SCN and be in top?
    I know with dedication and knowledge, at same time everyone will have their office work at priority after family/personal time.
    Also contributing for an hour daily is also not possible because you never know whether you get ideas within an hour ;-).
    Anyway, share your tips & tricks...
    Thanks,
    Umashanakr

    People who become Top Contributors fall into two main categories
    Category 1 - There is no need to know anything about SAP at all, but since they are SAP professionals at the end of the day, they know enough to get points. They spend all their time on SCN, Must follow every single member of HCL. Must go to each blog and like it ,and write "thank you". They  read every question posted on the forum, whether they know anything about it or not, and reply to it. They have excellent google skills, so they google the answer and post links in reply to every question. They could vary their approach by becoming active in Coffee Corner as well. Soon they will have million points and be a top contributor.
    Unfortunately, this method is not for those who have family/work/other commitments which are more important.
    Category 2 - These people have built up a tremendous amount of knowledge after years of practising in the business. They are genuine experts. They do not come into SCN with the sheer intent of accumulating points. However, when they do come in, and see fit to respond to a post, it is invariably the correct answer or  very helpful, that they get marked accordingly. These people post thoughtful blogs or comments or documents or discussions, which are useful and appreciated by the community and they get marked accordingly. Sooner or later, without really trying, but by simply practising their profession, these people accumulate enough points to become Top Contributors.
    These people do not have a set strategy intended to accumulate points, but they do have a set strategy of being good and knowledgeable at their job. They manage their work/life balance in a way that suits them to achive this goal.
    I am afraid there is no fixed way to achieve lofty goals with little or no effort.
    There is a 3rd category, who are pretty decent in their knowledge and sporadically answer questions when they feel like, and who randomly get points for their responses, and they will never become top contributors, however, they are not too worried about it, and they do get to spend time with their families/other interests. This is a technicality that need not detain us.
    YMMV
    Hope this helps.

  • Is this a BUG???  Database Export not including Foreign Key Constraints

    I'm using SQL Developer 1.5.4 with both the 59.47 and 59.59 patches installed. I want to do a database export from a 10g XE schema, and include all objects in the resulting DDL. So, I select ALL the checkboxes in the export wizard and when I get to Step 3 to specify objects, I don't see any of my constraints in the listbox... no foreign key constraints, no primary key constraints, no check constraints, nothing. Is this a bug, or is there a workaround, or what could I possibly be doing wrong? We want to be able to use the database export feature to easily transport and track modifications to our entire schema using source control compare.
    Any help or alternate suggestions would be apprieciated.
    Thanks,
    Matt

    Thanks skutz, we just figured that out this morning. Also, it should be noted that you need to be logged in as the owner of the schema otherwise selecting nothing in the filter will give you nothing, but selecting items in the filter will give you those items even if you're not connected as the schema owner. I wonder if that is the detail of the Bug 8679318.
    Edited by: mattsnyder on Jul 14, 2009 9:24 AM

Maybe you are looking for