7
Troubleshooting

This chapter lists possible solutions to errors that you may encounter while installing or using Oracle Portal.

7.1 What to do first?

If you are having any problems installing Oracle Portal, you can first ensure that your system has met the system requirements documented. You must have at least 100 MB in both the Default and SYSTEM tablespaces.

7.1.1 Check Installation Log

You should always check the installation session log that describes the actions performed and the components created upon installation. You can check the log file for ORA and PLS errors that may have occurred during installation.

The log file is located in the following location:

<ORACLE_HOME>/assistants/opca/install.log

7.2 Troubleshooting List

The following is a list of errors and page references to their solutions:

• Error: You cannot login because there is no configuration information stored in the enabler configuration table (WWC-41439)

• ORA-04031: unable to allocate 4032 bytes of shared memory ("shared pool","java/lang/ObjectSYS","joxlod: in ehe","ioc_allocate_pal")

• Error: A post check on the Portal installation has determined that the SSOHash class has not been loaded into the database

• Error: Not Found. The requested URL /servlet/page was not found on this server.

• Error: TNS could not resolve service name or Database Log In Failed

• Error: wdblsnr.exe - DLL Initialization Failed (Initialization of the dynamic link library x:\<ORACLE_HOME>\bin\oranro8.dll failed

• Error: missing string (login link text) language(e) domain(wwc) sub_domain(sec) Missing string(pages) language(e) domain(wwc) sub_domain(pob)

• Error: PLS-00306: wrong number or types of arguments

• Unable to create interMedia Text Indexes

Error: You cannot login because there is no configuration information stored in the enabler configuration table (WWC-41439)

This error displays because the Single Sign-On (SSO) Partner Enabler API cannot find the appropriate entry in the enabler configuration table, WWSEC_ENABLER_CONFIG_INFO$. This configuration information is required to successfully log onto Oracle Portal via SSO.

There are several reasons for such an error. Refer to the appropriate section below:

• Reason 1: The enabler table is empty.

• Reason 2: You've installed Oracle Portal over a previous installation of Oracle9i Application Server or the default Oracle HTTP Server powered by Apache ports are being used by some other process.

• Reason 3: The URL for the login link is not using the same host:port as the entry in the enabler table. This is usually due to one of the following:

• Reason 4: Insufficient tablespace, shared pool size, or Java Pool size to install Oracle Portal.

Reason 1: The enabler table is empty.

It is possible that loadjava is failing to load the SSOHash class early in the installation process. If this class is not loaded, then much of the Login Server and Partner Application seed data is unable to load and the table is not populated.

Solution: Make sure the Java Option is installed on the database and correct the Java environment variables such as CLASSPATH, and try to reinstall Oracle Portal.

If the problem is still not resolved, check that the SSOHash class is loaded.

1. Log onto SQL*Plus as the SYS user with the appropriate password.

2. Enter the following commands:

   SQL> select object_name from user_objects 
   2  where object_type = 'JAVA CLASS' 
   3  and object_name like '%SSO%'; 
   

Reason 2: You've installed Oracle Portal over a previous installation of Oracle9i Application Server or the default Oracle HTTP Server powered by Apache ports are being used by some other process.

Both Oracle Portal and Oracle9i Application Server default to port 80 on Windows NT and port 7777 on Solaris upon installation.

In the future, to avoid this situation, make sure that you stop any service running on either of these ports (depending on your operating system) before installing either Oracle9i Application Server or Oracle Portal.

Solution: Change the Oracle HTTP Server powered by Apache port number.

You will need to make changes to the Oracle HTTP Server's configuration file, httpd.conf.

1. With a text editor, open the Oracle HTTP Server's configuration file, httpd.conf, which is located in the following location by default:

   <ORACLE_HOME>/Apache/Apache/conf/httpd.conf
   
   

   1. For the HTTP port, edit the port number to 7777.

   2. Save the httpd.conf file.

   3. Repeat the above steps for the jserv.properties file.

2. With a text editor, open the Apache Jserv configuration file, jserv.conf, which is located in the following location by default:

   <ORACLE_HOME>/Apache/Jserv/conf/jserv.conf
   
   

   1. For the default port that Apache JServ is listening to, edit the port number if you have another JServ installation using the same port (8007).

   2. Remove any alias defined in the Apache configuration which makes Apache translate "host.domain.com" to "host" only. You must define the default domain as well.

   3. Save the jserv.conf.

Reason 3: The URL for the login link is not using the same host:port as the entry in the enabler table. This is usually due to one of the following:

• The URL was mistyped when invoking the ssodatan script. Re-run ssodatan with the correct data.

• The ssodatan script was run correctly with a full URL: host.domain:port. However, the Login link shows only host:port (dropping the domain). This is typically because there is an alias defined in the Oracle HTTP Server powered by Apache configuration (httpd.conf) resulting in the translation of host.domain.com to host.

• The default domain is not set in the Oracle HTTP Server powered by Apache configuration. When this is the case, only the hostname is produced, without the domain.

• The ssodatan script was run with the default port number 80. As a result, the Oracle HTTP Server and your browser drops the :80. Thus, the URL no longer matches the entry in the WWSEC_ENABLER_CONFIG_INFO$ table.

Solution: Install the Login Server by running the ssodatan script, which is located in the following location by default:

<ORACLE_HOME>\webdb30\admin\plsql

where <ORACLE_HOME> is where your Oracle Portal installation is located.

1. Start a command line prompt.

2. Enter the following command to associate a node to the Login Server:

   ssodatan <-w portal_url> <-l login_server_url> <-s portal_schema> <-p 
   portal_password> <-o sso_schema> <-d sso_password> <-c portal_connect_
   string>
   
   

Example

ssodatan -w http://server.oracle.com:7777/pls/portal/ -l 
http://server.oracle.com:3000/pls/portal_sso/ -s portal30 -p portal30 -o 
portal30_sso -c orcl

See: Table 6-1, "ssodatan parameters" for parameter descriptions.

1. Specify to use port number 7777 in the script's URL parameter.

   Important: If you are using the default port 80, do not specify this port number when running the ssodatan script.

Reason 4: Insufficient tablespace, shared pool size, or Java Pool size to install Oracle Portal.

Solution: You will have to correct the appropriate configuration setting before reinstalling Oracle Portal.

See also: Oracle8i documentation set.

ORA-04031: unable to allocate 4032 bytes of shared memory ("shared pool","java/lang/ObjectSYS","joxlod: in ehe","ioc_allocate_pal")

This error displays as a result of a parameter setting in the Oracle8i init.ora file. For some reason, the java_pool_size parameter may be set to 0. By default, the Oracle8i installation sets this parameter to approximately 20 MB.

Solution: You must drop the Oracle Portal objects from the database, set the java_pool_size initialization parameter to 20 MB or above and then reinstall Oracle Portal.

See also: "init.ora settings".

Error: A post check on the Portal installation has determined that the SSOHash class has not been loaded into the database

This error displays for any of the following reasons:

• the Java option was not installed with your Oracle8i database

• the Java environment variables such as CLASSPATH is incorrect

• the ORACLE_HOME is not set and the loadjava command cannot be found

Solution: Install the Java Option with the Database Assistant and rerun the Oracle Portal installation.

Error: Not Found. The requested URL /servlet/page was not found on this server.

This may be due to conflicts in the ports used by different Jserv installations on the same computer.

See Step 2 for Error: You cannot login because there is no configuration information stored in the enabler configuration table (WWC-41439) for a solution.

Error: TNS could not resolve service name or Database Log In Failed

Verify that the TNS name in the connectstring entry of the DAD for this URL is valid.

These errors occur because the connectivity information (connect string/TNS names alias) in your Gateway Database Access Descriptor (DAD) or in your database network configuration is incorrect. First make sure that the Oracle8i database and TNS listener is up and running. If they are and you still get this error, follow the solution below.

Solution: Edit the database network file and the Gateway DAD configuration file accordingly.

1. With a text editor, open the database network file, tnsnames.ora, which is located in the following location by default:

   <ORACLE_HOME>/network/admin
   
   

   where <ORACLE_HOME> is the location where Oracle Portal is installed.

   1. Verify that the following parameters are pointing to your Oracle Portal installation.

      HOST=<hostname.domain>
      PORT=<portnumber>
      
      

   2. Save the tnsnames.ora file.

2. With a text editor, open the Gateway DAD configuration file, gateway.htm, which is located in the following location by default:

   http://<hostname>:<port>/pls/DAD/<admin_path>/gateway.htm 
   
   

   1. Verify that the following parameters are correct for your Oracle Portal installation.

      Oracle User Name
      Oracle Password
      Oracle Connect String
      
      

   2. Make sure that EnableSSO=Yes.

   3. Click OK to save your settings.

See: Chapter 3, "Configuring the PL/SQL Gateway"

Error: wdblsnr.exe - DLL Initialization Failed (Initialization of the dynamic link library x:\<ORACLE_HOME>\bin\oranro8.dll failed

This error may occur during Oracle Portal installation in cases where an existing Oracle 8.1.5 database has been upgraded to Oracle 8.1.6 before installing Oracle Portal. However, the required .dll files are still missing.

Solution: Copy the missing .dll files to the location where Oracle Portal is installed.

1. Locate a machine with a clean installation of Oracle8i (8.1.6 or above).

2. Copy the OCI.DLL and ORANRO8.DLL files from this machine to the machine where your Oracle Portal product (or Oracle9i Application Server Home) is installed in the following location:

   <ORACLE_HOME>\bin
   
   

3. Try to access Oracle Portal again.

See: Section 2.4, "Accessing Oracle Portal in your Browser".

If this error still occurs, use the Oracle Home Selector tool to switch the Oracle Home to the Oracle Home in which Oracle Portal is installed or start the Oracle HTTP Listener powered by Apache. The ORACLE_HOME and PATH environment variables must also be set correctly.

Error: missing string (login link text) language(e) domain(wwc) sub_domain(sec) Missing string(pages) language(e) domain(wwc) sub_domain(pob)

This error may display when you try to access the Oracle Portal home page and National Language Support (NLS) files are missing.

Solutions:

• Check to make sure your browser language preference is set to the language you've installed with Oracle Portal. Oracle Portal is supported on 24 different languages with English as the default language. See "Installing language support in Oracle Portal".

• Make sure that your browser is set to accept Java and Javascript.

• Check the installation log file to see if wwvcbus.ctl and wwcus.ctl were loaded into Oracle Portal's NLS table, wwnls_strings$.

Error: PLS-00306: wrong number or types of arguments

This error occurs when you are installing Oracle Portal on a machine with an existing Oracle WebDB 2.2. The installed Oracle Portal synonym (webdb30.wwv_utl_api_types) causes the WebDB 2.2 components to become invalid and you'll experience problems with your pre-existing components and creating new components in WebDB 2.2.

You'll need to drop the WebDB 2.2 synonyms as follows:

1. Log onto SQL*Plus as the SYS user with the appropriate password.

2. Enter the following commands:

   drop public synonym wwv_utl_api_types;
   create public synonym wwv_utl_api_types for <webdb22schema>.wwv_utl_api_types
   

Unable to create interMedia Text Indexes

If you are unable to create an interMedia Text index, check that your system has met all the requirements. You must have an Oracle8i database with the interMedia Text option installed.

Also, interMedia Text should be installed in the same Oracle Home as the database. It is not installed if you choose to perform a Typical or default Custom installation of the Oracle8i database.

See: Chapter 4, "Using interMedia Text in Oracle Portal".