Performance benefits from database export import

Hi guru,
I have SAP R3 47.X110 WIN/SQL2005.
I want to improve performance by a sort of database reorganization.
I read this note  Note 159316 - Reorganizing tables on SQL Server SQL 2000/2005
but , there the method descrived is not much quick to do.
The question is : there is lot performance's benefits from make an export of my instance then re-import , according system copy procedure?
Or there is another quick way to reorganize database?
Thank you very much for answer.
Antonio.

You want to do an export/import or a reorganization to get more performance. The question is: does it make sense? The given Microsoft article and the mentioned notes describe pretty well, in which cases it makes sense and in which not.
I wouldn´t start with the last step (reorganization) but I would more try to find out, where the real problems are. Checking the I/O system throughput using performance monitor (perfmon.exe) on Windows, checking long running statements using ST05 and finding out if you have a real index fragmentation using the given DBCC procedures.
If you come to the conclusion then, that a reorganization makes sense, then I would do it.
And as stated in the SAP note, if it would become faster after such a task, the underlying I/O subsystem is not fast enough to serve all the requests.
There´s no general statement as "if you do reorganization using method A or method B it will be faster" because the reasons for a slow performance can vary.
Markus

Similar Messages

  • Migrate Database- Export/Import

    Hi,
    I need to migrate an Oracle database 9i from Sun Solaris to Linux. The final target database version would be 11g.
    Since this is a 9i database, I see that we have only option of export and database. We have around 15 schemas.
    I have some queries related to it.
    1. If I perform a export with full=y rows=y, Does it export Sys, System Schema objects also?
    2. Can we perform export in Oracle 9i and use datapump import on targert 11g?
    3. What is the ebst approach - a) to perform schema by schema export or b) to perform a full database export with exp / file=xxx.dmp log=xxxx.log full=y?
    Since there is a database version different I dont want to touch sys, system schema objects.
    Appreciate your thoughts.
    Regards
    Cherrish Vaidiyan

    Hi,
    Let me try to answer some of these questions you queried for:
    1. If I perform a export with full=y rows=y, Does it export Sys, System Schema objects also?Export won't export sys objects. For example, there are tables in sys, like obj$ that contain information for other metadata objects, like scott.emp, etc. This is not exported becuase when scott.emp is exported, the data from obj$ is essentially exported that way. When the dumpfile is imported and scott.emp is recreated, the data in sys.obj$ will be restored through the create table statement. As far as the SYSTEM schema is concerned, some objects are exported and some are not. There are tables in system that contain information about queues, jobs, etc. These will probably not make any sense on the target system so those types of tables are excluded from the export job. Other objects make sense to export/import so those are done. This is all figured out in the internals of export/import. Thre are other schemas that are not exproted. Some that I can think of are DMSYS, ORDSYS, etc. This would be for the same reason as SYS.
    2. Can we perform export in Oracle 9i and use datapump import on targert 11g?No, the dumpfiles are formatted differently. If you use exp, then you must use imp. If you use expdp, then you must use impdp. You can do exp on 9i and imp on 11g with the dumfile that was created on 9i.
    3. What is the ebst approach - a) to perform schema by schema export or b) to perform a full database export with exp / file=xxx.dmp log=xxxx.log full=y?This is case by case decision. It depends on what you want. If you want the complete database moved, then I would personally think that a full=y is what you would want to do. If you just did schema exports, then you would never export the tablespaces. This would mean that you would have to create the tablespaces on the source system before you ran imp. There are other objects that are not exported when a schema level export is performed that are exproted when a full is performed. This information can be seen in the utilities guide. Look to see what is exported when in user/schema mode vs full/database mode.
    Since there is a database version different I dont want to touch sys, system schema objects.This is all done for you with the internal workings of exp/imp.
    Dean
    Edited by: Dean Gagne on Jul 29, 2009 8:38 AM

  • Full Database Export/Import

    I was attempting to export a full database from one server (DB files on the N: drive) and import it into a freshly created new database with the same instance name on a new server (DB files on the D: drive).
    I was told to:
    1) Export the full database as sys using full=y
    2) Pre-create all of the tablespaces on the target database that do not exist on the target database
    3) Import the full database as sys using full=y
    =========================================================
    Here are the steps I had to follow:
    1) Export the full database as sys using full=y
    2) Pre-create all of the tablespaces on the target database
    3) Import the full database as sys using full=y - Result: over 1900 invalid objects and thousands of errors
    4) Run Utlrp.sql - Result: 8 to 10 invalid objects
    5) Manually attempt to compile or rebuild objects. Several grants were required to get most of these to work. - Result: After quite a bit of hand crafting, two objects are still invalid.
    6) After spending almost two hours in a Collaborative Conference with an analyst who is working very hard to sold this, there are still two objects that are invalid.
    Note: From my perspective this is not a straight forward process
    =========================================================
    Questions:
    1) Has anyone successfully moved a database as described without all of these annoying steps?
    2) Is there a document that details the full database export/import?
    Thanks, RJZ

    Hello RJZ,
    There is not sufficient information to reply accurately to your queries,
    1. Could you post the error message that you're getting when you compile these two programs? Do they compile okay on the old server?
    2. What was the reason you choose exp and imp, to move your db to the new server and different disk? Were you migrating to a different version, or was it because of the db-reorg? It would have been possible to simple copy the db-files to the new location, and then rename the datafiles in mount-state. It would be more simpler I believe unless as stated above
    Did you check the import logs? While importing were there any errors? Actually it should have been pretty straight forward (no reason why you need documentation for exp / imp). Grants should have automatically come, unless you have select grants=n option
    I think because of the changes you have done for step-5, you might have changed some stuff somewhere. Please post the error message, and tell us if you have migrated the db to a higher version
    Regards
    Sudhanshu

  • Recovering the rules app from one export/import (HOWTO?)

    Hello Aravind:
    I'm having an issue with my rules app.
    Our customer has a requirement. They want to export the production environment to the test environment, to have the data updated, and be able to reproduce recent issues to create a report.
    The problem is, when we import the schema into the test environment, we are not able to use the rules app again, the results views is no longer valid because the RLM$SESSRSLTTTAB tables used to create this views not exists. So we have to manually delete all related objects to the rules app, an re-run the scripts to create all again.
    The question is, if there is any procedure to re-create this internal objects, or a way to generate the export/import to avoid this.
    Thnks in advance Aravind.
    Alex.

    Alex,
    Rules Manager applications can be exported and imported to a different database with a restriction that the destination schema is same as the schema from which the objects are exported. When a rules application is exported, the internal objects are skipped. At the time of import, all the internal objects are recreated. Note that these internal objects may now have different names (object numbers) on the import site. Please let me know if you this is not the behavior you are seeing when you use export/import.
    http://download.oracle.com/docs/cd/B28359_01/appdev.111/b31088/exprn_brm_intro.htm#insertedID7
    Regards,
    -Aravind.

  • Database export /import

    hi all
    while i was exporting /importing im geting some of the errors so how to we need to avoiid thata errors .

    786631 wrote:
    but we can see using by the command at o.s level to verify the version ,so there is no pblm to check that.
    Posters, please mind these common-sense rules when participating here:
    - When asking a question, provide all the details that someone would need to answer it. Consulting documentation first is highly recommended.
    - When answering a question, please be courteous and respectful; there are different levels of experience represented here. A poorly worded question is better ignored than flamed - or better yet, help the poster ask a better question.
    - It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).
    - See more tips in the FAQ
    Thanks for doing your part to make this community as valuable as possible for everyone!
    - OTN ok post your os and oracle version and export/import command by os command here.

  • Errors while performing non-Unicode database export

    Hi,
    I am exporting of a non-unicode database (to perform a unicode conversion). The export has completed without any problems, but I frequently got the following messages in logfile.
    Error 1- UMGCOMCHAR read check skip, no data found; probably old SPUMG
    Error 2- enviornment variable I18N_POOL_WIDTH is not set. Checks are active
    Error 3- I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
    My query is that
    1- Are these above 3 errors an issue.
    2- When I import already exported files into a unicode database, will it cause any problem or loss of data.
    3- What is the fix to this issue.
    Points to be awarded for any kind of small help.
    Thanks

    Depending on the data that you have in your non-unicode database, potentially data expansions or data loss may occur.
    Data expansions
    For example, a 1 byte character in a VARCHAR2(1) column may expand to 2 bytes or 3 bytes in a Unicode (UTF8) database; hence you may need to re-define you scheme prior to importing the data into your new Unicode database.
    Data Loss
    This happens only if you have invalid characters inside your non-unicode database. For example, you may have some 8-bit non-ASCII characters inside your US7ASCII database, during export these characters will be converted to some replacement characters (?).
    However you can use the character set scanner (csscan) to scan your source database to detect both of the above scenarios. Please visit the Globalization Support section of OTN for more info - http://technet.oracle.com/tech/globalization/content.html
    Regards
    Nat

  • Higher to lower database export/import Query

    hi all,
    well i have exported 11g schema dump with version change 10.2(express edition) bcoz i want to import it to 10g express.....and now i m gettting error in import
    please tel me wt i have to do now?

    user9122568 wrote:
    ORA-19505: failed to identify file "E:\Oracle_xe\app\oracle\admin\XE\dpdump\xlntseo_16.dmp"
    ORA-27046: file size is not a multiple of logical block size
    OSD-04012: file size mismatch (OS 9192867)Does this file "xlntseo_16.dmp" exist on the location "E:\Oracle_xe\app\oracle\admin\XE\dpdump" ?
    If it does, what was the OS where 11g Express Edition was running ?
    How did you transferred the dmp file from there?
    It seems the dmp file is corrupted when you shifted it.

  • Full list of schemas not exported / imported when FULL=Y

    Hi Guys,
    Verison: 10.2.0.5
    Can advise on the full list of schemas not exported / imported when FULL=Y?
    thanks!

    dbaing wrote:
    Hi Guys,
    Verison: 10.2.0.5
    Can advise on the full list of schemas not exported / imported when FULL=Y?
    thanks!System schemas. Please see the following:
    http://docs.oracle.com/cd/B19306_01/server.102/b14215/dp_export.htm#i1006790
    http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_export.htm#i1006790
    You may also be interested in the following:
    -How to Perform A Full Database Export Import During Upgrade, Migrate, Copy Or Move Of A Database [ID 286775.1]
    -Oracle DataPump Quick Start [ID 413965.1]
    -How To move Or Copy A Database Using DataPump [ID 855268.1]

  • Database export from 32 bit to 64 bit...

    Hi All,
    I have one question about database export/import on different OS version i.e. 32 and 64 bit.
    I have below setup: I took one schema in export and import...
    export from : window-2003 server : 32 bit : ORACLE Database: 10.2.0.4.0
    import into : window-2003 server : 64 bit : ORACLE Database: 10.2.0.1.0
    and vise-verca is also working without any error or warnigns!!!
    from 32 to 64 bit (migrate from smaller to bigger )its okay but from 64 to 32 bit its also working !!! I really don't understand how its possible... not a single warning...
    Please suggest me.
    Thanks,
    Swati

    export basically consists of DDL and DML statements. These statements are platform independent. Only index definitions are exported, the indices are NOT exported.
    export does NOT copy or dump datafiles.
    As Microsoft wants to enslave the whole world, Sukkelserver will never be platform-indepedent.
    'One product to rule them all and in darkness bind them' (free after J.R.R. Tolkien Lord of the Rings)
    Sybrand Bakker
    Senior Oracle DBA

  • Database export/exports are extremely slow

    We run PeopleSoft (PeopleTools version 8.46) applications on Oracle 10g (10.1.0.3). database exports/imports were extremely slow, so when we contact PeopleSoft customer connection, we were advised to modify the init.ora file with the "_optimizer_cost_based_transformation=off". After we set the init.ora file, exports/imports are very fast.
    What is optimizercost_based_transformation? will database performance have any effect by setting this parameter? Does anybody has issues with 10g export/import issues?
    any help?
    Thanks,

    Here is the extract from PeopleSoft customer connection -
    . Required INIT.ORA Parameters for Oracle 10g
    . Change #1 - optimizercost_based_transformation=off
    According to Oracle support: "This parameter controls whether query transformations (sub-query unnesting, complex view merging and push join predicate ) are performed using an algorithm that relies only on optimizer cost (new in 10g) or an algorithm that uses a combination of optimizer cost and heuristics (pre-10g). "
    Can anbody tell me how extaclty this parameter will affect the performance of the system? Althoght we didn't see any performance issues right now (We are just in the process of implimentaion) Going forward, i am worried to have this im my init.ora file.
    Any thoughts/suggestions related to this topic is helpful.
    THanks,

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

  • Portal Export Import with DB on different OS

    Hi All,
    I have a quick question about exporting the OracleAS Portal Metadata Repository database. Our source DB is on a different OS to our target DB.
    We are going to apply the 10.1.2.3 patch and associated portal export/import patches to both nodes (from note 263995.1).
    Our understanding was that we would use the method described in Chapter 10 of the Portal 10.1.4 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/portal.1014/b19305/cg_imex.htm).
    However, according to metalink note#276620.1, because our source and target OS are different, we should use the database export/import methodology that is described in Chapter 11 of the Application Server 10.1.2 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/core.1012/b13995/prodtest.htm).
    Could anyone tell me which way is better, we would prefer to use the database export/import method, has anyone tried this and what are their experiences.
    Regards,
    Tim.

    kirwantd wrote:
    We are going to apply the 10.1.2.3 patch and associated portal export/import patches to both nodes (from note 263995.1).
    Our understanding was that we would use the method described in Chapter 10 of the Portal 10.1.4 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/portal.1014/b19305/cg_imex.htm).
    However, according to metalink note #276620.1, because our source and target OS are different, we should use the database export/import methodology that is described in Chapter 11 of the Application Server 10.1.2 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/core.1012/b13995/prodtest.htm).
    Could anyone tell me which way is better, we would prefer to use the database export/import method, has anyone tried this and what are their experiences.
    Regards,
    Tim.As far as your referred Metalink note is concerned, it gives you three options to move your repository with if you are working with 10.1.4 Portal.
    It's a difference of can, should and must.
    - It only shows ability to use three options ( can );
    - on the whole, it does not give preferences for any method ( should );
    - nor does it put a requirement for any single option ( must ).
    ( the only requirement/prohibition is for the option 2 which is not supported ).
    we have used the first three methods given on the note (yes, we also tried 2; this note came later). 1 is what we use regularly for transports between environments; and 3 we use for environment staging (as given in chap 11 of pt. 3). both can be messy with a large repository (we do so for about ~400 GB) repository. but following that supportability guide (Metalink Note 333867.1), method 1 works too.
    hope that helps!
    AMN

  • Export/import content area

    Hi,
    I'm trying to import/export the content area using the contexp.cmd and the contimp.cmd. When I run the import I receive the error '
    WWUTL_API_SiteTransport.GetImportSites: Import table WWUTL_SBR_TX_SITES$ is empty
    Rolling back transaction'
    The first thing the export does is truncate this table so it is always going to be empty. Any ideas how to get round this??
    I am running version 3.0.7.6.2 on NT 2000
    Thanks

    The import truncates the table to remove any old data that might be left from previous export/ import.
    Following this step, the Oracle Import utility imp is run. One reason why you are getting the error could be due to different versions of the 9iAS client utilities (which are 8.1.7 based in your case) and the database server. If the database server is 8.1.6 then you need to set the ORACLE_HOME to the database home prior to running the import. Once the import is complete you can reset the ORACLE HOME back to the 9iAS Home.

  • Difference between "Archive/restore" and "Export/import"

    What's the difference between the utilities "Archive/restore" and "Export/import"?
    Which utility must I use for putting my maps from a development environment to a production environment?
    For the moment I am using version 9.0.3.
    I will migrate to 9.2 when the version for AIX is available.

    Marc,
    You should use OWB Metadata Export/Import utilities (not to be confused with Database Export/Import utilities).
    The Archive and Restore utilities will be desupported in the next release of OWB.
    The exact differences are documented in "OWB 9.2 User Guide", page 15-12, "Differences Between Archive and Export" and page 15-23, "Differences Between Restore and Import". The same sections are available in "OWB 9.0.3 User Guide", pages 11-45 and 11-46 respectively.
    Nikolai

  • Command Line Export/Import Utility

    Hi,
    Is there a way to perform a command line export/import as if you were doing this via the Oracle ApEx GUI?
    If so, what is involved?
    Thanks.
    Tony.

    To import using SQL*Plus you are limited to installing an application as the original application ID and into the original workspace (both being the IDs contained in the file itself in various places). You can connect as any schema assigned to the workspace so long as that schema is not also assigned to other workspaces. If it is, you can connect as SYS, SYSTEM, or the FLOWS_xxxxxx schema, options that should be reserved as a last resort because of the undesirability of connecting as these privileged accounts.
    Scott

