Export and Import of SAP ABAP RFC using R3trans

Requirment :You are using SAP ABAP system and you want to export and import ABAP RFC .
You can export and Import the RFC at OS level using R3trans.

Steps

1. Create export script with following commands , we named this script as “rfc_backup”.
   export
   file ‘/home/abpadm/rfc_data’

   select * from RFCATTRIB

   select * from RFCDES

   select * from RFCSYSACL

   select * from RSECACHK

   select * from RSECACTB

   select * from RSECTAB

   2. Create import/restore script with following commands ,we named it as “rfc_restore”

   import

   file=’/home/abpadm/rfc_data’

   Please find below the screenshot of scripts content.Once we execute the export script using R3trans ,it will export the RFC in the output file named “rfc_data”.

   
   
   

   3. How to Export SAP ABAP RFC data using export script ?
        Enter following command at OS level :
                              ” R3trans rfc_backup”

4.How to Import SAP ABAP RFC data using import script ?
Enter following command at OS level :

                                 ” R3trans rfc_restore”

trans.log – Log file will be created after executing R3trans <option> command, in current directory. One can verify the steps executed in trans.log.

All About Client Copy – Local,Remote, Import/Export

We can generate a blank client with SCC4.But how to fill the data in the client ?”Answer is the client copy.”
Client copy means “transferring client specific data” within same instance(SID) or between different instances(SID).
Client copy can be performed with three different methods –

Local client copy.
Remote client copy.
Client Import/Export.
Below brief details are given about client copy methods.

Local Client Copy :- This method is used to copy client within the same instance (SID).It is done by T-code SCCL.
Remote Client Copy-This method is used to copy client between different instances(SID).It is performed by T-code SCC9.

Client Import/Export:- This method is used to copy client between different instances(SID).It is performed by T-code SCC8

 Client Copy Pre-steps
To avoid data inconsistencies there are few pre-steps to be performed before starting client copy:-

1) Disconnect and lock business users(SU10).You can end the session of active users in the system through SM04. Once all users are logged out , check that no cancelled or pending update requests exists in the system.
2) Suspend all background jobs

• Execute SE38 as given below.

• Fill program name with “BTCTRNS1” as above figure.
• Press Execute.

3)  For a local copy , system must have enough space in the database or tablespace .
For remote copy, target system must have enough space in the database or tablespace. Check space using Tx DB02.

4) To avoid inconsistencies during client copy users should not be allowed to work in source client.

5) rdisp/max_wprun_time parameter should be changed to 2000 second as a SAP recommendation . Although you use parallel processes and schedule job in background , dialog processes will be used.
Local Client Copy

Local client copy is performed using Tcode SCCL. 
Scenario:-

• Source Instance & client := DKM-000
• Target Instance & client := DKM-202

Step 1) Create an entry for your new target client using SCC4 . In our scenario, we will create client 202 in DKM system.Log on to this newly created target client (DKM-202) with user SAP* and default password pass.

Step 2) Excute T-code SCCL.

Step 3)

• Select your desired profile
• Enter Source client.
• Enter Description

Step 4) By default Client Copy is executed as a single process. Single process will take a lot of time.We will distribute workload of single process to parallel(multiple) processes which will reduce time in copying a client.

1. Select Gotofrom menubar.
2. Select Parallel Process.Parallel processes are used to exploit the capacity of database better

Step 5) Always execute long running processes in background mode rather than foreground/dialog mode. Infact, some  processes run more quickly in background.

Step 6) The client copy logs are available in SCC3 . Status – “Successfully Completed” means client copy is completed.

Remote Client Copy:-

This technique uses Remote function call. You can view RFC from SM59. This technique depends on the network ,so network connectivity must be strong enough.

Scenario:-
Source Instance & client := BD1-101
Target Instance & client := DKM-202
Step 1) Log on to the target system. Here we will log on to DKM system. Create a new target client entry(202) using SCC4. Log on to this new target client with user SAP* and default password “pass“.Here we will log on to DKM-200 system.

Step 2) Execute Transaction Code SCC9.

Step 3) Fill the basic details as per your requirement.

Step 4) Select Parallel Process.Parallel processes are used to exploit the capacity of database better.

Step 5) Schedule the client copy in background

