abainstallhistory (ap_inh)

Name

abainstallhistory

Code

ap_inh

Creation Date

13 december 2000 13:53:05

Modification Date

24 september 2012 09:43:42

Comment

History of builds and update/patch scripts.


Table description

This table provides a history of all builds, update scripts and patches that have been executed in the database. After a successful run for a subsystem there are two entires: one START and one STOP (or a REMOVE). Thus, if there is a START without a STOP, this indicates an installation in progress - or one that never was completed.

 

Note that executions of ABASQL are not logged in this table.

 

The purpose of this table is to provide auditing information for the DBA. AbaPerls itself does currently not use the information in this table.


Column list


Column


Domain

Data
Type

NOT
NULL

F
K


Comment

inhid

 

int

X

 

Synthetic primary key.

script

ap_scriptname

varchar(64)

X

 

Name of script/tool.

action

 

char(6)

X

 

START, STOP or REMOVE.

actiontime

 

datetime

X

 

Time when the row was written.

subsystem

ap_subsystem

varchar(30)

 

 

The affected subsystem.

ss_label

ap_sslabel

varchar(15)

 

 

 

vc_repository

ap_path

nvarchar(250)

 

X

 

vc_path

ap_path

nvarchar(250)

 

 

 

username

ap_ntname

nvarchar(40)

X

 

NT user that ran the installation.

hostname

ap_ntname

nvarchar(40)

X

 

From which host the user ran the installation.

domain

ap_ntname

nvarchar(40)

X

 

On which domain the user was logged into.


Table constraints

ckt_ap_inh_vccols (vc_repository IS NULL AND vc_path IS NULL OR
vc_repository IS NOT NULL AND vc_path IS NOT NULL)


Keys

Name

Columns

Options

PK

pk_ap_inh

inhid clustered

X


script

Name of the script/tool that installed something in the database. This is DBBUILD in the case you add a subsystem, else it is an update/patch script generated by DBUPDGEN. When you run DBBUILD with -rebuild, the value in this column is "DBUILD -rebuild".


action

Rules and defaults etc.

List of Values

START    
STOP    
REMOVE   


The action for the entry, usually START or STOP. REMOVE is added in place of STOP by an update script that completely removes a subsystem.


subsystem

The affected subsystem. This column is normally non-NULL, but is in NULL if the ABAPERLS subsystem was added when one or more subsystems already was present, and the existing information in abainstallinfo was converted to abainstallhistory.

 

But these exceptions aside, if the first subsystem you install is ABAPERLS, this column is never NULL.

 

There is no FK on this column to abasubsystems to permit for historic subystems that may have been flushed out with DBBUILD -restruct.


ss_label

Which label that was used if any. This column is always NULL for a patch, because patches do not affect the subsystem label.

 

In most cases, this will be a label that exists in abasslabels. However, in the case where the ABAPERLS subsytstem was added to existing databases, you may see non-standard labels coming from abainstallinfo. You will also see a non-standard label, if DBBUILD or DBUPDGEN was run for a date.


vc_repository

The version-control repository (e.g. TFS database) from which the files in the script were taken.


vc_path

Path in the repository from which the installation originated..


Tables referring to abainstallhistory

Child Table

Foreign Key Columns

abasubsystems

inhid


Tables abainstallhistory refers to

Parent Table

Foreign Key Columns

abarepositorymappings

vc_repository