RSDU_ANALYZE_TABLE_DB2/DB2

Hi All,
Did anyone ever come across this system exception while running Attribute Change run. I searched the oss notes and none of the notes are applicable (371483, 842792,764585). Our version is Db2 7.1.0
For now we are trying to drop all temp tables and proceed.
Any help is appreciated.

Hi Arthur,
We are experiencing an issue with your error. Can you please let me know how you solved it?
Regards,
Annie

Similar Messages

Support package / add on import error in DB2 V9.1 / windows 2003 system

Hi
I have installed ERP 6.0 IDES version in Windows 2003 server with DB2 LUW 9.1 / FP5.
I have selected "Row Compression" and "Deferred Table Creation" during installation.
Now when I am importing add on BI Content 7.03, I am getting error during Movename tabs phase.
Error in phase: IMPORT_PROPER
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package ALL, tp step "6", return code 0008
The error message in the file D:\usr\sap\trans\log\P090113.IDS is as follows,
2 ETP301
3 ETP361 "96" Shadow-Nametabs activated, DDL executed
2 ETP362 "6" Shadow-Nametab activations failed
2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/01/13 02:57:51")
2 ETP363 End : Act. of Shadow-Nametabs with DDL ("2009/01/13 02:58:07")
2 ETP301
1 ETP172 MOVE OF NAMETABS
1 ETP110 end date and time : "20090113025807"
1 ETP111 exit code : "8"
1 ETP199 ######################################
I have read some notes it may be due to "Row compression" and "Deffered table creation" option in DB2. Please help me in resolving this issue if it is DB2 related.
Regards,
Nallasivam.D

Hi,
Please find the real error message which I found in the same log file. This is a new installation.
System configuration details:
ERP 6.0 IDES SR3 + Windows 2003 enterprise server SP2 + DB2 V9.1 / FP5
BASIS and ABAP support pack level: (700) 13.
Error message:
3 ETP399 INDEX IN "IDS#BTABI"
3 ETP399 LONG IN "IDS#BTABD COMPRESS YES"
3 ETP399
2WETP000 02:53:26: Retcode 1: error in DDL statement for "/OSP/T_REPINFO                " - repeat
2EETP345 02:53:38: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#BTABD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/OSP/T_REPINFO
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:05: Retcode 1: error in DDL statement for "/SAPPO/CMP_ASG                " - repeat
2EETP345 02:54:17: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/CMP_ASG
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:17: error in DDL, nametab for "/SAPPO/CMP_ASG" not activated
3 ETP399 IN "IDS#POOLD"
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:17: Retcode 1: error in DDL statement for "/SAPPO/CSCRN_HDR              " - repeat
2EETP345 02:54:29: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/CSCRN_HDR
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:29: error in DDL, nametab for "/SAPPO/CSCRN_HDR" not activated
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:29: Retcode 1: error in DDL statement for "/SAPPO/F_ASG                  " - repeat
2EETP345 02:54:41: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/F_ASG
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:41: error in DDL, nametab for "/SAPPO/F_ASG" not activated
Regards,
Nallasivam.D

Error while calling a Db2 stored proc using Dataservice

Hi ,
I am getting the following exception while calling a Db2 proc.The proc is not returning any refcursor.It has one Input param of type String.We are expecting the result in resultset. I am able to call the proc using JDBC function and iterate tru the resultset and print it.
While doing import the source Metadata , I Added a "Editable Row Set" Type.
Any clue ?
ava.lang.RuntimeException: Incorrect definition, too many return resultset
     at com.bea.ld.wrappers.procedure.ProcedureAdapter$CallableWrapper.getNextReturnValue(ProcedureAdapter.java:634)
     at com.bea.ld.wrappers.procedure.ProcedureIterator.getNextToken(ProcedureIterator.java:249)
     at com.bea.ld.wrappers.procedure.ProcedureIterator.fetchNext(ProcedureIterator.java:125)
     at weblogic.xml.query.iterators.GenericIterator.hasNext(GenericIterator.java:134)
     at weblogic.xml.query.runtime.sequences.Subsequence.fetchNext(Subsequence.java:106)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.runtime.querycide.QueryAssassin.fetchNext(QueryAssassin.java:54)
     at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
     at weblogic.xml.query.runtime.qname.InsertNamespaces.fetchNext(InsertNamespaces.java:161)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.runtime.core.QueryIterator.fetchNext(QueryIterator.java:127)
     at weblogic.xml.query.iterators.GenericIterator.hasNext(GenericIterator.java:134)
     at weblogic.xml.query.xdbc.util.Serializer.serializeItems(Serializer.java:142)
     at com.bea.ld.server.QueryInvocation.getResult(QueryInvocation.java:461)
     at com.bea.ld.EJBRequestHandler.executeFunction(EJBRequestHandler.java:346)
     at com.bea.ld.ServerBean.executeFunction(ServerBean.java:108)
     at com.bea.ld.Server_ydm4ie_EOImpl.executeFunction(Server_ydm4ie_EOImpl.java:208)
     at com.bea.ld.Server_ydm4ie_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:491)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:120)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:429)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

Hi,
I am trying to do something like this but with Oracle stored procedure which returns an associate array and a cursor and these are defined as INOUT. I am not finding a way how to do it with editable row set. Can you plese list the steps used to make things work.
Thanks.

Error in starting DB2 UDB (AIX with ECC 6.0)

Hello All,
I am facing error in starting the database as below :
exec(): 0509-036 Cannot load program db2start because of the following errors:
 0509-130 Symbol resolution failed for /usr/lib/threads/libc.a[aio_64.o] because:
 0509-136 Symbol kaio_rdwr64 (number 0) is not exported from
 dependent module /unix.
 0509-136 Symbol listio64 (number 1) is not exported from
 dependent module /unix.
 0509-136 Symbol acancel64 (number 2) is not exported from
 dependent module /unix.
 0509-136 Symbol iosuspend64 (number 3) is not exported from
 dependent module /unix.
 0509-136 Symbol aio_nwait (number 4) is not exported from
 dependent module /unix.
 0509-136 Symbol aio_nwait64 (number 5) is not exported from
 dependent module /unix.
 0509-136 Symbol aio_nwait_timeout (number 6) is not exported from
 dependent module /unix.
 0509-136 Symbol aio_nwait_timeout64 (number 7) is not exported from
 dependent module /unix.
 0509-026 System error: Error 0
 0509-192 Examine .loader section symbols with the
 'dump -Tv' command.
SQL1652N File I/O error occurred.
I have even changed the Acc. I/O setting also as per the note :683396 .
But the error still exists.Please help me out in this ssue.
Regards,
Chandra.