Step 5) Once the job is executed  data files and co-files of profiles from PKT system’s database are transferred to DKM system’s import buffer.Once we will import request in DKM only then it will be reflected in database of DKM system.

Depending on the chosen export profile there can be up to 3 transport requests created :

• Request PKTKO00151 will hold the cross client data,
• Request  PKTKT00151 will hold the client dependent data,
• Request  PKTKX00151 will also hold some client dependent data.

How to import the client?

Step 1) Log on to the newly created target clien(DKM-202) using SAP* and password pass.

Step 2) Start the STMS_IMPORT transaction
As shown below , import queue will open
Step 2) Select the transport requests generated by client export .Import theses transport requests on the target client.

The transport requests should be imported in the following sequence :

Request PKTKO00151

Request  PKTKT00151

Request  PKTKX00151

The system automatically detects these are client export transport requests and automatically performs the import of the 3 requests.

The import logs can be seen in STMS_IMPORT.
All About Client Copy – Local,Remote, Import/Export

Step 3) Post import phase:-

Once the import is done, execute SCC7  to perform the post client import actions,
All About Client Copy – Local,Remote, Import/Export
Schedule the post import job in background.
All About Client Copy – Local,Remote, Import/Export

Step 4) Import log will be available in SCC3. Client is successfully  imported.

Importing Tables with BR*Tools

Use

You can use BR*Tools for Oracle to import tables from an operating system file.

This section describes how you import tables with BR*Tools.

For more information on the approach to table import, see Export/Import.

Do not use this procedure for the transport of database objects between databases.

Do not use this procedure for restore.

Procedure

…

1. Start the procedure using BRGUI or BRTOOLS, or from the command line:

¡        BRGUI or BRTOOLS:

1. Choose Segment Management ® Import tables.

BRGUI or BRTOOLS displays the menu BRSPACE options for import tables, where you specify the options with which you call BRSPACE.

1. Set the required options:

Menu Entry	Equivalent BRSPACE Command Option
BRSPACE profile (profile)	-p|-profile
Database user/password (user)	-u|-user
BRSPACE export run / dump file (export)	-f tbimport -x|-export
Confirmation mode (confirm)	-c|-confirm
Scrolling line count (scroll)	-s|-scroll
Message language (language)	-l|-language
BRSPACE command line (command)	This shows you the BRSPACE -f tbimport command that is to be executed using the current settings.

iii.       Choose Continue.

BRGUI or BRTOOLS prompts you to start BRSPACE.

1. Choose Continue to start BRSPACE.

¡        Command line:

…

Enter at least the following command:

brspace –f tbimport

You can enter more parameters, including the table names, if required. For more information, see BRSPACE -f tbimport.

Whichever way you start the procedure – with BRGUI or BRTOOLS, or from the command line – you can use quick mode if you know the final object names, in this case the name of the BRSPACE export run or the export file name. For more information, see How to Use BR*Tools.

BRSPACE starts and you see a message that includes Start of BRSPACE processing. From now on, BRSPACE writes a detail log.

2. If you have already entered the BRSPACE export run or the export file name, continue with step 5 (quick mode).

BRSPACE displays the Import tables main menu.

3. Choose Import tables.

BRSPACE displays the list of BRSPACE exports for import:

List Entry	Meaning
Pos.	List sequence number
Run	BRSPACE export identifier – BRSPACE log name
Date	Export date
Tables	Number of tables in export
Dumps	Number of export dump files
Size [KB]	Total size of the export dump file(s)

4. Select an export run.

BRSPACE displays the menu Main options for import.

5. Set the required options:

Menu Entry	Meaning
Import type (type)	-f tbimport -t|-type
Owners for export (owner)	-f tbimport -o|-owner
Tables for import (tables)	-f tbimport -t|-tables
Import table rows (rows)	-f tbimport -r|-rows
Import table indexes (indexes)	-f tbimport -i|-indexes
Import table constraints (constraints)	-f tbimport -c|-constraints
Import table grants (grants)	-f tbimport -g|-grants

6. When you have set the required options, choose Continue

BRSPACE displays the menu Additional options for import.

