Monitor red with errors while status is green

Errors originated when our production environment ran out of space. Since then more space is added resolving that issue. However, the monitor still remains with errors. The current production issue occurs when flat files are loaded via full loads; job shows successful, data is loaded in DSO, data is visible through reports, but monitor shows errors.
SM37 shows this error:
Check: No successful initialization of the delta update took place
Init. select. for field name currently running in request REQU_44CQ39DOX2Q85U97AKNKNMVOD
Error in generated init. package ZPAK_440UCB93QLW06PEMJ24OWYRQ5 for DSO LROTPD; no update
Report RSODSACT1 ended with errors
Job cancelled after system exception ERROR_MESSAGE
Thank you for you assistance,
Mustafa

Hello Mustafa,
One of the new features offered in Netweaver 2004s is the ability to set reports to include red requests in addition to the green an yellow ones. You might want to check the setting of the reports you are running. To do that, go to RSRT, enter the query name, and check the query properties. The value you're looking for is the "Data Integrity" setting. If the setting is "9 - All complete InfoProvider", it will include your red requests in the report.
Regards,
Adam

Similar Messages

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
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 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_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 .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
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 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_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 .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

SAP ECC error:'Migration Monitor' exits with error code 103.

Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
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 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha das

Hello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish.

Sapinst stops with error while installing ess component for Java AS

