Sql state 58p01 ошибка

I’m learning PostgreSQL, and i run into problem:
I have created table and trying to export it, but I have all the time same error

SQL Error [58P01]: ERROR: could not open file "D:\Janis\Mācības\SQL\Test\typestest.txt" for writing: No such file or directory
Hint: COPY TO instructs the PostgreSQL server process to write a file. You may want a client-side facility such as psql's \copy.

Script that I’m running:

CREATE TABLE char_data_types (
    varchar_column varchar(10),
    char_column char(10),
    text_column text
);

INSERT INTO char_data_types
VALUES
    ('abc', 'abc', 'abc'),
    ('defghi', 'defghi', 'defghi');

COPY char_data_types TO 'D:\Janis\Mācības\SQL\Test\typestest.txt'
WITH (FORMAT CSV, HEADER, DELIMITER '|');

I have taken off all possible security restriction from file typestest.txt

Jens's user avatar

Jens

67.9k15 gold badges99 silver badges113 bronze badges

asked Jan 7 at 11:56

Jānis's user avatar

5

There is no directory D:\Janis\Mācības\SQL\Test on the PostgreSQL server. Note that COPY writes to the database server, no the client (the statement runs on the server, and the server cannot access the client machine).

To export the data to the client machine, you have to use psql so that you can use \copy:

\copy char_data_types TO 'D:\Janis\Mācības\SQL\Test\typestest.txt' WITH (FORMAT CSV, HEADER, DELIMITER '|')

The command has to be in a single line.

answered Jan 8 at 5:01

Laurenz Albe's user avatar

Laurenz AlbeLaurenz Albe

211k17 gold badges207 silver badges266 bronze badges

3

Published: 29 Dec 2022
Last Modified Date: 29 Dec 2022

Issue

The following error occurs intermittently when refreshing an extract via Bridge using legacy schedules

Unable to refresh the data source because of a query compilation.
status code = 5029, Failed to refresh data source: xxxxxx due to the following error: [SQLSTATE:58P01] Cannot create temp database: The transient database could not be created

Environment

  • Tableau Bridge
  • Tableau Cloud

Resolution

Use the Online Schedule as a workaround.

Note: Support for Bridge (legacy) schedules will be removed in a future release. To ensure a smooth transition, we recommend you use Online refresh schedules.

Cause

This is a known issue when using legacy schedules. 
 

Additional Information

Migrate from Bridge (legacy) to Online schedules




