RMAN-03009: failure of backup command on ORA_DISK_1 channel

I encountered this error while using RMAN CONVERT DATABASE COMMAND. The exact error was as follows:
RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/27/2008 12:23:09ORA-09210: sftopn: error opening fileOSD-04002: unable to open fileO/S-Error: (OS 3) The system cannot find the path specified.

I was trying to put the converted files on z:\ which was a mapped drive. After opening an SR I came to know that I was to use UNC naming i.e. I had to use \\servername\sharename in the place of z:\.

Listener forks on 10.2.0.3 if LD_ASSUME_KERNEL is set

Found an interesting problem.

If the .bash_profile has LD_ASSUME_KERNEL parameter the listener forks itself as given below:
oratest 13305 1 0 16:59 ? 00:00:00 /u04/oracle/testdb/10.2.0//bin/tnslsnr TEST -inheritoratest 13306 13305 0 16:59 ? 00:00:00 /u04/oracle/testdb/10.2.0//bin/tnslsnr TEST -inheritoratest 13307 13306 0 16:59 ? 00:00:00 /u04/oracle/testdb/10.2.0//bin/tnslsnr TEST -inheritoratest 13308 13306 0 16:59 ? 00:00:00 /u04/oracle/testdb/10.2.0//bin/tnslsnr TEST -inherit

If this parameter is removed and the env file is resourced the listener behaves properly.

oratest 13370 1 0 17:01 ? 00:00:00 /u04/oracle/testdb/10.2.0//bin/tnslsnr TEST -inheritoratest 13374 13339 0 17:01 pts/4 00:00:00 grep tnslsnr

I also have another database which is running on 10.1.04 and I see the listener forking (this does not have the parameter in the .bash_profile)

oradev 12971 1 0 15:07 ? 00:00:00 /u01/oracle/devdb/10.1.0/bin/tnslsnr DEV -inheritoradev 12972 12971 0 15:07 ? 00:00:00 /u01/oracle/devdb/10.1.0/bin/tnslsnr DEV -inheritoradev 12973 12972 0 15:07 ? 00:00:00 /u01/oracle/devdb/10.1.0/bin/tnslsnr DEV -inheritoradev 12974 12972 0 15:07 ? 00:00:00 /u01/oracle/devdb/10.1.0/bin/tnslsnr DEV -inherit

I guess I have to get a patch from oracle for this or upgrade the same to 10.2.0.2.

Windows NT to Linux Migration - Unable to login to Self Service

While doing the migration to Linux I was stumped by an error. I was not able to login using Self Service but was able to login using dev60/f60cgi. This error kept haunting me and giving headaches for two weeks.

The error was as follows:

oracle.jsp.JspServlet: initOSS: Caught throwable in AppsLocalLogin.jsp : java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundErrorat oracle.apps.fnd.sso.SSOManager.getAppsServletAgent(SSOManager.java:1998)at oracle.apps.fnd.sso.SSOManager.getLoginUrl(SSOManager.java:338)at _oa__html._AppsLocalLogin._jspService(_AppsLocalLogin.java:483)at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119)at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417)at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267)at oracle.jsp.JspServlet.internalService(JspServlet.java:186)at oracle.jsp.JspServlet.service(JspServlet.java:156)at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456)at org.apache.jserv.JServConnection.run(JServConnection.java:294)at java.lang.Thread.run(Thread.java:534)
I had enabled jserv logging but it was not giving any insights. After 2 weeks of intense followup with Oracle Support it turned out that while the copy of $JAVA_TOP/COM is done from Windows to Linux the COM directory needs to be moved to lowercase i.e. com as Windows is case insensitive and Linux is not.

Oracle Support has created a metalink note 604529.1 which is not published yet.

ORA-12505 TNS:listener could not resolve SID given in connect description

Recently we changed the port of the DB from default 1521 to 1532. After this change it was noticed that clients could not connect although tnsping was working.

Metalink note 111911.1 points to registration of the instance name with the listener. Did the steps in the note and clients could connect to the instance.
Reason is prior to Oracle 8i, a listener was statically configured (listener.ora) to service a given set of SIDs. From 8i, PMON dynamically registers a database service with the listener.