Dear experts,
I really hope you can help me with this one,
We are installing a ABAP/Java AS development system and sapinst has gone through 75% of all execution tasks nicely,
but then stopped with error while deploying components for the Java AS:
ERROR 2009-03-30 13:01:27
CJS-30156 SDM deployment failed for at least one of the components to deploy. SOLUTION: Check 'C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/DISTRIBUTED/AS/CI/callSdmViaSapinst.log' for more information.
ERROR 2009-03-30 13:01:28
FCO-00011 The step enableUsageTypes with step key |NW_Doublestack_CI|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|15|0|enableUsageTypes was executed with status ERROR .
Any help would be really appreciated as I am stuck with this and dont seem to be able to find any information on this one.
Thanks a lot for your help in advance.
Here is the crucial part of callSdmViaSapinst.log:
Mar 30, 2009 12:55:18... Info: Starting: Initial deployment: Selected development component 'ess/bp_ess'/'sap.com'/'MAIN_ERP05VAL_C'/'788220'/'0' will be deployed.
Mar 30, 2009 12:55:18... Info: SDA to be deployed: D:\usr\sap\DE1\DVEBMGS00\SDM\root\origin\sap.com\ess\bp_ess\MAIN_ERP05VAL_C\0\788220\sap.com_ess~bp_ess.sda
Mar 30, 2009 12:55:18... Info: Software type of SDA: J2EE
*Mar 30, 2009 12:55:18... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) ******
Mar 30, 2009 1:00:21 PM Info: Begin of log messages of the target system:
*09/03/30 12:55:19 - ************************************************************
09/03/30 12:58:07 - Start updating EAR file...
09/03/30 12:58:07 - start-up mode is lazy
09/03/30 12:58:08 - EAR file updated successfully for 578ms.
09/03/30 12:58:08 - Start deploying ...
09/03/30 12:58:42 - EAR file uploaded to server for 30641ms.
09/03/30 13:00:20 - ERROR: Not deployed. Deploy Service returned ERROR:
 java.rmi.RemoteException: Cannot deploy application sap.com/ess~bp_ess..
 Reason: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception during deploy: Failed to deploy archive D:\usr\sap\DE1\DVEBMGS00\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1238414327258\sap.comessbp_ess.epa
 The following objects could not be locked: [pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess**.iviews/com.sap.pct.erp.ess.personal_information/com.sap.pct.erp.ess.mx/com.sap.pct.erp.ess.addr/com.sap.pct.erp.ess.addr|pcd_service], [pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.iviews/com.sap.pct.erp.ess.personal_information/com.sap.pct.erp.ess.de/com.sap.pct.erp.ess.addr|pcd_service], [pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.iviews/com.sap.pct.erp.ess.personal_information/com.sap.pct.erp.ess.id/com.sap.pct.erp.ess.addr/com.sap.pct.erp.ess.addr|pcd_service], [pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.pages/com.sap.pct.erp.ess.personal_information/com.sap.pct.erp.ess.jp/com.sap.pct.erp.ess.addr/com.sap.pct.erp.ess.addr|pcd_service], [pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.pages/com.sap.pct.erp.ess.personal_information/com.sap.pct.erp.ess.de/com.sap.pct.erp.es

Thanks Désirée for your answer and apologies for the late update on this one.
This issue is resolved now, the reason for the error was a lack of memory which probably triggered a timeout in sapinst. After upgrading the memory to 7GB and re-starting the ABAP+Java AS and resuming sapinst everything went through fine. However, this was hard to spot because the logs wouldn't tell you about the lack of memory but about everything else!
regards,
Manfred

Time Machine fails with "error while linking files on the backup volume"

One of my drives was nearly full. I moved some folders from that drive to one that had more space.
The next TM backup failed with "error while linking files on the backup volume". A full backup is about 620 GB, although this backup shouldn't have been a complete one. There was 570+ GB free on the drive.
A Disk Verify reported "Drive appears to be okay." Earlier TM backups appeared to be fine (at least accessible). I swapped the TM drive for another, initialized it, and TM used that drive with no complaints.
What does the message mean?
Thanks,
harv47

Pondini wrote:
harv47 wrote:
The Time Machine Buddy widget shows no messages. None of the buttons do anything.
What am I doing wrong?
See #A1 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
Your user account may not have permission to see the logs.
The sentence beginning "If the message area is blank ..." shows how to figure out if that's the problem, and how to fix it.
Post back if it's not clear, or doesn't work.
The Tip had the answer. It was permissions.
What follow are the messages for the last unsuccessful TM backup (on v.3), followed by
the successful TM backup on the replacement drive (v.1). The line
"Copied 11 files (0 bytes) from volume Bay 3 HPFS+." was odd.
Starting standard backup
Backing up to: /Volumes/Time Machine v.3/Backups.backupdb
Event store UUIDs don't match for volume: Bay 3 HPFS+
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/Volumes/Bay 3 HPFS+ reason:kFSEDBEventFlagMustScanSubDirs|
Node requires deep traversal:/ reason:kFSEDBEventFlagMustSc
(Finished May 4, 2010 9:31:21 AM-- Status unknown)
Starting standard backup
Backing up to: /Volumes/TimeMachine v.1/Backups.backupdb
Event store UUIDs don't match for volume: Bay 3 HPFS+
Event store UUIDs don't match for volume: Bay 2 HPFS+
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 169.1 GB excluded items size: 0 bytes for volume Bay 3 HPFS+
Backup content size: 305.5 GB excluded items size: 0 bytes for volume Bay 2 HPFS+
Backup content size: 145.7 GB excluded items size: 7.5 MB for volume Macintosh HD
No pre-backup thinning needed: 744.36 GB requested (including padding), 931.15 GB available
Waiting for index to be ready (909 > 0)
Copied 1951 files (169.0 GB) from volume Bay 3 HPFS+.
Copied 4999 files (474.3 GB) from volume Bay 2 HPFS+.
Copied 410304 files (612.4 GB) from volume Macintosh HD.
No pre-backup thinning needed: 712.2 MB requested (including padding), 315.09 GB available
Copied 11 files (0 bytes) from volume Bay 3 HPFS+.
Copied 20 files (1.1 GB) from volume Bay 2 HPFS+.
Copied 1103 files (1.1 GB) from volume Macintosh HD.
Starting post-backup thinning
No post-back up thinning needed: no expired backups exist
Backup completed successfully.
(Finished May 4, 2010 2:38:17 PM)
I hope this is useful. Thanks for your help.
harv47

Management console end up with error 1 status

Hi Friends,
When I start SAP management console, it is end-up with error status 1. Immediately after starting Management console, it is coming to Green color and with in 2~3 minutes, again it is coming to Yellow color and ending with error status-1.
Could anyone please help to solve this issue as I am not able to log-on SAP for a long time?
Please advice.
Regards,
Mani

Hi,
Agree with garyc007. Exchange 2010 tools show the currently installed Service Pack version, and not what RU is currently installed.
Exchange 2010 SP3's build number is 14.3.123.4. One CAS server ends up with version 14.03.0174.001, it means this server has installed Update Rollup 4 for Exchange Server 2010 SP3 successfully. I recommend you check if the other server has installed Update
Rollup 4 for Exchange Server 2010 SP3 successfully.
Here is a blog for your reference.
Exchange Server and Update Rollups Build Numbers
https://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollups-build-numbers.aspx
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

JCONTROL - dies with Error while connecting to DB

Hi....Experts
DB : Oracle 10.2.0.4.0
OS ; AIX 5.3
NW : 7.0 SP22
UT : EP
Yesterday the above server got rebooted by a power failure. after that
The server's DB is coming up as ora<sid> user, listener is also up
But as <sid>adm user - when i am starting . The jcotnrol dies and in thee work directory
....log_bootstrap_ID1168012.0.log fiel shows the below messages in the tail end,
================================================================
ERROR-1 : OBSERVED
================================================================
==[ Caused by: ]==----
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:365)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:130)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
 at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:74)
 at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:473)
 at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
 at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
 at java.lang.reflect.Method.invoke(Method.java:391)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: java.sql.SQLException: Io exception: There is no process to read data written to a pipe.
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)
 at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:387)
 at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)
 at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
 at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
 at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
 at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:307)
 ... 15 more
