on 02-25-2008 2:41 PM
Hello, we have an NWDI (NW04s) with SP13. Our developers can't connect anymore with their NWDS to the CBS.
In the default.trc on NWDI I find the following error message.
#1.5^H#001125C558CE00770000000900187078000446FC77810564#1203950057489#com.sap.tc.cbs.server.rt.bs.BSAdmin
##com.sap.tc.cbs.server.rt.bs.BSAdmin######ac6e59c0e3ae11dcab67001125c558ce#Thread[CBS BSA Orc,10,SAPEngi
ne_System_Thread[impl:5]_Group]##0#0#Error##Java###
[EXCEPTION]
#3#Unable to instantiate a Build Space administrator!
Build Space "NW1_GEMS_C" [bsID: 87, version: 7] [in-queue: on, out-queue: "on", processing: on]#Unexpecte
d response status [200 OK]#com.sap.tc.cbs.api.CommunicationException: Unexpected response status [200 OK]
at com.sap.tc.cbs.comm.Repository.execute(Repository.java:68)
at com.sap.tc.cbs.api.impl.BSFacade.getOwnerBuildspace(BSFacade.java:510)
at com.sap.tc.cbs.server.rt.bs._BuildSpaceValidator.checkWorkspace(_BuildSpaceValidator.java:87)
at com.sap.tc.cbs.server.rt.bs._BuildSpaceValidator.validateWSs(_BuildSpaceValidator.java:57)
at com.sap.tc.cbs.server.rt.bs.BSAdmin.validate(BSAdmin.java:183)
at com.sap.tc.cbs.server.rt.bs.BSAdmin.onInit(BSAdmin.java:175)
at com.sap.tc.cbs.server.rt.bs.BSAdmin.<init>(BSAdmin.java:143)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.determineChanges(BSAdminOrc.java:430)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.validateBuildSpaceData(BSAdminOrc.java:217)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.act(BSAdminOrc.java:339)
at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:139)
at java.lang.Thread.run(Thread.java:761)
#
#1.5^H#001125C558CE00770000000B00187078000446FC77810AC7#1203950057490#com.sap.sql.jdbc.direct.DirectPrepa
redStatement##com.sap.sql.jdbc.direct.DirectPreparedStatement######ac6e59c0e3ae11dcab67001125c558ce#Threa
d[CBS BSA Orc,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Database/sql/jdbc/direct#Jav
a#com.sap.sql_0003##SQL error occurred on connection b0d0td02:NW1:SAPNW1DB: code=-99,999, state="null", m
essage="[ibm][db2][jcc][102][10040] Non-atomic batch failure. The batch was submitted, but at least one
exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements.
=> (-803,23505,Error for batch element \#1: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;SA
PNW1DB.CBS_LOCK)";
SQL statement is "INSERT INTO "CBS_LOCK" ("LOCKID","LOCKGROUP","LOCKIT") VALUES (?,?,?)".
[EXCEPTION]
#6#-99999#<null>#[ibm][db2][jcc][102][10040] Non-atomic batch failure. The batch was submitted, but
at least one exception occurred on an individual member of the batch.
Regards,
Alexander
Is the database full? In any case, check the database status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.