SQL Developer export forgot to check to include semicolons in DDL

Question

Hi,
I used the SQL Developers Export-function (select tables and right click on them, then select export) to backup tables.
However, I forgot to set the 'Abschlusszeichen' (sorry for the german). That apparently means my create table statements are not finished by an ';', and they sinmply don't execute using the @script.sql method, or the sql developers import-function.
One sql-file is 2 GB in size, so I currently have no idea how to edit it and add the semicolons manually. Is there any hope to rescue the data?
I'm running sql developer 3.2.20.09, oracle Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production as well as Windows 8.1
For clarification, this is how the create table part looks:
--  Datei erstellt -Montag-September-30-2013  
--  DDL for Table ZZ_BEN_0
  CREATE TABLE "PIERUSCHM"."ZZ_BEN_0"
   (    "BENUTZER_ID" NVARCHAR2(30),
    "NAME" NVARCHAR2(30),
    "GUELT_VON" NVARCHAR2(30),
    "GUELT_BIS" NVARCHAR2(30),
    "IST_KORREKTUR" NVARCHAR2(30),
    "IST_HALBTAGSKRAFT" NVARCHAR2(30),
    "LADE_DAT" DATE
--  DDL for Table ZZ_BEN_1
  CREATE TABLE "PIERUSCHM"."ZZ_BEN_1"
   (    "BENUTZER_ID" NVARCHAR2(30),
    "NAME" NVARCHAR2(30),
    "GUELT_VON" NVARCHAR2(30),
    "GUELT_BIS" NVARCHAR2(30),
    "IST_KORREKTUR" NVARCHAR2(30),
    "IST_HALBTAGSKRAFT" NVARCHAR2(30),
    "LADE_DAT" DATE
--  DDL for Table ZZ_BEN_10

Answer 1

Also i'd like to add that the file begins with table definitions but then contains the actual (and randomly generated) data as well.
You still need to have the file regenerated or you should expect to have problems with ANY method you use to try to automatically 'fix' the problem.
1. No experienced developer that I have worked with would EVER try to execute such a monolithic script because there is virtually NO chance that a 2 GB script will EVER run successfully without an error of some sort. Objects have to be created in the proper order when dependencies exist between them. For example, you can't create an index if the table hasn't been created yet. There can even be circular references that will prevent all objects from being VALID even if they are created.
2. There is virtually NO chance that ANY method you use will put terminators in EXACTLY the right place without causing a problem of some sort.
3. When there is an error the script may continue to try to executed and that usually causes further errors. It also creates garbage objects that are not valid but will keep the script from working correctly the next time since the objects will already exist.
You need to create a SET of scripts that are of manageable size so that you can control the process of executing them in the proper order.
If you don't take the time to do that, up front, you are going to wasted a tremendous amount of time when the script fails trying to cut and paste the pieces you need out of that 'master' script.
There are NO SHORTCUTS: take the time to do it right the first time.