[Feb 10, 2012 4:46:28 PM ] [Bootstrap module]> Problem occurred while performing synchronization.
================================================================
ERROR-2 : OBSERVED
================================================================
also i see error in work directory ...sapcpe.log as below
Host:d45adm> more sapcpe.log
2012/02/10 19:01:45
sapcpe version UC: @(#) $Id: //bas/700_REL/src/ccm/sapstart/sapxxcpe.c#20 $ SAP
Command line:
0: /usr/sap/D45/SYS/exe/run/sapcpe
1: name=D45
Trace level (profile): 1
INFO: Try to find file table sapcpeft (default:sapcpeft)
INFO: Try to find file table in the central directory /usr/sap/D45/SYS/exe/ctrun/sapcpeft
INFO: not found any file table.
source: /usr/sap/D45/SYS/exe/ctrun
target: /usr/sap/D45/SYS/exe/run
ERROR: sapcpe: find <src> /usr/sap/D45/SYS/exe/ctrun failed, 2, No such file or directory, [sapxxcpe.c:1464]
sapcpe.log: END
================================================================
any thoughts & advises, clues ???
Rgds
PR

ISSUE - RESOLVED
####Summary######################################
Key Word of this Issue :
Exception in thread "main" java.sql.SQLException: Io exception: There is no process to read data written to a pipe.
Reason
Name resolution by conflict / failure by netsvc.conf even we have hostfile & ping works with host name for Every user.
Solution
Adjusted netsvc.conf file to use the hostfile.
DETAILS OF RESOLUTION
OSS Experts asked me to copy the results
SAP Note No. 867176: FAQ: Oracle JDBC (JdbcCheckup) - Point 10
01. I copied JdbcCheckup.sar to location /home/sidadm/867176-jdbchkup/
02. Extracted the same in same foler with command : SAPCAR -xvf JdbcCheckup.sar
03. Now folder contained 2 files ""JdbcCheckup.java"" and "" JdbcCheckup.sar""
04. my JDBC driver file ojdbc14.jar is in location /oracle/client/10x_64/instantclient/
05. To determine the JDBC driver version issued the below command as per note
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$Command : java -classpath /oracle/client/10x_64/instantclient/ojdbc14.jar:. JdbcCheckup
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Please enter information to test connection to the database
user: SAPSR3DB
password: PASSWORD
database(a TNSNAME entry): SID
Hostname: portalserver
Port (1521): 1527
Connecting to the database...Connecting...
jdbc:oracle:thin:@portalserver:1527:SID, SAPSR3DB, PASSWORD
Exception in thread "main" java.sql.SQLException: Io exception: There is no process to read data written to a pipe.
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)
 at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:387)
 at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:441)
 at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
 at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
 at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
 at java.sql.DriverManager.getConnection(DriverManager.java:559)
 at java.sql.DriverManager.getConnection(DriverManager.java:189)
 at JdbcCheckup.main(JdbcCheckup.java:128)
portalserver:sidadm>
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
06. Immediately id did google with above Syntax of error.
"""java.sql.SQLException: Io exception: There is no process to read data
written to a pipe"""
https://forums.oracle.com/forums/thread.jspa?threadID=1320173
which was referring about netsvc.conf
With UNIX Team discussions, adjusted the host file as first name
resolution source and DNS servers list followed in same(netsvc.conf) file. which
fixed the issue and "JdbcCheckup" passed.
07. JdbcCheckup Command - Passed output.
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$Command : java -classpath /oracle/client/10x_64/instantclient/ojdbc14.jar:. JdbcCheckup
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Command : java -classpath /oracle/client/10x_64/instantclient/ojdbc14.jar:. JdbcCheckup
Please enter information to test connection to the database
user: SAPSR3DB
password: PASSWORD
database(a TNSNAME entry): SID
Hostname: portalserver
Port (1521): 1527
Connecting to the database...Connecting...
jdbc:oracle:thin:@portalserver:1527:SID, SAPSR3DB, PASSWORD
connected.
=============
Database Product Name is ... Oracle
Database Product Version is Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Data Mining and Real Application Testing options
=============
JDBC Driver Name is ........ Oracle JDBC driver
JDBC Driver Version is ..... 10.2.0.4.0
=============
Hello World
Your JDBC installation is correct.
portalserver:sidadm>
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
BIG THANK TO EVERYONE !!!!!!!!!!!!!!!!
REGARDS
PR

Bursting Program errors with "Error while generating the Document"

Hello Folks
Here is my bursting control file
<?xml version="1.0" encoding="UTF-8"?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi">
<xapi:globalData location="stream">
</xapi:globalData >
<xapi:request select="/XMLEXCEL1/LIST_G_Q0">
<xapi:delivery>
<xapi:email server="mycompany.com" port="25" from="[email protected]"
reply-to ="[email protected]">
<xapi:message id="1234" to="[email protected]"
attachment="true" content-type="html/text"
subject="Employee Report for Empno"> Dear
Please review the attached document</xapi:message>
</xapi:email>
</xapi:delivery>
<xapi:document key="123" output-type="XLS" delivery="1234"
output="XMLEXCEL1" >
<xapi:template type="RTF" location="xdo://AR.XMLEXCEL1.en.00/?getSource=true">
</xapi:template>
</xapi:document>
</xapi:request>
</xapi:requestset>
this is the output of bursting status report:
<?xml version="1.0" encoding="UTF-8"?>
<BURS_REPORT><REQUESTID>40403415</REQUESTID>
<PARENT_REQUESTID>40403339</PARENT_REQUESTID>
<REPORT_DESC>XMLEXCEL1</REPORT_DESC>
<OUTPUT_FILE>/opt/local/application/orafin/applmgr/out/outfaud/S1759.zip
</OUTPUT_FILE>
<DOCUMENT_STATUS>
<KEY>123</KEY>
<OUTPUT_TYPE>XLS</OUTPUT_TYPE>
<DELIVERY></DELIVERY>
<OUTPUT>
</OUTPUT>
<STATUS>fail</STATUS>
<LOG>Error while generating the Document...</LOG>
</DOCUMENT_STATUS>
</BURS_REPORT>
Can anyone help on this please.

can anyone help me?

** End-to-End Monitoring - RFC destination error while save config in RWB

Hi Friends,
We have 2 RFC destinations in our XI server. 1) PMI<client>001 2) PMI<client><client>800. First one is for XI server. Next one is for Sender/Receiver System.
We want to activate End-to-End Monitoring in RWB. For this, when I save configuration, it throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
I have checked the user in the above destinations. For the first destination, we have assigned PIRWBUSER of XI system. Test Connection is OK, but unable to login remote. At the same time, PIRWBUSER is not locked.
For the second destination, I have assigned some login user of sender/receiver system. Test connection is OK. Able to login remotely.
There is no RFC user in our XI system. (I tried using RFCUSER* thru SU01 tcode).
There is no PIRWBUSER in the Sender/Receiver System.
In RWB, Configuration, 3 components are there. 1) XIIntegrationServer 2) Business System (for Sender/Receiver System) 3) XI Adapter Framework. I selected last two. (First one is already selected). Monitoring Level : Medium (for all 3). Send and Receive Check box is selcted for the last two.
So, what could be the problem for the above error?
Could you kindly clarifiy friends.
Thanking you
Kind Regards,
Jeg P.

Hi friends,
I have one RFC Destination PMI<sysid>001. (Abap Connction) in my XI system. This destination is for XI server. Connection Test is OK. Remote Logon by using the PIRWBUSER is also ok.
In the 'Configuration' tab of the Runtime Workbench, when we select 'Save Configuration', (Business System and Adapter Framework is not activated) with the default activation for XI Integration Server, the system throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
When we save configuration, an one more destination is automatically created in the name as below.
PMI<sysid>001<yyyymmdd>. For Example, PMIPID00120080207.
When we test newly created RFC destination, connection is OK, but not able to remot login using the same user PIRWBUSER.
The difference between old and new RFC destination, in old, we have selected Load Balancing is 'Yes', but in the new it is 'No'. The system also tells the error below.
Name or Password is incorrect (repeat logon) - PMIPID00120080207
But, still remote login is possible in the old RFC destination using the PIRWBUSER.
So, What could be the problem ...?
Kindly reply, friends.

