Solution to oracle tablespace deletion errors in linux

In linux, when oracle deletes a tablespace, an error occurs. Due to insufficient tablespace capacity, the tablespace capacity needs to be increased. Therefore, a new tablespace is created in the original tablespace and added to the original tablespace, failed to be created. During the creation process, the newly added tablespace is added and deleted multiple times. At that time, the machine was not restarted. Therefore, no problems are found, and everything is normal. However, everything is hard to predict. Due to the high power consumption in summer, the fuse is burned, resulting in a large area of power failure. This host is not spared. This power failure led to a tragedy. Www.2cto.com
After a call, open the machine again and report "your $ home/. dmrc has been ignored" when logging on to the oracle user. This will not save the default session and language. The file should be owned by the user and the permission should be set to 644. The $ home directory of the user should be owned by the user, and other users cannot write "error. If the problem was not solved at the time, the system was directly ignored. The specified user cannot be connected when sqlplus is enabled in the system. Therefore, the System user is connected, and the sys user can be connected. This indicates that the oracle service is enabled. Both the test listener and em are enabled. When em is enabled, the listener is normal and the instance is not enabled. And reported "ora-01033: oracle initialization or shutdown in SS ". At this point, I thought about it. After shutdown oracle, I start up again to see if the oracle instance can be opened. Then, let's test it based on our own ideas. After the restart is disabled, the problem persists. Search for it online.
To sum up, you must first correct the error when logging on to an oracle user. Then, according to the method described on the Internet, the solution is to: chmod 755-R/home/user name chmod 644/home/user name /. dmrc to modify the oracle user logon error. After resolving this error, you need to solve the oracle instance error. This is the need to first use sqlplus sys/password as sysdba, after logging on to sqlplus, SQL> shutdown immediateORA-01109: the database has not opened the detached database.
The ORACLE routine has been disabled. SQL> startup mount; the ORACLE routine has been started. Total System Global Area 171966464 bytesFixed Size 787988 bytesVariable Size 145750508 bytesDatabase Buffers 25165824 bytesRedo Buffers 262144 bytes database loaded. Www.2cto.com SQL> alter database open; alter database open * 1st Line Error: ORA-01122: database file 11 Verification Failed ORA-01110: Data File 11: 'e: \ APP \ DATABASE \ STU_DB.DBF 'ora-01203: Prototype error for this file-create SCN error SQL> alter database open resetlogs; alter database open resetlogs * 1st Line Error: ORA-01139: the RESETLOGS option is valid only after Incomplete database recovery> alter database datafile 11 offline drop; // (here "11" is the previous "database file 11") The database has been changed. SQL> alter database open resetlogs; alter database open resetlogs * row 1st error: ORA-01139: RESETLOGS option valid only after Incomplete database recovery> alter database open; database changed. SQL> shutdown normal; the database has been closed. The database has been detached. The ORACLE routine has been disabled. Www.2cto.com SQL> startup mount; the ORACLE routine has been started. Total System Global Area 171966464 bytesFixed Size 787988 bytesVariable Size 145750508 bytesDatabase Buffers 25165824 bytesRedo Buffers 262144 bytes database loaded. At this point, the problem is solved. Author: rbyyy924805