If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Originally posted by nagarjuna nah.. Server processes do coalesc when you use the 'alter tablespace tsname coalesce;' command.

Where did you hear that????? Server proces *can never* write to the database file. Never! It can only read from database file. It would be a shocking news to me if you could prove me wrong on that.

Why would be any different with ALTER TABLESPACE COALESCE command? How does it differ with any other CREATE, ALTER, etc commands? No matter what command is executed, server process can only *read* from datafiles. All modifications that must be performed by server processare are executed in the buffer cache, and it is DBWR that performs any datafile writes associated with that.

Realy, can you provide any explanation/URL regarding what is so special about ALTER TABLESPACE COALESCE in this context?

Jurij ModicASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?

Well, it hasn't taught you everything, and what id has taught you is certanly not 100% complete. For example in the above quote it is not mentioned that LGWR is one of those processes that write to controlfiles.

And most importantly, your official OCP training does not provide any answer to the original question of this thread: Which process is responsible for writing changed database names into the controlfile?

Jurij ModicASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?

I don't remember coming across the term "foreground process" in this context.

It's user process not foreground process. Sometimes we invoke userprocess at the server end when we open sqlsessions at the server. This is the scenarion when we learn Oracle at home installing the Oracle s/w in our home PC-server

Originally posted by jmodic Where did you hear that????? Server proces *can never* write to the database file. Never! It can only read from database file. It would be a shocking news to me if you could prove me wrong on that.

Why would be any different with ALTER TABLESPACE COALESCE command? How does it differ with any other CREATE, ALTER, etc commands? No matter what command is executed, server process can only *read* from datafiles. All modifications that must be performed by server processare are executed in the buffer cache, and it is DBWR that performs any datafile writes associated with that.

Realy, can you provide any explanation/URL regarding what is so special about ALTER TABLESPACE COALESCE in this context?

I may be wrong. But, coelescing is done by a server process when we use this "alter tablespace ...." command.

Originally posted by nagarjuna I may be wrong. But, coelescing is done by a server process when we use this "alter tablespace ...." command.

Hey, lets make one thing clear: (Almost) everything in the database "is done" by server process - create table, drop table, craete tablespace, create database, alter database, alter system, .... you name it ... - everything is "done" by server process. But what does expression "done" mean here? It means that server process performs all necessery changes *in the buffer cache* and in the buffer cache alone! But those changed buffers will *never* be written to the datafiles by server process. Never! There are background processes that are responsible for that and only those processes will ever be able to do that. It's as simple as that, and I can't see why you've exposed ALTER TABLESPACE COALESCE as something special - its just one of those DDL commands, nothing special about it.

Once again: the isue in this thread was: which process performs PHYSICAL WRITES into database (control) files.

Jurij ModicASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?