Unable To Create Dump file | ORA-39001,ORA-39000,ORA-31641,ORA-27054

Error Details:
*****************

Export: Release 11.2.0.3.0 - Production on Sat Apr 29 15:00:44 2017

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "/mount-mig/TT0037598650/fullpserv_01.dmp"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
Additional information: 18


Solution Description:
**************************
Mostly you will get this error on SunOS:
----------------------------------------------------
Start The Database And Run This : sqlplus / as sysdba

ALTER SYSTEM SET EVENTS '10298 trace name context forever, level 32'; 

Datapump Import (IMPDP) fails due to Error ORA-31693,ORA-31640,ORA-19505,ORA-27037

Error Details:
*****************

ORA-31693: Table data object "VERTEX"."RATECITY" failed to load/unload and is being skipped due to error:
ORA-31640: unable to open dump file "/mnt/vertex/importdata/expdp_fulldb_vert/expdp_fulldb_vertppf_19082017_02.dmp" for read
ORA-19505: failed to identify file "/mnt/vertex/importdata/expdp_fulldb_vert/expdp_fulldb_vertppf_19082017_02.dmp"
ORA-27037: unable to obtain file status

Solution Description:
**************************

Issue is due to the mount/file system was not being accessible from the second node.
Then use Cluster=N to force Data Pump to use only the instance where the job is started and ran again data pump job using below datapump parameter:

Cluster=N

ORA-17503: ksfdopn:2 Failed to open file +PROD_DATA_01/prod/spfileprod.ora & ORA-12547: TNS:lost contact

Problem:
************

 You attempted to start you database after silent installation and received this error message:

[root@dell ~]# su - oracle
[oracle@dell ~]$ . oraenv
ORACLE_SID = [oracle] ? prod
The Oracle base has been set to /u01/app/oracle
[oracle@dell ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Wed Sep 14 08:50:02 2016

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+PROD_DATA_01/prod/spfileprod.ora'
ORA-17503: ksfdopn:2 Failed to open file +PROD_DATA_01/prod/spfileprod.ora
ORA-12547: TNS:lost contact

 This message indicates you start you database, you need check you oracle utility permissions.

Solution:
***********


To place your database in archivelog mode, perform the following steps:

  1. Check listener status.
  2. Check oracle utility permission for both users grid & oracle.
  3. Change permission of oracle utility for both users grid & oracle.
  4. Startup your database.


Check listener status:
***************************

LSNRCTL> status

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.4.0 - Production
Start Date                14-SEP-2016 08:17:33
Uptime                    0 days 0 hr. 32 min. 6 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/grid/11.2.0/grid_home/network/admin/listener.ora
Listener Log File         /u01/app/grid/diag/tnslsnr/dell/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dell.localdomain)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM", status READY, has 1 handler(s) for this service...
The command completed successfully


Check oracle utility permission for both users grid & oracle:
*************************************************************************


[grid@dell bin]$ ls -al oracle
-rwxrwxr-x 1 grid oinstall 209914513 Sep 11 08:23 oracle

[oracle@dell bin]$ ls -al oracle
-rwxrwsr-x 1 oracle asmadmin 239626683 Sep 11 09:28 oracle


Change permission of oracle utility for both users grid & oracle:
******************************************************************************

[root@dell ~]# cd /u01/app/grid/11.2.0/grid_home/bin
[root@dell bin]# chmod 6751 oracle

[root@dell bin]# ls -lrth oracle
-rwsr-s--x 1 grid oinstall 201M Sep 11 08:23 oracle

[root@dell bin]# cd /u01/app/oracle/product/11.2.0/db_1/bin/
[root@dell bin]# chmod 6555 oracle

[root@dell bin]# ls -lrth oracle
-r-sr-sr-x 1 oracle asmadmin 229M Sep 11 09:28 oracle


Startup your database:
****************************

[root@dell ~]# su - oracle
[oracle@dell ~]$ . oraenv
ORACLE_SID = [oracle] ? prod
The Oracle base has been set to /u01/app/oracle
[oracle@dell ~]$
[oracle@dell ~]$
[oracle@dell ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Wed Sep 14 09:51:57 2016

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area  839282688 bytes
Fixed Size                  2257880 bytes
Variable Size             545262632 bytes
Database Buffers          289406976 bytes
Redo Buffers                2355200 bytes
Database mounted.
Database opened.
SQL>

ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

Problem:
************

You attempted to use RMAN to back up your database and received this error message:

RMAN-03009: failure of backup command on ORA_DISK_1 channel
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

This message indicates that before you can create an RMAN online backup, you need to place your database into archivelog mode.

Solution:
***********

To place your database in archivelog mode, perform the following steps:

1. Connect as sysdba.
2. Shut down your database.
3. Start up in mount mode.
4. Alter the database into archivelog mode.
5. Open your database for use.

If you want to disable archivelog mode, then you would execute all the previous steps, with one change; in step 4, you will need to use the noarchivelog parameter (instead of archivelog mode).

Enabling Archivelog Mode:
**********************************

You first need to connect to your database with a schema that has sysdba privileges (usually the sys schema). The following example connects as sys and then issues the commands to enable archivelog mode:

SQL> connect sys/pradeep as sysdba
SQL> shutdown immediate;
SQL> startup mount;
SQL> alter database archivelog;
SQL> alter database open;


Disabling Archivelog Mode:
**********************************

If for some reason you want to disable archiving, issue these commands:

SQL> connect sys/pradeep as sysdba
SQL> shutdown immediate;
SQL> startup mount;
SQL> alter database noarchivelog;
SQL> alter database open;

Displaying Archive Information:
***************************************

After you have changed the archivelog mode of your database, you might want to verify that the mode has been set properly. To display the status of archiving, you can query V$DATABASE as follows:

SQL> select log_mode from v$database;
LOG_MODE
--------------------
ARCHIVELOG

The SQL*Plus archive log list command displays a useful summary of the archiving
configuration of your database. As shown in the following output, it includes information such
as the archivelog mode, automatic archiving, archive destination, and log sequence numbers.

SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination  +FRA
Oldest online log sequence 87950
Next log sequence to archive 87952
Current log sequence 87952

Enabling archivelog mode is a prerequisite for online backups. The previous commands give you a quick way to verify the archivelog mode status of your database.