Oracle's DMP file modified version number

In summary, it is toss.

1, 11G of Oracle Backup (originally did not know), to the 10G of Oracle Recovery, recovery when the tip is incorrect, so the long revision of the version number began.

2, because the backup is very big, start with UE and so on to try, long wait after the card dead + disk space is insufficient.

3, then began to find the file segmentation tool, found the tool. The result is too big, finally split up, the merger is always in half when the error. (All of a sudden a day has passed)

4, finally ready to own hands and clothing.

That's the way it's written.

public static void Dofile (String fileName) {Try{randomaccessfile RAF = new Randomaccessfile (fileName, "RW"); byte b[] = new B YTE[50];  Raf.read (b); for (int i=0;i<b.length;i++) {System.out.print (b[i]+ ",");} B[12] = 48;//commend by Danielinbiti, this is modified to 10g:v10.02.01. If you can cut out a few bytes of the head before the change to confirm, is not to modify the 12th, 18 bytes b[18] = 49;raf.seek (0); Raf.write (b); System.out.println ("");} catch (Exception ex) {}}

Finish me depressed bad ... If I had known, I would have written it myself. A few lines of code modification + verification has not been tossing more than half an hour. Hope Yimeimei have the same situation can spend less energy.

Oracle's DMP file modified version number