[dgoli]

hi friends,

I have installed OTM5.5 CU4 on Windows Server 2003 Enterprise Edition SP2.
After starting otmapp55,otmweb55 and otmwebtomcat55 in sequence,I can access the OTM instance using the url http://systemName

But when I try to login using the default users dba.admin or guest.admin or servprov.admin,I get an error saying

A connection to the server could not be established: {exception=null} (user=GUEST.ADMIN)

When I check the cosole.log located under OTM_HOME/logs/weblogic/,it says

INFO | jvm 1 | 2008/06/04 18:20:31 | java.sql.SQLException: ORA-00942: table or view does not exist
INFO | jvm 1 | 2008/06/04 18:20:31 |
INFO | jvm 1 | 2008/06/04 18:20:31 | at oracle.jdbc.driver.DatabaseError.throwSqlException (DatabaseError.java:112)
INFO | jvm 1 | 2008/06/04 18:20:31 | at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoe r.java:331)
INFO | jvm 1 | 2008/06/04 18:20:31 | at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoe r.java:28
INFO | jvm 1 | 2008/06/04 18:20:31 | at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java: 745)
INFO | jvm 1 | 2008/06/04 18:20:31 | at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4 CPreparedStatement.java:216)
INFO | jvm 1 | 2008/06/04 18:20:31 | at oracle.jdbc.driver.T4CPreparedStatement.executeFor Describe(T4CPreparedStatement.java:810)
INFO | jvm 1 | 2008/06/04 18:20:31 | at oracle.jdbc.driver.OracleStatement.executeMaybeDes cribe(OracleStatement.java:1039)
INFO | jvm 1 | 2008/06/04 18:20:31 | at oracle.jdbc.driver.T4CPreparedStatement.executeMay beDescribe(T4CPreparedStatement.java:850)
INFO | jvm 1 | 2008/06/04 18:20:31 | at oracle.jdbc.driver.OracleStatement.doExecuteWithTi meout(OracleStatement.java:1134)
INFO | jvm 1 | 2008/06/04 18:20:31 | at oracle.jdbc.driver.OraclePreparedStatement.execute Internal(OraclePreparedStatement.java:3339)
INFO | jvm 1 | 2008/06/04 18:20:31 | at oracle.jdbc.driver.OraclePreparedStatement.execute Query(OraclePreparedStatement.java:3384)
INFO | jvm 1 | 2008/06/04 18:20:31 | at weblogic.jdbc.wrapper.PreparedStatement.executeQue ry(PreparedStatement.java:124)
INFO | jvm 1 | 2008/06/04 18:20:31 | at glog.util.jdbc.noserver.SqlQuery.executeQuery(SqlQ uery.java:146)
INFO | jvm 1 | 2008/06/04 18:20:31 | at glog.util.jdbc.noserver.SqlQuery.resetArguments(Sq lQuery.java:124)
INFO | jvm 1 | 2008/06/04 18:20:31 | at glog.util.jdbc.noserver.SqlQuery.open(SqlQuery.jav a:94)
INFO | jvm 1 | 2008/06/04 18:20:31 | at glog.server.useraccess.UserAccessSessionBean.getUs erAccess(UserAccessSessionBean.java:151)
INFO | jvm 1 | 2008/06/04 18:20:31 | at glog.server.useraccess.UserAccessSessionServerSide EJBWrapper.getUserAccess(UserAccessSessionServerSi deEJBWrapper.java:70)
INFO | jvm 1 | 2008/06/04 18:20:31 | at glog.server.useraccess.UserAccessSessionHome_uzvgz z_EOImpl.getUserAccess(UserAccessSessionHome_uzvgz z_EOImpl.java:154)
INFO | jvm 1 | 2008/06/04 18:20:31 | at glog.server.useraccess.UserAccessSessionHome_uzvgz z_EOImpl_WLSkel.invoke(ILweblogic.rmi.spi.InboundR equest;Lweblogic.rmi.spi.OutboundResponse;Ljava.la ng.ObjectLweblogic.rmi.spi.OutboundResponse;(Unk nown Source)
INFO | jvm 1 | 2008/06/04 18:20:31 | at weblogic.rmi.internal.BasicServerRef.invoke(BasicS erverRef.java:477)
INFO | jvm 1 | 2008/06/04 18:20:31 | at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke( ReplicaAwareServerRef.java:10
INFO | jvm 1 | 2008/06/04 18:20:31 | at weblogic.rmi.internal.BasicServerRef$1.run(BasicSe rverRef.java:420)
INFO | jvm 1 | 2008/06/04 18:20:31 | at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(AuthenticatedSubject.java:363)
INFO | jvm 1 | 2008/06/04 18:20:31 | at weblogic.security.service.SecurityManager.runAs(Se curityManager.java:147)
INFO | jvm 1 | 2008/06/04 18:20:31 | at weblogic.rmi.internal.BasicServerRef.handleRequest (BasicServerRef.java:415)
INFO | jvm 1 | 2008/06/04 18:20:31 | at weblogic.rmi.internal.BasicExecuteRequest.execute( BasicExecuteRequest.java:30)
INFO | jvm 1 | 2008/06/04 18:20:31 | at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:219)
INFO | jvm 1 | 2008/06/04 18:20:31 | at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:17

I have run the "Setup Security Roles" procedure as glogowner in the d/b.

Can someone suggest what could be the problem.

Thanks for your time,
Durga

[chrisplough]

Durga,

It appears that there is a problem with the installation / configuration of the OTM DB. I'd go back to the OTM Administration Guide and look at the section "Installing Oracle Transportation Management on the Database Server". Ensure that you've followed all of the steps, including verifying the import logs and running all of the post-import verification steps.

Also ensure that you've run the DB patch scripts to update the schema to CU04 after you've verified that the whole import process proceeded without issue.

--Chris

[chrisp]

1. Log on to the database server as sys user and edit the init.ora file relating to the database instance on which the CU3 install is being done.

2.Change the value for the parameter, O7_DICTIONARY_ACCESSIBILITY to TRUE
The line should read: O7_DICTIONARY_ACCESSIBILITY=TRUE

3. Re-start the database and then run the dbpatch_55.sql

4. Make sure that the errors are not shown now

[nick.polites]

One thing to note...if O7_DICTIONARY_ACCESSIBILITY=TRUE isn't enable before you import the out of box dump file then you need to start from scratch and import that because the import will not complete successfully without this parameter.

[dgoli]

Hello everyone,

Thanks for your time in replying.

Let me explain my situation here.Pls apologise for not providing complete details before.

We have our DB server,Oracle 10g,running on a different machine,say m1.
Also we have OTM 5.5 instance running on Unix platform on a machine m2.
Now we are installing OTM 5.5 on a Windows machine,say m3,so that some users can use this instance.

we have executed the set_*_roles.sql(don't remember exact name) as mentioned in the ADMIN guide.

The OTM instance on m3 is trying to connect to DB instance running on m1.
Sometimes we get the following error in weblogic\console.log when i start the OTMAPP55,OTMWEB55 AND OTMWEBTOMCAT55

INFO | jvm 1 | 2008/06/05 19:57:02 | cause.WorkflowManager.0006 (classesItem=class glog.server.workflow.process.ProcessControlTimer)
INFO | jvm 1 | 2008/06/05 19:57:02 | java.sql.SQLException: Listener refused the connection with the following error:
INFO | jvm 1 | 2008/06/05 19:57:02 | ORA-12519, TNS:no appropriate service handler found
INFO | jvm 1 | 2008/06/05 19:57:02 | The Connection descriptor used by the client was:
INFO | jvm 1 | 2008/06/05 19:57:02 | fqdn:1521:OTMDEV
INFO | jvm 1 | 2008/06/05 19:57:02 |
INFO | jvm 1 | 2008/06/05 19:57:02 |
INFO | jvm 1 | 2008/06/05 19:57:02 | java.sql.SQLException: Listener refused the connection with the following error:
INFO | jvm 1 | 2008/06/05 19:57:02 | ORA-12519, TNS:no appropriate service handler found

under weblogic\weblogic.log,we found this exception

weblogic.common.ResourceException: 96:Could not create pool connection. The DBMS driver exception was: Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found
The Connection descriptor used by the client was:
fqdn:1521:OTMDEV
- with nested exception:
[weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found
The Connection descriptor used by the client was:
fqdn:1521:OTMDEV

When i attempt login,I found the following errors for different users under tomcat/console.log

INFO | jvm 1 | 2008/06/05 20:12:03 | cause.Security_UserBadCredential (userName=DBA.ADMIN)

for GUEST.ADMIN
INFO | jvm 1 | 2008/06/05 20:13:25 | java.sql.SQLException: Pool connect failed : java.sql.SQLException: Connection Pool PRIMARY_JTS does not exist.

for SERVPROV.ADMIN
INFO | jvm 1 | 2008/06/05 20:13:25 | java.sql.SQLException: Pool connect failed : java.sql.SQLException: Connection Pool PRIMARY_JTS does not exist.

Sometimes when I attempt login we get the following error
INFO | jvm 1 | 2008/06/05 20:33:52 | java.sql.SQLException: ORA-00942: table or view does not exist

Don't really understand what is happening here.
My point is that,since we are making use of DB instance which is upgraded to CU4 and already being used by OTM instance on m2,I don't feel the necessity to go through all the steps mentioned in the section "Installing Oracle Transportation Management on the Database Server" and running the DB patch scripts to update the schema to CU04.

Pls correct me if I assumed anything wrong.

Thanks for your time in reading my posting.
Durga

[nick.polites]

Durga,

As I have mentioned in my earlier post, you need to check you glog.properties entries as the database connection information is not correct.

You can see from your log files it is not correct:
fqdn:1521:OTMDEV

the fqdn would show up here.

All of the stack information you are getting is due to the application server not being able to connect to the database.


Also you shouldn't connect two application machines to the same database server without scalability enabled as your caching and data will become corrupt.

Even in scalability you need to have the same platform O/S platforms as the JDK is differnt between Solaris (Sun) and Windows (Jrockit).

[nick.polites]

Sorry getting confused with all of the posts with property entries not being correct . Your original post had errors which were db related, thus why everyone suggested you start over again. The new error you have indicates a problem with your connection to the db. But again take my advice and do not have both machines connected simultaneously to the database server otherwise you will have major problems down the road.

[dgoli]

Hello everyone,

Thanks for your time in replying my post.

Mr.Nick,I understand your concern of having two OTM instances on diff OS accessing the same DB server.As of now,my only concern is to get the OTM instance on windows connect to the DB Server.

As many of you have suggested,I assume the problem is with the App Server(Weblogic) unable to connect to the database.

I see a property section in glog.propeties as follows
# application server type
glog.app.server.name=weblogic
appserver.protocol=t3://

When I try to login,I see the following enty in tomcat/console.log

For DBA.ADMIN : Authentication Failed for user DBA.ADMIN
For GUEST.ADMIN : java.sql.SQLException: ORA-00942: table or view does not exist
For SERVPROV.ADMIN : java.sql.SQLException: ORA-00942: table or view does not exist

I changed the appserver.protocol prop to http://
,restarted the server and upon attempting to login I get the same error.

I checked the file weblogic.log under logs/weblogic directory.I found an a warning that reads as bea 149317.

The description for this warning says
BEA-149317
Warning: Application app is configured with a deprecated deployment protocol and will be deployed as such.
Description
The application is configured with the TwoPhase attribute set to false or left unspecified. While supported, the application cannot take advantage of numerous features (such as application scoped resources) using the deprecated deployment protocol.Cause
A deprecated deployment configuration was found in the domain configuration.Action
No action required. However, consider reconfiguring the application to use two-phase deployment. To do so, the application must be udeployed and then deployed again using either the console or weblogic.Deployer.
Even though not required,I changed the attribute TwoPhase from False to True in the file config.xml located under OTM_HOME\weblogic\config\gc3domain

When I restarted the server,I don't see the warning bea 149317 in weblogic.log.
But end up with the same errors as above when I try to login.

Can somebody suggest an approach at this point.I am attaching my glog.properties as txt file.

glog.txt

Thanks for your time,
Durga

Originally Posted by nick.polites

Sorry getting confused with all of the posts with property entries not being correct . Your original post had errors which were db related, thus why everyone suggested you start over again. The new error you have indicates a problem with your connection to the db. But again take my advice and do not have both machines connected simultaneously to the database server otherwise you will have major problems down the road.

[nick.polites]

Durga,

Don't change the t3:// to http:// otherwise you won't get the application to work at all. The t3 needs to be there.

You have verified that the database parameters in your glog.properties are correct?
dbserver=hydhtc60432d.domainName is the correct URL?

If they match exactly what you have on your working instance then the only thing I can think of is you don't have the same CU patch applied otherwise you would be seeing the same issue on your other instance.

Post your glog.properties from your other working instance so I can compare the parameters.

Nick

[dgoli]

Mr.Nick,

Thanks for your reply.

I changed the appserver.protocol value back to "t3://".

Also,the domainName in the value dbserver=hydhtc60432d.domainName isn't actual value.I changed it bcs I am not sure if I can post the domainName in a forum.But it is the correct value as per the domain we are working.

I checked both the glog.properties and the only major diff I see is : the unix prop file has
glog.webserver.xsl.debug=true which windows prop file doesn't have.

I am posting both the files in case you wish to verify.Pls note the two OTM Instances are accessing two different DB instances on two different DB servers.I thought both OTM instances are accessing the same DB instances until I saw the properties file of the OTM instance running on the UNIX.Sorry for posting wrong info.

glog.txt
glog(Unix).txt

Regarding the same CU patch you mentioned before,I think the DB instance for the windows is already upgraded to CU4.

Pls let me know what could be going wrong.

Thanks for your time,
Durga

Originally Posted by nick.polites

Durga,

Don't change the t3:// to http:// otherwise you won't get the application to work at all. The t3 needs to be there.

You have verified that the database parameters in your glog.properties are correct?
dbserver=hydhtc60432d.domainName is the correct URL?

If they match exactly what you have on your working instance then the only thing I can think of is you don't have the same CU patch applied otherwise you would be seeing the same issue on your other instance.

Post your glog.properties from your other working instance so I can compare the parameters.

Nick