sometimes, the expdp utility may be corrupted, in this case either the expdp file which is inside the $ORACLE_HOME/bin folder may be missing or the filesize is 0 bytes,
Easiest method to solve this issue is to copy the expdp from a working server to the server which is not working - make sure that we need to copy from the same version of the database example if the server which is having trouble is running in the Database ver 10.2.03 then, the file which is copied should also run in the version 10.2.03.
After this it will show the error message as /opt/oracle/product/10gR2/bin/expdp: error while loading shared libraries: libclntsh.so.10.1: cannot open shared object file: No such file or directory when trying to run the expdp file.
Soltion for this is we need to set the environment variable as follows.
$export LD_LIBRARY_PATH=$ORACLE_HOME/lib
Make sure that you have set the ORACLE_HOME variable before.
Sunday, November 1, 2009
Recovery from missing or corrupted datafile(s):
Case 1: Recovery from corrupted or missing datafile
This scenario deals with a situation where a datafile has gone missing, or is corrupted beyond repair. For concreteness, we look at a case where a datafile is missing. Below is a transcript of an SQL Plus session that attempts to open a database with a missing datafile (typed commands in bold, lines in italics are my comments, all other lines are feedback from SQL Plus):
The error message tells us that file# 4 is missing. Note that although the startup command has failed, the database is in the mount state. Thus, the database control file, which is also the RMAN repository can be accessed by the instance and by RMAN. We now recover the missing file using RMAN. The transcript of the recovery session is reproduced below (bold lines are typed commands, comments in italics, the rest is feedback from RMAN):
In the above scenario, the database is already in the mount state before the RMAN session is initiated. If the database is not mounted, you should issue a "startup mount" command before attempting to restore the missing datafile. The database must be mounted before any datafile recovery can be done.
Case 1: Recovery from corrupted or missing datafile
This scenario deals with a situation where a datafile has gone missing, or is corrupted beyond repair. For concreteness, we look at a case where a datafile is missing. Below is a transcript of an SQL Plus session that attempts to open a database with a missing datafile (typed commands in bold, lines in italics are my comments, all other lines are feedback from SQL Plus):
The error message tells us that file# 4 is missing. Note that although the startup command has failed, the database is in the mount state. Thus, the database control file, which is also the RMAN repository can be accessed by the instance and by RMAN. We now recover the missing file using RMAN. The transcript of the recovery session is reproduced below (bold lines are typed commands, comments in italics, the rest is feedback from RMAN):
In the above scenario, the database is already in the mount state before the RMAN session is initiated. If the database is not mounted, you should issue a "startup mount" command before attempting to restore the missing datafile. The database must be mounted before any datafile recovery can be done.
Subscribe to:
Posts (Atom)