Is the string buffer too small? -- Oracle also falsely reports military information

To test the system a few days later, you need to install the entire system on the virtual machine. The database uses the Oracle version 10.2.0. However, due to Oracle's military fraud, I have reinstalled n times.

The currently running database server is Oracle of version 10.2.0.3.0. When I generate a data copy of DMP and IMP to the database of the VM, Oracle cannot read the file. After checking it carefully, we found that the database version of the virtual machine is 10.1.0, so we can unmount it and change it to Oracle 10.2.0. This nightmare began.

When IMP data is executed, the new version of Oracle can read the DMP file. However, when an import job is executed, it always fails to run and prompts:

ORA-06502: PL/SQL: Number or value error: string buffer is too small

PL/SQL 18th row Error

....

This is the case several times.

In desperation, you can only seek help from Google. After searching, you can find the so-called Oracle bug. This is what I am worried about, because I only have the Installation File 10.2.0.1.0 on hand. Isn't it... there is no other way. Drag a 10.2.0.3.0 installation patch from the Internet and install it. After n times of re-installation and patching (the patch installation is not as smooth, and there are many errors, which are not described in detail here ), the reality has poured cold water on me again-the same mistake.

It seems that it is not a so-called bug.

Therefore, only 10.2.0.1.0 can be reinstalled. (Other problems caused by upgrading to 10.2.0.3.0 are excluded ). The solution to this error (from network resources)-I cannot find a place to change the buffer size. It seems that I have to work overtime today.

When I got off work, I suddenly found a suspicious place when I looked at the imported log.

Xxx import error. Table space XXX not found

I quickly found the tablespace settings of the real system, and found that the service occupied two tablespaces, but there was only one tablespace definition in the Virtual Machine System, but there was no ing during the import. Don't you know? We have done a good job of ing the imported tablespace. Import...

Two minutes later. OK! The puzzling "the string buffer is too small" error failed.

When the system ran up, it had been off work for an hour, but today we didn't even work overtime. We also learned Oracle's false reporting technology for everyone.