Messages

1

OD/WEK & JAVA API / Re: Finding Segment date serach field in AG

« on: April 10, 2017, 12:58:08 AM »

Hi JD

We have a common search portal which is to search across all the repositories (CMOD, P8 etc). Search portal holds GUID, Segment date and AG name in DB from CMOD. For retrieval, Search portal provides the above values (not field names) to CMOD. We have one to one folder AG mapping. GUID field name is same across all AGs & folders. Only difficulty is to find the Segment date field name in OD and corresponding mapping in folder to set the search criteria. Hope this explains the scenario better.

Thanks

2

OD/WEK & JAVA API / Finding Segment date serach field in AG

« on: April 07, 2017, 02:11:26 AM »

Hi

Please help on how to find Segment (date) field for an AG which is having multiple date fields using ODWEK. Also the corresponding folder field to which the segment field is mapped. I have an idea like get all the AG fields and use the mask values to find the Segment Date field { mod(mask/4,2) = 1  }. Thanks in advance.

3

MP Server / ARSSOCKD crashes in V9.0.0.6

« on: June 08, 2016, 09:01:19 AM »

Hi All

We are running CMOD 9.0.0.6 with DB2 9.7 and TSM 6.3.5 all hosted in same AIX server.

ARSSOCKD process went down without any error message. DB2 and TSM had no issue during the time. After checking the AIX alog, we noticed that below error message thrown from TSM just before the crash. There is no error in syslog also.


0 Wed Jun  8 15:27:03 SGT 2016 arssockd (ARCHIVE): 2016-06-08 15:27:03.006064 231261 BRCHILW  2 429 ARS0429E TSM Error: ANS1033E (RC-53)  An invalid TCP/IP address was specified.
, Return Code=-53, Reason=0, File=arssmsms.cpp, Line=1235  Srvr->a01goddb1a<-         0 Wed Jun  8 15:27:03 SGT 2016
         0 Wed Jun  8 15:27:03 SGT 2016 arssockd (ARCHIVE): 2016-06-08 15:27:03.014272 0 ARSMSG  2 146 ARS0146E The communication layer was unable to receive data.  The error number is 35
         0 Wed Jun  8 15:27:03 SGT 2016 arssockd (ARCHIVE): 2016-06-08 15:27:03.032617  ARSSOCKD  4  ARSI Message Error


Also whether the below ulimit values any reason for the arssockd crash?

time(seconds)        unlimited
file(blocks)              unlimited
data(kbytes)           unlimited
stack(kbytes)         4194304
memory(kbytes)     unlimited
coredump(blocks)     0
nofiles(descriptors) 2000
threads(per process) unlimited
processes(per user)  unlimited

Anyone faced similar issue before? Kindly help.

4

MP Server / Re: Increase System Log message text field length

« on: May 31, 2016, 02:15:51 AM »

Hi JD

I could see ARSAG table contains all 34 columns as given in the IBM 9.0 Admin guide in my upgraded instance. Also I am able to bring up the application in 9.0V. Only issue is the System Log message text still having the 254 varchar.

Thanks
Anand

5

MP Server / Sync user password between 2 Ondemand instances

« on: May 30, 2016, 03:19:59 AM »

Hi All

We have two separate CMOD instances (Primary & Seconday running 9.0.0.6 and DB2 9.7) both active and documents are loaded separately and are in sync. Users accesses documents through Windows client usually login into Primary but sometimes go to Secondary instances if any slowness in accessing documents in Tape.

We want to sync the user login passwords between the two instances if any user reset the password in one instance and not in another instance. Previously in V8.4, passwords sync was done by exporting the passwords from arsuser table from primary and updating the same passwords on secondary using SQL update. Since in 9.0, due to change in password encryption type, we cannot perform the same and also this process not supported by IBM.

Need help on this. Thanks !

6

MP Server / Re: Increase System Log message text field length

« on: May 30, 2016, 01:41:34 AM »

I have got SQL error while trying to update the System Log using steps mentioned in the upgrade guide. Anyone, kindly help.

7

MP Server / Increase System Log message text field length

« on: April 21, 2016, 12:48:10 AM »

Hi All,

In our environment, System Log message text field is configured for 254 characters length. As for audit purpose, we added to log few of the metadata field values in System Log during document retrieval. Since the field length is 254 chars only, some of the metadata field values are truncated. So planning to increase the message text length to 500 chars.

Kindly advise whether updating the System Log AG is also same as others (Rename old AG , Copy and create a new System Log AG and update the field with 500 chars in new AG and map to Sys Log folder) or Update DB or any other way?

Thanks !

8