Error Code Condition Name
Class 00 — Successful Completion
00000 successful_completion
Class 01 — Warning
01000 warning
0100C dynamic_result_sets_returned
01008 implicit_zero_bit_padding
01003 null_value_eliminated_in_set_function
01007 privilege_not_granted
01006 privilege_not_revoked
01004 string_data_right_truncation
01P01 deprecated_feature
Class 02 — No Data (this is also a warning class per the SQL standard)
02000 no_data
02001 no_additional_dynamic_result_sets_returned
Class 03 — SQL Statement Not Yet Complete
03000 sql_statement_not_yet_complete
Class 08 — Connection Exception
08000 connection_exception
08003 connection_does_not_exist
08006 connection_failure
08001 sqlclient_unable_to_establish_sqlconnection
08004 sqlserver_rejected_establishment_of_sqlconnection
08007 transaction_resolution_unknown
08P01 protocol_violation
Class 09 — Triggered Action Exception
09000 triggered_action_exception
Class 0A — Feature Not Supported
0A000 feature_not_supported
Class 0B — Invalid Transaction Initiation
0B000 invalid_transaction_initiation
Class 0F — Locator Exception
0F000 locator_exception
0F001 invalid_locator_specification
Class 0L — Invalid Grantor
0L000 invalid_grantor
0LP01 invalid_grant_operation
Class 0P — Invalid Role Specification
0P000 invalid_role_specification
Class 0Z — Diagnostics Exception
0Z000 diagnostics_exception
0Z002 stacked_diagnostics_accessed_without_active_handler
Class 20 — Case Not Found
20000 case_not_found
Class 21 — Cardinality Violation
21000 cardinality_violation
Class 22 — Data Exception
22000 data_exception
2202E array_subscript_error
22021 character_not_in_repertoire
22008 datetime_field_overflow
22012 division_by_zero
22005 error_in_assignment
2200B escape_character_conflict
22022 indicator_overflow
22015 interval_field_overflow
2201E invalid_argument_for_logarithm
22014 invalid_argument_for_ntile_function
22016 invalid_argument_for_nth_value_function
2201F invalid_argument_for_power_function
2201G invalid_argument_for_width_bucket_function
22018 invalid_character_value_for_cast
22007 invalid_datetime_format
22019 invalid_escape_character
2200D invalid_escape_octet
22025 invalid_escape_sequence
22P06 nonstandard_use_of_escape_character
22010 invalid_indicator_parameter_value
22023 invalid_parameter_value
22013 invalid_preceding_or_following_size
2201B invalid_regular_expression
2201W invalid_row_count_in_limit_clause
2201X invalid_row_count_in_result_offset_clause
2202H invalid_tablesample_argument
2202G invalid_tablesample_repeat
22009 invalid_time_zone_displacement_value
2200C invalid_use_of_escape_character
2200G most_specific_type_mismatch
22004 null_value_not_allowed
22002 null_value_no_indicator_parameter
22003 numeric_value_out_of_range
2200H sequence_generator_limit_exceeded
22026 string_data_length_mismatch
22001 string_data_right_truncation
22011 substring_error
22027 trim_error
22024 unterminated_c_string
2200F zero_length_character_string
22P01 floating_point_exception
22P02 invalid_text_representation
22P03 invalid_binary_representation
22P04 bad_copy_file_format
22P05 untranslatable_character
2200L not_an_xml_document
2200M invalid_xml_document
2200N invalid_xml_content
2200S invalid_xml_comment
2200T invalid_xml_processing_instruction
22030 duplicate_json_object_key_value
22031 invalid_argument_for_sql_json_datetime_function
22032 invalid_json_text
22033 invalid_sql_json_subscript
22034 more_than_one_sql_json_item
22035 no_sql_json_item
22036 non_numeric_sql_json_item
22037 non_unique_keys_in_a_json_object
22038 singleton_sql_json_item_required
22039 sql_json_array_not_found
2203A sql_json_member_not_found
2203B sql_json_number_not_found
2203C sql_json_object_not_found
2203D too_many_json_array_elements
2203E too_many_json_object_members
2203F sql_json_scalar_required
2203G sql_json_item_cannot_be_cast_to_target_type
Class 23 — Integrity Constraint Violation
23000 integrity_constraint_violation
23001 restrict_violation
23502 not_null_violation
23503 foreign_key_violation
23505 unique_violation
23514 check_violation
23P01 exclusion_violation
Class 24 — Invalid Cursor State
24000 invalid_cursor_state
Class 25 — Invalid Transaction State
25000 invalid_transaction_state
25001 active_sql_transaction
25002 branch_transaction_already_active
25008 held_cursor_requires_same_isolation_level
25003 inappropriate_access_mode_for_branch_transaction
25004 inappropriate_isolation_level_for_branch_transaction
25005 no_active_sql_transaction_for_branch_transaction
25006 read_only_sql_transaction
25007 schema_and_data_statement_mixing_not_supported
25P01 no_active_sql_transaction
25P02 in_failed_sql_transaction
25P03 idle_in_transaction_session_timeout
Class 26 — Invalid SQL Statement Name
26000 invalid_sql_statement_name
Class 27 — Triggered Data Change Violation
27000 triggered_data_change_violation
Class 28 — Invalid Authorization Specification
28000 invalid_authorization_specification
28P01 invalid_password
Class 2B — Dependent Privilege Descriptors Still Exist
2B000 dependent_privilege_descriptors_still_exist
2BP01 dependent_objects_still_exist
Class 2D — Invalid Transaction Termination
2D000 invalid_transaction_termination
Class 2F — SQL Routine Exception
2F000 sql_routine_exception
2F005 function_executed_no_return_statement
2F002 modifying_sql_data_not_permitted
2F003 prohibited_sql_statement_attempted
2F004 reading_sql_data_not_permitted
Class 34 — Invalid Cursor Name
34000 invalid_cursor_name
Class 38 — External Routine Exception
38000 external_routine_exception
38001 containing_sql_not_permitted
38002 modifying_sql_data_not_permitted
38003 prohibited_sql_statement_attempted
38004 reading_sql_data_not_permitted
Class 39 — External Routine Invocation Exception
39000 external_routine_invocation_exception
39001 invalid_sqlstate_returned
39004 null_value_not_allowed
39P01 trigger_protocol_violated
39P02 srf_protocol_violated
39P03 event_trigger_protocol_violated
Class 3B — Savepoint Exception
3B000 savepoint_exception
3B001 invalid_savepoint_specification
Class 3D — Invalid Catalog Name
3D000 invalid_catalog_name
Class 3F — Invalid Schema Name
3F000 invalid_schema_name
Class 40 — Transaction Rollback
40000 transaction_rollback
40002 transaction_integrity_constraint_violation
40001 serialization_failure
40003 statement_completion_unknown
40P01 deadlock_detected
Class 42 — Syntax Error or Access Rule Violation
42000 syntax_error_or_access_rule_violation
42601 syntax_error
42501 insufficient_privilege
42846 cannot_coerce
42803 grouping_error
42P20 windowing_error
42P19 invalid_recursion
42830 invalid_foreign_key
42602 invalid_name
42622 name_too_long
42939 reserved_name
42804 datatype_mismatch
42P18 indeterminate_datatype
42P21 collation_mismatch
42P22 indeterminate_collation
42809 wrong_object_type
428C9 generated_always
42703 undefined_column
42883 undefined_function
42P01 undefined_table
42P02 undefined_parameter
42704 undefined_object
42701 duplicate_column
42P03 duplicate_cursor
42P04 duplicate_database
42723 duplicate_function
42P05 duplicate_prepared_statement
42P06 duplicate_schema
42P07 duplicate_table
42712 duplicate_alias
42710 duplicate_object
42702 ambiguous_column
42725 ambiguous_function
42P08 ambiguous_parameter
42P09 ambiguous_alias
42P10 invalid_column_reference
42611 invalid_column_definition
42P11 invalid_cursor_definition
42P12 invalid_database_definition
42P13 invalid_function_definition
42P14 invalid_prepared_statement_definition
42P15 invalid_schema_definition
42P16 invalid_table_definition
42P17 invalid_object_definition
Class 44 — WITH CHECK OPTION Violation
44000 with_check_option_violation
Class 53 — Insufficient Resources
53000 insufficient_resources
53100 disk_full
53200 out_of_memory
53300 too_many_connections
53400 configuration_limit_exceeded
Class 54 — Program Limit Exceeded
54000 program_limit_exceeded
54001 statement_too_complex
54011 too_many_columns
54023 too_many_arguments
Class 55 — Object Not In Prerequisite State
55000 object_not_in_prerequisite_state
55006 object_in_use
55P02 cant_change_runtime_param
55P03 lock_not_available
55P04 unsafe_new_enum_value_usage
Class 57 — Operator Intervention
57000 operator_intervention
57014 query_canceled
57P01 admin_shutdown
57P02 crash_shutdown
57P03 cannot_connect_now
57P04 database_dropped
57P05 idle_session_timeout
Class 58 — System Error (errors external to PostgreSQL itself)
58000 system_error
58030 io_error
58P01 undefined_file
58P02 duplicate_file
Class 72 — Snapshot Failure
72000 snapshot_too_old
Class F0 — Configuration File Error
F0000 config_file_error
F0001 lock_file_exists
Class HV — Foreign Data Wrapper Error (SQL/MED)
HV000 fdw_error
HV005 fdw_column_name_not_found
HV002 fdw_dynamic_parameter_value_needed
HV010 fdw_function_sequence_error
HV021 fdw_inconsistent_descriptor_information
HV024 fdw_invalid_attribute_value
HV007 fdw_invalid_column_name
HV008 fdw_invalid_column_number
HV004 fdw_invalid_data_type
HV006 fdw_invalid_data_type_descriptors
HV091 fdw_invalid_descriptor_field_identifier
HV00B fdw_invalid_handle
HV00C fdw_invalid_option_index
HV00D fdw_invalid_option_name
HV090 fdw_invalid_string_length_or_buffer_length
HV00A fdw_invalid_string_format
HV009 fdw_invalid_use_of_null_pointer
HV014 fdw_too_many_handles
HV001 fdw_out_of_memory
HV00P fdw_no_schemas
HV00J fdw_option_name_not_found
HV00K fdw_reply_handle
HV00Q fdw_schema_not_found
HV00R fdw_table_not_found
HV00L fdw_unable_to_create_execution
HV00M fdw_unable_to_create_reply
HV00N fdw_unable_to_establish_connection
Class P0 — PL/pgSQL Error
P0000 plpgsql_error
P0001 raise_exception
P0002 no_data_found
P0003 too_many_rows
P0004 assert_failure
Class XX — Internal Error
XX000 internal_error
XX001 data_corrupted
XX002 index_corrupted

