I installed firebird database for the first time in my life (version 1.5.6 on Windows 7), after installation I can not connect to the sample database (employee.fdb exists), or create a database. This gives the following error in ISQL Tool:
C:Program FilesFirebirdFirebird_1_5bin>isql
Use CONNECT or CREATE DATABASE to specify a database
SQL> CONNECT "C:Program FilesFirebirdFirebird_1_5examplesemployee.fdb"
CON> user 'SYSDBA' password 'masterkey';
Statement failed, SQLCODE = -904
unavailable database
SQL> create database 'C:test.fdb'
CON> user 'SYSDBA' password 'masterkey';
Statement failed, SQLCODE = -904
unavailable database
asked May 9, 2013 at 19:57
Bartłomiej PachBartłomiej Pach
2411 gold badge6 silver badges13 bronze badges
1
Firebird 1.5 was written (long) before Windows 7, and before things like UAC existed. It may simply be that Firebird 1.5 doesn’t work correctly with Windows 7, or that it requires additional effort to work. I’d suggest to install Firebird 2.5.2 (update 1) as that is the latest version and is known to work with Windows 7.
Another problem might be that local system connections don’t work as I seem to remember that Firebird 1.5 uses an older local protocol which doesn’t work on newer Windows versions. This protocol was replaced in Firebird 2.0. To workaround that you need to include the hostname in the CREATE DATABASE
or CONNECT
statement, so for example:
create database 'localhost:C:test.fdb' user 'SYSDBA' password 'masterkey';
answered May 10, 2013 at 6:53
Mark RotteveelMark Rotteveel
96.7k180 gold badges135 silver badges188 bronze badges
Windows 7+ breaks the local api protocol. You have to use Tcpip protocol to connect to the database, even for local connections.
answered Aug 13, 2015 at 5:05
Rohit GuptaRohit Gupta
3,86513 gold badges30 silver badges41 bronze badges
The table provides the SQLCODE groupings, the numeric and symbolic values for the GDSCODE errors and the message texts.
🛈︎
Note
SQLCODE
has been used for many years and should be considered as deprecated now.
Support for SQLCODE
is likely to be dropped in a future version.
Table B.2.1 SQLCODE and GDSCODE Error Codes and Message Texts (1)
SQLCODE | GDSCODE | Symbol | Message Text |
---|---|---|---|
101 |
335544366 |
Segment |
Segment buffer length shorter than expected |
100 |
335544338 |
from_no_match |
No match for first value expression |
100 |
335544354 |
no_record |
Invalid database key |
100 |
335544367 |
segstr_eof |
Attempted retrieval of more segments than exist |
100 |
335544374 |
stream_eof |
Attempt to fetch past the last record in a record stream |
0 |
335741039 |
gfix_opt_SQL_dialect |
-sql_dialect | set database dialect n |
0 |
335544875 |
bad_debug_format |
Bad debug info format |
-84 |
335544554 |
nonsql_security_rel |
Table/procedure has non-SQL security class defined |
-84 |
335544555 |
nonsql_security_fld |
Column has non-SQL security class defined |
-84 |
335544668 |
dsql_procedure_use_err |
Procedure @1 does not return any values |
-85 |
335544747 |
usrname_too_long |
The username entered is too long. Maximum length is 31 bytes |
-85 |
335544748 |
password_too_long |
The password specified is too long. Maximum length is @1 bytes |
-85 |
335544749 |
usrname_required |
A username is required for this operation |
-85 |
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 in the security database |
-85 |
335544753 |
usrname_not_found |
The user name specified was not found in the security database |
-85 |
335544754 |
error_adding_sec_record |
An error occurred while attempting to add the user |
-85 |
335544755 |
error_modifying_sec_record |
An error occurred while attempting to modify the user record |
-85 |
335544756 |
error_deleting_sec_record |
An error occurred while attempting to delete the user record |
-85 |
335544757 |
error_updating_sec_db |
An error occurred while updating the security database |
-103 |
335544571 |
dsql_constant_err |
Data type for constant unknown |
-104 |
336003075 |
dsql_transitional_numeric |
Precision 10 to 18 changed from DOUBLE PRECISION in SQL dialect 1 to 64-bit scaled integer in SQL dialect 3 |
-104 |
336003077 |
sql_db_dialect_dtype_unsupport |
Database SQL dialect @1 does not support reference to @2 datatype |
-104 |
336003087 |
dsql_invalid_label |
Label @1 @2 in the current scope |
-104 |
336003088 |
dsql_datatypes_not_comparable |
Datatypes @1are not comparable in expression @2 |
-104 |
335544343 |
invalid_blr |
Invalid request BLR at offset @1 |
-104 |
335544390 |
syntaxerr |
BLR syntax error: expected @1 at offset @2, encountered @3 |
-104 |
335544425 |
ctxinuse |
Context already in use (BLR error) |
-104 |
335544426 |
ctxnotdef |
Context not defined (BLR error) |
-104 |
335544429 |
badparnum |
Bad parameter number |
-104 |
335544440 |
bad_msg_vec |
— |
-104 |
335544456 |
invalid_sdl |
Invalid slice description language at offset @1 |
-104 |
335544570 |
dsql_command_err |
Invalid command |
-104 |
335544579 |
dsql_internal_err |
Internal error |
-104 |
335544590 |
dsql_dup_option |
Option specified more than once |
-104 |
335544591 |
dsql_tran_err |
Unknown transaction option |
-104 |
335544592 |
dsql_invalid_array |
Invalid array reference |
-104 |
335544608 |
command_end_err |
Unexpected end of command |
-104 |
335544612 |
token_err |
Token unknown |
-104 |
335544634 |
dsql_token_unk_err |
Token unknown — line @1, column @2 |
-104 |
335544709 |
dsql_agg_ref_err |
Invalid aggregate reference |
-104 |
335544714 |
invalid_array_id |
Invalid blob id |
-104 |
335544730 |
cse_not_supported |
Client/Server Express not supported in this release |
-104 |
335544743 |
token_too_long |
Token size exceeds limit |
-104 |
335544763 |
invalid_string_constant |
A string constant is delimited by double quotes |
-104 |
335544764 |
transitional_date |
DATE must be changed to TIMESTAMP |
-104 |
335544796 |
sql_dialect_datatype_unsupport |
Client SQL dialect @1 does not support reference to @2 datatype |
-104 |
335544798 |
depend_on_uncommitted_rel |
You created an indirect dependency on uncommitted metadata. |
-104 |
335544821 |
dsql_column_pos_err |
Invalid column position used in the @1 clause |
-104 |
335544822 |
dsql_agg_where_err |
Cannot use an aggregate function in a WHERE clause, use HAVING instead |
-104 |
335544823 |
dsql_agg_group_err |
Cannot use an aggregate function in a GROUP BY clause |
-104 |
335544824 |
dsql_agg_column_err |
Invalid expression in the @1 (not contained in either an aggregate function or the GROUP BY clause) |
-104 |
335544825 |
dsql_agg_having_err |
Invalid expression in the @1 (neither an aggregate function nor a part of the GROUP BY clause) |
-104 |
335544826 |
dsql_agg_nested_err |
Nested aggregate functions are not allowed |
-104 |
335544849 |
malformed_string |
Malformed string |
-104 |
335544851 |
command_end_err2 |
Unexpected end of command- line @1, column @2 |
-104 |
336397215 |
dsql_max_sort_items |
Cannot sort on more than 255 items |
-104 |
336397216 |
dsql_max_group_items |
Cannot group on more than 255 items |
-104 |
336397217 |
dsql_conflicting_sort_field |
Cannot include the same field (@[email protected]) twice in the ORDER BY clause with conflicting sorting options |
-104 |
336397218 |
dsql_derived_table_more_columns |
Column list from derived table @1 has more columns than the number of items in its SELECT statement |
-104 |
336397219 |
dsql_derived_table_less_columns |
Column list from derived table @1 has less columns than the number of items in its SELECT statement |
-104 |
336397220 |
dsql_derived_field_unnamed |
No column name specified for column number @1 in derived table @2 |
-104 |
336397221 |
dsql_derived_field_dup_name |
Column @1 was specified multiple times for derived table @2 |
-104 |
336397222 |
dsql_derived_alias_select |
Internal dsql error: alias type expected by pass1_expand_select_node |
-104 |
336397223 |
dsql_derived_alias_field |
Internal dsql error: alias type expected by pass1_field |
-104 |
336397224 |
dsql_auto_field_bad_pos |
Internal dsql error: column position out of range in pass1_union_auto_cast |
-104 |
336397225 |
dsql_cte_wrong_reference |
Recursive CTE member (@1) can refer itself only in FROM clause |
-104 |
336397226 |
dsql_cte_cycle |
CTE ‘@1’ has cyclic dependencies |
-104 |
336397227 |
dsql_cte_outer_join |
Recursive member of CTE can’t be member of an outer join |
-104 |
336397228 |
dsql_cte_mult_references |
Recursive member of CTE can’t reference itself more than once |
-104 |
336397229 |
dsql_cte_not_a_union |
Recursive CTE (@1) must be an UNION |
-104 |
336397230 |
dsql_cte_nonrecurs_after_recurs |
CTE ‘@1’ defined non-recursive member after recursive |
-104 |
336397231 |
dsql_cte_wrong_clause |
Recursive member of CTE ‘@1’ has @2 clause |
-104 |
336397232 |
dsql_cte_union_all |
Recursive members of CTE (@1) must be linked with another members via UNION ALL |
-104 |
336397233 |
dsql_cte_miss_nonrecursive |
Non-recursive member is missing in CTE ‘@1’ |
-104 |
336397234 |
dsql_cte_nested_with |
WITH clause can’t be nested |
-104 |
336397235 |
dsql_col_more_than_once_using |
Column @1 appears more than once in USING clause |
-104 |
336397237 |
dsql_cte_not_used |
CTE «@1» is not used in query |
-105 |
335544702 |
like_escape_invalid |
Invalid ESCAPE sequence |
-105 |
335544789 |
extract_input_mismatch |
Specified EXTRACT part does not exist in input datatype |
-150 |
335544360 |
read_only_rel |
Attempted update of read-only table |
-150 |
335544362 |
read_only_view |
Cannot update read-only view @1 |
-150 |
335544446 |
non_updatable |
Not updatable |
-150 |
335544546 |
constaint_on_view |
Cannot define constraints on views |
-151 |
335544359 |
read_only_field |
Attempted update of read — only column |
-155 |
335544658 |
dsql_base_table |
@1 is not a valid base table of the specified view |
-157 |
335544598 |
specify_field_err |
Must specify column name for view select expression |
-158 |
335544599 |
num_field_err |
Number of columns does not match select list |
-162 |
335544685 |
no_dbkey |
Dbkey not available for multi — table views |
-170 |
335544512 |
prcmismat |
Input parameter mismatch for procedure @1 |
-170 |
335544619 |
extern_func_err |
External functions cannot have more than 10 parameters |
-170 |
335544850 |
prc_out_param_mismatch |
Output parameter mismatch for procedure @1 |
-171 |
335544439 |
funmismat |
Function @1 could not be matched |
-171 |
335544458 |
invalid_dimension |
Column not array or invalid dimensions (expected @1, encountered @2) |
-171 |
335544618 |
return_mode_err |
Return mode by value not allowed for this data type |
-171 |
335544873 |
array_max_dimensions |
Array data type can use up to @1 dimensions |
-172 |
335544438 |
funnotdef |
Function @1 is not defined |
-203 |
335544708 |
dyn_fld_ambiguous |
Ambiguous column reference |
-204 |
336003085 |
dsql_ambiguous_field_name |
Ambiguous field name between @1 and @2 |
-204 |
335544463 |
gennotdef |
Generator @1 is not defined |
-204 |
335544502 |
stream_not_defined |
Reference to invalid stream number |
-204 |
335544509 |
charset_not_found |
CHARACTER SET @1 is not defined |
-204 |
335544511 |
prcnotdef |
Procedure @1 is not defined |
-204 |
335544515 |
codnotdef |
Status code @1 unknown |
-204 |
335544516 |
xcpnotdef |
Exception @1 not defined |
-204 |
335544532 |
ref_cnstrnt_notfound |
Name of Referential Constraint not defined in constraints table |
-204 |
335544551 |
grant_obj_notfound |
Could not find table/procedure for GRANT |
-204 |
335544568 |
text_subtype |
Implementation of text subtype @1 not located |
-204 |
335544573 |
dsql_datatype_err |
Data type unknown |
-204 |
335544580 |
dsql_relation_err |
Table unknown |
-204 |
335544581 |
dsql_procedure_err |
Procedure unknown |
-204 |
335544588 |
collation_not_found |
COLLATION @1 for CHARACTER SET @2 is not defined |
-204 |
335544589 |
collation_not_for_charset |
COLLATION @1 is not valid for specified CHARACTER SET |
-204 |
335544595 |
dsql_trigger_err |
Trigger unknown |
-204 |
335544620 |
alias_conflict_err |
Alias @1 conflicts with an alias in the same statement |
-204 |
335544621 |
procedure_conflict_error |
Alias @1 conflicts with a procedure in the same statement |
-204 |
335544622 |
relation_conflict_err |
Alias @1 conflicts with a table in the same statement |
-204 |
335544635 |
dsql_no_relation_alias |
There is no alias or table named @1 at this scope level |
-204 |
335544636 |
indexname |
There is no index @1 for table @2 |
-204 |
335544640 |
collation_requires_text |
Invalid use of CHARACTER SET or COLLATE |
-204 |
335544662 |
dsql_blob_type_unknown |
BLOB SUB_TYPE @1 is not defined |
-204 |
335544759 |
bad_default_value |
Can not define a not null column with NULL as default value |
-204 |
335544760 |
invalid_clause |
Invalid clause — ‘@1’ |
-204 |
335544800 |
too_many_contexts |
Too many Contexts of Relation/Procedure/Views. Maximum allowed is 255 |
-204 |
335544817 |
bad_limit_param |
Invalid parameter to FIRST.Only integers >= 0 are allowed |
-204 |
335544818 |
bad_skip_param |
Invalid parameter to SKIP. Only integers >= 0 are allowed |
-204 |
335544837 |
bad_substring_offset |
Invalid offset parameter @1 to SUBSTRING. Only positive integers are allowed |
-204 |
335544853 |
bad_substring_length |
Invalid length parameter @1 to SUBSTRING. Negative integers are not allowed |
-204 |
335544854 |
charset_not_installed |
CHARACTER SET @1 is not installed |
-204 |
335544855 |
collation_not_installed |
COLLATION @1 for CHARACTER SET @2 is not installed |
-204 |
335544867 |
subtype_for_internal_use |
Blob sub_types bigger than 1 (text) are for internal use only |
-205 |
335544396 |
fldnotdef |
Column @1 is not defined in table @2 |
-205 |
335544552 |
grant_fld_notfound |
Could not find column for GRANT |
-205 |
335544883 |
fldnotdef2 |
Column @1 is not defined in procedure @2 |
-206 |
335544578 |
dsql_field_err |
Column unknown |
-206 |
335544587 |
dsql_blob_err |
Column is not a BLOB |
-206 |
335544596 |
dsql_subselect_err |
Subselect illegal in this context |
-206 |
336397208 |
dsql_line_col_error |
At line @1, column @2 |
-206 |
336397209 |
dsql_unknown_pos |
At unknown line and column |
-206 |
336397210 |
dsql_no_dup_name |
Column @1 cannot be repeated in @2 statement |
-208 |
335544617 |
order_by_err |
Invalid ORDER BY clause |
-219 |
335544395 |
relnotdef |
Table @1 is not defined |
-219 |
335544872 |
domnotdef |
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 |
Log file @1 not latest in the chain but open flag still set |
-234 |
335544491 |
logh_open_flag2 |
Log file @1 not closed properly; database recovery may be required |
-235 |
335544492 |
logh_diff_dbname |
Database name in the log file @1 is different |
-236 |
335544493 |
logf_unexpected_eof |
Unexpected end of log file @1 at offset @2 |
-237 |
335544494 |
logr_incomplete |
Incomplete log record at offset @1 in log file @2 |
-238 |
335544495 |
logr_header_small2 |
Log record header too small at offset @1 in log file @ |
-239 |
335544496 |
logb_small |
Log block too small at offset @1 in log file @2 |
-239 |
335544691 |
cache_too_small |
Insufficient memory to allocate page buffer cache |
-239 |
335544693 |
log_too_small |
Log size too small |
-239 |
335544694 |
partition_too_small |
Log partition size too small |
-243 |
335544500 |
no_wal |
Database does not use Write-ahead Log |
-257 |
335544566 |
start_cm_for_wal |
WAL defined; Cache Manager must be started first |
-260 |
335544690 |
cache_redef |
Cache redefined |
-260 |
335544692 |
log_redef |
Log redefined |
-261 |
335544695 |
partition_not_supp |
Partitions not supported in series of log file specification |
-261 |
335544696 |
log_length_spec |
Total length of a partitioned log must be specified |
-281 |
335544637 |
no_stream_plan |
Table @1 is not referenced in plan |
-282 |
335544638 |
stream_twice |
Table @1 is referenced more than once in plan; use aliases to distinguish |
-282 |
335544643 |
dsql_self_join |
The table @1 is referenced twice; use aliases to differentiate |
-282 |
335544659 |
duplicate_base_table |
Table @1 is referenced twice in view; use an alias to distinguish |
-282 |
335544660 |
view_alias |
View @1 has more than one base table; use aliases to distinguish |
-282 |
335544710 |
complex_view |
Navigational stream @1 references a view with more than one base table |
-283 |
335544639 |
stream_not_found |
Table @1 is referenced in the plan but not the from list |
-284 |
335544642 |
index_unused |
Index @1 cannot be used in the specified plan |
-291 |
335544531 |
primary_key_notnull |
Column used in a PRIMARY constraint must be NOT NULL |
-292 |
335544534 |
ref_cnstrnt_update |
Cannot update constraints (RDB$REF_CONSTRAINTS) |
-293 |
335544535 |
check_cnstrnt_update |
Cannot update constraints (RDB$CHECK_CONSTRAINTS) |
-294 |
335544536 |
check_cnstrnt_del |
Cannot delete CHECK constraint entry (RDB$CHECK_CONSTRAINTS) |
-295 |
335544545 |
rel_cnstrnt_update |
Cannot update constraints (RDB$RELATION_CONSTRAINTS) |
-296 |
335544547 |
invld_cnstrnt_type |
Internal gds software consistency check (invalid RDB$CONSTRAINT_TYPE) |
-297 |
335544558 |
check_constraint |
Operation violates check constraint @1 on view or table @2 |
-313 |
336003099 |
upd_ins_doesnt_match_pk |
UPDATE OR INSERT field list does not match primary key of table @1 |
-313 |
336003100 |
upd_ins_doesnt_ match _matching |
UPDATE OR INSERT field list does not match MATCHING clause |
-313 |
335544669 |
dsql_count_mismatch |
Count of column list and variable list do not match |
-314 |
335544565 |
transliteration_failed |
Cannot transliterate character between character sets |
-315 |
336068815 |
dyn_dtype_invalid |
Cannot change datatype for column @1.Changing datatype is not supported for BLOB or ARRAY columns |
-383 |
336068814 |
dyn_dependency_exists |
Column @1 from table @2 is referenced in @3 |
-401 |
335544647 |
invalid_operator |
Invalid comparison operator for find operation |
-402 |
335544368 |
segstr_no_op |
Attempted invalid operation on a BLOB |
-402 |
335544414 |
blobnotsup |
BLOB and array data types are not supported for @1 operation |
-402 |
335544427 |
datnotsup |
Data operation not supported |
-406 |
335544457 |
out_of_bounds |
Subscript out of bounds |
-407 |
335544435 |
nullsegkey |
Null segment of UNIQUE KEY |
-413 |
335544334 |
convert_error |
Conversion error from string «@1» |
Table B.2.2 SQLCODE and GDSCODE Error Codes and Message Texts (2)
SQLCODE | GDSCODE | Symbol | Message Text |
---|---|---|---|
-413 |
335544454 |
nofilter |
Filter not found to convert type @1 to type @2 |
-413 |
335544860 |
blob_convert_error |
Unsupported conversion to target type BLOB (subtype @1) |
-413 |
335544861 |
array_convert_error |
Unsupported conversion to target type ARRAY |
-501 |
335544577 |
dsql_cursor_close_err |
Attempt to reclose a closed cursor |
-502 |
336003090 |
dsql_cursor_redefined |
Statement already has a cursor @1 assigned |
-502 |
336003091 |
dsql_cursor_not_found |
Cursor @1 is not found in the current context |
-502 |
336003092 |
dsql_cursor_exists |
Cursor @1 already exists in the current context |
-502 |
336003093 |
dsql_cursor_rel_ambiguous |
Relation @1 is ambiguous in cursor @2 |
-502 |
336003094 |
dsql_cursor_rel_not_found |
Relation @1 is not found in cursor @2 |
-502 |
336003095 |
dsql_cursor_not_open |
Cursor is not open |
-502 |
335544574 |
dsql_decl_err |
Invalid cursor declaration |
-502 |
335544576 |
dsql_cursor_open_err |
Attempt to reopen an open cursor |
-504 |
336003089 |
dsql_cursor_invalid |
Empty cursor name is not allowed |
-504 |
335544572 |
dsql_cursor_err |
Invalid cursor reference |
-508 |
335544348 |
no_cur_rec |
No current record for fetch operation |
-510 |
335544575 |
dsql_cursor_update_err |
Cursor @1 is not updatable |
-518 |
335544582 |
dsql_request_err |
Request unknown |
-519 |
335544688 |
dsql_open_cursor_request |
The prepare statement identifies a prepare statement with an open cursor |
-530 |
335544466 |
foreign_key |
Violation of FOREIGN KEY constraint «@1» on table «@2» |
-530 |
335544838 |
foreign_key_target_doesnt_exist |
Foreign key reference target does not exist |
-530 |
335544839 |
foreign_key_references_present |
Foreign key references are present for the record |
-531 |
335544597 |
dsql_crdb_prepare_err |
Cannot prepare a CREATE DATABASE/SCHEMA statement |
-532 |
335544469 |
trans_invalid |
Transaction marked invalid by I/O error |
-551 |
335544352 |
no_priv |
No permission for @1 access to @2 @3 |
-551 |
335544790 |
insufficient_svc_privileges |
Service @1 requires SYSDBA permissions. Reattach to the Service Manager using the SYSDBA account |
-552 |
335544550 |
not_rel_owner |
Only the owner of a table may reassign ownership |
-552 |
335544553 |
grant_nopriv |
User does not have GRANT privileges for operation |
-552 |
335544707 |
grant_nopriv_on_base |
User does not have GRANT privileges on base table/view for operation |
-553 |
335544529 |
existing_priv_mod |
Cannot modify an existing user privilege |
-595 |
335544645 |
stream_crack |
The current position is on a crack |
-596 |
335544644 |
stream_bof |
Illegal operation when at beginning of stream |
-597 |
335544632 |
dsql_file_length_err |
Preceding file did not specify length, so @1 must include starting page number |
-598 |
335544633 |
dsql_shadow_number_err |
Shadow number must be a positive integer |
-599 |
335544607 |
node_err |
Gen.c: node not supported |
-599 |
335544625 |
node_name_err |
A node name is not permitted in a secondary, shadow, cache or log file name |
-600 |
335544680 |
crrp_data_err |
Sort error: corruption in data structure |
-601 |
335544646 |
db_or_file_exists |
Database or file exists |
-604 |
335544593 |
dsql_max_arr_dim_exceeded |
Array declared with too many dimensions |
-604 |
335544594 |
dsql_arr_range_error |
Illegal array dimension range |
-605 |
335544682 |
dsql_field_ref |
Inappropriate self-reference of column |
-607 |
336003074 |
dsql_dbkey_from_non_table |
Cannot SELECT RDB$DB_KEY from a stored procedure |
-607 |
336003086 |
dsql_udf_return_pos_err |
External function should have return position between 1 and @1 |
-607 |
336003096 |
dsql_type_not_supp_ext_tab |
Data type @1 is not supported for EXTERNAL TABLES. Relation ‘@2’, field ‘@3’ |
-607 |
335544351 |
no_meta_update |
Unsuccessful metadata update |
-607 |
335544549 |
systrig_update |
Cannot modify or erase a system trigger |
-607 |
335544657 |
dsql_no_blob_array |
Array/BLOB/DATE data types not allowed in arithmetic |
-607 |
335544746 |
reftable_requires_pk |
«REFERENCES table» without «(column)» requires PRIMARY KEY on referenced table |
-607 |
335544815 |
generator_name |
GENERATOR @1 |
-607 |
335544816 |
udf_name |
UDF @1 |
-607 |
335544858 |
must_have_phys_field |
Can’t have relation with only computed fields or constraints |
-607 |
336397206 |
dsql_table_not_found |
Table @1 does not exist |
-607 |
336397207 |
dsql_view_not_found |
View @1 does not exist |
-607 |
336397212 |
dsql_no_array_computed |
Array and BLOB data types not allowed in computed field |
-607 |
336397214 |
dsql_only_can_subscript_array |
Scalar operator used on field @1 which is not an array |
-612 |
336068812 |
dyn_domain_name_exists |
Cannot rename domain @1 to @2. A domain with that name already exists |
-612 |
336068813 |
dyn_field_name_exists |
Cannot rename column @1 to @2.A column with that name already exists in table @3 |
-615 |
335544475 |
relation_lock |
Lock on table @1 conflicts with existing lock |
-615 |
335544476 |
record_lock |
Requested record lock conflicts with existing lock |
-615 |
335544507 |
range_in_use |
Refresh range number @1 already in use |
-616 |
335544530 |
primary_key_ref |
Cannot delete PRIMARY KEY being used in FOREIGN KEY definition |
-616 |
335544539 |
integ_index_del |
Cannot delete index used by an Integrity Constraint |
-616 |
335544540 |
integ_index_mod |
Cannot modify index used by an Integrity Constraint |
-616 |
335544541 |
check_trig_del |
Cannot delete trigger used by a CHECK Constraint |
-616 |
335544543 |
cnstrnt_fld_del |
Cannot delete column being used in an Integrity Constraint |
-616 |
335544630 |
dependency |
There are @1 dependencies |
-616 |
335544674 |
del_last_field |
Last column in a table cannot be deleted |
-616 |
335544728 |
integ_index_deactivate |
Cannot deactivate index used by an integrity constraint |
-616 |
335544729 |
integ_deactivate_primary |
Cannot deactivate index used by a PRIMARY/UNIQUE constraint |
-617 |
335544542 |
check_trig_update |
Cannot update trigger used by a CHECK Constraint |
-617 |
335544544 |
cnstrnt_fld_rename |
Cannot rename column being used in an Integrity Constraint |
-618 |
335544537 |
integ_index_seg_del |
Cannot delete index segment used by an Integrity Constraint |
-618 |
335544538 |
integ_index_seg_mod |
Cannot update index segment used by an Integrity Constraint |
-625 |
335544347 |
not_valid |
Validation error for column @1, value «@2» |
-625 |
335544879 |
not_valid_for_var |
Validation error for variable @1, value «@2» |
-625 |
335544880 |
not_valid_for |
Validation error for @1, value «@2» |
-637 |
335544664 |
dsql_duplicate_spec |
Duplicate specification of @1- not supported |
-637 |
336397213 |
dsql_implicit_domain_name |
Implicit domain name @1 not allowed in user created domain |
-660 |
336003098 |
primary_key_required |
Primary key required on table @1 |
-660 |
335544533 |
foreign_key_notfound |
Non-existent PRIMARY or UNIQUE KEY specified for FOREIGN KEY |
-660 |
335544628 |
idx_create_err |
Cannot create index @1 |
-663 |
335544624 |
idx_seg_err |
Segment count of 0 defined for index @1 |
-663 |
335544631 |
idx_key_err |
Too many keys defined for index @1 |
-663 |
335544672 |
key_field_err |
Too few key columns found for index @1 (incorrect column name?) |
-664 |
335544434 |
keytoobig |
Key size exceeds implementation restriction for index «@1» |
-677 |
335544445 |
ext_err |
@1 extension error |
-685 |
335544465 |
bad_segstr_type |
Invalid BLOB type for operation |
-685 |
335544670 |
blob_idx_err |
Attempt to index BLOB column in index @1 |
-685 |
335544671 |
array_idx_err |
Attempt to index array column in index @1 |
-689 |
335544403 |
badpagtyp |
Page @1 is of wrong type (expected @2, found @3) |
-689 |
335544650 |
page_type_err |
Wrong page type |
-690 |
335544679 |
no_segments_err |
Segments not allowed in expression index @1 |
-691 |
335544681 |
rec_size_err |
New record size of @1 bytes is too big |
-692 |
335544477 |
max_idx |
Maximum indexes per table (@1) exceeded |
-693 |
335544663 |
req_max_clones_exceeded |
Too many concurrent executions of the same request |
-694 |
335544684 |
no_field_access |
Cannot access column @1 in view @2 |
-802 |
335544321 |
arith_except |
Arithmetic exception, numeric overflow, or string truncation |
-802 |
335544836 |
concat_overflow |
Concatenation overflow. Resulting string cannot exceed 32K in length |
-803 |
335544349 |
no_dup |
Attempt to store duplicate value ( visible to active transactions ) in unique index «@1» |
-803 |
335544665 |
unique_key_violation |
Violation of PRIMARY or UNIQUE KEY constraint «@1» on table «@2» |
-804 |
336003097 |
dsql_feature_not_supported_ods |
Feature not supported on ODS version older than @[email protected] |
-804 |
335544380 |
wronumarg |
Wrong number of arguments on call |
-804 |
335544583 |
dsql_sqlda_err |
SQLDA missing or incorrect version, or incorrect number/type of variables |
-804 |
335544584 |
dsql_var_count_err |
Count of read — write columns does not equal count of values |
-804 |
335544586 |
dsql_function_err |
Function unknown |
-804 |
335544713 |
dsql_sqlda_value_err |
Incorrect values within SQLDA structure |
-804 |
336397205 |
dsql_too_old_ods |
ODS versions before [email protected] are not supported |
-806 |
335544600 |
col_name_err |
Only simple column names permitted for VIEW WITH CHECK OPTION |
-807 |
335544601 |
where_err |
No WHERE clause for VIEW WITH CHECK OPTION |
-808 |
335544602 |
table_view_err |
Only one table allowed for VIEW WITH CHECK OPTION |
-809 |
335544603 |
distinct_err |
DISTINCT, GROUP or HAVING not permitted for VIEW WITH CHECK OPTION |
-810 |
335544605 |
subquery_err |
No subqueries permitted for VIEW WITH CHECK OPTION |
-811 |
335544652 |
sing_select_err |
Multiple rows in singleton select |
-816 |
335544651 |
ext_readonly_err |
Cannot insert because the file is readonly or is on a read only medium |
-816 |
335544715 |
extfile_uns_op |
Operation not supported for EXTERNAL FILE table @1 |
-817 |
336003079 |
isc_sql_dialect_conflict_num |
DB dialect @1 and client dialect @2 conflict with respect to numeric precision @3 |
-817 |
336003101 |
upd_ins_with_complex_view |
UPDATE OR INSERT without MATCHING could not be used with views based on more than one table |
-817 |
336003102 |
dsql_incompatible_trigger_type |
Incompatible trigger type |
-817 |
336003103 |
dsql_db_trigger_type_cant_change |
Database trigger type can’t be changed |
-817 |
335544361 |
read_only_trans |
Attempted update during read — only transaction |
-817 |
335544371 |
segstr_no_write |
Attempted write to read-only BLOB |
-817 |
335544444 |
read_only |
Operation not supported |
-817 |
335544765 |
read_only_database |
Attempted update on read — only database |
-817 |
335544766 |
must_be_dialect_2_and_up |
SQL dialect @1 is not supported in this database |
-817 |
335544793 |
ddl_not_allowed_by_db_sql_dial |
Metadata update statement is not allowed by the current database SQL dialect @1 |
-820 |
335544356 |
obsolete_metadata |
Metadata is obsolete |
-820 |
335544379 |
wrong_ods |
Unsupported on — disk structure for file @1; found @[email protected], support @[email protected] |
-820 |
335544437 |
wrodynver |
Wrong DYN version |
-820 |
335544467 |
high_minor |
Minor version too high found @1 expected @2 |
-820 |
335544881 |
need_difference |
Difference file name should be set explicitly for database on raw device |
-823 |
335544473 |
invalid_bookmark |
Invalid bookmark handle |
-824 |
335544474 |
bad_lock_level |
Invalid lock level @1 |
-825 |
335544519 |
bad_lock_handle |
Invalid lock handle |
-826 |
335544585 |
dsql_stmt_handle |
Invalid statement handle |
-827 |
335544655 |
invalid_direction |
Invalid direction for find operation |
-827 |
335544718 |
invalid_key |
Invalid key for find operation |
-828 |
335544678 |
inval_key_posn |
Invalid key position |
-829 |
336068816 |
dyn_char_fld_too_small |
New size specified for column @1 must be at least @2 characters |
-829 |
336068817 |
dyn_invalid_dtype_conversion |
Cannot change datatype for @1.Conversion from base type @2 to @3 is not supported |
-829 |
336068818 |
dyn_dtype_conv_invalid |
Cannot change datatype for column @1 from a character type to a non-character type |
-829 |
336068829 |
max_coll_per_charset |
Maximum number of collations per character set exceeded |
-829 |
336068830 |
invalid_coll_attr |
Invalid collation attributes |
-829 |
336068852 |
dyn_scale_too_big |
New scale specified for column @1 must be at most @2 |
-829 |
336068853 |
dyn_precision_too_small |
New precision specified for column @1 must be at least @2 |
-829 |
335544616 |
field_ref_err |
Invalid column reference |
-830 |
335544615 |
field_aggregate_err |
Column used with aggregate |
-831 |
335544548 |
primary_key_exists |
Attempt to define a second PRIMARY KEY for the same table |
-832 |
335544604 |
key_field_count_err |
FOREIGN KEY column count does not match PRIMARY KEY |
-833 |
335544606 |
expression_eval_err |
Expression evaluation not supported |
-833 |
335544810 |
date_range_exceeded |
Value exceeds the range for valid dates |
-834 |
335544508 |
range_not_found |
Refresh range number @1 not found |
-835 |
335544649 |
bad_checksum |
Bad checksum |
-836 |
335544517 |
except |
Exception @1 |
-836 |
335544848 |
except2 |
Exception @1 |
-837 |
335544518 |
cache_restart |
Restart shared cache manager |
-838 |
335544560 |
shutwarn |
Database @1 shutdown in @2 seconds |
-841 |
335544677 |
version_err |
Too many versions |
-842 |
335544697 |
precision_err |
Precision must be from 1 to 18 |
-842 |
335544698 |
scale_nogt |
Scale must be between zero and precision |
-842 |
335544699 |
expec_short |
Short integer expected |
-842 |
335544700 |
expec_long |
Long integer expected |
-842 |
335544701 |
expec_ushort |
Unsigned short integer expected |
-842 |
335544712 |
expec_positive |
Positive value expected |
-901 |
335740929 |
gfix_db_name |
Database file name (@1) already given |
-901 |
336330753 |
gbak_unknown_switch |
Found unknown switch |
-901 |
336920577 |
gstat_unknown_switch |
Found unknown switch |
-901 |
336986113 |
fbsvcmgr_bad_am |
Wrong value for access mode |
-901 |
335740930 |
gfix_invalid_sw |
Invalid switch @1 |
-901 |
335544322 |
bad_dbkey |
Invalid database key |
-901 |
336986114 |
fbsvcmgr_bad_wm |
Wrong value for write mode |
-901 |
336330754 |
gbak_page_size_missing |
Page size parameter missing |
-901 |
336920578 |
gstat_retry |
Please retry, giving a database name |
-901 |
336986115 |
fbsvcmgr_bad_rs |
Wrong value for reserve space |
-901 |
336920579 |
gstat_wrong_ods |
Wrong ODS version, expected @1, encountered @2 |
-901 |
336330755 |
gbak_page_size_toobig |
Page size specified (@1) greater than limit (16384 bytes) |
-901 |
335740932 |
gfix_incmp_sw |
Incompatible switch combination |
-901 |
336920580 |
gstat_unexpected_eof |
Unexpected end of database file |
-901 |
336330756 |
gbak_redir_ouput_missing |
Redirect location for output is not specified |
-901 |
336986116 |
fbsvcmgr_info_err |
Unknown tag (@1) in info_svr_db_info block after isc_svc_query() |
-901 |
335740933 |
gfix_replay_req |
Replay log pathname required |
-901 |
336330757 |
gbak_switches_conflict |
Conflicting switches for backup/restore |
-901 |
336986117 |
fbsvcmgr_query_err |
Unknown tag (@1) in isc_svc_query() results |
-901 |
335544326 |
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 |
Device type @1 not known |
-901 |
335544327 |
bad_req_handle |
Invalid request handle |
-901 |
335740935 |
gfix_val_req |
Numeric value required |
-901 |
336330759 |
gbak_no_protection |
Protection is not there yet |
-901 |
335544328 |
bad_segstr_handle |
Invalid BLOB handle |
-901 |
335740936 |
gfix_pval_req |
Positive numeric value required |
-901 |
336330760 |
gbak_page_size_not_allowed |
Page size is allowed only on restore or create |
Table B.2.3 SQLCODE and GDSCODE Error Codes and Message Texts (3)
SQLCODE | GDSCODE | Symbol | Message Text |
---|---|---|---|
-901 |
335544329 |
bad_segstr_id |
Invalid BLOB ID |
-901 |
335740937 |
gfix_trn_req |
Number of transactions per sweep required |
-901 |
336330761 |
gbak_multi_source_dest |
Multiple sources or destinations specified |
-901 |
335544330 |
bad_tpb_content |
Invalid parameter in transaction parameter block |
-901 |
336330762 |
gbak_filename_missing |
Requires both input and output filenames |
-901 |
335544331 |
bad_tpb_form |
Invalid format for transaction parameter block |
-901 |
336330763 |
gbak_dup_inout_names |
Input and output have the same name. Disallowed |
-901 |
335740940 |
gfix_full_req |
«full» or «reserve» required |
-901 |
335544332 |
bad_trans_handle |
Invalid transaction handle (expecting explicit transaction start) |
-901 |
336330764 |
gbak_inv_page_size |
Expected page size, encountered «@1» |
-901 |
335740941 |
gfix_usrname_req |
User name required |
-901 |
336330765 |
gbak_db_specified |
REPLACE specified, but the first file @1 is a database |
-901 |
335740942 |
gfix_pass_req |
Password required |
-901 |
336330766 |
gbak_db_exists |
Database @1 already exists.To replace it, use the -REP switch |
-901 |
335740943 |
gfix_subs_name |
Subsystem name |
-901 |
336723983 |
gsec_cant_open_db |
Unable to open database |
-901 |
336330767 |
gbak_unk_device |
Device type not specified |
-901 |
336723984 |
gsec_switches_error |
Error in switch specifications |
-901 |
335740945 |
gfix_sec_req |
Number of seconds required |
-901 |
335544337 |
excess_trans |
Attempt to start more than @1 transactions |
-901 |
336723985 |
gsec_no_op_spec |
No operation specified |
-901 |
335740946 |
gfix_nval_req |
Numeric value between 0 and 32767 inclusive required |
-901 |
336723986 |
gsec_no_usr_name |
No user name specified |
-901 |
335740947 |
gfix_type_shut |
Must specify type of shutdown |
-901 |
335544339 |
infinap |
Information type inappropriate for object specified |
-901 |
335544340 |
infona |
No information of this type available for object specified |
-901 |
336723987 |
gsec_err_add |
Add record error |
-901 |
336723988 |
gsec_err_modify |
Modify record error |
-901 |
336330772 |
gbak_blob_info_failed |
Gds_$blob_info failed |
-901 |
335740948 |
gfix_retry |
Please retry, specifying an option |
-901 |
335544341 |
infunk |
Unknown information item |
-901 |
336723989 |
gsec_err_find_mod |
Find / modify record error |
-901 |
336330773 |
gbak_unk_blob_item |
Do not understand BLOB INFO item @1 |
-901 |
335544342 |
integ_fail |
Action cancelled by trigger (@1) to preserve data integrity |
-901 |
336330774 |
gbak_get_seg_failed |
Gds_$get_segment failed |
-901 |
336723990 |
gsec_err_rec_not_found |
Record not found for user: @1 |
-901 |
336723991 |
gsec_err_delete |
Delete record error |
-901 |
336330775 |
gbak_close_blob_failed |
Gds_$close_blob failed |
-901 |
335740951 |
gfix_retry_db |
Please retry, giving a database name |
-901 |
336330776 |
gbak_open_blob_failed |
Gds_$open_blob failed |
-901 |
336723992 |
gsec_err_find_del |
Find / delete record error |
-901 |
335544345 |
lock_conflict |
Lock conflict on no wait transaction |
-901 |
336330777 |
gbak_put_blr_gen_id_failed |
Failed in put_blr_gen_id |
-901 |
336330778 |
gbak_unk_type |
Data type @1 not understood |
-901 |
336330779 |
gbak_comp_req_failed |
Gds_$compile_request failed |
-901 |
336330780 |
gbak_start_req_failed |
Gds_$start_request failed |
-901 |
336723996 |
gsec_err_find_disp |
Find / display record error |
-901 |
336330781 |
gbak_rec_failed |
gds_$receive failed |
-901 |
336920605 |
gstat_open_err |
Can’t open database file @1 |
-901 |
336723997 |
gsec_inv_param |
Invalid parameter, no switch defined |
-901 |
335544350 |
no_finish |
Program attempted to exit without finishing database |
-901 |
336920606 |
gstat_read_err |
Can’t read a database page |
-901 |
336330782 |
gbak_rel_req_failed |
Gds_$release_request failed |
-901 |
336723998 |
gsec_op_specified |
Operation already specified |
-901 |
336920607 |
gstat_sysmemex |
System memory exhausted |
-901 |
336330783 |
gbak_db_info_failed |
gds_$database_info failed |
-901 |
336723999 |
gsec_pw_specified |
Password already specified |
-901 |
336724000 |
gsec_uid_specified |
Uid already specified |
-901 |
336330784 |
gbak_no_db_desc |
Expected database description record |
-901 |
335544353 |
no_recon |
Transaction is not in limbo |
-901 |
336724001 |
gsec_gid_specified |
Gid already specified |
-901 |
336330785 |
gbak_db_create_failed |
Failed to create database @1 |
-901 |
336724002 |
gsec_proj_specified |
Project already specified |
-901 |
336330786 |
gbak_decomp_len_error |
RESTORE: decompression length error |
-901 |
335544355 |
no_segstr_close |
BLOB was not closed |
-901 |
336330787 |
gbak_tbl_missing |
Cannot find table @1 |
-901 |
336724003 |
gsec_org_specified |
Organization already specified |
-901 |
336330788 |
gbak_blob_col_missing |
Cannot find column for BLOB |
-901 |
336724004 |
gsec_fname_specified |
First name already specified |
-901 |
335544357 |
open_trans |
Cannot disconnect database with open transactions (@1 active) |
-901 |
336330789 |
gbak_create_blob_failed |
Gds_$create_blob failed |
-901 |
336724005 |
gsec_mname_specified |
Middle name already specified |
-901 |
335544358 |
port_len |
Message length error ( encountered @1, expected @2) |
-901 |
336330790 |
gbak_put_seg_failed |
Gds_$put_segment failed |
-901 |
336724006 |
gsec_lname_specified |
Last name already specified |
-901 |
336330791 |
gbak_rec_len_exp |
Expected record length |
-901 |
336724008 |
gsec_inv_switch |
Invalid switch specified |
-901 |
336330792 |
gbak_inv_rec_len |
Wrong length record, expected @1 encountered @2 |
-901 |
336330793 |
gbak_exp_data_type |
Expected data attribute |
-901 |
336724009 |
gsec_amb_switch |
Ambiguous switch specified |
-901 |
336330794 |
gbak_gen_id_failed |
Failed in store_blr_gen_id |
-901 |
336724010 |
gsec_no_op_specified |
No operation specified for parameters |
-901 |
335544363 |
req_no_trans |
No transaction for request |
-901 |
336330795 |
gbak_unk_rec_type |
Do not recognize record type @1 |
-901 |
336724011 |
gsec_params_not_allowed |
No parameters allowed for this operation |
-901 |
335544364 |
req_sync |
Request synchronization error |
-901 |
336724012 |
gsec_incompat_switch |
Incompatible switches specified |
-901 |
336330796 |
gbak_inv_bkup_ver |
Expected backup version 1..8. Found @1 |
-901 |
335544365 |
req_wrong_db |
Request referenced an unavailable database |
-901 |
336330797 |
gbak_missing_bkup_desc |
Expected backup description record |
-901 |
336330798 |
gbak_string_trunc |
String truncated |
-901 |
336330799 |
gbak_cant_rest_record |
warning — record could not be restored |
-901 |
336330800 |
gbak_send_failed |
Gds_$send failed |
-901 |
335544369 |
segstr_no_read |
Attempted read of a new, open BLOB |
-901 |
336330801 |
gbak_no_tbl_name |
No table name for data |
-901 |
335544370 |
segstr_no_trans |
Attempted action on blob outside transaction |
-901 |
336330802 |
gbak_unexp_eof |
Unexpected end of file on backup file |
-901 |
336330803 |
gbak_db_format_too_old |
Database format @1 is too old to restore to |
-901 |
335544372 |
segstr_wrong_db |
Attempted reference to BLOB in unavailable database |
-901 |
336330804 |
gbak_inv_array_dim |
Array dimension for column @1 is invalid |
-901 |
336330807 |
gbak_xdr_len_expected |
Expected XDR record length |
-901 |
335544376 |
unres_rel |
Table @1 was omitted from the transaction reserving list |
-901 |
335544377 |
uns_ext |
Request includes a DSRI extension not supported in this implementation |
-901 |
335544378 |
wish_list |
Feature is not supported |
-901 |
335544382 |
random |
@1 |
-901 |
335544383 |
fatal_conflict |
Unrecoverable conflict with limbo transaction @1 |
-901 |
335740991 |
gfix_exceed_max |
Internal block exceeds maximum size |
-901 |
335740992 |
gfix_corrupt_pool |
Corrupt pool |
-901 |
335740993 |
gfix_mem_exhausted |
Virtual memory exhausted |
-901 |
336330817 |
gbak_open_bkup_error |
Cannot open backup file @1 |
-901 |
335740994 |
gfix_bad_pool |
Bad pool id. |
-901 |
336330818 |
gbak_open_error |
Cannot open status and error output file @1 |
-901 |
335740995 |
gfix_trn_not_valid |
Transaction state @1 not in valid range |
-901 |
335544392 |
bdbincon |
Internal error |
-901 |
336724044 |
gsec_inv_username |
Invalid user name (maximum 31 bytes allowed) |
-901 |
336724045 |
gsec_inv_pw_length |
Warning — maximum 8 significant bytes of password used |
-901 |
336724046 |
gsec_db_specified |
Database already specified |
-901 |
336724047 |
gsec_db_admin_specified |
Database administrator name already specified |
-901 |
336724048 |
gsec_db_admin_pw_specified |
Database administrator password already specified |
-901 |
336724049 |
gsec_sql_role_specified |
SQL role name already specified |
-901 |
335741012 |
gfix_unexp_eoi |
Unexpected end of input |
-901 |
335544407 |
dbbnotzer |
Database handle not zero |
-901 |
335544408 |
tranotzer |
Transaction handle not zero |
-901 |
335741018 |
gfix_recon_fail |
Failed to reconnect to a transaction in database @1 |
-901 |
335544418 |
trainlim |
Transaction in limbo |
-901 |
335544419 |
notinlim |
Transaction not in limbo |
-901 |
335544420 |
traoutsta |
Transaction outstanding |
-901 |
335544428 |
badmsgnum |
Undefined message number |
-901 |
335741036 |
gfix_trn_unknown |
Transaction description item unknown |
-901 |
335741038 |
gfix_mode_req |
«read_only» or «read_write» required |
-901 |
335544431 |
blocking_signal |
Blocking signal has been received |
-901 |
335741042 |
gfix_pzval_req |
Positive or zero numeric value required |
-901 |
335544442 |
noargacc_read |
Database system cannot read argument @1 |
-901 |
335544443 |
noargacc_write |
Database system cannot write argument @1 |
-901 |
335544450 |
misc_interpreted |
@1 |
-901 |
335544468 |
tra_state |
Transaction @1 is @2 |
-901 |
335544485 |
bad_stmt_handle |
Invalid statement handle |
-901 |
336330934 |
gbak_missing_block_fac |
Blocking factor parameter missing |
-901 |
336330935 |
gbak_inv_block_fac |
Expected blocking factor, encountered «@1» |
-901 |
336330936 |
gbak_block_fac_specified |
A blocking factor may not be used in conjunction with device CT |
-901 |
336068796 |
dyn_role_does_not_exist |
SQL role @1 does not exist |
-901 |
336330940 |
gbak_missing_username |
User name parameter missing |
-901 |
336330941 |
gbak_missing_password |
Password parameter missing |
-901 |
336068797 |
dyn_no_grant_admin_opt |
User @1 has no grant admin option on SQL role @2 |
-901 |
335544510 |
lock_timeout |
Lock time-out on wait transaction |
-901 |
336068798 |
dyn_user_not_role_member |
User @1 is not a member of SQL role @2 |
-901 |
336068799 |
dyn_delete_role_failed |
@1 is not the owner of SQL role @2 |
-901 |
336068800 |
dyn_grant_role_to_user |
@1 is a SQL role and not a user |
-901 |
336068801 |
dyn_inv_sql_role_name |
User name @1 could not be used for SQL role |
-901 |
336068802 |
dyn_dup_sql_role |
SQL role @1 already exists |
-901 |
336068803 |
dyn_kywd_spec_for_role |
Keyword @1 can not be used as a SQL role name |
-901 |
336068804 |
dyn_roles_not_supported |
SQL roles are not supported in on older versions of the database. A backup and restore of the database is required |
-901 |
336330952 |
gbak_missing_skipped_bytes |
missing parameter for the number of bytes to be skipped |
-901 |
336330953 |
gbak_inv_skipped_bytes |
Expected number of bytes to be skipped, encountered «@1» |
-901 |
336068820 |
dyn_zero_len_id |
Zero length identifiers are not allowed |
-901 |
336330965 |
gbak_err_restore_charset |
Character set |
-901 |
336330967 |
gbak_err_restore_collation |
Collation |
-901 |
336330972 |
gbak_read_error |
Unexpected I/O error while reading from backup file |
-901 |
336330973 |
gbak_write_error |
Unexpected I/O error while writing to backup file |
-901 |
336068840 |
dyn_wrong_gtt_scope |
@1 cannot reference @2 |
-901 |
336330985 |
gbak_db_in_use |
Could not drop database @1 (database might be in use) |
-901 |
336330990 |
gbak_sysmemex |
System memory exhausted |
-901 |
335544559 |
bad_svc_handle |
Invalid service handle |
-901 |
335544561 |
wrospbver |
Wrong version of service parameter block |
-901 |
335544562 |
bad_spb_form |
Unrecognized service parameter block |
-901 |
335544563 |
svcnotdef |
Service @1 is not defined |
-901 |
336068856 |
dyn_ods_not_supp_feature |
Feature ‘@1’ is not supported in ODS @[email protected] |
-901 |
336331002 |
gbak_restore_role_failed |
SQL role |
-901 |
336331005 |
gbak_role_op_missing |
SQL role parameter missing |
-901 |
336331010 |
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 only on restore or create |
-901 |
336331014 |
gbak_inv_size |
Size specification either missing or incorrect for file @1 |
-901 |
336331015 |
gbak_file_outof_sequence |
File @1 out of sequence |
-901 |
336331016 |
gbak_join_file_missing |
Can’t join — one of the files missing |
-901 |
336331017 |
gbak_stdin_not_supptd |
standard input is not supported when using join operation |
-901 |
336331018 |
gbak_stdout_not_supptd |
Standard output is not supported when using split operation |
-901 |
336331019 |
gbak_bkup_corrupt |
Backup file @1 might be corrupt |
-901 |
336331020 |
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 |
File size given (@1) is less than minimum allowed (@2) |
-901 |
336331025 |
gbak_svc_name_missing |
Service name parameter missing |
-901 |
336331026 |
gbak_not_ownr |
Cannot restore over current database, must be SYSDBA or owner of the existing database |
-901 |
336331031 |
gbak_mode_req |
«read_only» or «read_write» required |
-901 |
336331033 |
gbak_just_data |
Just data ignore all constraints etc. |
-901 |
336331034 |
gbak_data_only |
Restoring data only ignoring foreign key, unique, not null & other constraints |
-901 |
335544609 |
index_name |
INDEX @1 |
-901 |
335544610 |
exception_name |
EXCEPTION @1 |
-901 |
335544611 |
field_name |
COLUMN @1 |
-901 |
335544613 |
union_err |
Union not supported |
Table B.2.4 SQLCODE and GDSCODE Error Codes and Message Texts (4)
SQLCODE | GDSCODE | Symbol | Message Text |
---|---|---|---|
-901 |
335544614 |
dsql_construct_err |
Unsupported DSQL construct |
-901 |
335544623 |
dsql_domain_err |
Illegal use of keyword VALUE |
-901 |
335544626 |
table_name |
TABLE @1 |
-901 |
335544627 |
proc_name |
PROCEDURE @1 |
-901 |
335544641 |
dsql_domain_not_found |
Specified domain or source column @1 does not exist |
-901 |
335544656 |
dsql_var_conflict |
Variable @1 conflicts with parameter in same procedure |
-901 |
335544666 |
srvr_version_too_old |
Server version too old to support all CREATE DATABASE options |
-901 |
335544673 |
no_delete |
Cannot delete |
-901 |
335544675 |
sort_err |
Sort error |
-901 |
335544703 |
svcnoexe |
Service @1 does not have an associated executable |
-901 |
335544704 |
net_lookup_err |
Failed to locate host machine |
-901 |
335544705 |
service_unknown |
Undefined service @1/@2 |
-901 |
335544706 |
host_unknown |
The specified name was not found in the hosts file or Domain Name Services |
-901 |
335544711 |
unprepared_stmt |
Attempt to execute an unprepared dynamic SQL statement |
-901 |
335544716 |
svc_in_use |
Service is currently busy: @1 |
-901 |
335544731 |
tra_must_sweep |
[no associated message] |
-901 |
335544740 |
udf_exception |
A fatal exception occurred during the execution of a user defined function |
-901 |
335544741 |
lost_db_connection |
Connection lost to database |
-901 |
335544742 |
no_write_user_priv |
User cannot write to RDB$USER_PRIVILEGES |
-901 |
335544767 |
blob_filter_exception |
A fatal exception occurred during the execution of a blob filter |
-901 |
335544768 |
exception_access_violation |
Access violation.The code attempted to access a virtual address without privilege to do so |
-901 |
335544769 |
exception_datatype_missalignment |
Datatype misalignment. The attempted to read or write a value that was not stored on a memory boundary |
-901 |
335544770 |
exception_array_bounds_exceeded |
Array bounds exceeded. The code attempted to access an array element that is out of bounds. |
-901 |
335544771 |
exception_float_denormal_ operand |
Float denormal operand. One of the floating-point operands is too small to represent a standard float value. |
-901 |
335544772 |
exception_float_divide_by_zero |
Floating-point divide by zero. The code attempted to divide a floating-point value by zero. |
-901 |
335544773 |
exception_float_inexact_result |
Floating-point inexact result. The result of a floating-point operation cannot be represented as a decimal fraction |
-901 |
335544774 |
exception _float_invalid_operand |
Floating-point invalid operand. An indeterminant error occurred during a floating-point operation |
-901 |
335544775 |
exception_float_overflow |
Floating-point overflow. The exponent of a floating-point operation is greater than the magnitude allowed |
-901 |
335544776 |
exception_float_stack_check |
Floating-point stack check. The stack overflowed or underflowed as the result of a floating-point operation |
-901 |
335544777 |
exception_float_underflow |
Floating-point underflow. The exponent of a floating-point operation is less than the magnitude allowed |
-901 |
335544778 |
exception_integer_divide_by_zero |
Integer divide by zero. The code attempted to divide an integer value by an integer divisor of zero |
-901 |
335544779 |
exception_integer_overflow |
Integer overflow. The result of an integer operation caused the most significant bit of the result to carry |
-901 |
335544780 |
exception_unknown |
An exception occurred that does not have a description.Exception number @1 |
-901 |
335544781 |
exception_stack_overflow |
Stack overflow. The resource requirements of the runtime stack have exceeded the memory available to it |
-901 |
335544782 |
exception_sigsegv |
Segmentation Fault. The code attempted to access memory without privileges |
-901 |
335544783 |
exception_sigill |
Illegal Instruction. The Code attempted to perfrom an illegal operation |
-901 |
335544784 |
exception_sigbus |
Bus Error. The Code caused a system bus error |
-901 |
335544785 |
exception_sigfpe |
Floating Point Error. The Code caused an Arithmetic Exception or a floating point exception |
-901 |
335544786 |
ext_file_delete |
Cannot delete rows from external files |
-901 |
335544787 |
ext_file_modify |
Cannot update rows in external files |
-901 |
335544788 |
adm_task_denied |
Unable to perform operation. You must be either SYSDBA or owner of the database |
-901 |
335544794 |
cancelled |
Operation was cancelled |
-901 |
335544797 |
svcnouser |
User name and password are required while attaching to the services manager |
-901 |
335544801 |
datype_notsup |
Data type not supported for arithmetic |
-901 |
335544803 |
dialect_not_changed |
Database dialect not changed |
-901 |
335544804 |
database_create_failed |
Unable to create database @1 |
-901 |
335544805 |
inv_dialect_specified |
Database dialect @1 is not a valid dialect |
-901 |
335544806 |
valid_db_dialects |
Valid database dialects are @1 |
-901 |
335544811 |
inv_client_dialect_specified |
Passed client dialect @1 is not a valid dialect |
-901 |
335544812 |
valid_client_dialects |
Valid client dialects are @1 |
-901 |
335544814 |
service_not_supported |
Services functionality will be supported in a later version of the product |
-901 |
335544820 |
invalid_savepoint |
Unable to find savepoint with name @1 in transaction context |
-901 |
335544835 |
bad_shutdown_mode |
Target shutdown mode is invalid for database «@1» |
-901 |
335544840 |
no_update |
Cannot update |
-901 |
335544842 |
stack_trace |
@1 |
-901 |
335544843 |
ctx_var_not_found |
Context variable @1 is not found in namespace @2 |
-901 |
335544844 |
ctx_namespace_invalid |
Invalid namespace name @1 passed to @2 |
-901 |
335544845 |
ctx_too_big |
Too many context variables |
-901 |
335544846 |
ctx_bad_argument |
Invalid argument passed to @1 |
-901 |
335544847 |
identifier_too_long |
BLR syntax error. Identifier @1… is too long |
-901 |
335544859 |
invalid_time_precision |
Time precision exceeds allowed range ([email protected]) |
-901 |
335544866 |
met_wrong_gtt_scope |
@1 cannot depend on @2 |
-901 |
335544868 |
illegal_prc_type |
Procedure @1 is not selectable (it does not contain a SUSPEND statement) |
-901 |
335544869 |
invalid_sort_datatype |
Datatype @1 is not supported for sorting operation |
-901 |
335544870 |
collation_name |
COLLATION @1 |
-901 |
335544871 |
domain_name |
DOMAIN @1 |
-901 |
335544874 |
max_db_per_trans_allowed |
A multi database transaction cannot span more than @1 databases |
-901 |
335544876 |
bad_proc_BLR |
Error while parsing procedure @1′ s BLR |
-901 |
335544877 |
key_too_big |
Index key too big |
-901 |
336397211 |
dsql_too_many_values |
Too many values (more than @1) in member list to match against |
-901 |
336397236 |
dsql_unsupp_feature_dialect |
Feature is not supported in dialect @1 |
-902 |
335544333 |
bug_check |
Internal gds software consistency check (@1) |
-902 |
335544335 |
db_corrupt |
Database file appears corrupt (@1) |
-902 |
335544344 |
io_error |
I/O error for file «@2» |
-902 |
335544346 |
metadata_corrupt |
Corrupt system table |
-902 |
335544373 |
sys_request |
Operating system directive @1 failed |
-902 |
335544384 |
badblk |
Internal error |
-902 |
335544385 |
invpoolcl |
Internal error |
-902 |
335544387 |
relbadblk |
Internal error |
-902 |
335544388 |
blktoobig |
Block size exceeds implementation restriction |
-902 |
335544394 |
badodsver |
Incompatible version of on-disk structure |
-902 |
335544397 |
dirtypage |
Internal error |
-902 |
335544398 |
waifortra |
Internal error |
-902 |
335544399 |
doubleloc |
Internal error |
-902 |
335544400 |
nodnotfnd |
Internal error |
-902 |
335544401 |
dupnodfnd |
Internal error |
-902 |
335544402 |
locnotmar |
Internal error |
-902 |
335544404 |
corrupt |
Database corrupted |
-902 |
335544405 |
badpage |
Checksum error on database page @1 |
-902 |
335544406 |
badindex |
Index is broken |
-902 |
335544409 |
trareqmis |
Transaction — request mismatch ( synchronization error ) |
-902 |
335544410 |
badhndcnt |
Bad handle count |
-902 |
335544411 |
wrotpbver |
Wrong version of transaction parameter block |
-902 |
335544412 |
wroblrver |
Unsupported BLR version (expected @1, encountered @2) |
-902 |
335544413 |
wrodpbver |
Wrong version of database parameter block |
-902 |
335544415 |
badrelation |
Database corrupted |
-902 |
335544416 |
nodetach |
Internal error |
-902 |
335544417 |
notremote |
Internal error |
-902 |
335544422 |
dbfile |
Internal error |
-902 |
335544423 |
orphan |
Internal error |
-902 |
335544432 |
lockmanerr |
Lock manager error |
-902 |
335544436 |
sqlerr |
SQL error code = @1 |
-902 |
335544448 |
bad_sec_info |
[no associated message] |
-902 |
335544449 |
invalid_sec_info |
[no associated message] |
-902 |
335544470 |
buf_invalid |
Cache buffer for page @1 invalid |
-902 |
335544471 |
indexnotdefined |
There is no index in table @1 with id @2 |
-902 |
335544472 |
login |
Your user name and password are not defined. Ask your database administrator to set up a Firebird login |
-902 |
335544506 |
shutinprog |
Database @1 shutdown in progress |
-902 |
335544528 |
shutdown |
Database @1 shutdown |
-902 |
335544557 |
shutfail |
Database shutdown unsuccessful |
-902 |
335544569 |
dsql_error |
Dynamic SQL Error |
-902 |
335544653 |
psw_attach |
Cannot attach to password database |
-902 |
335544654 |
psw_start_trans |
Cannot start transaction for password database |
-902 |
335544717 |
err_stack_limit |
Stack size insufficent to execute current request |
-902 |
335544721 |
network_error |
Unable to complete network request to host «@1» |
-902 |
335544722 |
net_connect_err |
Failed to establish a connection |
-902 |
335544723 |
net_connect_listen_err |
Error while listening for an incoming connection |
-902 |
335544724 |
net_event_connect_err |
Failed to establish a secondary connection for event processing |
-902 |
335544725 |
net_event_listen_err |
Error while listening for an incoming event connection request |
-902 |
335544726 |
net_read_err |
Error reading data from the connection |
-902 |
335544727 |
net_write_err |
Error writing data to the connection |
-902 |
335544732 |
unsupported_network_drive |
Access to databases on file servers is not supported |
-902 |
335544733 |
io_create_err |
Error while trying to create file |
-902 |
335544734 |
io_open_err |
Error while trying to open file |
-902 |
335544735 |
io_close_err |
Error while trying to close file |
-902 |
335544736 |
io_read_err |
Error while trying to read from file |
-902 |
335544737 |
io_write_err |
Error while trying to write to file |
-902 |
335544738 |
io_delete_err |
Error while trying to delete file |
-902 |
335544739 |
io_access_err |
Error while trying to access file |
-902 |
335544745 |
login_same_as_role_name |
Your login @1 is same as one of the SQL role name. Ask your database administrator to set up a valid Firebird login. |
-902 |
335544791 |
file_in_use |
The file @1 is currently in use by another process.Try again later |
-902 |
335544795 |
unexp_spb_form |
Unexpected item in service parameter block, expected @1 |
-902 |
335544809 |
extern_func_dir_error |
Function @1 is in @2, which is not in a permitted directory for external functions |
-902 |
335544819 |
io_32bit_exceeded_err |
File exceeded maximum size of 2GB. Add another database file or use a 64 bit I/O version of Firebird |
-902 |
335544831 |
conf_access_denied |
Access to @1 «@2» is denied by server administrator |
-902 |
335544834 |
cursor_not_open |
Cursor is not open |
-902 |
335544841 |
cursor_already_open |
Cursor is already open |
-902 |
335544856 |
att_shutdown |
Connection shutdown |
-902 |
335544882 |
long_login |
Login name too long (@1 characters, maximum allowed @2) |
-904 |
335544324 |
bad_db_handle |
Invalid database handle (no active connection) |
-904 |
335544375 |
unavailable |
Unavailable database |
-904 |
335544381 |
imp_exc |
Implementation limit exceeded |
-904 |
335544386 |
nopoolids |
Too many requests |
-904 |
335544389 |
bufexh |
Buffer exhausted |
-904 |
335544391 |
bufinuse |
Buffer in use |
-904 |
335544393 |
reqinuse |
Request in use |
-904 |
335544424 |
no_lock_mgr |
No lock manager available |
-904 |
335544430 |
virmemexh |
Unable to allocate memory from operating system |
-904 |
335544451 |
update_conflict |
Update conflicts with concurrent update |
-904 |
335544453 |
obj_in_use |
Object @1 is in use |
-904 |
335544455 |
shadow_accessed |
Cannot attach active shadow file |
-904 |
335544460 |
shadow_missing |
A file in manual shadow @1 is unavailable |
-904 |
335544661 |
index_root_page_full |
Cannot add index, index root page is full |
-904 |
335544676 |
sort_mem_err |
Sort error: not enough memory |
-904 |
335544683 |
req_depth_exceeded |
Request depth exceeded. (Recursive definition?) |
-904 |
335544758 |
sort_rec_size_err |
Sort record size of @1 bytes is too big ???? |
-904 |
335544761 |
too_many_handles |
Too many open handles to database |
-904 |
335544792 |
service_att_err |
Cannot attach to services manager |
-904 |
335544799 |
svc_name_missing |
The service name was not specified |
-904 |
335544813 |
optimizer_between_err |
Unsupported field type specified in BETWEEN predicate |
-904 |
335544827 |
exec_sql_invalid_arg |
Invalid argument in EXECUTE STATEMENT-cannot convert to string |
-904 |
335544828 |
exec_sql_invalid_req |
Wrong request type in EXECUTE STATEMENT ‘@1’ |
-904 |
335544829 |
exec_sql_invalid_var |
Variable type (position @1) in EXECUTE STATEMENT ‘@2’ INTO does not match returned column type |
-904 |
335544830 |
exec_sql_max_call_exceeded |
Too many recursion levels of EXECUTE STATEMENT |
-904 |
335544832 |
wrong_backup_state |
Cannot change difference file name while database is in backup mode |
-904 |
335544852 |
partner_idx_incompat_type |
Partner index segment no @1 has incompatible data type |
-904 |
335544857 |
blobtoobig |
Maximum BLOB size exceeded |
-904 |
335544862 |
record_lock_not_supp |
Stream does not support record locking |
-904 |
335544863 |
partner_idx_not_found |
Cannot create foreign key constraint @1. Partner index does not exist or is inactive |
-904 |
335544864 |
tra_num_exc |
Transactions count exceeded. Perform backup and restore to make database operable again |
-904 |
335544865 |
field_disappeared |
Column has been unexpectedly deleted |
-904 |
335544878 |
concurrent_transaction |
Concurrent transaction number is @1 |
-906 |
335544744 |
max_att_exceeded |
Maximum user count exceeded.Contact your database administrator |
-909 |
335544667 |
drdb_completed_with_errs |
Drop database completed with errors |
-911 |
335544459 |
rec_in_limbo |
Record from transaction @1 is stuck in limbo |
-913 |
335544336 |
deadlock |
Deadlock |
-922 |
335544323 |
bad_db_format |
File @1 is not a valid database |
-923 |
335544421 |
connect_reject |
Connection rejected by remote interface |
-923 |
335544461 |
cant_validate |
Secondary server attachments cannot validate databases |
-923 |
335544464 |
cant_start_logging |
Secondary server attachments cannot start logging |
-924 |
335544325 |
bad_dpb_content |
Bad parameters on attach or create database |
-924 |
335544441 |
bad_detach |
Database detach completed with errors |
-924 |
335544648 |
conn_lost |
Connection lost to pipe server |
-926 |
335544447 |
no_rollback |
No rollback performed |
-999 |
335544689 |
ib_error |
Firebird error |
Содержание
- Error SQLCODE -904 in firebird after installation
- 2 Answers 2
- Related
- Hot Network Questions
- Subscribe to RSS
- The database ‘xxx’ cannot be opened because it is version 904
- 2 Answers 2
- Error Code: 904, SQL State: 42000] ORA-00904: «G».»NAME»: invalid
- Best Answer
- ORA-00904: invalid identifier
- 13 Answers 13
- What is sql error 904
Error SQLCODE -904 in firebird after installation
I installed firebird database for the first time in my life (version 1.5.6 on Windows 7), after installation I can not connect to the sample database (employee.fdb exists), or create a database. This gives the following error in ISQL Tool:
2 Answers 2
Firebird 1.5 was written (long) before Windows 7, and before things like UAC existed. It may simply be that Firebird 1.5 doesn’t work correctly with Windows 7, or that it requires additional effort to work. I’d suggest to install Firebird 2.5.2 (update 1) as that is the latest version and is known to work with Windows 7.
Another problem might be that local system connections don’t work as I seem to remember that Firebird 1.5 uses an older local protocol which doesn’t work on newer Windows versions. This protocol was replaced in Firebird 2.0. To workaround that you need to include the hostname in the CREATE DATABASE or CONNECT statement, so for example:
Windows 7+ breaks the local api protocol. You have to use Tcpip protocol to connect to the database, even for local connections.
Hot Network Questions
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.1.14.43159
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
Источник
The database ‘xxx’ cannot be opened because it is version 904
I can’t attach my database. When I try to attach a database in SQL Server Management Studio, I get this error:
The database ‘C:FILESACCOUNTING.MDF’ cannot be opened because it is version 904. This server supports version 852 and earlier. A downgrade path is not supported. Could not open new database ‘C:FILESACCOUNTING.MDF’. CREATE DATABASE is aborted. (.Net SqlClient Data Provider)
and I have tried these commands:
but it still has an error
2 Answers 2
You CANNOT do this — you cannot attach/detach or backup/restore a database from a newer version of SQL Server (v904 = SQL Server 2019) down to an older version (v852 which is SQL Server 2016) — the internal file structures are just too different to support backwards compatibility.
You can either get around this problem by
using the same version of SQL Server on all your machines — then you can easily backup/restore databases between instances
otherwise you can create the database scripts for both structure (tables, view, stored procedures etc.) and for contents (the actual data contained in the tables) either in SQL Server Management Studio ( Tasks > Generate Scripts ) or using a third-party tool
or you can use a third-party tool like Red-Gate’s SQL Compare and SQL Data Compare to do «diffing» between your source and target, generate update scripts from those differences, and then execute those scripts on the target platform; this works across different SQL Server versions.
The error message in the problem statement occurs because the SQL Server database files (*.mdf, *.ndf and *.ldf) and backups are not backward compatible. Backward compatibility is why we cannot restore or attach a database created from a higher version of SQL Server to a lower version of SQL Server. However, there are a few options that can help us to downgrade the database from a higher version of SQL Server to a lower version SQL Server. These options include:
Use the Generate Scripts Wizard in SQL Server Management Studio Use SQL Server Integration Services Create Custom Scripting and BCP In this tip we will use the Generate Scripts Wizard in SQL Server Management Studio.
Here are the basic steps we need to follow:
Script the database schema and data from the higher version of SQL Server by using the Generate Scripts Wizard in SSMS. Connect to the lower version of SQL Server, and run the SQL scripts that were generated in the previous step, to create the database schema and data. In the next section, I will demonstrate the steps for downgrading a SQL Server 2012 database to SQL Server 2008 R2 database.
Steps to Downgrade a SQL Server Database Using SSMS Generate Scripts Wizard
Step 1 Script the schema of the OUTLANDER database on the SQL Server 2012 instance (IITCUKDEV01) using the Generate Scripts wizard in SSMS.
In Object Explorer connect to IITCUKDEV01, right-click on the OUTLANDER database, expand Tasks and choose «Generate Scripts. «.
This launches Generate and Publish Scripts wizard. Click Next, to skip the Introduction screen and proceed to the Choose Objects page.
On the Choose Objects page, choose option «Script entire database and all database objects», and then click Next to proceed to «Set Scripting Options» page.
n the Advanced Scripting Options dialog box,
set Script for Server Version to SQL Server 2008 R2 (or whatever version you want) under the Table/View Options, set Script Triggers, Script Indexes and Script Primary Keys to True and set Types of data to script to Schema and Data — this last option is key because this is what generates the data per table.
Once done, click OK, to close the Advanced Scripting Options dialog box and return to Set Scripting Options page. In Set Scripting Options page, click Next to continue to Summary page.
After reviewing your selections on Summary page, click Next to generate scripts.
Once scripts are generated successfully, choose the Finish button to close the Generate and Publish Scripts wizard.
Step 2 Connect to the SQL Server 2008 R2 instance (IITCUKSQLSERVER2008), and then run the SQL scripts that were generated in Step 1, to create the OUTLANDER database schema and data.
In Object Explorer connect to IITCUKSQLServer2008, then in SQL Server Management Studio, open the SQL Server script you saved in Step 1
Modify the script, to specify the correct location for the OUTLANDER database data and log files. Once done, run the script to create the OUTLANDER database on IITCUKSQLServer2008 instance.
Upon successful execution, refresh the Database folder in Object Explorer. As you can see in the following image, the OUTLANDER database has been successfully downgraded.
Notes There are a few things to be aware of when using this approach.
This solution creates one large SQL file that has the scripts to create the database objects and also INSERT statements for the data in the tables. For a large databases, the SQL file can get very large if you script out both the schema and the data and could be hard to load into an editor. Also, you may get a memory related error message from the editor if the file is too big. For large databases, around 1GB or more, if this approach does not work, then you should look at using SSIS to migrate the database or create custom scripts to script out the objects and BCP out the data for each of the tables. You can use this Generate Scripts wizard to just generate the schema without the data and use SSIS or BCP to export and import the data. This approach works for SQL Server 2017 to SQL Server 2005. Some of the scripting options might be a bit different in newer versions, but the process is still the same. Before just executing the script, you should review the script to make sure everything looks correct such as the path of the database files, database options, etc. Also if you are using new functionality that does not exist in the lower version, SQL Server won’t be able to create the objects and you will need to review the scripts that were generated and update the code accordingly. For a very simple database this approach should work pretty easliy, but you might need to spend some time making some modifications to the script for a more complex database. Below is a list of all of the scripting options. If you click on an item, the bottom part of the screen gives you a short definition of the option.
Next Steps To avoid this issue, always make sure that you perform a full backup of the database before you upgrade the SQL Server and database to a higher version of SQL Server. In addition, be sure to thoroughly test the application prior to releasing the application to the users. Consider this downgrade option as your last option to rollback from an upgrade because the time and storage needed can be very large. With a very large database be sure you have sufficient storage to support the data needs. Be sure to verify row and object counts as well as test your application before releasing to production.
Источник
Error Code: 904, SQL State: 42000] ORA-00904: «G».»NAME»: invalid
When I run the SQL below, I receive the following:
08:00:08 [SELECT — 0 row(s), 0.000 secs] [Error Code: 904, SQL State: 42000] ORA-00904: «G».»NAME»: invalid identifier
When I comment out the BOLD lines, it runs okay. I’ve tried fully qualifying the column with no success. I’m sure it’s a formatting issue.
Select
sr.schoolid,
sr.studentid, sr.coursenumber,
sr.REGISTREQ_ID,
(select
min(rr.ID||’-‘||rr.COURSEGROUP)
from
REGISTREQ rr
where
rr.grade_level = (select s.sched_nextyeargrade from students s where sr.studentid = s.id)
and rr.yearid = 2100
and rr.id not in (6426,6415)
and rr.COURSEGROUP in
(select
g.name
from
gen g
where
g.CAT = ‘coursegroups’
and instr(g.valuet, sr.coursenumber) > 0
and g.schoolid = sr.schoolid)
and ((g.name like ‘%ALT%’ and sr.GLOBALALTERNATECOURSE=1)
or (g.name not like ‘%ALT%’ and sr.GLOBALALTERNATECOURSE=0))
) as New_RegID
from
SCHEDULEREQUESTS sr
where
sr.schoolid = 703
and sr.yearid = 2100
Best Answer
That’s because the lines you’ve highligted are out of scope for the «g» alias which is part of the inner query.
You perhaps just want «name» without the «g.» prefix.
Источник
ORA-00904: invalid identifier
I tried to write the following inner join query using an Oracle database:
That gives the below error:
The DDL of one table is:
13 Answers 13
Your problem is those pernicious double quotes.
Oracle SQL allows us to ignore the case of database object names provided we either create them with names all in upper case, or without using double quotes. If we use mixed case or lower case in the script and wrapped the identifiers in double quotes we are condemned to using double quotes and the precise case whenever we refer to the object or its attributes:
tl;dr
don’t use double quotes in DDL scripts
(I know most third party code generators do, but they are disciplined enough to put all their object names in UPPER CASE.)
The reverse is also true. If we create the table without using double-quotes …
… we can reference it and its columns in whatever case takes our fancy:
In my case, this error occurred, due to lack of existence of column name in the table.
When i executed » describe tablename » , i was not able to find the column specified in the mapping hbm file.
After altering the table, it worked fine.
FYI, in this case the cause was found to be mixed case column name in the DDL for table creation.
However, if you are mixing «old style» and ANSI joins you could get the same error message even when the DDL was done properly with uppercase table name. This happened to me, and google sent me to this stackoverflow page so I thought I’d share since I was here.
The two SQL statements above are equivalent and produce no error.
When you try to mix them you can get lucky, or you can get an Oracle has a ORA-00904 error.
And the unhelpful error message that doesn’t really describe the problem at all:
I was able to find some research on this in the following blog post:
In my case, I was attempting to manually convert from old style to ANSI style joins, and was doing so incrementally, one table at a time. This appears to have been a bad idea. Instead, it’s probably better to convert all tables at once, or comment out a table and its where conditions in the original query in order to compare with the new ANSI query you are writing.
Источник
What is sql error 904
Answers were Sorted based on User’s Feedback
-904 UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE
RESOURCE. REASON reason-code, TYPE OF RESOURCE resource-
type, AND RESOURCE NAME reason-name
Explanation: The SQL statement could not be executed
because resource resource-name of type resource-type was
not available at the time for the reason indicated by
reason-code.
Try to display the stats of the table and check if it is in
RW mode, If not use the required repair utility to get the
table to RW mode.
If the table is in RW mode then may be the underlying
dataset may have got deleted in that case we will need to
do a dummy load to get those created.
If that also doesnt work will need to drop and recreate the
objects from TABLESPACE level.
Ths above is for IBM DB2 for z/os. Correct me if Iam wrong
Is This Answer Correct ? | 3 Yes | 0 No |
When querying or retrieving items or importing new items,
the library server returns [LS RC = 7015, SQL RC = -904]
DGL5050A: SQL error executing query. XQPE query: /ITA
[@SEMANTICTYPE
BETWEEN 1 AND 2].
Return code: 7015. Reason code: 0. Extended return code: —
904.
Extended reason code: 0.
(STATE) : [LS RC = 7015, SQL RC = -904] There is also a
warning in the library server log:
ICMPLSCP handleForeignKeys 06174 03/09 06:25:24.457 GMT
;09045111471478 16:10285a68c22:X7ea2 IFVTE WARNING—
Please perform CHECK DATA command on z/OS.
Possible cause
When adding a foreign key to an existing component type
table (ICMUTnnnnnsss), SQLCode 162 is returned. DB2® places
a table space into CHECK PENDING state if:
Any table in that table space has ever been populated at
any time.
A foreign key is added or modified for any table in the
table space.
The library server performs and commits the foreign key
creation. However, a warning message is written to the
library server log to remind you to run the CHECK DATA DB2
utility so that tables and views in this table space can be
accessed.
Action
Perform the CHECK DATA command: CHECK DATA TABLESPACE
DATABASE NAME TABLESPACE NAME
SQLCode 162
+162 TABLESPACE database-name.tablespace-name HAS BEEN
PLACED IN CHECK PENDING
Explanation: The indicated table space is in check pending
status because the ALTER TABLE statement was used to
specify a referential constraint or a check constraint
(while special register CURRENT RULES = ‘DB2’) on a
populated table. The table space is not generally available
until the check pending status is removed from the table
space.
System Action: The table space was placed in check pending
status.
Programmer Response: Run the CHECK DATA utility. The
enforcement of the referential constraint or the check
constraint is deferred until the CHECK DATA utility is run.
SQLCode -904
-904 UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE
RESOURCE. REASON reason-code, TYPE OF RESOURCE resource-
type, AND RESOURCE NAME reason-name
Explanation: The SQL statement could not be executed
because resource resource-name of type resource-type was
not available at the time for the reason indicated by
reason-code.
Источник
Nekr0n 0 / 0 / 0 Регистрация: 18.05.2010 Сообщений: 68 |
||||
1 |
||||
18.05.2010, 11:26. Показов 13979. Ответов 7 Метки нет (Все метки)
Подскажите пожалуйста в чем может быть ошибка, и как исправить, открываю isql.exe
Statement failed, SQLCODE = -904 2ой Statement failed, SQLCODE = -904
__________________
0 |
912 / 877 / 62 Регистрация: 06.01.2010 Сообщений: 2,367 Записей в блоге: 6 |
|
18.05.2010, 12:13 |
2 |
данная инструкция у меня выполняется.
0 |
0 / 0 / 0 Регистрация: 18.05.2010 Сообщений: 68 |
|
18.05.2010, 12:19 [ТС] |
3 |
Да у других вроде тоже выполняется, а у меня на компе нет( D есть точно, как и E Да нет вродь дословно все перенес.
0 |
912 / 877 / 62 Регистрация: 06.01.2010 Сообщений: 2,367 Записей в блоге: 6 |
|
18.05.2010, 12:42 |
4 |
D есть точно, как и E Диск D — полноценный физический диск (раздел винчестера)?
0 |
0 / 0 / 0 Регистрация: 18.05.2010 Сообщений: 68 |
|
18.05.2010, 12:51 [ТС] |
5 |
arni
0 |
912 / 877 / 62 Регистрация: 06.01.2010 Сообщений: 2,367 Записей в блоге: 6 |
|
18.05.2010, 13:36 |
6 |
ну тогда читай фак по сабжу тут — может осенит
0 |
0 / 0 / 0 Регистрация: 18.05.2010 Сообщений: 68 |
|
18.05.2010, 13:52 [ТС] |
7 |
Хмм запустил, но подсказали а не из фака нашел, оказывается в панели управления надо было в файрберд сервер зайти и старт нажать
0 |
912 / 877 / 62 Регистрация: 06.01.2010 Сообщений: 2,367 Записей в блоге: 6 |
|
18.05.2010, 14:24 |
8 |
мда, все равно что долго-долго ругаться с автосервисом, и под конец обнаружить, что заправиться бензином забыл
0 |
Модераторы: kdv, Alexey Kovyazin
-
Vladgul
- Сообщения: 12
- Зарегистрирован: 01 дек 2004, 16:07
Проблема подключения через ODBC к Firebird 2.5
Здравствуйте.
Задача такая: есть приложение (стороннее), которое умеет выводить данные через ODBC. Нужно эти данные получать.
Вот здесь и кроется проблема для меня.
OC Win7x64
Firebird 2.5 x32 (пробовал также и x64)
стороннее приложение под win32
Устанавливаю драйвера Firebird_ODBC_2.0.2.153_Win32.exe
После его установки не появляется в источниках данных (ODBC) драйвер для Firebird и соответственно я не могу создать DSN
В случае установки Firebird_ODBC_2.0.2.153_x64.exe драйвер появляется и можно попытаться создать DSN (Firebird уже переставлен x64)
Сама база есть. Ее можно открыть и посмотреть в IbExpert
Создаю DSN
Параметры:
Имя Fb Драйвер IscDbc
Примечание
База данных
127.0.0.1:C:UsersVladgulProgramDBTABLEALLTRANSACTION.FDB
Клиент
C:WindowsSystem32fbclient.dll
Пользователь
SYSDBA
пароль
masterkey
Попытка проверки соединения выдает «Открыть базу данных ‘127.0.0.1:C:UsersVladgulProgramDBTABLEALLTRANSACTION.FDB’ не удалось»
Если нажать кнопку «Сервис» в настройках «Firebird ODBC конфигуратор», и затем попробовать выполнить любое действие (backup/restore или просто переключиться на вкладку «Users»)
выдается ошибка sqlcode -904, fbcode 335544375 — Unable to connect to datasource: library ‘C:WindowsSystem32fbclient.dll’ failed to load.
fbclient.dll есть в этой папке.
Облазил почти весь инет , но решения так и не нашел. Вроде важно, чтобы разрядность драйвера ODBC совпадала с разрядностью приложения, которое будет его использовать (?), но до этого еще даже не дошло.
крик души — ПОМОГИТЕ!!!
спасибо.
-
Vladgul
- Сообщения: 12
- Зарегистрирован: 01 дек 2004, 16:07
Re: Проблема подключения через ODBC к Firebird 2.5
Сообщение
Vladgul » 03 авг 2014, 12:29
Проблема решена. Наверно просто запутался с установкой/переустановкой Firebird и драйверов ODBC.
И еще возможно запускал из панели управления настройки ODBC, а для Win7 x64 нужно нужно запускать odbcad32.exe вручную из каталога WindowsSystem32
Но возник другой вопрос. Вывод по ODBC в MySQL идет быстрее почти в 2.5 раза, чем тоже количество в Firebird по ODBC.
Таблица и там и там без индексов. Полей около 10. Общее кол-во записей для вывода чуть больше 560000.
Можно ли ускорить?