Hello,

We need to use the session ttaad4226m000 (Create Sequential Dump of Table) to export ALL data from our PRODUCTION/LIVE envt and Tables/Indexes for inventory purposes.

Can we run that session during the day while users are entering/processing data without slowing down the system OR damaging actual previous and current data.

Thank you for your prompt reply as this is VERY URGENT.

Kind regards,

Bertrand:confused:

It will for sure influence the performance since it has to write a lot of data to disk. Furthermore the export will not be consistent since data will be exported table wise, however the transactions that your users perform could affect tables that already have been exported and tables that still have to be exported.

Also, the dump process puts locks on tables, so for larger tables in particular, users can run into table locking errors if the session they are in is trying to use the table currently being dumped.

Vince

newer protingsets dont lock the table.. they make only a select about the rows... but the data you are exported could be corrupted.

right, you won't have a consistent data set.

a better idea would be to use oracle export, which can make a consistent backup.


Dave

if you want to use the dump as back up you can use oracle export. put if you want to create a demo copmany (and you must change the company number at the tables) it is better to use "baan tools" for the ex - import.

when you want to copy the whole BSE you can clone the database into a new instance...

but the simplest way is still to have a downtime at the weekend :-)

if you want to use the dump as back up you can use oracle export. put if you want to create a demo copmany (and you must change the company number at the tables) it is better to use "baan tools" for the ex - import.


it's not that tough to rename the tables and re-create the indexes when doing it with oracle exp/imp. but yes, it's certainly much easier with bdbpre/post.

but if you can't have downtime then exp is the way to go.

Dave