ORA-01861: literal does not match format string
When I try to execute this snippet: I get: There is no problem with database connection because I can execute basic SQL commands. What is the problem with this statement?
When I try to execute this snippet: I get: There is no problem with database connection because I can execute basic SQL commands. What is the problem with this statement?
Try something like this. Replace ‘NikitaBuriak’ with the ID you used when you created the table..
Since Oracle 9i there are two ways or declaring a directory for use with UTL_FILE. The older way is to set the INIT.ORA parameter UTL_FILE_DIR. We have to restart the database for a change to take affect. The value can like any other PATH variable; it accepts wildcards. Using this approach means passing the directory … Read more
You should specify column names as below. It’s good practice and probably solve your problem EDIT: As you said employees has 112 columns (sic!) try to run below select to compare both tables’ columns and than you should upgrade your tables to have the same structure.
You’re missing service name: EDIT If you can connect to the database from other computer try running there: and
You are exceeding the SQL limit of 4000 bytes which applies to LISTAGG as well. As a workaround, you could use XMLAGG. For example, If you want to concatenate multiple columns which itself have 4000 bytes, then you can concatenate the XMLAGG output of each column to avoid the SQL limit of 4000 bytes. For example,
After some googling, I found the advice to do the following, and it worked:
Perhaps you should check NLS_DATE_FORMAT and use the date string conforming the format. Or you can use to_date function within the INSERT statement, like the following: Additionally, Oracle DATE stores date and time information together.
A query’s projection can only have one instance of a given name. As your WHERE clause shows, you have several tables with a column called ID. Because you are selecting * your projection will have several columns called ID. Or it would have were it not for the compiler hurling ORA-00918. The solution is quite simple: you … Read more
A query’s projection can only have one instance of a given name. As your WHERE clause shows, you have several tables with a column called ID. Because you are selecting * your projection will have several columns called ID. Or it would have were it not for the compiler hurling ORA-00918. The solution is quite simple: you … Read more