Due to GI_HOME restricted access, you might get following errors when you extract opatch utility to GI_HOME:
checkdir error: cannot create /u01/app/12.2.0.1/grid/OPatch Permission denied unable to process OPatch/config/opatch.properties.
Here is one of the appropriate way for extracting opatch utility :
Read more of this content when you subscribe today.
After manually dismounting an ASM group, then queries on v$asm_* views hang forever.
Read more of this content when you subscribe today.
1) To disable certain ASM Diskgroup automatic mount on all RAC nodes, run below command as grid user:
$ srvctl disable diskgroup -diskgroup testdg
2) To disable certain ASM Diskgroup automatic mount on specific RAC node, run below command as grid user:
$ srvctl disable diskgroup -diskgroup testdg -node racnode1
3) To check the status of ASM diskgroup:
$ srvctl status diskgroup -diskgroup testdg -detail -verbose Disk Group testdg is running on racnode1, racnode2 Disk Group testdg is disabled
Note: You cannot run the “srvctl start” command on a disabled object until you first re-enable the object
The below errors occurred while export tables by using datapump:
$expdp userid=... tables=... directory=... dumpfile=... .. UDE-31623: operation generated ORACLE error 31623 ORA-31623: a job is not attached to this session via the specified handle ORA-06512: at "SYS.DBMS_DATAPUMP", line 3905 ORA-06512: at "SYS.DBMS_DATAPUMP", line 5203 ORA-06512: at line 1
Stream pool size is too small, and there is no more memory for stream pool to increase.
Increase streams_pool_size:
SQL> show parameter streams_pool_size NAME TYPE VALUE ----------------- ----------- --------- streams_pool_size big integer 20M SQL> alter system set streams_pool_size=128M ;
If not enough memory available:
SQL> alter system flush SHARED_POOL; System altered. -- OR SQL> alter system flush BUFFER_CACHE; System altered. SQL> alter system set streams_pool_size=128M ;
For AMM or ASMM, after data pump is complete, reset the parameter to leave system to manage this parameter again.
SQL> alter system reset streams_pool_size;
The following errors occurred from 11.2.0.4 standby databases:
SQL> select open_mode from v$database; OPEN_MODE -------------------- MOUNTED SQL> select * from v$rman_backup_job_details; select * from v$rman_backup_job_details * ERROR at line 1: ORA-00604: error occurred at recursive SQL level 2 ORA-00904: "SYS"."DBMS_RCVMAN"."NUM2DISPLAYSIZE": invalid identifier
The problem is that DBMS_RCVMAN and other packages are not initialized when database in MOUNT mode, only in OPEN mode, hence the error when using SYS.DBMS_RCVMAN
dbms_rcvman package is not loaded in memory until database is open or RMAN client is ran explicitly.
This error is expected because the standby instances are in MOUNT mode and the DBMS_RCVMAN does not get initialized.
Workaround: just make a call to rman before running the query in the Standby database. This will initialize the DBMS_RCVMAN package.
SQL> select * from v$rman_backup_job_details; select * from v$rman_backup_job_details * ERROR at line 1: ORA-00604: error occurred at recursive SQL level 2 ORA-00904: "SYS"."DBMS_RCVMAN"."NUM2DISPLAYSIZE": invalid identifier SQL> exit $ rman target / RMAN> exit $ sqlplus / as sysdba SQL> select * from v$rman_backup_job_details; ... .. .
Make DBA Life Easy 