I don t have enough space when installing Oracle, what s going on??

Explain that your C disk has no space, try to install the program to other disks, do not put it on the C disk, put everything in the C disk, the system speed will be relatively slow, because the general default cache is the C disk, secondly, if there is a problem with the computer, once reinstalled, all your things will be lost, it is recommended to put the program class on the D disk, work or study with the E disk, backup or games and movies and so on on the F disk.

Is there still room for your C drive?

Even if it is not installed in the system disk, some programs will install something in the system disk, and if your system disk really runs out of space, it may also report you an error.

In addition, the installer sometimes needs to decompress some files and will be completed in the temporary file directory of the system disk, which requires space.

When installing, especially some large software, you need to have 1 place as the installation buffer, although you did not install it on the C disk, but the oracle installation also needs to have this exchange area, this exchange area is like the directory mentioned in your question, if this exchange area is not satisfied, that is, the space of your C disk is not enough to reach the size of his buffer, you may have such a problem.

Suggestion:First help C disk reduce**,You can move the file to another disk first,Put it back after installation,Try it out,When I install Oracle myself, the C disk probably leaves about 2G space Successful installation,If you can't,I'll add

temp is the system cache directory,,You can empty the cache,If you can no longer clean up the C disk space,Just set the cache directory in the registry to other more free disks,Wait for the installation to be restored。

For novices, this kind of error is still often encountered o( o. If you confirm that your table space is large enough, then I think it's probably a problem with creating a table when you're doing an imp. How did this question arise? Probably:

1. You use the compress=y parameter when you exp, this parameter seems to mean compression at first glance, but in fact, its function is to increase the initial value of the table to the amount of space occupied by the table in the original database. In other words, if the waterline of the original table is relatively high, then if you import the data directly, this mistake is basically unavoidable.

2. The initail value of your original table was originally set to a large size, and although there is space in the new database, these spaces are not continuous. The database could not find suitable contiguous blocks to allocate.

The fastest solution to the above problems is to manually create the objects to be imported in the new database, and then import the data. (Don't forget to use the ignore=y parameter).

Of course, there is a special case, that is, the amount of data of each piece of your data is relatively large, directly exceeding the size of a data block, then the "row link" situation will occur, so the size of the data you import will be much larger than the size of the dmp package you see, which will also lead to 1658 errors.

It is recommended that the landlord increase the surface space and try again.