Menu Entry	Meaning
Import buffer size in KB (buffer)	-f tbimport -b|-buffer
Commit after each array insert (commit)	-f tbimport -m|-commit
Ignore creation errors (ignore)	-f tbimport -n|-ignore
Max. size of dump file in MB (filesize) – input only possible if the dump file is notfrom BRSPACE. For more information, see menu entry BRSPACE export run / dump file above.	-f tbimport -z|-filesize
Force table import (force)	-f tbimport -f|-force
IMP command	The IMP command that is to be executed using the current settings. For more information, see your Oracle documentation.

7. To start processing with the selected options, choose Continue.

Results

Check the results in the BRSPACE logs.

• The summary log space<DBSID>.log displays the return code.
• The detail log s<encoded timestamp>.tbidisplays the details.

For more information on how to view the logs with BR*Tools, see Showing Logs and Profiles with BR*Tools.

The parameter file, PARFILE.IMP, is created in subdirectory <encoded timestamp> of the directory $SAPDATA_HOME/sapreorg. It contains the parameters for the Oracle import tool, IMP.

Exporting Tables with BR*Tools

Use

You can use BR*Tools for Oracle to export tables to an operating system file.

This section describes how you export tables with BR*Tools.

For more information on the approach to table export, see Export/Import.

Do not use this procedure for the transport of database objects between databases.

Do not use this procedure for restore.

Procedure

…

1. Start the procedure using BRGUI or BRTOOLS, or from the command line:

¡        BRGUI or BRTOOLS:

1. Choose Segment Management ® Export tables.

BRGUI or BRTOOLS displays the menu BRSPACE options for export tables, where you specify the options with which you call BRSPACE.

1. Set the required options:

Menu Entry	Equivalent BRSPACE Command Option
BRSPACE profile (profile)	-p|-profile
Database user/password (user)	-u|-user
Tablespace names (tablespace)	-f tbexport -s|-tablespaces
Table owner (owner)	-f tbexport -o|-owner
Table names (table)	-f tbexport -t|-tables
Export dump directory	-f tbexport -u|-dumpdir
Confirmation mode (confirm)	-c|-confirm
Scrolling line count (scroll)	-s|-scroll
Message language (language)	-l|-language
BRSPACE command line (command)	This shows you the -BRSPACE -f -tbexport command that is to be executed using the current settings.

If required, in Table names you can enter the names of multiple tables. You can use wildcards. For more information, see “Selecting Objects“ in Segment Management with BR*Tools.

In Tablespace names and Table owner, you can specify multiple objects but you cannot  use wildcards. BRSPACE processes all the tables in the specified tablespace name(s) or all tables belonging to the specified table owner(s).

You can also specify the dump directory using the parameter exp_dump_dir in the initialization profile init.sap, but the entry you make on the screen overwrites the profile parameter.

iii.       Choose Continue.

BRGUI or BRTOOLS prompts you to start BRSPACE.

1. Choose Continue to start BRSPACE.

¡        Command line:

…

Enter at least the following command:

brspace –f tbexport

You can enter more parameters, including the table names, if required. For more information, see -BRSPACE -f -tbexport.

Whichever way you start the procedure – with BRGUI or BRTOOLS, or from the command line – you can use quick mode if you know the final object names, in this case the table names. For more information, see How to Use BR*Tools.

BRSPACE starts and you see a message that includes Start of BRSPACE processing. From now on, BRSPACE writes a detail log.

2. If you have already entered the table names, continue with step 5 (quick mode).

If you have entered multiple tables, BRSPACE displays as confirmation a List of tables for export. If you have not already made a final selection, you can make a selection from this list.

Continue with step 5 (quick mode).

BRSPACE displays the Export tables main menu.

3. Choose Export tables.

BRSPACE displays the table list:

List Entry	Meaning
Pos.	List sequence number
Owner	Table owner
Table	Table name
Part.	Partitioned
Rows	Number of rows
Space [KB]	Space occupied by the table
Data [KB:%]	Amount of data in the table: percentage of occupied space

4. Select a table or multiple tables.

These examples only apply to input in character mode:

To select the first three tables in the list, enter 1-3.

To select the first and third tables, enter 1,3.

To select the first three tables and the fifth, enter 1-3,5.

To select all tables, select 0.

