Submitted by zainmdm on Sun, 2012-11-04 23:32
Oracle Database A to Z question and answers and
very importantly the Experiences also you can share here...
The Blog is for Both the beginners and as well as experienced people to discuss and gain knowledge in Oracle.
Here we are going to share every thing about Oracle....
And Simply saying, we will only work on oracle related but nothing else here....
We will Eat Oracle, Drink Oracle and Walk Oracle
Submitted by arunbharat2001 on Sat, 2012-10-20 12:03
1.DML data can be recovered by rollback before commit
2.Remove any subset of data
3.Delete is slower when table have numerous indexes and triggers
4.DML triggers fire for delete mthod
5.data can be recovered after commit by flashback method
6.high water mark will remain the same
7.data deleted info capture with returning clause
8. you can not delete data if function based index is invalid
9. can not delete data from complex views.
10. Space is not freed
Submitted by mikerajendran on Sun, 2012-10-07 01:30
Oracle Database 12c: New Features – Pluggable Databases by Michael
Submitted by John Watson on Sun, 2012-09-16 02:48
The COST column cannot be used to compare execution plans. Punkt.
Submitted by vamsi kasina on Fri, 2012-09-14 13:42
In case of unitended usage of system source in conditions may lead to the following error in Create Accounting:
There is a missing system source value. Please inform your system administrator or support representative that: There are no values for the system source XXXXXXXXXXXXXXXXX used by Oracle Subledger Accounting.
Submitted by csm.dba on Tue, 2012-09-04 05:52
We all know that CHAR and VARCHAR2 are two different datatypes used for storing strings in Oracle. When I asked many people about what’s the difference exactly, all were saying VARCHAR2 can be used for variable sized character strings. As I’m not satesfied with the answer, as always, I’ve decided to do my own experiments on these two. Please find the exercise I’ve performed below.
SQL> create table t1 (col1 char(10), col2 varchar2(10));
SQL> insert into t1 values(‘Oracle’,'Oracle’);
1 row created.
Submitted by csm.dba on Tue, 2012-09-04 05:48
When I was doing a research on Oracle Database creation, through DBCA, last week, I came across a very interesting scenario which I couldn’t stop sharing with you :)
I have a cluster of machines (don’t confuse it with a RAC cluster but just a group of machines required for my application deployment) with 18.104.22.168 installed and a Database instance running.
I got a requirement to remove everything accumulated in the machine as a result of the Oracle installation and the Database creation: The installation directories, the datafiles, oratab entries etc…
Submitted by csm.dba on Tue, 2012-09-04 05:47
Hi Oracle geeks,
Last Friday, I’ve noticed a strange thing happening in my 22.214.171.124 Database: I’m able to create objects in a tablespace which is marked READ ONLY !!!
Don’t believe this?? See the below
SQL> create tablespace ro datafile ‘/xxx/RO.DBF’ size 10M AUTOEXTEND ON;
SQL> alter tablespace ro read only;
SQL> select status from dba_tablespaces where tablespace_name=’RO’;
SQL> sho user
USER is “CSM“
Submitted by manasn on Sun, 2012-08-12 17:58
I have just joined an in flight project and find the lead data modeler has created a name value pair data model.
The reason given was flexibility of data model considering some records can have as many as 900 attributes. The .Net application team seem to be loving it, as they can code everything with very few tables in mind.
I feel the model is difficult to query, difficult to load and difficult to syndicate and in all likelyhood will suffer from poor performance. Also the data model can't be considered as a rich metadata repository and difficult to understand.
Submitted by mbartov on Fri, 2012-08-10 11:07
I just posted a complete integrated set of tools to manage, monitor and tune the Oracle database.
It is free, no registration or email is required. I will just appreciate any kind of feedback to make it better.
The package comprises the following topics:
This section allows you to view and maintain virtually all database objects, including partitioned tables and materialized views. It also includes a function to view inter-dependency between objects.