Moving Old Development server to New Development server

[former_member430534]

Dear All,

We have installed a new sap development server with "Install Export" cd's provided in SAP Installation pack. Can any buddy tell us the procedure of importing old sap development server database into new sap development server.

Regards,

Danish Baig.

[Former Member · Accepted solution]

There is a way to transport your own developments (Z-programs, tables etc).

Please note that this is ONLY workbench objects.

NO customizing is included here!!!

If you also want customizing, please refer to system copy earlier in this thread.

You can logon to the old development system and go to transaction SE80.

Choose Package in the pulldown menu.

Enter Z* and press enter.

You can now doubleclick on a package of your choise.

Under "Object Name", mark the package name and right mouse click it.

Choose "Write Transport Entry".

You now get the possibility to enter either:

the package

or

all objects belonging to the package in a transport request. <-- this is what you want

One important thing though - Does the old and new development system have the same SID?

Yes:

You have to adjust the transport number range in the new development server (table E070L)

E g if the old server has DEVK901500 you can adjust the number range to DEVK902999 in the new server.

No:

You have to change owner of the objects in the new development server after import (tcode SM30, table TADIR)

[former_member430534 · Accepted solution]

We have started export of our old sap development server through SYSTEM COPY procedure and we got the error, I am attaching the export monitor log. You are requested to kindly help us,

INFO: 2010-07-10 09:00:16

Export Monitor is started.

CONFIG: 2010-07-10 09:00:16

Application options:

dataCodepage=4103

dbType=ADA

exportDirs=/dev_export/ABAP

installDir=/tmp/sapinst_instdir/ERPEhP4/LM/COPY/ADA/EXP/CENTRAL/AS-ABAP/EXP

jobNum=3

loadArgs=-stop_on_error

monitorTimeout=30

orderBy=

r3loadExe=/usr/sap/DEV/SYS/exe/run/R3load

sapinst=

server=

trace=all

tskFiles=yes

CONFIG: 2010-07-10 09:00:16

List of packages with table structure: 'SAP0000'.

CONFIG: 2010-07-10 09:00:16

List of packages with views: 'SAPVIEW'.

TRACE: 2010-07-10 09:00:16 com.sap.inst.migmon.LoadTask run

Unloading of 'SAPAPPL1' export package is started.

TRACE: 2010-07-10 09:00:16 com.sap.inst.migmon.LoadTask processPackage

Unloading of 'SAPAPPL1' export package from database:

/usr/sap/DEV/SYS/exe/run/R3load -e SAPAPPL1.cmd -datacodepage 4103 -l SAPAPPL1.log -stop_on_error

ERROR: 2010-07-10 09:00:18 com.sap.inst.migmon.LoadTask run

Unloading of 'SAPAPPL1' export package is interrupted with R3load error.

Process '/usr/sap/DEV/SYS/exe/run/R3load -e SAPAPPL1.cmd -datacodepage 4103 -l SAPAPPL1.log -stop_on_error' exited with return code 2.

For mode details see 'SAPAPPL1.log' file.

Standard error output:

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

INFO: 2010-07-10 09:00:46

All export packages are generated.

INFO: 2010-07-10 09:00:46

All export packages are processed.

WARNING: 2010-07-10 09:00:46

1 error(s) during processing of packages.

INFO: 2010-07-10 09:00:46

Export Monitor is stopped.

[Former Member · Accepted solution]

And did you read SAPAPPL1.log ?

[former_member430534 · Accepted solution]

Yes it is giving following errors

(EXP) TABLE: "QCM8ZITAX_SLABS" #20100709122513

DbSl Trace: prepare() of C_0157, rc=1, rcSQL=-942 (POS(97) Unknown table name:QCMZITAX_SLABS)

DbSl Trace: SQL PREPARE on connection 0, rc=-942 (POS(97) Unknown table name:QCMZITAX_SLABS)

(EXP) ERROR: DbSlPrepare/BegRead failed

rc = 103, table "QCMZITAX_SLABS"

(SQL error -942)

error message returned by DbSl:

POS(97) Unknown table name:QCMZITAX_SLABS

(DB) INFO: disconnected from DB

/usr/sap/DEV/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/DEV/SYS/exe/run/R3load: END OF LOG: 20100709122513

[Former Member · Accepted solution]

This means that you have temporary conversion tables in you source system.

You have to investigate your source system to see if you have tables that are not fully converted

(e g ICNV or table conversion such as pool to transparent) or if the entries can be deleted.

Follow the note:

[Note 9385 - What do you do with QCM tables (conversion tables)|https://service.sap.com/sap/support/notes/9385]

It doesn't matter if the note is old, it's is still valid in your case.

When you're done, you have to run the export again.

[Former Member · Accepted solution]

Don't know wheather you perform Import / Export or copying the DB using offline backup, It should also promt in case of Import. Also check if you have any other DB02 / DB connections with your old system.

Regards;

[JPReyes · Accepted solution]

That means you have not read the System copy guide... one of the first preparation steps is to check for this tables.

Read the Documentation before proceding any further.

Regards

Juan

[former_member430534 · Accepted solution]

I have checked the "Invalid Temp Table" and deleted that table "QCMZITAX_SLABS" through SE14. When I display that table in the transaction screen SE14 through Extras>RunTime Object->Display it is still showing me all the records in the table, but when I go to Extras>RunTime object>Check it is show me a message "Active DDIC source for QCMZITAX_SLABS missing or incorrect"

Regards,

Danish Baig.

[Former Member · Accepted solution]

When you delete temporary tables via SE14, the physcial table is also deleted.

What happends if you start tcode SE14, enter the table name and press enter.

You should receive a message "Object does not exist".

If this is true, then the table doesn't actually exist in the database, but only as a runtime object.

If you want to delete an runtime object you must be sure that the table does not really exists.

Nor should the source code exist (tcode SE11).

When you are sure (and even checked again!) you can drop the nametab.

Start tcode SE37 and first run function DD_GET_NAMETAB and press F8

Enter your tablename and press F8 again.

If the nametab exist, you get values in X030L_WA and resulting entries in X031L_TAB.

If you got entries, continue by start tcode SE37 again.

Enter function DD_NAMETAB_DELETE and press F8.

Enter your tablename and press F8 again.

Afterwards, run the function DD_GET_NAMETAB to make sure that it's actually gone.

Also check in SE14 as you did before.

[JPReyes]

That depends in several factors.. is your system ABAP, ABAP+JAVA?, Is the target server the same platform/database?...

Hardware migration should be done via system copy as said before.

Read the system copy guides

Regards

Juan

[former_member430534]

Thanks for the response. We have installed our new SAP development server on same OS (Suse Linux 64bit) and database (Max DB 7.7.06) versions which were installed in old SAP development server.

After going through the link, it seems like I have to install new SAP development server after taking Export from old SAP development server which means we need to install new SAP development server again? if this the case can any buddy guide me how I can import the old SAP development server data with out re-installing new SAP development server?

Regards,

Danish Baig.

[JPReyes]

You should have read the guides before proceding...

Anyhow... If your instance is ABAP you could do a DB copy which is basically restore the DB from a backup of the old server DB.

If ABAP+JAVA you are better off following the steps on the system copy guide as JAVA can give you quite a few headaches if done incorrectly.

In anycase is not big deal to remove the installation and run sapinst again.

Regards

Juan

[former_member430534]

We have installed only ABAP instance.

Regards,

Danish Baig.

[Former Member]

Hi,

This process called homogenious system copy, please go thr below link, it will help you

or else please check with DB Admin or Basis team they will help you to export and import DB

Thanks,

Sreeni.