-
Create table as **selectThe table should exist in the data dictionary, so that the table can be created successfully, you have a complex subquery, such as count(*)as samplid, how does the database know whether samplid should be created as int or bigint? It is recommended that you split the dynamic statement into two statements, one for the regular table creation statement and the other for the insert statement.
-
You do not need to wrap the list in double quotation marks, and the use of double quotation marks indicates that the column names are consistent with the case of the column names defined in the database table. In addition, check whether the double quotation marks are also used in the table statement, and if so, remove the double quotation marks.
-
You have values here (hr, hr, hr
hr wrote it twice, so it's probably wrong here.
-
Do you have this in your table? Or when inserting, the properties are inconsistent.
-
It should be create or replace! Also, do your users have permissions for creaet stored procedures?
-
If it's a table or something, it depends on whether your current user has access to the object, and if it's a stored procedure that is called, see if the stored procedure can run correctly.
-
Take a look at the process.
Or maybe it's not a matter of permissions.
-
Is the object invalid, is it a stored procedure or what? **Post it out and take a look.
-
Check that the permissions and the object are compiled correctly.
-
Method steps.
1. In most cases, this error is caused by referencing a non-existent column name. For example, select name from studtent This error is reported when there is no name column in the studeng table.
2. The solution is to determine whether the column names referenced in the database are consistent with the column names written in your own SQL. If there is a difference, modify it and retest it should solve the problem.
3. For the SQL generated by some tools, the list may not match the expectation, for example, the column name generated by some tools will have double quotation marks, which will cause this error. Please also note this situation.
-
...Judging from the error, it must be a question mark error.
Although I don't know much about oracle, but if you are in pure SQL, you must not be able to use the output parameters in the call? , you should declare a number or something and pass that variable in as an argument.
If you are ......... in the programCan jdbc be written directly? But you also need setstring to replace it later? ......
PS: Don't use call, just use begin....end.
Although I prefer that you write it directly in the oracle.,But the comrades said that it can't be ruled out from the way it is written.。。。
-
The call is made with begin end.
begininsertteacou('1400123','2013000012','North 1101','1-1','100000','The first semester of the 2012-2013 academic year');
end;Also, why did you have a question mark, that is.
call insertteacou(?,'1400123','2013000012','North 1101','4-2','100000','The first semester of the 2012-2013 academic year')
The first one in parentheses.
-
begininsertteacou(?,'1400123','2013000012','North 1101','4-2','100000','The first semester of the 2012-2013 academic year');
end;No call is required
-
Removing declare is a syntax problem, you can take a look at the syntax of create proc, the variables declared after is as do not need to declare, the syntax is prescribed by oracle, if you don't write it like this, it will not be recognized.
Visually, your stored procedure needs to run at these moments: >>>More
Memory, also known as memory, is an electronic device made of semiconductor technology to store data. The data of electronic circuits is stored in binary, and each memory cell is called a memory element or cell. >>>More
Stack errors are usually used because of a function called cdecl with stdcall. >>>More
Haier air conditioning. The core components of the compressor are international famous brand compressors, Mitsubishi, Panasonic, Hitachi. >>>More
Memory cards should be used with care, like you will not work. >>>More