Migrating to DB6 v9.5

Hello,
i want to migrate DB release v8.2 FP12 to v9.5.
If i follow SAP Note 101809 - DB6:Supported Fix Packs for UDB i can find that currently supported software level for DB2 is 9.5GA with special_18161.
SAP Note 1079000 Number IV explains the need for Fixpack 1 to migrate Unicode Databases.
Does this meen that the Migration to v9.5 is currently not supported?
Thanks,
Tino

Hello Tino,
we have several reports from customers who faced the problem described in APAR IZ14827 during the migration from DB2 UDB 8.2 to DB2 9.5 GA. For IBM the problem is solved with Fix Pack 1 which is available from IBM but is still validated at SAP.
I see two options here.
Option 1:
Before you migrate
- Ensure that you have an appropriate backup (you should have this anyway...).
- Check if table sysibm.syscolchecks has entries. To the best of our knowledge the problem does not appear if this table is empty.
Option 2:
If you want to be 100% sure: request Fix Pack 1 for DB2 9.5 from SAP Support.
Regards,
Johannes

Similar Messages

The system executes DB6-specific jobs on a non-DB6 system.

Hi experts,
Our R3 system is ECC6 and is running on oracle.
The below background jobs are running in our system.
CCMS_COLL_DB:RSDBPREV
CCMS_COLL_DB:RSDB_DAILY
CCMS_COLL_DB:RSDB_PAR
CCMS_COLL_DB:RSDB_TDB
CCMS_COLL_DB:RSDB_WDB
As per note 1167933, These jobs are provided for the monitoring of DB6 systems in a heterogenous system landscape. They are also scheduled if there are no DB6 systems to be monitored.
Could anybody please confirm if I can go ahead and delete this jobs as they do not seem to required in sap system with oracle database?
Thanks and Regards,
Amit Jana.

Was this system migrated from DB6? Did you use SM36 - Default Jobs - to schedule them?
Markus

SAP DEV migration process error

Hi all,
SAP DEV migration process error.Error Details:
Source system
SAP ECC6.0 SR2
DB: DB2.9.1.4
OS: AIX 5.3
Target system
SAP ECC6.0 SR2
DB: DB2.9.1.4
OS: SUSE 10 64 Bit
ERROR 2008-11-13 07:41:06
 CJSlibModule::writeError_impl()
CJS-30023 Process call '/usr/sap/DEV/SYS/exe/run/dipgntab -rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT' exits with error code 126. For details see log file(s) dipgntab.log.
TRACE [iaxxejsbas.hpp:460]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2008-11-13 07:41:06 [iaxxgenimp.cpp:731]
 showDialog()
FCO-00011 The step adjustNametab with step key |NW_Doublestack_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_Postload|ind|ind|ind|ind|10|0|NW_Postload_DB6|ind|ind|ind|ind|5|0|adjustNametab was executed with status ERROR .
TRACE [iaxxgenimp.cpp:719]
 showDialog()
<html><head></head><body>An error occurred while processing service SAP ERP 2005 Support Release 2 > Additional Software Life-Cycle Tasks > System Copy > IBM DB2 for Linux, UNIX, and Windows > Target System > Central System > Based on AS ABAP and AS Java > Central System Installation. You may now<ul> <li>press Retry to repeat the current step.</li> <li>press the View Log button to get more information about the error.</li> <li>stop the task and continue with it later.</li></ul>Log files are written to /tmp/sapinst_instdir/ERP/LM/COPY/DB6/SYSTEM/CENTRAL/AS/.</body></html>
TRACE [iaxxgenimp.cpp:1155]
 showDialog()
waiting for an answer from gui
dipgntab.log
/usr/sap/DEV/SYS/exe/run/dipgntab: /usr/sap/DEV/SYS/exe/run/dipgntab: cannot execute binary file

Hi,
1. please check if /usr/sap/DEV/SYS/exe/run/dipgntab exists or not ?
2. Does it have executable permissions?
3. Does your user have authorization to execute it?
4. if you executed dipgntab manually, does it work ?
Regards,
Vincent

Homogeneous System Copy for 4.5B/DB6/W2K ?

I'm looking for the documentation on doing a homogeneous system copy for an R/3 4.5B System for a client. They are running DB6 on Windows 2000. I've searched Service Marketplace and can only find doc's back as far as 4.6C. I can't find the one for 4.5B.
The client is looking to migrate the current system to new hardware and then subsequently upgrade to ECC 6.00, but that part is off a piece. The first part is to migrate the system to the new hardware in order to solve some space and performance issues.
If anyone can point me to the docs, or has a copy on their local machines they can send me, then please let me know.
Thanks.

