Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

New DB_Maint_Job Table (in FI_Data_2)

  • Last UpdatedDec 18, 2018
  • 2 minute read

Defines the Archive/Purge/Restore jobs that can be run and the current run status

Field

Datatype

PK

Nulls?

Description

db_maint_job_id

string40

N

N

Identifies the maintenance job

description

string80

N

Y

Description of the job

actiontype

int32

N

N

1 = archive (default)

2 = purge

3 = restore

4 = archive_purge

event_type_details

notes

N

Y

Comma-separated list of the main historical tables on which the job will operate (e.g., tables to archive, tables to purge)

date_range_type

int32

N

Y

1 = absolute (default)

2 = relative

start_date_local

tdatetime

N

Y

Local start time of an absolute date range filter; null if the job uses a relative time filter

start_date_utc

tdatetime

N

Y

UTC start time of an absolute date range filter; null if the job uses a relative time filter

end_date_local

tdatetime

N

Y

Local end time of an absolute date range filter; null if the job uses a relative time filter

end_date_utc

tdatetime

N

Y

UTC end time of an absolute date range filter; null if the job uses a relative time filter

relative_offset

int32

N

Y

The numeric offset used for time filtering (e.g., purge anything more than 5 days in the past); null if the job uses an absolute time filter

relative_offset_units

int32

N

Y

The units of the relative_offset value; null if the job uses an absolute time filter.

1 = days (default)

2 = months

3 = years

data_set_path

string1000

N

Y

The path and name of the.meszip file to restore; null if the actiontype is not 3 (Restore)

conflict_option

int32

N

Y

Action to take is a conflict is detected:

0 = none (continue on error)

1 = abort

last_exec_date_local

tdatetime

N

Y

Local time the job last started

last_exec_date_utc

tdatetime

N

Y

UTC time the job last started

last_exec_userid

string40

N

Y

Last user who executed the job

cur_event_count

int32

N

Y

Number of events the job has processed so far (usually records except for purge)

cur_error_count

int32

N

Y

Number of errors that occurred so far while the job was running

cur_status

int32

N

Y

Current status of the job:

0 = none (default)

1 = running

2 = completed

3 = aborted by user

4 = aborted by system

5 = aborting

last_edit_comment

string254

N

Y

Why this record was changed

last_edit_by

string40

N

Y

Who last changed this record

last_edit_at

tdatetime

N

Y

When this record was last changed

row_id

ID 1

Y

N

Unique row identifier

TitleResults for “How to create a CRG?”Also Available in