huge ALM file

[WokingJon]

Re: huge ALM file

Not sure how I managed it, but I converted all my scripts to a filesystem on Christmas day! As a result all password protection from my scripts was removed although the passwords were still in place. Tried many things to resolve this before finding this thread.

Reverted to original status by switching to the code tab then selecting script -> restore library from filesystem (or similar wording) from the main menu. For future reference you need all 3 old_al* files to enable the restore (luckily I had backed them up before one of my previous recovery efforts)

[TheSmitchell]

Re: huge ALM file

OMG. I did not know about this. ALM went from 75 MB down to a 750 KB. >_< doh!

[kingcarol]

Re: huge ALM file

Wow, thanks, Larry, for posting that about the compacting. I hadn't realized, either, what it would do. This is going to speed my report uploads immensely also! My 200 mb alm file went to 18 mb. Wonderful!!

[lgrupido]

Re: huge ALM file

Thanks for the tip.

Yes, they are all SQL based reports. I hadn't realized what compacting can do for you!

Uploading reports to the server is suddenly a much quicker process! I'm hoping it will also speed up my reports a little too. searching for a report in a 5mb file should be quicker than grabbing one from a 500 mb file.

[Al Buchholz]

Re: huge ALM file

My ALM file was at 600MB. I did a workspace compact and the size dropped to 5MB. The reports seem to be fine. Is that normal? How often do you recommend doing a compact?

I'm guessing that you are writing SQL based reports... They are stored there.

Each report modification and save creates another entry in the memo field for the workspace (aka database) structure file (.alm)

I tend to compact when I move to production, or have an issue that is otherwise alluding me.

[lgrupido]

Re: huge ALM file

My ALM file was at 600MB. I did a workspace compact and the size dropped to 5MB. The reports seem to be fine. Is that normal? How often do you recommend doing a compact?

[Lance Gurd]

Re: huge ALM file

Thanks Jerry, got it back by renaming the files. Wont be playing around with the file system again in a hurry.

[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.

[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.

[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.

[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.

[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.

[Lance Gurd]

Re: huge ALM file

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

[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.

[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