I suggest you open an OSS call under BC-INS and ask for the guide there.
Since 4.5B is out of maintenance and you/your customer has (hopefully) an extended maintenance contract for that version they will give you that guide.
If you do NOT have them, you might be pretty lost in case of a problem, if you have the guide or not...
Markus

Migration unicode Linux to unicode AIX

Not sure if this is the right forum.
I am trying to run heterogeneous system copy of Unicode SolMan 7 Enh 1 system from Source Linux target AIX.
Having problems with R3load export.
/usr/sap/SID/SYS/exe/run/R3load -e D010INC.cmd -datacodepage 4102 -l D010INC.log
-stop_on_error
(DB) INFO: connected to DB
(DB) INFO: Export without hintfile
(CNV) ERROR: There shall be only one Unicode in a database
I THINK I have to do a Unicode migration to get from Linux Unicode little endian
to AIX Unicode big endianu2026
Is there such a thing as Unicode to Unicode migration documentation anywhere?
Does current Unicode Migration document have Unicode source section?
This system already had Unicode migration at SM 7.0 level...
Does this mean UMG tables need reset?
Ken

TRACE 2010-08-10 16:25:53.385 [syuxctask.cpp:1382]
 CSyTaskImpl::start(bool)
A child process has been started. Pid = 20731
ERROR 2010-08-10 16:25:53.421 [sixxcstepexecute.cpp:950]
FCO-00011 The step runMigrationMonitor with step key |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Export|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
TRACE 2010-08-10 16:25:53.440 [iaxxgenimp.cpp:752]
 CGuiEngineImp::showMessageBox
