Subject | Backup and restore problem |
---|---|
Author | wojciech_materna |
Post date | 2004-11-29T13:29:06Z |
Hello, (sorry, my English is.....but I'am working on it)
I create tables with computed fields. For example in one table I
declare field like :
SYMB varchar(2) computed by (substr(SYMB_FULL,1,2))
Everything works good till I must do backup and restore database.
Backup is OK, then in restore, I get error that function SUBSTR is
not existing - so table is not created, restore stops. For every
table in which I have computed fields which uses stored procedures
this error occurs.
So, to make backup and restore - first I must drop every calculated
field, next do backup, restore and finally create them back.
Am I doing something wrong? Can I do it in other way? It is not good
to use computed fields on this kind?
Thanks for every comment
Wojtek
I create tables with computed fields. For example in one table I
declare field like :
SYMB varchar(2) computed by (substr(SYMB_FULL,1,2))
Everything works good till I must do backup and restore database.
Backup is OK, then in restore, I get error that function SUBSTR is
not existing - so table is not created, restore stops. For every
table in which I have computed fields which uses stored procedures
this error occurs.
So, to make backup and restore - first I must drop every calculated
field, next do backup, restore and finally create them back.
Am I doing something wrong? Can I do it in other way? It is not good
to use computed fields on this kind?
Thanks for every comment
Wojtek