1. Invalid Number:
Itself is a string format and must be converted to a string format
2. A non-numeric charactor was found where a numeric was expected:
The date format is also converted to the date format.
3. Column ambiguously defind:
The field is ambiguous. In each of the tables, you must specify the table field.
4. character to numeric Conversion error
It is originally a three-digit number. To convert to_char (273.4, '99. 9') to a two-digit number, an error is returned.
5. ORA-04063: Package body "fast. pkg_zcommissionstatr" has errors
The method stored procedure has encountered an error. It can be compiled and run before. It is not allowed now. The table structure, ob, and NT have changed.
6. ORA-06508: PL/SQL: unable to find the calledProgramUnit
That is, ob does not write the body.
View code
Create Or ReplaceType Body ob_1_holdersrewardtrackIs--Member procedures and functionsConstructorFunctionOb_1_holdersrewardtrackReturnSelfAsResultIsBeginReturn;End;End;
7. the same PKG compilation in this environment (ended with Dev in the image) does not pass (stuck, no response, the process must be terminated), but in the exception environment (ended with orcl in the image) however, this is a problem with the resource environment (not completed at noon, but compiled in the afternoon ).
8. When PKG is executed, a deadlock is detected when the Oracle ora-00060 is waiting for resources.
Run this SQL: Select spid, osuser
From v $ session S, V $ PROCESS p
Where S. paddr = P. ADDR
And S. Sid in (select Sid from V $ access where object = 'pkg _ smssend_proc '); -- remember that the name is in uppercase.
Then, run the kill-9 spid command on the server (my database is deployed on Linux) to end the process.
ORA-12801: Error signaled in parallel query server p025
Contact the database service provider for insufficient tablespace Revocation
ORA-01555: ORA-01555: Snapshot too old: rollback segment number 21 with name "_ syssmu21 $" too small
The database buffer is too small. Contact the Database Service Provider
ORA-01410: Invalid rowid.:
Because dynamic data is deleted during data extraction (you have collected all the data three hours ago, because the data volume is too large, when the task thread processes a piece of data, but the current data is deleted by someone else, you can only try catch continue to skip this section of data)
ORA-06502: PL/SQL: numeric or value error: character string buffer too small ORA-06512: At "Sa. sfzh18to15", line 8
There are two reasons: first, when you query, the accept field is too small, smaller than the corresponding field in the database, and an error is returned.
Second, the field you define is too large to be larger than the field in the corresponding table. When you insert a field into the database, an error will be reported for that field.
Java. SQL. sqlexception: Io exception: Connection Reset
There are many reasons for connection resetting: connection pool problems, database problems. Our system takes five attempts to connect and then breaks down.