solaris 关闭防火墙 soa 10.1.3.1.0安装错误
# svcs -a |grep network |egrep "pfil|ipf"
enable 4:36:25
svc:/network/pfil:default
online 23:41:33
svc:/network/ipfilter:default
#svcadm disable svc:/network/ipfilter:default
OWSM Config Assistant Fails with: java.sql.sqlexception: Connection Reset, and with Error Code = 12592 in the Database [ID 740861.1]
需要重新安装
In this Document
Symptoms
Cause
Solution
References
Applies to:
Oracle Web Services Manager - Version: 10.1.3.1 to
10.1.3.4.0 - Release: AS10gR3 to
Oracle SOA Platform - Version:
10.1.3.1.0 to 10.1.3.4.0 [Release: AS10gR3 to ]
Information in this
document applies to any platform.
Symptoms
When attempting to install the SOA
suite there is an error in the log while installing the OWSM
section of
it.
ERROR
BUILD
FAILED
/u01/app/oracle/product/soa_suite/owsm/scripts/install.xml:1971: The
following error occurred while executing this
line:
/u01/app/oracle/product/soa_suite/owsm/scripts/dataload.xml:314: The
following error occurred while executing this
line:
/u01/app/oracle/product/soa_suite/owsm/scripts/dataload.xml:316: The
following error occurred while executing this
line:
/u01/app/oracle/product/soa_suite/owsm/scripts/dataload.xml:278:
java.sql.SQLException: connection
reset
during the loading of this table:
desc
orawsm.policy_manager_objects;
Name Null?
Type
----------------------------------------- --------
----------------------------
OBJECT_ID NOT NULL NUMBER(12)
OBJECT_DOCUMENT
CLOB
On the server side the next trace file is generated:
opitsk: network error
occurred while two-task server trying to send break; error code =
12592
Cause
Based on the error reported in the
database side: error code = 12592
The issue is caused by the next
possible reasons:
- One possible source of the problem:
There is more than one default gateway IP address and no static IP entry in the routing tables for the server attempting the remote access. The NT server is not always sending the return message to the same gateway IP address and therefore the remote user session locked.
Solution
Check if there is more than one default gateway IP address entered with no static entry in the routing table. Remove the extra default gateway IP address (located in the TCP/IP properties) where possible. If the remote client is required to do other connections to the NT server then add the IP address as static (permanent) to the NT routing table.
- Some times this problem is generated by the networking card. Check if the
cards are in perfect conditions.
- Is there any firewall between the SOA installation and the database
host?
If there is one, is it possible to check the configuration or disable it just for the time the installation is done and let me know the results?
This issue is described in Note 373431.1
: TroubleShooting Guide For TNS - 12592 TNS BAD PACKET
Solution
As the problem has been verified as
been introduced by the firewall, it is necessary to disable
the firewall
during the installation process to avoid this problem to happen.
It has
been verified that the firewall introduces an erroneous behavior during the
installation
of OWSM (network connection reset); in particular while execute
the POLICY_MANAGER_OBJECTS.sql script. It doesn't happen if the firewall.is not
crossed.
References
NOTE:373431.1 - TroubleShooting Guide For TNS - 12592 TNS BAD PACKET