Thanks for the question, Tom.
Asked: May 30, 2002 - 2:13 pm UTC
Last updated: May 30, 2002 - 4:03 pm UTC
Version: 8.1.7
Viewed 1000+ times
You Asked
I set up "ctxsrv" here, and I'm checking the log contents to make sure it's doing what it should be. Based on the app behaviour, it is. But still I want to understand the log. Here's the beginning of the log below. It goes on like that continually. What does "cid=1026" mean? I love return codes of 0 as much as anyone, but I can't find any docs that explain why I should love it. Thanks, Tom.
Here's the ctxsrv log:
14:39:37 05/15/02 === OCO server startup ===
14:39:37 05/15/02 Initialized CORE
14:39:38 05/15/02 Connected to database.
14:39:38 05/15/02 === Initializing dispatcher ===
14:39:38 05/15/02 === Server startup completed. ===
14:39:40 05/15/02 DML batch: cid=1026
14:39:51 05/15/02 End batch, return code is 0
14:39:52 05/15/02 DML batch: cid=1026
14:39:52 05/15/02 End batch, return code is 0
14:47:28 05/15/02 DML batch: cid=1026
14:47:28 05/15/02 End batch, return code is 0
15:09:24 05/15/02 DML batch: cid=1026
15:09:25 05/15/02 End batch, return code is 0
15:12:21 05/15/02 DML batch: cid=1026
15:12:21 05/15/02 End batch, return code is 0
PS - now that I got my foot in the door... any chance you could put a timestamp on the asktom entries? It would help to know whether you're reading something you already read a while ago. Along the same lines, on the main listing of subjects, a marker beside the "new" ones would be nice too... basically, those that consist only of a question, and the first reply by you... as opposed to those that have been going back and forth for a while.
and Tom said...
it is Context InDex command, the 1026 corresponds to the index. When you add a row to your table, context adds a row to the dr$pending table. In there you'll see colums:
ctxsys@ORA8I.WORLD> desc dr$pending
Name Null? Type
----------------------- -------- ----------------
PND_CID NOT NULL NUMBER
PND_ROWID NOT NULL ROWID
PND_TIMESTAMP DATE
the CID is the cid you are seeing (what index). they have the rowid or primary key to be indexed in there as well.
Return code would be zero on success, not zero (with details) otherwise. Eg: an error might look like this:
13:51:57 02/10/99 End batch, return code is 1
13:51:57 02/10/99 DRG-50857: oracle error in drtldml(dml)
13:51:57 02/10/99 ORA-20000: ConText error:
ORA-28579: network error during callback from external procedure agent
ORA-6512: at "CTXSYS.DRUE", line 122
ORA-6512: at line 1
.
As for the timestamp, what I've done is:
o added the original date the question was "asked" in ()'s after the last updated date (what I've been showing) on the home page. Also, the number of days between the two is there.
o same for the search page.
o the "new" marker -- well, thats a bit hard. I guess I could put a "*" next to anything such that the last updated date is within X days/hours of the time they submitted it. The problem is that sometimes
a) a question takes a bit of time to answer -- hence it'll be NEW but not
marked as "new"
b) a question can be new yet have a back and forth trail on it very quickly
(meaning it stays at the top of the list for a while). This happens very
often
So, for now, I'll leave it with the two dates and number of days and we'll see how that goes.
Rating
(1 rating)
Is this answer out of date? If it is, please let us know via a Comment