Hi,
Baan crashed and we dont have the recent object dump(that contains customized reports, menus etc). Is there anyway we could salvage the reports in this scenario? I need to salvage couple of reports that were created recently and there is no backup of it... With the current scenario is there any hope of retrieving those reports??

Anyone??

sk

Hi there,

afaik most information concerning report layouts etc. is kept in some tools tables of company 000 (ttadv330-ttadv335)- so you could perhaps find something there, assuming that you have at least a backup of your tables.
Report scripts however reside in $BSE/application/MODULE/rxxxxx - if you don't have a backup of these directories ... :-(

But what the heck happened? "Baan crashed" meaning .....?

good luck

Norbert

I agree with norwim. If you dont have regular backup of baan applicaiton directory, I am sorry there is no chance to recover your reports and menu.May be you can get your some scripts from Baan/tmp folder on your client. Baan editor opens your scripts on that folder. You may get something from this. But recover is not possible for your case.


G.Luck !

Hmmmm,

how can you agree with me and state something completely different?
I was pointing out that WITHOUT a backup of $BSE an existing backup of the company 000 tables however will contain information about the layout, the fields used etc. - only report scripts will be lost in this case. If there is no backup of $BSE/application, I wouldn't expect $BSE_TMP to have been saved.

At least we agreed on wishing sukesh good luck :-)

Norbert

I think that you mean what I pointed out . Suke said that there is no recently backup.And I mean on windows baan tmp may be some latest scripts workshops can be found !. Anyway , Norwim Needless to say needless things. Please reads all thread twice and think twice norwim.

Mr_Suleyman !

I thought the post in the other thread for Operating System & Databases would be noticeable as no one's replied to that.
So let me just quote what i wrote in that thread..

"On restarting our Baan server after it hung while creating sequential dump of the live company, the baan database was marked suspect. The drive where the mdf file is on has an excess of 19GB free while the drive where the backup file(7Gb) is being created has almost 85gb free and so it wasnt due to disk space problem..I rememeber once seeing a Suspect Database case on Baanboard but i couldnt find it anymore......"
....and so it goes..

Dbcc Checkdb gave out a lot of allocation and consistency errors on some of the tables..and the best way forward was to retrieve the sequential dump of a day earlier. Unfortunately this doesnt create a dump of the objects which we had changed recently...
The server is up and running. SQL Server is working. Operating system is fine...Just one database got corrupted, if i could safely assume so...

Now that you know the story...anything i could do to retrieve the reports?
I tried copying and pasting objects of a particular report starting oxxxx and uxxxx(both in objects folder) and rxxxx (in report folder) to a newly created report of the same name and package. However on compiling those objects were overwritten and so i dont think copying and pasting would work...

sk

Hi sukesh,

I read your posting about the crashed DB, but not being familiar with microsoft sql DB, I couldn't give any helpful tip.

You said that you recreated your data using sequential files one day old.
What about company 000? Sounds like you used an older version to rebuild this. If your modifaction of the reports weren't done exactly on the day missing, everything should be fine.

Report name, layout, fields etc. should be found in company 000 in the tables mentioned above.

What is the status of a "missing" report? Can you access it with "Maintain reports" or doesn't it show up there?

regards

Norbert

Ideally we would have taken the sequential dump, along with the toolsdata(ttcon61export) and object dump(ttiex1280m000). With this if we reinstall the application server, i could have my live co. up and running. The only minus point is that someone has to create and link database users with the Baan user. This time around we were caught offguard when the object dump that we had was older.

We restored the data on a different server running one of our sister companies data..Package combination of both the co were different and so the restoration went well with the only drawback that couple of reports were not reflecting the recent changes. The reports are accessible but they are old.. Some of the standard reports were customized to suit our needs and there has been some recent customization done...

I hope the picture is clear...

sk

OK, I think I understood now.
I only use object dumps to transport SW from one system to another, I don't think I ever saw this used for backup purposes. To get up running quickly after a crash you only need a backup of company 000 plus the $BSE plus the tables of your other companies. For the future I would definetly advise you to work on your backup strategy, ttcon61export and ttiex1280m000 are used to port systems.
I hope that you haven't erased the defective DB. The data you need is contained in the tools tables describing reports. If you can't start the DB so that you can create seq. dumps of these tables I am afraid your reports have gone.
Normaly there should be a way to at least create sequential dumps of single tables in ms sql .... the DB is marked suspect, not corrupt - what would be the reason of having different states if you can't access the whole DB anyway.

good luck

Norbert

