• Article Type: General
• Product: Aleph
• Product Version: 20

Description:
We are upgrading from version 17 to version 20. Various documents (such as the "Guidelines for Aleph 18.01 to 20.x Upgrade" and Jerry Specht's "Upgrading to Aleph Version 20 - Upgrade Express.ACTUAL RUN.doc") show a dpdir directory being produced. For example:

30- aleph112-a18(1) >>cd files/dpdir
31- aleph112-a18(1) >>ls -lrt
32- -rwxrwxrwx 1 oracle dba 61440 Apr 26 16:17 law0102.dmp*
33- -rwxrwxrwx 1 oracle dba 105893888 Apr 26 16:17 law0101.dmp*
34- -rwxrwxrwx 1 oracle dba 4820 Apr 26 16:17 explaw01.log

The export seemed to go OK on our server, but, though our ./upgrade_express_1901_2001/data/a17_7/abc01/files directory has an abc01.export.gz_aa file, this file is *not* in "dpdir" subdirectory (as shown in the example). Why is this?

Resolution:
The "dp" in "dpdir" stands for "data pump" . Since you are coming from version 17 and did not (and *could* not) use the data pump (-- but instead used the regular Aleph export utility --) you will not have any "dpdir" directory.

The important thing is that a proper ./upgrade_express_1901_2001/data/a17_7.tar.gz was produced -- which I see that it was.

• Article last edited: 10/8/2013