Search results

You're right James, the docs are not clear. The KB says that you need to use prorest ... -newinstance (create a new DB GUID) and then use proutil db -C epolicy manage keystore rebind. https://community.progress.com/s/article/000028091 https://community.progress.com/s/article/000028092 In my...

There are SaaS-bsaed OpenEdge applications. You can read about database multi-tenancy in the documentation. As for security and privacy, those can mean many things to different people, so some detail is needed. As always, your options will be better if you use the latest release and commit to...

I would hate to see that. Yes, the site could do with some more hands-on administration. But occasional spam aside, historically this site has had a very good signal-to-noise ratio. There is a lot of valuable content in all the posts of the regulars. It would be a shame to see that body of...

Good call Patrice! That helps a lot until the posts themselves are deleted.

I didn't check the 9.1D, as I already have them, but I was able to download individual 10.0A PDFs from the Wayback links. Thanks Stefan!

OECC monitors PASOE and databases, and we don't have a PASOE forum, so this thread may as well live here for now. ;) I haven't used OECC 2.0 yet. It is on my list to get to when I have a chance. Please keep us updated on what you learn with this issue!

Agreed. In the past, some have argued in favour of using fixed-length extents to avoid paying the (theoretical) computational cost of extending the files. OpenEdge now provides the ability to pre-extend variable-length extents, so that should prevent having to pay that cost, and thus this...

If you have no empty AI extents (current extents are busy and others are full or locked), the database will continue writing to the busy extent as long as it can. If it is a variable-length extent, it will continue to grow. If it is a fixed-length extent, it will write until the extent fills...

This belongs in a new thread.

The original problem was stated as "recover a lot of "deleted" space after purging". And you have decided that the correct solution is purge/dump & load; specifically multi-threaded D&L. Why are you purging? Is it because you don't have the storage capacity you need? Is it because you are...

Binary dump does use an index. That is how it finds the records and determines their order in the dump file(s), and thus in the resulting table in the target. You use the -index n option to specify the dump index. Source...

Long story short, Progress added features like modern compression, multi-threaded backup, and multi-threaded restore, which might help you in the future. But they were added in 12.5 and later, so you won't get access to these features until you upgrade from the 12.2 (LTS, or Long-Term Support)...

It would help to know the specific release of Progress OpenEdge you are using, as probkup and prorest were enhanced later in the 12.x family of releases. The OE version format is major.minor.update, where major.minor is the release. E.g. "OpenEdge 12.8.7" is the 12.8 release with update 7...

Or add a new forum for PASOE, as there are people still using WebSpeed/App Server, and PASOE is a distinct and different technology.

I don't think this is a DB Admin question. ;)

Error 49 is a Progress bug. You are on 11.7.9, which is four and a half years old; the current update is 11.7.22. So you are missing 13 updates worth of bug fixes.

This seems relevant. You should not try to update Java while WebSpeed is running, any more than you should try to upgrade OpenEdge while there are running OpenEdge processes. The WebSpeed broker is Java-based.

https://community.progress.com/s/article/What-auditing-related-indexes-can-be-deactivated

Mod note: this thread should be in the Development forum.

Remember that best practice with OE Auditing is to keep minimal audit data in the source database, and archive (dump/delete) it regularly to an audit archive database. You should do audit data reporting from the archive database. This approach does the following: Keeps the source database...