Hi Norbert,
We havent done anything to the server where the Baan database crashed. We have sequential dump of the live company as well as 000.
Now could you please let me know the steps in a sequential order to bring back the live company by using the 000 sequential dump and live co dump.

Right now we are on SP 19 and using bck(AFS). The only doubt i have after reading your post is do we copy the entire BSE Folder back into the new installation as it is after we installed baan and restored both the 000 and live co dumps?

If yes, wont there be problems with certain services like Licensing, shared memory etc?

The database right now is in emergency mode and therefore i can access the tables using sql enterprise manager.

sk

Hi Sukesh,

please bear in mind that I hardly worked on windows servers.
But as your live server is offline now anyway, I would try to set this one up again. To achieve this, you only have to rebuild the ms sql database with the sequential dumps. $BSE should be ok anyway.
1) Make sure that you can go back to the present situation by backing up defective live system.
2) Use ms sql tools to drop all tables so that DB is not marked suspect or corrupt any longer.
3) use bdbpost to read in the sequential dump(s) of company 000
You should now be able to log in, all users, printers etc. and your beloved reports should be there - but of course no data in other companies.
4) when work is done on the other server and users have gone home, create seq. dump of live data (NOT company 000), read these into original system and tomorrow everything should be back to normal. (Run a create table for all companies to create empty tables where necessary)

hth

Norbert

Hi,
A suspect database doesnt show any tables inside it and hence wont allow you to drop any tables or any object inside it. Tried this in emergency mode and it rejected the drop command citing the database to be read-only and so no editing or deleting. We have decided to go ahead with a different approach to retrieve our reports and objects. The plan is..
1) Reinstall Baan from scratch
2) Apply service packs till the same level as the old installation before it crashed.
3) Restore sequential dump of 000
4) Overwrite the application folder in BSE with the old application folder...

Since the 000 company would have the last minute details of the objects, it would be complimented by the old application folder, enough to let us export the objects...That is the goal

Will this work?
sk

Hi Sukesh,

okay, so you can't use the DB any more.

Can you simply set up the DB? Absolutely no need to install Baan, let alone servicepacks ---- you have all this. What you lack ist the MS-SQL instance.
If you can reinstall this (with the correct name, users and passwords), then you don't need to bother about the rest. Reloading the 000 data will be sufficient then. (Plus the other companies then, of course)
If you are already considering to reinstall Baan, you have a manual or guideline for this .... have a look at it and only do the steps to install the DB.

Don't have the document here and it's a very long time since i installed a M$ system - but I hope you get my idea

thumbs up!

Norbert

What about the BSE? By just installing the DB and recovering the 000 and production company wont bring back the bse right?
Perhaps you are referring to the old installation? In my last post i was talking about a fresh installation(after formatting and setting up the OS)..

sk

Hi Sukesh,

sure, I was refering to my suggestion to repair the (now) idle live system, mainly because the $BSE is already there and you save a lot of time this way.

hth

Norbert

As of yesterday evening, the installation that had problems was reformatted and a fresh copy of Baan installed. At the time of writing this, the service packs 1-18 batch installer program is running after which SP 19 will be installed.
The next step i could decide whether i test with restoring the 000 company and overwriting the current application(//BSE/Application) folder with its older counterpart (in an effort to export the object dump)
or
Restore the production company data along with the import object(older copy) and toolsdata and do the necessary customization of the report all over again.

I am not sure whether the first step would work because i have never tried it even if theoretically it should work...If it doesnt work, then i would have to re-do the entire installation process all over again and then go with the second option...

What do you think??

sk

Shame really -

what I would do now was to backup the system when all service packs have been installed - and then copy $BSE and bdbpost company 000.
If this goes wrong for any reason (which I doubt), you only have to reload the backup in order to proceed the other way instead of installing yet again.

Still: thumbs up

Norbert

Time was really a factor and so i chose the second option without trying the first. If by any chance anything goes wrong after the installation or even during the next few weeks, i would have to face the users as wells as some of the peers wrath(been very understanding this week...dont want to push it)...so took the tried and tested route...

Within today and by tomorrow afternoon i would have to bring up the server to its previous stage minus the data(production co data). This will inlude the creation of users both on the server and in the database and then linking them, importing of the objects and tools data and some other baan related checks.

Thanks for all the input. Later on i would really like to try the procedure you suggested. If it works, it would really save a lot of time...

sk

Hi Sukesh,

since the crash happened more than a week ago, I can understand that you don't want to risk any more delay. Wishing you all the luck that your box will be up and good soon.
As I won't be in office for the next ten days, perhaps you may want to drop me a mail so we can keep in touch anyway : norbert.wimmerATono.de

thumbs up!

Norbert