Messages

16

MP Server / Trace Logs

« on: February 19, 2016, 01:33:02 AM »

Hi

After having a few server crashes in our SIT environment, I switched on the trace logging by setting the value to the highest levet (INFO, FLOW, WARNING, ERROR, etc). The server did crash again. But on looking into the trace log (after converting it into readable format), I did not see any ERROR information. All I saw was INFO and FLOW messages.

Does anyone have any suggestions to find out what caused the server to Crash?
Note that the System Log also didn't give much information.

Thanks
Pankaj.

17

MP Server / Re: Difference between hits and count

« on: February 03, 2016, 12:10:51 AM »

Bumping it again!!

18

MP Server / Re: Migrate the System log to another system like Terradata.

« on: January 11, 2016, 02:57:42 AM »

Agreed JD. But the management is reluctant in getting rid of the old data.

19

MP Server / ARS2164I

« on: January 11, 2016, 02:55:02 AM »

I got this message while creating a user on CMOD.
I do not see anything wrong with the file system.

Not sure if anyone else has seen this message?

"The operation could not be completed because required data resides on unavailable archive media. Contact your system administrator to make the data available."

20

MP Server / CMOD not starting

« on: November 12, 2015, 04:47:47 AM »

Tried restarting the cmod server but I see the below since a long time.

xxxx@xxxx>ps -ef | grep arssockd
xxxx 29452     1  0 11:34 pts/3    00:00:00 arssockd-DB2UT005: initializing
xxxx 29680 31149  0 11:39 pts/3    00:00:00 grep arssockd



Here is the dbfs usage.

/dev/mapper/root_vg-db2data1
                       15481840  14678992     16480 100% /apps/IBM/db2/xxxx/data1
/dev/mapper/root_vg-db2data2
                       10321208   8807484    989436  90% /apps/IBM/db2/xxxx/data2
/dev/mapper/root_vg-db2data3
                       10321208   6510916   3286004  67% /apps/IBM/db2/xxxx/data3

Any suggestions?

21

MP Server / Re: Migrate the System log to another system like Terradata.

« on: October 20, 2015, 06:24:08 AM »

Agreed Alessandro.
But my concern now is getting rid of the already existing logs.

22

MP Server / Migrate the System log to another system like Terradata.

« on: October 20, 2015, 12:09:26 AM »

We have this requirement to move the System logs to Terradata.
The reason this is being done is because these logs are consuming a lot of space and we do not have the option of moving them to TSM.

So we need to migrate the metadata and documents (message 87 stores a document with the load log).
Any pointers on how we should do the extraction of metadata and documents and then correspondingly link them.

23

MP Server / Re: Issue with search.

« on: September 28, 2015, 04:10:54 AM »

Apparently there had been a bad date in the input data that caused the DOC START DATE in the ARSSEG table to be set to 0 which is an invalid arsdate value. This was causing the issue.
However just updating the ARSSEG table did not help.
I had to move the entire data from old AG to new AG.
I am sure that would be a better way of doing it. But since I did not had much time for R&D, just created a new AG and migrated data after removing the entry that had a bad date.

24

MP Server / Re: Issue with search.

« on: September 24, 2015, 02:36:59 AM »

Yeah I already checked that and there is no issue with the SQL at all.

25

MP Server / Issue with search.

« on: September 23, 2015, 11:51:48 PM »

I have this strange situation.
I have 2 pair of Application Group and Application.
Both the pairs are exactly same except for their names and retention periods.

The two application groups are mapped to the same folder.
The Folder to AG mapping is also the same for both application groups.

I then loaded the same document with same dates but with different account numbers.
Note that this is online upload using ODWEK.

When I do individual  search by account number (say account 123 and 456), I get the results from both the AGs in subsequent queries.
When I use the Account number and Date combination (say account 123 and date 20150924) I get the expected result.
When I use the Account number and Date combination (say account 456 and date 20150924) I get no results.
A search by just account number = 456, returns the result. On analyzing the result, I do see the date column populated with 20150924.

I am not able to understand the reason for no results when I use the Account number and date combination for AG1 while the same search combination returns results from AG2!!

Thanks
Pankaj.

26

MP Server / Multiple Technology Systems

« on: September 15, 2015, 04:25:25 AM »

Here is an excerpt from the IBM documentation about scaling a CMOD system.

1. Single technology systems: The Content Manager OnDemand instance
consists of systems that are of the same architecture. For example, all
systems might be AIX systems.

2. Multiple technology systems: The Content Manager OnDemand instance
might consist of systems of different architectures. For example, the library
server and an object server might be on a z/OS system, two other object
servers might be on AIX systems, and another object server might be on a
Windows system.

Specific to 'Multiple Technology systems', I was unable to find any compatibility matrix that would tell me what combination of technology systems can I use. For example, can I use a Linux Library server with an i series Object server.
Do anyone have any pointers?

Cheers
Pankaj.

27

MP Server / Retrieving an AFP that was loaded with RESTYPE=NONE

« on: September 02, 2015, 10:39:45 PM »

Hi

I received an AFP file from the composition team.
This AFP does not have embedded resources in it.
The composition team also provided a resource file separately that will be common across all AFPs.

I could load the AFP with RESTYPE=NONE option.
I am not sure how to configure CMOD to use the resource file provided so that it can be used during retrieval and further for conversion into AFP.

Any suggestions?

Thanks
Pankaj.

28

MP Server / Re: Error Message 107 in the arssock.err file

« on: August 10, 2015, 04:37:36 AM »

Agree JD.
We were able to recreate this issue in other servers also.

How this happened was, someone defined an AG with a date field that had a 'LIKE' operator.
As soon as we fired the serach with the like operator on the date field, the server came down.
So now we know the root cause.

But the question is, how was someone able to add a Like operator to a field that was defined as a Date field?
If you select a filed to have type as Date, the 'LIKE' operator is automatically greyed out.

The only way that I could think of is creating a Folder using the ARSXML.

Any comments?

Cheers
Pankaj.

29

MP Server / Re: Error Message 107 in the arssock.err file

« on: August 06, 2015, 12:33:42 AM »

No I didn't check
Let me do that now.

Thanks
Pankaj.

30

MP Server / Re: Error Message 107 in the arssock.err file

« on: August 05, 2015, 02:25:09 AM »

Our production support team was able to replicate the issue in a lower environment.
The way it was replicated was using a 'like' operator for a date field.
This immediately caused the SIT server to go down.

I am not really very convinced that this caused the issue but at this point this is how it looks.