Relativity EVENT.LOG reldbsrv : WARN: Unix event ID=-2147483574: Event Msg=Query Time Out Exceeded

Hi! I hope you all are well

Is there any documentation on the event.log file that Relativity DataServer creates? We see tons of WARN with Query Time Out Exceeded and as there is a problem working with the Data Server since a couple of days ago, I would like to understand the cause of the problem.

reldbsrv : WARN: Unix event ID=-2147483574: Event Msg=Query Time Out Exceeded: HostName=PCSC0532, Application=Relativity® Database Designer, IP=10.8.0.66
reldbsrv : WARN: Unix event ID=-2147483574: Event Msg=Query Time Out Exceeded: HostName=PCSC0533, Application=Relativity JDBC Client, IP=10.8.0.194

Any ideas?

Regards,

  • I didn´t find any documentation on the event.log file.

    This problem is happening on a system that worked for years without any issue and started with this problem this week. They run under Solaris Sparc with a Relativity DataServer version 12.07.

    It started with one catalog and now other catalogs have the same problem. You can open the catalog in the Relativity Designer and shows the tables but if you want to enter into the details, Designer hungs. The same happens with other tools.

    The event.log shows a lot of those WARN messages but we do not understand what that Unix event ID is.

  • What errant behavior, or problem, are the Relativity users experiencing? For example, are their queries hanging, or, are the receiving any error messages when executing queries?

    Have you tried reinstalling the Relativity Data Server in the affected environment? Also, have you tried restoring the catalog(s) from a known, working, backup copy?

    The event.log messages that you have provided indicate that the Relativity Data Server has detected, and terminated, a runaway query. A runaway query is one that has ceased to return result rows to the ODBC application for longer than the configured "ConnectionQueryTimeout" value, which is by default, 60 minutes.

    The event.log does not capture detailed information about query execution, therefore, it might be necessary to enable the Relativity Data Server tracing in order to gather additional information in regards to why a specific query failed. However, since, Relativity used to work properly in this environment, it is possible that either the Relativity installation, or the catalog in use, have been corrupt in some way. So, the first thing I would recommend doing would be to uninstall/reinstall the Relativity Data Server, and, restore a backup copy of the catalogs being used.

    If restoring the environment does not address the concern, then, you could enable some of the Relativity Data Server tracing, and, see if you can determine what particular queries are failing, which, might provide some additional insight into why that particular query is failing. The Relativity Data Server tracing options are configurable in the [SimbaTrace] section of the Relativity Data Server "odbc.ini" file, that, is located in the "etc" sub-directory of your product installation.

    **For more information in regards to Relativity Data Server odbc.ini file, please see the Relativity Client / Server for UNIX Installation Guide.

    Regards,

    Steve Jolivet
    Senior SupportLine Representative, North American Support

  • Thanks Steve!

    I will ask them to reinstall the Relativity Data Server and to look for a backup of the rcg files from last week.

    I enabled the trace today for a while but I didn´t see any significant info there.

    What happens is really strange. You open the Relativity Designer, open a catalog and the tables names are shown but when you try to open one, Designer hungs.

    The same happens with other tools like Servoy in the same situation.

    A Servoy solution in production returns error but that error is not trapped in any Relativity log file in order to understand what is causing the problem.

    In the other hand, a user uses RazorSQL and can query data from that tables.

    If you need the trace log or any other file just let me know.

    Regards,

    Juan Urraburu

  • Hi Steve,

    I've been working these days on this. The problem seems to be related to a particular file but the situation is really strange. Let me tell you my last test:

    I copied the COBOL data file to my Windows PC
    I created a new Relativity Catalog and imported the COBOL definition from a program I created.
    Created a table and could see the first 100.000 records without problems.

    I copied the catalog to the Unix server and created a new Relativity Server entry into the odbc.ini using the Relativity Server Admin tool.

    I used the DBSample java program and connected to that DSN

    Clicked on View Tables and the table is shown.

    Then enter a simple SQL command select * from that table and nothing happens, the program hungs with no error. This also happen if I use RazorSQL or Servoy but work with other tables.

    Any idea?

    Juan Urraburu

  • I copied the catalog to the Unix server and created a new Relativity Server entry into the odbc.ini using the Relativity Server Admin tool.

    What version of the Relativity Data Server is deployed on the UNIX machine?

    I used the DBSample java program and connected to that DSN

    Have you tried using the Relativity Data Client for ODBC to access this table?  If so, does that work?

    You can use an ODBC testing tool, like Microsoft's ODBCTest, to test the Relativity Data Client with the affected table.

    Then enter a simple SQL command select * from that table and nothing happens, the program hungs with no error. This also happen if I use RazorSQL or Servoy but work with other tables.

    The behavior that you are describing might indicate that you are encountering an issue with the Relativity Data Server product.  Therefore, I recommend that you submit a Case to Micro Focus SupportLine, so that, this concern can be properly investigated, and, reported to Development if necessary.

    You can submit Cases to Micro Focus SupportLine on the Micro Focus SupportLine Web Portal.

    **As a note; once a Case has been created, we can provide you with a means to upload the affected catalog, and data file, for analysis.

    Regards,

    Steve Jolivet
    Senior SupportLine Representative, North American Support

  • Thanks Steve.

    Version is 12.07 and yes, I also tried with ODBC via RazorSQL with the same result. In fact with Relativity Designer you can see the same problem just trying to edit the definition of that table (it freezes with no error).

    Regards,

    Juan Urraburu