Skip Headers
JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide
Release 8.98 Update 4

Part Number E14718-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

10 Backing Up JD Edwards EnterpriseOne Tables

This chapter contains the following topics:

10.1 Understanding Backup Requirements for Servers

A well-planned backup strategy is essential to protect the enterprise information assets. Rigorously following the backup strategy will provide insurance against data lost by acts of nature, hardware or software failure, or human error. The backup strategy must balance the level of protection you need against the physical constraints of the system, such as information storage capacity.

We recommend that the backup strategy include these:

When you perform a backup on a server, you can back up either the entire server or only the changed objects and data. You do not need to perform a complete backup of the server nightly. Only directories that change daily require daily backups.

Note:

You should outline and implement the backup strategy before you begin the Prototype phase of implementation.

10.1.1 Backing Up a Deployment Server

JD Edwards EnterpriseOne on the deployment server includes these items:

  • JD Edwards EnterpriseOne directory (all subdirectories and contents).

  • jde.ini file on c:\winnt.

  • Services file on c:\winnt\system32\drivers\etc.

  • Registry export file.

  • JD Edwards EnterpriseOne files in the root directory (c:\):

  • jdeapp.ddp

  • jdeapp.xdp

  • jdeauth.dda

  • jdeauth.xda

  • jdemod.ddm

  • jdemod.xdm

  • jdesec.dds

  • jdesec.xds

  • jdecode.ddm

  • jdecode.xdm

If you modify objects, build new packages, or update the Access database delivered during a workstation installation, create backups of the PD900, DV900, and PY900 directories. If you modify help files, create a backup of the HELPS directory. If the media objects reside on the deployment server, create a backup of the MEDIA OBJ directory.

If important data, such as system data, resides on the deployment server, create nightly backups of the JD Edwards EnterpriseOne data sources (Oracle or SQL Server). For example, if the central objects or Object Management Workbench resides on the deployment server, create a nightly backup.

10.1.2 Backing Up an Enterprise Server

JD Edwards EnterpriseOne on the enterprise server runs on the IBM i, UNIX, or Windows operating systems. You back up key libraries on the IBM i and key files on the UNIX and Windows operating systems.

IBM i

These JD Edwards EnterpriseOne IBM i libraries should be backed up:

Note:

Shut down the database before you create any backups.
  • All JD Edwards EnterpriseOne system libraries.

    • JDEOW

    • SYS900

    • E900SYS

    • SVM900

    • JD Edwards EnterpriseOne data dictionary library: DD900.

    • JD Edwards EnterpriseOne Object Management Workbench library: OL900.

  • All JD Edwards EnterpriseOne production libraries (This example is for pristine and production):

    • PD900

    • PY900

    • PRODDTA

    • PRSTDTA

  • All JD Edwards EnterpriseOne business data libraries:

    • PRODDTA

    • CRPDTA

    • PRSTDTA

    • TESTDTA

  • All JD Edwards EnterpriseOne control libraries:

    • PRODCTL

    • CRPCTL

    • TESTCTL

    • PRSTCTL

  • All JD Edwards EnterpriseOne versions libraries:

    • PD900DNT

    • PY900DNT

    • PS900DNT

    • DV900DNT

  • IFS (Integrated File System) libraries:

    • PD900

    • PY900

    • PS900

    • TS900

    • DV900

  • IBM libraries that require backups:

    • OCPA

    • OGPL

    • Central objects on the deployment server in Oracle or Microsoft SQL Server database.

UNIX

On a JD Edwards EnterpriseOne UNIX system, backup these database files:

Note:

Shut down the database before you create any backups using Backup Manager. If you export or import using Data Manager, you do not need to shut down the database.
  • System files

    Create backups of all host files under the JDEdwards/E900 directory. For example, /u03/JDEdwards/E900/*.

  • Database files

    Create backups of all data files that reside in the JD Edwards EnterpriseOne tablespaces.

    Use the Oracle Data Manager Tool on the deployment server to make a .dmp file of the desired database, and then back up the .dmp file on tape or hard disk.

Windows

On a JD Edwards EnterpriseOne Windows system, back up these database files:

Note:

Shut down the database before you create any backups.
  • System files.

    JDEdwards\ddp\E900 directory.

  • Oracle database files.

    Create backup files for all data files that reside in the JD Edwards EnterpriseOne tablespaces

    Use the Oracle Data Manager Tool on the deployment server to make a .dmp file of the desired database, and then back up the .dmp file on tape or hard disk.

  • Microsoft SQL Server database files.

    Create backup files for all tables that reside in the JD Edwards EnterpriseOne databases.

    Use the SQL Server Database/Object Transfer tool on the enterprise server to copy the desired tables or database (for example, PSFT900) to a backup database.

    Note:

    We recommend that you use the backup tool provided by the RDBMS vendor.

10.1.3 JD Edwards EnterpriseOne Tables and Object Owner IDs

These tables list JD Edwards EnterpriseOne tables by type and with the associated object owner IDs.

Note:

If any of the control table merges fail or if the specification merge fails, you might need to restore the tables to a pre-merge condition and run the merge again. Follow the restore instructions for the database.

System Tables

The Object Owner for System tables is sys900.

  • F00053

  • F000531

  • F000532

  • F0092

  • F00921

  • F00924

  • F0093

  • F0094

  • F00941

  • F00942

  • F00945

  • F00946

  • F00948

  • F00950

  • F00960

  • F99001

  • F986101

  • F98611

  • F986115

  • F986116

  • F98613

  • F986150

  • F986151

  • F986152

  • F98616

  • F986161

  • F986162

  • F986163

  • F986164

  • F986165

  • F98701

  • F98800D

  • F98900D

  • F9882

  • F98825

  • F9883

  • F9885

  • F9886

  • F9887

  • F9888

  • F98881

  • F98882

  • F98885

  • F98887

  • F9889

  • F98891

  • F98892

  • F98980

  • F98CONST

  • F98DRENV

  • F98DRLOG

  • F98DRPCN

  • F98DRPUB

  • F98DRSUB

  • F98EVDTL

  • F98EVHDR

  • F98MOQUE

  • F98OWSEC

  • F98TMPL

  • F98VAR

Object Management Workbench (OMW) Tables

The Object Owner for OMW tables is obj900.

  • F00165

  • F9860

  • F9861

  • F9862

  • F9863

  • F9865

Data Dictionary Tables

The Object Owner for the Data Dictionary tables is dd900.

  • F00165

  • F9200

  • F9202

  • F9203

  • F9207

  • F9210

  • F9211

Server Map Tables

The Object Owner for Server Map tables is svm900.

  • F986101

  • F98611

  • F986110

  • F986111

  • F986113

  • F98DRPCN

  • F98DRLOG

Control Tables

The Object Owners for the Control Tables are:

  • Control Tables - PROD: prodctl

  • Control Tables - CRP: crpctl

  • Control Tables - TEST: testctl

  • Control Tables - PS900: prstctl

The Control Tables are listed:

  • F0002

  • F00021

  • F0004

  • F0004D

  • F0005

  • F0005D

  • F0082

  • F00821

  • F00825

  • F00826

  • F0083

  • F0084

Versions Tables

The Object Owners of the Versions tables are:

  • Versions - PD900: PD900

  • Versions - PY900: PY900

  • Versions - DV900: DV900

  • Versions - PS900: PS900

The Versions tables are listed:

  • F983051

  • F98306

Central Objects

The Object Owners of the Central Objects tables are:

  • Central Objects - PD900: pd900

  • Central Objects - PY900: py900

  • Central Objects - DV900: dv900

  • Central Objects - PS900: PS900

The Central Objects tables are listed:

  • F980011

  • F980021

  • F983051

  • F98306

  • F98710

  • F98711

  • F98712

  • F98713

  • F98720

  • F98740

  • F98741

  • F98743

  • F98745

  • F98750

  • F98751

  • F98752

  • F98753

  • F98760

  • F98761

  • F98762

  • F98950

Business Data

The Object Owners of the Business Data tables are:

  • Business Data - PROD: proddta

  • Business Data - CRP: crpdta

  • Business Data - TEST: testdta

  • Business Data - PS900: prstdta

10.2 Backing Up JD Edwards EnterpriseOne Tables on Servers

This section discusses how to:

10.2.1 Prerequisites

Before you complete the tasks in this section:

  • If you are using SQL Server or Oracle, verify that you have enough disk space for the backup copy before you begin the backup.

  • If you are using SQL Server, verify that the Select Into/Bulk Copy option on the Options form is turned on for the database into which you will transfer objects. Double-click the database in the tree structure to access the Options form.

10.2.2 Creating a Backup for IBM i

To create a backup for IBM i:

  1. On a tape drive, back up these libraries, depending on which path codes you have installed:

    Library name Description
    SYS900 System library
    SVM900 Server Map
    OL900 Object Librarian
    DD900 Data Dictionary
    COPY900 Central Objects - Prototype
    COPS900 Central Objects - PS900
    COPD900 Central Objects - PROD
    CODV900 Central Objects - DEV
    PRODDTA Production Business Data
    PRODCTL Production Control Tables
    CRPDTA Prototype Business Data
    CRPCTL Prototype Control Tables
    TESTDTA Test Business Data
    TESTCTL Test Control Tables
    PRSTDTA Pristine Business Data
    PRSTCTL Pristine Control Tables
    PY900DNT Versions for CRP
    PD900DNT Versions for PROD
    PS900DNT Versions for PRST
    DV900DNT Versions for DEV
    E900SYS Server system library
    JDEOW JD Edwards Installation
    PY900 Server modules - Prototype
    PY900FA Package Library - Prototype
    PS900 Server modules - PS900
    PS900FA Package Library - PS900
    PD900 Server modules - PROD
    PD900FA Package Library - PROD
    DV900 Server modules - DEV
    DV900FA Package Library - DEV

  2. Back up these IFS structure with the subdirectories:

    Library name Description
    PSFT900 Logging directory
    E900SYS Kernel spec and XML
    PY900 Spec files for Prototype
    PS900 Spec files for PSFT
    PD900 Spec files for PROD
    DV900 Spec files for DEV
    JD Edwards Contains the spec files for each path code.

    \JDEdwards\PACKAGES\PY900FA\SPEC\*.*

    \JDEdwards\PACKAGES\PS900FA\SPEC\*.*

    \JDEdwards\PACKAGES\PD900FA\SPEC\*.*

    \JDEdwards\PACKAGES\DV900FA\SPEC\*.*


10.2.3 Creating a Backup for Oracle on UNIX or Windows

To create a backup for Oracle on UNIX or Windows:

  1. From the Oracle Enterprise Manager Tool, open Data Manager and from the Data menu, select Export.

  2. Type the name for the export utility .dmp file.

    Click the Browse button to select the directory where the .dmp file will reside.

  3. Click Next.

  4. On the Object Selection form, select the objects you want to back up, and then click Next.

    Note:

    Objects selected in the tree on the Data Manager form appear in the Selected Objects form. You can move objects between forms using the arrow buttons or by dragging and dropping.

    To export objects, expand the Available Objects tree and select the item to export. Use the arrows to move objects to and from the Selected Objects form.

  5. On the Tuning form, select generate a log file, if needed.

  6. Click Next.

    Note:

    Select the Generate Log File option and enter a log file name or use Browse to select a log file.
  7. On the Advanced Options form, take the default values or select the desired options, and click Next.

  8. On the Summary form, verify that all of the chosen objects and options are correct.

  9. Click Finish to begin exporting objects.

    A message window opens that displays information about the progress of the export process.

    When the export process is completed, you will receive these message: "Export terminated successfully without warnings."

  10. If errors or warnings exist, check the log file to review the export process.

10.2.4 Creating a Backup for SQL Server

To create a backup for SQL Server:

  1. From SQL Enterprise Manager, select Database/Object Transfer from the Tools menu.

  2. On the Database/Object Transfer form, select a destination server and database on which to create backup copies of the tables.

    Note:

    The source server and the destination server can be the same, but the database must be different.
  3. Keep all default settings and then click the Start Transfer button.

    The Database/Object Transfer tool moves the objects.

  4. Perform either of these tasks to verify whether the backup was successful:

    • When the process completes the transfer, click the View Logs button to review the transfer process.

    • Run a SELECT statement to verify that the backup tables transferred to the new database with data.

10.2.5 Restoring a Backup File for Oracle on UNIX or Windows

To restore a backup file for Oracle on UNIX or Windows:

  1. From the Oracle Enterprise Manager Tool, open Data Manager and from the Data menu, select Import.

  2. Type the name of the import utility .dmp file.

  3. Click Next.

  4. On the Object Selection form, select the objects you want to restore and click Next.

    The Importable Objects tree contains the objects that are importable in the file you specified. To move the object to the Selected Objects tree, select an object in the tree and click the down arrow.

    Note:

    When the .dmp file is on a remote machine, Data Manager uses the Console job and event system to retrieve the file before displaying the data through the Import Wizard. The Remote Import page of the Import Wizard has a status line at the top of the page that displays the progress of data retrieval. The Oracle Enterprise Manager Console must be running.

    Three conditions can be displayed: Job Submitted, Job Started, and Job Completed.

    Note:

    Data retrieval must complete successfully before beginning the import operation.

    The Selected Objects/Available Objects tree contains the objects to be imported. To remove an object from the list, select the object and use the up arrow or drag and drop.

  5. Click Next.

  6. On the Associated Objects form, accept the defaults and click Next.

  7. On the Tuning form, you can generate a log file, if needed.

  8. Click Next.

    Note:

    Select the Generate Log File options and enter a log file name or use Browse to select a log file.
  9. On the Advanced Options form, select the Increment Type. If you followed the instructions to create a backup, select None for Increment Type and click Next.

  10. On the Summary form, verify that all selected objects and options are correct.

    Note:

    You must drop the existing objects in the database that you want to restore or the import process will fail.
  11. Click Finish to begin importing objects.

  12. When the import process is completed, you will receive these message: "Process terminated successfully with no warnings."

    If errors or warnings exist, check the log file to review the export process.

  13. Perform a SELECT statement to verify that the backup tables are populated with data.

10.2.6 Restoring a Backup File for IBM i

To restore a backup file for IBM i:

Restore the libraries and IFS directories that you backed up from tape.

10.2.7 Restoring a Backup File for SQL Server

To restore a backup file for SQL Server:

  1. Verify that the Choose Into/Bulk Copy option on the Options form is turned on for the database into which you will transfer objects.

    Double-click the database in the tree structure to access the Options form.

  2. From SQL Enterprise Manager, select Database/Object Transfer from the Tools menu.

  3. On the Database/Object Transfer form, select a destination server and database from which to transfer backup copies of the tables.

    Note:

    The source server and the destination server can be the same, but the database must be different.
  4. Deselect the Transfer All Objects option, but keep all of the other default settings.

  5. Click the Choose Objects button, select the objects that you want to transfer, and then click OK to return to the Database/Object Transfer form.

  6. Click the Start Transfer button.

    The Database/Object Transfer tool moves the objects.

  7. Perform either of these to verify whether the backup was successful:

    • When the process completes the transfer, click the View Logs button to review the transfer process.

    • Run a SELECT statement to verify that the backup tables transferred to the new database with data.

10.2.8 Restoring a Backup File for SQL Server on Windows

To restore a backup file for SQL Server on Windows:

  1. Verify that the Select Into/Bulk Copy option on the Options form is turned on for the database into which you will transfer objects.

    Double-click the database in the SQL Enterprise Manager tree structure to access the Options form.

  2. Generate scripts for the tables you want to restore and then drop the tables.

  3. Use SQL to recreate the scripts for the tables.

  4. From the command line, type this command:

    bcp [[database_name.]owner.] table_name(in|out) datafile /n /u /p /s
    
  5. Perform a SELECT statement to verify that data populates the backup tables.