Ошибка 1630 mysql

MacLochlainns Weblog

Michael McLaughlin’s Technical Blog

Placement over substance

I was stunned when a SQL query raised an ERROR 1630 (42000) telling me the SUM function didn’t exist in MySQL 5.5.23. The fix was simple. The opening parenthesis of the SUM function must be on the same line as the SUM keyword without an intervening white space. Alternatively phrased, you can’t have a line return or white space between the SUM function name and the opening parenthesis of the call parameter list. The same rule doesn’t apply to the opening parenthesis of the FORMAT function and it seems to me that this parsing inconsistency is problematic.

Therefore, my surprise, observation, and complaint is that all functions don’t parse the same way, using the same rules. That is, unless you use specialized SQL_MODE settings. This assumption was borne out by Kolbe Kegel’s comment on this post, and there are 30 remaining built in functions that have specialized parsing and resolution markers.

A simplified version of the code that raises the error follows. As you’ll notice the opening parenthesis for the FORMAT and SUM function have intervening white space and a line return.

SELECT t.transaction_account AS «Transaction» , LPAD(FORMAT (SUM (CASE WHEN EXTRACT(MONTH FROM transaction_date) = 1 AND EXTRACT(YEAR FROM transaction_date) = 2011 THEN CASE WHEN t.transaction_type = cl.common_lookup_type THEN t.transaction_amount ELSE t.transaction_amount * -1 END END),2),10,’ ‘) AS «JAN» FROM TRANSACTION t CROSS JOIN common_lookup cl WHERE cl.common_lookup_table = ‘TRANSACTION’ AND cl.common_lookup_column = ‘TRANSACTION_TYPE’ AND cl.common_lookup_type = ‘DEBIT’ GROUP BY t.transaction_account;

Based on the comments, the SQL_MODE is:

It raises the following error:

ERROR 1630 (42000): FUNCTION studentdb.SUM does not exist. Check the ‘Function Name Parsing and Resolution’ section in the Reference Manual

Moving ONLY the opening parenthesis to the end of the SUM keyword (or removing the line return and white space from between the SUM keyword and opening parenthesis) prevents the error but it would be more convenient if it supported both approaches. It seems odd that an intervening line return and white space for the SUM function raises an exception while the same intervening line return and white space doesn’t raise an exception for the FORMAT function. It strikes me the parser should support both or reject both. Here’s the fixed code that works without enabling the IGNORE_SPACE SQL Mode option.

SELECT t.transaction_account AS «Transaction» , LPAD(FORMAT (SUM( CASE WHEN EXTRACT(MONTH FROM transaction_date) = 1 AND EXTRACT(YEAR FROM transaction_date) = 2011 THEN CASE WHEN t.transaction_type = cl.common_lookup_type THEN t.transaction_amount ELSE t.transaction_amount * -1 END END),2),10,’ ‘) AS «JAN» FROM TRANSACTION t CROSS JOIN common_lookup cl WHERE cl.common_lookup_table = ‘TRANSACTION’ AND cl.common_lookup_column = ‘TRANSACTION_TYPE’ AND cl.common_lookup_type = ‘DEBIT’ GROUP BY t.transaction_account;

As noted by the comments, adding the IGNORE_SPACE to the SQL_MODE lets both queries work without moving the open parenthesis. You can do that in a session with the following syntax (which is covered in an older post):

SET SQL_MODE=(SELECT CONCAT(@@sql_mode,’,IGNORE_SPACE’));

Источник

MacLochlainns Weblog

Michael McLaughlin’s Technical Blog

Archive for the ‘SQL_MODE’ tag

Placement over substance

I was stunned when a SQL query raised an ERROR 1630 (42000) telling me the SUM function didn’t exist in MySQL 5.5.23. The fix was simple. The opening parenthesis of the SUM function must be on the same line as the SUM keyword without an intervening white space. Alternatively phrased, you can’t have a line return or white space between the SUM function name and the opening parenthesis of the call parameter list. The same rule doesn’t apply to the opening parenthesis of the FORMAT function and it seems to me that this parsing inconsistency is problematic.

Therefore, my surprise, observation, and complaint is that all functions don’t parse the same way, using the same rules. That is, unless you use specialized SQL_MODE settings. This assumption was borne out by Kolbe Kegel’s comment on this post, and there are 30 remaining built in functions that have specialized parsing and resolution markers.

A simplified version of the code that raises the error follows. As you’ll notice the opening parenthesis for the FORMAT and SUM function have intervening white space and a line return.

SELECT t.transaction_account AS «Transaction» , LPAD(FORMAT (SUM (CASE WHEN EXTRACT(MONTH FROM transaction_date) = 1 AND EXTRACT(YEAR FROM transaction_date) = 2011 THEN CASE WHEN t.transaction_type = cl.common_lookup_type THEN t.transaction_amount ELSE t.transaction_amount * -1 END END),2),10,’ ‘) AS «JAN» FROM TRANSACTION t CROSS JOIN common_lookup cl WHERE cl.common_lookup_table = ‘TRANSACTION’ AND cl.common_lookup_column = ‘TRANSACTION_TYPE’ AND cl.common_lookup_type = ‘DEBIT’ GROUP BY t.transaction_account;

