Sql1042c произошла непредвиденная системная ошибка sqlstate 58004

Problem

On a Windows OS based server running Db2 server, Db2 fails to start and gives the following error
«SQL1042C An unexpected system error occurred. SQLSTATE=58004».
Also the key service for Db2 (db2sysc.exe) is not started or running.

Symptom

On a Windows OS machine whenever you try to launch Db2 using the db2start command you see the error below:

C:\>db2start
DB2 : The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

SQL1042C  An unexpected system error occurred.  SQLSTATE=58004

Cause

The Windows Service responsible for the «db2sysc.exe» process is either disabled, or not able to run by some other cause.

Diagnosing The Problem

Check that the Db2 related service that runs the executable «db2sysc.exe» is running.

Resolving The Problem

Ensure that the service can start. If it’s not running or able to start then check what «Log On» user ID and password credentials the service is using, and make fully sure that these credentials are correct, enabled and working. If the current credentials still cause the service to fail from starting then try a different set of credentials. If that fails then you may need to re-install or repair the Db2 installation and files or refer to your Windows Server administrator.

Related Information

[{«Product»:{«code»:»SSEPGG»,»label»:»Db2 for Linux, UNIX and Windows»},»Business Unit»:{«code»:»BU058″,»label»:»IBM Infrastructure w\/TPS»},»Component»:»Operating System \/ Hardware — OS Configuration»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»9.8;9.7;10.1;10.5;11.1″,»Edition»:»Advanced Enterprise Server;Advanced Workgroup Server;Enterprise Server;Express;Express-C;Personal;Workgroup Server»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

Источник

When I give DB2 CONNECT command I get the error saying «SQL1042C An unexpected system error occurred». The most weird thing is this issue is intermittant.

sqlcode: -1042; 
sqlstate: 58004; 
DB2 connect command: connect to dbname user db2admin using password;

My DB2 version is: DB2/NT64 9.5.0

AngocA's user avatar

AngocA

7,6556 gold badges39 silver badges56 bronze badges

asked May 23, 2012 at 10:52

user1412385's user avatar

There are a few directions in the Information Center on how you might be able to fix this error, one of which involves calling IBM for support.

Hope that helps!

answered May 23, 2012 at 13:45

bhamby's user avatar

bhambybhamby

15.1k1 gold badge45 silver badges66 bronze badges

Try to use

db2 "? sql-1042"

for more information.
On the other hand, if you just installed new db2 software code, try to use

db2iupdt instance_name

to update db2 instance.

answered May 27, 2015 at 5:31

William Kwok's user avatar

You might find additional information in the file db2diag.log, which is located in a place like /home/db2inst1/sqllib/db2dump/db2diag.log . Or you can use the command db2diag with an option like db2diag -lastrecords 100

answered Mar 30, 2015 at 14:09

Oliver Schoett's user avatar

Actually SQL1042C can be happened with many reasons.
It’s better to check db2diag.log first as it will give the idea about what this may be about.

And if that happens with DB activation by first connect,

db2stop
db2diag -A
db2start
db2 connect to dbname user db2admin using password
=> SQL1042C

Check what’s recorded on new db2diag.log.

As William mentioned previously, ‘db2iupdt’ is the good attempt when you have no idea right away.

answered Nov 5, 2016 at 1:18

Jun Su Lee's user avatar

run db2iupdt,
looks like issues with binaries ,
let me know , when you got this error.
if possible upload following command output
db2diag -g ‘level=Critical’

answered Aug 28, 2018 at 3:31

EnnamLekha's user avatar

Источник

We recently upgraded some of our employee’s DB2 Runtime client from 9.7 (32 bit) to 10.5 FP3 (64 bit) in their windows 7 machines.After that some of them are having issues when trying to connect to our database through an excel macro or even through db2 clp.They are getting the below error

IBM CLI Driver SQL1042C An unexpected system error occurred.
SQLSTATE=58004

I have checked their db2diag.log and i see this

2015-06-17-17.06.34.820000-240    I11076H445            LEVEL: Error
PID     : 1216                 TID : 5372           PROC : EXCEL.EXE
INSTANCE: DB2                  NODE : 000
HOSTNAME: MLIW*****
EDUID   : 5372

FUNCTION: DB2 Common, Cryptography, cryptDynamicLoadGSKitCrypto, probe:998

MESSAGE : ECF=0x90000007=-1879048185=ECF_UNKNOWN
          Unknown

DATA #1 : unsigned integer, 4 bytes

60

DATA #2 : String, 11 bytes

gsk8sys.dll*

Please advise.

Brent Washburne's user avatar

asked Jun 17, 2015 at 23:39

Venkata Pakalapati's user avatar

2

The symptom may be depended on the installation order of Db2 connect and a program (EXCEL). If DB2 connect is installed first, it should not be occurred.

So it is nice that checking installation order for EXCEL and Db2 at both OK and NG user’s machines. If don’t remember, try to remove and re-install both products once then install Db2 connect first.

Hope this helps.

answered Nov 8, 2019 at 8:39

hidehy's user avatar

hidehyhidehy

1795 bronze badges

Источник

When i run it with my node server my node app runs fine but when i try to initiate a db2 connection my node server says

warn: [IBM][CLI Driver] SQL1042C An unexpected system error occurred. SQLSTATE=58004

Im running a windows with latest node-ibm.

Here is the output from the testconnection.bat file you guys provide

===============================================================================
Client information for the current copy (copy name: F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidriver):

Client Package Type : IBM Data Server Driver For ODBC and CLI
Client Version (level/bit): DB2 v11.1.3031.295 (s1804271300/64-bit)
Client Platform : NT 64BIT
Install/Instance Path : F:\Jenkins\workspace\DataHub_API_development\node_modules\ibm_db\installer\clidriver

Common App Data Path : C:\ProgramData\IBM\DB2\F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidriver
DB2DSDRIVER_CFG_PATH value:
db2dsdriver.cfg Path : \cfg\db2dsdriver.cfg
DB2CLIINIPATH value :
db2cli.ini Path : \cfg\db2cli.ini
db2diag.log Path : \db2diag.log

===============================================================================
List of all IBM Data Server client packages on the current workstation:

Copyname Version Package Language Installed-Location

F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidriver[C] 11.1.0303 CLI EN F:\Jenkins\workspace\DataHub_API_development\node_modules\ibm_db\installer\clidriver

CLI: IBM Data Server Driver for ODBC and CLI

===============================================================================
db2dsdriver.cfg schema validation for the entire file:

Note: The validation utility could not find the configuration file
db2dsdriver.cfg. The file is searched at
«C:\ProgramData\IBM\DB2\F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidriver\cfg\db2dsdriver.cfg».

===============================================================================
db2cli.ini validation for database «sample:hotel.torolab.ibm.com:21169»:

Note: The validation utility could not find the configuration file db2cli.ini.
The file is searched at
«C:\ProgramData\IBM\DB2\F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidriver\cfg\db2cli.ini».

===============================================================================
db2dsdriver.cfg validation for database «sample:hotel.torolab.ibm.com:21169»:

Note: The validation utility could not find the configuration file
db2dsdriver.cfg. The file is searched at
«C:\ProgramData\IBM\DB2\F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidriver\cfg\db2dsdriver.cfg».

===============================================================================
Connection attempt for database «sample:hotel.torolab.ibm.com:21169»:

[FAILED]: [IBM][CLI Driver] SQL1042C An unexpected system error occurred. SQLSTATE=58004

===============================================================================
Error: The validation operation failed.

===============================================================================
The validation is completed.

Источник

Problem

On a Windows OS based server running Db2 server, Db2 fails to start and gives the following error
«SQL1042C An unexpected system error occurred. SQLSTATE=58004».
Also the key service for Db2 (db2sysc.exe) is not started or running.

Symptom

On a Windows OS machine whenever you try to launch Db2 using the db2start command you see the error below:

C:>db2start
DB2 : The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

SQL1042C  An unexpected system error occurred.  SQLSTATE=58004

Cause

The Windows Service responsible for the «db2sysc.exe» process is either disabled, or not able to run by some other cause.

Diagnosing The Problem

Check that the Db2 related service that runs the executable «db2sysc.exe» is running.

Resolving The Problem

Ensure that the service can start. If it’s not running or able to start then check what «Log On» user ID and password credentials the service is using, and make fully sure that these credentials are correct, enabled and working. If the current credentials still cause the service to fail from starting then try a different set of credentials. If that fails then you may need to re-install or repair the Db2 installation and files or refer to your Windows Server administrator.

Related Information

[{«Product»:{«code»:»SSEPGG»,»label»:»Db2 for Linux, UNIX and Windows»},»Business Unit»:{«code»:»BU058″,»label»:»IBM Infrastructure w/TPS»},»Component»:»Operating System / Hardware — OS Configuration»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»9.8;9.7;10.1;10.5;11.1″,»Edition»:»Advanced Enterprise Server;Advanced Workgroup Server;Enterprise Server;Express;Express-C;Personal;Workgroup Server»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

When i run it with my node server my node app runs fine but when i try to initiate a db2 connection my node server says

warn: [IBM][CLI Driver] SQL1042C An unexpected system error occurred. SQLSTATE=58004

Im running a windows with latest node-ibm.

Here is the output from the testconnection.bat file you guys provide

===============================================================================
Client information for the current copy (copy name: F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidriver):

Client Package Type : IBM Data Server Driver For ODBC and CLI
Client Version (level/bit): DB2 v11.1.3031.295 (s1804271300/64-bit)
Client Platform : NT 64BIT
Install/Instance Path : F:JenkinsworkspaceDataHub_API_developmentnode_modulesibm_dbinstallerclidriver

Common App Data Path : C:ProgramDataIBMDB2F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidriver
DB2DSDRIVER_CFG_PATH value:
db2dsdriver.cfg Path : cfgdb2dsdriver.cfg
DB2CLIINIPATH value :
db2cli.ini Path : cfgdb2cli.ini
db2diag.log Path : db2diag.log

===============================================================================
List of all IBM Data Server client packages on the current workstation:

Copyname Version Package Language Installed-Location

F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidriver[C] 11.1.0303 CLI EN F:JenkinsworkspaceDataHub_API_developmentnode_modulesibm_dbinstallerclidriver

CLI: IBM Data Server Driver for ODBC and CLI

===============================================================================
db2dsdriver.cfg schema validation for the entire file:

Note: The validation utility could not find the configuration file
db2dsdriver.cfg. The file is searched at
«C:ProgramDataIBMDB2F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidrivercfgdb2dsdriver.cfg».

===============================================================================
db2cli.ini validation for database «sample:hotel.torolab.ibm.com:21169»:

Note: The validation utility could not find the configuration file db2cli.ini.
The file is searched at
«C:ProgramDataIBMDB2F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidrivercfgdb2cli.ini».

===============================================================================
db2dsdriver.cfg validation for database «sample:hotel.torolab.ibm.com:21169»:

Note: The validation utility could not find the configuration file
db2dsdriver.cfg. The file is searched at
«C:ProgramDataIBMDB2F_Jenkins_workspace_DataHub_API_development_node_modules_ibm_db_installer_clidrivercfgdb2dsdriver.cfg».

===============================================================================
Connection attempt for database «sample:hotel.torolab.ibm.com:21169»:

[FAILED]: [IBM][CLI Driver] SQL1042C An unexpected system error occurred. SQLSTATE=58004

===============================================================================
Error: The validation operation failed.

===============================================================================
The validation is completed.

An application owner reported an error on a DB2 database connection attempt.  A query on db2diag.log returned  this message

ADM1710C  The database is not accessible because the DB2 database 
          manager cannot write to the log control file "SQLOGCTL.LFH.2" on 
          database partition "0".  Possible reasons for this include: the file 
          does not exist; the file is not accessible to the database manager 
          because of network, file system, or OS problems; or incorrect file 
          permissions are preventing the database manager from writing to the 
          file.  Ensure that the file is accessible to the database manager and 
          that the file system is functioning properly, and restart or 
          reconnect to the database.

I attempted a DB2 database database connection, with a message of: 

SQL1042C  An unexpected system error occurred.  SQLSTATE=58004

The database was marked as bad .  the DB2 error messages correlated with Linux messages, relating to SCSI errors . 

 
Dec 19 08:02:05 server1 kernel: Buffer I/O error on device dm-18, logical block 1562696
Dec 19 08:02:05 server1 kernel: lost page write due to I/O error on dm-18
Dec 19 08:02:05 server1 kernel: SCSI error : <0 0 2 0> return code = 0x20000
Dec 19 08:02:05 server1 kernel: end_request: I/O error, dev sdc, sector 12503752

DB2 couldn’t write  due to the Linux file system drive moving into a read-only state ,which it does under certain circumstances to protect itself . Using Commands check for read only Linux file system  , to verify the filesystem was in read only , I contact the Linux administrator.

The filesytem was remounted and placed back into the read/write state. Various DB2 files were recovered and made accessible again – which allowed the database to become available .

 Read More

Commands to check for read only Linux file system — DBA DB2

DB2 and Linux IO testing tools — DBA DB2

Command to see connection on a DB2 database — list applications

So I had a customer complain that their DB2 Express-C database (version 9.0) wouldn’t talk to them any more.  When I attempted a direct connection to the database, I found that it was suffering from ‘unexpected system error’.  

So I attempted to restart the database.

db2 => restart database [dbname]
SQL1042C  An unexpected system error occurred.  SQLSTATE=58004

Puzzled, I attempted to restore an old backup of the database — just throw away the log files and start back at a point when the database was good.

db2 => restore database [dbname] from d:db2_backups taken at 20101001020000 with
out rolling forward
SQL2537N  Roll-forward is required following the Restore.

db2 => rollforward database [dbname] complete
SQL1015N  The database is in an inconsistent state.  SQLSTATE=55025

My next step was to check the db2diag.log file.   It told me that DB2 had attempted to recover from a crash and had failed to do so.  

I will include some relevant snippets below.

I am frankly out of ideas. Is there any way to make this system functional again?  Or should I start building a new database from scratch?

Respectfully,

Brian P.

Db2diag.log snippets:

2010-11-27-00.49.58.712000-480 I34928586H457      LEVEL: Warning
PID     : 2080                 TID  : 2880        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000         DB   : [database]
APPHDL  : 0-7                  APPID: *LOCAL.DB2.101127084938
AUTHID  : [user]
FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:4000
MESSAGE : DIA2051W Forward phase of crash recovery has completed.  Next LSN is
          «000002A01DF9FFD1».

2010-11-27-00.49.58.760000-480 I34929045H399      LEVEL: Severe
PID     : 2080                 TID  : 2880        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000         DB   : [database]
APPHDL  : 0-7                  APPID: *LOCAL.DB2.101127084938
AUTHID  : [user]
FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:4110
MESSAGE : Recovery did not reach the end of the logs!

2010-11-27-00.49.58.760000-480 I34929446H161      LEVEL: Severe
PID:2080 TID:2880 NODE:000 Title: SQLP_DBCB
Dump File:C:PROGRA~1IBMSQLLIBDB220802880.000

2010-11-27-00.49.58.760000-480 I34929609H515      LEVEL: Error
PID     : 2080                 TID  : 2880        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000         DB   : MINIBAR
APPHDL  : 0-7                  APPID: *LOCAL.DB2.101127084938
AUTHID  : [user]
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:640
DATA #1 : String, 142 bytes
Crash recovery failed with rc -2045771763
LowtranLSN 000002A01DF9F1FE MinbuffLSN 000002A0190F2F38
Recovery started on log file S0172056.LOG.

2010-11-27-00.49.58.823000-480 I34930126H433      LEVEL: Severe
PID     : 2080                 TID  : 2880        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000         DB   : MINIBAR
APPHDL  : 0-7                  APPID: *LOCAL.DB2.101127084938
AUTHID  : [user]
FUNCTION: DB2 UDB, base sys utilities, recover, probe:16
DATA #1 : Hexdump, 4 bytes
0x04DE9704 : 0D00 1086                                  ….

2010-11-27-00.49.58.871000-480 I34930561H432      LEVEL: Error
PID     : 2080                 TID  : 2880        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000         DB   : [database]
APPHDL  : 0-7                  APPID: *LOCAL.DB2.101127084938
AUTHID  : [database]
FUNCTION: DB2 UDB, base sys utilities, recover, probe:16
DATA #2 : Hexdump, 4 bytes
0x04DE9704 : 0D00 1086            

2010-11-27-00.49.58.871000-480 E34931408H392      LEVEL: Severe
PID     : 2080                 TID  : 2880        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000         DB   : [database]
APPHDL  : 0-7                  APPID: *LOCAL.DB2.101127084938
AUTHID  : [user]
FUNCTION: DB2 UDB, base sys utilities, sqleMarkDBad, probe:10
MESSAGE : ADM7518C  «[database] » marked bad.

2010-11-27-00.49.58.871000-480 I34931802H405      LEVEL: Severe
PID     : 2080                 TID  : 2880        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000         DB   : [database]
APPHDL  : 0-7                  APPID: *LOCAL.DB2.101127084938
AUTHID  : [user]
FUNCTION: DB2 UDB, base sys utilities, sqleMarkDBad, probe:210
MESSAGE : Database logging stopped due to mark db bad.

This post is specific to DB2 for UNIX or Linux. SQL1042C can have a number of causes and be received as an error from a number of different commands. The IBM Support Portal does a good job of coming up with the issues and solutions. And I have it in the back of my head that when I get this error, I need a db2iupdt – which is non trivial since it requires the instance to be down and root access to run.

The Problem

Today, on a server I’m working on, I noticed that one of my maintenance checking scripts was returning incorrect restults. It was reporting that a database backup had never been taken when I knew I had verified a backup just yesterday. I had just started this maintenance script running in this new non-production environment.

When I dug into the detailed script output, I discovered this issue:

db2 "select last_backup from table(snap_get_db('SAMPLE', -1)) as tab_snap"
SQL1042C  An unexpected system error occurred.  SQLSTATE=58004

The Investigation

My script was unable to get a value for the timestamp of the last backup. Now, I knew that I probably needed a db2iupdt because that’s the most common solution I’ve seen for this error message. But I also wanted to have ammunition to back me up in case someone objected to the 15 minutes of down time that this would require. On searching the support portal, I found this Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21399105, which describes receiving SQL1042C when running a fenced stored procedure. I figured that it is entirely possible that a system table function is using a fenced stored procedure at some point, so I look in the db2diag.log for the error that the document references. I find this:

2012-11-13-14.23.03.101637-360 E3064418E1437       LEVEL: Error
PID     : 9888                 TID  : 139713792960256PROC : db2sysc 0
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE
APPHDL  : 0-4498               APPID: *LOCAL.db2inst1.121113202302
AUTHID  : DB2INST1
EDUID   : 1250                 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerRemoveAllIPCforRow, probe:30
DATA #1 : String, 29 bytes
Number of IPC resource found:
DATA #2 : signed integer, 4 bytes
1
DATA #3 : String, 29 bytes
Number of IPC resource freed:
DATA #4 : signed integer, 4 bytes
1
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
  [0] 0x00007F135201C996 pdLog + 0x398
  [1] 0x00007F1352FC25C5 _Z23sqlerRemoveAllIPCforRowP11sqlerFmpRowb + 0x3FF
  [2] 0x00007F1352FC215C /db2home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x1D0715C
  [3] 0x00007F1352FC2662 _Z23sqlerRemoveFmpFromTableP11sqlerFmpRowb + 0x2A
  [4] 0x00007F1352FC2819 /db2home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x1D07819
  [5] 0x00007F13521A0948 _Z19sqlerGetFmpFromPoolP14sqlerFmpHandleP13sqlerFmpParms + 0x498
  [6] 0x00007F135219DF07 _Z24sqlerInvokeFencedRoutineP13sqlerFmpParms + 0x3D1
  [7] 0x00007F135272B39C _Z18sqlriInvokeInvokerP10sqlri_ufobb + 0x2CA
  [8] 0x00007F1353FE80B4 _Z8sqlriutfP8sqlrr_cb + 0x2EA
  [9] 0x00007F13526EDD0F _Z15sqlriExecThreadP8sqlrr_cbP12sqlri_opparm + 0x73

To me, that doesn’t look much like what’s in the Technote, but I decide to test out the permissions issue for the fenced user that the Technote describes anyway. When I look at the permissions on sqllib and sqllib/db2systm, they look correct. But when I actually su over to my fenced user and try to view the file as the Technote suggests, I get a permission denied error. That confirms for me that I need the db2iupdt. As the Technote says “If permission problems were found when accessing the db2systm file then use the db2iupdt command (as root userid) to reset the permissions for the instance.”

The Solution

I have to schedule an outage on this particular system, so when the scheduled time comes, here’s what I do:

  • force off all connections
  • stop DB2
  • su over to root
  • cd to /opt/IBM/db2/V9.7/instance (the first part of that is your install path, and may vary – I believe the default has a lower-case IBM in it)
  • execute: 
    # ./db2iupdt -k db2inst1
DBI1070I  Program db2iupdt completed successfully.

I then start my instance back up, and try the failing query again:

$ db2 "select last_backup from table(snap_get_db('WC036Q01', -1)) as tab_snap"

LAST_BACKUP               
--------------------------
2012-11-11-03.00.02.000000

  1 record(s) selected.

And my problem is resolved.

Ember is always curious and thrives on change. She has built internationally recognized expertise in IBM Db2, and is now pivoting to focus on learning MySQL. Ember shares both posts about her core skill set and her journey learning MySQL.

Ember lives in Denver and work from home


  • Remove From My Forums

  • Общие обсуждения

  • I have a problem migrating the reporting service from 2014 to 2017. When I test connection in the data source, it says connected. but when I try to run the report, this is the error I got:

    • An error has occurred during report processing. (rsProcessingAborted)
      • Cannot create a connection to data source ‘DynamicDB2’. (rsErrorOpeningConnection)
        • ERROR [HY000] [IBM][CLI Driver] SQL1042C An unexpected system error occurred. SQLSTATE=58004 ERROR [HY000] [IBM][CLI Driver] SQL1042C An unexpected system error occurred. SQLSTATE=58004 

        Anyone has encountered this issue before?

        Thank you in advance!

    • Изменен тип

      24 июня 2019 г. 2:54
      this is discussion

Источник

Понравилась статья? Поделить с друзьями:
  • Sql сервер ошибка 4064
  • Sqlserverwriter неисправен неповторяемая ошибка
  • Sql сервер ошибка 3417
  • Sqlite ошибка проверки внешних ключей после изменения таблицы
  • Sqlite ошибка no such table