Listers,
I just ran the Sync Search database operation on one of my servers
(development server) which have most of the ITSM 7 apps installed including
SIM, EIE (AIE), Remedy Knowledge Management 7, CMDB 2... After what appears
like the sync ran successfully - I do get the prompt that the sync completed
successfully and the admin Run /Not Run Unique value does get reset to 0 on
accepting the prompt...
I had started the operation after deleting everything in the T and H tables
belonging to the details and reference forms and resetting the next ID
values to 1.. However I notice the following inconsistencies in the results
of the following SQL statements after the run of the Sync Search Database
operation...
SQL> select count(*) from t1632;
COUNT(*)
----------
17522
SQL> select count(*) from t1633;
COUNT(*)
----------
176587
SQL> select name, schemaid, nextid from arschema where name like 'object%';
NAME SCHEMAID NEXTID
--------------------- ---------- ----------
object_search_admin 1631 2
object_search_details 1632 17521
object_search_ref 1633 176591
>From my past experience I know first of all that these row counts in both
these forms is way less than what it should have been. So having suspected
that something was wrong I investigated and it appears like the sync
operation has actually failed although I got a successfully completed
prompt. Half the information is missing - for e.g. if I go to the Related
Workflow tab on the Helpdesk form fields, I see related filters, but no
other workflow like active links or menus etc that are attached to that
field.. (Yes this workflow does exist.)
What's even more weird is the next Id and count for T1632 which is 17521 and
17522 respectively.. How could the next ID be lower than the count when the
next ID should have been 17523??
Then there seem to be what might be missing rows in T1633. The next ID is
176591 and count is 176587 which should have been 176590. What happened to 3
records? Has anyone seen issues like these where there is an inconsistent
row count when compared to the next ID after a sync operation???
I checked the arxref.log file and as usual there are loads of errors
pointing to missing fields in the log, which I hear is 'normal' as Remedy
engineering has yet to clear off some of the redundant piece of workflow to
get rid of such problems.. Attached is the arxref.log file with piles of
those 'expected' errors. Does anyone know a way to get more information
written to this file? I know its not a good idea to do that considering that
this information is held in memory of the client until the operation is
complete before it is written to the file, but that's the only thing I can
think of doing if I wanted to trace what's happening without turning on the
SQL or API log which will get even bigger..
Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.
Cell: +1.732.331.5004
Desk: +1.732.698.7275
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.17.9/1197 - Release Date: 12/25/2007
8:04 PM
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