I’m trying to import a CSV file into postgresql database.
First of all I tried following query:

copy temporaryData
from '/home/milad/Desktop/myFolder/csvFiles/test.csv'
delimiter ',' csv;

But it gave me below Error:

SQL Error [42501]: ERROR: could not open file "/home/milad/Desktop/myFolder/test.csv" for reading: Permission denied

This error is reasonable as suggested by this thread and also by postgresql tutorial:

Notice that the file must be read directly by the PostgreSQL server, not by the client application. Therefore, it must be accessible by the PostgreSQL server machine. Also, you need to have superuser access in order to execute the COPY statement successfully.

Since I don’t like to change my system permissions just to import a file, To solve this issue I decided to move my CSV file to /tmp/ directory which is suggested by this answer.

Then I tried to run below script:

create or replace procedure loadInstructorOfCourses()
language plpgsql
as $$
begin 
    create table temporaryData(
        courseSectionID varchar(10),
        instructorID    varchar(25),
        courseTitle     varchar(50)
    );

    copy temporaryData
    from '/tmp/test.csv'
    delimiter ',' csv;

    drop table temporaryData;
end;$$;

call loadInstructorOfCourses();

And now it gives me below error:

SQL Error [58P01]: ERROR: could not open file "/tmp/test.csv" for reading: No such file or directory

