10g (9.0.4)
Part Number B10608-01
 Home |
 Solution Area |
 Contents |
 Index |
| Oracle Application Server Portal Error Messages Guide 10g (9.0.4) Part Number B10608-01 |
|
This chapter describes the error and warning messages, their causes, and suggested actions that may be encountered when upgrading to OracleAS Portal or when using an upgraded OracleAS Portal repository. The messages have been listed in alphabetical order in each section for easy location. For more information on upgrading the Oracle9iAS Portal repository, refer to the Oracle Application Server 10g Upgrading to 10g (9.0.4) guide, or the Upgrade documentation, available on Portal Center (http://portalcenter.oracle.com/upgrades).
This chapter contains the following upgrade error messages:
The following issues might be seen when the OUI installer was run.
Cause: This error can be caused by the JRE_MEMORY_OPTIONS being set too low on UNIX platforms.
Action: Consider running the installer with a high java heap size:
$ runInstaller -ms64m -mx128m
All of the messages are prefixed with ERROR: unless noted in the description. Some of the errors can be followed by additional Oracle messages, such as:
ERROR: ORA-12154: TNS:could not resolve service name
Error messages that are generated after the upgrade script has progressed past the precheck stage indicate that the Oracle9iAS Portal schema has had modifications. If you receive any error messages after the precheck step, you must fix the problem, restore your Oracle9iAS Portal from its backup and then run the upgrade script again.
Cause: This is the actual PL/SQL error in the WWUI_API_ALERT type body.
Action: Verify that this error is from the WWUI_API_ALERT type body. Also, confirm that the type is valid at the end of the upgrade. If this is the case, this error is benign and can be ignored. This error can cause the upgrade to state Upgrade Failed. However, if this is the only error, you can consider your upgrade successful.
Cause: The script that generates or validates the SSO ID reported an error so a valid SSO ID is not available to perform conversion.
Action: Run the upgrade again, specifying a valid SSO ID value for the -ssoid parameter. The value of the SSO ID can be obtained from the SSO migration log. The SSO ID appears in this log in the form SSO_IDENTIFIER:<string>, for example, SSO_IDENTIFIER:9E3985C4F187966.
Cause: An unexpected error was encountered while generating the SSO ID required for conversion of external application identifiers.
Action: Run the upgrade again, specifying a valid SSO ID value for the -ssoid parameter. The value of the SSO ID can be obtained from the SSO migration log. The SSO ID appears in this log in the form SSO_IDENTIFIER:<string>, for example, SSO_IDENTIFIER:9E3985C4F187966.
Cause: An unexpected error was encountered when reading the preference store.
Action: Run the upgrade again specifying a valid SSO ID value for the -ssoid parameter. The value of the SSO ID can be obtained from the SSO migration log. The SSO ID appears in this log in the form SSO_IDENTIFIER:<string>, for example, SSO_IDENTIFIER:9E3985C4F187966.
Cause: An unexpected error caused the script to abort.
Action: Based on the details in the message, correct the problem, restore your database from its backup and run the upgrade script again.
Cause: An unexpected error caused the script to abort.
Action: Based on the details in the message, correct the problem and run the upgrade script again. For example:
If the following lines are found in the log, then the error may be because Oracle Text is not installed correctly.
### PHASE I STEP 8: Perform pre upgrade checks Upgrade step started at Fri Apr 4 02:28:18 2003 Running upg/common/utlchvpd.sql Connected Calling DoPreChecks() Starting precheck at Fri Apr 4 02:28:21 2003 Calling upg/common/sysuppre.sql Connected.
ERROR: An unexpected exception was raised during the upgrade prechecks:
ORA-00942: table or view does not exist
----- PL/SQL Call Stack -----
object handle line number object name
80bc68c4 76 anonymous block
80bc68c4 380 anonymous block
Verify if the Oracle Text component is installed and reinstall it if it does not exist. Refer to the Oracle Application Server Portal Configuration Guide.
Cause: This error often accompanies the following errors:
32/5 PLS-00593: default value of parameter "P_BUTTON_STYLE" in body must match that of specIn alter type <portal_schema>.WWUI_API_ALERT compile body.
If the assertation violation accompanies these errors, its cause is the preceding errors. Refer to 32/5 PLS-00593: default value of parameter "P_BUTTON_STYLE" in body must match that of spec and In alter type WWUI_API_ALERT compile body reuse settings..
Action: If the assertation violation error accompanies the previously mentioned errors, it is benign and can be ignored. However, if an assertation violation appears in any other context, it is not benign and should be investigated.
Cause: You have answered n (no) when asked if the schema has been backed up.
Action: Back up the database and restart the script.
Cause: This error is seen in the log file when loading the LDIF files into OID. One error file, with the extension err, is created for each LDIF file. Each erroneous entry is listed in the LDIF format followed by the OID error code. An error file can be corrected and loaded again by using the ldapadd or ldapmodify command line utility. Refer to the Oracle Internet Directory Administrator's Guide for details on these commands.
For example:
dn:cn=PORTAL,cn=users, dc=us,dc=oracle,dc=com changetype:modify replace:OrclIsVisible OrclIsVisible:true # LDAP Error code: 32
In this particular case, either the host name or the port number is incorrect, or the OID server can not be accessed.
OID error code 49 -LDAP_INVALID_CREDENTIALS - The bind failed because the credentials are not correct.
Cause: Invalid SYS password for SSO.
Action: Confirm that you have completed the configuration steps in the documentation.
Cause: An invalid SYS password was supplied or the orapw file is missing.
Action: Supply the correct SYS password.If the password
is correct, make sure you can connect to SYS as sysdba
by creating a orapw<SID> file in the database Oracle
Home's dbs directory by running orapwd with the same password
used by the SYS database account.
Cause: Incorrect Oracle9iAS Portal schema, password or connect string.
Action: Supply the correct Oracle9iAS Portal schema, password or connect string.
Cause: Incorrect SSO Partner Application schema or password.
Action: Supply the correct SSO Partner Application schema or password.
Cause: Incorrect password store schema or password or connect string.
Action: Supply the correct Password Store schema or password.
Cause: Either the OID host, port, admin dn or admin password is not correct.
Action: Verify and correct the OID host, port, admin dn or admin password.
Cause: Dropping the Oracle Text indexes, or removing the synchronization or optimization jobs has failed. Find the output of the
uptxtdrpscript in the upgrade log to see what should be done. The entireuptxtdrp.logis appended to the error message output in the upgrade log.
Action: If the error was encountered while dropping the Oracle Text indexes, make sure that all the Oracle Text indexes are dropped before restarting the upgrade. For information about dropping Oracle Text indexes, refer to the Index Maintenance chapter of the Oracle Text Application Developer's Guide.
If the error was encountered while removing the synchronization or optimization jobs, make sure that these jobs are removed from the job queue before restarting the upgrade. For information about breaking or removing jobs, refer to the Managing Job Queues chapter of the Oracle9i Database Administrator's Guide.
After upgrading, manually recreate the Oracle Text indexes and the synchronization and optimization jobs if you wish to use Oracle Text searching in your OracleAS Portal. Refer to the Oracle Application Server Portal Configuration Guide for complete instructions.
Cause: The ORACLE HOME environment variable is not set.
Action: Review your environment and set the Oracle Home environment variable.
Cause: The schema or procedure is missing. For example:
ERROR: granting execute on SCHEMA1.CHECK_SAL to SCHEMA1B as SCHEMA1--ORA-01001:invalid cursor
In this case, there is a form in a database provider based on
SCHEMA1B, on the procedureSCHEMA1.CHECK_SALand either the procedureCHECK_SALis missing or one of the schemasSCHEMA1orSCHEMA1Bis missing. Therefore, the form will not run. However, it would not have run before the upgrade either.Action: Determine if the form or database provider is obsolete. If it is obsolete, delete it. If not, supply the missing schema or procedure.
Cause: This error can be seen during the patch application. It is caused by a Oracle9iAS Portal 3.0.9 type body that compiled normally in Oracle Database 8.1.7 and prior versions. However, it does not compile in Oracle9i databases. This error is expected while a patch is being applied. The type body becomes valid before the end of the upgrade, so the error no longer appears in the final validation step.
Action: Make sure WWUI_API_ALERT is valid
at the end of the upgrade. If this is the case, this error is benign and
can be ignored. This error can cause the upgrade to state Upgrade
Failed. However, if this is the only error, you can consider your
upgrade successful.
Cause: This error is due to the previous error. It occurs shortly after the patch application, during the early package recompiling step.
Action: Make sure WWUI_API_ALERT is valid
at the end of the upgrade. If this is the case, this error is benign and
can be ignored. This error can cause the upgrade to state Upgrade
Failed. However, if this is the only error, you can consider your
upgrade successful.
Cause: This error is seen in the log file when loading
the LDIF files into OID. One error file, with the extension err,
is created for each LDIF file. Each erroneous entry is listed in the LDIF
format followed by the OID error code. An error file can be corrected and
loaded again by using the ldapadd or ldapmodify
command line utility. Refer to the Oracle Internet Directory Administrator's
Guide for details on these commands.
For example:
dn:cn=PORTAL,cn=users, dc=us,dc=oracle,dc=com changetype:modify replace:OrclIsVisible OrclIsVisible:true # LDAP Error code: 32
In this case, either the OID administrator's Distinguished Name (DN) or the password is incorrect, or is not specified.
OID error code 49 -LDAP_INVALID_CREDENTIALS - The bind failed because
the credentials are not correct.
Cause: This is an OID error related to the modification of entries. While trying to modify an attributes value, it was discovered that an entry does not exist.
OID error code 32 - LDAP_NO_SUCH_OBJECT because the base specified
for the operation does not exist.
Related files used during the SSO migration: sm#.ldif
Related files used during the Oracle9iAS Portal
upgrade: pappacp.ldif, pu#.ldif, pacp#.ldif, pm#.ldif
Cause: This is an OID error related to the modification of entries.While trying to add an attribute value to an existing entry in OID, it was discovered that an attribute value already exists.
OID error code 20 - LDAP_TYPE_OR_VALUE_EXISTS because of duplicate
values specified for the attribute.
Related files used during the SSO migration: sm#.ldif
Related files used during the Oracle9iAS Portal
upgrade: pappacp.ldif, pu#.ldif, pacp#.ldif, pm#.ldif
Cause: This is an OID error related to the modification of entries. While trying to modify an attributes value, it was discovered that an entry does not exist.
OID error code 32 - LDAP_NO_SUCH_OBJECT because the base specified
for the operation does not exist.
Related files used during the SSO migration: sm#.ldif
Related files used during the Oracle9iAS Portal
upgrade: pappacp.ldif, pu#.ldif, pacp#.ldif, pm#.ldif
Cause: This is an OID error related to the modification of entries. While trying to modify an attributes value, it was discovered that an entry does not exist.
OID error code 32 - LDAP_NO_SUCH_OBJECT because the base specified
for the operation does not exist.
Related files used during the SSO migration: sm#.ldif
Related files used during the Oracle9iAS Portal
upgrade: pappacp.ldif, pu#.ldif, pacp#.ldif, pm#.ldif
Cause: This is an OID error related to the modification of entries. While trying to add an attribute value to an existing entry in OID, it was discovered that an attribute value already exists.
OID error code 20 - LDAP_TYPE_OR_VALUE_EXISTS because of duplicate
values specified for the attribute.
Related files used during the SSO migration: sm#.ldif
Related files used during the Oracle9iAS Portal
upgrade: pappacp.ldif, pu#.ldif, pacp#.ldif, pm#.ldif
Cause: SQLLDR encountered issues when trying
to load the languages.
Action: Look at the corresponding log and the .log
and .bad files from <upgrade_tmp_dir> for
specific issues. Give these to Oracle Support along with the upgrade logs.
Cause: An incorrect perl executable is being
used to run the upgrades.
Action: Refer to the Conventions and Definitions section in the Upgrade documentation.
Cause: The init parameter o7_dictionary_accessibility
is set to FALSE and a patch is being installed.
Action: Change the parameter o7_dictionary_accessibility
to TRUE. In addition, the remote_login_passwordfile init parameter
must be set to EXCLUSIVE. The upgrade can then be restarted. You can change
the parameter o7_dictionary_accessibility back to FALSE after the upgrade
has completed.
Cause: An error has occurred whilst attempting to retrieve information about the Oracle Text installation.
Action: Ensure the Oracle Text component is correctly installed. If necessary, reinstall the Oracle Text component. Refer to the Oracle Application Server Portal Configuration Guide for complete instructions.
Cause: One or more one-off patches that have schema changes have been applied to the Oracle9iAS Portal schema. These changes have not been tested with this release of the upgrade scripts, so the upgrade cannot proceed.
Action: See if a version of the upgrade scripts based on the next patch set has been released on Metalink. If so, download and run the new version. If not, wait until it is released. For example: You currently have Oracle9iAS Portal version 3.0.9.8.5 installed along with a one-off patch that has a schema change. The upgrade scripts you downloaded are based on 3.0.9.8.5 and were released before the one-off was released. This state is not supported for an upgrade using your current scripts. See if upgrade scripts based on the next patch set (3.0.9.8.6) have been released since you last downloaded the patch. If so, the one-off error message will not appear when the new version of the scripts are run.
Cause: Verify if this error is preceded by the following line as shown in this example:
Connect Information: portal30_DEMO/portal30_DEMO@orcl ERROR: ORA-01017: invalid username/password;logon denied
If so, this could be caused by a patch being applied and the Oracle9iAS Portal demo schema password is not equal to
<portal_schema_password>_DEMOor it could be because the schema does not exist.
Action: To avoid this error, set the password for the demo schema before the upgrade to have the value
<portal_schema_password>_DEMO. You can also choose to ignore this error.
Cause: This error can occur under several circumstances and indicates that the Oracle server process has failed.
Action: There is one case that may be encountered during
an upgrade that has a known solution. When running on certain 64-bit platforms,
the RDBMS bug 2614728 may cause the defnavpg.sql script to
fail. If you are on a 64-bit platform, check your upgrade log file to see
if the problem is encountered in the following context:
#-- Beginning inner script: wwd/defnavpg # Create seeded navigation pages for page groups declare * ERROR at line 1: ORA-03113: end-of-file on communication channel
If it is in this context, apply the patch for bug 2614728 for your platform. Restore from your backup, and run the upgrade again.
Cause: The shared pool size database parameter is too small.
Action: The value for this parameter depends on the size of your Oracle9iAS Portal. It may need to be several hundred megabytes for large Oracle9iAS Portals to avoid encountering this problem. Increase the shared pool size in your database and restart your upgrades after restoring from a backup.
Cause: The sysdba connection to the database has failed due to insufficient privileges.
Action: To connect to SYS as sysdba, create the orapw<SID>
file in the database Oracle Home's dbs directory by running orapwd
with the same password used by the SYS database account.
Cause: The instructions contained in Metalink Note 222437 to facilitate Oracle9iAS Portal working on an Oracle 9.2 database have not yet been applied. Here is an example of the error:
Loading Java Classes - soap.jar errors : class oracle/soap/providers/ejbprov/<class> ORA-29521: referenced name javax/ejb/<name> could not be found The following operations failed class oracle/soap/providers/ejbprov/<provider>: resolution exiting : Failures occurred during processing
Action: Restore your repository back to its Oracle9iAS Portal 3.0.9 state and follow the instructions contained in the Metalink Note 222437.1 available from the Oracle Metalink web site at http://metalink.oracle.com. Run the upgrade again after the steps have been completed.
Cause: The Oracle Text context indextype is not valid or does not exist. This may indicate a problem with the Oracle Text installation.
Action: Ensure the Oracle Text context indextype is present and valid. If necessary, reinstall the Oracle Text component. Refer to the Oracle Application Server Portal Configuration Guide.
Cause: The database does not contain the CTXSYS schema. This indicates that Oracle Text is not installed.
Action: Install the Oracle Text component in the database. Refer to the Oracle Application Server Portal Configuration Guide.
Cause: The database version is more recent that the Oracle Text component. This may indicate that the Oracle Text component was not upgraded correctly. The Oracle Text manual upgrade steps may have been omitted or failed. However, on certain platforms, this may also indicate that patch 2658339 has not been applied.
Action: Run the Oracle Text upgrade again or download and apply the patch depending on your situation.
Cause: The ORACLE_HOME environment variable is defined as a directory which does not contain an Oracle9i middle-tier installation.
Action: Define ORACLE_HOME to point to your Oracle9i middle-tier installation.
Cause: A patch installation has failed.
Action: Look at the upgrade log file for details.
Cause: UPG_ prefix tables exist in the Oracle9iAS
Portal schema. The upgrade is aborted.
Action: Delete all tables with the UPG_ prefix
from the Oracle9iAS Portal schema. Backup the tables
before removing them.
Cause: The Oracle9iAS Portal schema user has the EXEMPT ACCESS POLICY system privilege.
Action: Revoke the EXEMPT ACCESS POLICY privilege from the Oracle9iAS Portal schema user by running the following SQL command in SQL*Plus:
revoke exempt access policy from <portal_schema_user>;
Also verify the Oracle9iAS Portal schema user does not inherit the EXEMPT ACCESS POLICY privilege from any of its assigned roles.
Cause: The VPD check does not support your current version of Oracle9iAS Portal.
Action: Verify your Oracle9iAS Portal version is supported by this upgrade.
Cause: There is a mismatch between the ID and the prefix of the reference path. For example, if the ID was 104 and the following was shown:
105_HTMLPORTLET_511386
Action: Perform the following steps.
Cause: The ID portion of the reference path is missing. This causes non-unique portlet instance names in the table. For example, in the code below an ID should come before HTMLPORTLET:
_HTMLPORTLET_511386
Action: Perform the following steps.
Cause: This message indicates that the post upgrade scripts have not been executed. These tasks require a completed upgrade and your upgrade has errors. A summary of the errors are listed at the end of the upgrade log.
Action: Attempt to fix any errors listed. Search through this chapter and apply any fixes mentioned. Then restore from your backup and run another upgrade. If this fails, contact Oracle Support.
An example of a post-upgrade task is checking whether VPD is enabled correctly. Another example of a post-upgrade task is verifying if the SSO Partner Configuration has been run.
Cause: The upgrade script was unable to execute the SQL*Plus command.
Action: Make sure that bin/sqlplus exists
under your Oracle Home, and that you have permissions to execute it.
Cause: You have answered n (no) when asked if input details are correct.
Action: Correct the perceived problem and restart the upgrade script.
Cause: You are trying to run multiple simultaneous upgrades from the same location.
Action: Wait until the upgrade you started earlier finishes
before starting another one. If a previous upgrade (run using upgrade.csh)
terminated abnormally (for example, with Ctrl+C), the lock
file created during upgrade (upgcsh.lok) is not deleted. Therefore,
if you attempt to start another upgrade, you will see this message. In this
case you will need to manually delete the lock file. You should delete this
lock file only when an upgrade has abnormally terminated, not if an upgrade
is actually running. You can find the lock file in the location from where
you ran the upgrade script.
Cause: Packages in the Oracle Text schema (CTXSYS)
beginning with DRI or CTX_ are invalid.
Action: Revalidate the Oracle Text invalid packages. If necessary, reinstall the Oracle Text component. Refer to the Oracle Application Server Portal Configuration Guide.
Cause: The ID in the prefix of the reference path is repeated. For example:
105105_HTMLPORTLET_511386
Action: Perform the following steps:
<upgrade_directory>/309-903/wws/upfixpin.sql
on your Oracle9iAS Portal repository from SQL*Plus
as the schema owner. pobcheck.log file from
the <upgrade_tmp_dir> directory.
Cause: The value of SSO ID was passed when converting the external application identifiers. This value is invalid.
Action: Specify a valid SSO ID value for the -
ssoidparameter and run the upgrade again.
Cause: The version of SQL*Plus you are trying to execute is not current enough.
Action: Verify that the version of bin/sqlplus
under your Oracle Home is at least 9.0.1.
Cause: The SSO version is not correct.
Action: Install one of the supported SSO versions.
Cause: System triggers are disabled in your database configuration file.
Action: Verify that the _
system_trig_enabledparameter is set to TRUE in your database'sinit.orafile. If it is not, set it to TRUE and restart your database.
Cause: The java pool size parameter is too small.
Action: Increase the java pool size parameter to 20 MB or greater. Refer to the documentation, if necessary, then run the upgrade again.
Cause: The shared pool size parameter is too small.
Action: Increase the shared pool size to 20 MB or greater. Refer to the documentation, if necessary, then run the upgrade again.
Cause: If users have not been correctly migrated from the 3.0.9 SSO Server, it can cause errors such as this one. In this case, the application entry does not exist in OID when trying to synchronize data between the OID server and the Oracle9iAS Portal schema. This may indicate that either the application entry was not created in OID or a different Oracle9iAS Portal instance name was used when creating the LDIF files, compared with the Oracle9iAS Portal instance name used when synchronizing the OID entries.
Action: The creation of OID entries during upgrade involves the following steps provided by different modes of the upgrade script
upsecoid.
- Creation of the SBS files (
createmode)
- Conversion of the SBS files to the LDIF files (
ldifmode)
- Load the LDIF files into OID (
loadmode)
- Synchronize the OID entries (
syncmode)
The four modes specified must be done in the order listed. If one of these steps was missed, then all steps from that step onwards must be performed again.
Verify the parameters specified for these steps to make sure that the parameters (such as the host and port for the OID server and the Oracle9iAS Portal instance name) have been used consistently throughout.
Cause: If the compatible init parameter is not set to at least 9.0.0, then the upgrade aborts.
Action: Set the compatible init parameter to at least 9.0.0 in your
init.orafile.
Cause: The database blocksize is less than 8K.
Action: Create a new Oracle9i database with a minimum blocksize of 8K. Use the database import/export utilities to move your Oracle9iAS Portal from your prior database to the new one.
Cause: Jobs submitted under a previous version of Oracle9iAS Portal may not run properly under OracleAS Portal 9.0.4 and higher.
Action: Re-enable the job queue and allow the jobs to complete, or remove them.
Cause: The export/import internal view has not been installed.
Action: Load rdbms/admin/catexp.sql from
your database Oracle Home. Then restart the upgrade.
Cause: There are invalid Oracle9iAS Portal objects in the Portal schema.
Action: Investigate the invalid Oracle9iAS Portal objects in the Oracle9iAS Portal schema and fix the source of the problem. Run the upgrade again.
Cause: Mandatory objects which Oracle9iAS Portal relies on are not present in the database or are invalid. If they are missing due to a faulty upgrade of the database, it could cause failures in the Oracle9iAS Portal upgrade as well.
Action: Review your database installation and upgrade procedures. If the object is present but invalid, run the utlrp.sql script located in rdbms/admin of your database Oracle Home in an installation to recompile all invalid objects in the database.Or, this error could be the result of missing JAR files. If the precheck failed due to missing JAR files, the JAR files can be reloaded before trying the upgrade again. All of these JAR files can be found under your Oracle9iAS 1.0.2.2 Oracle Home under
portal30/java. The following are the JAR files that are loaded in Oracle9iAS Portal.
xmlparserv2.jar - This JAR file is
loaded during the Oracle9iAS Portal installation
only if the Oracle database version is 8.1.5 or 8.1.6.
whttpsrc.jar - This JAR file is loaded
during the Oracle9iAS Portal installation only
if the Oracle database version is 8.1.5 or 8.1.6.
xmltrans.jar
bulkload.jar
prohttp.jar
wwvdp.jar
wwvdpdb.jar
In addition to the above JAR files, SSOHash.class is loaded
in both Oracle9iAS Portal and SSO schema. SSOHash.class
is found under your Oracle9iAS 1.0.2.2 Oracle Home
under portal30/wwc.
Perform the following operations if you are missing a JAR file.
portal30/admin/plsql/lib directory.
Table 6-1 JAR files contained in Oracle9iAS Portal Patch Release Versions
loadjava -user <portal_schema_user>/<portal_schema_password> -verbose -resolve -force <jar_file>
SSOHash class with the following
commands:
loadjava -resolve -user <sso_schema>/<sso_password> SSOHash.class loadjava -resolve -user <portal_schema>/<portal_password> SSOHash.class
Oracle9iAS Portal 9.0.2 uses a Java component in the Oracle9iAS Portal repository to communicate with Web Providers. After loading the JAR files, if you still encounter problems with Web Provider communications, it could be due to missing Java permissions or invalid Java classes loaded into the Oracle9iAS Portal database.
Cause: Java is not installed in the database or there was a problem during the Java portion of the database upgrade.
Action: Enable the Java Option and run the upgrade again.
Cause: SYS java objects are not present in the database or are invalid.
Action: Recompile the invalid java objects in SYS. If this fails, reinstall the JVM in the database.
Cause: The LDAP packages were not installed.
Action: Load
rdbms/admin/catldap.sqlfrom your database Oracle Home. Then restart the upgrade.
Cause: The optimizer mode is incorrectly set as
RULE.
Action: Change the optimizer mode to
CHOOSEand run the upgrade again.
Cause: An incorrect
perlexecutable is being used to run the upgrades or your Oracle Home is not pointing to the middle-tier Oracle Home.
Action: Verify that your Oracle Home is pointing to the middle-tier Oracle Home and using the correct
perlexecutable. Restart the upgrade.
Cause: The schema on which the Portlet Builder application is based is missing.
Action: There are two possible ways to fix this issue:
Cause: The SSO ID required for conversion of external application identifiers could not be generated. This could happen if a unique
ls_login_urlcannot be obtained from the Oracle9iAS Portal schema.
Action: Run the upgrade again, specifying a valid SSO ID value for the
-ssoidparameter. The value of the SSO ID can be obtained from the SSO migration log. The SSO ID appears in this log in the formSSO_IDENTIFIER:<string>, for example,SSO_IDENTIFIER:9E3985C4F187966.
Cause: The SSO version is correct, but the migration has not been done.
Action: Migrate the SSO and then upgrade the Oracle9iAS Portal repository.
Cause: The system triggers are not enabled.
Action: Set the system triggers enabled flag in the Oracle parameters file to TRUE and run the upgrade again.
Cause: The value of the SSO ID parameter specified during upgrade is invalid.
Action: Run the upgrade again, specifying a valid SSO ID value for the
-ssoidparameter. The value of the SSO ID can be obtained from the SSO migration log. The SSO ID appears in this log in the formSSO_IDENTIFIER:<string>, for example,SSO_IDENTIFIER:9E3985C4F187966.
Cause: There are other sessions running on the Oracle9iAS Portal schema.
Action: Make sure your Oracle9iAS Release 2 middle-tier is shut down and no other connections are made to the schema being upgraded.
Cause: There are other sessions running on the Oracle9iAS Portal schema.
Action: Make sure your OracleAS Middle Tier 10g (9.0.4) is shut down and no other connections are made to the schema being upgraded. Check the Analyze Product Schema step in the upgrade log for more information on the concurrent sessions.
Cause: There are DBMS jobs running.
Action: Either kill the DBMS jobs or wait for them to finish before restarting the upgrade. Check the Analyze Product Schema step in the upgrade log for more information on the running jobs.
Cause: There are Oracle9iAS Portal jobs in the DBMS job queue which were either incorrectly submitted as another user, or submitted as the Oracle9iAS Portal user with another default schema or default privilege user.
Action: Remove these jobs from the job queue. The upgrade correctly resubmits any jobs that are missing.
Cause: Some VPD policies in Oracle9iAS Portal schema are not static.
Action: Run the
vpdstatic.sqlscript from SQL*Plus while logged in as a Oracle9iAS Portal schema user. The script is located in the Oracle9iAS Portal 3.0.9.8.3 or later patch set.
Cause: There is less than 20MB of free default tablespace.
Action: Create at least 20MB of free default tablespace. Run the upgrade again.
Cause: There is less than 10M of free temporary tablespace.
Action: Create at least 10M of free temporary tablespace. Run the upgrade again.
Cause: You do not have permissions to create the temporary directory.
Action: Change your permissions on the parent directory.
Cause: The upgrade log file could not be created.
Action: Change your permissions on the directory where the upgrade log is written or specify a different log file location and run the upgrade again.
Cause: The permissions on the temporary directory do not allow the creation of a login.sql script for the user profile.
Action: Change your permissions on the temporary directory and run the upgrade again.
Cause: This error is caused by running an upgrade on a UNIX platform with an incorrect library path.
Action: On UNIX platforms, verify that
$ORACLE_HOME/libis at the beginning of the library path.
Cause: This error is caused by running an upgrade on a UNIX platform with an incorrect library path.
Action: On UNIX platforms, verify that
$ORACLE_HOME/libis at the beginning of the library path.
Cause: This is an internal error that may occur when converting the external application identifiers.
Action: Report this error to Oracle Support and provide them the output files for upgrade.
Cause: An unexpected error happened during the specified step. A subsequent message following this one will contain details about the error.
Action: If the situation described in the details can be corrected, do so.
Cause: Incorrect arguments were supplied to
upgrade.csh.This error is not prefixed with ERROR:.
Action: Check the usage of the
upgrade.cshcommand and run the upgrade again.
Cause: This message indicates that the version of Oracle9iAS Portal will not be updated to the new version. Errors have occurred in the upgrade which will prevent Oracle9iAS Portal from functioning properly. A summary of the errors is listed at the end of the upgrade log.
Action: Attempt to fix any errors listed. Search through this chapter and apply any fixes mentioned. Then restore from your backup and run another upgrade. If this fails, contact Oracle Support.
Cause: Unsupported Oracle9iAS Portal version.
Action: Make sure you are running the upgrade on a supported Oracle9iAS Portal version (3.0.9.8.3, 3.0.9.8.3A, 3.0.9.8.4, 3.0.9.8.5, 9.0.2.0, 9.0.2.2, 9.0.2.3, or 9.0.2.6).
Cause: Incorrect RDBMS version.
Action: Upgrade to the minimum database version of Oracle9i Database 9.0.1.4 Enterprise or Standard editions.
Cause: Incorrect Oracle9iAS Portal version.
Action: Make sure you are running on a supported Oracle9iAS Portal version (3.0.9.8.3, 3.0.9.8.3A, 3.0.9.8.4, 3.0.9.8.5, 9.0.2.0, 9.0.2.2, 9.0.2.3, or 9.0.2.6).
Cause: The login trigger(s) is not setting the correct context.
Action: Verify the login trigger is correctly installed. To install the trigger, run the
logintrg.sqlscript from SQL*Plus while logged in as SYS user. The script is located in<upgrade_directory>/upg/commondirectory.
Cause: The Oracle9iAS Portal login trigger that sets the VPD context is not installed or is disabled.
Action: Verify the Oracle9iAS Portal login trigger was installed and enabled on you database. If you need to install the trigger, run the
logintrg.sqlscript from SQL*Plus while logged in as SYS user. The script is located in<upgrade_directory>/upg/commondirectory.
Cause: One of the VPD checks has failed.
Action: This error is followed by a detailed message. Resolve the issue by examining the information provided in the message.
Cause: A problem occurred in the database that caused the VPD check to fail.
Action: Consult your database documentation to find possible actions.
Cause: You do not have permissions to write to the temporary directory.
Action: Change your permissions on the temporary directory or specify a different temporary directory location and run the upgrade again.
The following messages are informational. Although they do not prevent the upgraded Oracle9iAS Portal from functioning, they should be investigated. All of the following messages are prefixed with WARNING:, unless noted in the description.
Cause: The session cleanup job is a job that usually exists in the Oracle9iAS Portal schema. However, an earlier operation such as the database upgrade resulted in creating this job in the SYS schema. For example:
WARNING: 1 session cleanup job(s) detected in the SYS schema.
Action: This message is informational only. No action is required.
Cause: By default, the debug log files generated by the
OID Control Utility are created in your Oracle Home's ldap/log directory.
This error indicates that the log file could not be created because of insufficient
privileges. This error is not prefixed with WARNING:. The ldifmigrator
command creates the following output:
Cannot create log file. The log message will be re-directed to standard error stream. Migration of LDIF data to OID starts: <date> Input file: secuaci.sbs Output file: secuaci.ldif Substitution Variables s_SubscriberDN: dc=mycompany.dc=com s_UserContainerDN: cn=Login Server (portal30_sso) s_GroupContainerDN: cn=Groups, dc=mycompany,dc=com s_SubscriberOracleContextDN: cn=OracleContex,dc=mycompany,dc.com s_UserNicknameAttribute: cn s_RootOracleContentDN: cn=OracleContent s_CurrentUserDN: cn=oracladmin Migration of LDIF data to OID completed: <date>
Action: Obtain write permissions to the Oracle Home's
ldap/log directory. Save your changes and run the upsecoid
script again to see the log files in this directory. Refer to the Oracle Internet
Directory Administrator's Guide for details.
Cause: Titles of Portlet Builder (formerly WebView) components
must be unique. If there are any Portlet Builder components with duplicate
titles, they are renamed to <display_ name> <component_id>.
Customizations remain intact. For example:
WARNING: Changing title of component RPT_WIZ1 from "Wizard Report" to "Wizard Report 1169884988"
When this component is rendered, the new title appears. If this has been customized, there is no effect. The customized title appears.
Action: Go to the component and rename it to something more meaningful.
Cause: The component is based on one or more missing objects. For example, a QBE is created based on table
MY_TABLE. ThenMY_TABLEis dropped. For example:WARNING: Component SCOTT.MY_QBE has errors. Please check that all the objects it is based on are present.
Action: Supply the missing object. If the component is no longer being used, delete it using the OracleAS Portal Navigator.
Cause: An object on which a Portlet Builder calendar is based is missing. This happens when:
Examples:
WARNING: Could not Parse select a1.HIREDATE the_date, a1.ENAME the_name, null the_name_link, null the_date_link, null the_target from test_1.EMP_ 1 a1 order by a1.HIREDATE as TEST_1. WARNING: Could not Parse select b2.HIREDATE the_date, b2.ENAME the_name, null the_name_link, null the_date_link, null the_target from test_2.EMP_ 2 b2 order by b2.HIREDATE as TEST_2.This warning usually occurs while upgrading a Oracle9iAS Portal which was created using Oracle export/import. Not all of the schemas on which the Portlet Builder components are based were imported. Calendars which show this warning cannot be used unless the missing objects are supplied, and the calendar component is regenerated.
Cause: The refresh of the OminPortlet provider failed because the provider is not accessible.
Action: Verify that the OmniPortlet Web provider is accessible on the portal's middle-tier. After verification, refresh this provider from the Portlet Repository.
Cause: The refresh of the OracleAS Portal database provider failed because the provider is not accessible.
Action: Verify that the OracleAS Portal provider is accessible and that the
wwptl_general_providerpackage in the OracleAS Portal schema is valid. After verification, refresh this provider from the Portlet Repository.
Cause: This site is missing style information that is needed for upgrade. The site has been deleted.
Action: No action is required.
Cause: At the time of upgrade, when the seeded OmniPortlet, Web Clipping, and OracleAS Portal Building Tools providers are registered, it is assumed that these providers are deployed on the same middle-tier as identified in the Default JPDK Instance URL. You can view this value by completing the following steps:
- Log on to your OracleAS Portal.
- Click the Administer tab.
- In the Services portlet, click the Global Settings link.
- Click the Configuration tab.
- Locate the Default JPDK Instance URL field. Usually this value is
<portal_middle_tier_protocol>://<portal_middle_tier_host>:<portal_middle_tier_port>/jpdk/servlet/soaprouter/. If there is no value in this field, you will receive the warning mentioned above in your upgrade log.
Action: Run the script
<upgrade_directory>/upg/9025-9026/wws/updmturl.sqlto update the URLs for these providers. The script updates the middle-tier URL for the PORTLETBLDGTOOLS, OMNIPORTLET, and WEBCLIPPING providers in the providers table. This script is not run from the upgrade script. Run it in standalone mode to update the URLs. For example:updmturl.sql http my.domain.com 80where:
httpis the middle-tier's protocol
my.domain.comis the middle-tier's host
Cause: The upgrade found an item on a page which appears to have a document attached but this document does not actually exist. This indicates a data corruption in the data for the item. The item will be upgraded but its document will not be accessible. It is unlikely that the document was accessible in Oracle9iAS Portal 3.0.9 either.
Action: Delete the item and recreate it.
Cause: Image charts, which were a beta feature in Oracle9iAS Portal 3.0.9, are not supported in OracleAS Portal 9.0.4 and are removed from the repository. Any image charts in the Oracle9iAS Portal being upgraded will be lost. If the chart has been referenced by another component, such as a menu or a link, it now produces a warning. For example, menus could link to an image chart. When the user clicks on the item, an error message indicates that the component is missing. This warning is also produced if a legacy menu is linked to a non-existent component.
This means that the image chart:
- No longer appears in the navigator under the provider.
- No longer appears in the portlet repository.
- No longer appears on any pages that it was previously added to.
- Also, links to the image chart result in errors.
Action: Delete or edit the menus, links and other components that previously pointed to the charts to point to a new location.
Cause: The given path already exists in the DAV tables. This could be because a subpage has the same name as a document in the path shown in the warning. The upgrade continues, but the page group may not be accessible from DAV.
Action: Rename the subpage (name field in the edit page properties dialog) so that it no longer clashes with the document filename. Then run the DAV Loader by executing the following SQL while logged in as the schema owner:
set serveroutput on size 100000 begin wwdav_loader.create_dav_content; end;
Cause: You have a very large number of external applications. The customizations for these applications have exceeded the maximum physical limit for their storage. As a result, some customizations may have been lost.
Action: Reduce the number of external applications on the SSO server. Edit the defaults for the external applications portlet and advise the users to check their customizations.
Cause: This message may occur when there are invalid NAVBAR references in the folders table (
wwv_corners). This does not have an effect on the upgraded OracleAS Portal.Action: This is a benign warning message that can be ignored.
Cause: This message may occur when there are invalid style references in the folders table (
wwv_corners). This does not have an effect on the upgraded OracleAS Portal.Action: This is a benign warning message that can be ignored.
Cause: Non-Oracle9iASPortal objects in the Oracle9iAS Portal schema cannot be compiled and have errors.
Action: Find out what is causing the object not to compile and rectify it.One reason these errors could occur is because deprecated or changed Oracle9iAS Portal 3.0.9 APIs are being referenced and these APIs do not work with OracleAS Portal 9.0.4. Refer to the PDK information on http://portalcenter.oracle.com.
Cause: It was not possible to
pingthe specified host usingperl. There are detected cases where theperlversion ofping, used in the upgrades, does not detect availability of hosts even when they can actually be reached.Action: Try using the Operating System
pingcommand to see if the host can be reached. If the host can be reached, then you can ignore this warning. If the Operating Systempingfails, then bring up the host or check if it is in the network. Use the Operating Systempingcommand for each failed host. The following example shows the Reachability Details which follow this warning.Host Reachability Details Portal Midtier Host: yes Web Cache Host: yes SSO Midtier Host: noIn this case, the upgrade script was not able to
pingthe SSO middle-tier host. Useping <sso_midtier_host>from the command prompt to see if the SSO Middle-Tier host can be reached or not.
Cause: This informational message indicates there are too many archive versions of Portlet Builder (formerly WebView) components. This may be because in Oracle9iAS Portal 3.0.9 a new version of a component was created each time the component was edited and saved. For example:
WARNING: Only 38 % of components in wwv_modules$ table are production components.Action: Delete as many of the archive versions of components as possible. This reduces the size of the tables where attributes for all the archive versions are stored.
Cause: When upgrading Oracle9iAS Portal 3.0.9 Personal Pages to the Shared Objects page group, if the ID of a personal page already exists in the Shared Objects page group as a Personal Folder in Oracle9iAS Portal 3.0.9, it will be assigned a new ID. For example:
Personal page id change - old id:: 443 => new id:: 32256Action: If the user has bookmarked the Oracle9iAS Portal 3.0.9 URLs for personal pages, then the bookmarks must be updated with the new ID value.
Cause: Personal Pages whose names clash with Personal Folders in the Shared Objects page group are updated. For example:
WARNING: Renamed personal page from "MY_REPORTS" to "MY_REPORTS_10104585"Action: Rename the page to a more meaningful, unique name if desired. Access the warning file
<upgrade_tmp_dir>/upgrade.wrn.
Cause: The Portlet Builder components (packages) are invalid.
Action: Try resolving the cause of the errors when compiling the packages listed in the log. For example, a report may be based on a table and the table has been dropped. In this case, the report is no longer valid, so you can drop the report.
Cause: When a user is deleted from the portal, the pages for that user are not deleted. Even though the user has been deleted, the pages could still be required within the portal. In this case, the owner of these pages is reassigned to be the portal schema owner. For example:
Reassign for page id = 23555 user name = STIGERAction: No action required.
Cause: When a user is deleted from the portal, the pages for that user are not deleted. Even though the user has been deleted, the pages could still be required within the portal. In this case, the owner of the these pages is reassigned to be the portal schema owner. For example:
Reassigning the owner of the following pages to the schema owner PORTAL30Action: No action required.
Cause: The upgrade script could not delete the recent object portlet preferences.
Action: Although deleting the preferences does not affect the Oracle9iAS Portal, remove them to eliminate this warning.
Cause: The region on the page was not successfully converted to a sub-page links region during the upgrade, since it contained items other than just the sub-page display items.
Action: The user must first move all the existing items in the region to a different region on the page. After making this change, the user can edit the region properties to convert it to a sub-page links region. Alternatively, a sub-page links region can also be created on the page.
Cause: The region on the template was not successfully converted to a sub-page links region during the upgrade, either because there were items other than just the sub-page display items on the template itself, or on the pages based on the template. In this case, there were far too many items found in the region, so individual warnings for all pages based on the template could not be reported.
Action: The user must first move all the existing items in the region to a different region on the template/page. After making this change, the user can edit the region properties to convert it to a sub-page links region. Alternatively, a sub-page links region can also be created on the template.
Cause: The session cleanup job is a job that usually exists in the Oracle9iAS Portal schema. However, an earlier operation such as the database upgrade has resulted in removing this job as a part of the upgrade. For example:
WARNING: Removed session cleanup job: 63 from the SYS schema.Action: If the database instance where the upgrade is being performed does not contain any other Oracle9iAS Portal schema, then no action is required. This is because the session cleanup job gets created in the Oracle9iAS Portal schema during upgrade. However, if there are other Oracle9iAS Portal schemas in the database instance, then it must be verified that they all have their respective session cleanup jobs. Run the script
<upgrade_directory>/wwc/ctxjget.sqlfromsqlplusin a Oracle9iAS Portal schema to check whether the session cleanup job exists. If this job is missing in any Oracle9iAS Portal schema then you can create it by running the script<upgrade_directory>/wwc/ctxjsub.sqlfromsqlplusin that schema.
Cause: During precheck upgrade mode, it was detected that one or more sites were missing style information that is needed for upgrade.
Action: This sites in question will be deleted because they cannot be repaired. Save any information that you need from these sites before running the upgrade. To determine which sites are affected, refer to the
sitechk.logfile found in the <upgrade_tmp_dir> directory, which includes the following message for each site:Site <site name> will be deleted because it is missing necessary data and cannot be upgraded.
Cause: The subpage item was obsoleted but could not be replaced by a subpage region type because there were other items in the same region.
Action: Create a new subpage type region on the page where the warning message appears.
Cause: The VPD policy on the table indicated in the message was not installed properly in your Oracle9iAS Portal schema.
Action: If the table indicated in the message is not part of the Oracle9iAS Portal product, it is safe to ignore the warning. If the table is one of the following, it is also safe to ignore this warning:
In all other cases, there may have been a problem with a previous installation or upgrade procedure. Contact Oracle Support for more information.
Cause: The region on the template was not successfully converted to a sub-page links region during the upgrade, either because there were items other than just the sub-page display items on the template itself, or on the pages based on the template.
Action: The user must first move out all the existing items in the region to a different region on the template/page. After making this change, the user can edit the region properties to convert it to a sub-page links region. Alternatively, a sub-page links region can also be created on the template.
Cause: The DBMS job queue must be enabled for proper operation. It may have been disabled by setting the system parameter
job_queue_processesto 0, or by restricting logins.Action: Make sure
job_queue_processesis set to one or greater, and that logins are not restricted by changing the system disable restricted session.
Cause: Oracle9iAS Portal and non-Oracle9iAS Portal objects are compiled separately. For Oracle9iAS Portal objects, compilation problems are reported as errors. However, for non-Oracle9iAS Portal objects, compilation problems are reported as warnings, since they should not cause the upgrade to be considered a failure.
Action: Examine the generated file
<upgrade_tmp_dir>/nonportal.logand fix the compilation problems associated with your objects. Compilation errors in your packages may cause your portlets to render incorrectly.
Cause: Either the OID server has not yet been configured or the OID parameters in the preference store are incorrect. Therefore, there is a problem accessing the OID server in order to refresh the local cache.
Action: Run
ptlasstin the MIDTIER mode after the upgrade to manually refresh the local cache from OID.
Cause: There is a conflict between the names of providers. For example:
WARNING: The provider name for application MY_APP has been changed to MY_APP_63Action: Specify the new name instead of the old one when you register the provider as a remote provider using the PL/SQL adapter. For example:
The
service_idshould be:urn:MY_APP_63instead ofurn:MY_APPIf you have no plans of using the PL/SQL adapter, you can ignore this message.
Cause: Some VPD policies in Oracle9iAS Portal schema are not static.
Action: Run the
vpdstat.sqlscript from SQL*Plus while logged in as a Oracle9iAS Portal schema user. The script is located in<upgrade_directory>/upg/309-903/wwhdirectory.
Cause: Top Level Pages whose names clash with Personal Folders in the Shared Objects Page Group are updated.
Action: Rename the page to a more meaningful, unique name if desired. Access the warning file
<upgrade_tmp_dir>/upgrade.wrn.
Cause: A database provider (formerly called application) schema is missing. For example:
WARNING User/Role SCOTTB does not exist. Application based on SCOTTB will have errors.In this case, the database provider would not have been accessible before the upgrade either.
Action: Determine if the database provider is obsolete. If it is, delete it. If not, supply the missing schema.
Cause: One of the VPD checks has failed.
Action: This warning is followed by a detailed message. Resolve the issue by examining the information provided in the message.
The following errors are seen after the OracleAS Portal has been upgraded and is in use.
When the user clicks on a DAS link or the user or group LOV after upgrading the OID server from Oracle9iAS Portal 9.0.2 to OracleAS Portal 9.0.4.
Cause: The DAS URLs have changed between a 9.0.2 OID server and a 9.0.4 OID server. When the OID server is upgraded from 9.0.2 to 9.0.4, these URLs get updated. OracleAS Portal maintains a cache of these URLs in its repository. The OracleAS Portal cache does not get updated automatically so it becomes inconsistent with the URLs maintained in the OID server upon OID server upgrade.
Action: Reconfigure OracleAS Portal for the Oracle Internet Directory server, as described in the "Reconfiguring the OracleAS Portal for the Oracle Internet Directory Server" section of the Oracle Application Server 10g Upgrading to 10g (9.0.4) guide. This step is required to ensure that the OracleAS Portal entries in the Oracle Internet Directory are properly updated, and that the correct provisioning events required by Oracle Application Server 10g are sent to the portal.
Cause: The deployment of portalTools.ear or
portalHelp.ear has failed while you are trying to access:
portalTools: http://<host>:<port>/portalTools portalHelp: http://<host>:<port>/portalHelp/en/
Action: Run the OC4J configuration assistant again to deploy the applications.
This error can occur if a Oracle9iAS Portal Repository (9.0.2) configured to use Oracle Internet Directory (9.0.4) is upgraded to OracleAS Metadata Repository (9.0.4) and you try to edit a private group:
Cause: To be able to view private groups, Portal needs to be a member of the group "
cn=Common Group Attributes,cn=Groups,cn=OracleContext". The Portal application is missing this privilege in the Oracle Internet Directory server.Action: Run
ptlasst.cshwith-mode MIDTIERand-type OID,e.g., ptlasst.csh -mode MIDTIER -type OID -s portal -sp portal -c dbHostName:1521:dbServiceName -ldap_h myOIDServer -ldap_p 389 -ldap_w welcome1 -pwd secret123
Cause: The following error is written to the database trace file when read and write permissions for Java properties are not granted to the SYS user. The permissions must be granted for the Java component in the Oracle9iAS Portal database to run correctly.
Java call terminated by uncaught Java exception:ExceptionInInitializerError (WWC-43000)Action: Perform the following actions:
Connect to the OracleAS Portal database as SYS.
Run the following query to determine if the permission has been granted:
SELECT * FROM dba_java_policy WHERE grantee = 'SYS' AND type_name = 'java.util.PropertyPermission' AND enabled = 'ENABLED'If no rows are returned from the query, execute the following statement when connected as SYS:
call dbms_java.grant_ permission('SYS','SYS:java.util.PropertyPermission', '*', 'read,write');Check that the Java classes in the database are valid
The Java classes used to communicate with Web Providers are in the package
oracle.webdb.provider.web. Check that these classes are valid using the following query when connected as the Oracle9iAS Portal owner:SELECT dbms_java.longname(object_name), status FROM user_objects WHERE object_type = 'JAVA CLASS' AND dbms_java.longname(object_name) LIKE 'oracle/webdb/provider/web/%'If any objects have an invalid status, recompile them using:
ALTER JAVA CLASS <class_name> COMPILE.
Cause: The category or perspective portlet had not been customized to select anything for display. Thus, the upgraded search results page portlet instance does not have any search criteria selected. In such a case, the upgraded portlet instance is rendered with this message. For information how to set up the search feature, refer to the Portal Online Help, Setting Up the Search Feature topic or the OracleAS Portal User's Guide, Adding Search Functionality section.
Action: Define the search terms.
Cause: If you encountered this error while accessing documents with spaces or plus signs in the document name, it could because the
PlsqlCompatibilityModeflag is still set. This flag is located in the DAD configuration file.Action: Remove the
PlsqlCompatibilityModeflag. This flag is located in the DAD configuration file.
If this error is seen for URLs in the format:
/pls/dad/url/...
Cause: The
PlsqlPathAliasProcedureparameter in the portal DAD is incorrectly configured asschema.wwdoc_process.process_downloadinstead of being set toschema.wwpth_api_alias.process_download. This can happen if you use Oracle Enterprise Manager 9.0.2 to create a Oracle9iAS Portal DAD.Action: Change PlsqlPathAliasProcedure in the Portal DAD to schema.wwpth_api_alias.process_download by following these instructions:
- Navigate to the EM UI (typically, this is http://host:1810).
- Select the Oracle9iAS instance you wish to configure.
- Select the HTTP server component.
- Select PL/SQL properties.
- Under the DAD section, select the erroneous DAD.
- Select the section Document, Alias and Session.
- Change the value of Path Alias Procedure to <portal_schema>.wwpth_api_alias.process_download.
- Apply the change.
- Restart OHS to make the configuration change take effect.
- If you do not wish to use EM UI, refer to the OHS configuration guide on how to make manual changes to the mod_plsql configuration.
Cause: The deployment of portalTools.ear or portalHelp.ear has failed while trying to access:
portalTools: http://<host>:<port>/portalTools portalHelp: http://<host>:<port>/portalHelp/en/Action: Run the OC4J configuration assistant again to deploy the applications.
Cause: This error can occur if the OracleAS Portal owner is not granted the correct Java permissions. If the permissions have not been granted, this browser error is accompanied by the following error in the database trace file:
java.security.AccessControlException: the Permission (java.net.SocketPermission <ip_address> connect,resolve) has not been granted to <portal_schema_user>.Action: Perform the following steps:
Connect to the OracleAS Portal database as SYS.
Use the following queries to determine if the permission has been granted:
SELECT * FROM dba_java_policy WHERE grantee = '<portal_schema_user>' AND type_name = 'java.net.SocketPermission' AND enabled = 'ENABLED'The permission is also granted via the
JAVASYSPRIVrole. Check if this role is granted to the Oracle9iAS Portal owner using this query:SELECT * FROM dba_role_privs WHERE grantee = '<portal_schema_user>' AND granted_role = 'JAVASYSPRIV'If no rows are returned from either query, execute the following statement to grant the permission:
call dbms_java.grant_permission('<portal_schema_ user>','SYS:java.net.SocketPermission', '*', 'connect,resolve');
Cause: Due to the new architecture, URLs have changed. In this case, a user's custom data created a broken link.
Action: Correct the invalid URLs.
Cause: This error is seen when running
upsecoidmanually. The application entry DN is constructed based on the instance name provided when runningupsecoid. The OracleAS Portal was unable to locate the application entry, based on the specified instance name, in OID. This can happen if either thesyncmode ofupsecoidwas run before running thecreate,ldifandloadmodes, or if there was a mismatch between the instance name used for theldifandsyncmodes. This can also happen ifupsecoidwas run from a pre-upgraded schema.Action: Verify that all modes of
upsecoidhave been run in order. Theloadmode loads the OID entries. Use the LDAP command line tools to verify the existence of the OID entries. If these entries are not found in OID, then run thecreateandldifandsyncmodes ofupsecoidagain.If, however, these entries are already present in OID, then find the instance name that was used for running the
ldifmode and use the same value to run thesyncmode ofupsecoid.Obtain the instance name by looking at the relative distinguished name of the application entry created undercn=Portal, cn=Products, cn=OracleContextnode in OID. Refer to the OID Administrator's Guide for theldapcommand line tools.
Cause: This is an invalid version error in the servlet. For example:
Error: The servlet produced the following error stack. java.lang.Exception: Invalid version, this servlet works with 308 and below at oracle.webdb.page.PageBuilder.process(Unknown Source) at oracle.webdb.page.ParallelServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:244) at javax.servlet.http.HttpServlet.service(HttpServlet.java:336) at...This error will be seen if you are trying to access the Oracle9iAS Portal 9.0.2 or OracleAS Portal 9.0.4 repository from an Oracle Portal 3.0.9 middle-tier. This is not supported.
Action: Upgrade to an OracleAS middle-tier 10g (9.0.4) before attempting to access the OracleAS Portal 9.0.4 repository.
This error can occur if a Oracle9iAS Portal Repository (9.0.2) configured to use Oracle Internet Directory (9.0.4) is upgraded to OracleAS Metadata Repository (9.0.4) and you login as a user that belongs to a private group with no other group memberships.
Cause: While logging in the users group membership information
is retrieved from the Oracle Internet Directory. As this user belongs to
a private group, Portal needs to be a member of the group "cn=Common
Group Attributes,cn=Groups,cn=OracleContext" in order to access the
entry for this private group. The Portal application is missing this privilege
in the Oracle Internet Directory server.
Action: Run ptlasst.csh with -mode
MIDTIER and -type OID, e.g:, ptlasst.csh -mode MIDTIER
-type OID -s portal -sp portal -c dbHostName:1521:dbServiceName -ldap_h
myOIDServer -ldap_p 389 -ldap_w welcome1 -pwd secret123
|
 Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved. |
|