General
During an update of the Automic AutomationEngine database the DB.Load utility sets the db status to "empty". When loadingUC_UPD.TXT is finished the db status is set to "ready" again.
In case of DB.Load cannot finish loadingUC_UPD.TXT successfully the db status remains "empty". Possible reasons for anabortion are:
Step 1
Find the reason for the abortion and fixit. E.g. adjust the db user's authorizations.
Step 2
Find out which of the steps in UC_UPD.TXTwere executed successfully before the failure. Remove successfully executedcommands from UC_UPD.TXT and / or form the subordinated (sql-) scripts, whichare called by UC_UPD.TXT.
Step 3
Prepare UC_UPD.TXT for the restart and loadit again. That means the DB.Load has to start with an "empty" db status.
For example: Update from 6.00A to 8.00Auses the following entry point:
check_db_version
dbvers 6.00A R 8.00A
message *************************************************************
message *** DB-Schema 6.00A wasrecognized ***
message *** It will be changedto 8.00A ***
message *************************************************************
Once the db is in "empty" status, this entrypoint should look like:
check_db_version
dbvers 8.00 L 8.00A
message *************************************************************
message *** DB-Schema 6.00A wasrecognized ***
message *** It will be changedto 8.00A ***
message *************************************************************
Messages if you skip Step 3
U0038042 DB-Version = 8.00/L
English | German |
Version and status of database: '8.00'/'LEER'. | Version und Zustand der Datenbank: '8.00'/'LEER'. |
Version and content of data file: '8.00A'/'UPGRADE'. | Version und Inhalt des Datenfiles: '8.00A'/'UPGRADE' |
Version of database objects: 'Empty' | Version der Datenbankobjekte: 'Leer' |
Note: In this case nothing happens, because no entry point fits to the dbstatus. Just go ahead and do step 3.