• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerServer
  • Database error -1 Failed to commit because there is no available database connection or transaction

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (5)

Resolved Database error -1 Failed to commit because there is no available database connection or transaction

  1. Issue
0
Votes
Undo
  1. Pascal Phan
    Pascal Phan
  2. PowerServer
  3. Thursday, 11 May 2023 18:28 PM UTC

I am using PB 2022 Build 1878 I get the following errors:

Follow by:

I am using IIS local Server in my laptop and started the session manually by code successful 

The database using was Oracle 19c

I troubleshoot with DBA and he was certain those errors came from PowerServer Web but we don't know how to fix it.

Any ideas?

 

Closing App after several hours of inactivity
Error opening 32-bit DLL in a 64-bit PB app
Responses (5)
Pascal Phan
Pascal Phan Accepted Answer Pending Moderation
  1. Friday, 12 May 2023 15:12 PM UTC
  2. PowerServer
  3. # 1

Hi Chris,

This is my Oracle database profile settings for SESSIONS_PER_USER, IDLE_TIME, and CONNECT_TIME

 

 

 

Comment
There are no comments made yet.
Pascal Phan
Pascal Phan Accepted Answer Pending Moderation
  1. Friday, 12 May 2023 15:08 PM UTC
  2. PowerServer
  3. # 2

Hi Chris,

 

 

I don't think any changes in settings will help because this is the C/S App converting to PowerServer App and the database access info was stored in the Web Server not the Client. 

I think PowerServer lost the connection after opening many data windows and data windows childs

plus queries in my app.

 

 

Attachments (1)
RBRS PowerSer Database Advance Setting.PNG RBRS PowerSer Database Advance Setting.PNG
Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 12 May 2023 15:23 PM UTC
Hi Pascal;

If your PS Server though is hosted under IIS, then it's IIS timeouts also come into play. You might need to change these settings so that your HTTP/HTTPS sessions are not being truncated prematurely based on what your Web Server team has the timeout setting values at..

Tip: Also check your "Application Pool" timeout settings as well in IIS. HTH

Regards ... Chris
  1. Helpful
There are no comments made yet.
Pascal Phan
Pascal Phan Accepted Answer Pending Moderation
  1. Friday, 12 May 2023 14:35 PM UTC
  2. PowerServer
  3. # 3

My SQL is:

SQL.AutoCommit = False

and database Resource:

SESSIONS_PER_USER, IDEL_TIME, and CONNECT_TIME are UNLIMITED

This app was originally CLIENT SERVER app and I was trying to convert to POWERSERVER app. If I ran the same app in C/S it went fine with no errors

I think this error occurred after the POWERSERVER app loaded many data windows and data windows child plus ran many queries.  

 

Comment
There are no comments made yet.
David Xiong @Appeon
David Xiong @Appeon Accepted Answer Pending Moderation
  1. Friday, 12 May 2023 08:26 AM UTC
  2. PowerServer
  3. # 4

Hi Pascal,

 

Please check if your application has a commit or rollback statement while sqlca.autocommit = true. 

If yes, those commit or rollback statements need to be commented out.

 

Regards,

David

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 11 May 2023 18:49 PM UTC
  2. PowerServer
  3. # 5

Hi Pascal;

   My guess is that it might be either  a DBMS "timeout" caused by a) inactivity or b) a super long running DB process .

   Please check with your Oracle DBA team and see what these O19C server timeout settings are within your environment.

   Then adjust them accordingly in either A) the O19C server or B) within your PowerServer DBMS "cache" settings...

HTH

Regards ... Chris

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.