MP Server / Re: Speed of TSM database to DB2

« on: April 17, 2016, 08:28:11 PM »

We just completed TSM 5.5 to 6.3 migration, and the TSM database export & import to new 6.3 DB2 process took around 1 hr to complete for ~5 GB database size.

9

MP Server / Re: Segmentation fault while loading PDF using PDF indexer

« on: February 19, 2016, 01:11:10 AM »

We found out that for those AGs which we are getting core dump while loading, few metadata fields went missing (while seeing in Admin client and exporting the AG using ARSXML but available in ARSAGFLD table) after upgrade. Upon further analysis, we found that for those missing fields, the MASK value in ARSAGFLD table are having -ve value eg. -32756,-32766 etc.  MASK column is of SMALLINT type in 8.4.0.x version and converted to INT type on later versions. We suspect that the MASK values were altered during the upgrade casting the column from SMALLINT to INT. We provided the details to IBM for confirmations. Waiting for their reply. Anyone faced similar scenario while upgrading from 8.4.0.x version.

10

MP Server / Re: Segmentation fault while loading PDF using PDF indexer

« on: February 17, 2016, 05:14:02 AM »

kbsiva, Checked all the ENV variables. All set as recommended. Checked ARSTMP , HOME dir path permission and space. All okay.

Raised PMR case with IBM. Waiting for their reply.

11

MP Server / Segmentation fault while loading PDF using PDF indexer

« on: February 16, 2016, 04:51:37 AM »

Hi

After upgrading Ondemand server & PDF indexer component from 8.4.0.3 to 9.0.0.6 MP in AIX server, getting Segmentation fault while trying to load PDF files using PDF indexer. We are running Ondemand using root user and checked the ulimit. All values set for unlimited only.

Indexer process completing successfully and creating proper *.ind and *.out.

Issue only for PDF using PDF indexer, all other types (AFP, TEXT and PDF using generic indexer) are loading without issues.

Error msg:
ARS4315I Processing file >/home/drcoana/TEST.PDF<
ARS4334I Load Version <9.0.0.6>  Operating System <AIX> <6.1>  OS Userid <root>  Install Location </usr/lpp/ars/>
ARS4335I Server Version <9.0.0.6>  Operating System <AIX> <6.1>  Database <DB2> <09.07.0011>
ARS4302I 02/16/16 15:07:21 -- Indexing started, 66728 bytes to process
ARS4901I TRIGGER1=ul(5.99,0.99),lr(6.71,1.16),*,'FACTORPRO'
ARS4901I FIELD1=ul(0.99,0.99),lr(1.44,1.16),0
ARS4901I FIELD3=ul(1.34,1.49),lr(1.92,1.66),0
ARS4901I FIELD4=ul(7.38,0.99),lr(7.58,1.16),0
ARS4901I INDEX1='ReportID',FIELD1
ARS4901I INDEX3='ReportDate',FIELD3
ARS4901I INDEX4='pccode',FIELD4
ARS4901I INDEXSTARTBY=1
ARS4901I parmdd=./TEST.PDF.parm
ARS4901I inputdd=/home/drcoana/TEST.PDF
ARS4901I outputdd=./TEST.PDF.out
ARS4901I indexdd=./TEST.PDF.ind
ARS4901I resobjdd=./TEST.PDF.res
ARS4902I Number of input pages = 9
ARS4922I ARSPDOCI completed code 0
ARS4308I 02/16/16 15:07:21 Indexing completed
ARS4312I 02/16/16 15:07:21 -- Loading started, 65525 bytes to process
Segmentation fault

ARSLOAD Trace:

26345606:1 02/16/2016 15:07:21:840035 ERROR arsload.c(4793)ArcLOADP_LoadFile:Current state msg_buf=ARS4312I 02/16/16 15:07:21 -- Loading started, 65525 bytes to process
 rc=1
26345606:1 02/16/2016 15:07:21:840045 INFO arsload.c(4793)ArcLOADP_LoadFile:Current state msg_buf=ARS4312I 02/16/16 15:07:21 -- Loading started, 65525 bytes to process
 
