cancel
Showing results for 
Search instead for 
Did you mean: 

Revising through API: "absence of session record in the database"

This happened out of the blue today (well after I cleared some database locks). Whenever I try to programmatically revise an ItemRevision, I get the following partial errors:

 

2015-01-27 13:50:43,677  WARN - Error0
2015-01-27 13:50:43,677  WARN - 	Code:     515239
2015-01-27 13:50:43,677  WARN - 	Severity: 3
2015-01-27 13:50:43,677  WARN - 	Message:  The session is in read-only mode because of the  absence of session record in the database.
2015-01-27 13:50:43,677  WARN - Error1
2015-01-27 13:50:43,677  WARN - 	Code:     214140
2015-01-27 13:50:43,677  WARN - 	Severity: 3
2015-01-27 13:50:43,677  WARN - 	Message:  The business object "CREO_MULTI_ITER01/B;1" could not be revised.

 

I can't find any information about this online. Does anyone know what this error is even referring to? Or what caused it? Or how to fix it?

 

Any help would be much appreciated.

 

Thanks!

 

2 REPLIES

Re: Revising through API: "absence of session record in the database"

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

It sounds like you might have run clearlocks -verbose in a 4tier environment which removed inactive sessions list in the database sessions table. However, they were not inactive but sleeping. When they wake up to perform an action you requested the db knows nothing about them. Restarting pool manager should resolve the whole problem or you can kill each warm started tcserver individually using the server manager admin console. Instead of running clearlocks verbose to clean up dead process locks try running list_users instead. You might be pleasantly surprised by what it actually does without bragging about it in the utilities reference (in other words, undocumented).

 

Best,

/Randy


Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: Revising through API: "absence of session record in the database"

Yup that fixed it. I figured it had something to do with that clearlocks command. Thanks a lot!