Hi Chandra,
this error may occure when you do not install DB2 on the node via db2setup on AIX. I assume you moved DB2 via ACC to this box. DB2 requires AIO. In general db2setup enables it for you. You can check this by issuing the following command: 'lsdev -Cc aio'
The correct output should be like:
aio0 Available Asynchronous I/O (Legacy)
The wrong one with disabled AIO:
aio0 Defined Asynchronous I/O (Legacy)
Use 'smitty aio' to configute AIO for your machine.
Regards,
Steffen

Data Federator XI 3.0 using DB2 VARCHAR FOR BIT DATA Column?

We have a column in a DB2 database that is defined as VARCHAR(16) FOR
BIT DATA.
We are using the suggested IBM JDBC driver, db2jcc.jar, against a DB2
OS/390 8.1.5 version database.
The Datasource column displays a data type of NULL, indicating the DF
does not understand or cannot handle this IBM data type.
We have two issues.
First, target tables are not able to return any columns, regardless if
we exclude columns defined as NULL as mentioned above. We see the
'Wait' animation for a very long time when we use the 'Target table
test tool' option. Selecting to display the count only, returns zero.
We are able to fetch and view non-NULL column data when using the
'Query tool' under the Datasource pane.
I also get the same result when using the 'My Query Tool' in Server
Administrator; a selection agains the sources returns data while
selecting from a target table returns no data. Also, a 'select
count(*)' returns zero.
The second issue is in mapping a relationship between two DB2 tables
where the join is between two columns of the above mentioned type
(NULL).
The error we get back when we use "Show Errors" is "The types
'NULL' (in 'S1.PLANNEDGOALID') and 'NULL' (in 'S2.PLANNDEDGOALID') are
not compatible.". When reviewing the relationship, a dashed red line
appears instead of a solid grey line between the two tables in the
"Table relationships and pre-filers" section of our mapping pane.
The following query returns an error via the Server Administrator
Query Tool; "Types 'NULL' and 'NULL' are not compatible for operator
'=' (Error code : 10248)".
select count(*)
from
(select s1.CASEID, s2.PLANNEDGOALID, s2.NAME, s2.PLANNEDGRPSTTYCD
from "/DF_CMS_ODS/sources/CMFSREPT/CMSPROD.PLANNEDGOAL" AS s1
,"/DF_CMS_ODS/sources/CMFSREPT/CMSPROD.PLANNEDGOAL" s2
where s1.PLANNEDGOALID = s2.PLANNEDGOALID)
Here are the properties settings in the Resource Connector Settings
for jdbc.db2.zSeries we are using.
capabilities: isjdbc=true;orderBy=false
driverLocation: drivers/db2jcc_license_cisuz.jar;drivers/db2jcc.jar
jdbcClass: com.ibm.db2.jcc.DB2Driver
sourceType: db2
supportsCatalog: no
urlTemplate: jdbc:db2://<hostname>[:<port>]/<databasename>
Here are the Connection parameters as defined for the datasource in DF
Designer.
Defined resource: jdbc.db2.zSeries
Jdbc connection URL: jdbc:db2://DB2D03:50000/CMFSREPT
Authentication: Use a specific database logon for all Data Federator
users.
User Name: x
Password: hidden
Login domain: -- Choose a defined login domain --
Supports Schema: checked
Schema: is empty
Prefix table names with schema name: checked
Supports catalog: unchecked
Prefix table names with the database name: unchecked
Table types: TABLE and VIEW
So, the following is the two questions we require answers for...
Is this a limitation of Data Federator?
Is there a work around short of changing the datatype in the database.

Hi Darren,
The VARCHAR() FOR BIT DATA is a binary data type and Data Federator does not support binaries. But if in your case, it makes sense to map this column to a VARCHAR data type you can configure the DB2 connector to view this column as a VARCHAR.
Your column can be mapped explicitly to a data type of your choice using a property: castColumnType.
This property can be set updating the resource you selected when you registered you DB2 data source.
If the resource is "jdbc.db2", then:
1. Launch Data Federator Administrator
2. Click on "Administration" tab
3. Click on "Connector Settings"
4. Select the right resource: "jdbc.db2"
5. Click "Add a property"
6. Select "castColumnType"
7. Set its value to: VARCHAR() FOR BIT DATA=VARCHAR
8. Click on Ok
You should see this column as a VARCHAR.
Regards,
Mokrane
PS: For the target table issue, we have forwarded your mail to the Data Federator Designer team.

HELP - DB2 v9 & App Server PE 9.0 - PING Connection Pool Failure - HELP

I've been playing around with Studio Creator and DB2 v9 without any issues.
So I figured I would installed App Server PE 9 and use this as my production server that I would deploy to from studio creator.
However, in my efforts to set up db2/v9 I have been trying to ping a connection pool without any luck. I get the following message:
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: [sunm][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.
My datasource class name is com.sun.sql.jdbcx.db2.DB2DataSource.
And my resource type is javax.sql.datasource
I have copied smbase.jar, smdb2.jar and smutil.jar into c:\sun\appserver\lib
and I have all of the properties (serverName, portNumber, databaseName, user, password) created and set accordingly.
Any help would be greatly appreciated.

Here is how I got the DB2 Express-C and Sun PE 9.0 to work. ( at least base connectivity wise )
1. ) You have to have at least the DB2 Client installed on the system that will be communicating to the DB2 instance.
2.) The following jars will be needed ( depending on the driver type used) . db2java.zip, db2jcc.jar, and db2jcc_license_cu.jar and use them in the App Server ->JVM settings -> Path Settings -> Classpath Suffix
3.) The next setup is dependent on the Type driver you use
I used the Type 4 and this is the resource setup I used.
Connection Pool:
Name: DB2TestPool
Datasource Classname: com.ibm.db2.jcc.DB2SimpleDataSource
Resource Type: javax.sql.ConnectionPoolDataSource
Properties:
user: xxxxxx
password: xxxxxx
databaseName: TEST
serverName: <hostname of machine>
portnumber: 50000
driverType: 4
URL: jdbc:db2://<hostname>:<port>/<database>
JDBC Resource:
JNDI Name: jdbc/TEST
Pool Name: DB2TestPool
With this configuration I was able to ping the database as well as connect to create an entity bean from a table. This should give you a starting point.
I have yet to deploy my application, but should be doing that sometime today to verify that a connection can be made and used from within the application.

Problem with DB2 database connection.

