Skip Headers

Oracle Files Administration Guide

Part Number A97358-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page

Go to previous page
Go to next page
View PDF

Migrating Data to Oracle Files

This appendix tells you how to migrate content and users from legacy systems to Oracle Files. Topics include:

Migrating Data from Other File Servers

Many Oracle Files administrators migrate data by scheduling downtime for the weekend, when file system usage is at a low point. The administrator can then perform the migration, shut down the old servers, and give the new server the same IP address, name, and other characteristics of the old system. When users arrive on Monday morning, they see the same file, FTP, or Web server they saw before. Some differences users may notice will be different paths to their files.

Server Consolidation Checklist

Consolidating users, folder hierarchy, content, and access privileges from other file server systems to Oracle Files involves moving:

Migrate the Users

The first task in moving to a new Oracle Files server is creating the user list. For each user you want to migrate to Oracle Files, you will need to create a new user using Oracle Internet Directory. For detailed information on this process, see the Oracle Internet Directory Administrator's Guide.

Recreate the Groups

Recreating the groups requires creating the groups, then adding the users to them.

Scripted Group Creation

If your management tools let you export group information to a file, you could then write a translation script to convert the groups into XML format and then load them into Oracle Files.

Migrate the Content

After creating users and groups, the next step is to move the files and folders into Oracle Files.

What actually gets moved? The files and folders themselves, as well as the basic metadata about them that any Copy command would support during a copy operation through FTP, Windows networking, or some other protocol. The filename, size, and date last modified are the key attributes that get copied along with the content.

However, there may be metadata that you cannot migrate from the old system to Oracle Files. For example, if your old file system or document repository stores owner information, this type of metadata may not be copied with the file. The owner in this case becomes the Oracle Files user copying the file, not the original owner in the old system.

Similarly, if applications running on the old system maintain metadata about files, this information will not be copied with the files. For example, a document management system may point to files in the old file system and add attributes to these files. Since this information is intrinsic to the document management system, not the file system, the extra metadata will not get copied along with the files.

Protocols for Copying Data

When copying the files, you'll use one of the network protocols:


If you have trouble logging into Oracle Files using your FTP client, make sure to enter the correct port, which is chosen during configuration of Oracle Files.