OS/ DB Migration Solman 4.0

Dear Experts,
I need all of your views as we need to start the OS/DB migration of solution manager in next 2 days and complete it by 7 days. The configuration details are as follows.
Source:
Solution Manager:Solution Manager 4.0
OS: Windows Server 2003 Enterprise x64 Edition
Database: DB2 V9.1.01
Target:
Solution Manager:Solution Manager 7.0 EhP1
OS: HP_UX11.23 (11v2)
Database: DB2 9.7.01
I will really appreciate all of your responses
Best Regards,
Viswanathan Subramanian

Hi Derek,
This will be a non-production OS migration.
Is there any procedure specific to solman 7.0 to be followed I believe it is same for any system flavour under NW 7.0 except BW.
Can u give me idea on this process I understood R3load is the method to be used for DB independent copy.
Thanks in advance
Viswanathan S

Similar Messages

Migrating SolMan to HEC questions

Hi Experts!
If we move SolMan 7.0 to HEC, do we need to upgrade to 7.1 first and then migrate to HEC?
If an upgrade must be done first, is there an approach, like for BW, to upgrade and migrate in one step to HEC?
Any possibility of migrating to HEC first and then performing the upgrade to 7.1?
We are trying to avoid a two step process (upgrade/migrate) and combine into one step.
Thanks.
S

Setup Assistant is the best method for migrating. What normally slows down a computer is not enough RAM, a setting that has gone amiss possibly installing antivirus or other performance enhancing (actually performance robbing) applications. You can break down the migration to be apps, settings, data files etc. IMHO the VERY best thing you can do is to ensure your old machine is up-to-date in all the applications it has, ensure not antivirus or performance robbing apps are uninstalled per the developers instructions and that it's running well. The back the old machine to a Time Machine external HD> DO NOT USE a NAS to backup!
If you are worried about apps then don't migrate them, do a manual re-install on all your legacy apps. However remember mavericks will not run PPC based apps so if you have any legacy apps that are PPC based then upgrade or replace them because they will NOT work in Mavericks.
To be honest you are probably worrying about this too much, doing a migration is extremely simple and efficient assuming you follow some basic rules:
1. Restore from Time Machine or a bootable clone external HD, NOT A NAS
2. DO NOT attempt a wireless migration unless you don't mind it to take weeks, no I am not kidding!
To get your libraries on the external HD recognized simply connect the external HD to the new machine and double click the libraries and the app will launch and link to the EHD.
AGAIN DO NOT USE A NAS for backing up or restoring. At best they are unreliable and worst they fail to connect at all.

Solution Manager Key info for Migration

Hi Guru's,
As we are planning to migrate / system copy all systems like SAP Portal , BI & XI to a new hardware, from P5-P590 to P6-P570 (The OS version, TL level and Patch Level for the both LPAR's remains same, i.e No change on OS versions).
My question here is:
We have generated a solution manager key for all systems while installation, if we migrate any SAP system to a new hardware i.e. P6-P570, will the solution manager keys work in new environment for all systems? Our Solution manager server is also on P5-P590 environment.
As we are planning to migrate solman server also to a new env (P6-P570) from P5-P590, if the solmanger key doesnu2019t work on new env, do we need to migrate the solman server first to a new env and generate a new solman key and assign the key to the migrated systems on new env.
Note: We are doing as is migration, i.e. hostname, SID & IP remains same.
I hope my question is clear and understandable.
Please provide your valuable inputs / suggestions for the migration and also provide any link for the migrations.
Points will be awarded for each valuable answer.
Regards
Sreedhar Gunda

Hi,
If your operating system is Unix ( any flavour ) then you can create the same mount points on new hardware ( except rootvg - operating system ) and copy entire contents from old hardware's mount points to new one. You need to take care of users , groups like ORA<SID>, and <SID>ADM , DBA, SAPSYS etc. In that scenario your hardware key will change so you need to apply new license in marketplase.
Better to migrate rootvg from your existing OS if possible , in that scenartio you need not take care of OS users , groups etc.
Regards
Kulwinder Singh

Solution Manager Key info

Hi Guru's,
As we are planning to migrate / system copy all systems like SAP Portal , BI & XI to a new hardware, from P5-P590 to P6-P570 (The OS version, TL level and Patch Level for the both LPAR's remains same, i.e No change on OS versions).
My question here is:
We have generated a solution manager key for all systems while installation, if we migrate any SAP system to a new hardware i.e. P6-P570, will the solution manager keys work in new environment for all systems? Our Solution manager server is also on P5-P590 environment.
As we are planning to migrate solman server also to a new env (P6-P570) from P5-P590, if the solmanger key doesnu2019t work on new env, do we need to migrate the solman server first to a new env and generate a new solman key and assign the key to the migrated systems on new env.
Note: We are doing as is migration, i.e. hostname, SID & IP remains same.
I hope my question is clear and understandable.
Please provide your valuable inputs / suggestions for the migration and also provide any link for the migrations.
Points will be awarded for each valuable answer.
Regards
Sreedhar Gunda

Hi,
Solution Manager key is based on SID, Hostname, Installation Number, and Product Versions. Since in your case all these remains the same. You don't need to Generate a new key. Moreover, you are not upgrading or installing new instance.
Check [this link|http://help.sap.com/saphelp_sm40/helpdata/en/45/50b3347f166600e10000000a114a6b/content.htm].
and the note 811923.
This should solve your problem.
Feel free to revert back.
-=-Ragu

Migration monitor (migmon.jar) not found when installing Solman 4.0

Hi again all,
I am doing the installation of the database instance for Solution Manager 4.0 and at the Import ABAP step, it ends with the following error:
WARNING 2007-09-20 17:22:32
Execution of the command "/opt/IBMJava2-amd64-142/bin/java -classpath migmon.jar
-showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs /u02
/sap/EXP1:/u02/sap/EXP2:/u02/sap/EXP3:/u02/sap/EXP4 -installDir /tmp/sapinst_ins
tdir/SOLMAN/SYSTEM/ORA/DISTRIBUTED/AS/DB -orderBy "" -r3loadExe /usr/sap/SMD/SYS
/exe/run/R3load -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorT
imeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return
code 1. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142ifx-200703
28 (JIT enabled)
J9VM - 20070327_1654_LHdSMr
JIT - r7_level20061020_1803ifx1)
The java class is not found: com.sap.inst.migmon.imp.ImportMonitor
The migmon.jar file is not present anywhere on the server. It appears that this is needed for doing system copies but why is it looking for it here since this is just a fresh installation and not a system copy? And more importantly, how do I resolve this?
Steve

Read the first sentence of my first reply to your question
The tool to import data is called "Migration Monitor" because it was initially developed assisting on migrations of systems. Since the process itself is the same (R3load export/import), it was integrated in the installer. Don't let the name confuse you.
Markus

Migration SAP SolMan 7.1 MSSQL 2008 R2 Enterprise Edition to MSSQL Standard Edition

Hello,
I try to migrate a SAP SolMan 7.1 on Windows MSSQL 2008 R2 ENTERPRISE EDITION to
MSSQL 2008 R2 STANDARD EDITION.
In the source system (MSSQL 2008 R2 ENTERPRISE EDITION) there is "table compression" and
"partitioning" active.
the MSSQL STANDARD EDITION doesn`t support these two features.
So a normal DB backup on the source system and restore in the destination system is not possible.
But the tables compression I can deactivte by the SQL script
SELECT DISTINCT ‘ALTER TABLE [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
FROM sys.partitions p
join sys.objects o
on p.object_id = o.object_id
WHERE o.TYPE = ‘u’
and data_compression_desc != ‘NONE’
UNION
SELECT ‘ALTER INDEX ALL ON [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
FROM sys.partitions p
join sys.objects o
on p.object_id = o.object_id
WHERE o.TYPE = ‘u’
and data_compression_desc != ‘NONE’
is there a way to undo or deactivate the the SQL table partitioning without any data lost ?
Or is there a other way to migrate a SAP SolMan 7.1 form MSSQL 2008 R2 ENTERPRISE EDITION to MSSQL 2008 R2 STANDARD EDITION ?
Best regards
A. Moore

Hi Moore
Could you refer the SAP Note for MS Sql Version supports
1076022 - Release planning for Microsoft SQL Server 2008 (R2)
and MS SQL table compression & decompression SAP Note
1488135 - Database compression for SQL Server
BR
SS

Configuring CHARM after solman migration

Hi,
We are going to migrate our existing Solman system to another system using system refresh, we have implemented CHARM which takes care of the Transport for our ECC and Portal Systems, my question is what needs to be done in the newly migrated system after the system refresh and what changes we need to make in our ECC System in order for CHARM to work in the newly migrated system.
Our landscape info
We have DEV,QA and Prod in our existing landscape with charm is configured in the Solman. Our Prod is the main domain controller and solman is the secondary domain controller, can some one explain me what needs to be done in the configuration after the system migration.
Sathish

Hi
Only hostname/ipaddress and SID name will be changed for solution manager. So for solution manager back RFC in ECC and EP systems you need to change hostname/ipaddress and instance number.
From SMSY try to update/read ECC and EP systems data. Check it is working fine or not.
Suman

Trusted systems gone after Solman hardware migration

Hi All,
I migrated our Solman EHP1 to a new x64 box via homogeneous system copy, everything went absolutely fine but one thing... Solman is not trusted any longer in any of the systems. The host/IP is the same and RFC's in SM59 all look good... I wondered if theres any way to regenerate the trusted/trusting RFC's without affecting the rest of the configuration in SMSY.
Also, checked and the satellite systems still and Solman still trust them but not the other way around
Regerads
Juan

Hi Juan,
I came across issue some times back and got Note 128447 - Trusted/trusting systems
This refrence i got from some other note which was referring the post installation activities(System copy) and was suggesting to re-estabilishing trusting/trusted system relationship.
May be worth to read this note
Regards,

ChaRM migration to New Solman System

Hi,
We are planning to Migrate old Solman system ChaRM to new Solman ChaRM.
Now how can I migrate RFCs & CDs to new Solman system ChaRM.
Regards
P K

Hi PK
There is no tool for moving the SLFN documents from one solman to the other. The only option to keep the already created tickets is to upgrade the the existing solman system to release 7.1.
In SOlman 7.1 SM* transaction types are comming so during the upgrade we don´t make any changes to the old transaction types like SLFN, so the upgrade should not change your current configuration in solman 7.0 for incident management.
You will not have any impact on Service Desk when using the old transaction type SLFN.
So there can be only one recommendation for your situation:
Perform an UPGRADE and please don't go for a fresh installation with data migration afterwards.
There is no easy transfer of CRM document (as incidents, change requests, issues, top issues, ...) available.
Advantages of the upgrade:
- standard procedure
- configuration and data is available after the upgrade
The solman 7.1 is coming with new transaction types that you need to customizing and it is not touching the old transaction types existing in solman 7.0.
Please, take a look at this:
http://scn.sap.com/docs/DOC-30133
Also check below note which answers few FAQ's:
1567003: FAQ: ST710 Incident Management Frequently Asked
Check below Wiki as well:
http://wiki.sdn.sap.com/wiki/display/SAPITSM/Configuration+and+Administration+of+ITSM
(all in one line)
And select Configuration Guide - Application Incident Management
Also check the External Service Desk Functionality.
Please follow the path to the nodes listed below.
SAP Solution Manager Implementation Guide
SAP Solution Manager
    Capabilities (Optional)
      IT Service Management
        External Integration
             Service Desk
                 External Service Desk
Thanks
Vikram

Notice to end customer explaining SolMan migration

Hi there,
Please see query from Partner:
"We were verifying one of our license customers about S-user usage and they are asking for u201Cofficialu201D information in regards to SolMan migration from SAP before they could verify the information. Can you help me on this? Is there a notice to end customer explaining SolMan migration? "
Any direction that can be provided would be greatly appreciated.
Regards,
Martin

Hi Martin,
Is this the requested letter from SAP?
[Letter to VAR customers|http://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000087033&_OBJECT=011000358700000619282008E]
You may also post VAR specific questions in
[Forum - SAP Solution Manager for VARs Partners|/community [original link is broken];
Best regards,
Ruediger

Migration SAP SolMan 7 MSSQL 2008 R2 Enterprise Edition to MSSQL Standard Edition

Hello,
I try to migrate a databse on Windows MSSQL 2008 R2 ENTERPRISE EDITION to
MSSQL 2008 R2 STANDARD EDITION.
In the source system (MSSQL 2008 R2 ENTERPRISE EDITION) there is "table compression" and
"partitioning" active.
Unfortunately the MSSQL STANDARD EDITION doesn`t support these two features.
So a normal DB backup on the source system and restore in the destination system is not possible.
But the tables compression I can deactivte by the SQL script
SELECT DISTINCT ‘ALTER TABLE [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
FROM sys.partitions p
join sys.objects o
on p.object_id = o.object_id
WHERE o.TYPE = ‘u’
and data_compression_desc != ‘NONE’
UNION
SELECT ‘ALTER INDEX ALL ON [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
FROM sys.partitions p
join sys.objects o
on p.object_id = o.object_id
WHERE o.TYPE = ‘u’
and data_compression_desc != ‘NONE’
is there a way to undo or deactivate the the SQL table partitioning without data lost ?
Best regards
B.-D.

Hello Lydia Zhang,
thanks for your help.
For a few tables this will work.
Unfortunately I have an SAP system with thousands of tables and index`s .
With the SQL script:
SELECT
SCHEMA_NAME(t.schema_id) AS SchemaName
,OBJECT_NAME(i.object_id) AS ObjectName
,p.partition_number AS PartitionNumber
,fg.name AS Filegroup_Name
,rows AS 'Rows'
,au.total_pages AS 'TotalDataPages'
,CASE boundary_value_on_right
   WHEN 1 THEN 'less than'
   ELSE 'less than or equal to'
END AS 'Comparison'
,value AS 'ComparisonValue'
,p.data_compression_desc AS 'DataCompression'
,p.partition_id
FROM sys.partitions p
JOIN sys.indexes i ON p.object_id = i.object_id AND p.index_id = i.index_id
JOIN sys.partition_schemes ps ON ps.data_space_id = i.data_space_id
JOIN sys.partition_functions f ON f.function_id = ps.function_id
LEFT JOIN sys.partition_range_values rv ON f.function_id = rv.function_id AND p.partition_number = rv.boundary_id
JOIN sys.destination_data_spaces dds ON dds.partition_scheme_id = ps.data_space_id AND dds.destination_id = p.partition_number
JOIN sys.filegroups fg ON dds.data_space_id = fg.data_space_id
JOIN (SELECT container_id, sum(total_pages) as total_pages
       FROM sys.allocation_units
       GROUP BY container_id) AS au ON au.container_id = p.partition_id
JOIN sys.tables t ON p.object_id = t.object_id
WHERE i.index_id < 2
ORDER BY ObjectName,p.partition_number;
GO
Output:
SchemaName   ObjectName   PartitionNumber   Filegroup_Name   Rows   TotalDataPages   Comparison   ComparisonValue   DataCompression
partition_id
swp   /BI0/F0CCMARSH   1   PRIMARY   0   0   less than   NULL   NONE   72057613126729728
swp   /BI0/F0CCMAWDD1   1   PRIMARY   0   0   less than   NULL   NONE   72057613127516160
swp   /BI0/F0CCMAWDD2   1   PRIMARY   0   0   less than   NULL   NONE   72057613128237056
swp   /BI0/F0CCMAWDH1   1   PRIMARY   0   0   less than   NULL   NONE   72057613128957952
and so on
I got about 5000 tables .
Is there a way to delete all index on the partioned table an create a new with one script ?
Best regards
B.-D.

SOLMAN 3.2 LIS to SLD Migration

Are there any notes on this? We'd like to move from LIS to SLD. Other than needing the Java stack is there any other gotchya's?
M.
Message was edited by: Michael Brierley

Hi stefano
Try this link. Found it to be usefull info for us.
http://help.sap.com/saphelp_nw04s/helpdata/en/11/0dfe55e0c8fc4e910706a47ca6859b/content.htm

Error in installing Solman 4.0 SR2

Hi,
An Error occured during the installation of Solman 4.0 SR2 in import ABAP phase.
Sofware and Hardware configurartion:
Java 1.4.2_12
Database MSSQL 2005 SP2
Solution manager 4.0 SR2
Dual core 2.6 GHZ
2 gb ram
160gb hard drive
Plz find attached the sapinst.log file and import_monitor.log file.
Needfull help in this regard would be highly appreciated. Deserving points will be rewarded.
Best Regards
Omeir.
*import_monior.log*
INFO: 2007-09-21 01:21:36
Import Monitor is started.
CONFIG: 2007-09-21 01:21:36
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-09-21 01:21:36
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-09-21 01:21:36
List of packages with views: 'SAPVIEW'.
TRACE: 2007-09-21 01:21:36 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2007-09-21 01:21:36 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2007-09-21 01:21:36
Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2007-09-21 01:21:37
Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-09-21 01:21:37
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is started.
TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
INFO: 2007-09-21 01:25:22 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is successfully completed.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP1\DATA\SAPSSEXC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSEXC.TSK MSS -l SAPSSEXC.log
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPAPPL0.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL0.TSK MSS -l SAPAPPL0.log
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAPAPPL1.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL1.TSK MSS -l SAPAPPL1.log
TRACE: 2007-09-21 01:25:37 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2007-09-21 01:25:37 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2007-09-21 01:25:38 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
INFO: 2007-09-21 13:22:54
Import Monitor is started.
CONFIG: 2007-09-21 13:22:54
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-09-21 13:22:54
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-09-21 13:22:54
List of packages with views: 'SAPVIEW'.
TRACE: 2007-09-21 13:22:54 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2007-09-21 13:22:54 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2007-09-21 13:22:54
Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2007-09-21 13:22:58
Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-09-21 13:22:58
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL0.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
ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast' 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
ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSSEXC.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
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is started.
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is started.
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPAPPL2.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL2.TSK MSS -l SAPAPPL2.log
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is started.
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSRC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSRC.TSK MSS -l SAPSSRC.log
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPPOOL' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPPOOL.TSK MSS -l SAPPOOL.log
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPPOOL' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -loadprocedure fast
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSRC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -loadprocedure fast
TRACE: 2007-09-21 13:23:25 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -loadprocedure fast
INFO: 2007-09-21 13:24:19 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is successfully completed.
TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.
TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSPROT' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSPROT.TSK MSS -l SAPSPROT.log
TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast
INFO: 2007-09-21 13:25:38 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is successfully completed.
TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is started.
TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDOCU' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDOCU.TSK MSS -l SAPSDOCU.log
TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDOCU' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -loadprocedure fast
INFO: 2007-09-21 13:26:05 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is successfully completed.
TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is started.
TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLEXC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLEXC.TSK MSS -l SAPSLEXC.log
TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -loadprocedure fast
INFO: 2007-09-21 13:26:30 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is successfully completed.
TRACE: 2007-09-21 13:26:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is started.
TRACE: 2007-09-21 13:26:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPCLUST' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPCLUST.TSK MSS -l SAPCLUST.log
TRACE: 2007-09-21 13:26:56 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPCLUST' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -loadprocedure fast
INFO: 2007-09-21 13:27:12 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is successfully completed.
TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is started.
TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLOAD' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLOAD.TSK MSS -l SAPSLOAD.log
TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLOAD' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -loadprocedure fast
INFO: 2007-09-21 13:27:28 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is successfully completed.
INFO: 2007-09-21 13:27:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is successfully completed.
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is started.
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is started.
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDDIM' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDDIM.TSK MSS -l SAPDDIM.log
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDFACT' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDFACT.TSK MSS -l SAPDFACT.log
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDDIM' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -loadprocedure fast
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDFACT' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -loadprocedure fast
INFO: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is successfully completed.
INFO: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is successfully completed.
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is started.
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER.TSK MSS -l SAPUSER.log
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDODS' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDODS.TSK MSS -l SAPDODS.log
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -loadprocedure fast
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -loadprocedure fast
INFO: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is successfully completed.
INFO: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is successfully completed.
TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is started.
TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAP0000' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAP0000' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
INFO: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
INFO: 2007-09-21 13:34:56 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is successfully completed.
WARNING: 2007-09-21 13:35:24
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-09-21 13:35:24
3 error(s) during processing of packages.
INFO: 2007-09-21 13:35:24
Import Monitor is stopped.
INFO: 2007-09-21 13:38:06
Import Monitor is started.
CONFIG: 2007-09-21 13:38:06
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-09-21 13:38:06
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-09-21 13:38:06
List of packages with views: 'SAPVIEW'.
TRACE: 2007-09-21 13:38:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2007-09-21 13:38:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2007-09-21 13:38:06
Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2007-09-21 13:38:06
Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-09-21 13:38:06
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
ERROR: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSSEXC.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
ERROR: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast' 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
ERROR: 2007-09-21 13:38:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL0.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
WARNING: 2007-09-21 13:38:36
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-09-21 13:38:36
3 error(s) during processing of packages.
INFO: 2007-09-21 13:38:36
Import Monitor is stopped.
sapinst.log
INFO 2007-09-21 13:22:26
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.2.xml'.
INFO 2007-09-21 13:22:27
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.3.xml'.
INFO 2007-09-21 13:22:29
Execute step
Component W2K_ServicePack_Check|ind|ind|ind|ind
Preprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO 2007-09-21 13:22:40
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.2.xml'.
INFO 2007-09-21 13:22:41
Execute step runMigrationMonitor of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0.
INFO 2007-09-21 13:22:51
Switched to user: prdadm.
INFO 2007-09-21 13:22:51
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\import_monitor.java.log.
INFO 2007-09-21 13:22:51
Switched to user: prdadm.
INFO 2007-09-21 13:22:51
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS.
INFO 2007-09-21 13:22:51
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING 2007-09-21 13:35:24
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 16, completed 1, failed 0, total 18.
Import Monitor jobs: running 2, waiting 15, completed 1, failed 0, total 18.
Import Monitor jobs: running 3, waiting 14, completed 1, failed 0, total 18.
Loading of 'SAPAPPL0' import package: ERROR
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 1, waiting 14, completed 1, failed 2, total 18.
Import Monitor jobs: running 0, waiting 14, completed 1, failed 3, total 18.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 0, waiting 14, completed 1, failed 3, total 18.
Import Monitor jobs: running 1, waiting 13, completed 1, failed 3, total 18.
Import Monitor jobs: running 2, waiting 12, completed 1, failed 3, total 18.
Import Monitor jobs: running 3, waiting 11, completed 1, failed 3, total 18.
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 2, failed 3, total 18.
Import Monitor jobs: running 3, waiting 10, completed 2, failed 3, total 18.
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 3, failed 3, total 18.
Import Monitor jobs: running 3, waiting 9, completed 3, failed 3, total 18.
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 4, failed 3, total 18.
Import Monitor jobs: running 3, waiting 8, completed 4, failed 3, total 18.
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 5, failed 3, total 18.
Import Monitor jobs: running 3, waiting 7, completed 5, failed 3, total 18.
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 6, failed 3, total 18.
Import Monitor jobs: running 3, waiting 6, completed 6, failed 3, total 18.
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 7, failed 3, total 18.
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 1, waiting 6, completed 8, failed 3, total 18.
Import Monitor jobs: running 2, waiting 5, completed 8, failed 3, total 18.
Import Monitor jobs: running 3, waiting 4, completed 8, failed 3, total 18.
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 9, failed 3, total 18.
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 1, waiting 4, completed 10, failed 3, total 18.
Import Monitor jobs: running 2, waiting 3, completed 10, failed 3, total 18.
Import Monitor jobs: running 3, waiting 2, completed 10, failed 3, total 18.
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 11, failed 3, total 18.
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 1, waiting 2, completed 12, failed 3, total 18.
Import Monitor jobs: running 2, waiting 1, completed 12, failed 3, total 18.
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 13, failed 3, total 18.
Loading of 'SAPAPPL2' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 14, failed 3, total 18.
ERROR 2007-09-21 13:35:24
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-09-21 13:35:24
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
INFO 2007-09-21 13:38:06
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
INFO 2007-09-21 13:38:06
Switched to user: prdadm.
INFO 2007-09-21 13:38:06
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\import_monitor.java.log.
INFO 2007-09-21 13:38:06
Switched to user: prdadm.
INFO 2007-09-21 13:38:06
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS.
INFO 2007-09-21 13:38:06
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING 2007-09-21 13:38:36
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 3, completed 14, failed 0, total 18.
Import Monitor jobs: running 2, waiting 2, completed 14, failed 0, total 18.
Import Monitor jobs: running 3, waiting 1, completed 14, failed 0, total 18.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 14, failed 1, total 18.
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 14, failed 2, total 18.
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 14, failed 3, total 18.
ERROR 2007-09-21 13:38:36
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-09-21 13:38:36
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
INFO 2007-09-21 13:38:40
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
Edited by: mohammed omeir on Dec 31, 2007 2:30 PM

Hi Markus,
Its says a previous run may not have finished clearly.
What i need to do now?
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070921132313
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Sep 1 2006 00:38:35
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
Hi Markus,
Its says a previous
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist
             a previous run may not have been finished cleanly
             file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070921132321
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070921133807
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Sep 1 2006 00:38:35
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist
             a previous run may not have been finished cleanly
             file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070921133807

Migrating an SAP 4.7x110 system on W2003 32-bit to a 64-bit host (x86_64)

We want to migrate an SAP 4.7x110 system on Windows Server 2003 32-bit to a 64-bit host (x86_64). Afterwards we want to upgrade the system to ECC 6.0.
According to PAM, 4.7x110 is not supported on Windows 64-bit.
According to note 960769,
"After the migration to the 64-bit hardware, your SAP system may have a status that is not supported by SAP for productive use (see Note 814834). You may need to upgrade to a new SAP release. In this exceptional circumstance, SAP offers support for the duration of the upgrade. Note that SAP does not support a longer, more productive use of such a system for the period after the migration and before the upgrade....
...We generally recommend to use SQL Server 2005 (64-bit) for the productive use on x86_64. However, the 32-bit operation of SQL Server 2000 on Windows x86_64 64-Bit (supported by Microsoft) is also supported by SAP...
...The following table illustrates which OS/DB combination supports each SAP release in the target system.
Source System   Target System (Kernel, DB Software)     Support Comment
3.1I   3.1I 32-bit, MSSQL 2000 32-bit    only for upgrade (a,c)
4.0B   4.0B 32-bit, MSSQL 2000 32-bit    only for upgrade (c)
4.5B    4.5B 32-bit, MSSQL 2000 32-bit    only for upgrade (c)
4.6C   4.6D 32-bit, MSSQL 2005 64-bit     productive (b)
620   640 64-bit, MSSQL 2005 64-bit    productive (b)
640   640 64-bit, MSSQL 2005 64-bit    productive (b)
700   700 64-bit, MSSQL 2005 64-bit    productive (b) "
According to note 814834,
"SAP supports the x86_64 platform on Windows 2003 Server SP1 x64 for kernel 4.6D and kernel 6.40 and higher. ... For product versions based on kernel 6.40 and higher, only 64-bit operation is supported."
According to note 905634, about SQL Server 2005 support (where a mention to R3E 4.7 x110 is missing)
"Supported SAP products based on SAP_BASIS 6.20 and SAP_BASIS 6.40
Product Windows platforms
BW 3.10 x86, IA-64
SCM 4.0 x86, IA-64
EBP/CRM 4.0 x86, IA-64
ECC 5.0 SR1 x86, IA-64, x64
NetWeaver'04 SR1 x86, IA-64, x64
SCM 4.1 x86, IA-64, x64
SRM 4.0 SR1 x86, IA-64, x64
CRM 4.0 SR1 x86, IA-64, x64
R3E 4.7 x200 SR1 x86, IA-64, x64
SolMan 3.2 SR1 x86, IA-64, x64 "
+//////////////////////+//
According to all this information, may I move our 4.7x110 system onto a Windows Server 2003 SP1 64-bit, SQL Server 2005 64-bit, and after that we would upgrade to ECC 6.0?
Thanks !!!
Eva
Edited by: Eva Verdaguer on Jul 25, 2008 12:41 PM

Sorry, I forgot posting the SAP answer, which is also "Yes":
30.07.2008 - 16:19:00 CET - Respuesta by SAP
Dear Eva,
Yes, you can move to the 64 bit platform with SQL Server 2005 according
to note 960769.
Information in note 905634 means there is no installation DVD for
release 47x110 for SQL Server 2005. So it is not possible to do a fresh
installation of 47x110 except if you follow the workaround of note
899111 (for x64).
Best Regards,
Manuel García Guardiola
SAP Active Global Support - Netweaver Web Application Server
****************************************************************+
Thanks very much for your message, anyway.
Regards !!
Eva

"Table VSEOPARENT is not in the database" after SolMan system copy to x64

Hi SDNners,
We've just completed a system copy of our SolMan 3.1 system onto a new
(Xeon x64 based) server. This system copy is part of the process of
moving SolMan 3.1 from an old server onto 64bit hardware and then
upgrading it to SolMan v4 and Oracle 10G.
Although the system appears to start properly in the MMC, we are unable
to log into the system through SAPGUI - we get a SYNTAX_ERROR window
instead of a logon screen.
I've checked the SysLog from within the MMC and noticed a number of
errors stating:
Database: Table VSEOPARENT is not in the database
Database: Table VSEOIFIMPL is not in the database
Database: Table VSEOIFCOMP is not in the database
I tried running SQL command 'select * from "SAPSOL"."VSEOPARENT"; and
it confirmed that the table didn't exist. I then ran the same command
on the source SolMan system and it showed that VSEOPARENT DID exist. I
don't understand how these VSEO* tables could have gone missing between
the source and target systems.
I've searched OSS for VSEO* and cannot find anything. Please help!
Thanks,
Arwel.

We have 640 kernel, ECC 5.0 and BASIS patch 23.
For me the problem was with SAPVIEW table wasnt imported from source to target becuase SAPVIEW.STR file was 0 byte. STR files gets created in export preparation phase.
It did happen because on source side master DVD, there was no option for export preparation. I had only option for tablesplit and export db.
I did use ECC 5.0 SR2 Master DVD which had option for export preparation phase and that created SAPVIEW.STR file.
Using migration monitor I did re-export and re-import and this time all views are imported in target.
Regards,
Mamadi.

OS/ DB Migration Solman 4.0

Similar Messages

Maybe you are looking for