Connecting to an alternate Database UNIX Platform

Question

We were having a single node installation.
All our servers were on a single machine(old machine) but now we have separated
the database on to a new machine.
In short we can say we have two machine Apps server and Database server.
We have transferred the Db from old machine(now apps server) to new machine (now db server) and we have made relevant changes to TNSNAMES.ora and Listener.ora files.
Now we are running two listeners one db listener on db server and other apps
listener on apps server machine.
We are able to connect to the database through application as well as through
sql plus
Also we are able to start our concurrent managers.
Everything is fine But
PROBLEM IS :
1)APPS SIGN ON SCREEN WHERE WE HAVE TO SPECIFY USER NAME AND PASSWORD GOES INTO A HANG .IT HANGS FOR A MINUTE AND HALF ENDING UP WITH THE FOLLOWING ERRORS:
ERROR1 :APP-01564 : ORACLE ERROR 3123 IN AFPODBLOAD
CAUSE: AFPODBLOAD FAILED DUE TO ORA-3123:OPERATION WOULD BLOCK
ERROR2:FRM-40735 SPECIALTRIGGER RAISED UNHANDELED EXCETION ORA-03127
ORA-03127:NO NEW OPERATIONS ALLOWEDUNTIL THE ACTIVE OPERATIONS ENDS.
2) Many a times we are able to log in into the apps and while switching
responsiblitiy the screen goes into hangs and all the above messages repeats.
Many time this problem does not come and everything works fine
What we did ??
1)We have installed the Oracle Server on the new machine(db)machine.
2)Copied the database from old(now Apps Server) to new machine(now db server).
3)Changed the tnsnames.ora to point to new machine(now db server)
4)stared the listener on new machine(mow db server)
5) started forms server,web server listeners .
6) connected to db via the application
Did i miss any of the steps ??
I hope above information gives u clear picture of our Problem.
We then tried exactly the viceversa, ie the apps server was made as a DB server and the DB server as the apps server. But still the problem persists.
What we did ?
We did a fresh single node installation in our New DB Server machine. We installed the VISION instance. We started the database, db listeners, Apps listeners, forms server and concurrent manager. We were able to connect to Oracle Applications successfully.
Then we pointed our database to the old Apps Server by changing the right hand side of tnsnames.ora. But unfortunately, we are experiencing the same hang problem.
Both the machines are on Compaq tru unix 4.0f.
Is there some parameters to be set (other than tnsnames and listeners) ????

Answer 1

<p>got it working, here&#39;s some sample code.  </p><p> </p><p><%<br />    try{<br />        ReportClientDocument clientDoc = new ReportClientDocument();<br />        clientDoc.open(reportName, 0);<br />    <br />        ConnectionInfos connInfos = new ConnectionInfos();<br />        IConnectionInfo iConnInfo = new ConnectionInfo();<br /><br />        PropertyBag bag = new PropertyBag();<br />        bag.put("Database Class Name",driverName);    // "oracle.jdbc.driver.OracleDriver"<br />        bag.put("Connection URL",connectStr);        // "jdbc:oracle:thin:@dbName:1521:sid"<br />                            <br />        PropertyBag pb = new PropertyBag();<br />        pb.put(PropertyBagHelper.CONNINFO_CRQE_LOGONPROPERTIES ,bag);<br />        pb.put(PropertyBagHelper.CONNINFO_DATABASE_DLL ,"crdb_jdbc.dll");<br />        iConnInfo.setAttributes(bag);<br />        <br />        iConnInfo.setUserName(userName);<br />        iConnInfo.setPassword(password); <br />                <br />        iConnInfo.setAttributes(pb);<br />            <br />        connInfos.add(iConnInfo);<br />        session.setAttribute(reportName, clientDoc);<br />        session.setAttribute("reportSource", clientDoc.getReportSource());<br /><br />        //Setup viewer. Only going to include the relevant line, the rest can be found</p><p>        //elsewhere.<br /></p><p>        CrystalReportViewer oCrystalReportViewer = new CrystalReportViewer();                   oCrystalReportViewer.setDatabaseLogonInfos(connInfos);                                      }    </p><p>catch(ReportSDKExceptionBase exc)%></p>