Announcement

**chrisplough** · June 4, 2008, 14:06

Re: OTM 5.5 CU4 Installation

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** · June 5, 2008, 09:40

Re: OTM 5.5 CU4 Installation

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** · June 5, 2008, 12:08

Re: OTM 5.5 CU4 Installation

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** · June 6, 2008, 13:29

Re: OTM 5.5 CU4 Installation

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** · June 6, 2008, 13:41

Re: OTM 5.5 CU4 Installation

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** · June 6, 2008, 13:45

Re: OTM 5.5 CU4 Installation

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** · June 9, 2008, 07:00

Re: OTM 5.5 CU4 Installation

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** · June 9, 2008, 11:13

Re: OTM 5.5 CU4 Installation

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** · June 9, 2008, 13:37

Re: OTM 5.5 CU4 Installation

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

**nick.polites** · June 9, 2008, 13:43

Re: OTM 5.5 CU4 Installation

Ok with that being said then your problem is with the database then. First thing I would review is the database import log. Make sure everything imported without any errors. I'm guessing this is where the problem really is.

If that checks out, then I would go back and re-run all of the post import scripts starting at @create_vpd_package.sql. Rerun each script and be sure you get 0 errors when you recompile_invalid_objects for both reportowner and glogowner.

When you import the database, even though CU4 was installed as part of the app/web server, the database dump is from GA and must be patched to the latest CU by running dbpatch_55.

The table view does not exist errors indicate that something is wrong in the database.

Nick

**dgoli** · June 11, 2008, 10:06

Re: OTM 5.5 CU4 Installation

Mr.Nick,

Thanks for your reply.

Pls apologise for the confusion I have already created and the one I am about to create in this reply.

We have a working OTM instance(OTM1) on Unix connected to DB instance(DATA1).

Now I have installed OTM(OTM2) on Windows and trying to connect to DB instance(DATA2). The installation is successful.
We have executed all the database related scripts,verified the database structure and finally executed “insert_security_roles.sql” as GLOGOWNER for DATA2.
Everything seems fine as per Admin guide.

Finally,I am getting the Login screen
When I try to login into OTM2,we are getting different errors for different users.

When correct Login information is provided :

For DBA.ADMIN

INFO | jvm 1 | 2008/06/11 12:56:07 | Authentication Failed for user DBA.ADMIN
INFO | jvm 1 | 2008/06/11 12:56:07 |
INFO | jvm 1 | 2008/06/11 12:56:07 | at jrockit.reflect.NativeConstructorInvoker.newInstan ce([Ljava.lang.ObjectLjava.lang.Object;(Unknown Source)

For GUEST.ADMIN and SERVPROV.ADMIN

INFO | jvm 1 | 2008/06/05 20:33:52 | java.sql.SQLException: ORA-00942: table or view does not exist

When I attempt to Login with WRONG information:

For DBA.ADMIN ,GUEST.ADMIN and SERVPROV.ADMIN

INFO | jvm 1 | 2008/06/05 20:33:52 | java.sql.SQLException: ORA-00942: table or view does not exist

We thought the problem is with the DATA2.
So we changed glog.properties and WL config.xml in OTM2 to connect to DATA1.

When CORRECT Login information is provided :

For DBA.ADMIN

INFO | jvm 1 | 2008/06/11 12:56:07 | Authentication Failed for user DBA.ADMIN
INFO | jvm 1 | 2008/06/11 12:56:07 |
INFO | jvm 1 | 2008/06/11 12:56:07 | at jrockit.reflect.NativeConstructorInvoker.newInstan ce([Ljava.lang.ObjectLjava.lang.Object;(Unknown Source)

For GUEST.ADMIN and SERVPROV.ADMIN

INFO | jvm 1 | 2008/06/11 12:57:14 | java.lang.NullPointerException
INFO | jvm 1 | 2008/06/11 12:57:14 | at oracle.jdbc.driver.OracleDriver.connect(OracleDriv er.java:592)

When I attempt to Login with WRONG information:

For DBA.ADMIN ,GUEST.ADMIN and SERVPROV.ADMIN

INFO | jvm 1 | 2008/06/11 12:57:14 | java.lang.NullPointerException
INFO | jvm 1 | 2008/06/11 12:57:14 | at oracle.jdbc.driver.OracleDriver.connect(OracleDriv er.java:592)

Until now we thought the problem is with current database DATA2.On connecting to the WORKING database DATA1,I am suspecting the problem might be somewhere with the WebLogic Connection Pool.

One issue that really confuses is that I am getting different error msg if I attempt to login with CORRECT info and WRONG info.
Pls provide some input as I am unable to conclude anything. Both DATA1 and DATA2 are running on differenet DB Servers.

I am attaching my glog.properties and WebLogic config.xml as text files in case you wish to look into. The domainName in the attached files isn’t actual domain value.I changed it.

glog.txt
config.txt

Thanks for your time,
Durga

**nick.polites** · June 11, 2008, 11:08

Re: OTM 5.5 CU4 Installation

Attach your weblogic console.log file. I still think that you have a problem in your database. At the same time, what you can do to confirm/rule this out is shut down both your Unix and Windows instances. Change the glog.properties database entries to point to the database server that your Unix instance is using and then try starting up the Windows environment. If you get a successful login, then you know where your problem is.

**dgoli** · June 11, 2008, 13:08

Re: OTM 5.5 CU4 Installation

Hi Nick,

Thanks for your patience in replying.

I restarted my Windows Database instance(Data2) and tried login from the Windows OTM instance(OTM2).
But ended up with the same error(I am not supposed to touch Unix Database.So just tried restart with Windows DB).

My colleague suggests there might be problem with the user access in VPD.

I am attaching the console log files from both Tomcat and WebLogic as text files for your reference.

Tomcat_console.txt
Weblogic_console.txt

I really appreciate any suggestions at this point.

Thanks for your time,
Durga

**nick.polites** · June 11, 2008, 13:19

Re: OTM 5.5 CU4 Installation

If you patched the database to CU4 and didn't recieve any error message then your import was not successful.

In the admin guide it states to run @object_count.sql. Check the results and compare them with what there is supposed to be. You can also attach your dbpatch log from your <<OTM Directory>>/glog/oracle/script8 and I can see if that looks clean.

You are missing at least one table so you won't be able to login until you fix it.

Announcement

OTM 5.5 CU4 Installation

OTM 5.5 CU4 Installation

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment