I found a workaround - given that Procedure Editor does not require the quotes, I generated a .p file with the query I need within my test, and ran that file through the command line, outputting the results to the file. From there, it's easy enough to compare the generated file. I don't think...
It does. The test framework I'm using is written in Python (Robot Framework, using the pypyodbc library to run queries using ODBC), and backslashes are the Python standard way of escaping characters. Even if I run this through the Python console, the error message is identical, backslashes and...
I tried quoting the table name as you suggested, but executing the query with the name in quotes gives me this error: [DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Syntax error in SQL statement at or about "_user-id=\'something\'" (10713)')
Because the field in my where...
Is it possible to query Progress meta schema via ODBC? I have a meta schema table called _aud-audit-data that I would like to run a query against. I can query it with the Procedure Editor and DataDigger using a standard query: SELECT * from _aud-audit-data where _user-id='something' I'm...
While messing with the AdminService and looking through its log file as you suggested, I happened to bounce it, and... that fixed the issue.
My coworker also had the same issue with his machine, and we tried restarting the AdminService on his machine, and it worked there, too.
What a simple and...
When I try to start my database from the command line with `call dbman -database Docutapweb -start`, I get this error:
dbman hangs on the "starting" stage for several minutes, and eventually it shows that error, but if I watch OpenEdge explorer, the database is started almost instantly and I...
Well, the big news is that for the past 2 nights, probkup has run within my test suite without any hangups. I haven't made any new changes since then, just the ones I mentioned before that didn't have an effect right away. I don't know what happened, and I certainly hope that posting this...
That makes sense, and it's unfortunate that this is the way it's set up. I'm still curious about why it only seems to happen with scheduled tasks, though, and not when I run the backup manually. In my mind, there shouldn't be a difference in how the backup accesses the disk between the two...
In the past few days, I've been trying to replicate the problem with perfmon running, and naturally, because I'm watching it, it runs without a hitch. These tests usually run overnight; I've disabled probkup in the overnight run for now because I'm reluctant to to include a script that often...
The log file does have some strange stuff in it, now that you mention it.
For the first couple of tests I ran last night (and this is after the changes), the database never stopped properly. The only message I see is "Usernum 24 terminated abnormally" - this is most likely because at the...
I changed the configuration of the tasks in Task Scheduler to Windows 7, manually set the priority of each to 4 instead of 7, and increased the number of blocks in the DB buffer (through Progress Explorer) to 196000. Unfortunately, the problem is still happening. Is there something I'm...
I'm looking into how the machine in question handles caching. I'll let you know what I find.
I am using Windows 7, and I am using Task Scheduler to start up TestExecute to run the automated tests. I noticed that the tasks are all configured for Vista and Server 2008, though. It does seem to...
Hi all,
I have an application that uses Progress 10.2B that I'm running nightly automated regression tests against. There are multiple test projects, and I would like to backup the state of the database after every individual test project using probkup. Our database is tiny - only 2.9GB when...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.