Hello, I configured a DB2 connection. Was also able to create all the view objects. When I run my application using jdeveloper embedded oc4j I am getting the following error: (The connection is already created and the test is successful. I have also created the entity and view objects.)
WARNING: Exception creating connection pool. Exception: oracle.oc4j.sql.config.DataSourceConfigException: Unable to create : com.ibm.db2.jcc.DB2Driver
07/04/25 14:05:12 SEVERE: ApplicationStateRunning.initConnector Error occurred initializing connectors. Exception is: Exception creating connection pool. Exception: oracle.oc4j.sql.config.DataSourceConfigException: Unable to create : com.ibm.db2.jcc.DB2Driver
07/04/25 14:05:12 SEVERE: ApplicationStateRunning.initConnector Stack trace: oracle.oc4j.sql.DataSourceException: Exception creating connection pool. Exception: oracle.oc4j.sql.config.DataSourceConfigException: Unable to create : com.ibm.db2.jcc.DB2Driver
at com.evermind.server.ApplicationStateRunning.initDataSourceConnectionPool(ApplicationStateRunning.java:2072)
at com.evermind.server.ApplicationStateRunning.initDataSourceConnector(ApplicationStateRunning.java:2017)

Copy the DB2 JDBC JAR file to the \j2ee\home\applib dir or the
C:\JDeveloper\j2ee\home\lib.

Dbcon connection from sap db2 to external sql server

Hi ,
I am trying to connect from my sap server which is in unix platform with DB2 database to external SQL server using DBCON as MSSQL_SERVER=<server_name> MSSQL_DBNAME=<db_name>. But while running ADBC_TEST_connection i am getting the error . When i check the error log it says
Loading DB library '/usr/sap/DVL/SYS/exe/run/dbmssslib.so' ...
M *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/SID/SYS/exe/run/dbmssslib.so") FAILED
"Unable to find library '/usr/sap/DVL/SYS/exe/run/dbmssslib.so'." [dlux.c 445]
M {root-id=002655A9DCD21EE3B89D69F99DF39F0D}_{conn-id=00000000000000000000000000000000}_0
B *** ERROR => Couldn't load library '/usr/sap/SID/SYS/exe/run/dbmssslib.so'
How to resolve this issue. As it was mentioned in few forum we need to download the dbsl library from kernel patches and to load in kernel path. As my db is DB2 can we download dbmssslib.so this library and load in kernel file? Is it will work?
Regards,
Rai

Hi Rai,
This error indicates that the ABAP stack could not find the SAP DBSL for SQL Server (dbmssslib.dll) in the kernel directory. If you encounter this error on a Unix - based server the root cause is clear: the DBSL does not exist for other platforms than Windows or Linux x84_64. In this case use a Windows-based or a Linux x86_64-based SAP Application Server to establish the connection. If your system does not contain a Windows-based or a Linux x86_64-based Application Server you need to setup a small one as workaround. If you encounter this error on a Windows Application Server or a Linux x86_64 based Application Server make sure that the DBSL is properly installed in the kernel directory as explained in the document below.
For more details on configuration and troubleshooting refer to below SCN document
How to access an external Microsoft SQL Server database
Hope this helps.
Regards,
Deepak Kori

Remoted DB2 connection from SAP

Hello Experts,
We have a requirement to connect the remote DB DB2 (No SAP) which is on I series from our SAP ECC EHP 5 system so I made a below entry in table DBCON -
Database connection - PRMS_TEST
DBS - DB4
Username - SAP
*Password ***********
Connection Information - AS4_HOST=S1031993;AS4_DB_LIBRARY=RMTLIB
but while doing the test connection, it gives the below error-
B Loading DB library '/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so' ...
M *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so") FAILED
"/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so: cannot open shared object file: No such file or directory" [dlux.c 445]
M {root-id=000C298267DF1EE0BBC9171365715368}_{conn-id=00000000000000000000000000000000}_0
B *** ERROR => Couldn't load library '/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so'
[dbcon.c 5263]
B {root-id=000C298267DF1EE0BBC9171365715368}_{conn-id=00000000000000000000000000000000}_0
B ***LOG BYG=> could not load library for database connection PRMS_TEST [dbds 886]
B ***LOG BZY=> unexpected return code 8192 calling DBDS [dbacds 1536]
My SAP environment is -
SAP - ECC EHP 5
Kernel Release 720 patch 90
OS - Red Hat Linux 5.5 - 64 bit
Database - DB2 (DB6)
Kindlly let us know if I have to put the file dbdb4slib.so in kernel directory and from where I can get this file and if my DBCON entry is correct ?
Regards
Saurabh Mishra

As per note 663756, I can use the DB2 CLI driver as I am on Kernel release 720 (see below) -
If you use a DB2 CLI driver client, the following changes are required in
the procedure described above because the CLI driver does not support DB2
CLP and BIND commands:
o The CATALOG commands are omitted.
o The target host and port must be entered in the table DBCON.
For example, the CON ENV row looks as follows:
DB6_DB_NAME=HOSTDB;DB6_DB_TYPE=DB2/390;DB6_DB_HOST=<hostname>;
DB6_DB_SVCENAME=<portnum>;
o The BIND commands must be executed by a runtime client.
Alternatively, you can use the DB2Binder utility from Note 784264
to bind the CLI packages.
Is that mean that I need to only maintain the DBCON entry as all other commands are omitted for CLI driver and license file is mandatory or temp license will work ?
As per note 784264, I checked my CLASSPATH directory and it contain the JDBC driver file -
sapecdci1:db2ecd 58> pwd
/db2/db2ecd/db2_software/java
sapecdci1:db2ecd 59> ls db2*.jar
db2dbgm.jar db2jcc4.jar db2jcc.jar db2jcc_license_cu.jar db2policy.jar db2umplugin.jar
sapecdci1:db2ecd 60> db2set -all
[e] DB2DBDFT=ECD
 DB2_RESTORE_GRANT_ADMIN_AUTHORITIES=YES [DB2_WORKLOAD]
 DB2_BLOCKING_WITHHOLD_LOBLOCATOR=NO [DB2_WORKLOAD]
 DB2_AGENT_CACHING_FMP=OFF [DB2_WORKLOAD]
 DB2_TRUST_MDC_BLOCK_FULL_HINT=YES [DB2_WORKLOAD]
 DB2_CREATE_INDEX_COLLECT_STATS=YES [DB2_WORKLOAD]
 DB2_ATS_ENABLE=YES [DB2_WORKLOAD]
 DB2_RESTRICT_DDF=YES [DB2_WORKLOAD]
 DB2_DUMP_SECTION_ENV=YES [DB2_WORKLOAD]
 DB2_OPT_MAX_TEMP_SIZE=10240 [DB2_WORKLOAD]
 DB2_WORKLOAD=SAP
 DB2_TRUNCATE_REUSESTORAGE=IMPORT [DB2_WORKLOAD]
 DB2_MDC_ROLLOUT=DEFER [DB2_WORKLOAD]
 DB2_ATM_CMD_LINE_ARGS=-include-manual-tables [DB2_WORKLOAD]
 DB2_SKIPINSERTED=YES [DB2_WORKLOAD]
 DB2_VIEW_REOPT_VALUES=YES [DB2_WORKLOAD]
 DB2_OBJECT_TABLE_ENTRIES=65532 [DB2_WORKLOAD]
 DB2_OPTPROFILE=YES [DB2_WORKLOAD]
 DB2_IMPLICIT_UNICODE=YES [DB2_WORKLOAD]
 DB2_RUNTIME_DEBUG_FLAGS=TOLERANT_FLOAT [DB2_WORKLOAD]
 DB2STMM=APPLY_HEURISTICS:YES [DB2_WORKLOAD]
 DB2_INLIST_TO_NLJN=YES [DB2_WORKLOAD]
 DB2_MINIMIZE_LISTPREFETCH=YES [DB2_WORKLOAD]
 DB2_REDUCED_OPTIMIZATION=4,INDEX,JOIN,NO_TQ_FACT,NO_HSJN_BUILD_FACT,STARJN_CARD_SKEW,NO_SORT_MGJOIN,CART OFF,CAP OFF [DB2_WORKLOAD]
 DB2NOTIFYVERBOSE=YES [DB2_WORKLOAD]
 DB2TERRITORY=1
 DB2_INTERESTING_KEYS=YES [DB2_WORKLOAD]
 DB2_EVALUNCOMMITTED=YES [DB2_WORKLOAD]
 DB2_EXTENDED_OPTIMIZATION=NLJOIN_KEYCARD,IXOR [DB2_WORKLOAD]
 DB2_ANTIJOIN=EXTEND [DB2_WORKLOAD]
 DB2COMPOPT=327685,131776 [DB2_WORKLOAD]
 DB2ATLD_PORTS=60000:65000
 DB2ENVLIST=INSTHOME SAPSYSTEMNAME dbs_db6_schema DIR_LIBRARY LD_LIBRARY_PATH
 DB2COMM=TCPIP [DB2_WORKLOAD]
