How to Change the OID Ports
If at some point it is deemed necessary to change the ports OID is using from those assigned when OID was installed, it is best to create a new Configuration Set with the new ports, and then start the OID processes using that Configset. Do the following: 1. Login to the Oracle Directory Manager 2. Navigate to Server Management > Directory Server 3. Right click on Default Configuration Set and select Create Like. The new configset number is automatically incremented 4. On the General tab, edit the Non SSL Port as desired 5. On the SSL Settings tab, edit the SSL Port as desired 6. Click OK to save the new configset. Ensure it is now listed under the previous one 7. Exit from ODM 8. Shutdown OID 9. Restart OID using the new configset 10. Launch ODM 11. Click on the icon to the right of the Server field on the login screen 12. Select the existing entry for the OID server and click on Edit. 13. Update the new port, and then click OK 14. Login to ODM to ensure OID is up and listening on the new port. Check that any odisrv instances are modified to include the new server port, e.g. flags="-port " Other Changes: For an OracleAS infrastructure OID this change will also require changes to a number of OracleAS configuration files, both in the infrastructure and for any midtiers. Edit the ias.properties file: Unix: $ORACLE_HOME/config/ias.properties Windows: %ORACLE_HOME%\config\ias.properties Under section: [InstallData] change the OIDport to the new port. e.g. [InstallData] ... OIDhost=ukp16015.uk.oracle.com OIDport=4032
2. Check the documentation for each midtier to determine how the update the appropriate configuration files. Note that the following components will definitely be affected: JAZN, Forms, Reports, Portal, Discoverer, OLAP, and Oracle Collaboration Suite. Changing the SSO Settings Run the following script to update the Single Sign-On (SSO) configuration: Unix: $ORACLE_HOME/sso/admin/plsql/sso/ssooconf.sql Windows: %ORACLE_HOME%\sso\admin\plsql\sso\ssooconf.sql If only the enter key is pressed in response to all questions then the configuration remains unchanged and the current values are displayed. Supply the new OID port numbers when prompted. The output looks like the following: CONFIGURATION FOR SSO SERVER: LDAP HOST: ukp16015.uk.oracle.com LDAP PORT: 4032 SSO SERVER DN: orclApplicationCommonName=ORASSO_SSOSERVER,cn=SSO,cn=Products, cn=OracleContext SSO SERVER PASSWORD: 5C8150FB1EF32B5F83C6C6B18EAF1934 LDAP USE SSL: N ---------------------------------------Implications for Client Connections If the original Configset will cease to be used, Net clients accessing OID (e.g., sqlplus users) will need their ldap.ora files updated to reflect the new ports. The ldap.ora file should have the following line updated: DIRECTORY_SERVERS=(::) For example: DIRECTORY_SERVERS=(infraserver.us.oracle.com:3891:6361) Implications for Oracle Application Server Changes to the OID ports can adversely impact the behavior of the Application Server, and it may be safer/easier to reinstall. An example error is the following, upon attempting to start the HTTP Server: dcmctl start -ct ohs –v ADMN-202026 A problem has occurred accessing the Oracle9iAS infrastructure database. Base Exception: oracle.ias.repository.schema.SchemaException: Unable to connect
to Directory Server:javax.naming.CommunicationException: infraserv.oracle.com:4031 [Root exception is java.net.ConnectException: Connection refused] These steps can safely be used to create a new Configset with the new ports that can be run simultaneously with the default Configset.