<html> <head> </head> <body> An error occurred while processing option SAP Solution Manager 7.0 EhP1 > Software Life-Cycle Options > System Copy > IBM DB2 for Linux, UNIX, and Windows > Source System Export > Central System > Based on AS ABAP and AS Java > Database and Central Instance Export. You can now: <ul> <li> Choose Retry to repeat the current step. </li> <li> Choose View Log to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> Log files are written to /nfs/@soulman-t/cd/tmpdir/sapinst_instdir/SOLMAN/LM/COPY/DB6/EXP/CENTRAL/AS/EXP. </body></html>
export_monitor.java.log -
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04)
Export Monitor jobs: running 1, waiting 55, completed 0, failed 0, total 56.
Export Monitor jobs: running 2, waiting 54, completed 0, failed 0, total 56.
Export Monitor jobs: running 3, waiting 53, completed 0, failed 0, total 56.
Export Monitor jobs: running 3, waiting 52, completed 1, failed 0, total 56.
Export Monitor jobs: running 3, waiting 51, completed 2, failed 0, total 56.
Unloading of 'BALDAT' export package: ERROR
Export Monitor jobs: running 1, waiting 51, completed 2, failed 2, total 56.
Unloading of 'BDLDATCOL' export package: ERROR
Export Monitor jobs: running 0, waiting 51, completed 2, failed 3, total 56.
Unloading of 'D010INC' export package: ERROR
Export Monitor jobs: running 0, waiting 51, completed 2, failed 3, total 56.
Export Monitor jobs: running 1, waiting 50, completed 2, failed 3, total 56.
Export Monitor jobs: running 2, waiting 49, completed 2, failed 3, total 56.
Export Monitor jobs: running 3, waiting 48, completed 2, failed 3, total 56.
Unloading of 'DOKCLU' export package: ERROR
Export Monitor jobs: running 2, waiting 48, completed 2, failed 4, total 56.
Unloading of 'DSVASREPODOCS' export package: ERROR
Export Monitor jobs: running 1, waiting 48, completed 2, failed 5, total 56.
Unloading of 'D010TAB' export package: ERROR
Export Monitor jobs: running 0, waiting 48, completed 2, failed 6, total 56.
Export Monitor jobs: running 1, waiting 47, completed 2, failed 6, total 56.
Export Monitor jobs: running 2, waiting 46, completed 2, failed 6, total 56.
Export Monitor jobs: running 3, waiting 45, completed 2, failed 6, total 56.
Unloading of 'DSVASRESULTSGEN' export package: ERROR
Export Monitor jobs: running 2, waiting 45, completed 2, failed 7, total 56.
Unloading of 'DSVASRESULTSATTR' export package: ERROR
Export Monitor jobs: running 1, waiting 45, completed 2, failed 8, total 56.
Unloading of 'DSVASTEXTCLUSTER' export package: ERROR
Export Monitor jobs: running 0, waiting 45, completed 2, failed 9, total 56.
Export Monitor jobs: running 1, waiting 44, completed 2, failed 9, total 56.
Export Monitor jobs: running 2, waiting 43, completed 2, failed 9, total 56.
Export Monitor jobs: running 3, waiting 42, completed 2, failed 9, total 56.
Unloading of 'DYNPSOURCE' export package: ERROR
Export Monitor jobs: running 1, waiting 42, completed 2, failed 11, total 56.
Unloading of 'E071K' export package: ERROR
Export Monitor jobs: running 1, waiting 42, completed 2, failed 11, total 56.
Unloading of 'OCSCMPLOBJ' export package: ERROR
Export Monitor jobs: running 0, waiting 42, completed 2, failed 12, total 56.
Export Monitor jobs: running 1, waiting 41, completed 2, failed 12, total 56.
Export Monitor jobs: running 2, waiting 40, completed 2, failed 12, total 56.
Export Monitor jobs: running 3, waiting 39, completed 2, failed 12, total 56.
Unloading of 'RSDDSTATEVDATA' export package: ERROR
Export Monitor jobs: running 2, waiting 39, completed 2, failed 13, total 56.
Unloading of 'REPOTEXT' export package: ERROR
Export Monitor jobs: running 1, waiting 39, completed 2, failed 14, total 56.
Unloading of 'REPOSRC' export package: ERROR
Export Monitor jobs: running 0, waiting 39, completed 2, failed 15, total 56.
Export Monitor jobs: running 1, waiting 38, completed 2, failed 15, total 56.
Export Monitor jobs: running 2, waiting 37, completed 2, failed 15, total 56.
Export Monitor jobs: running 3, waiting 36, completed 2, failed 15, total 56.
Unloading of 'SACONT01' export package: ERROR
Unloading of 'SAPAPPL0_1' export package: ERROR
Export Monitor jobs: running 1, waiting 36, completed 2, failed 17, total 56.
Export Monitor jobs: running 1, waiting 36, completed 2, failed 17, total 56.
Unloading of 'RSDDSTATLOGGING' export package: ERROR
Export Monitor jobs: running 0, waiting 36, completed 2, failed 18, total 56.
Export Monitor jobs: running 1, waiting 35, completed 2, failed 18, total 56.
Export Monitor jobs: running 2, waiting 34, completed 2, failed 18, total 56.
Export Monitor jobs: running 3, waiting 33, completed 2, failed 18, total 56.
Unloading of 'SAPAPPL0_4' export package: ERROR
Export Monitor jobs: running 2, waiting 33, completed 2, failed 19, total 56.
Unloading of 'SAPAPPL0_2' export package: ERROR
Export Monitor jobs: running 1, waiting 33, completed 2, failed 20, total 56.
Unloading of 'SAPAPPL0_3' export package: ERROR
Export Monitor jobs: running 0, waiting 33, completed 2, failed 21, total 56.
Export Monitor jobs: running 1, waiting 32, completed 2, failed 21, total 56.
Export Monitor jobs: running 2, waiting 31, completed 2, failed 21, total 56.
Export Monitor jobs: running 3, waiting 30, completed 2, failed 21, total 56.
Unloading of 'SAPAPPL0_5' export package: ERROR
Export Monitor jobs: running 2, waiting 30, completed 2, failed 22, total 56.
Unloading of 'SAPAPPL1_1' export package: ERROR
Export Monitor jobs: running 1, waiting 30, completed 2, failed 23, total 56.
Unloading of 'SAPAPPL1_2' export package: ERROR
Export Monitor jobs: running 0, waiting 30, completed 2, failed 24, total 56.
Export Monitor jobs: running 1, waiting 29, completed 2, failed 24, total 56.
Export Monitor jobs: running 2, waiting 28, completed 2, failed 24, total 56.
Export Monitor jobs: running 3, waiting 27, completed 2, failed 24, total 56.
Unloading of 'SAPAPPL1_3' export package: ERROR
Export Monitor jobs: running 2, waiting 27, completed 2, failed 25, total 56.
Unloading of 'SAPAPPL2_1' export package: ERROR
Export Monitor jobs: running 1, waiting 27, completed 2, failed 26, total 56.
Unloading of 'SAPAPPL2_2' export package: ERROR
Export Monitor jobs: running 0, waiting 27, completed 2, failed 27, total 56.
Export Monitor jobs: running 1, waiting 26, completed 2, failed 27, total 56.
Export Monitor jobs: running 2, waiting 25, completed 2, failed 27, total 56.
Export Monitor jobs: running 3, waiting 24, completed 2, failed 27, total 56.
Unloading of 'SAPAPPL2_4' export package: ERROR
Export Monitor jobs: running 2, waiting 24, completed 2, failed 28, total 56.
Unloading of 'SAPAPPL2_3' export package: ERROR
Unloading of 'SAPCLUST' export package: ERROR
Export Monitor jobs: running 0, waiting 24, completed 2, failed 30, total 56.
Export Monitor jobs: running 0, waiting 24, completed 2, failed 30, total 56.
Export Monitor jobs: running 1, waiting 23, completed 2, failed 30, total 56.
Export Monitor jobs: running 2, waiting 22, completed 2, failed 30, total 56.
Export Monitor jobs: running 3, waiting 21, completed 2, failed 30, total 56.
Unloading of 'SAPDFACT' export package: ERROR
Export Monitor jobs: running 2, waiting 21, completed 2, failed 31, total 56.
Unloading of 'SAPDODS' export package: ERROR
Unloading of 'SAPDDIM' export package: ERROR
Export Monitor jobs: running 0, waiting 21, completed 2, failed 33, total 56.
Export Monitor jobs: running 0, waiting 21, completed 2, failed 33, total 56.
Export Monitor jobs: running 1, waiting 20, completed 2, failed 33, total 56.
Export Monitor jobs: running 2, waiting 19, completed 2, failed 33, total 56.
Export Monitor jobs: running 3, waiting 18, completed 2, failed 33, total 56.
Unloading of 'SAPPOOL' export package: ERROR
Export Monitor jobs: running 2, waiting 18, completed 2, failed 34, total 56.
Unloading of 'SAPSDIC' export package: ERROR
Export Monitor jobs: running 1, waiting 18, completed 2, failed 35, total 56.
Unloading of 'SAPNTAB' export package: ERROR
Export Monitor jobs: running 0, waiting 18, completed 2, failed 36, total 56.
Export Monitor jobs: running 1, waiting 17, completed 2, failed 36, total 56.
Export Monitor jobs: running 2, waiting 16, completed 2, failed 36, total 56.
Export Monitor jobs: running 3, waiting 15, completed 2, failed 36, total 56.
Unloading of 'SAPSDOCU' export package: ERROR
Export Monitor jobs: running 2, waiting 15, completed 2, failed 37, total 56.
Unloading of 'SAPSLDEF' export package: ERROR
Export Monitor jobs: running 1, waiting 15, completed 2, failed 38, total 56.
Unloading of 'SAPSLEXC' export package: ERROR
Export Monitor jobs: running 0, waiting 15, completed 2, failed 39, total 56.
Export Monitor jobs: running 1, waiting 14, completed 2, failed 39, total 56.
Export Monitor jobs: running 2, waiting 13, completed 2, failed 39, total 56.
Export Monitor jobs: running 3, waiting 12, completed 2, failed 39, total 56.
Unloading of 'SAPSLOAD' export package: ERROR
Export Monitor jobs: running 2, waiting 12, completed 2, failed 40, total 56.
Unloading of 'SAPSSEXC_1' export package: ERROR
Export Monitor jobs: running 1, waiting 12, completed 2, failed 41, total 56.
Unloading of 'SAPSPROT' export package: ERROR
Export Monitor jobs: running 0, waiting 12, completed 2, failed 42, total 56.
Export Monitor jobs: running 1, waiting 11, completed 2, failed 42, total 56.
Export Monitor jobs: running 2, waiting 10, completed 2, failed 42, total 56.
Export Monitor jobs: running 3, waiting 9, completed 2, failed 42, total 56.
Unloading of 'SAPUSER' export package: ERROR
Export Monitor jobs: running 2, waiting 9, completed 2, failed 43, total 56.
Unloading of 'SAPSSEXC_2' export package: ERROR
Export Monitor jobs: running 1, waiting 9, completed 2, failed 44, total 56.
Unloading of 'SAPSSRC' export package: ERROR
Export Monitor jobs: running 0, waiting 9, completed 2, failed 45, total 56.
Export Monitor jobs: running 1, waiting 8, completed 2, failed 45, total 56.
Export Monitor jobs: running 2, waiting 7, completed 2, failed 45, total 56.
Export Monitor jobs: running 3, waiting 6, completed 2, failed 45, total 56.
Unloading of 'SAPUSER1' export package: ERROR
Unloading of 'SASACONT1' export package: ERROR
Export Monitor jobs: running 1, waiting 6, completed 2, failed 47, total 56.
Export Monitor jobs: running 1, waiting 6, completed 2, failed 47, total 56.
Unloading of 'SEOCOMPODF' export package: ERROR
Export Monitor jobs: running 0, waiting 6, completed 2, failed 48, total 56.
Export Monitor jobs: running 1, waiting 5, completed 2, failed 48, total 56.
Export Monitor jobs: running 2, waiting 4, completed 2, failed 48, total 56.
Export Monitor jobs: running 3, waiting 3, completed 2, failed 48, total 56.
Unloading of 'SMD_HASH_TABLE' export package: ERROR
Export Monitor jobs: running 1, waiting 3, completed 2, failed 50, total 56.
Unloading of 'TST03' export package: ERROR
Export Monitor jobs: running 1, waiting 3, completed 2, failed 50, total 56.
Unloading of 'SOFFCONT1' export package: ERROR
Export Monitor jobs: running 0, waiting 3, completed 2, failed 51, total 56.
Export Monitor jobs: running 1, waiting 2, completed 2, failed 51, total 56.
Export Monitor jobs: running 2, waiting 1, completed 2, failed 51, total 56.
Export Monitor jobs: running 3, waiting 0, completed 2, failed 51, total 56.
Unloading of '_BI0_F0CCMARSH' export package: ERROR
Export Monitor jobs: running 2, waiting 0, completed 2, failed 52, total 56.
Unloading of '_BI0_F0CCMSAEXE' export package: ERROR
Export Monitor jobs: running 1, waiting 0, completed 2, failed 53, total 56.
Unloading of 'WDR_ADP_CONST_MP' export package: ERROR
Export Monitor jobs: running 0, waiting 0, completed 2, failed 54, total 56.
sample failing package log D010INC.log (they all look the same)
/usr/sap/SSM/SYS/exe/run/R3load: START OF LOG: 20100810161653
/usr/sap/SSM/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/SSM/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled May 22 2010 00:12:41
/usr/sap/SSM/SYS/exe/run/R3load -ctf E /nfs/@soulman-t/cd/export/ABAP/DATA/D010INC.STR /nfs/@soulman-t/cd/export/ABAP/DB/DDLDB6_LRG.TPL D010INC.TSK DB6 -l D010INC.log
(RTF) ########## WARNING ###########
 Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
/usr/sap/SSM/SYS/exe/run/R3load: job completed
/usr/sap/SSM/SYS/exe/run/R3load: END OF LOG: 20100810161653
/usr/sap/SSM/SYS/exe/run/R3load: START OF LOG: 20100810161653
/usr/sap/SSM/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/SSM/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled May 22 2010 00:12:41
/usr/sap/SSM/SYS/exe/run/R3load -e D010INC.cmd -datacodepage 4102 -l D010INC.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: Export without hintfile
(CNV) ERROR: There shall be only one Unicode in a database
/usr/sap/SSM/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/SSM/SYS/exe/run/R3load: END OF LOG: 20100810161655
end of logs -
Ken

Procedure for becoming certified for OS/DB migrations?

Hi,
Can someone please tell me how one can go about becoming certified for OS/DB migrations?... ie is there a specific course and what are the pre-requisites?
Thanks
Sharon
PS: We are currently on 4.6C and looking to migrate to another O/S.

All complete now.
There isn't a SAP suported method of migrating an APO 30A system, just some generic migration info.
I used a combo of the DB6 migration stuff, standard migration utilities and oracle exp/imp.
All worked without a hitch.

Migration doubt

Hello All,
I am doing the migration and during the import i had selected "Start Migration Monitor Manually".
I had set all the required parameters in the "import_monitor_cmd.properties" file and started the import.
All my import was sucessufully except one package "SAPAPPL2_1"
In which i got the following error in the SAPAPPL2_1.log file
(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 26, table "CSMCLSMAP"
(DB) INFO: disconnected from DB
After that i set one more parameter in the "import_monitor_cmd.properties" file that is
"loadArgs=-stop_on_error -loadprocedure fast LOAD"
And then the import of this table was sucesufull
Can Any one explain what the parameter "loadprocedure fast LOAD" means and how did the table got imported successfully.
And why only one package required this parameter and not all packages.
Regards
Anthony

> I am doing the migration and during the import i had selected "Start Migration Monitor Manually".
"the migration" means what? What are you migrating from where to where?
> ********************************
> (IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
> rc = 26, table "CSMCLSMAP"
> (DB) INFO: disconnected from DB
> ************************************
That error means, that a LOB could not be imported.
> After that i set one more parameter in the "import_monitor_cmd.properties" file that is
>
> "loadArgs=-stop_on_error -loadprocedure fast LOAD"
Where did you get that information?
> And then the import of this table was sucesufull
>
> Can Any one explain what the parameter "loadprocedure fast LOAD" means and how did the table got imported successfully.
> And why only one package required this parameter and not all packages.
The "-loadprocedure" options are database dependent, I assume you're on DB2 LUW, right? Since you didn't give any other information what you are doing all I can do is to point you to
Note 1058437 - DB6: R3load options for compact installation with DB2 9
which explains the different options.
Markus

DB6 backup to tape

I'm new to DB6. We have just migrated our SAP ECC6 sytem from Oracle 10.2 to DB2 v9.1(FP3).
If I try to backup to tape, I get the following message whether the tape is blank or not:
sapdev:db2hsd 4> db2 backup database HSD online to /dev/rmt0.1
SQL2031W Warning! Please mount the target or source media on device
"/dev/rmt0.1".
Do you want to continue(c), terminate this device only(d), abort the utility(t) ? (c/d/t) c
SQL2059W A device full warning was encountered on device "/dev/rmt0.1".
Do you want to continue(c), terminate this device only(d), abort the utility(t) ? (c/d/t)
If I backup to disk I have no problem.If I look @ db2diag.log, I see the following information:
2008-08-08-13.10.38.537853+120 E7613028A695       LEVEL: Error
PID     : 1540336              TID : 1           PROC : db2med.1442010.0 0
INSTANCE: db2hsd               NODE : 000
FUNCTION: DB2 UDB, oper system services, sqlowrite, probe:60
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
          DIA8312C Disk was full.
DATA #1 : String, 205 bytes
EINVAL from write() does not mean a real disk full condition.
Possible reasons :
1. Invalid parameters to the API.
2. The file size / offset specified is > 2G but the file system
   does not support > 2G.
DATA #2 : File descriptor, 8 bytes
12884902016
DATA #3 : unsigned integer, 8 bytes
12783616
DATA #4 : File Offset, 8 bytes
-1
The sytem is definitely seeing the tape drive, because if I use the following command, it works:
db2tapemgr DB HSP DOUBLE STORE ON /dev/rmt0.1 FORCE
My one concern, with the above command is that I have to use the force option.
When the system was still on Oracle, we used brbackup and brarchive without a problem.
Is there something else I need to configure to see the tape drive "properly"?

Hello Jean-Jacques,
There is a restriction on the number of fixed block sizes that can be used when backing up. This restriction exists because DB2 writes out the backup image header as a 4-KB block. The only fixed block sizes DB2 supports are 512, 1024, 2048, and 4096 bytes. If you are using a fixed block size, you can specify any backup buffer size. However, you might find that your backup operation will not complete successfully if the fixed block size is not one of the sizes that DB2 supports:
[http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/c0006201.htm]
There is a SAP DBA Guide: DB2 for Linux, UNIX, and Windows on SAP Marketplace (Installation & Upgrade Guides -> SAP NetWeaver -> SAP NetWeaver 7.0 2004s (if this is your system's version) -> Operations, then choose Database-Specific Guides -> "SAP DBA Guide: DB2 for Linux, UNIX, and Windows", which has extensive session on how to setup your tape drives to work with db2 backup.
As well, you can check out OSS Note 141872 that talks about a similar problem.
I hope it helps.
Regards,

Invalid Migration key

Dear expert
I am import sap system through system copy methored
during starting of ABAP Import phase it's prompt me to enter Migration key I gave it but it say's Invalid
/usr/sap/DEV/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/DEV/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140301123959
/usr/sap/DEV/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20140301125743
/usr/sap/DEV/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/740_REL/src/R3ld/R3load/R3ldmain.c#2 $ SAP
/usr/sap/DEV/SYS/exe/uc/rs6000_64/R3load: version R7.40/V1.7 [UNICODE]
Compiled Apr 10 2013 20:36:43
/usr/sap/DEV/SYS/exe/uc/rs6000_64/R3load -dbcodepage 4102 -i test_MIGKEY.cmd -l test_MIGKEY.log -K 1gQgf5M50Dv01eqtfaQy3A96
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(GSI) INFO: dbname   = "DEV20140301090313                                                                                                               "
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "ERPDEV                                                          "
(GSI) INFO: sysname = "AIX"
(GSI) INFO: nodename = "ERPDEV"
(GSI) INFO: release = "1"
(GSI) INFO: version = "7"
(GSI) INFO: machine = "000D94DBD400"
(VK) INFO: installation number = "0020599121"
(VK) ERROR: invalid migration key
/usr/sap/DEV/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/DEV/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140301125743
source IBM DB2 for UNIX and Windows
target oracle
regards

Thanks all for support and guidance
following is the source system SAPAPPL0.log information
_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
/usr/sap/C42/DVEBMGS10/exe/R3load: version R7.40/V1.8 [UNICODE]
Compiled Jul 23 2013 21:07:34
/usr/sap/C42/DVEBMGS10/exe/R3load -e SAPAPPL0_1_1.cmd -datacodepage 4102 -l SAPAPPL0_1_1.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: Export without hintfile
(GSI) INFO: dbname   = "C42                                                                                                                             "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "AIX"
(GSI) INFO: nodename = "slcmin"
(GSI) INFO: release = "1"
(GSI) INFO: version = "6"
(GSI) INFO: machine = "000F5D41D900"
(GSI) INFO: instno   = "0020599121"
I am unable to understand why (GSI) INFO: hostname = "UNKNOWN   "
as per sap note 1519000 - ERROR: invalid migration key
" In the installation directory, a MIGKEY.log or test_MIGKEY.log is written at the same time. If the entry
(VK) ERROR: invalid migration key
is to be found here at the end of the log file, the migration key is incorrect. In this case, you must ensure that you have generated the migration key under the alias service.sap.com/migrationkey for the installation number of the source system. The information relating to OS, DB and so on is required for statistical purposes, but is not used for generating the migration key. "
can I create installation number of the source system in my portal then generate migration key from that installation number ?
Regards

Db2 migration - /AFI/DIC_ANLA C err in TSK file

Hello,
I am using import_monitor to import tables in to Db6 using r3load and all tables completed except SAPAPPLO and SAPAPPL1. The following is the error from the log file
Could not deactivate CLI LOAD.
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: disconnected from DB
/usr/sap/SID/SYS/exe/run/R3load: job finished with 1 error(s)
In TSK, I found the following
T /AFI/DIC_ANLA C err
I tried to restart it and it gave the following error
dsql_exec_immediate returned DS_DBOBJECTEXISTS
(DB) INFO: disconnected from DB
Any help on this ?
This is on Db2, Linux and migration DB from oracle to DB6. I have been testing this on our sand box to figure out timing issue.
Thanks!

Hello,
You have to follow this notes
Note 1317905 - DB6: SQL0964C Transaction log full when using LOAD API
Before you start import again on the table /AFI/DIC_ANLA using R3load, drop the table manually and change the respective table in *.TSK file status err to xeq. And run again R3load import command manually.
Note 1068806 - DB6: TRUNCATE TABLE command delivers SQL3007C
Regards,
Surendra

Wrong migration key - installation number 00000000

Hi gurus,
Im trying to migrate SAP ERP EHP7 from MaxDB to DB2 database and while import ABAP phase I received error, that migration key is wrong. I was generating key via OSS, but it is always wrong. In log file I see something weird:
process id 3722
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "NAO                                                                                                                             "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "Linux"
(GSI) INFO: nodename = "bpx-nao"
(GSI) INFO: release = "3.0.13-0.27-default"
(GSI) INFO: version = "#1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b)"
(GSI) INFO: machine = "x86_64"
(VK) INFO: installation number = "0000000000"
(VK) ERROR: invalid migration key
/usr/sap/NAO/SYS/exe/uc/linuxx86_64/R3load: job finished with 1 error(s)
/usr/sap/NAO/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20140825185045
I think that this is the problem, how can I solve it?
Thanks in advance

Hi Martin,
Have you tried the above note and checked other parts to troubleshoot.
Also, can you check this note that you generated the key correctly.
317096 - Migration Key Generation for ABAP Systems
Also, please share test_MIGKEY.log or MIGKEY.log file
Regards,
Divyanshu

How can I Migrate/Split itunes/icloud account for a large family now that they have family sharing

Ok, now that Apple has finally come out with family sharing I need to get things sorted out and I think it is going to be a mess. I have 6 family members (my spouse and 4 children) all sharing/using one itunes account. For parental reasons this made perfect sense. Now with the the advent of family sharing and such we have alot of sorting and migrating to do and I am very unsure how to go about it. Here is what we have.
Myself - I have a 64GB iPad 3 and a 64GB iPhone 5
Spouse - 64GB iPhone 5
Children - x4 16GB iPhone 5C (pink, blue, green, and a yellow)
We have had one itunes account now for several years, we used to have x4 16GB iphone 4's and a 16GB iPod touch 4 so we needed it to be shared at the time. We all have different Game Center ID's and Facetime/iMessages are all setup to the phone numbers (aside from mine which also uses the itunes e-mail). We currently have 1 upgraded icloud account with 200GB of storage on it (love the new tiers). So here are the questions.
1) How do I go about using and isolating all the devices so they can all use the iCloud storage? Right now if I try and setup backups by device under the what to backup there is no simple "Full Backup" option, they have all the categories separated. I cannot backup my daughters contacts without forcing a merging of them and so on. Same thing with Documents and Data. Would I need to setup a different iCloud account for each device now?
2) iTunes Music/App purchases. Now that they have a family sharing function I am assuming it would be a good time to separate all the devices (aside from my personal iPad/iPhone). If I understand correctly we need to setup a new itunes account for each and link them with family sharing, does this then allow us to disperse/move items from a singular to the multiple account (at least a one time option to move around) or would it simply be shared off the original account? My daughter for example will be 18 next summer and as such no longer under our care. How do we move her items to her account? She has a lot of purchased Music. Now keep in mind I am talking about an account for someone who was 12 when she had her first device and as such needed to be under her parents.
I just want to state that repurchasing things is NOT an option, and to be frank, according to Canadian laws pertaining to *licensing* we actually own the product if we paid for it and have the right to transfer the ownership thereof. This issue went through the courts regarding used copies of OEM editions of Microsoft Windows several years ago and they closed the legal *license* vs ownership separation.

Go to appleid.apple.com to manage the ID, sign in and select to the Name, ID and Email Addresses section, then change the birth date on the bottom right. At the present time you may not be able to enter the correct birth date, but others have had success changing the year to 2000, or the date to 1/1/2001, both of which will have child ID status.

AR Open/Closed Invoices Migration Help

Hello Experts,
We have a data migration requirement for AR invoices from a legacy system to Oracle.
We have both open and closed invoices. Can anyone of you help in giving the steps to be followed? This is for India AR Invoices. Expecting a quick response and it would be of great help to us! This is in 11.5.10
Thanks,
Janani Sekar
Edited by: user11981778 on 20-Dec-2012 20:32

Hi,
Pl. populate the following open interfaces from your legacy data and then run the 'Autoinvoice Master Program'
(1) RA_INTERFACE_LINES_ALL
(2) ra_interface_distributions_all
For open invoices the AR_PAYMENT_SCHEDULES_ALL.STATUS sholuld be equal to 'OP' .
Pl. visit following link also for more info.
http://bhaskarreddyapps.blogspot.in/2011/10/ar-invoice-interface.html
HTH
Sanjay

Migrate all Open Sales Orders From Legacy System (SAP) To SAP System using

Hi Experts,
             I've to Migrate all Open Sales Orders From Legacy System (SAP) To SAP System using Business Objects with a new SALES ORDER DOCUMENT NUMBER referencing the older one.
           I'll get all the required data with field in an excel file.
             Does any standard transaction exist for it ? Or how to go ahead with it ?
Thanks and regards,
Jyoti Shankar

Hi
If you are checking for CREATE option then Sales Doc Type
For more Info goto SWO1 transaction -> BUS2032 --> DIsplay --> Execute --> There SELECT the method which you want to perform... There you can fine the MANDATORY parameters also....
Or in DISPLAY mode PLACE Cursor on the Required Method and CLick the PARAMETERS button on toolbar...
That will show the MANDATORY parameters...
Reward if helpful....
Message was edited by:
        Enter the Dragon

Migrating open POs and GR/IR clearing account balance

Hello gurus,
I've got the following problem concerning migration of open POs:
For example: In my source system there is a PO for 10 pcs. of some material. There has been a goods receipt for 5 pcs. (200$ each).
Now, when I import this order and the corresponding purchase order history into my target system (using LSMW), the target system creates the order, a material document for 5 pcs. and an account document.
But of course, our FI-team also has to migrate the balance of the 'old' GR/IR clearing account.
So, the balance in the source system is <> 0 (e.g. 1000$), because the 5 pcs. have been delivered but there has been no invoice receipt yet.
This balance is imported into the new system and then the open orders are migrated, generating an account document and thus, the balance is 2000$ afterwards.
This obviously is not correct, so I am sure that I am missing something, just what?
Thanks
Alicia

Hi,
1. There will be an open PO uploaded for 5 qty and price 200$ each
2. Opening Balance of Material - 5 qty and corresponding value to Stock A/c - 1000$
3. Also there will be Vendor Balances uploaded in the system as 1000$ against the invoice. (If the invoice is still expected then chec with FI Users if they can get invoice form vendor)
if no then do not upload initial stock entry of step2, create a PO of 10 qty and then do GR in system (SAP).

Migrating to DB6 v9.5

Similar Messages

Maybe you are looking for