BRSPACE displays the menu, Main options for export of tables.

5. Set the required options:

Menu Entry	Meaning
Tablespaces for export (tablespaces) – display only	The tablespace that you selected above, if any
Owners for export (owner) – display only	The table owner that you selected above, if any
Export table rows (rows)	-f tbexport -r|-rows
Export table indexes (indexes)	-f tbexport -i|-indexes
Export table constraints (constraints)	-f tbexport -c|-constraints
Export table grants (grants)	-f tbexport -g|-grants
Export table triggers (triggers)	-f tbexport -t|-triggers

6. When you have set the required options, choose Continue

BRSPACE displays the menu, Additional options for export of tables.

Menu Entry	Meaning
Use direct path (direct)	-f tbexport -d|-direct
Export buffer size in KB (buffer)	-f tbexport -b|-buffer
Compress table extents (compress)	-f tbexport -m|-compress
Consistent export (consistent)	-f tbexport -n|-consistent
Max. size of dump file in MB (filesize)	-f tbexport -z|-filesize
Force table export (force)	-f tbexport -f|-force
EXP command	The EXP command that is to be executed using the current settings. For more information, see your Oracle documentation.

7. To start processing with the selected options, choose Continue.

Results

Check the results in the BRSPACE logs.

• The summary log space.log displays the return code.
• The detail log s.tbedisplays the details.

For more information on how to view the logs with BR*Tools, see Showing Logs and Profiles with BR*Tools.

Two files are created during the export:

• The export dump file, expdat.dmp, is created in subdirectory .edd of the dump directory.
• The parameter file parfile.expis created in subdirectory of the directory $SAPDATA_HOME/ sapreorg. It contains the parameters for the Oracle export tool, EXP.

Export/Import Tables using BRTOOLS

Case: I want to reorganize table and rebuild index offline for table SOFFCONT1. Table SOFFCONT1 contains SAP Business Workplace/SAPoffice objects which often grow rapidly in Netweaver based component.

Procedure: Here’s the procedure to export/import tables and rebuild index using BRTOOLS,

Export table SOFFCONT1

Drop index

Import table SOFFCONT1

Run Update Statistics Optimizer

Details steps :

1. Export table SOFFCONT1

>brspace -f tbexport -t soffcont1

BR0280I BRSPACE time stamp: 2009-06-06 21.10.00

BR1009I Name of database instance: R3X

BR1010I BRSPACE action ID: seasymoz

BR1011I BRSPACE function ID: tbe

BR1012I BRSPACE function: tbexport

BR0280I BRSPACE time stamp: 2009-06-06 21.10.07

BR0657I Input menu 359 – please enter/check input values

Main options for export of tables: SAPR3X.SOFFCONT1

1 * Export utility (utility) …………… [EXP]

2 * Tablespaces for export (tablespaces) … []

3 * Owner for export (owner) …………… []

4 – Export table rows (rows) …………… [yes]

5 – Export table indexes (indexes) ……… [yes]

6 – Export table constraints (constraints) . [yes]

7 – Export table grants (grants) ……….. [yes]

8 – Export table triggers (triggers) ……. [yes]

Standard keys: c – cont, b – back, s – stop, r – refr, h – help

BR0662I Enter your choice:

BR0280I BRSPACE time stamp: 2009-06-06 21.12.18

BR0663I Your choice: ‘c’

BR0259I Program execution will be continued…

BR0280I BRSPACE time stamp: 2009-06-06 21.12.18

BR0657I Input menu 360 – please enter/check input values

Additional options for export of tables: SAPR3X.SOFFCONT1

1 – Use direct path (direct) ……………. [yes]

2 – Export buffer size in KB (buffer) ……. [10240]

3 – Compress table extents/data (compress) .. [no]

4 – Consistent export (consistent) ………. [no]

5 # Parallel degree (parallel) ………….. [1]

6 – Max. size of dump file in MB (filesize) . [20000]

7 – Force table export (force) ………….. [no]

8 – EXP/EXPDP command (command) …………. [E:\oracle\R3X\102\BIN\exp parfile=I:\Oracle\R3X\sapreorg\seasymoz\parfile.exp]

Standard keys: c – cont, b – back, s – stop, r – refr, h – help