SAPINST terminated with error "Exit status of child: 3"

The SAPINST terminated after run with the error message as
below:
SAPinst is getting started.
Please be patient ...
starting gui server process:
sapinstport: 21200
guiport : 21212
guistart : true
command : "C:\Program Files\Java\j2re1.4.2_09/bin\javaw.exe" -
cp "C:/DOCUME1/ADMINI1.LAE/LOCALS~1/Temp/sapinst_exe.3256.1197655087
\jar\instgui.jar;C:/DOCUME1/ADMINI1.LAE/LOCALS~1/Temp/sapinst_exe.3256.1197655087\jar\inqmyxml.jar" -Xmx256M -Dsun.java2d.noddraw=true
SDTServer config=jar:sdtserver.xml guiport=21212 sapinsthost=localhost
sapinstport=21200 guistart=true
load resource pool E:\SAPCD\Master\IM_WINDOWS_I386\resourcepool.xml
guiengine: no GUI connected; waiting for a connection on host sapprd2,
port 21200 to continue with the installation
guiengine: login in process.
This application has requested the Runtime to terminate it in an
unusual way.
Please contact the application's support team for more information.
Exit status of child: 3
First time I use JAVA SDK version 1.4.2_12 after that I try version
1.4.2_9 and 1.4.2_15 but all of them got the same error.
So please kindly help for this. We have planed to upload data to the
PRD System on next week.
Many thanks,
Amnat O.

The problem still occur with the error message as below:
SAPinst is getting started.
Please be patient ...
starting gui server process:
sapinstport: 21200
guiport    : 21212
guistart   : true
command    : "C:\Program Files\Java\j2re1.4.2_15/bin\javaw.exe" -cp "C:/Temp/sapinst_exe.3536.1198011240\jar\instgui.jar;C:/Temp/sapinst_exe.3536.1198011240\jar\inqmyxml.jar" -Xmx256M -Dsun.java2d.noddraw=true SDTServer config=jar:sdtserver.xml guiport=21212 sapinsthost=localhost sapinstport=21200 guistart=true
load resource pool E:\SAPCD\Master\IM_WINDOWS_I386\resourcepool.xml
guiengine: no GUI connected; waiting for a connection on host sapprd2, port 21200 to continue with the installation
guiengine: login in process.
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Exit status of child: 3

Idocs with errors added status-56 in file to idoc scenario- how to rectify

hi ,
in file to idoc scenario when i m sending the file from ftp server to IS Retail, file is successfully getting processed but the idoc is showing error ,when we see using WE05 tcode or BD87 , pl sugggest how to rectify it to make the status 53

Hi,
Have you configured the partner profile details? check these steps..
1. In the receiver system you must configure the partner profile for your sender system in WE20.
2. Add the IDoc message type to inbound parameters of the partner profile and configure the appropriate process code.
2. Fill the Logical system name for your senderservice-->Adapter Specific identifiers in ID.
<a href="/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi File-to-IDOC Scenario</a> By Venugopalarao
<a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> By Ravikumar Allampalam
Regards
San

Red Eclipse error while compiling

Hello.
I'm trying to install Red Eclipse. But when the compilation finishes, this message error appears:
ERFACE -DIRC -Ishared -Iengine -Igame -Ienet/include -I/usr/X11R6/include `sdl-config --cflags` -c -o shared/zip.o shared/zip.cpp
g++ -O3 -fomit-frame-pointer -Wall -fsigned-char -fno-exceptions -fno-rtti -DINTERFACE -DIRC -Ishared -Iengine -Igame -Ienet/include -I/usr/X11R6/include `sdl-config --cflags` -o engine/engine.tmp.h.gch engine/engine.h
engine/engine.h:742:1: error fatal: no se puede escribir el fichero PCH: No queda espacio en el dispositivo
compilación terminada.
make: *** [engine/engine.h.gch] Error 1
And I can't install it after that, even if I restart the installation.

fatal error: Can not write file PCH: No space left on device
compilation terminated.
Fixing that would be a good start.
Maybe change your BUILDDIR for makepkg temporarily or increase tempfs. A simple reboot and do nothing but get a term up and build the package may also work.

