Earlier I have already demonstrated adding and managing custom services in a RAC environment in a blog post and a video.
Earlier this week (10-April), I had done a Switchover from the 2node RAC database to a SingleInstance database.
Continuing the series of posts on the RAC/ASM to SingleInstance/FileSystem DataGuard configuration … With both instances RAC1 and RAC2 running, I have redo shipping from both instances to the single instance STBY.(In my test server with 3 VMs, it takes a number of minutes to have all 3 instances running and communicating with each other … so there are spurious ORA and TNS errors until the 3 instances have stabilized.
Continuing with the 18.104.22.168 non-RAC MultiTenant environment and two services demonstrated earlier, I have restarted the environment today : [grid@ora12102 ~]$ lsnrctl servicesLSNRCTL for Linux: Version 22.214.171.124.0 - Production on 16-JUN-2016 22:57:17Copyright (c) 1991, 2014, Oracle.
Here is a very clean and simple script which will monitor and check the status of listener for oracle database.
Just when I was thinking how boring my job as DBA was (doing the same routine work and nothing new to implement until you convince everyone and take approvals from them!!) I was made to feel that DBA work is not at all boring if you are at the receiving end 🙂 .
Ever spin up a database for some quick and dirty work, and you JUST WANT TO CONNECT (!!) without going through the whole ‘add the service to your local TNSNames.ORA’ rigmarole (Oracle Net Configuration Assistant)?
If you want to find out what happens when you run Oracle export or Oracle import utility is to set ON the Oracle trace event 10046. This will generate a trace file that can be used to find out the actual happenings behind the scene.
This is how you can get 10046 Trace for Export and Import Utilities
1] Run the Oracle export command export and let the program prompt you for the options.
Enter user and password as below when prompted
2] Open another window to the database server and login using sqlplus.
$ sqlplus system/manager
3] Now find out the SID of exp session
sql> select sid,program from
v$session where username = ‘SYSTEM’;
788 exp@SERVER01 (TNS V1-V3)
4] Now find the PID and SPID for that session
sql> select s.sid, p.pid, p.spid
from v$session s, v$process p
where s.paddr = p.addr and s.sid = 10;
SID PID SPID
———- ———- ———
788 189 1076
SPID from the previous query is equivalent to OSPID (operating System process). This is the process that will be traced
5] Now exit from this session
6] Generate a trace file for Procces ID 1076. To do that login as sys using sqlplus and run the commands (in bold)
$ sqlplus / as sysdba
SQL> oradebug setospid 1076
Oracle pid: 189, Unix process pid: 1076, image: oracle@SERVER01 (TNS V1-V3)
SQL> oradebug unlimit
SQL> oradebug tracefile_name
This gives the name of the trace file
SQL> oradebug Event 10046 trace name context forever, level 12;
7] From the window where “exp” command was run, now export a table
8] From the SQL prompt of the window where logged in as “sys” user
Set the Trace off once you get the Required information or the error.
SQL> oradebug Event 10046 trace name context off;
ORA-00072: process “Unix process pid: 17370, image: oracle@ SERVER01″ is not active
Now you have got the trace file which is