Error updating SAP kernel to 7.01(32 bits)
Hi experts,
I update our Solution manager kernel to 7.01 but fail when starting sapstartsrv.exe. The error message is "error 14001: this application has failed to start becuase the application configration is
incorrect. reinstalling the appliaction map fix this problem". I could run with 7.00 and 7.10 without any problem. Please help.
Hi,
This error generally happens due to missing Visual C++ runtime components. You have to execute a package vcredist.exe to fix this. You can refer the MS article (http://support.microsoft.com/kb/259403) for more information and for downloading the exe file. After executing the exe file, try starting sapstartsrv.exe again.
But before performing the above step, try replacing the sapstartsrv.exe under the Kernel directory from some other Kernel. May be sapstartsrv.exe is corrupt. But most probably you have to follow the first step which I explained. Let me know if this resolves the problem.
Thanks,
Varun
Similar Messages
-
Hello!
We are trying to find out why our cluster has a fail over every couple of days on a ressource. So we updated the kernel last week, but the problem is still there. We also learned today that there is more than one kernel folder on the windows server machine:
1) i:\usr\sap\prd\sys\exe\uc\ntamd64 (the one we updated)
2) c:\windows\sapcluster (here are some exe files, all outdated)
3) c:\usr\sap\prd\d01\exe (seems to be a copy of 1)
How important is 2)?
regards, PeterHi,
When updating the kernel it is important to update also the sapcluster folder but I don't think this is an explanation for the lost I: drive. You should ask your SAN team to investigate on the subject.
Regards,
Olivier -
J2ee startup (errors) after SAP kernel upgrade
Guys,
Not sure if anyone has seen this before, I have read the forums, and seen simular, but not exactly the same....
When trying to start the j2ee engine (add-in installation) the dev_jcontrol file contains the following error;
[Thr 01] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/EBG/SYS/exe/run//usr/sap/EBG/DVEBMGS00/exe/sapjvm_5/l
ib/jvmx.jar
[Thr 01] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/EBG/SYS/exe/run//usr/sap/EBG/DVEBMGS00/exe/sapjvm_5/j
re/lib/iqlib.jar
this has only just started occurring since applying the latest kernel patch. We have not installed the SAPJVM, but the framework properties seem to be looking for this. Can the framework settings be changed, and if so where?
AdeHello,
check j2ee rdbms driver location
Regards
Renato -
Update SAP kernel in UNIX based
I got a document for kernel update in UNIX based machine .Hereunder I pasted the steps ..In this am not able to understand step 4..Anybody please clarify it how can we compare the original kernel and the backup ..what is 840413 and 841992..Any mistake in the command.Please clarify the command of step4 for AIX .
1. Login as root
2. Make new backup directory
cd /
mkdir SIDkernel_10102007
3. Create latest kernel backup
cp -pr /sapmnt/SID/exe/* /SIDkernel_10102007
4. Compare the original kernel and the backup
du -sk /sapmnt/SID/exe/ --> 840413 /sapmnt/SID/exe
du -sk /SIDkernel_10102007 --> 841992 /SIDkernel_10102007
5. Make new shadow kernel directory
cd /
mkdir newkernel_175
6. Copy the new downloaded kernel files into /newkernel_175
7. Unpack the new downloaded kernel in folder /newkernel_175
SAPCAR -xvf SAPEXE_175-20000221.SAR
SAPCAR -xvf SAPEXEDB_175-20000223.SAR
8. Login as sidadm
9. Stop the SAP System
stopsap
10. Stop saposcol
saposcol -k
11. Login as root
12. Go to the current kernel directory
cd /sapmnt/SID/exe
13. Copy all extracted support packages into this folder
cp -pr /newkernel_175/* /sapmnt/SID/exe
14. Copy back the original file saproot.sh into this folder.
cp -p /SIDkernel_10102007/saproot.sh /sapmnt/SID/exe
15. Go to the current kernel directory
cd /sapmnt/SID/exe
Then run:
./saproot.sh SID
16. Login as sidadm
17. Start the saposcol service
saposcol
18. Start the SAP system
startsap
Thanks in advance> 4. Compare the original kernel and the backup
> du -sk /sapmnt/SID/exe/ --> 840413 /sapmnt/SID/exe
> du -sk /SIDkernel_10102007 --> 841992 /SIDkernel_10102007
On Unix system you can get help for specific commands by using
man <commandname>
If you execute "man du" you will see, that "du" means "disk usage" and options "-s" and "-k" means "sum of directory" and "in kilobyte". The numbers are the sizes of the directories.
Markus -
DB13 Job running error after upgate kernel patch
Dear Gurus,
I update sap kernel patch from level 159 to level 236 on QAS and DEV
and then, all DB job on DB13 error occure.
<br>
21.02.2010 07:00:47 Job started <br>
21.02.2010 07:00:47 Step 001 started (program RSDBAJOB, variant &0000000000014, user ID SAP*) <br>
21.02.2010 07:00:47 Execute logical command BRCONNECT On host eccqas <br>
21.02.2010 07:00:47 Parameters: -u / -jid CLNUP20081026070000 -c -f cleanup <br>
21.02.2010 07:00:48 > Function: BtcXpgPanicCan't exec external program (No such file or directory) <br>
21.02.2010 07:00:48 External program terminated with exit code 1 <br>
21.02.2010 07:00:48 BRCONNECT returned error status E <br>
21.02.2010 07:00:48 Job finished <br>
<br>
21.02.2010 20:00:48 Job started
21.02.2010 20:00:48 Step 001 started (program RSDBAJOB, variant &0000000000019, user ID SAP*)
21.02.2010 20:00:48 Execute logical command BRCONNECT On host eccqas
21.02.2010 20:00:48 Parameters: -u / -jid STATS20081026200000 -c -f stats -t ALL
21.02.2010 20:00:49 > Function: BtcXpgPanicCan't exec external program (No such file or directory)
21.02.2010 20:00:49 External program terminated with exit code 1
21.02.2010 20:00:49 BRCONNECT returned error status E
21.02.2010 20:00:49 Job finished
<br>
System : ECC 6.0 OS: Solaris DB Oracle 10g
Best regards,Hi,
Please ensure that sapxpg executable is located in your SAP Kernel directory where you have applied new kernel.
Whats the permission of sapxpg executable ? Check them.
Also check SM21 , dev_sapxpg and the required Work Process traces along with the testing of SAPXPG_DBDEST_<hostname> RFC. This will be helpful in finding the possible causes for the same.
Please refer this[ useful thread|DB 13 (CHECKDB) Can't exec external program (No such file or directory)] which is describing the same symptoms along with this [informative link|http://help.sap.com/saphelp_47x200/helpdata/en/c4/3a80c4505211d189550000e829fbbd/content.htm].
Regards,
Bhavik G. Shroff -
Not able to increase SAP kernel release 6.40 patch level from 43 to 71
Hi Guru's,
I have to update SAP kernel release 6.40 patch level from 43 to 71 but not able to do.I am running solution manager 3.2 on Oracle 9i and Win-2003 OS.
Please provide the solutions .
I have downloaded kernel patch from Path at Service matket place ---<b>Support Packages and Patches" SAP Technology Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 3.2" Entry by Component" SAP Solution Manager-SAP KERNEL 6.40 32-BIT UNICODE-Windows Server on IA32 32bit-ORACLE-
SAR SAPEXEDB_71-20000254.SAR Kernel Part II (for Basis 640/620) 71</b>
I followed following Steps:
1. Copied the patch into a temporary directory on system.
2. Unpacked the downloded SAPEXEDB_71-20000254.SAR Kernel Part II (for Basis 640/620) 71 patch .
3. Stoped the SAP System using MMC.
4. Saved the kernel directory by backup or by copying into a separate backup directory. (\usr\sap\<SAPSID>\sys\exe\run)
5. Re-started the server.
After logging again in SAP client 000 on checking found server patch level coming same as previous one .
Its not got updated and due to this in Tcode- <b>SPAM</b> I am getting error message :<b>'The OCS package SAPKITL318 requires a kernel with Release 640 and patch number 71. The kernel you are currently using has a lower version.'</b>.
Help!!!!
Regards
GauravHi Guru's,
Output for transaction SM51 enclosed below:
Application server gauravpc1_GSM_00
SAP R/3 Kernel information
SAP R/3 Kernel 640_REL
Database Client Library OCI_920_SHARE
created in NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10
created on Nov 4 2004 23:42:53
Support Level 0
Kernel Patch number 43
Source ID 0.043
DBSL Patch No. 172
ICU Version 2.6.1 Unicode Version 4.0
libsapu16 Version 2.0023 Nov 4 2004 20:04:27
Supported environment
SAP database version
610 , 620 , 630, 640
Database ORACLE 9.2.0..
ORACLE 10.1.0..
ORACLE 10.2.0..
Operating system
Windows NT 5.0, Windows NT 5.1,Windows NT 5.2
one more thing I have aloso tried to upload Kernel latest patch level 175 using same procedure but that too was not working.
HELP!!!!!!!!!!!!!
Regards -
Hello everyone,
Yesterday (April 30, 2015) SAP released the new patch 500 for SAP KERNEL 7.21 EXT 64-bit.
I am using Download Manager and I was able to download the Kernel Part II (DB-Dependent) .SAR file and other files as you can see in the screenshot, but for the Kernel Part I and disp+work files I get the error: "You are not authorized to download selected object".
On the other hand, I am able to download older versions of the Kernel Part I (SAPEXE_XXX.SAR).
Is this a technical problem on SAP side (SMP)? Did anyone encounter the same issue and found a solution?
Thanks.
BR,
MichelHello Michel,
Kernel Patch 500 is yet to release, to the customer.
Have a look at the below blog.
Surprise for Kernel version 7.21 patch level 500 !
Hope the above one helps.
regards,
pavan -
Error during sap r/3 installation at update databse statistics
Hi friends,
I am getting an error during sap r/3 installation almost at the last stage.
the error is at update database statistics.
my configuration is
os: windows 2000 server.
d/b: oracle 9i.
erp: sap 4.7 ee
During oracle installation stage the oui is asking for create a database, i am chechking it ok. Is that a problem ?.
I am sending the log file. Please can anybody help me, where i am going wrong-
The log file----
Click Browse and give location of export1, as shown in the bellow figure
INFO 2007-02-04 21:46:32
Creating directory D:\oracle\DRS\sapdata4\drs620_5.
INFO 2007-02-04 21:46:32
Creating file system node D:\oracle\DRS/sapdata4\drs620_5 with type DIRECTORY succeeded.
INFO 2007-02-04 21:46:32
Creating directory D:\oracle\DRS\sapdata5\drs620_6.
INFO 2007-02-04 21:46:32
Creating file system node D:\oracle\DRS/sapdata5\drs620_6 with type DIRECTORY succeeded.
INFO 2007-02-04 21:46:32
Creating directory D:\oracle\DRS\sapdata5\drs620_7.
INFO 2007-02-04 21:46:32
Creating file system node D:\oracle\DRS/sapdata5\drs620_7 with type DIRECTORY succeeded.
INFO 2007-02-04 21:46:32
Creating directory D:\oracle\DRS\sapdata6\drs620_8.
INFO 2007-02-04 21:46:32
Creating file system node D:\oracle\DRS/sapdata6\drs620_8 with type DIRECTORY succeeded.
INFO 2007-02-04 21:46:32
Creating directory D:\oracle\DRS\sapdata6\drs620_9.
INFO 2007-02-04 21:46:32
Creating file system node D:\oracle\DRS/sapdata6\drs620_9 with type DIRECTORY succeeded.
INFO 2007-02-04 21:46:32
Creating directory D:\oracle\DRS\sapdata6\drsusr_1.
INFO 2007-02-04 21:46:32
Creating file system node D:\oracle\DRS/sapdata6\drsusr_1 with type DIRECTORY succeeded.
INFO 2007-02-04 21:46:32
Creating directory D:\oracle\DRS\sapdata2\roll_1.
INFO 2007-02-04 21:46:32
Creating file system node D:\oracle\DRS/sapdata2\roll_1 with type DIRECTORY succeeded.
INFO 2007-02-04 21:46:32
Creating directory D:\oracle\DRS\sapdata3\temp_1.
INFO 2007-02-04 21:46:32
Creating file system node D:\oracle\DRS/sapdata3\temp_1 with type DIRECTORY succeeded.
INFO 2007-02-04 21:46:32
Creating directory D:\oracle\DRS\sapdata1\system_1.
INFO 2007-02-04 21:46:32
Creating file system node D:\oracle\DRS/sapdata1\system_1 with type DIRECTORY succeeded.
INFO 2007-02-04 21:46:32
Processing of all file system node operations of table tORA_SapdataNodes succeeded.
INFO 2007-02-04 21:46:33
Processing of all file system node operations of table tORA_DatabaseServerNodes succeeded.
INFO 2007-02-04 21:46:34
Processing of all file system node operations of table tORA_SapdataNodes succeeded.
INFO 2007-02-04 21:46:35
Creating file c:\oracle\ora90\database\initDRS.ora.
INFO 2007-02-04 21:46:36
Creating file C:\oracle\ora90\database\initDRS.sap.
INFO 2007-02-04 21:46:37
Copying file F:/sap4.7/ker/NT/COMMON/INSTALL/INITSID.DBA to: c:\oracle\ora90/database/initDRS.dba.
INFO 2007-02-04 21:46:37
Creating file c:\oracle\ora90\database\initDRS.dba.
INFO 2007-02-04 21:46:38
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 21:46:39
Moving file c:/oracle/ora90/database/initDRS.ora to: orig_init_ora_tmp.txt.
INFO 2007-02-04 21:46:39
Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: c:\oracle\ora90\database\initDRS.ora.
INFO 2007-02-04 21:46:39
Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
INFO 2007-02-04 21:46:40
Creating file C:\SAPinst ORACLE KERNEL\oradim.log.
INFO 2007-02-04 21:46:45
See 'c:\oracle\ora90/bin/oradim -new -sid DRS -STARTMODE auto' output in 'C:\SAPinst ORACLE KERNEL\oradim.log'.
INFO 2007-02-04 21:46:45
'c:\oracle\ora90/bin/oradim -new -sid DRS -STARTMODE auto' returned with '0'.
INFO 2007-02-04 21:46:46
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 21:46:49
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 21:59:57
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:00:00
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:00:44
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:00:46
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:01:31
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:01:34
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:02:18
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:02:20
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:03:06
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:03:09
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:03:55
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:03:57
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:04:44
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:04:46
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:05:32
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:05:35
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:06:21
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:06:23
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:07:10
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:07:12
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:07:58
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:08:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:08:48
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:08:50
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:09:38
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:09:40
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:09:44
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:09:46
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:10:06
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:10:09
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:10:39
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:10:41
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:10:44
Moving file c:/oracle/ora90/database/initDRS.ora to: orig_init_ora_tmp.txt.
INFO 2007-02-04 22:10:44
Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: c:\oracle\ora90\database\initDRS.ora.
INFO 2007-02-04 22:10:44
Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
INFO 2007-02-04 22:10:45
Creating file C:\SAPinst ORACLE KERNEL\lsnrctl.log.
INFO 2007-02-04 22:10:46
See 'c:\oracle\ora90/bin/lsnrctl stat' output in 'C:\SAPinst ORACLE KERNEL\lsnrctl.log'.
INFO 2007-02-04 22:10:46
'c:\oracle\ora90/bin/lsnrctl stat' returned with '3'.
INFO 2007-02-04 22:10:46
Creating file C:\SAPinst ORACLE KERNEL\lsnrctl.log.
INFO 2007-02-04 22:10:48
See 'c:\oracle\ora90/bin/lsnrctl start' output in 'C:\SAPinst ORACLE KERNEL\lsnrctl.log'.
INFO 2007-02-04 22:10:48
'c:\oracle\ora90/bin/lsnrctl start' returned with '0'.
INFO 2007-02-04 22:10:48
Copying file F:/sap4.7/ker/NT/COMMON/INSTALL/ORADBUSR.SQL to: ./oradbusr.sql.
INFO 2007-02-04 22:10:48
Creating file C:\SAPinst ORACLE KERNEL\oradbusr.sql.
INFO 2007-02-04 22:10:49
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:10:52
Changed working directory to C:\SAPinst ORACLE KERNEL.
PHASE 2007-02-04 22:10:54
Database Load
INFO 2007-02-04 22:10:58
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:10:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:00
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:02
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:02
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:02
Task files created
INFO 2007-02-04 22:11:03
Command files created
INFO 2007-02-04 22:11:05
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:05
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-04 22:11:05
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 00:06:44
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 03:43:19
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 04:55:23
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 05:17:24
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 05:39:25
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 05:45:25
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 05:57:26
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:00:26
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:03:26
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:05:26
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:07:26
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:08:27
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:09:28
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:24:46
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:24:46
Processes finished successfully
INFO 2007-02-05 06:26:23
Creating file C:\SAPinst ORACLE KERNEL\ddicora.sql.
INFO 2007-02-05 06:26:25
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:26:30
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:26:32
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:26:43
Moving file c:/oracle/ora90/database/initDRS.ora to: orig_init_ora_tmp.txt.
INFO 2007-02-05 06:26:43
Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: c:\oracle\ora90\database\initDRS.ora.
INFO 2007-02-05 06:26:43
Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
INFO 2007-02-05 06:26:43
Moving file c:/oracle/ora90/database/initDRS.ora to: orig_init_ora_tmp.txt.
INFO 2007-02-05 06:26:43
Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: c:\oracle\ora90\database\initDRS.ora.
INFO 2007-02-05 06:26:43
Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
INFO 2007-02-05 06:26:43
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:26:45
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:26:48
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:26:52
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:26:55
Creating file C:\SAPinst ORACLE KERNEL\brconnect.log.
INFO 2007-02-05 06:26:55
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-02-05 06:26:55
See 'D:\usr\sap\DRS\SYS\exe\run/brconnect -c -f crsyn -o SAPDRS' output in 'C:\SAPinst ORACLE KERNEL\brconnect.log'.
ERROR 2007-02-05 06:26:55
MOS-01012 PROBLEM: 'D:\usr\sap\DRS\SYS\exe\run/brconnect -c -f crsyn -o SAPDRS' returned with '128' which is not a defined as a success code.
ERROR 2007-02-05 06:26:55
FJS-00012 Error when executing script.
kindly help me where i am going wrong.
Yours friendly,
Bharath.Hi Andreas,
many thanks to you for the timely help.
a.)I want to know why there is an error at brconnect ? why is it returning an error code (128) at UPDATE DATABASE STATISTICS stage.
I have read in this forum itself that the UPDATE STATISTICS need not be suceesfully completed and we can edit database.r3s
" ..on the other hand you can easily invoke the update statistics after the installation has ended (succesfully!)...edit DATABASE.R3S (or the appropriate template file you are using) by changing the status=ERROR to status=OK...this will let you finish the installation..-GreetZ, AH."
I have searched for this file (database.r3s) in my system in vain Where can i find this file database.r3s?.
Have i done any configuration mistake at the pre-installation stage. I have installed Oracle 9.0 using setup.exe of oracle. should i use sapserver.cmd to install oracle?.I havent applied any patch for Oracle 9.0
Should I apply any patch just the same way we do for Oracle 8.1.x ?. If so, where can i get the patch for Oracle 9.0 .?.
b.) You said there should not be any spaces in file path (ex: C:/SAPinst ORACLE KERNEL/) . But I havent specified file path, the r/3 setup itself has created the directory path.
c.) I want to know one thing- should we create a database before installing r/3. When we are installing Oracle 8/9. x what are the components that we are installing?
Your friend,
Bharath. -
Error on SAP ECC 6.0 Update to EHP2
Hi Guru's,
I encountered below errors while to update SAP ECC 6.0 to EHP2 :
Error in phase: XPRA_EXECUTION
- Reason for error: TP_STEP_FAILURE
- Return code: 0012
- Error message: OCS Package SAPK-602DWINSAPAPPL, tp step R,
return code 0012
Dump message : st22 :
Error in the ABAP Application program
The current ABAP program "CL_FDT_FACTORY=====================CP" had to terminated because it has come accross a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_FDT_FUNCTION===========CP" in include
"CL_FDT_FUNCTION===========CM017" in line 57.
"The method "IS_GENERATING" does not have RETURNING parameter."
Kindly help on this. Thanks in advance.
GunaHi Guna,
maybe note [1083886|https://service.sap.com/sap/support/notes/1083886]?
One comment: For EHP2, please mind note [1052522|https://service.sap.com/sap/support/notes/1052522] and use an equivalent support package stack to your ECC 6.0 installation. EHP2/SPS02 as a minimum, higher even better.
Best regards,
Christoph
Edited by: Christoph Vehns on Feb 2, 2009 8:45 AM
Edited by: Christoph Vehns on Feb 2, 2009 8:45 AM -
Hi all
I updated my kernel from 160 to 175
When i log into SAP and execute SM51 it still shows 160 as the kernel patch level ????????
The SAR files are correct because i used the same files to update DEV and QA. and the same process.
The serve is not part of a cluster either.
Any ideas ??
Thanx in advancehmmmmmmmm i see
what did i do wrong
disp+work
disp+work information
kernel release 700
kernel make variant 700_REL
compiled on AIX 2 5 005DD9CD4C00
compiled for 64 BIT
compilation mode Non-Unicode
compile time May 13 2008 21:10:31
update level 0
patch number 160
source id 0.160
supported environment
database (SAP, table SVERS) 700
operating system
AIX 1 5
AIX 2 5
AIX 3 5
AIX 1 6 -
SAP Kernel update with HANA DATABASE
Dear experts,
I am planning to update the kernel with HANA database. It is my first time that I apply a kernel with HANA and for that reason I want to be sure everything is properly planned. I have updated kernel with Oracle databases and my biggest doubt is if I have to do something in the database, what would it be?
I have looking for any note that help me with a step by step but I couldn't find it. In that order I will ask you based on your own experiences.
Current Kernel is 742 PL28, I am planning to update to PL 101.
I appreciate any comments or suggestions,
Best regards,
DanielODear Reagan,
As you told, the kernel was applied and I had no issues. I appreciatte your help.
Best regards,
DanielO -
Hello,
I've got a null pointer in the SAP conector. What could be the problem?
Thanks.
LOG
2011-07-18 11:59:10,065 INFO [XL_INTG.SAPUSERMANAGEMENT] ***** Starting SAP User Reconciliation *****
2011-07-18 11:59:10,076 INFO [XL_INTG.SAPUSERMANAGEMENT] ***** Starting SAP INIT ******************************
2011-07-18 11:59:10,077 INFO [XL_INTG.SAPUSERMANAGEMENT] number of batches = all available.
2011-07-18 11:59:10,077 INFO [XL_INTG.SAPUSERMANAGEMENT] Resource ObjectSAP8 SRM
2011-07-18 11:59:10,077 INFO [XL_INTG.SAPUSERMANAGEMENT] *************** SAP INIT Ends******************************
2011-07-18 11:59:10,077 INFO [XL_INTG.SAPUSERMANAGEMENT] ***** Start EXECUTE Method*****
2011-07-18 11:59:10,077 INFO [XL_INTG.SAPUSERMANAGEMENT] Resource ObjectSAP8 SRM
2011-07-18 11:59:10,085 INFO [XL_INTG.SAPUSERMANAGEMENT] customQuery is userid=OIM_01
2011-07-18 11:59:10,085 INFO [XL_INTG.SAPUSERMANAGEMENT] parameters are [USERID;OIM_01]
2011-07-18 11:59:10,085 INFO [XL_INTG.SAPUSERMANAGEMENT] operators are []
2011-07-18 11:59:10,085 INFO [XL_INTG.SAPUSERMANAGEMENT] SAP Create Connection Request
2011-07-18 11:59:10,085 INFO [XL_INTG.SAPUSERMANAGEMENT] START SAP Connection creation.
2011-07-18 11:59:10,085 INFO [XL_INTG.SAPUSERMANAGEMENT] After Create Client
2011-07-18 11:59:10,099 INFO [XL_INTG.SAPUSERMANAGEMENT] SAP Connection creation successfull.
2011-07-18 11:59:10,099 INFO [XL_INTG.SAPUSERMANAGEMENT] handleRegularRecon method is started
2011-07-18 11:59:10,099 INFO [XL_INTG.SAPUSERMANAGEMENT] processChange method is started
2011-07-18 11:59:10,099 INFO [XL_INTG.SAPUSERMANAGEMENT] Recon From Date:Mon Jul 18 11:50:46 CEST 2011
2011-07-18 11:59:10,099 INFO [XL_INTG.SAPUSERMANAGEMENT] Recon To Date:Mon Jul 18 11:59:10 CEST 2011
2011-07-18 11:59:10,099 INFO [XL_INTG.SAPUSERMANAGEMENT] Recon From Time:Mon Jul 18 11:50:46 CEST 2011
2011-07-18 11:59:10,100 INFO [XL_INTG.SAPUSERMANAGEMENT] Recon To Time:Mon Jul 18 11:59:10 CEST 2011
2011-07-18 11:59:10,105 ERROR [XL_INTG.SAPUSERMANAGEMENT] ProxyUserReconManager: java.lang.NullPointerException
at com.sap.mw.jco.JCO$Function.<init>(JCO.java:18075)
at com.thortech.xl.integration.sap.proxy.SAPProxyUserReconManager.processChange(SAPProxyUserReconManager.java:156)
at com.thortech.xl.integration.sap.proxy.SAPProxyUserReconManager.handleRegularRecon(SAPProxyUserReconManager.java:549)
at com.thortech.xl.schedule.tasks.SAPUserRecon.execute(SAPUserRecon.java:368)
at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.run(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
at Thor.API.Security.LoginHandler.jbossLoginSession.runAs(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
2011-07-18 11:59:10,105 INFO [XL_INTG.SAPUSERMANAGEMENT] handleRegularRecon method ends
2011-07-18 11:59:10,105 INFO [XL_INTG.SAPUSERMANAGEMENT] No of modified users for SAP SAP8 R3 IT Resource:0
2011-07-18 11:59:10,244 INFO [XL_INTG.SAPUSERMANAGEMENT] START SAP Connection Close.
2011-07-18 11:59:10,255 INFO [XL_INTG.SAPUSERMANAGEMENT] SAP Connection Close successfull.
2011-07-18 11:59:10,255 INFO [XL_INTG.SAPUSERMANAGEMENT] Reconciliation is completed for :SAP8 R3 IT Resource
2011-07-18 11:59:10,293 INFO [XL_INTG.SAPUSERMANAGEMENT] START SAP Connection Close.
2011-07-18 11:59:10,293 INFO [XL_INTG.SAPUSERMANAGEMENT] SAP Connection Close successfull.Update SAP OIM add-on
-
Error Updating WAS SP13 -- SPS18, Phase Deploy Online: SAPJTECHS18_0.SCA
hello,
I can not update SAP WAS Java SP13 to SPS18. I get an error message during phase "deploy online" (18 of 24). see the error message and log below.
Previous to running the update I successfully run the WAS SP18 Prerequisite Check based on "WAS-PREREQUISITE_CHECK_DATA_640.XML" downloaded at 2006-08-24 without any warnings or errors.
I used sapcar 6.40 patchlevel 4, I extracted the following downloaded files in this order:
sapcar -xvf SAPINST18_0-20000118.SAR -R NW04-WebASJava-18
sapcar -xvf CTRLMSS18_0-20000118.SAR -R NW04-WebASJava-18
sapcar -xvf J2EERT18_0-10001982.SAR -R NW04-WebASJava-18
sapcar -xvf J2EERTOS18_0-20000118.SAR -R NW04-WebASJava-18
for any help I would be very greatful.
thanks, volker.
WARNING 2006-08-25 01:42:13
Execution of the command "C:\j2sdk1.4.2_12/bin/java.exe '-Xmx256M' '-jar' 'C:\usr\sap/J2E/JC00/SDM/program/bin/SDM.jar' 'deploy' 'list=C:\Program Files\sapinst_instdir\PATCH\MSS/SDAS_TO_BE_DEPLOYED.LST' 'onerror=stop' 'sdmhome=C:\usr\sap/J2E/JC00/SDM/program' 'logfile=C:\Program Files\sapinst_instdir\PATCH\MSS/callSdmViaSapinst.log' 'logtoconsole=true'" finished with return code 4. Output: Info: Info: ============================================Info: = Starting to execute command 'deploy' =Info: ============================================Info: Starting SDM - Software Deployment Manager...Starting SDM - Software Deployment Manager...Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000Info: SDM operation mode successfully set to: StandaloneInitializing Network Manager (50017)Info: Initializing Network Manager (50017)Checking if another SDM is running on port 50018Info: Checking if another SDM is running on port 50018Info: -
Starting deployment -
Info: Error handling strategy: OnErrorStopInfo: Prerequisite error handling strategy: OnPrerequisiteErrorStopInfo: Update strategy: UpdateLowerVersionsInfo: Starting deployment prerequisites:Info: Loading selected archives...Info: Loading archive 'S:\SAP\Downloads\200608\NW04-WebASJava-18\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'Info: Selected archives successfully loaded.Info: Actions per selected component:Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'0' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621161034.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.Info: Initial deployment: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' will be deployed.Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'0' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172955.0000'/'0'.Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621154902.0000'/'0'.Info: Update: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Initial deployment: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'0' will be deployed.Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050623162450.0000'/'0'.Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'0' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154156.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6. ...
ERROR 2006-08-25 01:42:13
MUT-02041 SDM call of deploySdaList ends with returncode 4. See output of logfile C:\Program Files\sapinst_instdir\PATCH\MSS\callSdmViaSapinst.log.
ERROR 2006-08-25 01:42:13
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
this is the contents of callSdmViaSapinst.log:
Aug 25, 2006 12:30:06... Info: Start logging to console
Aug 25, 2006 12:30:06... Info:
Aug 25, 2006 12:30:06... Info: ============================================
Aug 25, 2006 12:30:06... Info: = Starting to execute command 'deploy' =
Aug 25, 2006 12:30:06... Info: ============================================
Aug 25, 2006 12:30:06... Info: Starting SDM - Software Deployment Manager...
Aug 25, 2006 12:30:06... Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000
Aug 25, 2006 12:30:08... Info: SDM operation mode successfully set to: Standalone
Aug 25, 2006 12:30:08... Info: Initializing Network Manager (50017)
Aug 25, 2006 12:30:08... Info: Checking if another SDM is running on port 50018
Aug 25, 2006 12:30:08... Info: -
Starting deployment -
Aug 25, 2006 12:30:08... Info: Error handling strategy: OnErrorStop
Aug 25, 2006 12:30:08... Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Aug 25, 2006 12:30:08... Info: Update strategy: UpdateLowerVersions
Aug 25, 2006 12:30:08... Info: Starting deployment prerequisites:
Aug 25, 2006 12:30:11... Info: Loading selected archives...
Aug 25, 2006 12:30:11... Info: Loading archive 'S:\SAP\Downloads\200608\NW04-WebASJava-18\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'
Aug 25, 2006 12:30:16... Info: Selected archives successfully loaded.
Aug 25, 2006 12:30:18... Info: Actions per selected component:
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'0' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621161034.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Initial deployment: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' will be deployed.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'0' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172955.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621154902.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Initial deployment: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'0' will be deployed.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050623162450.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'0' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154156.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.
Aug 25, 2006 12:30:18... Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'0' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.13.0.20050720034335''/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818152118.0000'/'0' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163602.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'0' updates currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719161053.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'0' updates currently deployed development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050630075426.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050331133205.0000'/'0' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133205.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413100235.0000'/'0' updates currently deployed development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140206.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'0' updates currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050630075426.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818150135.0000'/'0' updates currently deployed development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154449.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111540.0000'/'0' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050624161235.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164103.0000'/'0' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164103.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119123705.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628142849.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4018.00.0000.20041104140331.0000'/'0' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140331.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:20... Info: Ending deployment prerequisites. All items are correct.
Aug 25, 2006 12:30:20... Info: Saved current Engine state.
Aug 25, 2006 12:30:20... Info: Starting: Update: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:20... Info: Creating connections to database "J2E".
Aug 25, 2006 12:30:20... Info: Creating vendor connection to database.
Aug 25, 2006 12:30:20... Info: Vendor connection created successfully.
Aug 25, 2006 12:30:20... Info: Creating openSQL connection to database.
Aug 25, 2006 12:30:21... Info: OpenSQL connection created successfully.
Aug 25, 2006 12:30:25... Info: <!LOGHEADER[START]/>
Aug 25, 2006 12:30:25... Info: <!HELP[Manual modification of the header may cause parsing problem!]/>
Aug 25, 2006 12:30:25... Info: <!LOGGINGVERSION[1.5.3.7186 - 630]/>
Aug 25, 2006 12:30:25... Info: <!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\jddilog20060825003021.log]/>
Aug 25, 2006 12:30:25... Info: <!PATTERN[jddilog20060825003021.log]/>
Aug 25, 2006 12:30:25... Info: <!FORMATTER[com.sap.dictionary.database.dbs.DbTraceFormatter(%s %m %-30l %24d)]/>
Aug 25, 2006 12:30:25... Info: <!ENCODING[Cp1252]/>
Aug 25, 2006 12:30:25... Info: <!LOGHEADER[END]/>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: $Id: //tc/DictionaryDatabase/630_VAL_REL/src/_dictionary_database_dbs/java/com/sap/dictionary/database/dbs/DbModificationManager.java#4 $
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBTABLERT >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBTABLERT >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTX >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTX >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: >>> Analysiere Tabellen aus dem Archiv auf Datenbank MSSQL
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: >>> Analysiere Tabellen aus dem Archiv auf Datenbank MSSQL
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ASSINST.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ASSINST.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ASSINST >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ASSINST >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ASSOC.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ASSOC.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ASSOC >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ASSOC >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_CHANGELOG.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_CHANGELOG.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_CHANGELOG >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_CHANGELOG >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_CLASS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_CLASS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_CLASS >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_CLASS >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_DELTAEXPORT.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_DELTAEXPORT.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_DELTAEXPORT >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_DELTAEXPORT >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_INST.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_INST.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_INST >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_INST >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_INSTANCES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_INSTANCES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_INSTANCES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_INSTANCES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_LONGVALUES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_LONGVALUES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_LONGVALUES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_LONGVALUES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_NAMESP.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_NAMESP.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_NAMESP >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_NAMESP >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_NAMESPACES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_NAMESPACES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_NAMESPACES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_NAMESPACES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPARRAYS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPARRAYS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPARRAYS >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPARRAYS >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPERTIES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPERTIES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPERTIES >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPERTIES >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPERTYREF.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPERTYREF.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPERTYREF >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPERTYREF >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_QUAL.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_QUAL.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_QUAL >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_QUAL >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_QUALIFIERS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_QUALIFIERS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_QUALIFIERS >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_QUALIFIERS >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ROLE.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ROLE.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ROLE >>>
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ROLE >>>
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Analyse und Anpassung von Tabellen erfolgreich ausgefuehrt
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Analyse und Anpassung von Tabellen erfolgreich ausgefuehrt
Aug 25, 2006 12:30:25... Info: Finished successfully: development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'0'
Aug 25, 2006 12:30:25... Info: Starting to save the repository
Aug 25, 2006 12:30:26... Info: Finished saving the repository
Aug 25, 2006 12:30:26... Info: Starting: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
Aug 25, 2006 12:30:27... Info: <!LOGHEADER[START]/>
Aug 25, 2006 12:30:27... Info: <!HELP[Manual modification of the header may cause parsing problem!]/>
Aug 25, 2006 12:30:27... Info: <!LOGGINGVERSION[1.5.3.7186 - 630]/>
Aug 25, 2006 12:30:27... Info: <!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\jddilog20060825003026.log]/>
Aug 25, 2006 12:30:27... Info: <!PATTERN[jddilog20060825003026.log]/>
Aug 25, 2006 12:30:27... Info: <!FORMATTER[com.sap.dictionary.database.dbs.DbTraceFormatter(%s %m %-30l %24d)]/>
Aug 25, 2006 12:30:27... Info: <!ENCODING[Cp1252]/>
Aug 25, 2006 12:30:27... Info: <!LOGHEADER[END]/>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: $Id: //tc/DictionaryDatabase/630_VAL_REL/src/_dictionary_database_dbs/java/com/sap/dictionary/database/dbs/DbModificationManager.java#4 $
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBTABLERT >>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBTABLERT >>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:It looks like you need to make sure server0 is running before trying to deploy the AutoID (AII) components; from your SDM log:
ERROR: Cannot perform action deploy on component library C:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\com.sap.aii.ibtransportclient\SAP AG\0\6.4018.00.0000.20060413102101.0000\aii_ibtransportclient.sda. Reason:
com.sap.engine.services.rmi_p4.P4ConnectionException: <b>Possible problem: no available running server node. Check your running servers.</b>
The SDM can't connect to the P4 service of the instance; make sure it's started and then try deploying the package again.
Rich -
Error in SAP installation in phase 19 of 34 - Import ABAP
Hi SAP Gurus,
Good day all, I'm facing problem when installing SAP ECC 6.0 EHP7 (IDES version). Its stucked in phase 19 of 34 Import ABAP.
Below are the error details:-
ECC Message Box
An error occurred while processing option SAP Business Suite 7i 2013 Support Release 1 > EHP7 for SAP ERP 6.0 ABAP Support Release 1 > Oracle > SAP Systems > Application Server ABAP > Standard System > Standard System( Last error reported by the step: Process call 'D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.). You can now:
Choose Retry
to repeat the current step.
Choose Log Files
to get more information about the error.
Stop the option and continue later.
Log files are written to C:\Program Files/sapinst_instdir/BS2013/BS2013SR1/ERP607SR1/ORA/INSTALL/STD/ABAP.
Below are the logs from R3load.exe:-
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20141006062234
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/741_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: version R7.40/V1.8 [UNICODE]
Compiled Nov 23 2013 13:31:32
-------------------- Start of patch information ------------------------
patchinfo (patches.h): (0.009) Support for SUM/ZDM and DMO (note 1778564)
DBSL patchinfo (patches.h): (0.011) DBSL error corrections in 7.41: (4) LOBs (note 1928526)
--------------------- End of patch information -------------------------
process id 4612
DbSl Trace: Connect via SAPUSER not supported for kernel >= 740.
(DB) ERROR: db_connect rc = 256
DbSl Trace: Connect via SAPUSER not supported for kernel >= 740.
(DB) ERROR: DbSlErrorMsg rc = 29
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20141006062234
Looking forward for your reply.
Regards,
Jay
-96-Hi
I'm afraid you forget selecting the SSFS option during installation and it is the only connection method supported for kernel 7.40
It should be possible to fix this manually and perform all the step to connect using SSFS... but restarting your installation might be faster & easier.
1622837 - Secure connection of AS ABAP to Oracle via SSFS
As of SAP Kernel Release 7.40 (irrespective of the Oracle version), only the secure connection (secure connect) is supported via SSFS.
Regards -
ERROR: Update mode C is not supported by the extraction API - R3 11
Hi gurus,
I just tryed to implement the solution I found at this link:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf
The data source is based on an Infoset on the KONV R/3 Table.
I setted the AIM delta process and I did all the activities as written in the document.
The process works if I load data to bw in "full", with "Init without data transfer" and "delta" mode. Of course if I change a Purchase document, it will be posted in the delta queue and then loaded to bw with the next delta load.
The "initialize delta process" (with data) doesen't work and returns the following error:
Update mode C is not supported by the extraction API
the error code is R3 11.
have you any idea about it???
Thanks!!!
Regards!
MatteoHi,
for me it sounds quite simple. It is that the update mode 'C' get flagged as 'not allowed' for this extractor. Did you check with rsa3? I guess you will get the same error message. May be you can start debugging in rsa3 to find the place where the update mode gets checked.
Anyway, it shouldn't be a issue as you have a workaround. May be you should raise a error message at sap because of this.
regards
Siggi
Maybe you are looking for
-
Error in Retroactive wages in payslip and Payroll register
Dear Consultants, One of my client facing error while retroactive wage display in payslip and as well as Payroll register, when the employee is having any retro arrears that time the total arrears are coming as "Stat.net subs.adjustment" but client w
-
Numbers not displaying certain text.
I use Numbers to create invoices. Previous versions of numbers would display and print but not export certain text. In version 9 the same text will not even display. Any way to fix without opening all my old invoices in a previous version of Numbers?
-
Hi I'm pretty new to SQL and need some help with SQL syntax. I am trying to write a sql query which takes as input a variable and dependent upon the value of this variable queries for specific values from the database. E.g., if varA =x then query d/b
-
UIX 2.1.20: Detecting current FACET in UIT / UIX
Hello, I have a custom UIX control implemented as UIT. This control should change its appearance on the page depending on which facet is currently being used. My plan was to have 2 different controls in our UIT and conditionally switch them ON and OF
-
I'm having issues with the shortcuts of Adobe Photoshop Cs2 I used to use the functions [ and ] to decrease/increase the brush size and also the shortcut to zoom in and zoom out, also I used the arrows on my keyboard to move things more precisely vs