Process of Importing and Exporting Table Space using Brtools

[Former Member]

Hi All,

I have been told by our development team to perform export a custom table from one system to another system.

Source table is from our legacy BW system -

SAP Release : SAP_BASIS 620

DBSL Patch No. 125

SAP R/3 Kernel 640_REL

Database Release 9.2.0.4.0

Target system is our New ECC6 BW System -

SAP Release : SAP_BASIS 700

SAP Kernel : 700_REL

Database Client Library : OCI_102 (10.2.0.2.0)

created in : HP-UX B.11.23 U ia64

DBSL Patch No. : 167

Database Release : 10.2.0.2

Can any one run through sequence of events which i must follow.

1. Table name : ZBFLINCOME / Table Owner SAPWUK

2. I dont see any ref of LONG RAW, so i assume LONGtoLOB migration/conversation stuff does not apply.

3. Confirm Size of Table , so that suffucent space is available in sapreporg directory ,

Table size is 554 MB, sapreorg has 8141MB free

4.To be on Safe Side, Stop sap and then export the table using brtools.

I have one question, When i export the table, does brtools delete the original table from the sap database, or does it do nothing.

Can anyone advise what correct command syntax i should to export the table ZBFLINCOME

5.Move th exported file to target server and import the table using brtools

Can anyone advise what correct command syntax i should to import the table ZBFLINCOME

Also what about table indexes, Do i need to create one maually or does one get generated automatically.

Thanks in advance

Edited by: Eric Brunelle on Jan 19, 2011 11:03 AM

[former_member227281]

Hello Rizwan,

I have one question, When i export the table, does brtools delete the original table from the sap database, or does it do nothing.

The Answer : If you select option -- reorganization then after export complete, brtools will delete the table. Hence it is advisable not to select the option - reorganization.

If the option only export is available in brtools then it is safe to perform export table as brtools does not delete table.

The other options is to use exp command at os level at ora<sid> user.

$exp and press enter key.

use copy command or ftp command to move the exported file (filename will have extension dmp) from source system to target system.

Then on target system, before import, check the exiswting entries of table becasue if existing records on target system is already present in source system then duplicate entries will be present when you import table. Incase if the table is not present in target system then import will create table structure during import .

The command to perform import at ora<sid> user is

$imp and press enter key

After import completed, then check index is created or not by imp command. If not then create index manually.

Thanks and Regards

APR

[Former Member]

Hi Prasad,

Can you please give me complete command syntax to export the table?

Thanks

[nirmal_konchada]

The below link would be helpful

http://help.sap.com/saphelp_crm50/helpdata/en/7c/209667b05b844399f6402a0213ef95/frameset.htm

Regards,

Nirmal.K

[former_member227281]

Hi Rizwan,

Login to ora<sid> user.

ENter the command as follows

$exp and press enter key.

Input prompt appears asking you tyo type the filename for export dump.

The next line will ask you to enter table name to be exported.

The remaining is default values just simply press enter key.

After the export complete then

use copy command or ftp command to move the exported file (filename will have extension dmp) from source system to target system.

Then on target system, .

The command to perform import at ora<sid> user is

$imp and press enter key

Thanks and Regards

APR

[volker_borowski2]

Hi,

since the Oracle release is diffrent, and may be the schemaowner is as well, I'd go with a transport!

Create a transport of copies with just a single line:

R3TR TABL ZBFLINCOME

Release the transport and import on target.

Warning: If a table with the same name already exists in the target system, it will be destroyed.

After importing this transport, you will have all neccessary dictionary information as well as

indexes defined in the source system also in the target system.

If you get any errors (check the transport independent steps in the logs as well), correct these before you proceed.

Once this is done, you can do the same with a

R3TR TABU ZBFLINCOME

as suggested by Eric. This will transport only the table data.

Volker

[former_member204746]

I have split your topic in 2 posts. here's the 2nd part.

Here the table structure details :

desc SAPWUK.ZBFLINCOME;

Name Null? Type

-

---

-

---

-

---

LOGSYS NOT NULL VARCHAR2(10)

EQUIP NOT NULL VARCHAR2(18)

CONTR NOT NULL VARCHAR2(10)

PERIOD NOT NULL VARCHAR2(3)

VERSION NOT NULL VARCHAR2(3)

ATTACH NOT NULL VARCHAR2(18)

TERM NOT NULL VARCHAR2(3)

COMP_CODE NOT NULL VARCHAR2(4)

RENTCOCD NOT NULL VARCHAR2(4)

LEASETYPE NOT NULL VARCHAR2(2)

SALESOFF NOT NULL VARCHAR2(4)

SALESGRP NOT NULL VARCHAR2(3)

SOLDTO NOT NULL VARCHAR2(10)

COUNTRY NOT NULL VARCHAR2(3)

FINTYPE NOT NULL VARCHAR2(3)

MTH_END_DT NOT NULL VARCHAR2(8)

FISCYEAR NOT NULL VARCHAR2(4)

REVCASH NOT NULL NUMBER(17,2)

REVACCR NOT NULL NUMBER(17,2)

EQUIPCOST NOT NULL NUMBER(17,2)

EQUIPRESID NOT NULL NUMBER(17,2)

RETURN_AMT NOT NULL NUMBER(17,2)

CASHFLOW NOT NULL NUMBER(17,2)

TAXMOVE NOT NULL NUMBER(17,2)

INTPAID NOT NULL NUMBER(17,2)

PTO NOT NULL NUMBER(17,2)

PROFIT NOT NULL NUMBER(17,2)

NCI NOT NULL NUMBER(17,2)

AVGNCI NOT NULL NUMBER(17,2)

NIFL NOT NULL NUMBER(17,2)

GROSS_EARN NOT NULL NUMBER(17,2)

DEPREC NOT NULL NUMBER(17,2)

TWDVBF NOT NULL NUMBER(17,2)

CAP_ALLOW NOT NULL NUMBER(17,2)

LEASE_IRR NOT NULL NUMBER(17,3)

ACCUM_GROSS_EARN NOT NULL NUMBER(17,2)

ACCUM_DEPREC NOT NULL NUMBER(17,2)

ACCUM_INTPAID NOT NULL NUMBER(17,2)

TOTAL_ACCUM_BILL NOT NULL NUMBER(17,2)

TOTAL_ACCUM_PTO NOT NULL NUMBER(17,2)

TOTAL_ACCUM_INT NOT NULL NUMBER(17,2)

DOC_CURRCY NOT NULL VARCHAR2(5)

BASE_UOM NOT NULL VARCHAR2(3)

COST_IRR NOT NULL FLOAT(126)

COST_RATE NOT NULL FLOAT(126)

TAX_RATE NOT NULL FLOAT(126)

TOTAL_ACCUM_DEPR NOT NULL NUMBER(17,2)

NPV NOT NULL NUMBER(17,2)

NPV_FUND NOT NULL NUMBER(17,2)

RETURN_MTH NOT NULL NUMBER(17,3)

PROFIT_RATE NOT NULL FLOAT(126)

NBV NOT NULL NUMBER(17,2)

LEASE_OBLIG NOT NULL NUMBER(17,2)

[former_member204746]

if table is not taht big, you could also transport it with its contents with R3TR-TABU and R3TR-TABL.