Based on the comments, the SQL_MODE is:

It raises the following error:

ERROR 1630 (42000): FUNCTION studentdb.SUM does not exist. Check the ‘Function Name Parsing and Resolution’ section in the Reference Manual

Moving ONLY the opening parenthesis to the end of the SUM keyword (or removing the line return and white space from between the SUM keyword and opening parenthesis) prevents the error but it would be more convenient if it supported both approaches. It seems odd that an intervening line return and white space for the SUM function raises an exception while the same intervening line return and white space doesn’t raise an exception for the FORMAT function. It strikes me the parser should support both or reject both. Here’s the fixed code that works without enabling the IGNORE_SPACE SQL Mode option.

SELECT t.transaction_account AS «Transaction» , LPAD(FORMAT (SUM( CASE WHEN EXTRACT(MONTH FROM transaction_date) = 1 AND EXTRACT(YEAR FROM transaction_date) = 2011 THEN CASE WHEN t.transaction_type = cl.common_lookup_type THEN t.transaction_amount ELSE t.transaction_amount * -1 END END),2),10,’ ‘) AS «JAN» FROM TRANSACTION t CROSS JOIN common_lookup cl WHERE cl.common_lookup_table = ‘TRANSACTION’ AND cl.common_lookup_column = ‘TRANSACTION_TYPE’ AND cl.common_lookup_type = ‘DEBIT’ GROUP BY t.transaction_account;

As noted by the comments, adding the IGNORE_SPACE to the SQL_MODE lets both queries work without moving the open parenthesis. You can do that in a session with the following syntax (which is covered in an older post):

SET SQL_MODE=(SELECT CONCAT(@@sql_mode,’,IGNORE_SPACE’));

Источник

MySQL Server Error Codes and Messages 1600 — 1649