26345606:1 02/16/2016 15:07:21:840050 FLOW arsload.c(768)ArcLOADP_StatusMsg1:Return
26345606:1 02/16/2016 15:07:21:840080 INFO arsload.c(5044)ArcLOADP_LoadFile:Load Started
26345606:1 02/16/2016 15:07:21:840087 FLOW arsload.c(905)ArcLOADP_Run:Enter
26345606:1 02/16/2016 15:07:21:840093 FLOW arsload.c(849)ArcLOADP_OSArgsInit:Enter
26345606:1 02/16/2016 15:07:21:840120 FLOW arsload.c(875)ArcLOADP_OSArgsInit:Return os_argv=4580849456
26345606:1 02/16/2016 15:07:21:840125 FLOW arsadmin.c(5035)ArcADMIN_MainRun:Enter
26345606:1 02/16/2016 15:07:21:840140 INFO arsadmin.c(5962)ArcADMIN_MainRun:Current state u_argv[1]=load title_str=/usr/lpp/ars/bin/arsadmin -s ./TEST.PDF.out -i ./TEST.PDF.ind -h localhost -u admin -g FMFPROOPS-STD -a FP4751SG-FMS -P 30957 -U 0 -Z  -x /home/drcoana/26345606.sysload
26345606:1 02/16/2016 15:07:21:840148 INFO arsadmin.c(5989)ArcADMIN_MainRun:Current state title_str=/usr/lpp/ars/bin/arsadmin -s ./TEST.PDF.out -i ./TEST.PDF.ind -h localhost -u admin -g FMFPROOPS-STD -a FP4751SG-FMS -P 30957 -U 0 -Z  -x /home/drcoana/26345606.sysload
26345606:1 02/16/2016 15:07:21:840194 FLOW arsadmin.c(2605)ArcADMINP_SetNodeId:Enter
26345606:1 02/16/2016 15:07:21:840202 FLOW arsadmin.c(2744)ArcADMINP_SetNodeId:Return rc=0
26345606:1 02/16/2016 15:07:21:840964 INFO arsadmin.c(7111)ArcADMIN_MainRun:Current state index_file=./TEST.PDF.ind resource_file=(null)


Need help to figure out the issue.

12

MP Server / System Log query failing while using ARSDOC QUERY

« on: August 12, 2015, 02:04:30 AM »

Hi All

In order to generate user login report for past 6 months in Ondemand, I planned to run arsdoc query with msg_num 30 and output the result to text file and then use scripts to generate the report like number of logins by each user and last login time. But when I execuete below arsdoc query in command line, I am getting "server failed during search operation" error even though I queried for 1 day timestamp.

/usr/lpp/ars/bin/arsdoc query -h localhost -u <userid> -p <password> -f 'System Log' -i "where time_stamp between 1439308800 and 1439395199" -H
/usr/lpp/ars/bin/arsdoc query -h localhost -u <userid> -p <password> -G 'System Log' -i "where time_stamp between 1439308800 and 1439395199" -H

08/12/15 16:30:00 : The server failed during a search operation.  View the System Log for additional messages.

While checking in the System log through Windows client, I could see error below DB error with message number 13.

13    DB Error: [IBM][CLI Driver][DB2/AIX64] SQL0101N  The statement is too long or too complex.  SQLSTATE=54001  -- SQLSTATE=54001, SQLCODE=-101, File=arsdoc.c, Line=2529

For the DB error code SQL0101N , reason stated is due to Statement Heap size.  But the above query is not a complex one and also the same working fine when I tried through Windows Client.

I also checked the System Log AG field properties and time_stamp is defined as Segment field and for partition. Similar setup we have in UAT and I am able to query without any issue.

Ondemand Version : 8.5.0.9 MP in AIX platform
Db2 : 9.7

Please advise.

13

MP Server / Re: ARSDB drop table command

« on: July 23, 2015, 06:14:19 AM »

 Thanks Justin. I changed the retention as 1 year and run arsmaint -d for system log AG. Able to reclaim 30 GB space. 

Just to know, what is the correct syntax for arsdb to delete any segment table in Ondemand? Thanks in advance.

14

MP Server / ARSDB drop table command

« on: July 20, 2015, 07:14:47 AM »

We want delete System Log tables in test environment as the System log table count reaches 100+ and occupies more space. We tried with all the below commands to drop old tables and indexes from DB. But getting the errors as unknown table.

Please correct me if wrong with the commands. Thanks in advance.

root is the instance owner & Instance name is ARCHIVE. CMOD version is 8.5.0.9 MP. Db2 is 9.7.

arsdb -I ARCHIVE -d SL10
arsdb -I ARCHIVE -d root.SL10
arsdb -I ARCHIVE -e SL10
arsdb -I ARCHIVE -e root.SL10

Are you sure you wish to drop the database tables and/or indexes:arsdb: Unknown table sl10
Are you sure you wish to drop the database tables and/or indexes:arsdb: Unknown table root.sl10

15

MP Server / Re: Doument expired in TSM not in CMOD

« on: July 09, 2015, 03:08:18 AM »

Adding new field and limit by query restriction seems easy and will try this way. Thanks Alessandro. !!!