Help need on Migration Monitor during the OS migration

[Former Member]

Dear Guru,

I need some helps to start the export with migration monitor tools.

First I want to start the export on the source system and then move the file by myself to the source system.

I can start the export in client mode? (I try already but it is just hang there)

Then, I try to start the export with server mode, but I got the error below:

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC

(DB) INFO: Export without hintfile

Alternate NameTab for type "BAPIPAREX_HELP" was missing and has been simulated.

(GSI) INFO: dbname = "BWT20030708040756 "

(GSI) INFO: vname = "ORACLE "

(GSI) INFO: hostname = "HSEA-PDC-S015 "

(GSI) INFO: sysname = "Windows NT"

(GSI) INFO: nodename = "HSEA-PDC-S015"

(GSI) INFO: release = "5.2"

(GSI) INFO: version = "3790 Service Pack 2"

(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 15 Step 6)"

(BEK) ERROR: SAPSYSTEMNAME not in environment

my export properties are as below:

#

1. Export Monitor options

#

#

1. Server operating mode

#

server

#

1. Client operating mode

#

#client

#

1. Exchange mode: ftp | net

#

#ftp

net

#

1. Common options

#

1. List of export directories, separator on Windows ; on UNIX :

exportDirs=V:\sap_inst_temp\export

1. Installation directory

installDir=C:\Program Files\sapinst_instdir\NW04\COPY\EXPORT\ABAP\COPY\NUC\DBEXP

1. Package order: name | file with package names

orderBy=name

1. DDL control file, default is DDL<DB_TYPE>.TPL

ddlFile=

1. File with mapping between DDL files and package names

ddlMap=

1. Monitor timeout in seconds

monitorTimeout=30

#

1. R3load options

#

1. Optional path of R3load executable

r3loadExe=

1. Generation of task files: yes | no

tskFiles=yes

1. Code page for data files

dataCodepage=

1. Additional R3load arguments for TASK phase

taskArgs=yes

1. Additional R3load arguments for LOAD phase

loadArgs=

1. Number of parallel export jobs

jobNum=3

#

1. Network options

#

1. Network exchange directory

netExchangeDir=V:\sap_inst_temp\export\netExchange

#

1. FTP options

#

1. Remote FTP host

ftpHost=

1. Name of remote FTP user

ftpUser=

1. Password of remote FTP user

ftpPassword=

1. List of remote FTP directories for export dump, separator : or ;

ftpExportDirs=

1. Remote FTP exchange directory

ftpExchangeDir=

1. Number of parallel FTP jobs

ftpJobNum=3

#

1. Socket options

#

#socket

1. Server hostname

host=

1. Server port number

port=

#

1. Trace option

#

1. Trace level

trace=all

#

1. E-mail options

#

1. SMTP server

mailServer=

1. "From" email address

mailFrom=

1. "To" email address

mailTo=

If anyone can share the document base on the migration monitor, It will be helpful.

Thank you and Best Regards,

Rapheephan

[markus_doehr2 · Accepted solution]

> Then, I try to start the export with server mode, but I got the error below:

>

> (DB) INFO: connected to DB

> (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC

> (DB) INFO: Export without hintfile

> Alternate NameTab for type "BAPIPAREX_HELP" was missing and has been simulated.

> (GSI) INFO: dbname = "BWT20030708040756 "

> (GSI) INFO: vname = "ORACLE "

> (GSI) INFO: hostname = "HSEA-PDC-S015 "

> (GSI) INFO: sysname = "Windows NT"

> (GSI) INFO: nodename = "HSEA-PDC-S015"

> (GSI) INFO: release = "5.2"

> (GSI) INFO: version = "3790 Service Pack 2"

> (GSI) INFO: machine = "4x AMD64 Level 6 (Mod 15 Step 6)"

> (BEK) ERROR: SAPSYSTEMNAME not in environment

Did you execute it as <sid>adm user?

Markus

[Former Member · Accepted solution]

Dear Markus,

I've execute it with my <sid>adm user.

I had no problem when exported the database without the migration monitor.

The reason to use the migration monitor to reduce downtime on the PRD system.

Thank you and Best Regards,

Raphee

[markus_doehr2 · Accepted solution]

Your problem is, that the environment SAPSYSTEMUSER is not set.

If you logon with <sid>adm - is that set?

Markus

[Former Member · Accepted solution]

Dear Markus,

Thank you so much.

We have setup the parameter manually.

It seem to be okay now.

Best Regards,

Rapheephan

[florin_radulea · Accepted solution]

Markus,

You are the man.

Regards,

Florin

[Former Member · Accepted solution]

Hi Rapheephan,

I have also strucked with the same error while migration

ERROR: SAPSYSTEMNAME not in environment

Could you please guide in how to solve the error.

Thanks!

Vardhan.

[Former Member · Accepted solution]

Hi Rapheephan ,

I have same situation, mean sapusername not in param , how you solved your problem