huge ALM file

[Steve Wood]

My ALM file on an SQL based application is approaching 2GB. I only have four reports, what makes this file so large and can it be "compressed"?

[Tom Cone Jr]

Re: huge ALM file

Steve, on the desktop side when an FPT file ( memo field ) grows that large it's a sign that the FPT is corrupted. I believe ( but don't know for certain ) that the ALM file is itself an FPT file. If correct this probably means the ALM is corrupted.

[Al Buchholz]

Re: huge ALM file

Many mods of the reports??.... probably just like the desktop side..

A database compact should lessen the size...

Unless it's corrupted...
Was all of the available space on the drive used up? That would happen when a corrupted memo file stops growing short of 2 gb... it ran out of space...

[Steve Workings]

Re: huge ALM file

Yup, compact the database first off. This grows big fast and a database compact can bring it right back down.

[JerryBrightbill]

Re: huge ALM file

You can always convert the library to a file system and then you don't have to worry about the ALM as there isn't one. All of items on the code tab, database properties, as well as all SQL reports and data sources are saved as files in a special library folder. The latest pre-release builds have greatly improved the process of using a file system and you can even publish the database library for SQL reports just as you can with the library.

[Lance Gurd]

Re: huge ALM file

Help,

Just did as Jerry suggested and everything on the code tab has disappeared, my named connections don't work and my sql reports are gone. How do I get them back?

[Steve Workings]

Re: huge ALM file

Lance - see the last few messages in this thread and my exchange with Selwyn:

http://msgboard.alphasoftware.com/al...ht=file+system

And note that Jerry's message is about improvements in the latest pre-release build.

I think there's a lot of benefit here (I particularly like the longer function name capability). While I'm not using this right now I'd like to learn more about it and consider it -- some of this may simply be some adjustments in our own methods. I'm looking forward to the improvements Jerry notes, learning more about this and maybe learning how to make use of this feature.

[JerryBrightbill]

Re: huge ALM file

Help,

Just did as Jerry suggested and everything on the code tab has disappeared, my named connections don't work and my sql reports are gone. How do I get them back?

You need the latest pre-release builds. The file system process in the last release build was flawed and did not work property for SQL reports, but did work for code on the code tab. When you set up a file system, just select the default path. What you need to find is where the <databaseName>.a5lib folder is located. It contains the file system files

If you set up a file system before the pre-release builds, converting the file system back to a library WITH THE BUILD YOU USED TO CREATE the file system will work for code, but not SQL reports. If you converted to a file system previously, you may have to restore from a backup. If you don't have a backup, The file system conversion process creates backups of the original files as .old_alb, .old_alm, old_alx. Backup the database folder and rename those files as .alb, .alm, .alx. You will be back to a library system.

If you created a file system with the latest pre-release build, you can still publish the database library for SQL reports in the publish process. The publish process converts the files system back to a temporary library and publishes the library, so the reports on the web work as they did before. The published folder will have an .alm file

[Lance Gurd]

Re: huge ALM file

I don't see an option to convert my file system backto a library on the code menu or the right click white space menu, looks like I will have to restore from my back up. Something I can't do until I go back to my office. There should have been a health warning on this.

[Lance Gurd]

Re: huge ALM file

I am using 2669 - 3921 and can't find anyway of restoring the library

[csda1]

Re: huge ALM file

Hi Lance,

I am using 2669 - 3921 and can't find anyway of restoring the library

If you don't have backups, there is a chance the ALM file can be recovered if you don't overwrite the disk drive with new data. 1st step is to remove the drive so it can't be written to. Contact me by email (click on my name in the signature below) for details. Unfortunately, recovery can be somewhat expensive, which is why backup are essential.

Also, if you have an AEX compiled library version, I can recover most of the objects from it's ALM that created it, in most cases.

[JerryBrightbill]

Re: huge ALM file

I am using 2669 - 3921 and can't find anyway of restoring the library

As stated above, the file system conversion process creates backups of the original files as .old_alb, .old_alm, old_alx. Backup the database folder and rename those files as .alb, .alm, .alx. You will be back to a library system.

[peteconway]

Re: huge ALM file

Hi Jerry, were changes made to how session variables work in this build? - I had all kinds of issues - had to retreat, it's a shame because there was a lot of good stuff in that build.

[kingcarol]

Re: huge ALM file

Hi Jerry, were changes made to how session variables work in this build?

Pete, I am interested in Jerry's answer, too. I have 3921 and have some other issues, too, but my session variables have suddenly become very unreliable. Unless they have a fix for this, I will also roll back because this is critical.

[JerryBrightbill]

Re: huge ALM file

Hi Jerry, were changes made to how session variables work in this build? - I had all kinds of issues - had to retreat, it's a shame because there was a lot of good stuff in that build.

As far as I know, there have been no changes to how session variables are handled. While the documentation for V11 states all session variables should be character springs, we haven't seen any issues with other datatypes.

We have not received any bug reports about session variables. If there is a specific problem we would like to hear about it.