Message: Creation context of view `%s`.`%s’ is invalid

Message: Creation context of stored routine `%s`.`%s` is invalid

Message: Corrupted TRG file for table `%s`.`%s`

Message: Triggers for table `%s`.`%s` have no creation context

Message: Trigger creation context of table `%s`.`%s` is invalid

Message: Creation context of event `%s`.`%s` is invalid

Message: Cannot open table for trigger `%s`.`%s`

Message: Cannot create stored routine `%s`. Check warnings

Error: 1608 SQLSTATE: HY000 (ER_NEVER_USED)

Message: Ambiguous slave modes combination. %s

Message: The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.

Message: Corrupted replication event was detected

Message: Invalid column reference (%s) in LOAD DATA

Message: Being purged log %s was not found

Error: 1613 SQLSTATE: XA106 (ER_XA_RBTIMEOUT)

Message: XA_RBTIMEOUT: Transaction branch was rolled back: took too long

Error: 1614 SQLSTATE: XA102 (ER_XA_RBDEADLOCK)

Message: XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected

Error: 1615 SQLSTATE: HY000 (ER_NEED_REPREPARE)

Message: Prepared statement needs to be re-prepared

Message: DELAYED option not supported for table ‘%s’

Message: The master info structure does not exist

Message: option ignored

Message: Built-in plugins cannot be deleted

Error: 1620 SQLSTATE: HY000 (WARN_PLUGIN_BUSY)

Message: Plugin is busy and will be uninstalled on shutdown

Message: %s variable ‘%s’ is read-only. Use SET %s to assign the value

Message: Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted

Message: Unexpected master’s heartbeat data: %s

Message: The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).

Message: Bad schema for mysql.ndb_replication table. Message: %s

Message: Error in parsing conflict function. Message: %s

Message: Write to exceptions table failed. Message: %s»

Message: Comment for table ‘%s’ is too long (max = %lu)

Message: Comment for field ‘%s’ is too long (max = %lu)

Message: FUNCTION %s does not exist. Check the ‘Function Name Parsing and Resolution’ section in the Reference Manual

Error: 1631 SQLSTATE: HY000 (ER_DATABASE_NAME)

Error: 1632 SQLSTATE: HY000 (ER_TABLE_NAME)

Error: 1633 SQLSTATE: HY000 (ER_PARTITION_NAME)

Error: 1635 SQLSTATE: HY000 (ER_TEMPORARY_NAME)

Error: 1636 SQLSTATE: HY000 (ER_RENAMED_NAME)

Message: Too many active concurrent transactions

Message: Non-ASCII separator arguments are not fully supported

Message: debug sync point wait timed out

Message: debug sync point hit limit reached

Error: 1641 SQLSTATE: 42000 (ER_DUP_SIGNAL_SET)

Message: Duplicate condition information item ‘%s’

Error: 1642 SQLSTATE: 01000 (ER_SIGNAL_WARN)

Message: Unhandled user-defined warning condition

Message: Unhandled user-defined not found condition

Message: Unhandled user-defined exception condition

Message: RESIGNAL when handler not active

Message: SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE

Message: Data truncated for condition item ‘%s’

Message: Data too long for condition item ‘%s’

Error: 1649 SQLSTATE: HY000 (ER_UNKNOWN_LOCALE)

Источник

MacLochlainns Weblog

Michael McLaughlin’s Technical Blog

Archive for the ‘SUM function’ tag

Placement over substance

I was stunned when a SQL query raised an ERROR 1630 (42000) telling me the SUM function didn’t exist in MySQL 5.5.23. The fix was simple. The opening parenthesis of the SUM function must be on the same line as the SUM keyword without an intervening white space. Alternatively phrased, you can’t have a line return or white space between the SUM function name and the opening parenthesis of the call parameter list. The same rule doesn’t apply to the opening parenthesis of the FORMAT function and it seems to me that this parsing inconsistency is problematic.

Therefore, my surprise, observation, and complaint is that all functions don’t parse the same way, using the same rules. That is, unless you use specialized SQL_MODE settings. This assumption was borne out by Kolbe Kegel’s comment on this post, and there are 30 remaining built in functions that have specialized parsing and resolution markers.

A simplified version of the code that raises the error follows. As you’ll notice the opening parenthesis for the FORMAT and SUM function have intervening white space and a line return.

SELECT t.transaction_account AS «Transaction» , LPAD(FORMAT (SUM (CASE WHEN EXTRACT(MONTH FROM transaction_date) = 1 AND EXTRACT(YEAR FROM transaction_date) = 2011 THEN CASE WHEN t.transaction_type = cl.common_lookup_type THEN t.transaction_amount ELSE t.transaction_amount * -1 END END),2),10,’ ‘) AS «JAN» FROM TRANSACTION t CROSS JOIN common_lookup cl WHERE cl.common_lookup_table = ‘TRANSACTION’ AND cl.common_lookup_column = ‘TRANSACTION_TYPE’ AND cl.common_lookup_type = ‘DEBIT’ GROUP BY t.transaction_account;

Based on the comments, the SQL_MODE is:

It raises the following error:

ERROR 1630 (42000): FUNCTION studentdb.SUM does not exist. Check the ‘Function Name Parsing and Resolution’ section in the Reference Manual

Moving ONLY the opening parenthesis to the end of the SUM keyword (or removing the line return and white space from between the SUM keyword and opening parenthesis) prevents the error but it would be more convenient if it supported both approaches. It seems odd that an intervening line return and white space for the SUM function raises an exception while the same intervening line return and white space doesn’t raise an exception for the FORMAT function. It strikes me the parser should support both or reject both. Here’s the fixed code that works without enabling the IGNORE_SPACE SQL Mode option.

SELECT t.transaction_account AS «Transaction» , LPAD(FORMAT (SUM( CASE WHEN EXTRACT(MONTH FROM transaction_date) = 1 AND EXTRACT(YEAR FROM transaction_date) = 2011 THEN CASE WHEN t.transaction_type = cl.common_lookup_type THEN t.transaction_amount ELSE t.transaction_amount * -1 END END),2),10,’ ‘) AS «JAN» FROM TRANSACTION t CROSS JOIN common_lookup cl WHERE cl.common_lookup_table = ‘TRANSACTION’ AND cl.common_lookup_column = ‘TRANSACTION_TYPE’ AND cl.common_lookup_type = ‘DEBIT’ GROUP BY t.transaction_account;

As noted by the comments, adding the IGNORE_SPACE to the SQL_MODE lets both queries work without moving the open parenthesis. You can do that in a session with the following syntax (which is covered in an older post):

SET SQL_MODE=(SELECT CONCAT(@@sql_mode,’,IGNORE_SPACE’));

Источник

Русские Блоги

[MySQL] При вызове хранимой процедуры отображается ОШИБКА 1305 (42000): PROCEDURE test.sp1 не существует

Описание проблемы:

1. Создайте простую хранимую процедуру запроса в MySQL:

2. Затем используйте CALL для вызова этой хранимой процедуры, и ошибка ОШИБКА 1305 (42000): PROCEDURE test.sp1 не существует:

Исправление проблем:

1. Сначала подумайте, действительно ли эта хранимая процедура отсутствует, проверьте текущую хранимую процедуру и убедитесь, что хранимая процедура существует:

2. В это время я думал, что у пользователя нет разрешения на вызов текущей хранимой процедуры, и разрешение хранимой процедуры было предоставлено текущему пользователю. В это время произошла другая ошибка:

Это обнаруживается путем запроса данных, которые необходимо обновить текущую хранимую процедуру перед выполнением оператора авторизации:

Выполните вызов этой хранимой процедуры еще раз, и отобразится успешный вызов:

Интеллектуальная рекомендация

Реализация оценки приложения iOS

Есть два способа получить оценку приложения: перейти в App Store для оценки и оценка в приложении. 1. Перейдите в App Store, чтобы оценить ps: appid можно запросить в iTunes Connect 2. Встроенная оцен.

JS функциональное программирование (е)

Давайте рассмотрим простой пример, чтобы проиллюстрировать, как используется Reduce. Первый параметр Reduce — это то, что мы принимаем массив arrayOfNums, а второй параметр — функцию. Эта функция прин.

PWN_JarvisOJ_Level1

Nc первый Затем мы смотрим на декомпиляцию ida Перед «Hello, World! N» есть уязвимая_функция, проверьте эту функцию после ввода Видно, что только что появившийся странный адрес является пе.

Установка и развертывание Kubernetes

На самом деле, я опубликовал статью в этом разделе давным -давно, но она не достаточно подробно, и уровень не является ясным. Когда я развернулся сегодня, я увидел его достаточно (хотя это было успешн.

На стороне многопроцессорного сервера — (2) *

Обработка сигнала Родительский процесс часто очень занят, поэтому вы не можете просто вызвать функцию waitpid, чтобы дождаться завершения дочернего процесса. Затем обсудите решение. Обратитесь .

Источник

i have on my site 7 cron jobs that automatically do commands (y’all know cron purpose but..:)*
but they all throw out the same Error..

this is the cron jobs:

*/4 * * * *  /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:bookings:alertImminent >> /var/www/Alerts/log.log 2>&1
*/5 * * * *  /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:bookings:expire >> /var/www/Alerts/log.log 2>&1
*/5 * * * *  /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:bookings:validate >> /var/www/Alerts/log.log 2>&1
*/5 * * * *  /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:bookings:alertExpiring >> /var/www/Alerts/log.log 2>&1
10 */1 * * * /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:bookings:checkBankWires >> /var/www/Alerts/log.log 2>&1
30 17 * * *  /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:currency:update >> /var/www/Alerts/log.log 2>&1
30 2 * * *   /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico_listing_search:computeNotation >> /var/www/Alerts/log.log 2>&1
0 0 27 * *   /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:listings:alertUpdateCalendars >> /var/www/Alerts/log.log 2>&1

Here what’s i get in the log..:

13:50:02 ERROR     [console] Error thrown while running command "--env=prod cocorico:bookings:alertExpiring". Message: "An exception occurred while executing '

    SELECT  b0_.id AS id_0, b0_.start AS start_1, b0_.end AS end_2,
            b0_.start_time AS start_time_3, b0_.end_time AS end_time_4,
            b0_.status AS status_5, b0_.validated AS validated_6,
            b0_.amount AS amount_7, b0_.amount_fee_as_asker AS amount_fee_as_asker_8,
            b0_.amount_fee_as_offerer AS amount_fee_as_offerer_9,
            b0_.amount_total AS amount_total_10, b0_.cancellation_policy AS cancellation_policy_11,
            b0_.new_booking_at AS new_booking_at_12, b0_.payed_booking_at AS payed_booking_at_13,
            b0_.refused_booking_at AS refused_booking_at_14, b0_.canceled_asker_booking_at AS canceled_asker_booking_at_15,
            b0_.alerted_expiring AS alerted_expiring_16, b0_.alerted_imminent AS alerted_imminent_17,
            b0_.invoice_number AS invoice_number_18, b0_.refund_invoice_number AS refund_invoice_number_19,
            b0_.message AS message_20, b0_.time_zone_asker AS time_zone_asker_21,
            b0_.time_zone_offerer AS time_zone_offerer_22, b0_.mangopay_card_id AS mangopay_card_id_23,
            b0_.mangopay_card_pre_auth_id AS mangopay_card_pre_auth_id_24,
            b0_.mangopay_payin_pre_auth_id AS mangopay_payin_pre_auth_id_25,
            b0_.url_draft AS url_draft_26, b0_.amount_options AS amount_options_27,
            b0_.created_at AS created_at_28, b0_.updated_at AS updated_at_29,
            u1_.username AS username_30, u1_.username_canonical AS username_canonical_31,
            u1_.email AS email_32, u1_.email_canonical AS email_canonical_33,
            u1_.enabled AS enabled_34, u1_.salt AS salt_35, u1_.password AS password_36,
            u1_.last_login AS last_login_37, u1_.confirmation_token AS confirmation_token_38,
            u1_.password_requested_at AS password_requested_at_39,
            u1_.roles AS roles_40, u1_.id AS id_41, u1_.person_type AS person_type_42,
            u1_.user_type AS user_type_43, u1_.company_name AS company_name_44,
            u1_.last_name AS last_name_45, u1_.first_name AS first_name_46,
            u1_.phone_prefix AS phone_prefix_47, u1_.phone AS phone_48,
            u1_.birthday AS birthday_49, u1_.nationality AS nationality_50,
            u1_.country_of_residence AS country_of_residence_51, u1_.profession AS profession_52,
            u1_.iban AS iban_53, u1_.bic AS bic_54, u1_.bank_owner_name AS bank_owner_name_55,
            u1_.bank_owner_address AS bank_owner_address_56, u1_.annual_income AS annual_income_57,
            u1_.phone_verified AS phone_verified_58, u1_.email_verified AS email_verified_59,
            u1_.id_card_verified AS id_card_verified_60, u1_.nb_bookings_offerer AS nb_bookings_offerer_61, u1_.nb_bookings_asker AS nb_bookings_asker_62, u1_.fee_as_asker AS fee_as_asker_63, u1_.fee_as_offerer AS fee_as_offerer_64, u1_.average_rating_as_asker AS average_rating_as_asker_65, u1_.average_rating_as_offerer AS average_rating_as_offerer_66, u1_.mother_tongue AS mother_tongue_67, u1_.answer_delay AS answer_delay_68, u1_.time_zone AS time_zone_69, u1_.mangopay_id AS mangopay_id_70, u1_.mangopay_wallet_id AS mangopay_wallet_id_71, u1_.mangopay_bank_account_id AS mangopay_bank_account_id_72, u1_.created_at AS created_at_73, u1_.updated_at AS updated_at_74, u1_.slug AS slug_75, u2_.id AS id_76, u2_.facebook_id AS facebook_id_77, u2_.link AS link_78, u2_.last_name AS last_name_79, u2_.first_name AS first_name_80, u2_.birthday AS birthday_81, u2_.address AS address_82, u2_.verified AS verified_83, u2_.location AS location_84, u2_.location_id AS location_id_85, u2_.hometown AS hometown_86, u2_.hometown_id AS hometown_id_87, u2_.gender AS gender_88, u2_.locale AS locale_89, u2_.timezone AS timezone_90, u2_.nb_friends AS nb_friends_91, u2_.picture AS picture_92, u2_.created_at AS created_at_93, u2_.updated_at AS updated_at_94, l3_.id AS id_95, l3_.status AS status_96, l3_.type AS type_97, l3_.price AS price_98, l3_.certified AS certified_99, l3_.min_duration AS min_duration_100, l3_.max_duration AS max_duration_101, l3_.cancellation_policy AS cancellation_policy_102, l3_.average_rating AS average_rating_103, l3_.comment_count AS comment_count_104, l3_.admin_notation AS admin_notation_105, l3_.availabilities_updated_at AS availabilities_updated_at_106, l3_.platform_notation AS platform_notation_107, l3_.created_at AS created_at_108, l3_.updated_at AS updated_at_109, b4_.id AS id_110, b4_.status AS status_111, b4_.amount AS amount_112, b4_.payed_at AS payed_at_113, b4_.mangopay_transfer_id AS mangopay_transfer_id_114, b4_.mangopay_payout_id AS mangopay_payout_id_115, b4_.created_at AS created_at_116, b4_.updated_at AS updated_at_117, b5_.id AS id_118, b5_.status AS status_119, b5_.amount AS amount_120, b5_.payed_at AS payed_at_121, b5_.mangopay_refund_id AS mangopay_refund_id_122, b5_.created_at AS created_at_123, b5_.updated_at AS updated_at_124, m6_.subject AS subject_125, m6_.created_at AS created_at_126, m6_.is_spam AS is_spam_127, m6_.id AS id_128, l7_.title AS title_129, l7_.description AS description_130, l7_.rules AS rules_131, l7_.locale AS locale_132, l7_.id AS id_133, l7_.slug AS slug_134, u8_.username AS username_135, u8_.username_canonical AS username_canonical_136, u8_.email AS email_137, u8_.email_canonical AS email_canonical_138, u8_.enabled AS enabled_139, u8_.salt AS salt_140, u8_.password AS password_141, u8_.last_login AS last_login_142, u8_.confirmation_token AS confirmation_token_143, u8_.password_requested_at AS password_requested_at_144, u8_.roles AS roles_145, u8_.id AS id_146, u8_.person_type AS person_type_147, u8_.user_type AS user_type_148, u8_.company_name AS company_name_149, u8_.last_name AS last_name_150, u8_.first_name AS first_name_151, u8_.phone_prefix AS phone_prefix_152, u8_.phone AS phone_153, u8_.birthday AS birthday_154, u8_.nationality AS nationality_155, u8_.country_of_residence AS country_of_residence_156, u8_.profession AS profession_157, u8_.iban AS iban_158, u8_.bic AS bic_159, u8_.bank_owner_name AS bank_owner_name_160, u8_.bank_owner_address AS bank_owner_address_161, u8_.annual_income AS annual_income_162, u8_.phone_verified AS phone_verified_163, u8_.email_verified AS email_verified_164, u8_.id_card_verified AS id_card_verified_165, u8_.nb_bookings_offerer AS nb_bookings_offerer_166, u8_.nb_bookings_asker AS nb_bookings_asker_167, u8_.fee_as_asker AS fee_as_asker_168, u8_.fee_as_offerer AS fee_as_offerer_169, u8_.average_rating_as_asker AS average_rating_as_asker_170, u8_.average_rating_as_offerer AS average_rating_as_offerer_171, u8_.mother_tongue AS mother_tongue_172, u8_.answer_delay AS answer_delay_173, u8_.time_zone AS time_zone_174, u8_.mangopay_id AS mangopay_id_175, u8_.mangopay_wallet_id AS mangopay_wallet_id_176, u8_.mangopay_bank_account_id AS mangopay_bank_account_id_177, u8_.created_at AS created_at_178, u8_.updated_at AS updated_at_179, u8_.slug AS slug_180, u9_.id AS id_181, u9_.facebook_id AS facebook_id_182, u9_.link AS link_183, u9_.last_name AS last_name_184, u9_.first_name AS first_name_185, u9_.birthday AS birthday_186, u9_.address AS address_187, u9_.verified AS verified_188, u9_.location AS location_189, u9_.location_id AS location_id_190, u9_.hometown AS hometown_191, u9_.hometown_id AS hometown_id_192, u9_.gender AS gender_193, u9_.locale AS locale_194, u9_.timezone AS timezone_195, u9_.nb_friends AS nb_friends_196, u9_.picture AS picture_197, u9_.created_at AS created_at_198, u9_.updated_at AS updated_at_199, b0_.user_id AS user_id_200, b0_.listing_id AS listing_id_201, u2_.user_id AS user_id_202, l3_.user_id AS user_id_203, l3_.location_id AS location_id_204, b4_.user_id AS user_id_205, b4_.booking_id AS booking_id_206, b5_.user_id AS user_id_207, b5_.booking_id AS booking_id_208, m6_.created_by_id AS created_by_id_209, m6_.listing_id AS listing_id_210, m6_.booking_id AS booking_id_211, l7_.translatable_id AS translatable_id_212, u9_.user_id AS user_id_213
        FROM  booking b0_
        LEFT JOIN  `user` u1_  ON b0_.user_id = u1_.id
        LEFT JOIN  `user_facebook` u2_  ON u1_.id = u2_.user_id
        LEFT JOIN  listing l3_  ON b0_.listing_id = l3_.id
        LEFT JOIN  booking_bank_wire b4_  ON b0_.id = b4_.booking_id
        LEFT JOIN  booking_payin_refund b5_  ON b0_.id = b5_.booking_id
        LEFT JOIN  message_thread m6_  ON b0_.id = m6_.booking_id
        LEFT JOIN  listing_translation l7_  ON l3_.id = l7_.translatable_id
        LEFT JOIN  `user` u8_  ON l3_.user_id = u8_.id
        LEFT JOIN  `user_facebook` u9_  ON u8_.id = u9_.user_id
        WHERE  b0_.status IN (?)
          AND  (b0_.new_booking_at <= ?
                  OR  CONCAT(DATE_FORMAT (b0_.start,'%Y-%m-%d'), ' ',
                             DATE_FORMAT (b0_.start_time, '%H:%i:%s')) <= ?
               )
          AND  b0_.alerted_expiring = ?'

 with params [1, "2019-10-02 15:50:02", "2019-10-04 19:50:02", 0]:

And :

  SQLSTATE[42000]: Syntax error or access violation: 1630 FUNCTION dbparty.DA
  TE_FORMAT does not exist. Check the 'Function Name Parsing and Resolution'
  section in the Reference Manual


In PDOStatement.php line 144:

  SQLSTATE[42000]: Syntax error or access violation: 1630 FUNCTION dbparty.DA
  TE_FORMAT does not exist. Check the 'Function Name Parsing and Resolution'
  section in the Reference Manual


In PDOStatement.php line 142:

  SQLSTATE[42000]: Syntax error or access violation: 1630 FUNCTION dbparty.DA
  TE_FORMAT does not exist. Check the 'Function Name Parsing and Resolution'
  section in the Reference Manual

i have on my site 7 cron jobs that automatically do commands (y’all know cron purpose but..:)*
but they all throw out the same Error..

this is the cron jobs:

*/4 * * * *  /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:bookings:alertImminent >> /var/www/Alerts/log.log 2>&1
*/5 * * * *  /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:bookings:expire >> /var/www/Alerts/log.log 2>&1
*/5 * * * *  /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:bookings:validate >> /var/www/Alerts/log.log 2>&1
*/5 * * * *  /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:bookings:alertExpiring >> /var/www/Alerts/log.log 2>&1
10 */1 * * * /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:bookings:checkBankWires >> /var/www/Alerts/log.log 2>&1
30 17 * * *  /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:currency:update >> /var/www/Alerts/log.log 2>&1
30 2 * * *   /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico_listing_search:computeNotation >> /var/www/Alerts/log.log 2>&1
0 0 27 * *   /usr/bin/php7.3 /var/www/Symfony/bin/console --env=prod cocorico:listings:alertUpdateCalendars >> /var/www/Alerts/log.log 2>&1

Here what’s i get in the log..:

13:50:02 ERROR     [console] Error thrown while running command "--env=prod cocorico:bookings:alertExpiring". Message: "An exception occurred while executing '

    SELECT  b0_.id AS id_0, b0_.start AS start_1, b0_.end AS end_2,
            b0_.start_time AS start_time_3, b0_.end_time AS end_time_4,
            b0_.status AS status_5, b0_.validated AS validated_6,
            b0_.amount AS amount_7, b0_.amount_fee_as_asker AS amount_fee_as_asker_8,
            b0_.amount_fee_as_offerer AS amount_fee_as_offerer_9,
            b0_.amount_total AS amount_total_10, b0_.cancellation_policy AS cancellation_policy_11,
            b0_.new_booking_at AS new_booking_at_12, b0_.payed_booking_at AS payed_booking_at_13,
            b0_.refused_booking_at AS refused_booking_at_14, b0_.canceled_asker_booking_at AS canceled_asker_booking_at_15,
            b0_.alerted_expiring AS alerted_expiring_16, b0_.alerted_imminent AS alerted_imminent_17,
            b0_.invoice_number AS invoice_number_18, b0_.refund_invoice_number AS refund_invoice_number_19,
            b0_.message AS message_20, b0_.time_zone_asker AS time_zone_asker_21,
            b0_.time_zone_offerer AS time_zone_offerer_22, b0_.mangopay_card_id AS mangopay_card_id_23,
            b0_.mangopay_card_pre_auth_id AS mangopay_card_pre_auth_id_24,
            b0_.mangopay_payin_pre_auth_id AS mangopay_payin_pre_auth_id_25,
            b0_.url_draft AS url_draft_26, b0_.amount_options AS amount_options_27,
            b0_.created_at AS created_at_28, b0_.updated_at AS updated_at_29,
            u1_.username AS username_30, u1_.username_canonical AS username_canonical_31,
            u1_.email AS email_32, u1_.email_canonical AS email_canonical_33,
            u1_.enabled AS enabled_34, u1_.salt AS salt_35, u1_.password AS password_36,
            u1_.last_login AS last_login_37, u1_.confirmation_token AS confirmation_token_38,
            u1_.password_requested_at AS password_requested_at_39,
            u1_.roles AS roles_40, u1_.id AS id_41, u1_.person_type AS person_type_42,
            u1_.user_type AS user_type_43, u1_.company_name AS company_name_44,
            u1_.last_name AS last_name_45, u1_.first_name AS first_name_46,
            u1_.phone_prefix AS phone_prefix_47, u1_.phone AS phone_48,
            u1_.birthday AS birthday_49, u1_.nationality AS nationality_50,
            u1_.country_of_residence AS country_of_residence_51, u1_.profession AS profession_52,
            u1_.iban AS iban_53, u1_.bic AS bic_54, u1_.bank_owner_name AS bank_owner_name_55,
            u1_.bank_owner_address AS bank_owner_address_56, u1_.annual_income AS annual_income_57,
            u1_.phone_verified AS phone_verified_58, u1_.email_verified AS email_verified_59,
            u1_.id_card_verified AS id_card_verified_60, u1_.nb_bookings_offerer AS nb_bookings_offerer_61, u1_.nb_bookings_asker AS nb_bookings_asker_62, u1_.fee_as_asker AS fee_as_asker_63, u1_.fee_as_offerer AS fee_as_offerer_64, u1_.average_rating_as_asker AS average_rating_as_asker_65, u1_.average_rating_as_offerer AS average_rating_as_offerer_66, u1_.mother_tongue AS mother_tongue_67, u1_.answer_delay AS answer_delay_68, u1_.time_zone AS time_zone_69, u1_.mangopay_id AS mangopay_id_70, u1_.mangopay_wallet_id AS mangopay_wallet_id_71, u1_.mangopay_bank_account_id AS mangopay_bank_account_id_72, u1_.created_at AS created_at_73, u1_.updated_at AS updated_at_74, u1_.slug AS slug_75, u2_.id AS id_76, u2_.facebook_id AS facebook_id_77, u2_.link AS link_78, u2_.last_name AS last_name_79, u2_.first_name AS first_name_80, u2_.birthday AS birthday_81, u2_.address AS address_82, u2_.verified AS verified_83, u2_.location AS location_84, u2_.location_id AS location_id_85, u2_.hometown AS hometown_86, u2_.hometown_id AS hometown_id_87, u2_.gender AS gender_88, u2_.locale AS locale_89, u2_.timezone AS timezone_90, u2_.nb_friends AS nb_friends_91, u2_.picture AS picture_92, u2_.created_at AS created_at_93, u2_.updated_at AS updated_at_94, l3_.id AS id_95, l3_.status AS status_96, l3_.type AS type_97, l3_.price AS price_98, l3_.certified AS certified_99, l3_.min_duration AS min_duration_100, l3_.max_duration AS max_duration_101, l3_.cancellation_policy AS cancellation_policy_102, l3_.average_rating AS average_rating_103, l3_.comment_count AS comment_count_104, l3_.admin_notation AS admin_notation_105, l3_.availabilities_updated_at AS availabilities_updated_at_106, l3_.platform_notation AS platform_notation_107, l3_.created_at AS created_at_108, l3_.updated_at AS updated_at_109, b4_.id AS id_110, b4_.status AS status_111, b4_.amount AS amount_112, b4_.payed_at AS payed_at_113, b4_.mangopay_transfer_id AS mangopay_transfer_id_114, b4_.mangopay_payout_id AS mangopay_payout_id_115, b4_.created_at AS created_at_116, b4_.updated_at AS updated_at_117, b5_.id AS id_118, b5_.status AS status_119, b5_.amount AS amount_120, b5_.payed_at AS payed_at_121, b5_.mangopay_refund_id AS mangopay_refund_id_122, b5_.created_at AS created_at_123, b5_.updated_at AS updated_at_124, m6_.subject AS subject_125, m6_.created_at AS created_at_126, m6_.is_spam AS is_spam_127, m6_.id AS id_128, l7_.title AS title_129, l7_.description AS description_130, l7_.rules AS rules_131, l7_.locale AS locale_132, l7_.id AS id_133, l7_.slug AS slug_134, u8_.username AS username_135, u8_.username_canonical AS username_canonical_136, u8_.email AS email_137, u8_.email_canonical AS email_canonical_138, u8_.enabled AS enabled_139, u8_.salt AS salt_140, u8_.password AS password_141, u8_.last_login AS last_login_142, u8_.confirmation_token AS confirmation_token_143, u8_.password_requested_at AS password_requested_at_144, u8_.roles AS roles_145, u8_.id AS id_146, u8_.person_type AS person_type_147, u8_.user_type AS user_type_148, u8_.company_name AS company_name_149, u8_.last_name AS last_name_150, u8_.first_name AS first_name_151, u8_.phone_prefix AS phone_prefix_152, u8_.phone AS phone_153, u8_.birthday AS birthday_154, u8_.nationality AS nationality_155, u8_.country_of_residence AS country_of_residence_156, u8_.profession AS profession_157, u8_.iban AS iban_158, u8_.bic AS bic_159, u8_.bank_owner_name AS bank_owner_name_160, u8_.bank_owner_address AS bank_owner_address_161, u8_.annual_income AS annual_income_162, u8_.phone_verified AS phone_verified_163, u8_.email_verified AS email_verified_164, u8_.id_card_verified AS id_card_verified_165, u8_.nb_bookings_offerer AS nb_bookings_offerer_166, u8_.nb_bookings_asker AS nb_bookings_asker_167, u8_.fee_as_asker AS fee_as_asker_168, u8_.fee_as_offerer AS fee_as_offerer_169, u8_.average_rating_as_asker AS average_rating_as_asker_170, u8_.average_rating_as_offerer AS average_rating_as_offerer_171, u8_.mother_tongue AS mother_tongue_172, u8_.answer_delay AS answer_delay_173, u8_.time_zone AS time_zone_174, u8_.mangopay_id AS mangopay_id_175, u8_.mangopay_wallet_id AS mangopay_wallet_id_176, u8_.mangopay_bank_account_id AS mangopay_bank_account_id_177, u8_.created_at AS created_at_178, u8_.updated_at AS updated_at_179, u8_.slug AS slug_180, u9_.id AS id_181, u9_.facebook_id AS facebook_id_182, u9_.link AS link_183, u9_.last_name AS last_name_184, u9_.first_name AS first_name_185, u9_.birthday AS birthday_186, u9_.address AS address_187, u9_.verified AS verified_188, u9_.location AS location_189, u9_.location_id AS location_id_190, u9_.hometown AS hometown_191, u9_.hometown_id AS hometown_id_192, u9_.gender AS gender_193, u9_.locale AS locale_194, u9_.timezone AS timezone_195, u9_.nb_friends AS nb_friends_196, u9_.picture AS picture_197, u9_.created_at AS created_at_198, u9_.updated_at AS updated_at_199, b0_.user_id AS user_id_200, b0_.listing_id AS listing_id_201, u2_.user_id AS user_id_202, l3_.user_id AS user_id_203, l3_.location_id AS location_id_204, b4_.user_id AS user_id_205, b4_.booking_id AS booking_id_206, b5_.user_id AS user_id_207, b5_.booking_id AS booking_id_208, m6_.created_by_id AS created_by_id_209, m6_.listing_id AS listing_id_210, m6_.booking_id AS booking_id_211, l7_.translatable_id AS translatable_id_212, u9_.user_id AS user_id_213
        FROM  booking b0_
        LEFT JOIN  `user` u1_  ON b0_.user_id = u1_.id
        LEFT JOIN  `user_facebook` u2_  ON u1_.id = u2_.user_id
        LEFT JOIN  listing l3_  ON b0_.listing_id = l3_.id
        LEFT JOIN  booking_bank_wire b4_  ON b0_.id = b4_.booking_id
        LEFT JOIN  booking_payin_refund b5_  ON b0_.id = b5_.booking_id
        LEFT JOIN  message_thread m6_  ON b0_.id = m6_.booking_id
        LEFT JOIN  listing_translation l7_  ON l3_.id = l7_.translatable_id
        LEFT JOIN  `user` u8_  ON l3_.user_id = u8_.id
        LEFT JOIN  `user_facebook` u9_  ON u8_.id = u9_.user_id
        WHERE  b0_.status IN (?)
          AND  (b0_.new_booking_at <= ?
                  OR  CONCAT(DATE_FORMAT (b0_.start,'%Y-%m-%d'), ' ',
                             DATE_FORMAT (b0_.start_time, '%H:%i:%s')) <= ?
               )
          AND  b0_.alerted_expiring = ?'

 with params [1, "2019-10-02 15:50:02", "2019-10-04 19:50:02", 0]:

And :

  SQLSTATE[42000]: Syntax error or access violation: 1630 FUNCTION dbparty.DA
  TE_FORMAT does not exist. Check the 'Function Name Parsing and Resolution'
  section in the Reference Manual


In PDOStatement.php line 144:

  SQLSTATE[42000]: Syntax error or access violation: 1630 FUNCTION dbparty.DA
  TE_FORMAT does not exist. Check the 'Function Name Parsing and Resolution'
  section in the Reference Manual


In PDOStatement.php line 142:

  SQLSTATE[42000]: Syntax error or access violation: 1630 FUNCTION dbparty.DA
  TE_FORMAT does not exist. Check the 'Function Name Parsing and Resolution'
  section in the Reference Manual