Kbase P129347: incremental df fails if lobs are in different areas
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/07/2008 |
|
Status: Verified
SYMPTOM(s):
incremental df fails if lobs are in different areas
incrdump.e already has a conflicting use. (99)
WARNING: The "<lob_file>" file AREA has changed. The incremental dump utility cannot be used to change database AREAS. Create AREAS with the "prostrct"utility and move tables with the "proutil tablemove" utility.
Warning: Blob Field "<field>" in database "clob" and Blob Field "<field>l" in database "area" are not in the same area.
no issue if clobs in the storage area in both databases
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.0x
OpenEdge 10.1A
OpenEdge 10.1B
CAUSE:
Bug# OE00136202
CAUSE:
the error .e file is opened for the error and never closed. Therefore when the tool goes to reopen the file, the error message 99 is displayed.
FIX:
Upgrade to OpenEdge 10.1C where the dump/_dmpincr.p has been changed.
Workaround: Modify the dump/_dmpincr.p in use as follows:
1. extract dump/_dmpincr.p from the prodict.pl
mkdir extract
cd extract
mkdir prodict
cd prodict
mkdir aud dump gate gui misc mss odb ora pro sec user
cd ..
prolib $DLC/src/prodict.pl -extract *
2. edit dump/_dmpincr.p
search for Warning: Blob Field
after the put stream line add OUPUT STREAM err-log CLOSE.
3. Start a progress editor.
Run: PROPATH="<pathtoextract>/extract:" + PROPATH.
4. Then perform the incremental dump as usual.
Should the modified code need to be compiled, it is necessar to first extract src/adecomm.pl as well. Then when connecting to a database two aliases need to be created before attempting to compile this file:
CREATE ALIAS DICTDB FOR DATABASE <databasename>.
CREATE ALIAS DICTDB2 FOR DATABASE <databasename>.