This is unfortunate and it is significant: this is not a technology problem. It is a people problem.
Your planner has already decided:
you need less than 24 GB of RAM;
you can't ask for what you want;
you must provide proof to justify what you will ask for.
Why 24? As opposed to 240? If...
It sounds like someone is trying to have their cake and eat it too: economize on disk capacity, but have the ability to grow back to a larger size on demand. As Tom pointed out, this is a false economy.
I have had a client call me one day because their database wouldn't start. It was...
I understand that the user might want the data later. That explains why you want the data. It does not explain why you are choosing to export it, delete it, and then import it. My question, again: why not just leave the data in place? That would also allow the user to read it later. What...
Another possibility that these totals are both correct. For example, if you had another 100 records where cono=888 and they got deleted somehow between the start and end of your test, the total record count of 900 would be correct.
I suggest that you query for all distinct values in this field...
What is the point of deleting and then reloading the records? Why not just leave them in place? And have you thought about how you will handle schema changes to this table?
How are you exporting and importing the data?
What are the indexes on com and are all of them active?
What is your...
I'm not sure what you want. Are you talking about saving the product (Progress OpenEdge AppServer Enterprise/Basic) or your AppServer-based application code?
If the latter, you can migrate it to PASOE. If the former, well, good luck. I can't see PSC ever bringing it back, despite PASOE's...
Absolutely. I ran into the same situation on AIX on OE 10.2B.
Archiving directly to a DR box, in theory, sounds like a great idea. When it works, it ensures your archived AI extents are away from production as soon as possible, giving you a good recovery position. However as you have seen...
Check the database log for error messages.
If your client uses the -clientlog startup parameter, check the client log for error messages. If it doesn't, add -clientlog <path to client log file> to your client startup parameters.
A while back, someone asked about upgrading from 10.1A02 to 11.7. So that's quite similar to your situation. This was my response, I hope you find it useful:
Question - Does anyone have a demo of Progress database migration?
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.