3. Standard Database Page Header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Database Header Page — Type 0x01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 8.1. Record Header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 10.1. B-Tree Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

not been activated. We can see that shadows are in use if we use gstat as follows: linux> gstat -header my_employee | grep -i shadow Shadow count 2  Sometimes, it takes gstat a while to figure out that activated, you can see the fact that there are active shadows in the output from gstat: linux> gstat -header my_employee | grep -i shadow Shadow count 2 Attributes active shadow, multi-user maintenance  gstat still shows the database as having two shadows, even when one has been removed. linux> gstat -header my_employee | grep -i shadow Shadow count 2 Attributes active shadow, multi-user maintenance 

actually deleted. DROP DIFFERENCE FILE deletes the path and name of the .delta file from the database header. Next time the database is switched to the “copy- Chapter 5. Data Definition (DDL) Statements 112 default value), shadowing ceases automatically, all references to it are deleted from the database header, and the database continues functioning normally. If the CONDITIONAL option was set, the system CREATE OR ALTER TRIGGER and RECREATE TRIGGER, is a compound statement, consisting of a header and a body. The header specifies the name of the trigger, the name of the relation (for a DML trigger), the

actually deleted. DROP DIFFERENCE FILE deletes the path and name of the .delta file from the database header. Next time the database is switched to the “copy-safe” mode, the default values will be used (i default value), shadowing ceases automatically, all references to it are deleted from the database header and the database continues functioning normally. If the CONDITIONAL option was set, the system will CREATE OR ALTER TRIGGER and RECREATE TRIGGER, is a compound statement, consisting of a header and a body. The header specifies the name of the trigger, the name of the relation (for a relation trigger)

gelöscht. DROP DIFFERENCE FILE löscht den Pfad und den Namen der .delta-Datei aus dem Datenbank-Header. Wenn die Datenbank das nächste Mal in den “copy-safe”-Modus geschaltet wird, werden die Standardwerte TRIGGER und RECREATE TRIGGER eine zusammengesetzte Anweisung, bestehend aus einem Header und einem Body. Der Header gibt den Namen des Triggers, den Namen der Beziehung (bei einem DML-Trigger), die Kapitel. Der Trigger-Body Die lokalen Deklarationen (sofern vorhanden) sind der letzte Teil des Header-Abschnitts eines Triggers. Es folgt der Triggerrumpf, wobei ein oder mehrere Blöcke von PSQL-Anweisungen

Table %s is not defined -230 335544487 walw_err WAL Writer error -231 335544488 logh_small Log file header of %s too small -232 335544489 logh_inv_version Invalid version of log file %s -233 335544490 logh_open_flag logr_incomplete Incomplete log record at offset %ld in log file %s -238 335544495 logr_header_small Log record header too small at offset %ld in log file %s -239 335544496 logb_small Log block too small gbak_unk_db_file_spec Database file specification missing -901 336331021 gbak_hdr_write_failed Can't write a header record to file %s -901 336331022 gbak_disk_space_ex Free disk space exhausted -901 336331023 gbak_size_lt_min

Domain @1 is not defined -230 335544487 walw_err WAL Writer error -231 335544488 logh_small Log file header of @1 too small -232 335544489 logh_inv_version Invalid version of log file @1 -233 335544490 logh_open_flag logr_incomplete Incomplete log record at offset @1 in log file @2 -238 335544495 logr_header_small Log record header too small at offset @1 in log file @2 -239 335544496 logb_small Log block too small gbak_unk_db_file_spec Database file specification missing -901 336331021 gbak_hdr_write_failed Can't write a header record to file @1 -901 336331022 gbak_disk_space_ex Free disk space exhausted -901 336331023 gbak_size_lt_min

"Arbeits"- Bereich und dem Festplattenspeicher. Beim Start liest Firebird die Datenbank-Header-Seite (engl. database header page), dann die erste Zeiger-Seite (engl. pointer page) der Systemtabelle RDB$PAGES Cache verbleiben - das wären Transaktions-Inventar-Seiten, Zeiger-Seiten für aktive Tabellen, die Header-Seite, die Top-Level-Indexes, etc.. Daten und Lower-Level-Index-Seiten werden rein- und rausgeladen

-230 335544487 walw_err WAL Writer error. Ошибка записи WAL. -231 335544488 logh_small Log file header of @1 too small. Заголовок файла лога @1 слишком мал. -232 335544489 logh_inv_version Invalid file @2. Неполная запись лога по смещению @1 в файл лога @2. -238 335544495 logr_header_small Log record header too small at offset @1 in log file @2. Заголовок записи лога слишком мал по смещению Файл спецификации базы данных отсутствует -901 336331021 gbak_hdr_write_failed Can't write a header record to file @1 Не могут записать заголовок в файл @1 -901 336331022 gbak_disk_space_ex Free

"working" parts of the database and the disk. When initially started, Firebird reads the database header page, then the first pointer page of a system table called RDB$PAGES from which it then knows where in the cache - those would be transaction inventory pages, pointer pages for active tables, the header page, the top levels of indexes, etc. Data and lower level index pages swap in and out as required