I have two full sets of close database files backup. One on 28 June
and another on 29 June.
Today, 30 June, I need to restore the whole database by using the
backup files on 29 June.

Early in my career, I was accustomed to seeing simple, sequence-
generated surrogate keys. Seemed clean and logical. Later in my
career, I saw seemingly monstrous (to me) composite keys of up to 5
fields. Found them initially repulsive because they made queries

In a pre-existing project, many tables reference domain (lookup)
tables of the general structure:
#   COL_NM (column name) -- a primary key containing a human-
intelligible value; max varchar length varies by table, but typically

I have many tables which need sequences.I think there are two
solutions.One is that I create each sequence for each table.The other
is that I create only one sequence for many tables.Which is the better
one(or another solution)?And Why?

The following query, using the ON clause, works fine:
-- Query #1
select e.employee_id, d.department_id, d.department_name
from employees e INNER JOIN departments d

10.2.0.4 on AIX if it matters:
I think we will end up with n number of databases on various machines,
and an RMAN catalog database elsewhere (I'm not concerned with how the
RMAN catalog is itself backed up; that is someone else's problem).

   we met problem with oracle8.1.7(on HP-UX)  SGA tuning.
   The Oracle server runs on HP-UX11i.  Previously, the server has
16GB RAM and 20CPU installed.
   The business data keeps increasing in past year which make us

I restored a cold backup and standby control file from 6/26.  When I
recover it's asking for an archive file from 6/21 even though the
database was restored from a cold backup on 6/26.  Our cold backup
performs a checkpoint and logfile switch prior to taking the DB down

In SQLServer I detach from one server and then attach it to another
server. Is something like this possible with Oracle ?
thanks
Sunit

We are using Oracle 10.2.0.3.0. I have a simple query like this -
select *
from large_table, small_table
where small_table.col = large_table.col (+)

Here's some advice for you about the pseudo-columns ROWID, ROWNUM and
their behaviour with views.
* As a general rule avoid using ROWID espcially with complex views
made up of multiple base tables where a DISTINCT clause is used. The

My db has three columns : pool id, pool name and pool description
1. Pool id is unique
2. Pool name is always either suffixed by intl or core. But there is
not formal constraint or foreign key relationships anywhere

We have a process that inserts a few million records in a table (It is
not a direct path load). In the entire process the max time the
process waits is for the event "db file sequential read".
The data files in the database are totally full (Space remaining shows

so far my oracle experience has been on 8i with only PL/SQL development on 9
and later.
I'm just going through some questions in preparation for a 10g Admin 1 exam
and find (among others) a question for which the answer seems to be less than

I'm working on a project using Oracle Text, and wondering if it is
possible display "relevant" parts of any documents returned by a
search (in a similar fashion to Google).
Heres a summary of what I have so far: