DB2 upgrade to 10.5
Hi,
We have planned for the db2 upgrade from V9.7 FP5 to V10.1 FP3 and we have about 10 application servers to our ERP system.
Apart from the execution of db6_update_client.sh , is there any particular steps needs to be done for application servers during upgrade ? or is it just the db2 upgrade on DB server and the execution of db6_update_client.sh script ?
Best Regards,
DVRK
Hi,
1. Prerequisites for a successful upgrade to DB2 LUW Version 10.5
- Ref. SAP Note:1837312 - DB6: Upgrade to Version 10.5 of DB2 for LUW
2. Make sure you are using the latest db6_update_client script.sh script
- Ref. SAP Note: 1365982 - DB6: Current db6_update_db/db6_update_client script (V41)
3. Check the required minimum SAP Basis Release Levels before you start.
- Ref. SAP Note: 1851853 - DB6: Using DB2 10.5 with SAP Applications
4. Install SAP Note 1835822 on top of your current minimum SAP Basis release
- So as to avoid having to troubleshoot the DBACockpit thereafter.
5. Following the above listed steps should preclude your anticipated appilcation server utilization
hitches.
B/Rgds., SAM.
Similar Messages
-
SIDADM do not have enough previlages to startsap after DB2 upgrade to 9.5
Hello Anyone,
I recently upgrade our DB2 version from 8.X to 9.5.2, We run SAP netweaver ECC 5 with DB2. I can startsap if I do db2start and and then issue a startsap after su to sidadm. Please can anyone advice
I had followed all instruction of the upgrade guide and OSS notes.
Many Thanks
JacobHi there,
I have tried to start sap using startsap as user sidadm, it just fails.
Here is the diag log
2009-08-17-00.08.37.417658+000 I1A1159 LEVEL: Event
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
START : New Diagnostic Log file
DATA #1 : Build Level, 152 bytes
Instance "db2met" uses "64" bits and DB2 code release "SQL09052"
with level identifier "03030107".
Informational tokens are "DB2 v9.5.0.2", "s080911", "U820796", Fix Pack "2a".
DATA #2 : System Info, 224 bytes
System: AIX met01 3 5 00C99E9B4C00
CPU: total:8 online:4 Threading degree per core:2
Physical Memory(MB): total:9216 free:3312
Virtual Memory(MB): total:16256 free:10323
Swap Memory(MB): total:7040 free:7011
Kernel Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304
shmMax:68719476736 shmMin:1 shmIDs:131072
shmSegments:68719476736 semIDs:131072 semNumPerID:65535
semOps:1024 semMaxVal:32767 semAdjustOnExit:16384
Information in this record is only valid at the time when this file was
created (see this record's time stamp)
2009-08-17-00.08.37.416595+000 I1161A362 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0198683.LOG.
2009-08-17-00.08.40.766956+000 I1524A423 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0198683.LOG to TSM chain 97 from
/db2/MET/log_dir/NODE0000/.
2009-08-17-02.13.33.102389+000 I1948A362 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0198684.LOG.
2009-08-17-02.13.36.482971+000 I2311A423 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0198684.LOG to TSM chain 97 from
/db2/MET/log_dir/NODE0000/.
2009-08-17-04.18.30.684538+000 I2735A362 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0198685.LOG.
2009-08-17-04.18.33.790534+000 I3098A423 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0198685.LOG to TSM chain 97 from
/db2/MET/log_dir/NODE0000/.
2009-08-17-06.23.26.267522+000 I3522A362 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0198686.LOG.
2009-08-17-06.23.29.483758+000 I3885A423 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0198686.LOG to TSM chain 97 from
/db2/MET/log_dir/NODE0000/.
2009-08-17-08.28.20.019219+000 I4309A362 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0198687.LOG.
2009-08-17-08.28.23.436688+000 I4672A423 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0198687.LOG to TSM chain 97 from
/db2/MET/log_dir/NODE0000/.
2009-08-17-10.24.00.636902+000 I5096A362 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0198688.LOG.
2009-08-17-10.24.05.195763+000 I5459A423 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0198688.LOG to TSM chain 97 from
/db2/MET/log_dir/NODE0000/.
2009-08-17-10.34.04.480384+000 I5883A362 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0198689.LOG.
2009-08-17-10.34.08.011061+000 I6246A423 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0198689.LOG to TSM chain 97 from
/db2/MET/log_dir/NODE0000/.
2009-08-17-12.39.10.127139+000 I6670A362 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0198690.LOG.
2009-08-17-12.39.12.681469+000 I7033A423 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0198690.LOG to TSM chain 97 from
/db2/MET/log_dir/NODE0000/.
2009-08-17-14.44.14.029881+000 I7457A362 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0198691.LOG.
2009-08-17-14.44.17.094413+000 I7820A423 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0198691.LOG to TSM chain 97 from
/db2/MET/log_dir/NODE0000/.
2009-08-17-16.49.06.646666+000 I8244A362 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0198692.LOG.
2009-08-17-16.49.10.213526+000 I8607A423 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0198692.LOG to TSM chain 97 from
/db2/MET/log_dir/NODE0000/.
2009-08-17-18.53.50.528211+000 I9031A362 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0198693.LOG.
2009-08-17-18.53.54.264228+000 I9394A423 LEVEL: Warning
PID : 139326 TID : 2881 PROC : db2sysc 0
INSTANCE: db2met NODE : 000
EDUID : 2881 EDUNAME: db2logmgr (MET) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0198693.LOG to TSM chain 97 from
/db2/MET/log_dir/NODE0000/.
Many Thanks
Jacob -
Hello All,
I have to upgrade DB2 9.7 to 10.1 or 10.5 where is OS is Linux.
Can anyone please help me on this?SAP version is ECC 6.0 with Linux SLES-9.My SAP Kernel Release version is 720 and SAP_BASIS release is 702.
Kindly share some documents for the same.It will be a great help for me.
Thanks
AjitabhHi Ajitabh,
Your RHEL version is supported for DB2 10.1 as well as 10.5. You may be required to update the kernel to 7.21 or 7.21_EXT.
Please check PAM for more details
https://service.sap.com/sap/support/pam?hash=s%3DNetweaver%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26p…
Hope this helps.
Regards,
Deepak Kori -
Db2 upgade from DB version 09.01.0009 to 09.01.0011
Dear Friends,
I am looking for easy document where i get an idea for Db2 database upgrade from 09.01.0009 to 09.01.0011 , I have tried reading the upgrade guide but its too complex to understand for newbies in DB2 Database.
Actually i am upgrading solution manager through SUM where its asking for DB2 upgrade my whole project is now standstill due to this upgrade.
Please help me .
Regards,
ISSureshReddy wrote:
BUNDLE_SERIES ACTION NAMESPACE VERSION ID COMMENTS
PSU APPLY SERVER 11.2.0.3 0 Patchset 11.2.0.2.0
PSU APPLY SERVER 11.2.0.3 0 Patchset 11.2.0.2.0
*PSU APPLY SERVER 11.2.0.3 3 PSU 11.2.0.3.3*>
Patch 13923374 : applied on Wed Sep 12 00:54:47 IST 2012
Unique Patch ID: 14858653
Patch description: *"Database Patch Set Update : 11.2.0.3.3 (13923374)"*
Hi,
I can see you have 11.2.0.3.3 now, see the above bold.
Also you can check action_time from registry$history, if the 11.2.0.3 is the latest one then that is the patch running on
Cheers -
Error upgrading DB2 database from 8.1 SP4 to 9.2
Has anyone encountered this before:
create_database_objects:
[echo] ***** Calling JDBCDataLoader ** to create database objects and insert seed data
[java] Loading Database...
[java] logFile=upgrade_db.log
[java] user=db2admin
[java] password=********
[java] url=jdbc:bea:db2://pod248:50000;DatabaseName=iwcontnt
[java] files=C:\bea\WEBLOG~2/common/p13n/db/db2/jdbc_index/UPGRADE/jdbc.index,C:\bea\WEBLOG~2/portal/db/db2/jdbc_index/UPGRADE/jdbc.index
[java] driver=weblogic.jdbc.db2.DB2Driver
[java] saltFile=C:\bea\weblogic92\portal\upgrade\db/security/SerializedSystemIni.dat
[java] prodDir=C:\bea\WEBLOG~2
[java] Processing file 'C:\bea\WEBLOG~2\common\p13n\db\db2\jdbc_index\UPGRADE\jdbc.index'
[java] Files=
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_drop_indexes.sql
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_drop_constraints.sql
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_create_tables.sql
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_create_indexes.sql
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/data/required/p13n9_insert_system_data.sql
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/data/required/bt9_insert_system_data.sql
[java] Error = SQLException when executing file file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_drop_indexes.sql
[java] java.lang.Exception: SQLException when executing file file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_drop_indexes.sql
[java] at com.bea.plateng.domain.jdbc.JDBCDataLoader.load(JDBCDataLoader.java:182)
[java] at com.bea.plateng.domain.jdbc.JDBCDataLoader.main(JDBCDataLoader.java:1320)
[java] Caused by: java.sql.SQLException: [BEA][DB2 JDBC Driver]Resource Limits Reached( ALLOCATE MEMORY FOR NEW SQLSTT FAILED ). Diagnostic Info: FUNCTION ID = 0049 , PROBE POINT = 0400 , TRACE POINT = 0030 , SUBCODE1 = 8B0F0000, SUBCODE2 = 78A68A98, SUBCODE3 = 00000000, ERROR MSG = Parser: Memory allocation error.
[java] at weblogic.jdbc.base.BaseExceptions.createException(Ljava.lang.String;Ljava.lang.String;)Ljava.sql.SQLException;(Unknown Source)
[java] at weblogic.jdbc.base.BaseExceptions.getException(I[Ljava.lang.String;)Ljava.sql.SQLException;(Unknown Source)
[java] at weblogic.jdbc.db2.drda.DRDARequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Unknown Source)
[java] at weblogic.jdbc.db2.drda.DRDAStatementRequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Unknown Source)
[java] at weblogic.jdbc.db2.drda.DRDAQueryStatementRequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Unknown Source)
[java] at weblogic.jdbc.db2.drda.DRDARequest.processReply(Lweblogic.jdbc.base.BaseWarnings;)V(Unknown Source)
[java] at weblogic.jdbc.db2.DB2ImplStatement.execute()V(Unknown Source)
[java] at weblogic.jdbc.db2.DB2PackageManager.getMaxSections()I(Unknown Source)
[java] at weblogic.jdbc.db2.DB2PackageManager.initialize(Lweblogic.jdbc.db2.drda.DRDALoginRequest;)V(Unknown Source)
[java] at weblogic.jdbc.db2.DB2ImplConnection.open()V(Unknown Source)
[java] at weblogic.jdbc.base.BaseConnection.connect()V(Unknown Source)
[java] at weblogic.jdbc.base.BaseConnection.setupImplConnection(I)Lweblogic.jdbc.base.BaseImplConnection;(Unknown Source)
[java] at weblogic.jdbc.base.BaseConnection.open(Lweblogic.jdbc.base.BaseConnectionProperties;Lweblogic.jdbc.base.BaseExceptions;Lweblogic.util.UtilDebug;)V(Unknown Source)
[java] Load Failed
[java] at weblogic.jdbc.base.BaseDriver.connect(Ljava.lang.String;Ljava.util.Properties;)Ljava.sql.Connection;(Unknown Source)
[java] at com.bea.plateng.domain.jdbc.JDBCConnectionTester.createConnection(JDBCConnectionTester.java:266)
[java] at com.bea.plateng.domain.jdbc.JDBCDataLoader.load(JDBCDataLoader.java:153)
[java] ... 1 more
I am trying to upgrade the schema for WL/Portal 9.2 from 8.1SP4 using the scripts supplied from BEA using the BEA DB2 driver.
-mikeMichael Melvin wrote:
Has anyone encountered this before:
create_database_objects:
[echo] ***** Calling JDBCDataLoader ** to create database objects and insert seed data
[java] Loading Database...
[java] logFile=upgrade_db.log
[java] user=db2admin
[java] password=********
[java] url=jdbc:bea:db2://pod248:50000;DatabaseName=iwcontnt
[java] files=C:\bea\WEBLOG~2/common/p13n/db/db2/jdbc_index/UPGRADE/jdbc.index,C:\bea\WEBLOG~2/portal/db/db2/jdbc_index/UPGRADE/jdbc.index
[java] driver=weblogic.jdbc.db2.DB2Driver
[java] saltFile=C:\bea\weblogic92\portal\upgrade\db/security/SerializedSystemIni.dat
[java] prodDir=C:\bea\WEBLOG~2
[java] Processing file 'C:\bea\WEBLOG~2\common\p13n\db\db2\jdbc_index\UPGRADE\jdbc.index'
[java] Files=
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_drop_indexes.sql
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_drop_constraints.sql
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_create_tables.sql
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_create_indexes.sql
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/data/required/p13n9_insert_system_data.sql
[java] file:/C:/bea/WEBLOG~2/common/p13n/db/data/required/bt9_insert_system_data.sql
[java] Error = SQLException when executing file file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_drop_indexes.sql
[java] java.lang.Exception: SQLException when executing file file:/C:/bea/WEBLOG~2/common/p13n/db/db2/p13n9_drop_indexes.sql
[java] at com.bea.plateng.domain.jdbc.JDBCDataLoader.load(JDBCDataLoader.java:182)
[java] at com.bea.plateng.domain.jdbc.JDBCDataLoader.main(JDBCDataLoader.java:1320)
[java] Caused by: java.sql.SQLException: [BEA][DB2 JDBC Driver]Resource Limits Reached( ALLOCATE MEMORY FOR NEW SQLSTT FAILED ). Diagnostic Info: FUNCTION ID = 0049 , PROBE POINT = 0400 , TRACE POINT = 0030 , SUBCODE1 = 8B0F0000, SUBCODE2 = 78A68A98, SUBCODE3 = 00000000, ERROR MSG = Parser: Memory allocation error.
[java] at weblogic.jdbc.base.BaseExceptions.createException(Ljava.lang.String;Ljava.lang.String;)Ljava.sql.SQLException;(Unknown Source)
[java] at weblogic.jdbc.base.BaseExceptions.getException(I[Ljava.lang.String;)Ljava.sql.SQLException;(Unknown Source)
[java] at weblogic.jdbc.db2.drda.DRDARequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Unknown Source)
[java] at weblogic.jdbc.db2.drda.DRDAStatementRequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Unknown Source)
[java] at weblogic.jdbc.db2.drda.DRDAQueryStatementRequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Unknown Source)
[java] at weblogic.jdbc.db2.drda.DRDARequest.processReply(Lweblogic.jdbc.base.BaseWarnings;)V(Unknown Source)
[java] at weblogic.jdbc.db2.DB2ImplStatement.execute()V(Unknown Source)
[java] at weblogic.jdbc.db2.DB2PackageManager.getMaxSections()I(Unknown Source)
[java] at weblogic.jdbc.db2.DB2PackageManager.initialize(Lweblogic.jdbc.db2.drda.DRDALoginRequest;)V(Unknown Source)
[java] at weblogic.jdbc.db2.DB2ImplConnection.open()V(Unknown Source)
[java] at weblogic.jdbc.base.BaseConnection.connect()V(Unknown Source)
[java] at weblogic.jdbc.base.BaseConnection.setupImplConnection(I)Lweblogic.jdbc.base.BaseImplConnection;(Unknown Source)
[java] at weblogic.jdbc.base.BaseConnection.open(Lweblogic.jdbc.base.BaseConnectionProperties;Lweblogic.jdbc.base.BaseExceptions;Lweblogic.util.UtilDebug;)V(Unknown Source)
[java] Load Failed
[java] at weblogic.jdbc.base.BaseDriver.connect(Ljava.lang.String;Ljava.util.Properties;)Ljava.sql.Connection;(Unknown Source)
[java] at com.bea.plateng.domain.jdbc.JDBCConnectionTester.createConnection(JDBCConnectionTester.java:266)
[java] at com.bea.plateng.domain.jdbc.JDBCDataLoader.load(JDBCDataLoader.java:153)
[java] ... 1 more
I am trying to upgrade the schema for WL/Portal 9.2 from 8.1SP4 using the scripts supplied from BEA using the BEA DB2 driver.
-mikeHi. You may need to consult your DB2 DBA. This is just the driver reporting that
it's processing failed at the DBMS because of hitting a DBMS resource limit on
memory.
Joe -
Upgrade DB2 database from 9.1 to 10.5
Dear All,
We are using Ecc6 with db2 database 9.1 now we want to upgrade database from 9.1 to 10.5. Is it possible to upgrade database & what are those steps are required for this operation. We are waiting your valuable support in this regards.
Regards
AbhijitHello,
Please check the guide https://websmp201.sap-ag.de/~sapdownload/011000358700000843422013E/DB6UpgrGuide10_5_upd.pdf
Database-Related Restrictions
If you are running DB2 for Linux, UNIX, and Windows Version 9.5 or lower, you first have to upgrade
the database to DB2 Version 9.7 or 10.1 as described in the relevant upgrade guide at:
http://service.sap.com/instguides Database Upgrades DB2 UDB
BR,
K. -
PeopleSoft Upgrade(DB2 8.46 to Oracle 8.49)
Hello,
We are trying to change database platform from DB2 to Oracle and tools release from 8.46 to 8.49 so far we are following Oracle Testmove methodology but the mail issue here is that we are spending lot of time doing this and so planning for altenate methodology of cloning the already created testmove instance but the main problem how to get the latest production data from DB2 to Oracle, we can move application tables using datamover but we are having trouble identifying the Tools tables that need to exported from 8.46 to 8.49 Oracle cloned instance can someone help me identify the tools tables that should not be exported and tables which needs to be exported so that we can have the cloned copy latest.
I really appreciate if some one throws light on this issue.
Thanks & RegardsWhenever you try to do Upgrade including with migration from one database to another , it is always advisable to follow that in 2 steps.
1. Migrate your DB first (in production itself)
2. Then go for your PS related Upgrade.
if you have not done this, then everytime that you want to do any Test Moves, you even for Test move to Prod, you would spend lot of time for migration effort.
if your DB size is very small (less than 5 GB), then you can try to export all PT and Functional tables and import it back using Data Mover at PT 8.46;
The Datamover process might be painful sometimes to convert the data.
Hope this helps
[Learn PeopleSoft |http://www.learnpeoplesoft.info]
[Learn PeopleSoft Upgrades |http://www.changeassistant.blogspot.com]
Edited by: user11093649 on Apr 22, 2009 7:42 AM -
Upgrading db2 connect thin client from v9.1 to v9.5
I'm looking for instructions on how to upgrade the db2 connect thin client CLI and JDBC drivers from v9.1 to v9.5 (latest fixpack). I found note 867976 describing how to update the JDBC portion. I'm wondering if there is an official way of upgrading the CLI client, now that this is normally automatically installed as part of the SAPINST process. We want to upgrade our system from v9.1 thin client ot v9.5 thin client to use the new functionality.
(We have instructions for upgrading from v9 Fat client to v9.5 thin client.)1.Copied new driver version into db2_clidriver and jdbc folders.
2. Ran db2radm to bind new collection
3. Used sappad to change connect.ini file back to Unix format.
4. Restarted Cluster.
New version working now. -
I have an existing and Operating LC ES2 installation running on WebSphere v6.1 and DB2 v9.5. I am trying to upgrade our DB2 server to DB2 v9.7 but the LiveCycle Database is not being upgraded. All my other database converted as expected but with the LiveCycle wont. Has anyone successfully migrated?
Does your OS release/patch and DP release/patch support backup of DB29.7?
Have a look here -> [http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01631170/c01631170.pdf]
Seems you will need at least HP-Ux 11.31 and DP A.06.1.x
Also check logs in '/usr/omni/log' (or the equivalent for HP-UX), you might find more details and some DP return codes.
Daniel -
Upgrade DB2 z/os to 9.7 version fixpack
Hi folks,
I am too confuse about upgrading DB2 z/os.
I need to upgrade DB2 z/os database to 9.7 version under SAP AIX system. My doubt is : what OS shoud I run the upgrade installer software?
I could sound too easy but It never work with DB2 z/os system.
Tks a lotHi,
1. We used Datamover to export from DB2 z/OS
2. Created a Database in DB2 LUW with same tablespace structure like DB2 z/OS
3. Imported Data using Datamover in LUW
4. Ran DDD, SYS audit after import.
5. Ran UPGCOUNT to validate the number of rows. -
Upgrade to BI 70 - OS400/DB2 - Not able to proceed
Hello
I am in the process to upgrade our 3.5 environment and am running prepare as the first step. Its getting stuck and am not able to proceed further. Any help in this regard would definitely be appreciated. Please find the error log from CHECKS.LOG file:
#=======================================================================
#Starting new execution of PREPARE modules
Parameter input
Initialization
Import
Extension
Integration
Installation
General checks
Activation checks
Necessary checks for conversions
Optional checks for conversions
Modification support
Pre-processing
at 20081016083015.
#=======================================================================
#=====================================================#
Requests and information for module Parameter input #
#=====================================================#
#===============================================================#
PREPARE module Parameter input finished with status succeeded #
#===============================================================#
#====================================================#
Requests and information for module Initialization #
#====================================================#
INFO: The version check of the R3trans in your active SAP kernel determined that it has a sufficient level.
No update of R3trans is necessary.
INFO: The version check of the disp+work in your active SAP kernel determined that it has a sufficient level.
No update of disp+work is necessary.
INFO: The version check of the tp in your active SAP kernel determined that it has a sufficient level.
No update of tp is necessary.
ERROR: The executable R3trans in /usr/sap/put/exe is too old.
It needs a release date of 15.01.08 or later.
Please proceed as described in note 19466.
ERROR: The new SAP tools in /usr/sap/put/exe cannot connect to your database.
Possible reasons are:
- Environment variables are not properly set for the version of the database client which is used by the new tools.
- Required database libraries are not accessible or cannot be found neither through a compiled-in path nor through explicit search via the shared library path.
- Auxiliary files such as language files etc. are not compatible with this version of the database client.
Please check database / OS specific upgrade notes for more help.
The log file /usr/sap/put/log/DBCONNCHK.LOG contains more details about the failure.
INFO: The upgrade strategy for the addon BI_CONT is described in note: 1000822
INFO: The upgrade strategy for the addon PI_BASIS is described in note: 555060
INFO: The upgrade strategy for the addon SAP_BW is described in note: 632429
#===========================================================#
PREPARE module Initialization finished with status failed #
#===========================================================#
#===================================================================
Execution of selected PREPARE modules finished but
PREPARE modules
Import
Extension
Integration
Installation
General checks
Activation checks
Necessary checks for conversions
Optional checks for conversions
Modification support
Pre-processing
could not be executed because their predecessors were not executed # successfully. Correct the errors and select the predecessors again.
#====================================================================
Any idea how to fix this error or how to proceed further?
EmJayAny suggestions. Hard deadline and not able to proceed.
Any help would be appreciated.
Thanks -
Upgrade running from long time on IBM iSeries DB2 platform
Hi Team
We are upgrading SAP ECC 6.0 from SAP 4.6c In Task Progress, Adjust Name table - activity which is running from last 8 hours.
Actually this job should complete in half hour. But this job is running from 8 hours. Our Production system is down from 20 hours.
Thanks
Raju SaleHi Raju,
First of all check logs for any error.
Second it depends upon how much you have optimized different parameter like number of R3trans process, db_Cache_size, RAM etc..
Thanks
Sunny
Edited by: Sunny Pahuja on Oct 12, 2009 6:42 PM -
SAP BW upgrade problem in phase lang_select
Hello everybody,
during our upgrade from SAP BW 3.0B to 3.5 a problem occurred in the phase lang_select running PREPARE. Unfortunately we did not find any up-to-date SAP note on this, except in the note (212481), where the symptom is descried quite well, but the solution does not fit. By the way, the folder-names are already in upper-case (a different note told to do so). So I would be glad if anybody who does have any experience with upgrading from 3.0B could take a look at our problem as described below.
<u>First of all our system information:</u>
SAP Kernel 640 PL 115
OS: IBM AIX 5.2.0
DB: DB2 V8 FP 10
actual release of SAP BW: 3.0B
target release of SAP BW: 3.5 SR1
R3trans: 6.13 (release 640)
Tp: 340.16.12 (release 640)
<u>Problem: PREPARE, phase lang_select</u>
>> 08:56:19 PREPARE: START OF PHASE LANG_SELECT
working on /software/51030722/LANG1 ...
working on /software/51030722/LANG2 ...
working on /software/51030722/LANG3 ...
The following language(s) could not be updated yet:
- German for component PI_BASIS
- German for component SAP_ABA
- German for component SAP_BASIS
- German for component SAP_BW
- English for component PI_BASIS
- English for component SAP_ABA
- English for component SAP_BASIS
- English for component SAP_BW
Please mount another Language Disk for these language(s).
You need at least CDs which satisfy the vector "DE"
(standard languages) for all components.
It is not allowed to omit this update.
<u>What we did until the message comes up:</u>
- all by SAP recommended preparations on the OS, the DB and SAP BW 3.0B have been successfully implemented (as described in Component Upgrade Guide SAP BW 3.5 SR1)
- we copied all the data from CD/DVD into directories on the server
- we copied the fix FIX_WEBAS640SR1.SAR into /usr/sap/put/, which is required by PREPARE later on (SAP note 663240)
- start of PREPARE on the command-line (the directory /usr/sap/put/ is now filled with files and subdirectories are created)
- overwriting R3trans and Tp with the newest versions (as mentioned at the beginning)
- executing UaServer on the AIX, accessing the tool via web browser from a client
- in the applet we start PREPARE
- making entries for PREPARE
- lang_select
We did also examine the logs, here is what they say:
<b>R3upchk.log</b>
UPGRADEPHASE LANG_SELECT
...started at 20060308085619
Phase log file: 'LANGSEL.LOG'
Condition #if 1 >= 0
is evaluated as a TRUE expression, total status is TRUE, stack level 1
...begin dialogue at 20060308085623
<b>Langsel.log</b>
1 ETQ201XEntering upgrade-phase "LANG_SELECT" ("20060308085619")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '10', GwService = 'sapgw10'
4 ETQ399 Environment variables:
4 ETQ399 dbs_db6_schema=SAP1
4 ETQ399 auth_shadow_upgrade=0
4 ETQ380 computing toolpath for request "TP_LANG_SELECT"
4 ETQ381 request "TP_LANG_SELECT" means "create cofile in phase TP_LANG_SELECT"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETG880 Language data requested for "" (without standard languages "DE")
4 ETQ359 RFC Login to: System="1", Nr="10", GwHost="sap1", GwService="sapgw10"
4 ETQ232 RFC Login succeeded
<b>cdtrace.log</b>
2006/03/08 08:56:19 Searching for Data Carrier labeled LANGUAGE
Adding path: /software/51030783
2006/03/08 08:56:19 Resolving directory structure below /software/51030783
Adding path: /software/51030783/UM1
Adding path: /software/51030783/UM2
2006/03/08 08:56:19 Directory structure below /software/51030783 resolved
2006/03/08 08:56:19 Working on /software/51030783 ... no matching label
2006/03/08 08:56:19 Working on /software/51030783/UM1 ... no matching label
2006/03/08 08:56:19 Working on /software/51030783/UM2 ... no matching label
Adding path: /software/51030777
2006/03/08 08:56:19 Resolving directory structure below /software/51030777
Adding path: /software/51030777/UPG1
Adding path: /software/51030777/UPG2
Adding path: /software/51030777/UPG3
2006/03/08 08:56:19 Directory structure below /software/51030777 resolved
2006/03/08 08:56:19 Working on /software/51030777 ... no matching label
2006/03/08 08:56:19 Working on /software/51030777/UPG1 ... no matching label
2006/03/08 08:56:19 Working on /software/51030777/UPG2 ... no matching label
2006/03/08 08:56:19 Working on /software/51030777/UPG3 ... no matching label
Adding path: /software/51030630
2006/03/08 08:56:19 Working on /software/51030630 ... no matching label
Adding path: /software/51030722
2006/03/08 08:56:19 Resolving directory structure below /software/51030722
Adding path: /software/51030722/LANG1
Adding path: /software/51030722/LANG2
Adding path: /software/51030722/LANG3
2006/03/08 08:56:19 Directory structure below /software/51030722 resolved
2006/03/08 08:56:19 Working on /software/51030722 ... no matching label
2006/03/08 08:56:19 Working on /software/51030722/LANG1 ... matches -> added to result list.
2006/03/08 08:56:19 Working on /software/51030722/LANG2 ... matches -> added to result list.
2006/03/08 08:56:19 Working on /software/51030722/LANG3 ... matches -> added to result list.
Adding path: /software/51030769
2006/03/08 08:56:19 Resolving directory structure below /software/51030769
Adding path: /software/51030769/K01
Adding path: /software/51030769/K02
Adding path: /software/51030769/K03
Adding path: /software/51030769/K04
Adding path: /software/51030769/K05
Adding path: /software/51030769/K06
Adding path: /software/51030769/K07
Adding path: /software/51030769/K08
2006/03/08 08:56:19 Directory structure below /software/51030769 resolved
2006/03/08 08:56:19 Working on /software/51030769 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K01 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K02 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K03 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K04 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K05 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K06 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K07 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K08 ... no matching label
Adding path: /software/51030865
2006/03/08 08:56:19 Working on /software/51030865 ... no matching label
Well, we actually do not know what the problem is. It seems to us that the program is not able to identify the language source files. The point is why did the source-paths for the other data work, as we copied the CD/DVD-data into folders? What is different with the language-CD?
Thanks a lot for your help,
PeterI had the same problem but for upgrading SAP SOLUTION MANAGER 3.2 to 4.0 in the PREPARE PHASE "LANG_SELECT"
In the PEVALLAN.<SAPSID> ,I realized that the path for the required DVD I entered was too long !!
My real path was "C:\SAP_CDS\Upgrade_SOL4\51031485\51031485_1\SAP_CRM_LNG"
and the PEVALLAN FILE in the IV_LANGDIR parameter it was
""C:\SAP_CDS\Upgrade_SOL4\51031485\51031485_1\SAP_CR"
I've just shortened the path and it works now.
This surprised me because from the beginning of the PREPARE phase, I had no problems with that kind of thing. -
Error in phase MAIN_SHADOW/START_SHDI_FIRST (Upgrade EHP)
Hello to all,
(This plataform is an IBM DB2 for i5/OS)
I´m performing a Enhancement Package upgrade in our sap system from EHP3 to EHP5, but I´m stuck in phase MAIN_SHADOW/START_SHDI_FIRST (STARTS THE SHADOW SYSTEM). This error show the following message:
severe error(s) occured in phase MAIN_SHADOW/START_SHDI_FIRST!
Last error code set: Shadow instance couldn´t be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG'
So, I will post here that log files.
STARTFI.LOG:
1 ETQ200 Executing actual phase 'MAIN_SHADOW/START_SHDI_FIRST'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'DEVTRACE.LOG'
4 ETQ399 Set environment for shadow connect:
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '01', GwService = 'sapgw01'
4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETQ399 Set tool parameters for shadow connect:
4 ETQ399 default TPPARAM: SHADOW.TPP
4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"
4 ETQ381 request "TP_ALWAYS_NEW" means "always tp from DIR_PUT/exe, for phase KX_SWITCH"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
2 ETQ399 Starting shadow instance
4 ETQ359 RFC Login to: System="DEV", Nr="01", GwHost="SAPDEV", GwService="sapgw01"
2 ETQ231 RFC Login failed
4 ETQ359 RFC Login to: System="DEV", Nr="01", GwHost="SAPDEV", GwService="sapgw01"
2 ETQ231 RFC Login failed
2 ETQ399 Stopping shadow instance
4 ETQ359 RFC Login to: System="DEV", Nr="01", GwHost="SAPDEV", GwService="sapgw01"
2 ETQ231 RFC Login failed
4 ETQ359 RFC Login to: System="DEV", Nr="01", GwHost="SAPDEV", GwService="sapgw01"
2 ETQ231 RFC Login failed
2 ETQ353 Starting system
3 ETQ399 Executing command: 'startsap SID(DEV) INSTANCE(01) PROFILE('/usr/sap/DEV/EHPI/abap/DEV/SYS/profile/START_DVEBMGS01_SAPDEV') TYPE(*SHD)'.
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DEV", Nr="01", GwHost="SAPDEV", GwService="sapgw01"
2 ETQ231 RFC Login failed
2WETQ372 test RFC failed, rc="-1"
2EETQ399 Starting shadow instance failed
2EETQ399 Test RFC failed finally
DEVTRACE.LOG:
DpShMCreate: sizeof(j2ee_adm) 3952
DpShMCreate: SHM_DP_ADM_KEY (addr: 700000060000000, size: 6379664)
DpShMCreate: allocated sys_adm at 700000060000010
DpShMCreate: allocated wp_adm_list at 700000060002ff0
DpShMCreate: allocated wp_adm at 7000000600031e0
DpShMCreate: allocated tm_adm_list at 7000000600104b0
DpShMCreate: allocated tm_adm at 700000060010500
DpShMCreate: allocated appc_ca_adm at 700000060562e20
DpShMCreate: allocated comm_adm at 700000060572830
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 7000000606011d0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated gw_adm at 700000060601280
DpShMCreate: allocated j2ee_adm at 7000000606012c0
DpShMCreate: allocated ca_info at 700000060602240
DpCommAttachTable: attached comm table (header=700000060572830/ft=700000060572840)
MtxInit: -2 0 0
DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 from sys_adm
Mon Sep 5 22:48:58 2011
GwISigint: received SIGINT (2), start shutdown phase
***LOG S30=> GwStopGateway, gateway stopped () [gwxxrd.c 12995]
Can you help me please, how to solve this error?
Best regards,
João Dimas - Portugal... continuation...
The dev_w0:
M Mon Sep 5 22:48:48 2011
M ThInit: running on host SAPDEV
M calling db_connect ...
B Loading DB library '/usr/sap/DEV/EHPI/abap/exe/dbdb4slib.o' ...
B Library '/usr/sap/DEV/EHPI/abap/exe/dbdb4slib.o' loaded
B Version of '/usr/sap/DEV/EHPI/abap/exe/dbdb4slib.o' is "720.00", patchlevel (0.98)
C DB4 SQL Reparse Activated
C *** ERROR => dbs/db4/schema contains wrong schema name SAPR3.
[dbsldb4.cpp 7094]
C Error is ignored. Schema R3DEVDATA is used.
C IBM i 7.1 - XDN Default
C XDN-Port: Assuming 9600 + sapmsDEV mod 100 = 9600
C as4IsHostLocal: SAPDBHOST 'SAPDEV' is local
C R3INLPGM: RmtExeLib from /usr/sap/DEV/EHPI/abap/exe/DBSLDB4RMT
C R3INLPGM: RmtExeLib is SAPDEVUPG
C DBSLENCWT: rc=0, msg=CPF9897 CONCURRENT WRITE IS ENABLED.
C QXDARECVR PTF Level is: SI37200
C
C Mon Sep 5 22:48:49 2011
C DbSl/DB codepage check: OK - (Unicode).
C Checking journal settings for QSQJRN /R3DEVDATA : OK
C === Central DB connect successfull! ===
C === Connection settings ===
C connected = TRUE
C con_hdl = 0
C db_handle = 1
C dbhost = SAPDEV
C dbhostport = 9600
C rdbname =
C dblib = R3DEVSHD
C r3sysle_changed = TRUE
C query_compl_reval = O
C dbconnecttype = L
C user = DEV01
C qaqqinilib = Default (QUSRSYS)
C dbjobname = WP00
C dbjobuser = DEV01
C dbjobno = 012091
C rmtexelib = SAPDEVUPG
C parallel_alter_tables = *OFF
C ===========================
C Query options file QUSRSYS/QAQQINI not found.
C -----------------------------------------------------------------------------
C ----- DbSl EGO Structure
C -----------------------------------------------------------------------------
C SAPSYSTEMNAME = DEV
C Character encoding = UNICODE
C process class = dialog process
C workprocess id = 0
C local host = SAPDEV
C dbhost = SAPDEV
C dbhostport = 9600
C rdbname =
C dbname = DEVSAPDEV
C dblib = R3DEVSHD
C application server = DVEBMGS01
C driver = DBSLDirectDrive
C Connect type = LOCAL
C pid = 9088
C wpjobname = WP00
C wpjobuser = DEV01
C wpjobno = 012091
C DB2/400 vers. appl. server = PASE 7.1
C DB2/400 vers. DB server = V7R1
C da_cache_size = 100
C dbsl_buffersize = 131072
C reopen = ON
C timeout_retry = 3
C alter_table_timeout_retry = 3
C ODP threshold = 800
C ODP commit thresh. = 810
C ODP open thresh. = 850
C QAQQINI library = Default (QUSRSYS)
C Alternate QAQQINI library = Not specified
C use_lobs_for_long = ON
C use_lobs_for_short = OFF
C single_execution_threshold = 2000
C single_execution_reuse = OFF
C keep_tmp_SQLpkgs = OFF
M Mon Sep 5 22:48:54 2011
M SecAudit(rsauinit): Start init of Security Audit Log for first wp.
M in_ThErrHandle: 1
M ThIErrHandle: new stat of W0 is WP_SHUTDOWN
M ThIErrHandle: I'm during shutdown
M PfStatDisconnect: disconnect statistics
M ThIErrHandle: entering ThSetStatError
M ThShutDownServer: shutdown server
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workp. 0 9088) [dpuxtool.c 327] -
Support Pack upgrade error in Import Phase
Hello,
Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase.
Could you please help me on this? I tried and still searching solution for this..But no luck...
Os is : AIX and
Log File: /usr/sap/trans/log/SAPIB70013.xxx
Main import
Transport request : SAPKB70013
System : xxxx
tp path : tp
Version and release: 372.04.71 700
child process 934006 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_OBJECT_COLLECTION==========CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1212554 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDR_APPLICATION_WINDOW=====CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1171520 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDY_MD_EVENT_SOURCE========CI
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1331412 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
child process 1310922 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_END
tabname: WDY_APP_PROPERTY
len (char): 64
key: DEMO_UIEL_DROPDOWN_BY_IDX DEMO_VIEW
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 018446 - 999999 not imported because the child processes died for unknown reason
child process 1310924 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDY_MD_OUTGOING_EVENT======CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1286192 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 009158 - 018411 not imported because the child processes died for unknown reason
import portion 018412 - 018527 not imported because the child processes died for unknown reason
import portion 018528 - 999999 not imported because the child processes died for unknown reason
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
Main import
End date and time : 20100909034914
Ended with return code: ===> 12 <===
| ######################################
Thanks and Regards,
Sankar
SAP BASIS ConsultantHi,
Thanks for you reply. I restarted import but no luck still. I activated some object also not working. when i call SPAM it is not going to the SPAM pager. Showing dump...
Runtime Errors CALL_FUNCTION_NOT_FOUND
Except. CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time 10.09.2010 09:41:37
Short text
Function module "POSS_UIREQ_OPT_SUBMIT" not found.
What happened?
The function module "POSS_UIREQ_OPT_SUBMIT" is called,
but cannot be found in the library.
Error in the ABAP Application Program
The current ABAP program "SAPLSTXC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
not caught in
procedure "OPEN_FORM" "(FUNCTION)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
The program "SAPLSTXC" contains the CALL FUNCTION statement.
The name of the function module to be called is "POSS_UIREQ_OPT_SUBMIT".
No function module exists with the name "POSS_UIREQ_OPT_SUBMIT".
All function modules are listed in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Pay particular attenti
upper/lower case and underscores ("_").
or
b) Transport error
c) In the case of an enqueue/dequeue module,
the lock object may not have been activated
(ABAP/4 Dictionary).
When i tried to check function module it is not there..
Could you please help on this?
Regards,
Sankar Basis Consultant
Maybe you are looking for
-
Ok. So a while ago we were backing up our Windows computer (pics, word documents, etc.) on this little flash drive. Now, I want to use it for school. So, I plugged it into our Macs for the first time, I was going to just delete everything from the me
-
Someone else set up my iTunes account for me and I can't remember the Apple ID, the Password, or the name he put under it all. How do I get back into my iTunes account???? Or at least a number to call to get back???
-
I purchased my Ipod Classic 160 GB about a year ago new and never had any issues until lately. I recently updated my itunes to the newest version and my Ipod seemed fine and didn't have any trouble. About a week later my Ipod was no longer recognized
-
Finder not working, responding.
I set up another user account on my server (in system prefs, not a directory user account) and when I try to use it (or the built in guest account) the Finder is non-responsive. I can launch Safari and other apps, but the Finder won't show windows o
-
I am not able to find the Photoshop Album forum.Has it been removed or it is still there ? If it is still there where can I find it?