ORA-27206 on Oracle 10G RAC

 

Sometimes you may see error shown below when incremental backup failed. To solve the issue, you have to resync the archive catalog.

Solution/Procedure:-

1.Connect to both db server:-

DB1 SERVER

i)rman target /

crosscheck archivelog all;

--- Once the process  completed ---

Connect to catalog db to perform re sync process:-

ii) rman target / CATALOG rman/rman@catdb

resync catalog;

DB2 SERVER

i)rman target /

crosscheck archivelog all;

--- Once the process  completed ---

Connect to catalog db to perform re sync process:-

ii) rman target / CATALOG rman/rman@catdb

resync catalog;

What is different between database, instance and service name

//* Knowledge Sharing *//

Database

It is the name of the physical database structure. It is stored at the control file and datafile header. It is used to identify all physical structures

that belong to the same database. It can be defined at install time. It is originally defined by the static instance parameter database name, and it cannot be changed,

and the only way to change it is by means of rebuilding the control file and resetting the log sequence.

Instance Name

It is the name of the memory structures + Background process (MEM + BGP) use to mount/open a database. In a RAC environment there are more than one

instance opening the same database, and each instance has a different name. On a single instance (non rac) environments, the instance name and the database name are

named (generally) the same. There is no reason to name the instance and the database differently.

Instance name is defined by the ORACLE_SID environment variable (unix) and by the windows service name (windows).

In a connect string this can be used to establish connection to a database, however this is valid for pre-8i versions (8.0 compatible) and even though it can work with

10g databases, it is not a good practice as it reduces the functionality provided since 8i.

Service Name

 This is a way to identify a target instance to get connected to. It is defined by the dynamic instance parameter service names, note the names word, it

is plural, that is because an oracle instance can have several service names. The concept service is more frequently used in a single instance to refer to an instance

with several alias. In a RAC environment it is used to balance power, create failed over / stand by instances and it is used in combination with resource manager.

Oracle Training for April 2009

*/New entries can be found below this entry/*

For those who planned to enroll Oracle Admin class for 10G (in Malaysia only), you can find those suitable dates for you from CSC. This training will be held at Amcorp Mall Petaling Jaya.

Oracle Database 10G: Administrator Workshop II
Date:6th April - 10th April 2009

Oracle Database 10G: OEM Grid Control R2
Date: 13th April - 17th April 2009

Oracle Database 10G: RAC for Adminstrator R2
Date:20th April - 24th April 2009

Anything, please make a call to +603-79588605 || www.csc.com

||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||=||

Oracle Malaysia also provides in-class training. Please have a look on available dates.

Oracle Database 9i: Administrator Fundamentals II
Date: 6th April - 10th April 2009
Location: Petaling Jaya

Oracle Database 10G: Administrator Workshop I
Date:13th April - 17th April 2009
Location:Oracle Corporation Malaysia Berhad, Menara Citibank, Kuala Lumpur

Oracle Database 10G: Administrator Workshop II
Date:20th April - 24th April 2009
Location:Oracle Corporation Malaysia Berhad, Menara Citibank, Kuala Lumpur

Oracle Database 10G: Performance Tuning
Date: 27th April - 30th April 2009
Location:Oracle Corporation Malaysia Berhad, Menara Citibank, Kuala Lumpur

Oracle Database 10G: Data Guard Administration R2
Date:13th April - 15th April 2009
Location:Oracle Corporation Malaysia Berhad, Menara Citibank, Kuala Lumpur

Oracle Database 11G: New Features for Administrator
Date:20th April - 24th April 2009
Location:Oracle Corporation Malaysia Berhad, Menara Citibank, Kuala Lumpur

For more information, please call Oracle at +603-21782517 || 1 800 80 6277

Who to blame?

I got this from OTN, there's a guy posted his entry:

Hi
All,

I have been working since 2 years and i have never seen ORA-00020 process value limit 400 exceeded. due to this it does not allow new connection to the database.

I am wondering why this happen all at sudden because database was running fine until now. do you know where i should look to find out root cause of the problem.


and see what the other guy answers:
Why would it be a problem?
Did your user community grow?
Or do you think for every problem
1 Oracle is too blame
2 I can't do any research, so let's dump it in an OTN forum
3 My boss beats me up for every character I type here, so I'll post an useless question without platform and version info, and sit back with my feet on my desk, and let those poor volunteers sweat.

What say you??

How to reduce UNDO tablespace

Undo tablespace is used to keep unrolled data. Sometime it may increase tremendously because some of the SQL statement is not committed.

We can reduce the tablespace sizing for undo tablespace by following method. Assuming your current undo tablesapce name is 'UNDOTBS':
1. Ensure there' s no application is connected to the database.
2. Login as Oracle user and connect to SQL as sysdba. Then create another undo tablespace and set as default.
SQL>create undo tablespace undonew datafile '/undonew.dbf' size 1024M;
SQL>alter system set undo_tablespace='undonew';
By doing this, it will change the default undo_tablespace id undonew in spfile. If you are not using spfile. then you may skip this and edit the undo_tablespace parameter in initfile.
3. Drop the old undo tablespace including all.
SQL>drop undotbs tablespace including contents and datafiles;

4. Shutdown database.
5. After database has been shutting down, you may edit your initfile to change the undo_tablespace parameter to 'undonew'.
6. Startup database
7. Create the old database 'UNDOTBS' and set it as default.
SQL>create undo tablespace UNDOTBS datafile '/undo01.dbf' size 1024M;
SQL>alter system set undo_tablespace='UNDOTBS';

As usual, if you are using initcfile, change the parameter value after shutting down database in initfile.

8. Drop the undonew tablespace including contents.
SQL>drop undonew tablespace including contents and datafiles;

9. Shutdown database.
10.Change the undo_tablespace parameter from undonew to undotbs if you are using initfile.
11. startup database.

ORA-04021: timeout occurred while waiting to lock object

This morning I received an e-mail from my college... she got an error while doing upgrade on her environment. This had happen few times when they finish do Fresh Install, and bring up the middleware and later when middleware has been brought down, they got error while doing upgrade.

I was a looking for a solution about this, without using DBA studio (still using Oracle9i). So what I asked them to do:

1. Bring down the middleware.
2. Connect to SQL as sysdba, and check the processes running using that schema/dbuser.
SQL>select sid, serial#, schemaname from v$session;

3.They will see some output and kill the processes using:
SQL>alter system kill session 'sid,serial#';

4.At one point, they schemaname still exist but we should check the status for that session.
SQL>select sid, serial#, status, process from v$session where schemaname='SCHEMANAME';
If the status given is 'KILLED', means all processes has been killed. Then they able to proceed with their installation.

whatever

This is all about my dreamworld... not so real but some are reals..

happy reading..