Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Restart Database Command

Matheus BoesingJul 1 2016 — edited Jul 28 2016

Sometimes the DBA just want to restart a database to enable a parameter value or change the pfile to spfile, or things like that. For these cases the is actually needed to shutdown database than startup the database. But it could have a ‘restart’ command to automatically make the shutdown/startup with parameters. Thinking like that, it can have ‘levels’ of restart, to avoid all process of checkpoint, flush data to disk, switch log file, and etc OR instance recover (in case of abort) like:

1. Complete Restart (similar to actual shutdown/startup):

SQL> RESTART COMPLETE

Database closed.

Database dismounted.

ORACLE instance shut down.

ORACLE instance started.

Total System Global Area  812529152 bytes

Fixed Size                  2264280 bytes

Variable Size             960781800 bytes

Database Buffers           54654432 bytes

Redo Buffers                3498640 bytes

Database mounted.

Database opened.

2. Quick Restart (kill all sessions and restart PMON, SMON, and others, but not flush data to disk neither refresh SGA structure):

SQL> RESTART QUICK

Database closed.

Sessions Killed.

Background Processes Restarted.

Database opened.

It might be combined to the current syntax used by SHUTDOWN or STARTUP, examples:

SQL> RESTART QUICK ABORT; -- (shutdown with abort)

SQL> RESTART COMPLETE [NO]MOUNT; -- (shutdown and startup database nomounted or mounted state only)

SQL> RESTART QUICK ABORT SPFILE=‘/new/location/pfile’; -- (shutdown abort and start with other SPFILE)

Another advantage is to enable QUICK RESTARTS to activities like enable or disable ARCHIVELOG, FLASHBACK and other things that, I think, not necessary demands a COMPLETE instance restart.

Other databases like MySQL have this kind of implementation and it’s very useful.

Comments

Sdhamoth-Oracle

Hi,

Did you set TNS_ADMIN environment variable? If not, can you try after setting it?

Thanks,

Senthil

TheVenkster

Senthil:

What should it point to?

Anyway, I re-installed both the 64-bit Oracle DB and the 32-bit client. There are two sets of TNSNames.Ora, Listener.Ora and SQLNet.ora, one for the 64-bit and one for the 32-bit in their respective folders.

I have no problem creating an ODBC DSN for the 64-bit version. The link connects fine to the DB

I have two TNS Listeners defined, one for the 64-bit and one for the 32-bit. While the 64-bit uses Port 1521, I am using Port 1522 for the 32-bit; I also made sure that Listener.ora refers to the same port. But when I use Oracle Net Configuration Assistant to configure Local Net Service Name Configuration to test the Service, it says "TNS:listener does not currently know of the service requested in connect descriptor.

I did check that both the TNS Listener services are running.

venki

TheVenkster

Senthil:

I don't know what happened but now, everything works just as expected. I am able to attach Oracle DB tables to an Access database using ODBC. I am able to also connect to the DB using the 64-bit drivers.

Venki

1 - 3

Post Details

Added on Jul 1 2016
5 comments
10,083 views