But I’m sure the file has read permission for others and also it’s available:

> ls -l -d /tmp
drwxrwxrwt 25 root root 700 Oct 20 09:53 /tmp
> ls -l /tmp/test.csv
-rw-r--r-- 1 milad milad 6700 Oct 20 09:53 /tmp/test.csv

Why does this problem happen and how to resolve it?

INFO:
My OS is Manjaro KDE:

> uname -r
5.4.150-1-MANJARO

And also I use DBeaver to connect to postgresql server and run my scripts.

UPDATES: Using psql I have the same issue too. When I connect to db by psql:

psql -U postgres -d IUTPlanning

and run my procedure:

call loadInstructorOfCourses();

I’ll get the same error:

ERROR:  could not open file "/tmp/test.csv" for reading: No such file or directory
HINT:  COPY FROM instructs the PostgreSQL server process to read a file. You may want a client-side facility such as psql's copy.
CONTEXT:  SQL statement "copy temporaryData
        from '/tmp/test.csv'
        delimiter ',' csv"
PL/pgSQL function loadinstructorofcourses() line 9 at SQL statement

Problem

CDC for Postgresql : 11.4

Postgresql:11

When creating cdc for postgresql instance, got below error:

Cannot create changes:A SQL exception has occurred. The SQL error code is ‘0’. The SQL state is: 58P01. The error message is:

ERROR: could not access file «test_decoding»: No such file or directory

Symptom

Cannot create changes:A SQL exception has occurred. The SQL error code is ‘0’. The SQL state is: 58P01. The error message is:

ERROR: could not access file «test_decoding»: No such file or directory

Cause

You must install postgresql-contrib additional supplied modules on Your source endpoint.

Using below command to install, then re-create instance.

sudo yum install postgresql11-contrib

Environment

You must install postgresql-contrib additional supplied modules on Your source endpoint.

Using below command:

sudo yum install postgresql11-contrib

Then recreate instance.

Document Location

Worldwide

