Question:
Hi all
OS : Win2K Server
DB : DB2 7.2
R/3 : 4.6C with 4.6D Kernel
Just finish installating the Dialog Instance without errors. But when I try to start the instance. It won't start, and there are no logs for me to trace the problem. Anyone have face this problem before? Thanks
Regards
William
Answer:
Hi,
Look in startsap logs in the sidadm home directory of the app server.
Post any errors msgs here.
Regards,
Syed
Answer:
Hi,
Similar to what the pervious posting states, check
/usr/sap/<SID>/<Instance Name>/work for the latest
traces (dev_*). You will likely see the errors.
You may want to check the equivalent directory (Likely
/usr/sap/<SID>/DVEBMGSxx/work) for possible
errors in the server containing the central instance,
as it is trying to communicate with the dialog instance.
Some of the time, you may find useful information in the database
and/or OS logs.
Good Luck
Answer:
Hi there, here is the sapstart.log
SAP-R/3-Startup Program
Starting at 2005/10/12 1:32:53
Startup Profile: "\\PROD_SAP\SAPMNT\PRD\sys\profile\START_D00_app3-sap"
Starting Programs
(532) Execute: F:\usr\sap\PRD\D00\exe\sapcpe.exe pf=\\PROD_SAP\sapmnt\PRD\SYS\profile\PRD_D00_app3-sap
(360) CreateProcess: F:\usr\sap\PRD\D00\exe\disp+work.exe pf=\\PROD_SAP\sapmnt\PRD\SYS\profile\PRD_D00_app3-sap
It went from yellow light back to grey.
Answer:
Hi,
Similar to what the pervious posting states, check
/usr/sap/<SID>/<Instance Name>/work for the latest
traces (dev_*). You will likely see the errors.
You may want to check the equivalent directory (Likely
/usr/sap/<SID>/DVEBMGSxx/work) for possible
errors in the server containing the central instance,
as it is trying to communicate with the dialog instance.
Some of the time, you may find useful information in the database
and/or OS logs.
Good Luck
Thanks for the info, I'll go through the logs first!
William
Answer:
This might be the problem why I can't start the server. They said that my Db2 version does not match. So I need to use the exact DB2 version and the fixpack version? What about Kernel files? Can the dialog instance have kernels that are new than the Central Instance? Thanks
BTW
Here is my dev_evt
--------------------------------------------------
trc file: "dev_w7", trc level: 1, release: "46D"
---------------------------------------------------
*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS all, M
*
B
B Wed Oct 12 01:53:43 2005
B create_con (con_name=R/3)
B Loading DB library 'F:\usr\sap\PRD\D00\exe\dbdb6slib.dll' ...
B Library 'F:\usr\sap\PRD\D00\exe\dbdb6slib.dll' loaded
B Version of library 'F:\usr\sap\PRD\D00\exe\dbdb6slib.dll' is "46D.00", patchlevel (0.2071)
C DbSl trace SM50: switch request to level 1
B New connection 0 created
M relno 4640
M patchlevel 0
M patchno 2113
M intno 0
M pid 1952
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 7 1952) [dpxxdisp.c 976]
I MtxInit: -2 0 0
X EmInit: MmSetImplementation( 2 ).
X <ES> client 7 initializing ....
X Using implementation std
M <ES> Memory Reset enabled
X ES initialized.
M
M Wed Oct 12 01:53:44 2005
M ThSysUsrCheck: clear T7
M calling db_connect ...
C Registering callback for dynamic profile parameters
C
C DB6 (DB2 UDB) database interface 46D.00 [opt]
C
C DB6 shared library (dbdb6slib) patchlevels
C (0.66) Lower isolation level reading cluster tables (note 316120)
C (0.137) Support for COMMON_TABLE_EXPRESSION (note 324496)
C (0.337) Wrong error class for SQL0289; use UPTO hint (note 363894)
C (0.437) Prepare: several mySAP.com components in one DB (note 379572)
C (0.481) Avoid Core Dump in DBSL Trace at CREATE TABLE statements (note 386217)
C (0.486) DB connect user in lower case letters (note 388052)
C (0.574) 'COMMIT' statements in ST05 trace (note 400480)
C (0.723) Improved Optlevel Handling (note 425035)
C (0.761) Allow DB2 V6.1 again (note 429230)
C (0.814) DB6: DDL autocommit (note 436717)
C (0.815) DB6: corrupted row in table buffer (note 437692)
C (0.838) DB6: TRUNCATE TABLE does not work (note 443680)
C (0.913) DB6: DBIF_RSQL_ERROR_INTERNAL after mass insert (note 453313)
C (0.914) DB6: ROLLBACK before disconnect (note 455769)
C (0.965) DB6: Missing execution times in DbSl Trace (note 483879)
C (0.997) Enable larger IN-Lists (note 493063)
C (0.1033) DB6: support SUBSTITUTE_LITERALS Hint (note 150037)
C (0.1064) Correct error handling for SQLAllocHandle (note 503564)
C (0.1069) Gather CC statistics for ST02 (note 505914)
C (0.1089) Correct CC statistic values (note 505914)
C (0.1108) Support DECIMAL literals (note 150037)
C (0.1139) Patch for SQLCancel operations (note 520974)
C (0.1159) Check for DB2 version mismatch (note 503122)
C (0.1237) Free CSTRACE statements (note 548282)
C (0.1282) View definition unknown (SE14) (note 555254)
C (0.1365) Handling of quotes in literal values (note 575672)
C (0.1372) UPDATE first row on cluster write (note 579215)
C (0.1440) Ignore warnings in get_dbparms sqlfxdb() (note 596298)
C (0.1506) DBSl patch collection 04/2003 (note 618003)
C (0.1508) DB6: no autocommit for NOT LOGGED INITIALLY statements (note 436717)
C (0.1537) DB6: check collating sequence (note 376746)
C (0.1564) DB6: dynamic load of DB2 libs on AIX,SOLARIS (note 641036)
C (0.1579) DB6: EXEC SQL WITH HOLD: out of handles (note 647325)
C (0.1588) DB6: corrupted short texts in CStrace (note 648128)
C (0.1589) DB6: release instance attachments (note 649139)
C (0.1600) Object consistency (note 650475)
C (0.1607) DB6: ignore SQL0000W warnings ( dbcode = 0 ) (note 653463)
C (0.1608) DB6: failed Login attempts for sidadm (note 653573)
C (0.1612) DB6: CALL PROCEDURE fix (note 655274)
C (0.1630) DB6: new hint 'CONVERT_FAE_TO_CTE' (note 150037)
C (0.1637) DB6: multiconnect to DB2/390 database (note 663756)
C (0.1644) DB6: core in buildStmtStr() (note 666831)
C (0.1647) DB6: SQLExtendeBind for DB2 procedures (note 668550)
C (0.1714) DB6: CLI0125E Function sequence error on ROLLBACK (note 687453)
C (0.1740) DB6: avoid missalignment traps on HP (note 698223)
C (0.1769) DB6: SET CURRENT QUERY OPTIMIZATION (note 710970)
C (0.1796) DB6: multiconnect to DB2/390 or DB2/400 database (note 663756)
C (0.1851) DB6: CLI LOAD bei INSERT ... FULLSELECT (note 737914)
C (0.1877) DB6: support OPT_FOR_ROWS 0 hint (note 150037)
C (0.1930) DB6: SQL0518 statement not in a prepared state (note 776540)
C (0.1983) DB6: Saturn Patch Collection (note 804651)
C (0.2024) DB6: check DB2_WORKLOAD=SAP registry setting (note 825392)
C (0.2066) DB6: V8.2.2 optguidelines in OPEN SQL (note 150037)
C (0.2071) DB6: link dbdb6slib.dll on windows with libdb6.obj (note 761159)
C
C Build includes
C - smart optlevel handling (non-UR, FAE)
C
C
C ..retrieving configuration parameters
C ..done
C
C Wed Oct 12 01:53:46 2005
C Connected to DB2 version '07.02.0003'
C AUTO DETECT: default optlevel for non UR scans set to 0
C AUTO DETECT: default optlevel for FAE statements set to 0
C AUTO DETECT: Enabling CLI execute chaining
C DB2 client software level: 07.02.0009
C DB2 server software level: 07.02.0003
C *** ERROR => DB2 software level mismatch between client and server.
[dbdb6.c 1470]
C
C Note: Version mismatches between client and server
C ---- may cause any type of unexpected errors and
C unforseeable behavior.
C Running client and server with different
C software levels is NOT supported by SAP.
C See note 101809 for a list of supported DB2 software levels
C
C If you temporarily need to override this check for
C testing purposes please refer to note 503122
C *** ERROR in DB6Connect[dbdb6.c, 1502]
C &+ DbSlConnectDB6: Version mismatch between client '07.02.0009' and server '07.02.0003'
C &+
C &+
C *** ERROR in DB6Connect[dbdb6.c, 1502]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c 1184]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3) [thxxhead.c 8395]
M
M Info for wp 7
M
M stat = 4
M reqtype = 1
M act_reqtype = -1
M tid = -1
M mode = 255
M len = -1
M rq_id = -1
M rq_source = 255
M rq_info = 0
M last_tid = 0
M last_mode = 0
M int_checked_resource = 0
M ext_checked_resource = 0
M report = > <
M action = 0
M tab_name = > <
M
M *****************************************************************************
M *
M * LOCATION SAP-Server app3-sap_PRD_00 on host app3-sap (wp 7)
M * ERROR tskh_init: db_connect
M *
M * TIME Wed Oct 12 01:53:46 2005
M * RELEASE 46D
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 8506
M * COUNTER 1
M *
M *****************************************************************************
M
M Entering ThSetStatError
M call ThrShutDown (1) ...
M ***LOG Q02=> wp_halt, WPStop (Workproc 7 1952) [dpnttool.c 310]
Answer:
William,
At least the problem has been identified.
The main issue is as follows:
" *** ERROR => DB2 software level mismatch between client and server. [dbdb6.c 1470] ".
I worked with some DB2 installations (On non-SAP systems)
and I do not remember the compatibility info. between client
levels and server levels, though I remember that it was an
issue.
The SAP DB2 installation guide should contain that info. , or refer
to a note that contains it. Perhaps 'service.sap.com/pam (Product
Availability Matrix) has that info.
Also, search sapserv (Notes and otherwise) on 'dbdb6.c'.
I keep the kernel levels of the central instance and the dialogs
the same. Otherwise, there is a good chance that it may not
work, though it seems like your immediate issue is DB2.
Answer:
William,
At least the problem has been identified.
The main issue is as follows:
" *** ERROR => DB2 software level mismatch between client and server. [dbdb6.c 1470] ".
I worked with some DB2 installations (On non-SAP systems)
and I do not remember the compatibility info. between client
levels and server levels, though I remember that it was an
issue.
The SAP DB2 installation guide should contain that info. , or refer
to a note that contains it. Perhaps 'service.sap.com/pam (Product
Availability Matrix) has that info.
Also, search sapserv (Notes and otherwise) on 'dbdb6.c'.
I keep the kernel levels of the central instance and the dialogs
the same. Otherwise, there is a good chance that it may not
work, though it seems like your immediate issue is DB2.
Hi there
after installing the same DB2 version and fixpack. Everything went well except one thing, in the event viewer, I kept getting this error "Transaction termination 00 (RAISE_EXCEPTION 20051013001445app3sap SAPSYS 0001 ) "
app3sap is my hostname.
Answer:
RAISE_EXCEPTIONS are typically errors related to the gui, but if you're using the latest gui/patch level there's an SAP note out there with what you need to do to troubleshoot those types of dumps.
_________________
http://help.sap.com
http://service.sap.com/notes
Answer:
RAISE_EXCEPTIONS are typically errors related to the gui, but if you're using the latest gui/patch level there's an SAP note out there with what you need to do to troubleshoot those types of dumps.
thanks prime
the server has been up for 2 days, everything seems to be normal but the performance isn't too good after reinstallation. A lot of dialog process ard taken too long to process. I guess there are still a lot of setting needs to be modified.