[g] DB2FCMCOMM=TCPIP4
[g] DB2SYSTEM=sapecdci1
[g] DB2INSTDEF=db2ecd
sapecdci1:db2ecd 61> java com.ibm.db2.jcc.DB3Binder
Exception in thread "main" java.lang.NoClassDefFoundError: com.ibm.db2.jcc.DB3Binder
 at gnu.java.lang.MainThread.run(libgcj.so.7rh)
Caused by: java.lang.ClassNotFoundException: com.ibm.db2.jcc.DB3Binder not found in gnu.gcj.runtime.SystemClassLoader{urls=[file:/db2/db2ecd/sqllib/java/db2jcc_license_cu.jar,file:/db2/db2ecd/sqllib/java/db2jcc.jar,file:/db2/db2ecd/sqllib/function/,file:./,file:/db2/db2ecd/sqllib/java/db2java.zip,file:./,file:/db2/db2ecd/sqllib/java/db2java.zip,file:./], parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}
 at java.net.URLClassLoader.findClass(libgcj.so.7rh)
 at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
 at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
 at gnu.java.lang.MainThread.run(libgcj.so.7rh)
sapecdci1:db2ecd 62> db2 get dbm cfg | grep -i svcename
TCP/IP Service name (SVCENAME) = sapdb2ECD
SSL service name (SSL_SVCENAME) =

DB2 error in file db2nodes.cfg on HPUX cluster instalation

I am installing ECC6 SR3 ABAP + DB2 V9.1 in cluster environment on HPUX IA64 + ServiceGuard.
I am with the following problem, DB2 software does not function in second node.
Overview:
node1: host1
node2: host2
virtual host: vthostci
virtual host: vthostdb
ServiceGuard Package
pkgdb (hostnames host1/vthostdb)
pkgci (hostnames host2/vthostci)
Shared Disk
/usr/sap (on package pkgci)
/db2
/db2/db2ecp
/db2/ECP
/db2/ECP/db2dump
/db2/ECP/db2ecp
/db2/ECP/log_dir
/db2/ECP/sapdata1
/db2/ECP/sapdata2
/db2/ECP/sapdata3
/db2/ECP/sapdata4
components installed on node1 (sapinst use virtual hostname)
ASCS on vthostci
DB Instance on vthostdb
CI on vthostci
components installed on node2
Creating Operating System Users (sapinst)
without problems until here, but when movement the DB instance and the ASCS to node2 the DB2 instance does not function, it presents error in the file db2nodes.cfg.
the file db2nodes.cfg contains the following line:
"0 host1 0" (the physical hostname the node1)
My problem is... How to configure DB2 Software/Instance on both node the HA cluster?
Another question, on ERP 2005 SR3 the db2 software is automatically installed by SAPinst in the following directory:/db2/db2<dbsid>/db2_software.
That is correct in cluster environment? because /db2 is shared disk.
Please help me
Thanks.

Hi Licia ,
if you are running an single node and simply switch database from node1 to node2 this should not be a problem since the database software is taken over with the database .
If you have problems taking over the database software due to some issues
( like open files ) you can also keep the database software locally as before , but this then implies to maintain database software twice .
If you are running multiple DB2 nodes on cluster node1 and cluster node2 of course you need
database software installed and maintained locally on both nodes .
Best regards
dirk

Does SAP support Solaris 10 ZFS filesystem when using DB2 V9.5 FP4?

Hi,
I'm installing NW7 (BI usage). SAPINST has failed in the step "ABAP LOAD due to the DB2 error message
"Unsupported file system type zfs for Direct I/O". It appears my Unix Admin must have decided to set these filesystems as ZFS on this new server.
I have several questions requiring your expertise.
1) Does SAP support ZFS filesystems on Solaris 10 (SPARC hardware)? I can not find any reference in SDN or Service Market Place? Any reference will be much appreciated.
2) How can I confirm my sapdata fielsystems are ZFS?
3) What actions do you recommend for me to resolve the SAPINST errors? Do I follow the note "Note 995050 - DB6: NO FILE SYSTEM CACHING for Tablespaces" to disable "Direct I/O" for all DB2 tablespaces? I have seen Markus Doehr's forum Link:[ thread|Re: DB2 on Solaris x64 - ZFS as filesystem possible?; but it does not state exactly how he overcame the error.
regards
Benny

Hi Frank,
Thanks for your input.
I have also found the command "zfs list" that would display any ZFS filesystems.
We have also gone back to UFS as the ZFS deployment schedule does not meet this particular SAP BW implementation timeline.
Has any one come across any SAP statement that states NW7 can be deployed with ZFS for DB2 database on Solaris SPARC platform. If not, I'll open an OSS message.
regards
Benny

