Skip Headers
Oracle® Fusion Middleware User's Guide for Oracle B2B
11g Release 1 (11.1.1.7)

Part Number E10229-13
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

15 Purging Data

This chapter describes how to use the Oracle B2B interface to purge design metadata and instance data.

The chapter contains the following topics:

See the following for alternate methods of purging:

Caution:

Archiving is required before purging data. Purging is an irreversible operation. Ensure that you first archive any important data.

15.1 Purging Design Metadata and Instance Data

Use the Oracle B2B interface to purge design metadata and instance data. Design metadata contains partner profile data, identifiers, document definitions, channels, and agreements. When you purge this data, predefined data that is part of the installation (the host trading partner name, protocols, and identification types, for example) is not purged. Instance data is created during runtime when messages are processed. Instance, or runtime, data contains the business messages and message-related data.

Specific instance data can be purged from the Business Message tab of the Reports link. See Section 18.1.2, "Purging Messages," for more information.

Purging does not remove artifacts that B2B creates in the Credential Store, such as passwords. See Oracle Fusion Middleware Security Guide for more information about the Credential Store.

With an instance message purge, you can optionally purge control number information. Control numbers are used in EDI (X12 and EDIFACT) and HL7 message standards. B2B keeps track of control numbers for inbound and outbound messages. For outbound messages, B2B generates the control numbers in a sequence from an internal control number table. Because purging instance data and control numbers resets the sequence (the control number table is reset), an outbound message after a purge may have the same control number as a message before the purge. If this is undesirable, do not purge control numbers.

Purging is useful for:

To purge design metadata or instance data:

  1. Click the Administration tab, and then the Purge tab.

  2. (Optional if purging instance data.) Select Purge Control Number to reset the sequence.

  3. Click Purge Design Metadata or Purge Instance Data, as shown in Figure 15-1.

    Figure 15-1 Purging Design Metadata or Instance Data

    Description of Figure 15-1 follows
    Description of "Figure 15-1 Purging Design Metadata or Instance Data"

    If you select Purge Design Metadata, then the message Do you want to delete all the design metadata from the repository permanently? appears.

    If you select Purge Instance Data, then the message Do you want to delete all the runtime data from the repository permanently? appears.

  4. Click Yes.

15.2 Purging Data Based on Database Partitions

Oracle B2B allows you to purge data from the B2B tables, based on the conditions provided by using the PURGE_INSTANCE_MSGS_AUDIT procedure. Typically, Oracle B2B uses the B2B_BUSINESS_MESSAGE table for performing database partition based purge.

The conditions that control the partition-based purge are:

Oracle B2B provides a command-line utility called b2bpurge that allows partition-based purge of data. See Section 20.3, "Purging Data" to know more about the utility.