Process Chain Ended with Errors - cause unknown

I have had several instances of process chains stopping for no apparent reason. The stops occur between 2 master data infopackage loads. The last step is green and the next is grey. The PSA table has been updated successfully for the last step. All IDocs are in green status in both systems. The monitor for the last successful step does say "Ended with Errors" although no errors are evident. The process chain starts back up via Repeat at the next (grey) step and continues successfully. There were no system problems or connection interruptions that occurred during the time the process chains failed. There were no changes in the remote user profile.
This exact problem has occurred a half dozen times since our application of ECC Support Packs several months ago and had not occurred before. The infopackages are different each time. Two different process chains have had this problem. I have re-activated and re-scheduled the process chains without solving the problem.
Thanks for any ideas on why this may be occurring or what I can do to prevent it.
Patty Moffatt

Hi Des,
Here's my BW release info:
SAP_ABA        640       0019 SAPKA64019     Cross-Application
SAP_BASIS      640       0019 SAPKB64019     SAP Basis
PI_BASIS       2005_1_6400009 SAPKIPYJ69     Basis Plug-In
ST-PI          2005_1_6400008 SAPKITLQH8     SAP Solution Tools Plug-
SAP_BW         350       0019 SAPKW35019   SAP_BW
ECC SPs 13-21 were applied before the BW problem started:
SAP_BASIS      640       0021 SAPKB64021
SAP_ABA        640       0021 SAPKA64021
PI_BASIS       2005_1_6400012 SAPKIPYJ6C
ST-PI          2005_1_6400008 SAPKITLQH8
SAP_BW         350       0021 SAPKW35021
PI             2004_1_5000016 SAPKIPZI6G
The process chain step and the monitor load both are green. The Details tab shows all the processing is green, but the Process Chain itself is red with "Errors Occurred. There have been no runtime dumps.
Patty

Urgent: Error while installing ECC6.0

Hi guys,
iam getting the following error while installing ecc6.0 at importing abap stage.
ERROR 2007-10-25 23:28:45
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-10-25 23:28:45
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|9|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 .
outof 59, 8 jobs failed. if u want i can post the log file.
thanks,
sandeep.

Hi guys,
i got rid of the problem,
when i want to login as sysdba in cmd, it says oracle error 01034
then tried these steps
set ORACLE_SID=XXX
sqlplus /nolog
conn system/manager as sysdba
shutdown abort
startup
then i tried to reinstall , it worked.
thanks
sandeep.

Error While loading Hierarchy from R3 to BW

Hi Experts,
plz solve my problem,
I am rtying to load Hierarchy data from IS-R R/3 to Bw
In the monitoring(left hand side) QM status is green saying that the load is successfull
Right hand side QMStatus also Green,
But in the Details Tab(right hand side)
the overall Status is Yellow and it's giving warning messa like Missing messages and Warnings Under this
*Requests (messages): Everything OK
 Data request arranged
 Confirmed with: OK
*Extraction (messages): Everything OK
 Data request received
 Data selection scheduled
 6154 Records sent ( 6154 Records received )
 Data selection ended
*Transfer (IDocs and TRFC): Missing messages(QMStatus is Yellow)
*Processing (data packet): Everything OK
*Data Package 1 ( Records ) : Everything OK
 *Transfer rules ( 6154 Records ) : No errors
 *Hierarchies for master data received. Processing being started.
 *Transfer 6154 data records in communication structure
 *Update ( 0 new / 0 changed ) : No errors
 *Data saved successfully
 *Processing end : No errors
 *Data successfully transferred to the update
*Subseq. processing (messages) : No errors
 -> Start update of master data hierarchy
 <- End update of master data hierarchy
Hierarchy successfully activated
Why in the update mode showing 0 new and 0 changed
it has to show records 6154 new.
but the hierarchy(Merchandise Category) is attching to the infoobject(0material),All the hierarchies are available in the BW .
But its displaying in the BEx report like Not Assigned Material,
I am Unable to solve this proble,
Plz give me the solution
Thanks in Advance
Anil

Hi Anil,
 See if this link can help you.. I am not sure though...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=/help/sdn_nw04/saphelp_nw04/helpdata/en/1f/83813ec8d3fe3ee10000000a114084/content.htm
Thanks,
Raj

Monitor red with errors while status is green

Similar Messages

Maybe you are looking for