DB2 9.7 DFACT.SQL syntax error in Import ABAP phase - System Copy

Hi all. I'm trying a system copy with a source system SAP ECC 6.0 ehp4 based on NW 701 and db2 LUW 9.1 .
As it seems supported by SAP, i'm using db2 LUW 9.7 in target system.
O.S. is Windows 2008.
I got an error in phase "Import ABAP".
Sapinst.log says:
INFO 2010-02-18 10:12:14.337
An error occured and the user decided to retry the current step: "|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
INFO 2010-02-18 10:12:14.509
Switched to user: devadm.
INFO 2010-02-18 10:12:14.572
Creating file C:\Program Files\sapinst_instdir\ERPEhP4\LM\COPY\DB6\SYSTEM\CENTRAL\AS-ABAP\import_monitor.java.log.
INFO 2010-02-18 10:12:14.603
Switched to user: devadm.
INFO 2010-02-18 10:12:14.618
Working directory changed to C:\Program Files\sapinst_instdir\ERPEhP4\LM\COPY\DB6\SYSTEM\CENTRAL\AS-ABAP.
INFO 2010-02-18 10:12:14.618
Output of C:\j2sdk1.4.2_24-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2010-02-18 10:12:44.790
Execution of the command "C:\j2sdk1.4.2_24-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_24-rev"
Java(TM) Platform, Standard Edition for Business (build 1.4.2_24-rev-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_24-rev-b06, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 73, failed 0, total 75.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 73, failed 1, total 75.
WARNING[E] 2010-02-18 10:12:44.790
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2010-02-18 10:12:44.790
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
Looking into import_monitor.java.log i found that the problem is in dfact import.
I've looked into sapdfact.log and i found:
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100218105045
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.01/V1.4 [UNICODE]
Compiled Jan 28 2010 20:22:25
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error -loadprocedure fast LOAD:COMPRESS_ALL
(DB) INFO: connected to DB
(DB6) INFO: COMPRESS YES is set during table creation.
(DB6) DB2 9.5 automatic dictionary creation does not require an explicit REORG.
(DB6) Compression threshold is ignored.
(GSI) INFO: dbname   = "DEV                                                                                "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SRVSAPDEV"
(GSI) INFO: release = "6.0"
(GSI) INFO: version = "6002 Service Pack 2"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 26 Step 5)"
(DB) ERROR: DDL statement failed with SQL error
( ALTER TABLE "/BI0/E0PPM_VC1" DROP PRIMARY KEY )
(SQL error -539)
error message returned by dsql:
SQL0539N Table or nickname "SAPDEV./BI0/E0PPM_VC1" does not have a "PRIMARY" key. SQLSTATE=42888
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB6) INFO: executing DDL statements for object /BI0/E0PPM_VC1 from external SQL file.
(DB) ERROR: DDL statement failed with SQL error
( CREATE TYPE 2 UNIQUE INDEX "/BI0/E0PPM_VC1~0" ON "/BI0/E0PPM_VC1"   ("KEY_0PPM_VC1T" ,   "KEY_0PPM_VC11" ,   "KEY_0PPM_VC1U" ,   "KEY_0PPM_VC1P" )   USING STOGROUP ___FAI PRIQTY 16   SECQTY 10240 FREEPAGE 0 PCTFREE 0   GBPCACHE CHANGED DEFINE NO   BUFFERPOOL BP3 COPY NO   PIECESIZE 2097152 K CLUSTER NOT PADDED )
(SQL error -7)
error message returned by dsql:
SQL0007N The character "_" following "" )   USING STOGROUP" is not valid. SQLSTATE=42601
(DB) INFO: disconnected from DB
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100218105045
So as you can see it seems that there's some syntax error in dfacl.log. The wrong SQL statement referred by sapdfact.log is
ind: /BI0/E0PPM_VC1~0
sql: CREATE TYPE 2 UNIQUE INDEX "/BI0/E0PPM_VC1~0" ON "/BI0/E0PPM_VC1"
("KEY_0PPM_VC1T" ,
"KEY_0PPM_VC11" ,
"KEY_0PPM_VC1U" ,
"KEY_0PPM_VC1P" )
USING STOGROUP ___FAI PRIQTY 16
SECQTY 10240 FREEPAGE 0 PCTFREE 0
GBPCACHE CHANGED DEFINE NO
BUFFERPOOL BP3 COPY NO
PIECESIZE 2097152 K CLUSTER NOT PADDED ;
|
ALTER TABLE "/BI0/E0PPM_VC1"
ADD PRIMARY KEY ("KEY_0PPM_VC1T",
"KEY_0PPM_VC11",
"KEY_0PPM_VC1U",
"KEY_0PPM_VC1P") ;
Am i missing something?
Data in referred tables (infocubes) isn't really important.
Is there a safe way to proceed?
Thanks in advance.
Regards
Simone Zaffalon

And this is the strange point: my source system is not a BI and my dataclasses .SQL files are not empty.
Me too i would expect that the files should be empty but instead they are full of object definitions.
For example i have APPL0.SQL that contains a list of all tables of ECC system, for example
tab: MAMT
sql:     CREATE TABLE "MAMT"
        ("MANDT" SAPDB6VARCHAR(000003)
        DEFAULT '000' NOT NULL,
        "MATNR" SAPDB6VARCHAR(000018)
        DEFAULT ' ' NOT NULL,
        "SPRAS" SAPDB6VARCHAR(000001)
        DEFAULT ' ' NOT NULL,
        "MEINH" SAPDB6VARCHAR(000003)
        DEFAULT ' ' NOT NULL,
        "MTXID" SAPDB6VARCHAR(000002)
        DEFAULT ' ' NOT NULL,
        "LFDNR" SAPDB6VARCHAR(000002)
        DEFAULT '00' NOT NULL,
        "MAKTM" SAPDB6VARCHAR(000040)
        DEFAULT ' ' NOT NULL)
        IN "&location&"
        INDEX IN "&locationI&"
        LONG IN "&locationL&"
      COMPRESS YES;
      ALTER TABLE "MAMT" LOCKSIZE ROW;
and like this for all others tables.
What would occur if i launch an import with such .SQL files?
(shuld i put this question to another thread or is fine for you to answer on this?)
Thank you again.
Simone Zaffalon

Can not get CF7 to Communicate with DB2 v9.1

