Oracle ERP DBA

Though this topic is unrelated any Apps DBA topics, I found it necessary to share the solution so that everyone benifits out of it ! Issue: I used to receive the below error message whenever I tried to shutdown windows XP. A rather vexing problem, no doubt. Cause: This message appears because when windows is trying to shutdown and end all the running processes, the WMS idle process keeps working. Thus an end-program message appears. The two most common reasons for this are: Scout service run by Nero 7 Microsoft Office Communicator 2005 Solution: The fix is simple, disable the Nero 7 scout service if it is enabled. For this, go to Start > All Programs > Nero > Tools > Nero Scout . On this screen , Uncheck Enable the Nero scout. This will fix the issue for most of the users, for the rest of you who are not using Nero are most probably getting this error because of Microsoft Office Communicator 2005. For that you need to either manually exit the communicator 2005 from the s

Though it was a bit tough to find out the version of Mod_security that is shipped with E-Business Suite 11.5.10.2, I finally managed to do it, thanks to Metalink Fora! The version that comes with eBS 11.5.10.2 is 1.8.4 . Below is how you find out the version of mod_security shipped with your version of eBS. $ strings $IAS_ORACLE_HOME/Apache/Apache/libexec/mod_security.so | grep mod_security/

What Is ModSecurity? ModSecurity is a web application firewall that can work either embedded or as a reverse proxy. It provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring, logging and real-time analysis. [7] mod_security is an Apache module (for Apache 1 and 2) that provides intrusion detection and prevention for web applications. It aims at shielding web applications from known and unknown attacks, such as SQL injection attacks, cross-site scripting, path traversal attacks, etc. [6] mod_security is an Apache module designed as a sort of web application firewall. It’s most useful for preventing SQL Injection and Cross Site Scripting (or XSS). [2] It is also an open source project that aims to make the web application firewall technology available to everyone. [7] SQL Injection SQL injection is a technique that exploits a security vulnerability occurring in the database layer of an application. The vulnerability is pr

A very common question in any interview is "How do you find the size of a database?" This question can be answered in numerous ways. For e.g., some might say that the size of the database is the sum of the size of each datafile. Some might add the size of the tempfiles to the afore mentioned answer. However, according to me, the size of the database can be calculated as below: Database size = size of datafiles + size of tempfiles + size of redologs + size of controlfiles The above formula can be put to use using the below mentioned SQL. set serveroutput on declare DB_SIZE number; dfsize number; tfsize number; rlsize number; cfsize number; begin select sum(bytes)/1024/1024 "DATA_FILE_SIZE" into dfsize from dba_data_files; select sum(bytes)/1024/1024 "TEMP_FILE_SIZE" into tfsize from dba_temp_files; select sum(bytes)/1024/1024 "REDO_LOG_SIZE" into rlsize from v$log; select (BLOCK_SIZE * (1 + FILE_SIZE_BLKS))/1024/1024 "CONTROL_FILE_SIZE"

Below is the SQL statement to find the size of the control files. select (BLOCK_SIZE * (1 + FILE_SIZE_BLKS))/1024/1024 "CONTROL_FILE_SIZE (MB)" from sys.v_$controlfile where rownum = 1; OR select distinct (BLOCK_SIZE * (1 + FILE_SIZE_BLKS))/1024/1024 "CONTROL_FILE_SIZE (MB)" from sys.v_$controlfile; Eg: SQL > select (BLOCK_SIZE * (1 + FILE_SIZE_BLKS))/1024/1024 "CONTROL_FILE_SIZE (MB)" from sys.v_$controlfile where rownum = 1; CONTROL_FILE_SIZE (MB) ---------------------- 18.515625 SQL > select distinct (BLOCK_SIZE * (1 + FILE_SIZE_BLKS))/1024/1024 "CONTROL_FILE_SIZE (MB)" from sys.v_$controlfile; CONTROL_FILE_SIZE (MB) ---------------------- 18.515625 SQL > select distinct (BLOCK_SIZE * (1 + FILE_SIZE_BLKS)) "CONTROL_FILE_SIZE (BYTES)" from sys.v_$controlfile; CONTROL_FILE_SIZE (BYTES) ------------------------- 19415040 $ ls -slrt [path_to_Controlfile]/cntrl0* 18984 -rw-rw---- 1 oracle dba 19415040 Jul 21 02:56 [path_

Many a time, DBAs and Developers tend to run scripts, accidentally, in instances that they do not actually intend to. In extreme cases, this might result in disastrous consequences, sometimes even leading to recovering/restoring the database from a backup. This mistake can easily be avoided if the sql prompt displays the username and/or the SID in lieu of just "SQL>". Whenever sqlplus is invoked, 2 files are executed: glogin.sql and login.sql (if it exists) in the order mentioned. These 2 files are located under $ORACLE_HOME/sqlplus/admin . Modify the file glogin.sql and add the below line: set sqlprompt " _user'@'_connect_identifier > " The net result of this is that the sqlprompt will appear as below whenever you login to sqlplus: system@ORCL > where system is the username and ORCL is the SID. Note: One drawback of this method, if it may be called so, is that whenever one logs in to sqlplus using /nolog option, only the '@' character