- #Oracle 11g database version 11.1.0.7 install#
- #Oracle 11g database version 11.1.0.7 update#
- #Oracle 11g database version 11.1.0.7 upgrade#
NOTE: This is a complex and time consuming process so we recommend that you only perform this if you have a lot of time to troubleshoot the issue.ģ.
#Oracle 11g database version 11.1.0.7 update#
If the updatedb will be successful after running it locally, then one of the reason why updatedb is failing earlier was because of an outdated Oracle driver and it would be a good idea to update the Oracle driver to see if it will resolve the issue. Verify and modify that the maximo.properties file has the new database information.
#Oracle 11g database version 11.1.0.7 install#
To test the updatedb locally, install an Oracle database in your Maximo administrative workstation and then create a new database so that you can import your existing Maximo 7.5 database to this newly created one. Please also check if there is a possibility of a firewall dropping the connection between the Oracle client and the database server. NOTE: If you had connection issues detectable by pinging the two servers, the updated command would not reach this point of failure. If the issue still persists after checking that there is no problem with the connection, proceed with number 2. Make sure that the two servers can communicate and can ping with each other. Check the physical connection between the two servers.
I have described the environment having two servers, one for the Maximo Administrative Workstation and one for the Oracle Database Server. Check the connection between the two servers. OR dbchange#ScriptFailure Closed Connection : Closed Connection at .newSQLException(SQLStateMapping.java:70) at .newSQLException(DatabaseError.java:131) at .throwSqlException(DatabaseError.java:197) at .throwSqlException(DatabaseError.java:261) at .throwSqlException(DatabaseError.java:269) at .throwSqlException(DatabaseError.java:490) at .commit(PhysicalConnection.java:3404) at .commit(PhysicalConnection.java:3438)ġ. In the event that the updatedb fails, you will see error messages like these: dbchange#ScriptFailure A statement failed to execute inside a freeform statement sql#17002 Io exception: Software caused connection abort: recv failed : scriptrun#freeformfail at .executeFreeFormStatement(Unknown Source) at .run(Unknown Source) at .runStatement(Unknown Source) at .run(Unknown Source) at (Unknown Source) at (Unknown Source) at (Unknown Source) at (Unknown Source) at (Unknown Source) at (Unknown Source) at (Unknown Source) at (Unknown Source) at (Unknown Source)
#Oracle 11g database version 11.1.0.7 upgrade#
The installation issue that we are going to troubleshoot is encountered during upgrade the database of Maximo (during the run of the updatedb command). This issue happens when you are trying to install Maximo 7.5.0.x fix pack in an environment that has Oracle database.įor a brief background of the environment, this is an environment where you have a separate Maximo Administrative Workstation and a separate Oracle Database Server. The title of this blog speaks for its content and this is can be a very specific issue. I hope that this will be helpful when you experience this kind of issue during an installation of a Maximo 7.5 fix pack.
0 kommentar(er)
