Главная » Основные форумы » Система QUIK
Страницы:
1
Leff
Сообщений: 63 |
#1 16.06.2015 21:48:12 [Microsoft][SQL Server Native Client 10.0][SQL Server]Ошибка арифметического переполнения при преобразовании expression к типу данных int. SQLSTATE=22003 Код ошибки=8115 ODBC_ERROR Как узнать на какое поле какой таблицы ругается? PS хелп свежий. седня качал. почему ничего в нем нет про таблицу транзакций? |
Alexey Ivannikov
Сообщений: 1276 |
#2 16.06.2015 21:56:32
Добрый день. Как вариант — посмотреть в логе, создав quik_odbc.log. Как создать файл с именем quik_odbc.log: |
||
Leff
Сообщений: 63 |
#3 16.06.2015 22:05:42
спасибо за оперативность. пробую |
||
Leff
Сообщений: 63 |
#4 16.06.2015 22:13:40
сделал. пока тишина — ошибок нет. неохота завтра нарваться в рабочем режиме |
||
Leff
Сообщений: 63 |
#5 16.06.2015 22:20:30 так. ошибка снова. лог куда слать? я посмотрел но ничо не понял. мало инфы в нем |
Alexey Ivannikov
Сообщений: 1276 |
#6 16.06.2015 22:27:23
Добрый день. quiksupport@arqatech.com |
||
Leff
Сообщений: 63 |
#7 16.06.2015 22:28:45
ушло |
||
Leff
Сообщений: 63 |
#8 16.06.2015 22:42:58 ошибка вышла в 22:14:02 похоже (если верить предыдущей записи) что на таблицу всех сделок. |
Leff
Сообщений: 63 |
#9 16.06.2015 22:49:32 похоже нашел. по номеру сделки перед ошибкой: толи кол-во толи 3 милиарда не вошло. |
Alexey Ivannikov
Сообщений: 1276 |
#10 16.06.2015 22:54:40
Добрый день. Ответили Вам на почту. P.S. Скорее всего у Вас формат для объёма в ТВС стоит неверный. |
||||
Страницы:
1
Читают тему (гостей: 2)
- Remove From My Forums
-
Question
-
Hello all,
SQL index maintenance job is keep on failing with the below error (both scheduled job and manual run). The job was created and last edited in 2015 and nothing is changed. Please suggest.
Job script:
DECLARE @ReturnCode
intEXEC @ReturnCode = [maintenance].[index_maintenance]
@RebuildLevel = 25.00,
@DefragLevel = 25.00,
@MinimumPagesToReorg = 8,
@DatabaseName = NULL,
@AllowOnlineRebuild = 1,
@RebuildDisabled = 0;PRINT ‘@ReturnCode = ‘ + CAST(@ReturnCode AS varchar(30));
IF @ReturnCode != 0
RAISERROR (‘Index Maintenance Failed with %d errors. Please check job history/log for details.’, 10, 1, @ReturnCode);Error :
Date 10/28/2019 1:16:35 AM
Log Job History (index maintenance)Step ID 1
Server xxxxxxxx
Job Name index maintenance
Step Name index_maintenance
Duration 06:13:54
Sql Severity 21
Sql Message ID 3621
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0Message
Executed as user: xxxxxxSQLAdmin. …************************************** [SQLSTATE 01000] (Message 0) ****
**** [SQLSTATE 01000] (Message 0) ****
msdb **** [SQLSTATE
01000] (Message 0) ****
**** [SQLSTATE 01000] (Message 0) ***********************************************************************************************/ [SQLSTATE 01000] (Message 0) —==============================================================================================—
[SQLSTATE 01000] (Message 0) — [msdb].[dbo].[backupmediafamily] [SQLSTATE 01000] (Message 0) — Start Time: 2019-10-28 02:59:49 [SQLSTATE 01000] (Message 0) ALTER INDEX [backupmediafamilyuuid] ON [msdb].[dbo].[backupmediafamily]
REBUILD WITH (ONLINE = ON); [SQLSTATE 01000] (Message 0) — Success [SQLSTATE 01000] (Message 0) — Duration: 00:00:00:053 [SQLSTATE 01000] (Message 0) —==============================================================================================—
[SQLSTATE 01000] (Message 0) —==============================================================================================— [SQLSTATE 01000] (Message 0) — [msdb].[dbo].[backupmediaset] [SQLSTATE 01000] (Message 0) — Start
Time: 2019-10-28 02:59:49 [SQLSTATE 01000] (Message 0) ALTER INDEX [backupmediasetuuid] ON [msdb].[dbo].[backupmediaset] REBUILD WITH (ONLINE = ON); [SQLSTATE 01000] (Message 0) — Success [SQLSTATE 01000] (Message 0) — Duration:
00:00:00:023 [SQLSTATE 01000] (Message 0) —==============================================================================================— [SQLSTATE 01000] (Message 0) —==============================================================================================—
[SQLSTATE 01000] (Message 0) — [msdb].[dbo].[backupset] [SQLSTATE 01000] (Message 0) — Start Time: 2019-10-28 02:59:49 [SQLSTATE 01000] (Message 0) ALTER INDEX [backupsetuuid] ON [msdb].[dbo].[backupset] REBUILD WITH (ONLINE
= ON); [SQLSTATE 01000] (Message 0) — Success [SQLSTATE 01000] (Message 0) — Duration: 00:00:00:017 [SQLSTATE 01000] (Message 0) /***********************************************************************************************
[SQLSTATE 01000] (Message 0) ****
**** [SQLSTATE 01000] (Message 0) ****
Accums **** [SQLSTATE 01000] (Message 0) ****
**** [SQLSTATE 01000] (Message 0) ***********************************************************************************************/ [SQLSTATE 01000] (Message 0) —==============================================================================================—
[SQLSTATE 01000] (Message 0) —==============================================================================================— [SQLSTATE 01000] (Message 0) — [Accums].[Accum].[AccumulatorLineClaimLine] [SQLSTATE 01000] (Message 0)
— Start Time: 2019-10-28 02:59:49 [SQLSTATE 01000] (Message 0) ALTER INDEX [ixAccumAccumulatorLineClaimLineAccumulatorClaimLineId] ON [Accums].[Accum].[AccumulatorLineClaimLine] REBUILD WITH (ONLINE = ON); [SQLSTATE 01000] (Message 0) —
Success [SQLSTATE 01000] (Message 0) — Duration: 00:00:01:407 [SQLSTATE 01000] (Message 0) /*********************************************************************************************** [SQLSTATE 01000] (Message 0) ****
**** [SQLSTATE 01000] (Message 0) **** ClaimODS_AQA
**… The step failed.-
Edited by
Tuesday, October 29, 2019 2:06 AM
-
Edited by
Answers
-
When I run it manually, it took 7 hrs and failed saying Timed out
«Timed out»? Do you happen to have the full error message? Normally, you cannot get time-out errors when running an SQL batch. More precisely, anything with timeouts can be any of these four:
- A time-out in the client-side API. This is clearly not the case here.
- A lock timeout. This can be configured with SET LOCK_TIMEOUT. This could possibly the reason here if the table is locked and a lock timeout has been set up.
- There can be a timeout when accessing a linked server. But this cannot be the case here.
- Finally, I seem to recall that there can be timeouts on internal semaphores. These counts as anomalies and could be considered bugs in SQL Server. If this would be the reason, you should find a dump in the SQL Server errorlog.
If you configure an output file as I suggested, you should get the error message, but if you already have it available, we can make progress faster.
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
-
Marked as answer by
Gopinath_DBA
Wednesday, October 30, 2019 3:55 AM
-
That is not an error message. That is just the output from the job. But it has neen truncated, so the error message is not seen.
On the Advanced tab for the job step, you can specify an output file. Do this, so that you get the complete output.
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
-
Marked as answer by
Gopinath_DBA
Wednesday, October 30, 2019 3:56 AM
-
Marked as answer by
Message
Executed as user: ArrivalsDepartures.
The INSERT statement conflicted with the FOREIGN KEY constraint «FK_DepartureStatusArchive_TechnicianName».
The conflict occurred in database «DatabaseName», table «dbo.Users», column ‘UserID’. [SQLSTATE 23000] (Error 547)
The statement has been terminated. [SQLSTATE 01000] (Error 3621).
The step failed.
Root Cause
Error is not referring to the table which is having foreign-key to the Users table rather it mentioned the constraint name FK_DepartureStatusArchive_TechnicianName.
Also, the procedure is inserting data from Table A to Table B. Table B is having the foreign key to Users Table. This foreign key column is accepting NULLs but the column in Users table is Primary Key.
Fix
Actually, the culprit table is Archive table and the table structure was changed recently as part of one change. As the table is Archive and does not require referential key to Users table. Dropped the foreign key and now the job executed successfully.
Drop Foreign Key: Expand the table B->expand the Keys->right-click and script the key to be deleted-> run it against the Database and the constraint is deleted.
Имеется таблица на SQL и подключена она к 1с как внешний источник. Необходимо из внешней обработки записать в таблицу данные. Попробовал так:
&НаСервере
Процедура Команда1НаСервере()
Данные=ВнешниеИсточникиДанных.ТаблицаSQL.Таблицы.dbo_eanuidnom.СоздатьОбъект();
Данные.code_ut=422;
Данные.ean=Данные.code_ut.ean;
Данные.guid=22234;
Данные.Записать();
КонецПроцедуры
&НаКлиенте
Процедура Команда1(Команда)
Команда1НаСервере();
КонецПроцедуры
Выдает ошибку!
по причине:
Ошибка внешней базы данных:
ошибка при выполнении запроса
по причине:
Ошибка ODBC. SQLSTATE: 23000
Номер ошибки: 547
Описание: [Microsoft][ODBC SQL Server Driver][SQL Server]Конфликт инструкции INSERT с ограничением FOREIGN KEY «FK_eanuidnom_nomenklatura». Конфликт произошел в базе данных «SCAN_SKLAD», таблица «dbo.nomenklatura», column ‘Code’.
Ошибка ODBC. SQLSTATE: 01000
Номер ошибки: 3621
Описание: [Microsoft][ODBC SQL Server Driver][SQL Server]Выполнение данной инструкции было прервано.
Что делаю не так?
Question: A client is sending a query to a SQL Server . After 30 seconds a message appears on the SQL Server trace:
User error message : The statement has been terminated
If I run the code from SSMS, it completes successfully. Could you explain how I can fix this problem?
Answer: SQL Server runs queries with no timeout. The query timeout error is occurring on the client side. When a command exceeds the timeout duration, the client API sends an attention signal to SQL Server to cancel the executing query.
An example is the CommandTimeout property, defaulting to 30 seconds in ADO and ADO.NET.
If you have the Attention event added to the SQL Server trace, you’ll notice it appearing. In addition, the client API throws the timeout expired exception error message. You could recreate the message by executing the code from SSMS and hitting the cancel after 30 seconds
Read More
SQL Server – Troubleshooting the SQL Profiler trace Attention class event
SQL Server – How to troubleshoot query timeouts
SQL Server SLEEPING MODE , locks and transactions
What is SQL Server Query Tuning?
Author: Tom Collins (http://www.sqlserver-dba.com)
Share: