Problem:
1, at the same time install desktop, engine,engine part of the control can not be used, always prompted to authorize.
2, will desktop uninstall, engine most of the controls can be used, a small number of can not be used.
Key issues:
There is a problem with the engine authorization file. Now there are too many versions of the Engine9.0 on the web, but some can and some are not. In fact, I was trapped by this problem, the delay can not be resolved, the available Engine9.0 authorization documents are published below (absolutely available):
3dengine,9,ecp379783729,none,d7mgje2110l5j9hsx169
designer,9,ecp240010879,none,gb20c3rm03hxntne9005
gdbedit,9,ecp180013971,none,pmyp34s0pbam2t8ag239
spatialengine,9,ecp339810398,none,8sja84s0pdj94p7ej048
standardengine,9,ecp100001222,none,6pc42xljh4c5lmz59217
streetmapengine,9,ecp299948323,none,1jhdjk988l2mc2en0146
Workaround:
1, install desktop, configure license Manager, the process I will not say it;
2, installation engine, with the above authorization file registration.
3. Some of the controls are still not available at this time.
4, please delete and save the feature Designe item in License.dat, restart license Manager;
5, problem solving.
Resolve Oracle 9i and Tomcat Port conflicts (reprint)
Programme I:
Installed the system, found in the debugger, Tomcat 8080 port has been used, so run Netstat-ano view port usage, found that 8080 port by Oracle listener to occupy, so combined with the Internet to find a way to Oracle The Xdb HTTP service port is changed to 8081 to solve the problem.
To sum up the workaround:
First, change the default port for Tomcat
Related files: "TOMCAT ROOT" \conf\server.xml
Second, use SYS to login Oracle, use DBMS_XDB to modify port settings
Sql> Call Dbms_xdb.cfg_update (Updatexml (
2 Dbms_xdb.cfg_get ()
3, '/xdbconfig/sysconfig/protocolconfig/httpconfig/http-port/text () '
4, 8081))
5/
Prompt after run: Call completed.
Then
Sql> COMMIT;
Hint: Commit complete.
Sql> EXEC Dbms_xdb.cfg_refresh; Hint: Pl/sql procedure successfully completed. Third, use Enterprise Manager Console, select database--xml database-configuration, change the default value of Http-port is 8081.
Programme II:
After the Oracle database is installed, when we access port 8080, a xdb window pops up asking for a username and password. This will conflict with some of our local applications that use the port, such as Tomcat, JBoss, and so on, although these ports can be modified, but it is always bad for Oracle to occupy this port. The Oracle database can connect over 8080 ports using the TCP protocol, so it occupies 8080 ports.
To cancel occupancy, you can open the Spfile[sid name in the database directory under the Oracle installation directory. Ora file for modification. This file is an Oracle startup configuration file.
Remove the *.dispatchers= ' (protocol=tcp) (service=or9ixdb) ' line.
Then restart the computer, or restart the Oracleservice[sid name in the service. You may not be able to connect using Enterprise Manager console and other clients after rebooting, then use Oracle's Configuration and migration tools/net Configuration The Assistant tool deletes the listener, then creates a new listener and restarts the listener.
Use the configuration and Migration Tools/net Manager tool to name the service, delete it, and then create a new one. Oracle should be able to use it now, and 8080 will not occupy it. Add: In fact, this is related to the starting order of services, you can set the Oracle listener service manually, Tomcat set to Automatic, restart the computer, test http://localhost:8080, then you can see the big cat, haha ... Then the Oracle listener is started, and there is no conflict.
