cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X

DataLogger Out of memory error

EA_11204094
2-Guest

DataLogger Out of memory error

"PostgreSQL database is running out of memory even though the total database size is only 500MB and the server has 1TB of RAM. I'm writing 800 values per minute into the database using a data logger. How can I resolve this issue?"

 

"It gives two different errors. The errors are as follows. I am using Kepserver version V6.6.350.0."

 
1 ACCEPTED SOLUTION

Accepted Solutions
ntripathi
13-Aquamarine
(To:EA_11204094)

Greetings @EA_11204094 

I trust you’re having a great day. 

I noticed your recent post about encountering an error related to opening a recordset on the log group ‘xxx’. The specific error message states: “Unable to open recordset on log group ‘xxx’. Reason: Out of memory while reading tuples.”

 

To address this issue, follow these steps:

  1. Check the “Use Declare/Fetch” Option:

    • Navigate to your DSN (Data Source Name) configuration.
    • Look for an option related to “Declare/Fetch” or “Use Declare/Fetch.”
    • Ensure that this option is enabled. If it’s currently disabled, enable it.
    • Save your changes.


ntripathi_1-1718896674655.png

 

        2. Restart the Application or Service:

  • After making the configuration change, restart the application or service that uses this DSN.
  • This step ensures that the new settings take effect.

View solution in original post

2 REPLIES 2
ntripathi
13-Aquamarine
(To:EA_11204094)

Greetings @EA_11204094 

I trust you’re having a great day. 

I noticed your recent post about encountering an error related to opening a recordset on the log group ‘xxx’. The specific error message states: “Unable to open recordset on log group ‘xxx’. Reason: Out of memory while reading tuples.”

 

To address this issue, follow these steps:

  1. Check the “Use Declare/Fetch” Option:

    • Navigate to your DSN (Data Source Name) configuration.
    • Look for an option related to “Declare/Fetch” or “Use Declare/Fetch.”
    • Ensure that this option is enabled. If it’s currently disabled, enable it.
    • Save your changes.


ntripathi_1-1718896674655.png

 

        2. Restart the Application or Service:

  • After making the configuration change, restart the application or service that uses this DSN.
  • This step ensures that the new settings take effect.

Thank you for the solution. Thanks to you my problem is solved

Top Tags