R3trans finsihed with error code 12 when starting SAP
Dear Experts,
Please note that the listener is up & running but still getting the error. Please find the logs below:
cat trans.log
4 ETW000 R3trans version 6.19 (release 720 - 24.08.10 - 14:38:42).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 07.11.2011 - 16:54:23
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc ,00000] Mon Nov 7 16:54:23 2011 115 0.000115
4 ETW000 [dev trc ,00000] db_con_init called 23 0.000138
4 ETW000 [dev trc ,00000] determine_block_commit: no con_hdl found as blocked for con_name = R/3
4 ETW000 51 0.000189
4 ETW000 [dev trc ,00000] create_con (con_name=R/3) 19 0.000208
4 ETW000 [dev trc ,00000] Loading DB library '/usr/sap/P7C/SYS/exe/run/dboraslib.so' ... 48 0.000256
4 ETW000 [dev trc ,00000] DlLoadLib() success: dlopen("/usr/sap/P7C/SYS/exe/run/dboraslib.so"), hdl 0
4 ETW000 17417 0.017673
4 ETW000 [dev trc ,00000] Library '/usr/sap/P7C/SYS/exe/run/dboraslib.so' loaded 28 0.017701
4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library /usr/sap/P7C/SYS/exe/run/dboraslib.so
4 ETW000 36 0.017737
4 ETW000 [dev trc ,00000] Version of '/usr/sap/P7C/SYS/exe/run/dboraslib.so' is "720.00", patchlevel (0.64)
4 ETW000 83 0.017820
4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library /usr/sap/P7C/SYS/exe/run/dboraslib.so
4 ETW000 26 0.017846
4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library /usr/sap/P7C/SYS/exe/run/dboraslib.so
4 ETW000 78 0.017924
4 ETW000 [dev trc ,00000] New connection 0 created 25 0.017949
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = -000000001, state = DISCONNECTED, tx = NO , bc = NO , hc = NO , perm = YES, reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO , prog =
4 ETW000 45 0.017994
4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3) 21 0.018015
4 ETW000 [dev trc ,00000] determine_block_commit: no con_hdl found as blocked for con_name = R/3
4 ETW000 25 0.018040
4 ETW000 [dev trc ,00000] find_con_by_name found the following connection: 16 0.018056
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , bc = NO , hc = NO , perm = YES, reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO , prog =
4 ETW000 33 0.018089
4 ETW000 [dev trc ,00000] oci_init1(ArrayBufSize=130000) 329 0.018418
4 ETW000 [dev trc ,00000] Oracle Client Version: 10.2.0.4.0, V5 123 0.018541
4 ETW000 [dev trc ,00000] Installed Oracle client patches: 199 0.018740
4 ETW000 [dev trc ,00000] # Unique Patch ID: 12114073Created on 15 Jan 2010, 09:30:31 hrs PST8PDT
4 ETW000 31 0.018771
4 ETW000 [dev trc ,00000] # Patch 8732366 : Created on 27 Jul 2009, 15:49:18 hrs CEST 63 0.018834
4 ETW000 [dev trc ,00000] # Patch 6944036 : Created on 3 Jun 2008, 23:35:37 hrs PST8PDT
4 ETW000 44 0.018878
4 ETW000 [dev trc ,00000] # Patch 6826661 : Created on 20 May 2008, 00:23:58 hrs PST8PDT
4 ETW000 38 0.018916
4 ETW000 [dev trc ,00000] # Patch 6775231 : Created on 2 Dec 2008, 21:45:40 hrs PST8PDT
4 ETW000 38 0.018954
4 ETW000 [dev trc ,00000] # Unique Patch ID: 12924916Created on 13 Sep 2010, 23:47:52 hrs PST8PDT
4 ETW000 39 0.018993
4 ETW000 [dev trc ,00000] Default connection: tnsname ='P7C' 26 0.019019
4 ETW000 [dev trc ,00000] -->oci_initialize(con=0, char='', nchar='') 31 0.019050
4 ETW000 [dev trc ,00000] application info callback registered 23 0.019073
4 ETW000 [dev trc ,00000] OCIEnvCreate(mode=16384=OCI_UTF16) failed with -1=OCI_ERROR 1311 0.020384
4 ETW000 [dev trc ,00000] OCIErrorGet() failed with rc=-2 37 0.020421
4 ETW000 [dev trc ,00000] -> no further error details available 26 0.020447
4 ETW000 [dev trc ,00000] OCIEnvCreate(mode=16384=OCI_UTF16) returned -1 (for default NLS handle)
4 ETW000 30 0.020477
4 ETW000 [dev trc ,00000] set_ocica() -> OCI return code -1 26 0.020503
4 ETW000 [dev trc ,00000] DbSlConnect(con=-1) -> orc=-1, 99=DBSL_ERR_DB 28 0.020531
4 ETW000 [dblink ,00000] ***LOG BY2=>sql error -1 performing CON 63 0.020594
4 ETW000 [dblink ,00000] ***LOG BY0=>OCI returned error code -1. 25 0.020619
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'P7C'"
Please help to resolve the issue.
> 4 ETW000 [dev trc ,00000] OCIEnvCreate(mode=16384=OCI_UTF16) failed with -1=OCI_ERROR 1311 0.020384
> 4 ETW000 [dev trc ,00000] OCIErrorGet() failed with rc=-2 37 0.020421
> 4 ETW000 [dev trc ,00000] -> no further error details available 26 0.020447
> 4 ETW000 [dev trc ,00000] OCIEnvCreate(mode=16384=OCI_UTF16) returned -1 (for default NLS handle)
> 4 ETW000 30 0.020477
> 4 ETW000 [dev trc ,00000] set_ocica() -> OCI return code -1 26 0.020503
> 4 ETW000 [dev trc ,00000] DbSlConnect(con=-1) -> orc=-1, 99=DBSL_ERR_DB 28 0.020531
> 4 ETW000 [dblink ,00000] ***LOG BY2=>sql error -1 performing CON 63 0.020594
> 4 ETW000 [dblink ,00000] ***LOG BY0=>OCI returned error code -1. 25 0.020619
> 2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'P7C'"
What happened prior to this error? was this system running before?
Markus
Similar Messages
-
Error message when starting SAP J2EE Engine 6.20
When i am starting SAP J2EE Engine 6.20 i am not able to get the homepage at its startup.
I have checked the Cluster_Log and it says
[OS: Windows XP] [VM vendor: Sun Microsystems Inc.] [VM version: 1.3.1_16-b06] [VM type: Java HotSpot(TM) Client VM]
SAP J2EE Engine Version 6.20 PatchLevel 100897.20 is starting...
Loading: LogManager ...
Loading: R3StartupManager ...
Loading: ThreadManager ...
Loading: TimeoutManager ...
Loading: MemoryManager ...
Loading: PoolManager ...
Loading: PolicyManager ...
Loading: ConnectionsManipulator ...
Loading: IpVerificationManager ...
Loading: ClusterManager ...
Loading: ClassLoaderManager ...
Loading: PortsManager ...
Loading: LockManager ...
Loading: ServiceManager ...
Loading core services:
Starting core service p4 ... done. (297 ms)
Starting core service security ... done. (78 ms)
Starting core service log ... done. (656 ms)
Starting core service admin ... done. (204 ms)
Starting core service monitor ... done. (235 ms)
Core services loaded successfully.
Loading additional services:
Starting service httptunneling ... done. (109 ms)
Starting service jms ... done. (0 ms)
Starting service telnet ... done. (94 ms)
Starting service shell ... done. (250 ms)
ID000544: Error starting service http. Can't start the service due to java.io.IOException: Can't open HTTP server socket on port 80
[ServiceManager]: ID000544: Error starting service http. Can't start the service due to java.io.IOException: Can't open HTTP server socket on port 80
Additional services loaded successfully.
[Framework -> criticalShutdown] [Tue Jul 22 13:44:16 IST 2008] Service http startup error!
Here i can notice "Cant open HTTP server socket on port 80".
How can i do this setting so that everything works fine.Hi
Check that your port 80 is not occupied by other running application (eg. IIS or ITS etc.)
Also check that it may be disabled by antivirus software.
Check the services file that this port is not assigned to other application then
http 80/tcp www www-http -
Error coming when starting SAP Management Console
Hi
Error is coming when trying to start the Server in Microsoft Management Console . Well this has started coming just now , it was working fine except one point i want to highlight is that on the machine WAS620gui was installed and i upgraded to WAS640 gui , so is it related to with the upgradation of gui ?
The error is :
Snap in failed to initialize |
Name : SAP system Manager |
CLSID {633547EE-A302-11D1-AE59-0800009B07DBB}|Hi
It seems that the registration of the sapmmc.dll failed.
You can recover SAP Management Console again by manually registering the MMC snap-in. Do the following:
Open a CMD.exe and walk through the directory containing the sapmmc.dll file (mostly is under %systemroot%\system32 directory) then execute the following command:
Regsvr32 sapmmc.dll
You should see a message confirmation that registration was successful.
Then start mmc again...it should now work smoothly!
Hope this helps!
Best Regards,
Federico G. Babelis
http://www.gazum.com -
SAP not starting after crash: Terminateing With error code 12
Hi,
After system crash SAP is not starting normally. When running startsap under SIDadm puts out: /usr/sap/TST/SYS/exe/run/startdb: Terminateing With error code 12
startdb.log shows that:
/oracle/TST/102_64/bin/sqlplus: error while loading shared libraries: libsqlplus.so: cannot open shares object file: No such file or directory
I have checked - file and directory are present.
However - when manually starting DB under oraSID and then logging in as SIDadm and starting SAP - everything starts normally.
(Allthough SID is has been changed before - system also worked normally after SID change) I have checked userrights and groups , also profile - everything seems to be normal. Any ideas?
Edited by: Kristjan T on Mar 16, 2011 1:16 PMHi,
1.what UNIX Flavor are we talking about -> SuSe
2.What SAP Kernel Release is in place (may be 6.40 non EX2 ?) -> 6.40
3.What release is the DB suposed to have? -> 10.2.0.2.0 - 64bit Prod
4.I see, you are calling an sqlplus from a 10.2 ORACLE_HOME.
Is that the correct HOME the DB is running with ? -> Yes
5.Can you start the DB with
brconnect -c -u / -f dbstart -> NO
Error is:
:devadm 51> brconnect -c -u / -f dbstart
BR0801I BRCONNECT 7.00 (40)
oracleDEV: error while loading shared libraries: libskgxp10.so: cannot open shared object file: No such file or directory
BR0278E Command output of '/oracle/DEV/102_64/bin/sqlplus /nolog':
/oracle/DEV/102_64/bin/sqlplus: error while loading shared libraries: libsqlplus.so: cannot open shared object file: No such file or directory
BR0280I BRCONNECT time stamp: 2011-05-05 15.01.17
BR0279E Return code from '/oracle/DEV/102_64/bin/sqlplus /nolog': 127
BR0302E SQLPLUS call for database instance DEV failed
BR0303E Determination of Oracle version failed
BR0280I BRCONNECT time stamp: 2011-05-05 15.01.17
BR0804I BRCONNECT terminated with errors
(Different machine but same situation)
6.As already requested, what is the output of:
6.1.ldd sqlplus
:devadm 55> ldd sqlplus
ldd: ./sqlplus: No such file or directory
in addition:
6.2. env | grep -i ora
devadm 56> env | grep -i ora
PATH=/oracle/DEV/102_64/bin:/opt/IBMJava2-amd64-142/bin:.:/home/devadm:/usr/sap/DEV/SYS/exe/run:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/devadm/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/bin/X11:/usr/lib/mit/bin:/usr/lib/mit/sbin
LD_LIBRARY_PATH=/usr/sap/DEV/SYS/exe/run:/oracle/client/10x_64/instantclient
dbms_type=ORA
dbs_ora_tnsname=DEV
dbs_ora_schema=SAPSR3
ORACLE_SID=DEV
ORACLE_BASE=/oracle
TNS_ADMIN=/usr/sap/DEV/SYS/profile/oracle
ORACLE_HOME=/oracle/DEV/102_64
SAPDATA_HOME=/oracle/DEV
6.3 env | grep -i nls
:devadm 57> env | grep -i nls
XNLSPATH=/usr/X11R6/lib/X11/nls
NLS_LANG=AMERICAN_AMERICA.UTF8
6.4 env | grep -i lib
devadm 58> env | grep -i lib
PATH=/oracle/DEV/102_64/bin:/opt/IBMJava2-amd64-142/bin:.:/home/devadm:/usr/sap/DEV/SYS/exe/run:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/devadm/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/bin/X11:/usr/lib/mit/bin:/usr/lib/mit/sbin
XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB
XNLSPATH=/usr/X11R6/lib/X11/nls
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:/usr/lib64/pkgconfig:/usr/share/pkgconfig:/opt/kde3/lib64/pkgconfig:/opt/gnome/lib64/pkgconfig:/opt/gnome/lib64/pkgconfig:/opt/gnome/share/pkgconfig
GTK_PATH=/usr/local/lib/gtk-2.0:/opt/gnome/lib/gtk-2.0:/usr/lib/gtk-2.0
GTK_PATH64=/usr/local/lib64/gtk-2.0:/opt/gnome/lib64/gtk-2.0:/usr/lib64/gtk-2.0
DIR_LIBRARY=/usr/sap/DEV/SYS/exe/run
LD_LIBRARY_PATH=/usr/sap/DEV/SYS/exe/run:/oracle/client/10x_64/instantclient
Any ideas???
Br,
Kristjan T. -
/usr/sap/QAS/SYS/exe/run/startdb: Terminating with error code 12
Hi Experts,
We have made a system copy from Production to Quality and it has been done successfully. Now we are able to open the database manually. But when we are trying to start SAP it is not connecting the database base and it is giving error which is given below :
/home/qasadm/startdb.log
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area 4764729344 bytes
Fixed Size 2035312 bytes
Variable Size 2432700816 bytes
Database Buffers 2315255808 bytes
Redo Buffers 14737408 bytes
Database mounted.
Database opened.
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning and Data Mining options
Mon Apr 12 10:45:40 IST 2010
Connect to the database to verify, that the database is now open
R3trans check finished with return code: 12
ERROR: Startup of database failed
Notify Database Administrator.
/usr/sap/QAS/SYS/exe/run/startdb: Terminating with error code 12
^C
root@bsltest # tail -f /home/qasadm/startdb.log
Connect to the database to check the database state:
R3trans: connect check finished with return code: 12
Database not available
Mon Apr 12 10:55:53 IST 2010
Shutdown database
First trying to shutdown the database - May be,
the database is in the nomount or mount state
Mon Apr 12 10:56:22 IST 2010
starting database
SQL*Plus: Release 10.2.0.2.0 - Production on Mon Apr 12 10:56:22 2010
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area 4764729344 bytes
Fixed Size 2035312 bytes
Variable Size 2432700816 bytes
Database Buffers 2315255808 bytes
Redo Buffers 14737408 bytes
Database mounted.
Database opened.
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning and Data Mining options
Mon Apr 12 10:56:42 IST 2010
Connect to the database to verify, that the database is now open
R3trans check finished with return code: 12
ERROR: Startup of database failed
Notify Database Administrator.
/usr/sap/QAS/SYS/exe/run/startdb: Terminating with error code 12
Kindly see the logs and request you to kindly help us how it will resolve this issue.
Regards,
JitendraWe have made a system copy from Production to Quality
After client copy sap schema had been changed thats why its not connecting.
fyi: Client copy and system copy both are different
schema had been changed thats why its not connecting
This is one of the post installation step after doing a system copy(reffer the ssytem copy guide)
Problem has resolved
Great, suggest you to close this thread
Regards,
Nick Loy -
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.
<br>
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.
<br>
We are again getting error in following steps:
<br>
sapinst.log
<br>
<br>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<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
<br>Loading of 'SAPNTAB' import package: OK
<br>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.<br>
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
<br>
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,
<br>
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 .
<br>
<br>import_monitor.log.
<br>****************************************************************************************************************************************************
<br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
<br>
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
<br>
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
<br>
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.
<br>*************************************************************************************************************************************************
<br>SAPAPPL02.LOG
<br>**************************************************************************************************************************************************
<br>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
<br>
(DB) INFO: TVV1 deleted/truncated #20091001110304
<br>
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
<br>
(DB) ERROR: DDL statement failed<br>
(ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
DbSlExecute: rc = 99<br>
(SQL error -539)<br>
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,
PrasadHello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
<br>
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.
<br>
We are again getting error in following steps:
<br>
sapinst.log
<br>
<br>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<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
<br>Loading of 'SAPNTAB' import package: OK
<br>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.<br>
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
<br>
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,
<br>
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 .
<br>
<br>import_monitor.log.
<br>****************************************************************************************************************************************************
<br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
<br>
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
<br>
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
<br>
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.
<br>*************************************************************************************************************************************************
<br>SAPAPPL02.LOG
<br>**************************************************************************************************************************************************
<br>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
<br>
(DB) INFO: TVV1 deleted/truncated #20091001110304
<br>
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
<br>
(DB) ERROR: DDL statement failed<br>
(ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
DbSlExecute: rc = 99<br>
(SQL error -539)<br>
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 -
Hi Board,
i´ve search across the board, technet and symantec sites but did not found a hint about my problem.
we drive a 2 node DAG (Location1-Ex1-mb1
Location2-exc1-mb1), on SP2 RU4 patchlevel with 40 Databases.
Since some time the backup of one - and only one DB - is failing with these events, logged on the Mailboxserver on which the passive DB is hosted.
Log Name: Application
Source: MSExchangeRepl
Date: 28.09.2012 00:37:17
Event ID: 2112
Task Category: Exchange VSS Writer
Level: Error
Keywords: Classic
User: N/A
Computer: Location1-Exc1-MB1
Description: The Microsoft Exchange Replication service VSS Writer instance 1ab7d204-609a-4aea-b0a7-70afb0db38de failed with error code 80070020 when preparing for a backup of database 'DB012'.
Followed by
Log Name: Application
Source: MSExchangeRepl
Date:
01.10.2012 03:33:06
Event ID: 2024
Task Category: Exchange VSS Writer
Level: Error
Keywords: Classic
User:
N/A
Computer: Location1-Exc1-MB1
Description:
The Microsoft Exchange Replication service VSS Writer (Instance 42916d80-36c1-4f73-86d0-596d30226349) failed with error 80070020 when preparing for a backup.
The backup Application - Symantec Backup Exec 2010 R3 – states, this error
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Check the Windows Event Viewer for details.
Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).
Symatec suggests within http://www.symantec.com/business/support/index?page=content&id=TECH184095
to restart the MS Exchange Replication Service – BUT the mentioned eventID
8229 isn´t present on any of the both Mailboxservers.
The affected Database is active on Location2-Exc1-Mb1 Server and in an overall healthy state. I found during my research, that below Location2-Exc1-Mb1 Server, there are not removed shadow copies present!
This confuses me, since all Backups are normally taken from the passive copy of a Database.
So my questions to the board are:
* Does anyone is facing similar issues?
* Can someone explain why snapshots are present on the Mailboxserver hosting the Active Database, whilst the errors are logged on the passive one?
- * Does someone know the conditions, why shadows copies remain and
aren´t removed in a proper manner?
What can cause the circumstance, that only 1 DB is facing such issues?
Any suggestion is welcome!
BR
MarkusHi Lenora,
I´ve encreases VSS / Exchange Backup Log levels to expert, before starting
those things i´ve all tried now:
- Backup from passive DB (forced within Symantec Backup Exec)
- Backup from active DB (forced within Symantec Backup Exec)
- Backup from passive DB without GRT enabled (forced within Symantec Backup Exec)
- Backup from active DB without GRT enabled(forced within Symantec Backup Exec)
All those attempts failed.
But brought some more details - the backup against the active DB states, that there is still a backup in progress and therefore this backup is cancelled by VSS.
The Solution was, that i´ve needed to restart the Exchange Replication Service on the Mailbox Server hosting the passive DB.
Backups are working again on all DBs!
THX for your replys.
Best regards
Markus -
Failed to execute with the error Error occurred when starting the parser: t
Dear All
I am getting this error
""A database error occurred. The database error text is: The MDX query SELECT { [DASKA1EDEL2DMLXTQ62S595QV].[DB7BP4A8AMQTUD3DPEEPS4J87] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CALMONTH].[LEVEL01].MEMBERS, [DASKFZ1TRFOLNTG78G0HH2B87].MEMBERS ), [0MATERIAL].[LEVEL01].MEMBERS ), [0PLANT].[LEVEL01].MEMBERS ), [0COMP_CODE].[LEVEL01].MEMBERS ), [0ACTDELDATE].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES MEMBER_NAME, MEMBER_CAPTION ON ROWS FROM [0IC_C03/ZMATSTOCK] failed to execute with the error Error occurred when starting the parser: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'. (WIS 10901)""
I already went to similar kind of error solution in forum,but this error is coming for one web I query,all other reports are working fine.
I already implemented note 1032461Hi,
Under normal circumstances it should be enough to restart the connection service.
As far as we know there is no formal solution to this problem from SAP yet but restarting the connection service is much less of an interuption compared to restarting the the SIA.
Re-starting the connection service should resolve this issue. since, Connection service is only related to DeskI and Rich Client re-statrng wonu2019t impact other business objects components including java report panel.
All the Best,
Madhu.... -
Hello. I am receiving "error codes" when trying to dowload songs. It charges me but the songs never download and I have restarted itunes and it does not automatically start downloading as instructed online. Help?
I don't know exactly what they said b/c they are nolonger on my screen. It said something to the effect of "incomplete dowload, there was an eror during the dowload of *Song*".
The songs purchased were showing in my purchased list with an "exclamation point" by them, which I believe indicates the download was incomplete. I restarted iTunes and the songs are no longer on my "Purchased list".
I was still charged after restarting iTunes -
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 dasHello 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. -
I have plugged my iphone 5s into windows computer, the computer picks up that its there and starts charging but keeps coming up with error message when i try connect to itunes... HELP!!!
What does the error message say? (Precise text, please.)
-
My itouch is disabled, when I tried to restore it, it came up with Error code 3094. Has anyone had this error code appear for them before and how were they able to fix it?
Thank YouSee SIMPLE easy solution for 1015 3094 3014 21 error
-
My CS can't start with error code 16
How can I find the CS5.5 serial number under MAC OS X if I want to reinstall it? My CS can't start with error code 16, it says configuration error.
Please refer the KB Doc : http://helpx.adobe.com/x-productkb/policy-pricing/configuration-error- cs5.html
-
Message "Error 4 when starting extraction program" with any extraction.
Hi to everyone.
We have a problem in a pre-existing BW system of development.
When we start any extraction (for example 0MATERIAL_ATTR), the monitor give us the following error:
ERROR 4 WHEN STARTING THE EXTRACTION PROGRAM (R3-19).
I've checked the link between the two system, and it may be right. When I check the soursystem from BW I havn't any error.
Then, when I test the extractor on R/3 with RSA3, any error as result and the tester extracts a lot of records.
Anyone have any idea ?
MaxThanks for your fast help.
Claudio, the messages are only two ...
- Error 4 when starting the extraction program
R3 19
- Errors in source system RSM 340
No dump on the R/3 and BW.
Roberto, I've followed the note 325470 too, but the problem remain. Only one ... the note 147104 say ...
"This server must be capable of starting a background process for data extraction".
Is there a way to check this point ?
Thanks in advance guys.
Max -
Error 16 code when starting up CS5, all I can do is uninstall and reinstall. How to fix this?
Hi Looze,
System information would really help as suggested by Mylenium . I would also recommend going through the below mentioned Kb article to see if that resolves the query.
Configuration error 16 | CC, CS
Cheers,
Kartikay Sharma
Maybe you are looking for
-
How to use multiple drop down lists and do not allow duplicates.
I am creating a roster that has multiple positions on multiple pages. I have a drop-down list that is populated with all of the employees and want to make sure that the same employee cannot be selected for multiple posts. Ideally, when one is selecte
-
hi gurus help me . in ge extraction we have delta loads as . 1. time stamp.2.calenday . 3. numericpointer. can u provide details in which situations we use this parameters .and what exactly these are uesd for induvidually
-
How to use case when function to calculate time ?
Dear All, May i know how to use case when function to calculate the time ? for the example , if the First_EP_scan_time is 12.30, then must minus 30 min. CASE WHEN FIRSTSCAN.EP_SHIFT <> 'R1' AND FIRSTSCAN.EP_SHIFT <> 'R2' THEN ROUND(CAST((DATEDIFF(
-
Transferring pc to macbook pro
I need help transferring all my photos and information from my hp pc onto my new macbook pro please.
-
I have a normal KM Navigation iView watching a KM folder path. This folder has an excel file in it. When the end user clicks the excel file, it prompts to Open, Save or Cancel as normal. Choosing Save works as expected. Choosing Open works as expecte