Hello Everyone,

I had a quick question that I was hoping someone here might be able to help me on.

I'm investigating the idea of splitting our archive company (197) off to a separate Oracle server box. A question came up when I was tossing this idea around as to the backups of these new tablespaces.

Can I set 197 tablespace to read-only and have baan work? I don't know if Baan does any internal/housekeeping in the company tables and if read-only will crash it.

I do know that under Oracle, if you set a tablespace read-only you need only back that tablespace up once...

Any ideas?

Cheers,
FT

One thing you have to keep in mind is that if you ever want to run 'reconfigure DD' on the PVRC's to which your archive company is attached to, you will have to put your tablespace in read-write again. Other than that I think Baan is quite happy with it.

The requirement that you only have to back it up once can also be potentially dangerous of course :)

We have set our archive company to read-only at the tablespace as you've mentioned.

Only issue which had to be worked around was that if users print via a Baan session rows are written to company 000 table used by Maintain Device Queue--so these would need to still be writeable.

Anyway, this is all from memory--let me know if you need more specifics and I can look-up and double-check if need be.

Regards,
Brendan

Hi Patvdv

why do you think "The requirement that you only have to back it up once can also be potentially dangerous of course"

I have found while reconfiguring the archive data, baan drops the table and not able to create new to the db.
If we keep it online and not backup for 6 months what problems you think can happen? What i think if we reconfigure the restored db with current PVRC then it should make the old data good for use. If i am wrong could explain why?

thanks in advance.
Eric

Eric,

The potential 'danger' I was referring to is linked to the usual retention periods people use to rotate their backups mediums. If you let the backup medium containing the single one copy of your read-only tablespace expire and overwrite then I think it's easy to imagine what will happen if your tablespace gets lost in the database itself. Likewise many backups mediums can get worn out, damaged etc.

thanks patvdv

JIC anyone is curious to know how all this is going...

1. Created a Linux server (RH 6.2 512MB 4x9GB)
2. Installed Oracle 8.1.7
3. Created the tablespaces for the data and indexes of arch co
4. Created r_baan role, user accounts
5. exp'ed all the data associated with our arch co
6. imp'ed the data into newly created instance
7. Manually modified tabledef6.1 :eek: (I know, I know) to point all arch co tables to new SID
8. altered 'live' arch co tablespaces (data & index) offline

Seems to work okay! :cool: