Firebird Wire Protocol Carlos Guzman Alvarez, Mark Rotteveel Version 0.15, 26 December 2021 Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.1.1. Deviations for protocol version 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.2.1. Deviations for protocol version 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

335544750 password_required A password is required for this operation -85 335544751 bad_protocol The network protocol specified is invalid -85 335544752 dup_usrname_found A duplicate user name was found 335740933 gfix_replay_req Replay log pathname required -901 335740934 gfix_pgbuf_req Number of page buffers for cache Firebird 1.5 Error Codes Updated 04/30/04 p. 17 required -901 335740935 gfix_val_req gbak_page_buffers_missing Page buffers parameter missing -901 336331011 gbak_page_buffers_wrong_param Expected page buffers, encountered "" -901 336331012 gbak_page_buffers_restore Page buffers is allowed

335544750 password_required A password is required for this operation -85 335544751 bad_protocol The network protocol specified is invalid -85 335544752 dup_usrname_found A duplicate user name was found 336330758 gbak_unknown_device Device type %s not known -901 335740934 gfix_pgbuf_req Number of page buffers for cache required -901 336330759 gbak_no_protection Protection is not there yet -901 335740935 gbak_page_buffers_missing Page buffers parameter missing -901 336331011 gbak_page_buffers_wrong_param Expected page buffers, encountered "%s" -901 336331012 gbak_page_buffers_restore Page buffers is allowed

335544750 password_required A password is required for this operation -85 335544751 bad_protocol The network protocol specified is invalid -85 335544752 dup_usrname_found A duplicate user name was found bad_dpb_form Unrecognized database parameter block -901 335740934 gfix_pgbuf_req Number of page buffers for cache required -901 336986118 fbsvcmgr_switch_unknown Unknown switch "@1" -901 336330758 gbak_unknown_device gbak_page_buffers_missing Page buffers parameter missing -901 336331011 gbak_page_buffers_wrong_param Expected page buffers, encountered "@1" -901 336331012 gbak_page_buffers_restore Page buffers is allowed

-B[ACKUP_DATABASE] backup database to file -BU[FFERS] override page buffers default -C[REATE_DATABASE] create database from backup file -CO[NVERT] backup -- data in XDR format gbak:restore options are: -BU(FFERS) override page buffers default -FIX_FSS_D(ATA) fix malformed UNICODE_FSS data -FIX_FSS_M(ETADATA) following switches, in addition to the common ones above, will be of use: -BU[FFERS] buffers> This switch sets the default database cache size (in number of database pages) for the database

-b(ail) bail on errors (set bail on) -c(ache) number of cache buffers -ch(arset) connection charset (set names) -d(atabase) database db_alias} ::= host[/{port | service}]: | \\host\ | <protocol>://[host[:{port | service}]/] <protocol> ::= inet | inet4 | inet6 | wnet | xnet All Firebird versions support the first specifies the name of the protocol, then a host name or IP address, port number, and path of the primary database file, or an alias. The following values can be specified as the protocol: INET TCP/IP (first

remote server specification. The remote server specification depends on the protocol being used. If you use the TCP/IP protocol to create a database, the primary file specification should look like this: this: _servername_[/{_port_|_service_}]:{_filepath_ | _db_alias_} If you use the Named Pipes protocol to create a database on a Windows server, the primary file specification should look like this: \ specified in the alias “test” that has been defined previously in the file aliases.conf. The TCP/IP protocol is used. The owner of the database will be the user wizard. The database will be in Dialect 3 and

LC_MESSAGES, LC_TYPE, LEV, LOG_BUFFER_SIZE, MAX_SEGMENT, MAXIMUM, MESSAGE, MINIMUM, NOAUTO, NUM_LOG_BUFFERS, OUTPUT, PAGELENGTH, PREPARE, PUBLIC, QUIT, RETURN, RUNTIME, SHELL, SHOW, SQLERROR, SQLWARNING LC_TYPE LEV LOG_BUF_SIZE LOG_BUFFER_SIZE LOGFILE MAX_SEGMENT MAXIMUM MESSAGE MINIMUM NOAUTO NUM_LOG_BUFFERS NUM_LOG_BUFS OUTPUT PAGELENGTH PREPARE PUBLIC QUIT RAW_PARTITIONS RETURN RUNTIME SHELL 24 Руководство VARIABLE REMOTE_PROTOCOL VARCHAR(8); DECLARE VARIABLE APP_NAME VARCHAR(253); DECLARE VARIABLE SERVER_PID INTEGER; DECLARE VARIABLE PC_USER_PID INTEGER; BEGIN SELECT M_A.MON$REMOTE_PROTOCOL, M_A.MON$REMOTE_PROCESS

db_alias} "'" ::= host[/{port | service}]: | \\host\ | <protocol>://[host[:{port | service}]/] <protocol> ::= inet | inet4 | inet6 | wnet | xnet Chapter 5. Data Definition (DDL) Statements remote server specification. The remote server specification depends on the protocol being used. If you use the TCP/IP protocol to create a database, the primary file specification should look like this: this: host[/{port|service}]:{filepath | db_alias} If you use the Named Pipes protocol to create a database on a Windows server, the primary file specification should look like this: \\host\{filepath |