Maybe you are looking for

  • Mac Mini with DVI to video adapter REFUSES to display on TV!! Please help!!

    I purchased an apple DVI to Video adapter - which says for Mac mini and power mac G5 on the package. However not matter what I do, I can't get a picture on my TV, I have tried on 2 TV's and I get nothing but blank screen on both, with occassional gre

  • How to view emails in T?M backup

    I am unable to determine how to view emails in a time machine backup. What path will take me to the mail boxes?

  • Compliation albums displaying as individual artists

    I have imported a couple of complation albums (Very best of Later With Jools Holland Disc 1 and Disc 2 e.g.) but on the scrolling display in itunes it displayes an individual 'icon' for each artist in the compilation e.g. one for Adele, one for Kings

  • Manufacturing - Open Interfaces

    Hi everyone, I'm working with the Manufacturing Open Interfaces, version is 11i. I want to fill those fields: PO_LINES_ALL.MIN_RELEASE_AMOUNT (<== PO_LINES_INTERFACE.MIN_RELEASE_AMOUNT) PO_LINES_ALL.COMMITTED_AMOUNT (<== PO_LINES_INTERFACE.COMMITTED_

  • Dequeue message enqueued by different Oracle user

    I have two applications say A and B both are connected to same DB using differenct users i.e. UserA and UserB. The A application is enqueuing messages in AQ such as AQ_QTAB.ENQ_UI = 'UserA'. My spring based application(using spring AQ api) is connect