[{«Business Unit»:{«code»:»BU059″,»label»:»IBM Software w/o TPS»},»Product»:{«code»:»SSTRGZ»,»label»:»InfoSphere Data Replication»},»Component»:»»,»Platform»:[{«code»:»PF016″,»label»:»Linux»}],»Version»:»11.4″,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

Перейти к содержимому

У нас вдруг, то есть неожиданно, приболел VMware vCenter. Cимптомы были самые разнообразные:

  • бесконечные вылеты vCenter(300+);
  • вылеты update manager;
  • невозможность удалить ВМ — они становились orphaned;
  • невозможность удалить снапшоты/сделать консолидацию/клонировать ВМ.

Попытки обновить vCenter до последнего билда, откатиться на недельный бэкап не принесли успеха.

Зацепились за вылет VMware vCenter с ошибкой:

An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (1) «ODBC error: (58P01) — ERROR: could not open file «base/16384/26436«: No such file or directory;

Error while executing the query» is returned when executing SQL statement «DELETE FROM VPX_SDRS_STATS_VM WHERE VM_ID = ?»

Решили отработать по старой схеме — подключиться в СУБД vPostgres:

  • Из файла C:ProgramDataVMwarevCenterServercfgvmware-vpxvcdb.properties берем адрес и порт, которые слушает СУБД (localhost:5432),  имя пользователя (vc) и копируем в буфер обмена пароль.
  • Скачиваем и ставим PGAdmin.
  • Запускаем PGAdmin, вводим полученные ранее данные.

Раскрываем дерево: Servers->vCenter->Databases->VCDB->Schemas->vc->Tables->VPX_SDRS_STATS_VM и получаем:

ERROR: could not open file «base/16384/26436»

По правой кнопке мыши на таблице VPX_SDRS_STATS_VM->Scripts->CREATE Script.

Раскомментировать удаление таблицы и выполнить скрипт:

DROP TABLE vc.vpx_sdrs_stats_vm;

CREATE TABLE vc.vpx_sdrs_stats_vm

(

    vm_id integer NOT NULL,

    quantiles text COLLATE pg_catalog.«default»,

    history text COLLATE pg_catalog.«default»,

    space_stats text COLLATE pg_catalog.«default»,

    CONSTRAINT pk_vpx_sdrs_stats_vm PRIMARY KEY (vm_id)

)

WITH (

    OIDS = FALSE

)

TABLESPACE pg_default;

ALTER TABLE vc.vpx_sdrs_stats_vm

    OWNER to vc;

Таблица будет удалена и создана заново с пустыми данными.

Обращаю внимание, что если в таблицах находятся критические данные, то это может и не помочь. Данная же таблица это статистика SDRS по ВМ, что у меня не востребовано, да и vCenter сам периодически заполняет данные.

Не подскажете в чем причина?
При попытке создания базы:
Ошибка СУБД:
58P01: ERROR: could not open extension control file «/usr/share/pgsql/extension/mchar.control»: No such file or directory
База на Postgre при этом создаётся. Если повторить создание базы на 1С сервере, то получаем другую ошибку:
DATABASE не пригоден для использования
Версии софта:
ALT Server 10.0 + PostgreSQL 13.5 сборка для 1С ; 1С сервер 8.3.20.1789 или 8.3.17 на Windows 2008

russian

postgresql

it

database


8

ответов

Постгрес патченный для 1с?



Постгрес патченный для 1с?

он из родного репо, заявлен для 1С, устанавливал так
apt-get install postgresql13-1C-server


Максим MaxS

он из родного репо, заявлен для 1С, устанавливал …

Да я скачал его. Это какой-то огрызок. Там нет mchar


Максим MaxS

12-й попробовать?

Контриб пакет поставьте


Максим MaxS

он из родного репо, заявлен для 1С, устанавливал …

Из родного для чего?
14-й есть от ПГ Про


Dmitry Kononov

Из родного для чего?
14-й есть от ПГ Про

ALT Server 10.0 искал так
apt-cache search 1C-server

Это проблема установки расширения. В пг отсутствует тип mchar, без него 1ц работать не будет. Проблма решается дистро-специфично.

vCenter crashed and down with errors like the following. At this time, no one has deleted anything manually from the base directory. It just happened out of the blue. This is an incident happened of vCenter Appliance with Postgresql and not uncommon. If indexes were the only corruption, they can be identified and recreated and perhaps reindex will reconstruct the corrupted indexes (I have not personally tried this, just a logical thinking). My guess is, this works similar if index pg_toast missing. If tables involved in the corruptions and disappeared, it is not worth the time and would likely have data integrity issues. Work on a plan to restore up to the point where corruptions no longer showing. There are chances that the backup may inherit the same corruption. This corruption might be detectable with vacuum full.

2015-05-14T10:40:00.011-04:00 warning vpxd[08940] [Originator@6876 sub=Default] [VdbStatement] Execution elapsed time: 4 ms

2015-05-14T10:40:00.011-04:00 warning vpxd[08940] [Originator@6876 sub=Default] [VdbStatement] Statement diagnostic data from driver is 58P01:0:7:ERROR: could not open file «base/16384/26465»: No such file or directory;

—> Error while executing the query

2015-05-14T10:40:00.011-04:00 error vpxd[08940] [Originator@6876 sub=Default] [Vdb::IsRecoverableErrorCode] Unable to recover from 58P01:7

2015-05-14T10:40:00.011-04:00 error vpxd[08940] [Originator@6876 sub=Default] [VdbStatement] SQLError was thrown: «ODBC error: (58P01) — ERROR: could not open file «base/16384/26465»: No such file or directory;

—> Error while executing the query» is returned when executing SQL statement «select rule_topn1_proc()»

2015-05-14T10:40:00.012-04:00 warning vpxd[08940] [Originator@6876 sub=OsLayer_win32] [VpxUnhandledException] Win32 Exception (3765269347) detected at 000007fefd90aaad

To confirm with missing objects, use can locate it with ‘ls’ command or the following query.

SELECT pg_catalog.pg_relation_filenode(c.oid) as «Object ID», relname as «Object Name»,

case WHEN relkind=’r’ THEN ‘Table’ when relkind=’m’

THEN ‘Materialized View’ when relkind=’i’

THEN ‘Index’ when relkind=’S’

THEN ‘Sequence’ when relkind=’t’

THEN ‘Toast’ when relkind=’v’

THEN ‘View’ when relkind=’c’

THEN ‘Composite’ when relkind=’f’

THEN ‘Foreign_Table’

ELSE ‘other’ end as «Object Type», o.rolname as «Owner»

FROM pg_catalog.pg_class c

LEFT JOIN pg_catalog.pg_authid o ON o.oid=c.relowner

LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace

LEFT JOIN pg_catalog.pg_database d ON d.datname = pg_catalog.current_database(),

pg_catalog.pg_tablespace t

WHERE pg_catalog.pg_relation_filenode(c.oid) = 26465

Problem

CDC for Postgresql : 11.4

Postgresql:11

When creating cdc for postgresql instance, got below error:

Cannot create changes:A SQL exception has occurred. The SQL error code is ‘0’. The SQL state is: 58P01. The error message is:

ERROR: could not access file «test_decoding»: No such file or directory

Symptom

Cannot create changes:A SQL exception has occurred. The SQL error code is ‘0’. The SQL state is: 58P01. The error message is:

ERROR: could not access file «test_decoding»: No such file or directory

Cause

You must install postgresql-contrib additional supplied modules on Your source endpoint.

Using below command to install, then re-create instance.

sudo yum install postgresql11-contrib

Environment

You must install postgresql-contrib additional supplied modules on Your source endpoint.

Using below command:

sudo yum install postgresql11-contrib

Then recreate instance.

Document Location

Worldwide

[{«Business Unit»:{«code»:»BU059″,»label»:»IBM Software w\/o TPS»},»Product»:{«code»:»SSTRGZ»,»label»:»InfoSphere Data Replication»},»Component»:»»,»Platform»:[{«code»:»PF016″,»label»:»Linux»}],»Version»:»11.4″,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

Понравилась статья? Поделить с друзьями:
  • Sql код ошибки 0x534
  • Sql игнорирование ошибки
  • Sql если ошибка функция
  • Sql вывод сообщения об ошибке
  • Sql writer ошибка