This section describes known problems and associated workarounds for the Sun Java System Application Server 7 2004Q2 Update 7 Standard and Enterprise Edition.
If a problem statement does not specify a particular platform, the problem applies to all platforms.
This information is organized into the following sections:
This section describes the known installation and uninstallation issues and associated solutions.
ID |
Summary |
---|---|
6602615 |
After upgrading from localized version of Application Server 7.1 Update 5 to Application Server 7.1 Update 7, the upgraded instance fails to start on Soalris 10 Update 3 and above. There is a conflict between the Message Queue (MQ) versions bundled with Solaris and the version bundled with Application Server. Solution: |
6606419 |
Upgrade from localized version of Application Server 7.1 Update 5 to Application Server 7.1 Update 7 fails. The installer fails to delete the directory, SUNWhadb/4. Solution: Do one of the following:
|
6606417 |
Upgrade from localized version of Application Server Enterprise Edition 7.1 Update 5 to Application Server Enterprise Edition 7.1 Update 7 does not change the SUNWhadb/4 symbolic links. Solution: Changed the symbolic link to 4.4.2-30. |
6606979 |
Upgrade to localized version of Application Server Enterprise Edition 7.1 Update 7 displays English index.html Solution: Perform the following steps:
|
6245916 |
When upgrading from localized Application Server 7.1 Update 2 to Update 3/Update 4/Update 7 in Japanese and Simplified Chinese locales, the localized welcome page and index.html is displayed from Update 2. The localized version of Application Server 7.1 Update 7 contain localized files from Application Server 7.1 Update 2. Solution After upgrading to Update 7, refer to the English welcome page and index page located at: Appserver_Install_Dir/docs/about.html Appserver_Install_Dirlib/install/templates/index.html To register Sun Java System Application Server, use the following URLS: Japanese: https://www.sun.com/software/product_registration?locale=ja_JP Simplified Chinese: https://www.sun.com/software/product_registration?locale=zh_CN To view the latest index.html (in English) for an existing domain, instead of the old localized version, copy the index.html to the docroot folder: copy Appserver_Install_Dir/lib/install/templates/index.html to Appserver_domain_root/domains/domain1/admin-server/docroot Before creating a new domain, replace the localized index.html with the English index.html: Copy Appserver_Install_Dir/lib/install/templates/index.html to Appserver_Install_Dir/lib/install/templates/{ja,zh_CN}/index.html Ensure that you back up your current Japanese or Chinese index.html file. |
6222700 |
When upgrading from localized Application Server 7.1 Update 2 to Update 3/Update 4/Update 7 in Japanese and Simplified Chinese locales, the default page of server1 instance is displayed in English. |
6245424 |
After uninstalling localized versions of Application Server Update 7, the localized packages/RPMs will remain. Solution Remove the localized packages/RPMs first and then run the uninstall program. Perform the following procedure on package-based Solaris installations.
|
6208875 |
Upgrade installation Failed:java.io.FileNotFoundException File-based upgrade of HADB on Solaris SPARC, Solaris x86, and Linux will encounter problems in certain scenarios, as described here: Installation fails with the following exception: java.io.FileNotFoundException: /sun/appserver7/./SUNWhadb/4 (Is a directory) Upgrade scenarios: 7.1RTM/7.1ER1/7.1UR1 file-based upgrade to 7.1UR2. Solution Rename the file-based-installing-directory/SUNWhadb/4 softlink to another name, such as, SUNWhadb/3. Restart the upgrade. |
6217112 |
Incremental installation is not working on Windows platforms. Sample applications can be installed along with Application Server. They cannot be incrementally installed. Solution Select to install sample applications at the beginning of installation. During incremental installations, do not select the sample applications option. |
5006942 |
On Windows, the services created have the start type set by default to “Automatic” after an upgrade. Solution
|
6217097 |
File-based upgrade performed as a non-root user seems to fail if the Application Server binaries for the upgrade were not downloaded as non-root user. Solution The downloaded binaries need to be owned by the non-root user. The downloaded archive must be unzipped by the user who will do the installation or upgrade. Otherwise this is known to lead to permissions issues while the JDK is being upgraded. |
This section describes the known startup and shutdown issues and the associated solutions.
This section describes the known database driver issues and associated solutions.
This section describes the known web container issues and associated solutions.
ID |
Summary |
---|---|
6183117 |
Incorrect http-headers when using servlet filters for pdf/ xls files. There is no default mime-type mapping in default-web.xml. Add the desired mime-types to default-web.xml. Solution Add the following mime-type definition in the default-web.xml of the instance that will server xls: <mime-mapping> <extension>xls</extension> <mime-type>application/vnd.ms-excel</mime-type> </mime-mapping> Similarly, add the specific mime-type definitions for other file types to the default-web.xml file. |
6308777, 6324326 |
Servlet container UTF-8 URI mapping vulnerability. ACL-based protection for JSPs can be bypassed by presenting characters in the URI in UTF-8 format. Solution Ensure to modify ACLs to not accept wildcards in the URI. |
5089201, 5001994 |
getRequestURI() returns unencoded values when it should not. The fix for this issue will break clients of older NSAPI, such as Portal Server 6.3, which call getRequestURI() and expect the URI to be automatically decoded when the data is returned. Therefore, to maintain backward compatibility for older NSAPI clients, a new JVM option has been added to revert to the old NSAPI behavior and allow Portal Server to function correctly. Solution Enable the JVM option, -DJ2EEDecodeURI, on computers running Portal Server to allow cookie-less mode (and all other functionality) on the getRequestURI() call. |
4951476 |
javax.ejb.EJBException: org/dom4j/Element error is thrown with JWSDP 1.2(1.3) installed. Solution Add dom4j-full.jar to server-classpath in server.xml file. It can be downloaded from http://dom4j.organd should precede appserv-jstl.jar entry in server-classpath. |
4997770 |
HTTP 404 error message still indicating "Sun ONE Application Server" Read "Sun ONE Application Server" as Sun Java System Application Server. |
This section describes the known issues in Java Message Service (JMS), Sun Java System Message Queue, and message-driven beans issues and the associated solutions.
ID |
Summary |
---|---|
6184426 |
ConnectException errors on HP-UX11.11during stress tests. Configuration of the HP-UX TCP-IP parameter at the OS level or at the IMQ level is required. Solution At the IMQ level, make the following changes: imq.portmapper.backlog=1000 imq.authentication.client.response.timeout=360 imq.jms.tcp.backlog=3000 imq.jms.max_threads=5000 |
4683029 |
The -javahome flag in all MQ Solaris scripts does not work if the value has a space. The command-line utilities in Sun ONE Message Queue have a -javahome option that allows you to specify an alternate Java runtime. Using this option exposes a limitation where the path of the specified alternate Java runtime must not contain spaces. Examples of paths that have spaces are: /work/java 1.4 This problem occurs at Application Server instance startup. When a Sun ONE Application Server instance is started, by default its corresponding Sun ONE Message Queue broker instance is also started. The broker always starts using the -javahome command-line option to ensure that it uses the same Java runtime used by the Application Server. If the Java runtime that is configured for use by the Application Server (and therefore passed on for use by the broker) is located at a path that contains spaces, broker startup fails, which also causes the Application Server instance startup to fail. Solution Make sure that the Java runtime used by the Application Server is located at a path that does not contain spaces. |
This section describes the known Java Transaction Service (JTS) issues and the associated solutions.
ID |
Summary |
---|---|
6218460 |
Transactions can fail due to a transaction timeout even when the JTS timeout is large enough. Solution Configure the Application Server’s transaction service property, xaresource-txn-timeout, and set its value to match the transaction timeout (in seconds) configured for the transaction service. |
There are some known problems with the recovery implementations of some of the JDBC drivers. For these known problems, Sun Java System Application Server provided some workarounds. By default, these workarounds will not be used unless you explicitly indicate that these workarounds are to be used.
Issue with the Oracle (R) JDBC driver—Oracle XA Resource implementation’s recover method repeatedly returns the same set of in-doubt Xids regardless of the input flag. According to the XA specs, the Transaction Manager should initially call XAResource.recover with TMSTARTSCAN and then call XAResource.recover with TMNOFLAGS repeatedly until no Xids are returned.
Oracle XA Resource’s commit method also has some problems, which are addressed in a workaround provided by the Application Server. To enable this workaround, the following property should be added to the transaction-service subelement in the server.xml file: oracle-xa-recovery-workaround
This property value should be set to true.
Issue with Sybase JConnect 5.2—There are some known problems with JConnect 5.2 driver which are resolved in JConnect 5.5. If the JConnect 5.2 driver is used, to make recovery to work, the following property should be added to the transaction-service subelement in the server.xml file:
sybase-xa-recovery-workaround
This property value should be sent to true.
In the server.xml file, res-type is used to demarcate the connection as non-XA or XA. This demarcation is used to identify the configuration of the data source to drive data. For example, in the Datadirect driver, the same data source can be used as either XA or non-XA.
The default behavior of the data source is non-XA. To make the data source behave as XA with the connpool element for transactions, res-type is needed. For the connpool element to work and participate in transactions, add the following for the attributes res-type in the server.xml file:
res-type="javax.sql.XADataSource"
This section describes the known application deployment issues and associated solutions.
ID |
Summary |
---|---|
6502888 |
In Application Server 7.1, when you deploy an application to server instance that is running as non-root user, the files of <server-instance>/generated is owned by root user. Solution You need to change the permissions manually. |
6078271 |
Deployment of an EAR fails on Windows due to file length issue. Windows running on non-NTFS file systems will face file name and path limitation of that file system. Solution Run Windows on an NTFS file system. |
6223279 |
ejb-ref-name to the jndi-name mapping incorrect if the jndi-name is missing. When deploying ejb applications, the XML Deployment Descriptor (sun-ejb-jar.xml) should have a jndi-name entry for each EJB reference. For example: <ejb-ref> <ejb-ref-name>ejb/package_name.ejb_name</ejb-ref-name> <jndi-name>ejb/package_name.ejb_name</jndi-name> </ejb-ref> If the jndi-name entry is missing, it will deploy without error, but the application will not work correctly as JNDI lookup will fail to find an EJB. Solution Ensure that JNDI names are present in the deployment descriptors. To ensure that your application does not have this problem, select the Run Verifier check box before deploying as this will highlight problems with missing JNDI names. |
4725147 |
Cannot choose a particular virtual server for deployment. In this case, two virtual servers are configured with exactly the same host and listener. If an application is deployed only for second virtual server, it cannot be reached because combination host:port leads to the first virtual server. Solution The virtual server hostname should not be the same as the original hostname, especially when the same HTTP listener is used. |
4994366 |
Deploy error with ejb-local-ref and ejb-link. Solution ejb-local-ref requires ejb-link. Therefore, when dealing with ejb-local-ref, you must specify an ejb-link value. |
This section describes the known verifier issues and associated solutions.
ID |
Summary |
---|---|
4742545 |
Standalone verifier shows EJB Class Not Found errors. The verifier indicates some failed tests with the following test description message: EJB Class Not Found. The test failures occur when an EJB JAR file uses an enterprise bean with a reference to another enterprise bean that is packaged in a separate EJB JAR file within the same EAR application. The failure messages are also observed if you try to validate the connector (RAR) dependent EAR files. This is because the RAR bundle need not be packaged within the EAR file that houses the enterprise bean with dependency on the RAR bundled files. The failures (exception to this are the connector-related failures) are only observed with the standalone verifier. The verifier invoked through the deployment command or the Administration interface does not show the failures. Solution Make sure that the packaging of the application EAR is correct and if you are using any utility JAR file, it is packaged within the EAR file. To resolve the referencing errors, you can shift to the verifier invoked through the deployment backend using asadmin or the Administration interface. For the connector-related failures, place the JAR file containing the required classes into the class path for the verifier. You can open the install_root/bin/verifier[.bat] file and add a LOCAL_CLASSPATH variable to the end of the JVM_CLASSPATH variable. Locally add the classes to the LOCAL_CLASSPATH variable, then run the verifier. |
This section describes the known load balancer issues and associated solutions.
ID |
Summary |
---|---|
6422893 |
The Application Server 7.1 UR5 load balancer plug-in does not recognize the HTTPS listeners even when the https-routing property is set to true in loadbalancer.xml. Solution If you are installing Application Server 7.1 afresh:
If you already have an installation of Application Server 7.1:
|
6338687 |
Load Balancer Plug-in cannot handle URL/URI greater than 8K. Ensure not to create a URL/URI greater than 8k if it is going to be forwarded by the load balancer plug-in to the Application Server. |
6262746 |
Load balancer plug-in on Apache web server, installed on Solaris 10 (SPARC and x86), is not a supported configuration. Solution
|
6155134 |
Manual setting of path is required for webservers to start. After installing load balancer plug-in on Windows for IIS or Apache, append the path of the Application Server to the Path environment variable.
|
4761151, 4825429, 4981545 |
Intermediate form and basic authentication failures while sending intermittent SSL and non-SSL requests through load balancer plug-in. Displays a 502 Bad Gateway error message. The persistency of proxy-to-container connections is not maintained with the default settings. Loadbalancer looses persistent connections to the application server due to deployment/undeployment on the application server and/or due to keep alive timeout or due to stale connections in the load balancer’s connection pool. When this happens, some of load balancer’s requests will fail and the error page is displayed. This typically occurs in a development environment where frequent deployment/undeployment and other configuration changes are tried and tested. Solution Set the keep alive timeout on the appserver to 0. Using web-based Administration interface:
|
4962735 |
On Linux, Apache Web Server 1.3.27 does not start after installing load balancer plug-in and sec_db files. Solution Include the following lines in /src/MakeFile after “End of automatically generated section,” and just before “OBJS= \”. Also, make sure the Application Server libraries are already installed in a particular location: LIBS+= -licuuc -licuil8n -lnspr4 -lpthread -lxerces-c -lsupport -lnsprwrap -lns-httpd40 LDFLAGS+= -L/space/SJSAS/installations/lib. Where: /space/SJSAS/installations is the location of the application server installation. For more information, see Appendix “Compiling Apache Web Server” in Sun Java System Application Server Administration Guide. |
5018537 |
Identity Server/Application Server Integration Services unavailable error shown during failover. Loadbalancer.xml has “/” as the context-root for a web-module. After a failover, since there is no context root, a “Default” string is assigned as the path of the update JROUTE cookie. This results in two JROUTE cookies on the browser side.
Solution Have specific context root for all web modules. For example: <web-module context-root=”appl” enabled=”true” disable-timeout-in-minutes=”60” error-url=”appl-lberror.html” /> <web-module context-root=”app2” enabled=”true” disable-timeout-in-minutes=”60” error-url=”app2-lberror.html” /> After the failover, the JROUTE gets the path as “/appl” which is valid and works correctly. |
5007720 |
Log message not proper for invalid value for error-url in web-module. When the error-url attribute in web-module tag of loadbalancer.xml is set, as follows, to an invalid value, such as: <web-module context-root="app1" enabled="true" disable-timeout-in-minutes="60" error-url="abc"/> The log message displayed is as follows: warning (11113): reports: lb.configurator: XML_VALIDATOR_WARNING: Invalid format for the error-url sun-http-lberror. However, the log should be: warning (20015): reports: lb.configurator: XML_VALIDATOR_WARNING: Invalid format for the error-url abc |
This section describes the known high availability issues and associated solutions.
ID |
Summary |
---|---|
6301842 |
Sometimes on Windows, the management agent cannot deregister the service when running, ma -r, and fails with the error message, Could not identify program. Solution Start a Windows command prompt window and run sc stop HADBMgmtAgent and then run sc delete HADBMgmtAgent. If the command ma -i -n servicename was used to install and start the service, then use servicename when running the command sc. |
6293912 |
The Management Agent should not use special-use interfaces. Solution When issuing hadbm create on hosts with multiple interfaces, always specify the IP-addresses explicitly, using DDN notation. |
6291562 |
Reassembly failures on Windows. On the Windows platform, with certain configurations and load, there may be a large number of reassembly failures in the operating system. The problem has been seen with configurations of more than 20 nodes when running several table scans (select *) in parallel. The symptoms could be that transactions abort frequently, or repair and recovery may take a long time to complete, and there may be frequent timeouts in various parts of the system. Solution To fix the problem, the Windows registry variable HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters should be set to a value higher than the default value of 100. We recommend increasing it to 0x1000 (4096). For more information, see article 811003 from the Microsoft support pages: http://support.microsoft.com/default.aspx?scid=kb;en-us;811003 |
6275319 |
Non-root users cannot manage HADB. Installing with Java Enterprise System (as root) does not permit non-root users to manage HADB. Solution Always login as root to manage HADB. |
6275103 |
hadbm management agent should give a better error message when a session object has timed out and deleted at MA. Sometimes, a resource contention problem on the server may cause a management client to become disconnected, When reconnecting, a misleading error message, hadbm:Error 22184: A password is required to connect to the management agent may be returned. Solution Check if there is a resource problem on the server, take proper action (e.g., add more resources), and retry the operation. |
6273681 |
Management agents in global and local zones may interfere. On Solaris 10, stopping a management agent by using the ma-initd script in a global zone stops the management agent in the local zone as well. Solution Do not install the management agent both in the global and local zone. |
6271063 |
Install/removal and symlink preservation. Regarding install/removal of HADB c package (Solaris: SUNWhadbc, Linux: sun-hadb-c) version <m.n.u-p>, the symlink /opt/SUNWhadb/<m> is never touched once it exists. Thus, it is possible that an orphaned symlink will exist. Solution Delete the symlink before install or after uninstall unless in use. |
6265419 |
Downgrading from HADB Version 4.4.2.5 to HADB Version 4.4.1.7 causes management agent to fail with different error codes. When downgrading to a previous HADB version, the management agent may fail with different error codes. Solution It is possible to downgrade the HADB database, however the management agent cannot be downgraded if there changes have been made in the repository objects. After a downgrade, you must use the management agent from the latest HADB version. |
6262824 |
hadbm does not support passwords containing uppercase letters. Capital letters in passwords are converted to lowercase when the password is stored in hadb. Solution Do not use passwords containing uppercase letters. |
6173886, 6253132 |
hadbm createdomain may fail. If running the management agent on a host with multiple network interfaces, the createdomain command may fail if not all network interfaces are on the same subnet: hadbm:Error 22020: The management agents could not establish a domain, please check that the hosts can communicate with UDP multicast. The management agents will (if not configured otherwise) use the first interface for UDP multicasts (first as defined by the result from java.net.NetworkInterface.getNetworkInterfaces()). Solution The best solution is to tell the management agent which subnet to use (using ma.server.mainternal.interfaces in the configuration file. For example, ma.server.mainternal.interfaces=10.11.100.0). Alternatively you can configure the router between the subnets to route multicast packets (the management agent uses multicast address 228.8.8.8). Before retrying with a new configuration of the management agents, you should clean up the management agent’s repository. Stop all agents in the domain, and delete all files and directories in the repository directory (identified by repository.dr.path in the management agent configuration file). This must be done on all hosts before restarting the agents with a new configuration file. |
6249685 |
clu_trans_srv process cannot be interrupted on Linux. There is a bug in the 64 bit version of Red Hat Enterprise Linux 3.0 that makes the clu_trans_srv process end up in an uninterruptible mode when performing asynchronous I/O. This means that kill -9 does not work and the operating system must be rebooted. Solution Use a 32 bit version of Red Hat Enterprise Linux 3.0. |
6230792, 6230415 |
Starting, stopping or reconfiguring HADB may fail or hang. On AMD OpteronTM systems running Solaris 10, starting, stopping or reconfiguring HADB using the hadbm command may fail or hang with one of the following errors: hadbm:Error 22009: The command issued had no progress in the last 300 seconds. HADB-E-21070: The operation did not complete within the time limit, but has not been cancelled and may complete at a later time. This may happen if there are inconsistencies while reading/writing to a file (nomandevice) which the clu_noman_srv process uses. This problem can be detected by looking for the following messages in the HADB history files: n:3 NSUP INF 2005-02-11 18:00:33.844 p:731 Child process noman3 733 does not respond. n:3 NSUP INF 2005-02-11 18:00:33.844 p:731 Have not heard from it in 104.537454 sec n:3 NSUP INF 2005-02-11 18:00:33.844 p:731 Child process noman3 733 did not start. Solution To solve the problem, run the following command for the affected node: hadbm restartnode --level=clear nodeno dbname Note that all devices for the node will be reinitialized. You may have to stop the node before reinitializing it. |
None |
HADB database creation fails. Creating a new database may fail with the following error, stating that too few shared memory segments are available: HADB-E-21054: System resource is unavailable : HADB-S-05512: Attaching shared memory segment with key "xxxxx" failed, OS status=24 OS error message: Too many open files. Solution Verify that shared memory is configured and the configuration is working. In particular, on Solaris 8, inspect the file /etc/system, and check that the value of the variable shmsys:shminfo_shmseg is at least six times the number of nodes per host. |
6232140 |
The management agent terminates with the exception, "IPV6_MULTICAST_IF failed." The management agent may terminate with the exception, IPV6_MULTICAST_IF failed, when starting on a host running Solaris 8 with several NIC cards, and if there is a mixture of cards with IPv6 and IPv4 enabled. The root cause is described in bug 4418866/4418865. Solution
|
6171832, 6172138 |
Stale sessions are not cleaned up leading to degraded HADB performance, or the data device is getting full. Solution To remove stale sessions efficiently, modify the sun-ejb-jar.xml file to set the value of cache-idle-timeout-in-seconds to less than the removal-timeout-in-seconds value. If the cache-idle-timeout-in-seconds is equal to or greater than the removal-timeout-in-seconds, old sessions will not be cleaned-up in HADB, which is the expected behavior. If you continue to face issues with stale sessions even after setting these properties as recommended, contact product support for help. |
6171994 |
Improper permissions in security.policy file causing startup hang. Description hadb-jdbc has improper access permissions in the security.policy file. Solution If there is an intermittent hang during startup, add the following suggested permissions in the security.policy file: By default, the following is present: permission java.net.SocketPermission "*", "connect"; Suggested permissions: permission java.net.SocketPermission "*", "connect accept,listen,resolve"; |
5042351 |
New tables created after new nodes are added will not spread on the added nodes. Description If a user creates a database instance, add nodes to it, then any new tables created afterwards will not be fragmented on the nodes added after database creation. Only the tables created before addnodes will be able to use the added nodes when hadbm addnodes refragment it. This is because create table uses the sysnode node group which is created at the boot time of the database (when hadbm create is executed). Solution Run hadbm refragment after new tables have been added, or create the new tables on nodegroup, all_nodes. |
6158393 |
HADB problem with RedHat AS 3.0 in co-located mode under load. Description HADB runs on RedHat Linux AS 3.0 co-located with Application Server. Transactions may get aborted and affect the performance. This is caused by the excessive swapping performed by the operating system. Solution This issue appears to have been resolved when HADB was tested against RedHat Linux AS 3.0 Update 4. |
6214601 |
Addnodes fails with table not found error since hadbm searches user tables in sysroot schema. Description The hadbm refragment command fails with: hadbm:Error 22042: Database could not be refragmented. Please retry with hadbm refragment command to refragment the database.. Caused by: HADB-E-11701: *Table singlesignon not found* Solution Refragment the Application Server tables manually with the help of clusql: > clusql server:port list> system+dbpassword specified at database create> SQL: set autocommit on; SQL: set schema haschema; SQL: alter table sessionattribute nodegroup all_nodes; SQL: alter table singlesignon nodegroup all_nodes; SQL: alter table statefulsessionbean nodegroup all_nodes; SQL: alter table sessionheader nodegroup all_nodes; SQL: alter table blobsessions nodegroup all_nodes; SQL: quit; |
6159633 |
configure-ha-cluster may hang. Description When the asadmin configure-ha-cluster command is used to create or configure a highly available cluster on more than one host, the command hangs. There are no exceptions thrown from the HADB Management Agent or the Application Server. Solution HADB does not support heterogeneous paths across nodes in a database cluster. Make sure that the HADB server installation directory and configuration directory are the same across all participating hosts. Additionally, clear the repository directories before running the command again. |
6197822 |
hadbm set brings the database instance to a state from which it is difficult to recover. Description In this scenario, the hadbm set command fails when attempting to change some database configuration variable; for example, setting DataBufferPoolSize to a larger size fails due to insufficient shared memory on node-0. The hadbm set command then leaves the database with node-0 in stopped state and node-1 in running state. Resetting the pool size back to the original value with the help of hadbm set fails with the message: 22073: The operation requires restart of node 1. Its mirror node is currently not available. Use hadbm status --nodes to see the status of the nodes. In this case, hadbm startnode 0 also fails. Solution Stop the database, then restore the old values using hadbm set and restart the database. |
6200133 |
Failure in configure-ha-cluster; creating an HADB instance fails. Description Attempts to create a HADB cluster fails with the message: HADB-E-00208: The transaction was aborted. The booting transaction populating the SQL dictionary tables gets aborted. Solution Run the configure-ha-cluster command again. If you run the hadbm create command and it fails with the previous message, rerun it. |
5091349 |
Heterogeneous install paths are not supported. It’s not possible to register the same software package with the same name at different locations on different hosts. Solution HADB does not support heterogeneous paths across nodes in a database cluster. Ensure that the HADB server installation directory and configuration directory are same across all participating hosts. |
5091280 |
hadbm set does not check resource availability (disk and memory space) Scenario Increasing device or buffer sizes using hadbm set. Description The management system will check resource availability when creating databases or adding nodes, but it will not check if there are sufficient resources available when device or main-memory buffer sizes are changed. Solution Check that there is enough free disk/memory space on all hosts before increasing any of the devicesize or buffersize configuration attributes. |
4855623 |
When one of the nodes’ host is down, hadbm stop command does not exit. The hadbm stop command may not be able to shutdown a database completely if HADB nodes do not receive shutdown messages due to network problems. The typical symptom is that hadbm takes more than 60 seconds to complete. In this situation, hadbm stop/delete will not work. You must specify the nodes that needs to be shutdown. Solution
|
4861337 |
If an active data node fails while executing hadm stopdb, hadm startdb will fail. hadbm status should return non-operational if the database is unable to start. Solution To correct the problem:
|
4958827 |
Child process transaction does not respond. When a host machine accommodates more than one HADB node and all nodes use the same disk for placing their devices, it is observed that the disk I/O becomes the bottleneck. HADB process have been waiting for asynchronous I/O and therefore did not answer the node supervisor’s heartbeat check. This causes the processes to be restarted by the node supervisor. Although this problem can occur on any operating system, it is observed on Red Hat Linux AS 2.1 and 3. Solution Use separate disks to place the devices belonging to different HADB nodes residing on the same machine. |
None |
HADB Configuration with Double Networks HADB, configured with double networks on two subnets, work properly on Solaris SPARC. However, due to problems in the operating system or network drivers on some hardware platforms, it is observed that Solaris x86 and Linux platforms do not handle double networks properly. This causes the following problems to HADB:
|
This section contains the following sections:
This section describes the known command-line interface issues and associated solutions.
This section describes the known administration infrastructure issues and associated solutions.
When using Administration interface, make sure that the browser is configured to check for newer versions of pages from the server, instead of picking these from cache. Generally, default browser settings would not cause problems.
On Internet Explorer, make sure that Tools->Settings...->Check for newer versions of stored pages: is not set to ’Never’.
On Netscape, make sure that Edit->Preferences...->Advanced->Cache->Compare the page in the cache to the page on the network: is not set to ’Never’.
This section describes the known administration graphical user interface issues, and the associated solutions.
This section describes known sample application issues and associated solutions.
This section describes known ORB/IIOP-Listener issues and associated solutions.
This section describes the known documentation issues and associated solutions.