| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1) for AIX-Based Systems Part Number B12204-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1) for AIX-Based Systems Part Number B12204-02 |
|
|
View PDF |
This appendix describes common installation problems and solutions.
This appendix contains these topics:
If a user logs into Oracle Collaboration Suite and sees a generic Oracle9iAS Portal page instead of the Oracle Collaboration Suite Home page, do the following:
Ensure that the user is a member of the Oracle Collaboration Suite Users group, as follows:
Log into Oracle Delegated Administration Services as orcladmin at the following URL:
http://host_name:port_number/oiddas/
|
Note: In a typical installation, Oracle Delegated Administration Services is located where the infrastructure is installed. |
Click the Directory tab.
Search for the user by user ID (orclguest, for example).
Select the user from the search results, and click Edit.
Scroll down to the Public Groups Assignment section, and ensure that the user is a member of the Oracle Collaboration Suite Users group.
If the user is not a member, select the Oracle Collaboration Suite Users box, and click Apply.
Log out of Oracle Delegated Administration Services.
Ensure that the Oracle Collaboration Suite Users group is the user's default group, as follows:
Log into Oracle9iAS Portal as the user in question. For example, go to http://host_name:port_number/, click End User Login, and log in as orclguest.
If the Oracle Collaboration Suite Home page displays, the user is now correctly provisioned and the rest of this procedure is unnecessary.
If the Oracle9iAS Portal Welcome page displays, click Account Info.
On the Account Info page, ensure that the user's default group is set to OCS_PORTAL_USERS.
If it is not, manually enter OCS_PORTAL_USERS for the user's default group, and click Apply.
Ensure the user's Default Home Page is blank.
Click the Home global button. You should see the Oracle Collaboration Suite Home page. If not, proceed to step 3.
If the Oracle Collaboration Suite Home page still does not display, do the following:
Log into Oracle9iAS Portal as the user in question. For example, go to http://host_name:port_number/, click End User Login, and log in as orclguest.
When the Oracle9iAS Portal Welcome page displays, click Account Info.
On the Account Info page, ensure that the user's default group is set to OCS_PORTAL_USERS.
If it is not, manually enter OCS_PORTAL_USERS for the user's default group, and click Apply.
Click the Browse Pages icon next to the Default Home Page field.
Locate the OCS_V2_PAGE_GROUP page group, and click to expand it.
Locate the Oracle Collaboration Suite Home page, and click Return Object.
Click Apply.
Click the Home global button and the correct home page should display.
Most configuration errors involve failure to carefully follow preinstallation instructions. The following section describes some common installation problems, their possible causes, and how to correct the problem. Installation and configuration actions are captured in the following log files:
$ORACLE_HOME/oraInventory/logs/installActions.log file records any errors encountered during installation.
$ORACLE_HOME/ifs/files/log/FilesConfig.log file records errors encountered during Oracle Files configuration.
$ORACLE_HOME/ifs/files/log/DBHost_port_ServiceName_SchemaName/midtierhostName_Node.log is the Files Node log file. Review this file to diagnose protocol servers and agents that are currently running. It is also useful for diagnosing issues with starting and stopping the protocol servers and agents.
For example:
/data/mtier/ifs/files/log/ifsqa1_us_oracle_com_1521_ifsqa1service_myschema/test2-pc_Node.log
ORACLE_HOME/j2ee/OC4J_iFS_files/application-deployments/files/OC4J_iFS_files_default_island_1/application.log is the Files HTTP Node log file. Review this log to diagnose the Oracle Files application and OC4J_iFS_files. This log is also useful for diagnosing issues when using Oracle Files with the Web browser or DAV clients (Web Folders, and Oracle FileSync).
For example:
/data/mtier/j2ee/OC4J_iFS_files/application-deployments/files/OC4J_iFS_files_default_island_1/application.log
$ORACLE_HOME/wf/install/workflow.log file records errors encountered during Oracle Workflow configuration.
$ORACLE_HOME/ifs/files/log/ifswfsetup.log file records errors encountered while integrating Oracle Workflow with the Oracle Files schema.
$ORACLE_HOME/ifs/files/log/ifswenablelang.log file records errors encountered while enabling additional languages in the Oracle Workflow schema.
This section describes the following problems:
Oracle Files Servers Fail Due to Insufficient Database Resources
"Out of database cursors" Message Written to $ORACLE_HOME/ifs/files/log/domain_name/node_name.log
Oracle Files Configuration Assistant "session_max_open_files must be set to 50" Error Message
The database is not running or is not available, or the listener is not running. Start the database and listener prior to configuration.
The database is not running or Oracle Text is not correctly configured. Start the database prior to installation and check the tnsnames.ora and listener.ora files.
The values in initsid.ora are too low. Check the $ORACLE_HOME/ifs/files/log directory for the log file of the failed server. Edit the initsid.ora file (or change the SPFILE), but provide larger values.
The Oracle Files configuration assistant performs a series of operations to determine if Oracle Text is operating correctly. These steps involve the following:
Creating and logging in as an IFSCTXTEST0 user
Creating an Oracle Text preference
Creating a table with a blob column
Creating an Oracle Text index based on this blob column
Loading a Word document into the table
Synching the Oracle Text index
If any of these steps fail, the Oracle Files configuration assistant notifies you that Oracle Text is not operating properly. The cause of the problem can be related to a number of issues. To find out in which step the test fails, use the following procedure.
|
Note: Oracle Files configuration against Windows 64-bit Oracle9i Database Server 9.2 database fails because the database is missing thectxhx executable that is required to enable Oracle Text on the schema.
There are two possible solutions to this problem:
|
Perform the following to do a manual step-by-step check of Oracle Text:
Log in as a DBA user and create a test user called ifsctxtest0, as follows:
SQL> CREATE USER IFSCTXTEST0 IDENTIFIED BY IFSCTXTEST0 DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP; SQL> GRANT CONNECT,RESOURCE,CTXAPP TO IFSCTXTEST0;
Create the directory to load the ifsctxtest.doc file from:
SQL> create or replace directory DIR_TESTCASE as '$ORACLE_ HOME/9ifs/admin/binaries';
Allow the IFSCTXTEST0 user to read from this directory:
SQL> grant read on directory DIR_TESTCASE to IFSCTXTEST0;
Connect as IFSCTXTEST0 and create a lexer preference:
SQL> exec ctx_ddl.create_preference('mylexer', 'basic_lexer');
Disable theme indexing for this preference:
SQL> exec ctx_ddl.set_attribute('mylexer', 'index_themes', 'NO');
Create a temporary table to store the Word document:
SQL> create table ifs_basic_lob_table( id NUMBER PRIMARY KEY, name VARCHAR2(64),content BLOB );
Create an Oracle Text index on the BLOB column:
SQL> create index content_i on ifs_basic_lob_table(content) indextype is
ctxsys.context parameters ('lexer mylexer');
Insert a row into the temporary table containing the lob locator and load the document using the following PL/SQL block:
SQL> DECLARE
Dest_loc BLOB;
Src_loc BFILE := BFILENAME('DIR_TESTCASE', 'ifsctxtest.doc');
BEGIN
INSERT INTO ifs_basic_lob_table (id,name,content)
VALUES (1,'ifsctxtest.doc',EMPTY_BLOB())
RETURN content INTO dest_loc;
DBMS_LOB.FILEOPEN(Src_loc, DBMS_LOB.LOB_READONLY);
DBMS_LOB.LOADFROMFILE(Dest_loc, Src_loc, DBMS_LOB.GETLENGTH(Src_
loc));
DBMS_LOB.FILECLOSE(Src_loc);
COMMIT;
END;
/
Synchronize the index:
SQL> alter index content_i rebuild parameters('sync');
Perform a content-based query on the table containing the Word document:
SQL> SELECT id, name FROM ifs_basic_lob_table WHERE CONTAINS (content,'Protocol') > 0;
If Oracle Text is operating properly, this should return the following row:
ID NAME
------ ----------------------------------------------------------------
1 ifsctxtest.doc
Any error messages that are returned should give you an indication of what could be causing the problem. If synchronizing the index or searching on the content fails, ensure you check the CTX_USER_INDEX_ERRORS for supplemental information, as ifsctxtest0:
SQL> select * from ctx_user_index_errors;
This information can be used to search OracleMetaLink for possible solutions or supply support analysts with better diagnostic information.
Remember to review the Oracle Text documentation and the troubleshooting sections in the Oracle Files Administrator's Guide for information on configuring Oracle Text.
|
Tips:
|
|
Note: Remember to drop theIFSCTXTEST0 user after these tests have been performed. |
The OPEN_CURSORS value in the initsid.ora is too low. Modify the initsid.ora file (or change the SPFILE) using a larger value for OPEN_CURSORS.
Tuning is required.
|
See Also: The Oracle Files troubleshooting and performance chapter in Oracle Files Administrator's Guide |
If you can log in to the Oracle Files Web Interface but cannot connect to some of the Oracle Files protocol servers, you must set the Oracle Files-specific password. Protocols with which to associate an Oracle Files-specific password were selected during Oracle Files configuration. By default, FTP and AFP require users to log in with an Oracle Files-specific password rather than a Single Sign-On password.
Connect to http://host_name:port/files/app/ProtocolAccess and set the Oracle Files-specific password for users.
|
See Also: Oracle Files Administrator's Guide for more information about configuring protocol servers |
There are two possible causes for this:
The OC4J_iFS_files instance is not running. You must restart the OC4J_ifs_files process after starting the Oracle Files domain (use the command ifstl start to start the Oracle Files domain).
Check the HTTP log for errors and start the OC4J_iFS_files instance. Then connect to http://hostname:port/files/app.
To start the OC4J_ifs_files process, run the following command in the $ORACLE_HOME/opmn/bin directory:
opmnctl startproc gid=OC4J_iFS_files
If you had previously started the OC4J_iFS_files process, use the following command to restart the process:
opmnctl restartproc gid=OC4J_iFS_files
The OC4J_iFS_files instance is running, but the interface is still loading. Wait approximately one minute after starting OC4J_iFS_files before connecting.
This occurs when the Oracle Files Configuration Assistant attempts to make a connection to a RAC database as SYS 'AS SYSDBA' using the thin JDBC driver, which fails.
To resolve this issue, you must create a new SYS user password:
On the database computer, run the following at the command line:
orapwd file=$ORACLE_HOME/dba/orapw password=password entries=5
Where password is the new value for the SYS user password.
Run the following two commands in SQL*Plus to change the password of the SYS user:
connect / as sysdba ALTER USER sys IDENTIFIED BY password
Where password is the password that you specified in step 1.
Add the following line to the init.ora file:
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
The session_max_open_files value in the initsid.ora file is not set correctly. Modify the initsid.ora file and set the value of the session_max_open_files parameter to 50.
Edit the file and add the following line:
session_max_open_files=50
After editing the file, shut down the database and then restart it with the new initsid.ora file. Use the following command in SQL*Plus to start the database:
startup pfile="$ORACLE_HOME/pfile/initsid.ora"
Run the Oracle Files configuration assistant.
Oracle Files uses Oracle UIX (User Interface XML) technology to generate web pages. UIX dynamically generates many images, such as buttons and tabs, appearing throughout the UI. Due to limitations in Java 2 Standard Edition (J2SE) prior to version 1.4, UIX requires an X server process in order to generate dynamic images on UNIX platforms.
|
Note: This limitation does not affect Windows platforms. |
To locate the X server, the UIX runtime relies on the value of the DISPLAY environment variable. If the Web Client is running on a UNIX host, and some of the images in the UI appear broken or inconsistent, the problem may be that the value of the DISPLAY environment variable for the Web Client process is set incorrectly.
A common symptom of this problem is that instead of the rounded, beige buttons, UI pages are rendered using native browser buttons.
To verify the value of the DISPLAY environment variable for the Web Client process, open the $ORACLE_HOME/opmn/conf/opmn.conf file in a text editor, and locate the entry for the instance called \OC4J_Portal\:
<oc4j maxRetry="3" instanceName="OC4J_Portal" gid="OC4J_Portal" numProcs="1">
<environment>
<prop name="DISPLAY" value="your-host-name:0.0"/>
</environment>
</oc4j>
Change the value of the DISPLAY property to a running X server computer.
|
Note: During installation, the Oracle Universal Installer automatically populates the value of the DISPLAY property inopmn.xml using the value of the DISPLAY environment variable detected during the installation session. If you are running OUI remotely, such as from a desktop PC with X emulation software such as Hummingbird Exceed), this auto-detected value will be incorrect, because it will point to a remote X server that is not guaranteed to be available. The safest approach is to create an X server on the middle tier host and set the DISPLAY property to point to it. Consult your UNIX documentation on how to start an X server on your platform. |