BR0662I Enter your choice:

BR0280I BRSPACE time stamp: 2009-06-06 21.13.15

BR0663I Your choice: ‘c’

BR0259I Program execution will be continued…

BR0280I BRSPACE time stamp: 2009-06-06 21.13.16

BR0370I Directory I:\Oracle\R3X\sapreorg\seasymoz created

BR0280I BRSPACE time stamp: 2009-06-06 21.13.16

BR0370I Directory I:\Oracle\R3X\sapreorg\seasymoz.edd created

BR1164I Export of tables will be started with command line: E:\oracle\R3X\102\BIN\exp parfile=I:\Oracle\R3X\sapreorg\seasymoz\parfile.exp

BR0280I BRSPACE time stamp: 2009-06-06 21.13.16

BR0670I Enter ‘c[ont]’ to continue, ‘b[ack]’ to go back, ‘s[top]’ to abort:

BR0280I BRSPACE time stamp: 2009-06-06 21.13.47

BR0257I Your reply: ‘c’

BR0259I Program execution will be continued…

BR0278I Command output of ‘E:\oracle\R3X\102\BIN\exp parfile=I:\Oracle\R3X\sapreorg\seasymoz\parfile.exp’:

Export: Release 10.2.0.2.0 – Production on Sat Jun 6 21:13:47 2009

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Username:

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 – 64bit Production

With the Partitioning, OLAP and Data Mining options

Export done in WE8DEC character set and UTF8 NCHAR character set

About to export specified tables via Direct Path …

Current user changed to SAPR3X

. . exporting table                      SOFFCONT1

continuing export into file I:\Oracle\R3X\sapreorg\seasymoz.edd\expdat1.dmp

962456 rows exported

Export terminated successfully without warnings.

BR0280I BRSPACE time stamp: 2009-06-06 22.44.59

BR1160I 1 table exported by EXP utility

BR0280I BRSPACE time stamp: 2009-06-06 22.45.02

BR0670I Enter ‘c[ont]’ to continue, ‘b[ack]’ to go back, ‘s[top]’ to abort:

BR0280I BRSPACE time stamp: 2009-06-06 22.55.09

BR0257I Your reply: ‘c’

BR0259I Program execution will be continued…

BR0280I BRSPACE time stamp: 2009-06-06 22.55.10

BR1022I Number of tables processed: 1

BR1003I BRSPACE function ‘tbexport’ completed

BR1008I End of BRSPACE processing: seasymoz.tbe 2009-06-06 22.55.10

BR0280I BRSPACE time stamp: 2009-06-06 22.55.12

BR1005I BRSPACE completed successfully

2. Drop index

>sqlplus “/as sysdba”

SQL>drop index “SAPR3X”.”SOFFCONT1~0″;

Index dropped

3. Import table SOFFCONT1

>brspace -f tbimport -t soffcont1

BR0280I BRSPACE time stamp: 2009-06-06 23.00.00

B1009I Name of database instance: R3X

BR1010I BRSPACE action ID: seasywiu

BR1011I BRSPACE function ID: tbi

BR1012I BRSPACE function: tbimport

BR0280I BRSPACE time stamp: 2009-06-06 23.00.00

BR0656I Choice menu 361 – please make a selection

Import tables main menu

1 = Import tables

2 – Show BRSPACE export runs

3 * Exit program

4 – Reset program status

Standard keys: c – cont, b – back, s – stop, r – refr, h – help

BR0662I Enter your choice:

BR0280I BRSPACE time stamp: 2009-06-06 23.00.14

BR0663I Your choice: ‘c’

BR0259I Program execution will be continued…

BR0699I Reading log file I:\Oracle\R3X\sapreorg\spaceR3X.log …

BR0280I BRSPACE time stamp: 2009-06-06 23.00.15

BR0658I List menu 362 – please select one entry

List of BRSPACE exports for import

Pos.  Run           Date                   Tables  Dumps       Size[KB]  Util.

1 = seasymoz.tbe  2009-06-06 21.09.57        1      2       25519234   EXP

Standard keys: c – cont, b – back, s – stop, r – refr, h – help

BR0662I Enter your selection:

BR0280I BRSPACE time stamp: 2009-06-06 23.01.22

