Data Loss Prevention

We are attempting to get a clean installof Vontu 11 with Oracle 11g in a Windows 64-bit environment.  The existing installation has been with us for years and we successfully migrated it recently from Vontu 9 to Symantec DLP 11 in a Windows 32-bit environment. This included the character set conversion.

In setting up Oracle 11g in a 64-bit environment with our current incident database we are getting some error messages regarding character set issues which both our Oracle consultant and Symantec tech support have said are safe to ignore.

Nonetheless, we don't want anything to bite us in a later update, so we're shooting for a clean upgrade. 

With that in mind, is is possible to perform a clean install of Vontu 11 and Oracle 11g in a Windows 64-bit environment and then import our incident database from the 32-bit Windows environment?  Has anyone done this successfully?  Was it a clean upgrade?

Maybe you can try to use export DB and import DB. But, export and import of the Symantec DLP database using Oracle utilities exp, imp, expdp, or impdp, is not supported by Symantec DLP support.  They should only be used by Symantec DLP Professional Services or an experienced Oracle DBA.

We are setting up the 64-bit installation now.  Will post if the export/import is successful. We do have an Oracle consultant engaged.

This worked for us. We used the Data Pump export/import utilities in order to get a clean database when we moved to a 64 bit platform

Some history:

• We've been using DLP (Vontu) since version 4 and Oracle 9i.
• We converted the database from our default Windows character set (WE8MSWIN1252) to the required (al32utf8) set also using the Oracle data pump export/import.
• Our last upgrade to Oracle 11g in the 32bit world had a number of memory issues that left 90+ invalid objects in the database.
• We created a new database template from the current prod db.
• Then exported and imported all of the data into the new clean database and everything seems to be working fine, just the usual 6 or 7 invalid objects.

Some details:

Our database export was 218GB, the export off the old system took just over 7 hours to an external esata drive (via pci card slot).

That same data imported on the new server took a little over and an hour (via pcie slot). Gotta love new hardware and faster drives.

Here's wishing you good luck with your upgrade/move.

Removed double post.