Oracle Service Registry (OSR) creates data file under $ORACLE_HOME/dbs

Issue and Cause:
---------------------------

After installing Oracle Service Registry (OSR) on SOA Suite; I found that it created a tablespace (if not renamed, it picks uddiuser by default) and put the data file under $ORACLE_HOME/dbs which I was not aware until I try to restore one of my backup taken at a later stage i.e after installing AIA on OSR. As the location for other SOA database datafiles was different; I never thought of taking backup of $ORACLE_HOME/dbs which made this data file out of sync and made my database backups INVALID / useless.


Fix:
----

As soon as OSR is installed, rename the datafile which is under $ORACLE_HOME/dbs and move it with other datafiles. This will make sure that this datafile is getting backed up every time with other datafile and backup is VALID and can be restored if needed.

RAC Instance not recognized by SRVCTL Utility

Issue:
-------

Version: 2 NODE 11.1.0.7 RDBMS RAC on 11.1.0.7 CRS + 11.1.0.7 ASM.

One of the RAC Instance is not being recongnized by SRVCRL; it was not getting started / stopped by SRVCTL utility. Below error were coming in adding / removing the instance when trying to fix it. In this example database sid is used as orcl1 and RAC nodes are NODEa and NODEb.

NODEa:/opt/ororcl1> srvctl status database -d orcl1
Instance orcl12 is running on NODE NODEb

NODEa:/opt/ororcl1> srvctl add database -d orcl1 -o /opt/ororcl1/product/11.1.0/rac -p +orcl1_DB/spfile.ora;
NODEa:/opt/ororcl1> srvctl add instance -d orcl1 -i orcl11 -n NODEa;
PRKO-2010 : Error in adding instance to NODE: NODEa
PRKR-1008 : adding of instance orcl11 on NODE NODEa to cluster database orcl1 failed.
CRS-0211: Resource 'ora.orcl1.orcl11.inst' has already been registered.
NODEa:/opt/ororcl1>
NODEa:/opt/ororcl1> srvctl modify instance -d orcl1 -i orcl11 -s +ASM1;
PRKO-2007 : Invalid instance name: orcl11


Cause:
--------

Database orcl1 doesn't recognize the instance keys anymore; Instance and database needs to be reconfigured with SRVCTL.


Resolution:
-------------

In this case please remove the instance with '-f' option

srvctl remove instance -d orcl1 -i orcl11 -f
srvctl remove instance -d orcl1 -i orcl12 -f
srvctl remove database -d orcl1 -f
srvctl config database


Try to add the database/instance again

srvctl add database -d orcl1 -o /opt/ororcl1/product/11.1.0/rac -p +orcl1_DB/spfile.ora;
srvctl add instance -d orcl1 -i orcl11 -n NODEa;
srvctl add instance -d orcl1 -i orcl12 -n NODEb;
srvctl modify instance -d orcl1 -i orcl11 -s +ASM1;
srvctl modify instance -d orcl1 -i orcl12 -s +ASM2;
srvctl setenv instance -d orcl1 -i orcl11 -T "TNS_ADMIN=/opt/ororcl1/product/11.1.0/rac/network/admin/orcl11_NODEa";
srvctl setenv instance -d orcl1 -i orcl12 -T "TNS_ADMIN=/opt/ororcl1/product/11.1.0/rac/network/admin/orcl12_NODEb";
srvctl start database -d orcl1;
srvctl status database -d orcl1;


Now both the Instances are getting recognized by SRVCTL.


NODEa:/opt/ororcl1> srvctl start database -d orcl1;
NODEa:/opt/ororcl1> srvctl status database -d orcl1;
Instance orcl11 is running on NODE NODEa
Instance orcl12 is running on NODE NODEb
NODEa:/opt/ororcl1> srvctl stop database -d orcl1;
NODEa:/opt/ororcl1> srvctl status database -d orcl1;
Instance orcl11 is not running on NODE NODEa
Instance orcl12 is not running on NODE NODEb
NODEa:/opt/ororcl1> srvctl start database -d orcl1;
NODEa:/opt/ororcl1> srvctl status database -d orcl1;
Instance orcl11 is running on NODE NODEa
Instance orcl12 is running on NODE NODEb

Design to Release PIP not working with SOA 10.1.3.4 + AIA 2.5 General Availability Version

Issue:
-----

We installed SOA 10.1.3.4, AIA 2.5 General Availability Version, Design to Release PIP but when we try to connect SOA applications from Agile web services, "PLMECOQUEUE" user account in SOA database got locked immediately. Ever after trying so many things, this was not working.

It turns out that one of init.ora parameter introduced in 11g is causing this issue. After disabling that parameter; Design to Release PIP started working as expected.

Resolution:
----------

Update init.ora file and change sec_case_sensitive_logon from TRUE to FALSE.