Installed on a windows server I have DB2 UDB Enterprise
edition 9.01, all the fix packs are current.
I also loaded ColdFusion MX7.02 Enterprise edition on the
same server. I had to download the latest JDBC Drivers from Adobe.
I let db2 create the DSN connections in the file system panel
one Local connection and one TCP/IP both connections passed the
connection test. Db2 also passed the connections test. I tested
each connection separately deleting one before creating the other.
When I get to coldfusions connection data sources panel and
create either connection I get a “ time out” message
from the server when I test the connection.
This morning I installed IIS on the server and now I am
getting a new message below.
I do know that the connections are set up right and the
authorities are correct. If I change any of the parameter either in
db2 or coldfusion it knows that they are incorrect (i.e. password,
user id, db name, server etc.)
I set up oracle and ASP in about 3 hours. Its been 3 weeks
since we purchased Coldfusion and I still can not get Coldfusion
and DB2 working together
Any help would be greatly appreciated
Connection verification failed for data source: TOOLSDB
java.sql.SQLException: [Macromedia][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.
The root cause was that: java.sql.SQLException:
[Macromedia][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.
Thanks bob

the only thing i can think of right now is to remove the pc suite, reinstall it, reboot your pc and see if the same problem presists
You know what I love about you the most, the fact that you are not me ! In love with technology and all that it can offer. Join me in discovery....

Error in Defining parameters for DB2 while installing IDES on Windows 2003

Hello,
I am facing DB2/LUW:V9:RDBMS:DB2/LUW:WINDOWS_X86_64.* While Installing IDES on 64 bit windows 2003 with DB2 V9., At the time of defining parameters, the SAPInst is not taking the Package Location for the Database parameter and giving me this error.
The set of database DVDs does not contain the DVDs for Windows and I have also downloaded 51032045_3      DB2 9 LUW Windows Server on x64 64bit - Full Install from marketplace but its of no use as well.
Please help me out with the correct database setup file or any other work around ASAP.
Many Thanks !!!
Amit

Hi,
You can download from this path.... My Company's Application Components"........ Complimentary Software".......... DB2/UDB" DB2 FOR LUW 9.7
     51039450      DB2 LUW 9.7 FP2SAP RDBMS Windows x64
     51039451      DB2 LUW 9.7 FP2SAP RDBMS Client
OR
51040240 DVD DB2 LUW 9.7 FP3SAP RDBMS WINDOWS
51040241 CD DB2 LUW 9.7 FP3SAP RDBMS client
Thanks
Siva

Can't Drop a table in DB2 UDB on Windows 2003 server Ent EDT

Previus step:
Database DB2 ibm for a sap BW production got error in log - cause: no space on disk.
system mark database as bad.
system connection with db was restored with sap and ibm support
I'm in disaster recovery situation,
we have rebuilded index and table that got problem in db2dart report.
Now Sap system go up, we have successfully dumped 29 of 30 tables with db2dart /ddel command, now there is only a table that got problem:
sapbw2.rsbatchdata
we can't drop this table.
We try with this step:
1) db2dart bw2 /ddel
 (table id)1837 (tablespaceid)10 0 9000000
 we obtain a SQL file
2) db2dart bw2 /mt
 (table id)1837 (tablespaceid)10 (password that you provide)
3) db2 drop bw2 sapbw2.rsbatchdata after this command we got a crash database.
2008-05-29-16.33.59.148000+120 I5094483F478 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : section stmt
DATA #1 : Hexdump, 29 bytes
0x000000003806E1F4 : 6472 6F70 2074 6162 6C65 2073 6170 6277 drop table sapbw
0x000000003806E204 : 322E 5253 4241 5443 4844 4154 41 2.RSBATCHDATA
2008-05-29-16.33.59.148000+120 I5094963F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: section stmt
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.148000+120 I5095124F174 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: informational text for dump
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.148000+120 I5095300F166 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: Unrelocation Needed
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.148000+120 I5095468F204 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: Section relocated; reltables in global cache inaccessible
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.148000+120 I5095674F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: section ptr
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5095834F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: section size
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5095995F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: dynamic ptr
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5096155F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: dynamic size
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5096316F165 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: shared dynamic ptr
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5096483F166 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: shared dynamic size
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5096651F169 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: dynamic section header
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.179000+120 I5096822F164 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: offset in section
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.179000+120 I5096988F153 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: opcode
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.179000+120 I5097143F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: agg_mode
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.179000+120 I5097300F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: section1
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.179000+120 I5097457F168 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: End of dumped section
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.241000+120 I5097627F438 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlC_dump, probe:25
MESSAGE : Context info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for
 additional data.
2008-05-29-16.33.59.273000+120 I5098067F452 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
MESSAGE : Private workspace info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
2008-05-29-16.33.59.288000+120 I5098521F451 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
MESSAGE : Shared workspace info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
2008-05-29-16.33.59.304000+120 I5098974F450 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_cache_full_dump, probe:25
MESSAGE : Package Cache info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000
 for additional data.
2008-05-29-16.33.59.335000+120 I5099426F166 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** DRDA ASCB ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.335000+120 I5099594F171 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** DRDA CMNMGR CB ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.335000+120 I5099767F171 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** RECEIVE BUFFER ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.335000+120 I5099940F169 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** SEND BUFFERS ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.335000+120 I5100111F174 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** CONNECTION HANDLE ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.335000+120 I5100287F172 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** DRDA ATTRIBUTES ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.351000+120 I5100461F171 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** AS UCINTERFACE ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.351000+120 I5100634F468 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
RETCODE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error detected"
 DIA8501C A buffer pool logic error has occurred.
