Starting and Stopping Database Control

Database control is the standalone management console. Each database has its own database control console. It requires the dbconsole process to be started prior to use.

To start the dbconsole process

$ emctl start dbconsole

To stop the dbconsole process

$ emctl stop dbconsole

To view the dbconsole process status

$ emctl status dbconsole

Thanks

Starting and Stopping Listener Service

To view the status of the listener

$ lsnrctl status [listener_name]

To start the listener

$ lsnrctl start [listener_name]

To stop the listener

$ lsnrctl stop [listener_name]

Thanks

Start and Stop iSQL*PLUS

The iSQL*PLUS Application Server must be running to start an iSQL*PLUS session. To start or stop the iSQL*PLUS Application Server on UNIX use the following commands,

$ isqlplusctl start

To Stop

$ isqlplusctl stop

Thanks

Ports used for OEM

To know the default ports used check the files portlist.ini or ports.ini

Oracle 10g

$more $ORACLE_HOME/install/portlist.ini

Oracle 9i

$more $ORACLE_HOME/Apache/Apache/ports.ini

Thanks

TSPITR Recovery Set Dependencies

Before performing TSPITR you must confirm whether the recovery set is fully contained. That means whether the objects present in the tablespaces that are included in the recovery set have any references to the objects that are present in the tablespaces that are not included in the recovery set.

To find out the objects that overlap the recovery set boundaries use the TS_PITR_CHECK view. For eg, if the recovery set contains two tablespaces (TS_RAIMS and TS_CMSCRM) then use the following query,

SQL> Select *from sys.ts_pitr_check
where ( ts1_name in ('TS_RAIMS', 'TS_CMSCRM')
and ts2_name not in ('TS_RAIMS', 'TS_CMSCRM') )
or ( ts1_name not in ('TS_RAIMS', 'TS_CMSCRM')
and ts2_name in ('TS_RAIMS', 'TS_CMSCRM') );

Proceed with TSPITR only when this query returns no rows.

Use the following query to check on all the tablespaces in the database,

SQL> Select * From SYS.TS_PITR_CHECK
Where ( 'SYSTEM' IN (TS1_NAME, TS2_NAME)
and TS1_NAME <> TS2_NAME
and TS2_NAME <> '-1')
Or ( TS1_NAME <> 'SYSTEM' and TS2_NAME = '-1') ;

Thanks

Objects Lost after TSPITR

When TSPITR is performed on a tablespace the objects created after the recovery time will be lost. To view the objects that will be lost use the following query,

SQL> Select owner, name, Tablespace_name,
to_char(creation_time, ‘YYYY-MM-DD:HH24:MI:SS’)
From TS_PITR_OBJECTS_TO_BE_DROPPED
Where Tablespace_name in (‘SCOTT’)
And creation_time > TO_DATE(’01-JAN-09:07:05:15’,’YY-MON-DD:HH24:MI:SS’);


Thanks

Database Properties

Here is a query to view important database properties like default permanent, default temporary tablespaces, NLS settings etc.

SQL> Select * From Database_Properties;

Thanks

ORA-25153: Temporary Tablespace is Empty

When you recreate a control file or restore a controlfile from backup, you must recreate the tempfile in the temporary tablespace.

Alter temporary_tablespace add tempfile size xM reuse;

otherwise you will encounter the following error,

ORA-25153: Temporary Tablespace is Empty

Thanks

Page Space Error

Last week we created a second database in our test server. Suddenly we encountered the following errors in the alert file of both the database.

ORA-27300: OS system dependent operation:fork failed with status: 12
ORA-27301: OS failure message: Not enough space
ORA-27302: failure occurred at: skgpspawn3

Solution

Check for the page size.

$ lsps -a

It was 97% used. We increased the page space and the problem is solved.

Thanks.