here attached the fail.sql file.
The SQLConsole is the one that into guptatechnologies.com is available for 11.7 version...
http://www.guptatechnologies.com/softwa ... onsole.zip
We tried to use the SQL Base command Center but every time that we open the "Table Lock" section .... the command center crash.....
It's the same problem as the first report: first a 1312 error (which shuts down the database) then a rollback error because the database is shut down.
What does the service errors show? Is there an event log? I suspect that there is another process that is running in the background that is causing the server engine to shut down.
We might need to get a netlog if we can't get this resolved.
The description for Event ID (300) in Source (Gupta SQLBase) could not be retrieved. The local computer may not have the necessary information in the registry or DLL files to display messages from a remote computer. Use / AUXSOURCE = flag to retrieve this description. For more information are part of the event: Database PLASTIAPE shutdown: Database Has Been shut down (please disconnect).
Can you try running it as an application instead of it as a service, i.e. stop the service and just double-click on the dbntsrv.exe? If that gets zapped then we can rule out a network process killing services...
https://support.guptatechnologies.com/su ... 27&t=11686
We had a lot of "SQLBase" transaction on our console, all users blocked without the possibilities to "cut" the transaction....
We are thinking that the "SQL Console" can cause this and we are trying to re-activate the new "Management Console".
We will activate also the DB as an application as suggested..
we ask to all users to stay outside the system but a specific user is showed (and he switched off his PC) under the "DB Engine" but under SQL Console we have a "SQLBase" transaction freezed with lot of Xlocks table.
the only thing to do is close and reopen the DB Engine.
(starting from now the DB is running in application mode as suggested)
You need to have a look at the cursor display to see what cursors are open. I suspect some cursor is not using an index and has locked up all the resources. You can use SQLConsole to have a look at a SQL Statement and Execution Plan of a cursor that have a very high SQL Cost.
No, the user is using the program normally.
We note that from the console when users run the operations the user name disappears and the message "SQLBase", stays there for a few seconds, and then disappears and returns the user name (with the same number of connection).
Sometimes "SQLBase" crashes and no longer able to exit the transaction, while blocking all others.
Who is online
Users browsing this forum: [Ccbot] and 0 guests