Invalid XML/EXF/CATALOG/CATPROC component in registry

In one of my database, I found that my XML/EXF/CATALOG/CATPROC component in registry got invalid.


COMP_ID COMP_NAM STATUS
---------- ----------------------- ---------
EXF Oracle Expression Filter INVALID
CATALOG Oracle Database Catalog Views INVALID
CATPROC Oracle Database Packages and Types INVALID
JAVAVM JServer JAVA Virtual Machine VALID
XML Oracle XDK INVALID
CATJAVA Oracle Database Java Packages VALID

6 rows selected.


Steps below:

SHUTDOWN IMMEDIATE
STARTUP UPGRADE
@?/rdbms/admin/catalog.sql
@?/rdbms/admin/catproc.sql
@?/rdbms/admin/catexf.sql

-- To validate EXF components
@utlrp.sql

SHUTDOWN IMMEDIATE

STARTUP

Finally all components became valid:

SQL> select COMP_ID,COMP_NAME,STATUS from dba_registry;

COMP_ID COMP_NAM STATUS
---------- ----------------------- ---------
EXF Oracle Expression Filter VALID
CATALOG Oracle Database Catalog Views VALID
CATPROC Oracle Database Packages and Types VALID
JAVAVM JServer JAVA Virtual Machine VALID
XML Oracle XDK VALID
CATJAVA Oracle Database Java Packages VALID

6 rows selected.

SQL> select owner,count(*) from dba_objects where status='INVALID' group by owner;

OWNER COUNT(*)
------------------------------ ----------
PUBLIC 25
SYS 73
EXFSYS 20

Run utlrp

@?/rdbms/admin/utlrp.sql

SQL> select owner,count(*) from dba_objects where status='INVALID' group by owner;

OWNER COUNT(*)
------------------------------ ----------
PUBLIC 21
SYS 43
EXFSYS 2

SQL> SQL> select COMP_ID,COMP_NAME,STATUS from dba_registry;

COMP_ID COMP_NAM STATUS
---------- ----------------------- ---------
EXF Oracle Expression Filter VALID
CATALOG Oracle Database Catalog Views VALID
CATPROC Oracle Database Packages and Types VALID
JAVAVM JServer JAVA Virtual Machine VALID
XML Oracle XDK VALID
CATJAVA Oracle Database Java Packages VALID

6 rows selected.

WARNING: Inbound connection timed out (ORA-3136) after DR

I just want to share one of my experience today with this error.
We did a DR test on one of our informatica standby database server using flashback letting primary database up and used by the application. Basically here standby database was opened as standalone database after cancelling the media recovery and opening the database. Before opening we enabled flashback in the database.

There was n number of issues faced and i would like to write on it in a separate post. Lets discuss considering error Inbound connection timed out (ORA-3136)
After we got the standby database after the application test during DR to put it back in sync with primary database and we did so.
After syncing though i was seeing that both the primary and standby was in sync i was continuouly seeing below error in alert log if standby database:


WARNING: inbound connection timed out (ORA-3136)
Sun Oct 2 20:10:50 2011
WARNING: inbound connection timed out (ORA-3136)
Sun Oct 2 20:11:20 2011
WARNING: inbound connection timed out (ORA-3136)
Sun Oct 2 20:11:51 2011
WARNING: inbound connection timed out (ORA-3136)
Sun Oct 2 20:12:21 2011
WARNING: inbound connection timed out (ORA-3136)
Sun Oct 2 20:12:31 2011
WARNING: inbound connection timed out (ORA-3136)



When I checked it further in sqlnet.log, it tells that the connection to the standby database is coming continuously from Informatica production server


***********************************************************************
Fatal NI connect error 12170.

VERSION INFORMATION:
TNS for Solaris: Version 10.2.0.3.0 - Production
Oracle Bequeath NT Protocol Adapter for Solaris: Version 10.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Solaris: Version 10.2.0.3.0 - Production
Time: 02-OCT-2011 19:53:15
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=148.168.**.**)(PORT=12345))


***********************************************************************
Fatal NI connect error 12170.

VERSION INFORMATION:
TNS for Solaris: Version 10.2.0.3.0 - Production
Oracle Bequeath NT Protocol Adapter for Solaris: Version 10.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Solaris: Version 10.2.0.3.0 - Production
Time: 02-OCT-2011 19:53:25
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=148.168.**.**)(PORT=12345))
***********************************************************************


SQL> !nslookup 148.168.**.**)(
Server: 127.0.0.1
Address: 127.0.0.1#53

Non-authoritative answer:
53.67.168.148.in-addr.arpa name = server001.pfizer.com.

Authoritative answers can be found from:


========================================================================


When i checked the server details of server001.pfizer.com in CMDB, i got to know that its informatica production application server. Then it understood that during DR application would have been pointed to the DR standby databaase and later after DR, they missed to disconnect those informatica connection to DR standby database.

Then i requested informatica team to disconnect and disable those connection to standby database from informatica production application server. Once this was done this error WARNING: Inbound connection timed out (ORA-3136) disappeared :).