BR0663I Your selection: ‘c’

BR0259I Program execution will be continued…

BR0280I BRSPACE time stamp: 2009-06-06 23.01.22

BR0657I Input menu 363 – please enter/check input values

Main options for import from dump file I:\Oracle\R3X\sapreorg\seasymoz.edd\expd        at.dmp,… (2 dumps)

1 * Import utility (utility) …………… [IMP]

2 – Import type (type) ………………… [full]

3 # Owner for import (owner) …………… []

4 # Tables for import (tables) …………. [SOFFCONT1]

5 – Import table rows (rows) …………… [yes]

6 – Import table indexes (indexes) ……… [yes]

7 – Import table constraints (constraints) . [yes]

8 – Import table grants (grants) ……….. [yes]

9 # Import table triggers (triggers) ……. [yes]

Standard keys: c – cont, b – back, s – stop, r – refr, h – help

BR0662I Enter your choice:

BR0280I BRSPACE time stamp: 2009-06-06 23.02.42

BR0663I Your choice: ‘c’

BR0259I Program execution will be continued…

BR0280I BRSPACE time stamp: 2009-06-06 23.02.42

BR0657I Input menu 364 – please enter/check input values

Additional options for import from dump file I:\Oracle\R3X\sapreorg\seasymoz.ed        d\expdat.dmp,… (2 dumps)

1 – Import buffer size in KB (buffer) ……. [10240]

2 – Commit after each array insert (commit) . [yes]

3 – Ignore creation errors (ignore) ……… [yes]

4 # Table exists action (action) ………… [skip]

5 # Parallel degree (parallel) ………….. [1]

6 # Max. size of dump file in MB (filesize) . [20000]

7 – Force table import (force) ………….. [no]

8 – IMP/IMPDP command (command) …………. [E:\oracle\R3X\102\BIN\imp parfile=I:\Oracle\R3X\sapreorg\seasywiu\parfile.imp]

Standard keys: c – cont, b – back, s – stop, r – refr, h – help

BR0662I Enter your choice:

BR0280I BRSPACE time stamp: 2009-06-06 23.03.06

BR0663I Your choice: ‘c’

BR0259I Program execution will be continued…

BR0280I BRSPACE time stamp: 2009-06-06 23.03.07

BR0370I Directory I:\Oracle\R3X\sapreorg\seasywiu created

BR1172I Import of tables will be started with command line: E:\oracle\R3X\102\BIN\imp parfile=I:\Oracle\R3X\sapreorg\seasywiu\parfile.imp

BR0280I BRSPACE time stamp: 2009-06-06 23.03.07

BR0670I Enter ‘c[ont]’ to continue, ‘b[ack]’ to go back, ‘s[top]’ to abort:

BR0280I BRSPACE time stamp: 2009-06-06 23.03.34

BR0257I Your reply: ‘c’

BR0259I Program execution will be continued…

BR0278I Command output of ‘E:\oracle\R3X\102\BIN\imp parfile=I:\Oracle\R3X\sapreorg\seasywiu\parfile.imp’:

Import: Release 10.2.0.2.0 – Production on Sat Jun 6 23:03:35 2009

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Username:

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 – 64bit Production

With the Partitioning, OLAP and Data Mining options

Export file created by EXPORT:V10.02.01 via direct path

import done in WE8DEC character set and UTF8 NCHAR character set

. importing SYS’s objects into SYS

. importing SAPR3X’s objects into SAPR3X

. . importing table                    “SOFFCONT1”     962456 rows imported

Import terminated successfully without warnings.

BR0280I BRSPACE time stamp: 2009-06-07 00.43.12

BR1166I 1 table imported by IMP utility

BR0280I BRSPACE time stamp: 2009-06-07 00.43.14

BR0256I Enter ‘c[ont]’ to continue, ‘s[top]’ to cancel BRSPACE:

BR0280I BRSPACE time stamp: 2009-06-07 00.46.19

BR0257I Your reply: ‘c’

BR0259I Program execution will be continued…

BR0280I BRSPACE time stamp: 2009-06-07 00.46.19

BR0656I Choice menu 361 – please make a selection

Import tables main menu

1 * Import tables

2 – Show BRSPACE export runs

3 = Exit program

4 – Reset program status

Standard keys: c – cont, b – back, s – stop, r – refr, h – help

BR0662I Enter your choice:

BR0280I BRSPACE time stamp: 2009-06-07 00.46.25

BR0663I Your choice: ‘c’

BR0259I Program execution will be continued…

BR0280I BRSPACE time stamp: 2009-06-07 00.46.25

BR0680I Do you really want to exit BRSPACE? Enter y[es]/n[o]:

BR0280I BRSPACE time stamp: 2009-06-07 00.46.33

BR0257I Your reply: ‘y’

BR0280I BRSPACE time stamp: 2009-06-07 00.46.33

BR1022I Number of tables processed: 1

BR1003I BRSPACE function ‘tbimport’ completed

BR1008I End of BRSPACE processing: seasywiu.tbi 2009-06-07 00.46.33

BR0280I BRSPACE time stamp: 2009-06-07 00.46.34

BR1005I BRSPACE completed successfully

4. Run Update Statistic Optimizer in SAP

Execute or Schedule this via DB13 then it will create a new index for table SOFFCONT1.

Note: Tables SOFFCONT1 need to be reorganized offline as they contain LONG RAW fields and must not be converted to LOBS with the online reorganization.

SAP-Export and Import tables in SAP from OS level

Summary:

You have a production system PRD-300.

You want to copy working PRD-300 to development system DEV-400.

System client copy is failing because system tables below in DEV-400 does not exist/corrupted/etc.

Table name: XXXX

Solution:

You can do a manual copy of system table to DEV-400

Given:

Target: DEV-400

Source: PRD-300 are not my systems.

Table: XXXX

Shared Transport directory: \\SAPtrans

* Note that above are pigment of explanation.

Requirements:

1. Disk space for transport directory

> To house the physical disk

2. Disk space for Target system

> When the copy is commited to target system

3. Be very careful in import. Avoid disconnection. Get a stable network connection and use mstsc CONSOLE to avoid getting kicked away from your work.

4. No users using the table. Lock the target system if you have to.

SAP tcode:

SE38 > RSTABLESIZE

This will let you view the actual physical SAP table size.

Procedure:

1.0 Create Export control file

1.1 Go to your SAP transport directory (\\SAPtrans).

1.2 Create a control file for R3trans with the following contents to create a data file:

1.2.1 Create a new file called export_control (no extension)

1.2.2 Place the details below

export

client =

file = ‘[the path for the data file and the file name]’

select * from XXXX

Example: (this will create a file in tmp directory from your data in working PRD-300 client.)

export

client = 300

file = ‘\\SAPtrans\tmp\XXXX_Table_copy_01042010.txt’

select * from XXXX

Step 2.0 Execute R3trans and Export data from working system

2.1 Logon as [sid]adm in the source system

2.2 Open command prompt.

2.3 Go to SAP bin directory and execute R3trans [control file]

R3trans [control file]

Example:

>R3trans export_control

>This is r3trans version 6.14 (release 700 – 12.06.09 – >15:20:00).

>unicode enabled version

>r3trans finished (0000).

***The process will create a data file as defined in the control file. In example, this will create a file XXXX_Table_copy_01042010.txt in tmp directory from your data in working PRD-300 client.

Step 3.0 Create Import control file

3.1 Go to your SAP transport directory (\\SAPtrans).

3.2 Create a control file for R3trans with the following contents to create a data file:

3.2.1 Create a new file called IMPORT_control (no extension)

3.2.2 Place the details below:

import

client =

file = ‘[the path for the data file and the file name]’

select * from XXXX

Example: (this will import table info from the physical data

in XXXX_Table_copy_01042010.txt to DEV client 400)

import

client = 400

file = ‘\\SAPtrans\tmp\XXXX_Table_copy_01042010.txt’

Step 4.0 Import the changes with R3trans

4.1 Logon as [sid]adm in the source system

4.2 Open command prompt.

4.3 Go to SAP bin directory and execute R3trans [control file]

R3trans [control file]

Example:

>R3trans IMPORT_control

>This is r3trans version 6.14 (release 700 – 12.06.09 – >15:20:00).

>unicode enabled version

>r3trans finished (0000).

When this is done. System table copy is completed.