Kbase 18315: RTB Schema update list build error:'record not on file(138)'
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
09/10/1998 |
|
RTB Schema update list build error:'record not on file(138)'
If you load a partner site deployment into its read-only workspace,
and you don't update the schema of the workspace database in the
read-only workspace, then you load the next partner site deployment,
the schema update will fail since information that would have been
created from the first update does not exist.
You may see the following errors on a couple tables during the schema
update list build:
bsledef-cur record not on file (138)
After the list is built, you may get the following Blderr on a number
of other tables:
ERROR!rtb_mksh: in index sequence section
Error!rtb_mksh: rtb_flddef missing for object <field-name>
Work-arounds after getting yourself into this unfortunate situation:
1. Delete the read-only workspace and get a new "full (not
incremental)" partner site deployment from the other site.
Since the read-only workspace only contains information sent from the
other site, you do not lose any history or work by deleting this
workspace (the full partner site deployment that you will re-load has
everything). This will also not affect imports into the other
workspaces since imports are based on object version numbers.
2. Restore from back-up to before loading the second partner site
deployment. Update the schema of the workspace database, then load
the second deployment.
10/9/98 FSI - GW