Limits the number of records to be deleted this is a nonimportation-specific feature True (default when any truncate or drop operation is performed) There are two variations, CONSOLE_ * that uses the dbms_output mode of logging (applicable only when the procedure is invoked directly through a client) and the other modes that log to a file in a SOA_PURGE_DIR directory.Ĭontrols whether to completely refresh the b2b_system materialized view. In this mode, no change is made to the database. STATEMENT: Statement mode does not clean up the tables, but only creates a drop statement and writes the statement to a file in the SOA_PURGE_DIR directory. TRUNCATE: Cleans up the partition by truncating it rather than deleting it. Note: This parameter is effective only when the partitioned flag is set to true.ĭROP: Indicates that the clean up mechanism is to drop the partition (Default). In case of absence of partitions, or non-date parameters are provided, this parameter is ineffective. Specifies the mode of cleaning for a partition that is identified for cleanup. Based on the value of this parameter, Oracle B2B allows you to purge data normally or based on database partitions. Indicates if the database is partitioned. Specifies the number of records after which the database commit takes place The sender ID_VALUE, the value associated with the identifier type.
STERLING INTEGRATOR DOCUMENT INFO SERVICE ZIP HOW TO
The sender ID_TYPE, or identifier type, which uniquely identifies a trading partner and defines how to exchange documents. This option not available when data is deleted for a specific date range.Īrchiving will only occur is this option is set to false.ĭeletes all messages, which created on or after this date.ĭeletes all messages, which created on or before this date. When set to true, all the runtime data is truncated from B2B tables. If msgstate is present, then start and end must be used.ĭeletes control numbers. (see Note below)ĭeletes messages with the specified message state. Specifies purging design-time or runtime data. Table 21-2 Options for b2bpurge Utility Option
To restrict the command-line tools from anonymous use, provide the following information in the jndi.properties file: Most of the command-line tools cannot be run without providing the JNDI credentials. In summary, if you are executing the B2B command utility and a user session is opened in the UI simultaneously, then it is advisable for the user to log out of the B2B UI and log back in again to see the candidate changes done by the command utility.Ĥ. Therefore, it is advisable to always re-login into the B2B Console after using command-line operations.ģ. The B2B Console caches some metadata and any command-line action which may have updated the metadata could lead to invalid cached data.
After running any command-line tool, you should re-log into the B2B Console. No security or permission checks are performed to prevent the logged-in user from purging, importing, or exporting data.Ģ. Command-line tools are for administrator use only.
0 kommentar(er)
