28. Mai 2020 ## I nhaltsverzeichnis 1. Einleitung ..... 2 2. Der Firebird-Cache ..... 3 3. MON$IO_STATS verwenden ..... 4 Appendices ..... 8 Anhang A: Dokumenthistorie ..... 9 Anhang B: Lizenzhinweis nach Gebrauch - aber der Cache wird immer gefüllt sein. Sie können die MON$-Tabellen (seit Firebird 2.1, insbesondere MON$IO_STATS) nutzen, um herauszufinden, wie gut Ihr Cache ausgelastet ist. Sie zeigen Wenn die Anzahl der Reads dramatisch in die Höhe geht, haben Sie den Cache zu sehr reduziert. Die MON$-Tabellen zeigen Ihnen außerdem die Anzahl der Marks gegen die Anzahl der Writes, welche angeben, wie

2020 ## Table of Contents 1. Introduction ..... 2 2. The Firebird Cache ..... 3 3. Using MON$IO_STATS ..... 4 Appendices ..... 8 Appendix A: Document history ..... 9 Appendix B: License notice out as required - but the cache will always be full. You can use the MON$ tables (in Firebird 2.1 onwards, especially MON$IO_STATS) to figure out how well your cache is being used. They will report on from disk. When the number of reads goes up dramatically, you've reduced the cache too much. The MON$ tables will also give you the number of Marks vs. Writes, which tells you the number of times pages

Tables 501 MON$ATTACHMENTS 502 Using MON$ATTACHMENTS to Kill a Connection 503 MON$CALL_STACK 503 MON$CONTEXT_VARIABLES 505 MON$DATABASE 505 MON$IO_STATS 506 MON$MEMORY_USAGE 507 MON$RECORD_STATS MON$RECORD_STATS 508 MON$STATEMENTS 508 Using MON$STATEMENTS to Cancel a Query 509 MON$TRANSACTIONS 509 Appendix F: Character Sets and Collation Sequences 511 Appendix G: License notice 517 Appendix H: event triggers will not be executed when clients are disconnected via monitoring tables (DELETE FROM MON$ATTACHMENTS) Only the database owner and administrators have the authority to create database triggers

689 MON$attachments ..... 690 Использование MON$attachments для закрытия подключений ..... 691 MON$call_stack ..... 692 MON$context_variables ..... 693 MON$database ..... 694 MON$io_stats ... .. 696 MON$memory_usage ..... 696 MON$record_stats ..... 698 MON$statements ..... 699 Использование MON$statements для отмены запросов ..... 700 MON$table_stats ..... 701 MON$transactions шифрования. ## Примечание Процесс шифрования может быть проконтролирован с помощью поля MON$CRYPT_PAGE в псевдо-таблице MON$DATABASE или просмотрен на странице заголовка базы данных с помощью gstat -e. gstat

it’s not really all that secure as the following SQL command shows: SQL> select MON$DATABASE_NAME from mon$database; MON$DATABASE_NAME ================================= /data/databases/firebird/test.fdb and later no longer has system functions as such), collations and roles. SQL> show system; Tables: MON$ATTACHMENTS ... SEC$USER_ATTRIBUTES Collations: ASCII ... WIN_PTBR Roles: RDB$ADMIN The show system show command. SQL> show table mon$io_stats; MON$STAT_ID (RDB$STAT_ID) INTEGER Nullable MON$STAT_GROUP (RDB$STAT_GROUP) SMALLINT Nullable MON$PAGE_READS

Tables 750 MON$ATTACHMENTS 751 Using MON$ATTACHMENTS to Kill a Connection 753 MON$CALL_STACK 753 MON$CONTEXT_VARIABLES 754 MON$DATABASE 755 MON$IO_STATS 757 MON$MEMORY_USAGE 757 MON$RECORD_STATS MON$RECORD_STATS 759 MON$STATEMENTS 760 Using MON$STATEMENTS to Cancel a Query 760 MON$TABLE_STATS 761 MON$TRANSACTIONS 762 Appendix F: Security tables 764 SEC$DB_CREATORS 764 SEC$GLOBAL_AUTH_MAPPING event triggers will not be executed when clients are disconnected via monitoring tables (DELETE FROM MON$ATTACHMENTS) Only the database owner and administrators have the authority to create database triggers

675 MON$ATTACHMENTS ..... 676 Verwendung von MON$ATTACHMENTS um eine Verbindung zu beenden ..... 677 MON$CALL_STACK ..... 678 MON$CONTEXT_VARIABLES ..... 679 MON$DATABASE ..... 680 MON$IO_STATS 681 MON$MEMORY_USAGE ..... 682 MON$RECORD_STATS ..... 683 MON$STATEMENTS ..... 685 Verwenden von MON$STATEMENTS zum Abbrechen einer Abfrage ..... 685 MON$TABLE_STATS ..... 686 MON$TRANSACTIONS ROLLBACK werden nicht ausgeführt, wenn Clients über Monitoring-Tabellen getrennt werden (DELETE FROM MON$ATTACHMENTS) Nur der Datenbankbesitzer und Administratoren haben die Berechtigung, Datenbank-Trigger

[dmtsai@study ~]$ su - # 这个指令在让你的身份变成 root ！下面请输入 root 的密码！ Password: # 就这里！请输入安装时你所设置的 root 密码！ Last login: Mon Jun 1 16:10:12 CST 2015 on pts/0 [root@study ~]# sync ![Image](/uploads/documents/b/a/d/d/baddd5 Found a swap file by the name ".man_db.conf.swp" <==下面数列说明有暂存盘的存在 owned by: dmtsai dated: Mon Jul 6 23:54:16 2015 file name: /tmp/vitest/man_db.conf <==这个暂存盘属于哪个实际的文件? modified: no user name: dmtsai host name: study.centos.vbird process ID: 31851 While opening file "man_db.conf" dated: Mon Jul 6 23:47:21 2015 下面说明可能发生这个错误的两个主要原因与解决方案！ (1) Another program may be editing the same file. If

|Infernalis|V9.0.0|2015.5.5| |Jewel|V10.0.0|2015.11| |Jewel|V10.2.0|2016.3| ### 1.2 Ceph的功能组件 Ceph提供了RADOS、OSD、MON、Librados、RBD、RGW和Ceph FS等功能组件，但其底层仍然使用RADOS存储来支撑上层的那些组件，如图1-2所示。 ![Image](/uploads/documents/d/0/4 情况进行相应调整和添加。具体优化情况本书后面会介绍。 [global] fsid = 67d997c9-dc13-4edf-a35f-76fd693aa118 mon_initial_members = node1, node2 mon_host = 192.168.1.2, 192.168.1.3 auth_cluster_required = cephx auth_service_required network = {ip-address}/{netmask} public network，一般生产都是定义两个网络，集群网络和数据网络分开 [mon] ..... 这里配置文件不再过多叙述。 10）安装Ceph到各节点。 root@localhost:~# ceph-deploy install {ceph-node}[{ceph-node}

file(s) are created; • The header page is formatted and written; • The various system tables—RDB$ and MON$—and associated indices are created, and appropriate pages formatted and written to disc; • Every 00 39 30 08 00 00 00|00 00 00 00| |---|---|---| From Firebird 2.x onwards, there is a system table—MON$DATABASE which has a copy of all of the above data in an easy to obtain format:  VARCHAR(253) NullableMON$PAGE_SIZE(RDB$PAGE_SIZE) SMALLINT NullableMON$ODS_M