2008-05-29-16.33.59.351000+120 I5101104F331 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
2008-05-29-16.33.59.820000+120 I5101437F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.820000+120 I5101595F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.835000+120 I5101753F400 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_AGENT_CB Pointer:
DATA #1 : Hexdump, 8 bytes
0x0000000005AA4AB0 : 0001 E637 0000 0000 ...7....
2008-05-29-16.33.59.835000+120 I5102155F160 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_AGENT_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.835000+120 I5102317F398 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_TRAN_CB Pointer
DATA #1 : Hexdump, 8 bytes
0x0000000005AA4AA0 : 8087 FD0F 0000 0000 ........
2008-05-29-16.33.59.835000+120 I5102717F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_TRAN_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.835000+120 I5102878F397 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_APP_CB Pointer
DATA #1 : Hexdump, 8 bytes
0x0000000005AA4AA8 : 0083 FD0F 0000 0000 ........
2008-05-29-16.33.59.835000+120 I5103277F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_APP_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.835000+120 I5103437F348 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 21 bytes
OPEN PERM CURSORS: >>
2008-05-29-16.33.59.851000+120 I5103787F345 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 22 bytes
OPEN PERM CURSORS: <<
2008-05-29-16.33.59.851000+120 I5104134F348 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 21 bytes
OPEN TEMP CURSORS: >>
2008-05-29-16.33.59.851000+120 I5104484F345 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 22 bytes
OPEN TEMP CURSORS: <<
2008-05-29-16.33.59.851000+120 I5104831F346 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 19 bytes
CLOSED CURSORS: >>
2008-05-29-16.33.59.851000+120 I5105179F364 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_CCB:
DATA #1 : String, 49 bytes
pool(TID)=0, obj(FID)=33, indexid(IID)=0, class=0
2008-05-29-16.33.59.851000+120 I5105545F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.851000+120 I5105702F364 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_CCB:
DATA #1 : String, 49 bytes
pool(TID)=0, obj(FID)=23, indexid(IID)=0, class=0
2008-05-29-16.33.59.851000+120 I5106068F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.866000+120 I5106225F342 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 19 bytes
CLOSED CURSORS: <<
2008-05-29-16.33.59.866000+120 I5106569F154 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLI_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.866000+120 I5106725F167 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.866000+120 I5106894F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_APP_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.866000+120 I5107054F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_TRAN_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.866000+120 I5107215F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_LFPB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.929000+120 I5107373F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.929000+120 I5107530F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.945000+120 I5107688F168 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.945000+120 I5107858F373 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : locklist
DATA #1 : String, 59 bytes
Check
t1srv5bw\db2dumpBW2\l57042.000 for additional data.
2008-05-29-16.33.59.960000+120 I5108233F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS AGENT CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.976000+120 I5108394F152 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLCA
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.976000+120 I5108548F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.976000+120 I5108708F162 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC PID
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.976000+120 I5108872F412 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->rdbcolidLen =
DATA #1 : Hexdump, 2 bytes
0x00000000056ABEA8 : 0800 ..
2008-05-29-16.33.59.976000+120 I5109286F425 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->pkgnamcsn.rdbcolid =
DATA #1 : Hexdump, 8 bytes
0x00000000056ABECA : 4E55 4C4C 4944 2020 NULLID
2008-05-29-16.33.59.976000+120 I5109713F491 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->rdbname =
DATA #1 : Hexdump, 18 bytes
0x00000000056ABEB8 : 4257 3220 2020 2020 2020 2020 2020 2020 BW2
0x00000000056ABEC8 : 2020
2008-05-29-16.33.59.976000+120 I5110206F491 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->pkgname =
DATA #1 : Hexdump, 18 bytes
0x00000000056ABEDC : 5351 4C43 3245 3037 2020 2020 2020 2020 SQLC2E07
0x00000000056ABEEC : 2020
2008-05-29-16.33.59.976000+120 I5110699F416 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->pkgcnstkn =
DATA #1 : Hexdump, 8 bytes
0x00000000056ABEEE : 4141 4141 4163 4555 AAAAAcEU
2008-05-29-16.33.59.991000+120 I5111117F406 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->pkgsn =
DATA #1 : Hexdump, 2 bytes
0x00000000056ABEF6 : CB00 ..
2008-05-29-16.33.59.991000+120 I5111525F496 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pStatementText =
DATA #1 : Hexdump, 29 bytes
0x00000000062D0CC0 : 6472 6F70 2074 6162 6C65 2073 6170 6277 drop table sapbw
0x00000000062D0CD0 : 322E 5253 4241 5443 4844 4154 41 2.RSBATCHDATA
2008-05-29-16.33.59.991000+120 I5112023F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS APPL CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.991000+120 I5112183F165 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS NESTED APPL CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.991000+120 I5112350F166 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS SP REGISTERS CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.991000+120 I5112518F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS TRAN CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.991000+120 I5112678F165 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS NESTED TRAN CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5112845F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS COORD CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5113006F160 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS NESTED CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5113168F164 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS INVOCATION CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5113334F165 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS ACTIVE STMT CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5113501F164 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: NLSWA:DatabaseApp
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5113667F153 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: nlsacb
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.023000+120 I5113822F157 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: dbNLSAppCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.023000+120 I5113981F162 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: UnicodeNLSAppCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.023000+120 I5114145F464 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
MESSAGE : Error -2045771763 when reading LSN 000006BDB601F7A1 from log file
 S0000000.LOG tellMe 0 dpsAcbFlags 0 setSkipOutputBuf 0
2008-05-29-16.34.00.023000+120 I5114611F468 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
MESSAGE : NOTE: The log state was marked bad by another process, this message
 is not an indication of an error with the logger process
2008-05-29-16.34.00.523000+120 I5115081F457 LEVEL: Error
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
 DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.00.538000+120 I5115540F459 LEVEL: Error
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlptudo, probe:1010
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
 DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.00.538000+120 I5116001F455 LEVEL: Warning
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlptudo, probe:4350
MESSAGE : LSN being undone:
DATA #1 : Hexdump, 8 bytes
0x0000000005AA87A8 : 0000 06BD B601 F7A1 ........
2008-05-29-16.34.00.538000+120 I5116458F157 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLP_TENTRY
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.554000+120 I5116617F166 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.554000+120 I5116785F155 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.554000+120 I5116942F154 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.554000+120 I5117098F390 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlptud1, probe:1880
MESSAGE : Due to error during UNDO, database will be brought down.
2008-05-29-16.34.00.570000+120 I5117490F459 LEVEL: Error
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlpxrbk, probe:3040
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
 DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.00.570000+120 I5117951F155 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.570000+120 I5118108F154 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.570000+120 I5118264F384 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : cr_error:
DATA #1 : Hexdump, 4 bytes
0x00000000056AF4C8 : 0100 0000 ....
2008-05-29-16.34.00.570000+120 I5118650F465 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrrbck_dps, probe:20
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
 DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.00.585000+120 I5119117F692 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 1
sqlerrmc: 2
sqlerrp : SQLRL281
sqlerrd : (1) 0x87020002 (2) 0x00000002 (3) 0x00000000
 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
 (7) (8) (9) (10) (11)
sqlstate:
2008-05-29-16.34.00.585000+120 I5119811F418 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, global services, sqlzerdm, probe:40
DATA #1 : Hexdump, 4 bytes
0x0000000005AA8B08 : 0D00 1086 ....
2008-05-29-16.34.01.070000+120 I5120231F461 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrrbck, probe:40
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
 DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.01.070000+120 I5120694F474 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_post, probe:88
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
 DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.01.070000+120 I5121170F435 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_post, probe:190
DATA #1 : Hexdump, 4 bytes
0x0000000005AA8F6C : 0200 0287 ....
2008-05-29-16.34.01.070000+120 I5121607F383 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : UCstate:
DATA #1 : Hexdump, 4 bytes
0x00000000056AFA70 : 4200 0004 B...
2008-05-29-16.34.01.070000+120 I5121992F692 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -984 sqlerrml: 1
sqlerrmc: 2
sqlerrp : sqlrrbkd
sqlerrd : (1) 0x8610000D (2) 0xFFFFFC2C (3) 0x00000000
 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
 (7) (8) (9) (10) (11)
sqlstate:
2008-05-29-16.34.01.070000+120 I5122686F508 LEVEL: Error
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, DRDA Application Server, sqljsTermAgentReply, probe:10
MESSAGE : DIA5000C A DRDA AS token "AGENT TERMINATING" was detected. The
 diagnostic data returned is (SRVDGN): "SQLERRP:sqlrrbkd
 SQLCODE:-984".
2008-05-29-16.34.01.085000+120 I5123196F691 LEVEL: Error
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -984 sqlerrml: 1
sqlerrmc: 2
sqlerrp : sqlrrbkd
sqlerrd : (1) 0x8610000D (2) 0xFFFFFC2C (3) 0x00000000
 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
 (7) (8) (9) (10) (11)
sqlstate:
2008-05-29-16.34.01.085000+120 I5123889F375 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:20
RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"
2008-05-29-16.34.01.085000+120 I5124266F692 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1034 sqlerrml: 0
sqlerrmc:
sqlerrp : SQLRR09E
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
 (4) 0x00000000 (5) 0xFFFFFFE2 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
 (7) (8) (9) (10) (11)
sqlstate:
2008-05-29-16.34.01.085000+120 I5124960F152 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLCA
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.085000+120 I5125114F385 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : CREATOR
DATA #1 : Hexdump, 8 bytes
0x0000000037E6D1AE : 4E55 4C4C 4944 2020 NULLID
2008-05-29-16.34.01.085000+120 I5125501F385 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : PACKAGE
DATA #1 : Hexdump, 8 bytes
0x0000000037E6D1CC : 5351 4C43 3245 3037 SQLC2E07
2008-05-29-16.34.01.101000+120 I5125888F154 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: CREATOR
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.101000+120 I5126044F154 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: PACKAGE
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.101000+120 I5126200F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: REQUEST TYPE
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.101000+120 I5126361F162 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: APM COMMON INFO
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.101000+120 I5126525F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: CONTEXT MCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.116000+120 I5126685F161 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: CONTEXT MEM CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.116000+120 I5126848F160 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: PACKAGE ENTRY
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.116000+120 I5127010F438 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlC_dump, probe:25
MESSAGE : Context info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for
 additional data.
2008-05-29-16.34.01.116000+120 I5127450F452 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
MESSAGE : Private workspace info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
2008-05-29-16.34.01.116000+120 I5127904F451 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
MESSAGE : Shared workspace info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
2008-05-29-16.34.01.132000+120 I5128357F450 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_cache_full_dump, probe:25
MESSAGE : Package Cache info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000
 for additional data.
2008-05-29-16.34.01.132000+120 I5128809F376 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"
2008-05-29-16.34.01.132000+120 I5129187F331 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
2008-05-29-16.34.01.601000+120 I5129520F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.601000+120 I5129678F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.601000+120 I5129836F400 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_AGENT_CB Pointer:
DATA #1 : Hexdump, 8 bytes
0x0000000005AA8970 : 0001 E637 0000 0000 ...7....
2008-05-29-16.34.01.601000+120 I5130238F160 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_AGENT_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.616000+120 I5130400F398 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_TRAN_CB Pointer
DATA #1 : Hexdump, 8 bytes
0x0000000005AA8960 : 8087 FD0F 0000 0000 ........
2008-05-29-16.34.01.616000+120 I5130800F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_TRAN_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.616000+120 I5130961F397 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_APP_CB Pointer
DATA #1 : Hexdump, 8 bytes
0x0000000005AA8968 : 0083 FD0F 0000 0000 ........
2008-05-29-16.34.01.616000+120 I5131360F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_APP_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.616000+120 I5131520F348 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 21 bytes
OPEN PERM CURSORS: >>
2008-05-29-16.34.01.616000+120 I5131870F345 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 22 bytes
OPEN PERM CURSORS: <<
2008-05-29-16.34.01.632000+120 I5132217F348 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 21 bytes
OPEN TEMP CURSORS: >>
2008-05-29-16.34.01.632000+120 I5132567F345 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 22 bytes
OPEN TEMP CURSORS: <<
2008-05-29-16.34.01.632000+120 I5132914F346 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 19 bytes
CLOSED CURSORS: >>
2008-05-29-16.34.01.632000+120 I5133262F364 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_CCB:
DATA #1 : String, 49 bytes
pool(TID)=0, obj(FID)=33, indexid(IID)=0, class=0
2008-05-29-16.34.01.632000+120 I5133628F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.632000+120 I5133785F364 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_CCB:
DATA #1 : String, 49 bytes
pool(TID)=0, obj(FID)=23, indexid(IID)=0, class=0
2008-05-29-16.34.01.632000+120 I5134151F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.648000+120 I5134308F342 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 19 bytes
CLOSED CURSORS: <<
2008-05-29-16.34.01.648000+120 I5134652F154 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLI_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.648000+120 I5134808F167 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.648000+120 I5134977F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_APP_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.648000+120 I5135137F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_TRAN_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.648000+120 I5135298F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_LFPB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.710000+120 I5135456F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.710000+120 I5135613F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.710000+120 I5135771F168 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.726000+120 I5135941F373 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : locklist
DATA #1 : String, 59 bytes
Check
t1srv5bw\db2dumpBW2\l79922.000 for additional data.
2008-05-29-16.34.01.741000+120 I5136316F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS AGENT CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.741000+120 I5136477F152 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLCA
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.757000+120 I5136631F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.757000+120 I5136791F162 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC PID
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.757000+120 I5136955F412 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->rdbcolidLen =
DATA #1 : Hexdump, 2 bytes
0x00000000056ABEA8 : 0800 ..
2008-05-29-16.34.01.757000+120 I5137369F425 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->pkgnamcsn.rdbcolid =
DATA #1 : Hexdump, 8 bytes
0x00000000056ABECA : 4E55 4C4C 4944 2020 NULLID

I can't use db2drop because this command crash my db with this table.
So I must take another way.
============================================================
About DB2 Administration Tools Environment
============================================================
DB2 administration tools level:
Product identifier SQL08025
Level identifier 03060106
Level DB2 v8.1.12.99
Build level s060429
PTF WR21370
============================================================
Java development kit (JDK):
Level IBM Corporation 1.4.2
============================================================

RSDU_ANALYZE_TABLE_DB2/DB2

Similar Messages

Maybe you are looking for