Errors and Resolutions

Portal Servlet Error An Unexpected servlet error was encountered

Problem accessing Portal

Error Message:

Servlet Error
An unexpected servlet error was encountered.
Please check the log file for more details.

Midtier_home/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island/Application.log shows ->

05/07/25 21:20:25 portal: [module=PortalServlet, ecid=84136174634,1] ERROR: oracle.webdb.utils.PortalExceptionImpl: Unable to obtain Portal Repository version.

Cause:
This can be caused by changing the Portal schema user password using sqlplus.

Resolution:

1. Change the password from database again using
SQL> alter user portal identified by password
this is so you know the portal schema password.

2. Login to OIDADMIN and enter the password:

i). Navigate to this entry (ENSURE YOU HAVE THE CORRECT ORCLREFERENCENAME if you have multiple Metadata Repository registered)

OrclResourceName=PORTAL,orclReferenceName=asdb1.au.oracle.com,cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext

ii).Change the value of orclpasswordttribute and Enter the Portal schema password as per step 1.

3. Login to EM and change the password

Disco Error: No Response from Application Web Server

Error:

When trying to access Discoverer Plus or Viewer following error message is encountered:

"There was no response from the application web server for the page you requested.
Please notify the site's webmaster and try your request again later. "
Cause:
Not all of the iAS services were started.
Running the /ora_home/opmn/bin/opmnctl status showed the Http server process was down.

Solution:

To implement the solution, please execute the following steps:

1. Start the Http server process using the following command:
opmnctl startproc ias-component=XXXX (where XXXX = HTTP_Server)

2. Test the Viewer and Plus connections they should be working now.

Unable to login: &REASON has been detected in &ROUTINE

On Apps 11.5.10.2 on Production, when any user attempts to login to applications,they receive the following error and are unable to login:

Error:

Oracle error &ERRNO: &REASON has been detected in &ROUTINE.

Cause:

Check if you can access forms via: http://host.domain:port/dev60cgi/f60cgi

This will produce an error message stating which trigger has become invalid.

Solution:

Try to recompile the trigger using:
SQL> alter trigger compile;

If this fails then:
SQL> alter trigger disable;

This should allow users to log into the application once again.
Then investigate the trigger to find out what the problem with it is

Changes:

An event alert had been activated on the FND_USER table

ORA-01658: unable to create INITIAL extent for segment in tablespace WAREHOUSE_DATA

If this error occurs then do the following scripts to check for tablespace free space and to increase the datafile size (if the datafile is small then increase it, otherwise create a new one).

Resolution:

Find out how much free space the tablespace has:
SQL> select tablespace_name, sum(bytes), max(bytes) from dba_free_space group by tablespace_name order by 2;

Find location of datafile:
SQL> select file_name, bytes from dba_data_files where tablespace_name =';

Increase the size of the datafile:
SQL> alter database datafile '' resize 2500M;

Commit the changes:
SQL> commit;

Cannot start up the BI Scheduler - [nQSError: 46029]

Applies to:

Oracle Business Intelligence Applications Foundation - Version: 10.1.3.3.2 to 10.1.3.4
This problem can occur on any platform.

Symptoms

Use the following command to startup BI Scheduler:
$ ./run-sch.sh start

It gives the following output:
$ Oracle BI Scheduler startup initiated.

Execute the following command to check the Oracle BI Scheduler logfile and see if it started.
$ tail -f /mnt/obiee/OracleBI/server/Log/NQScheduler.log

NQScheduler.log gives the following error:
[68008] Scheduler Error: libclntsh.so.10.1: cannot open shared object file: No such file or directory
[nQSError: 46029] Failed to load the DLL /mnt/obiee/OracleBI/server/Bin/libnqsdbgatewayoci10g.so. Check if ‘Oracle OCI 10G’ database client is installed.

Cause

It is unable to reference the libclntsh.so.10.1.

Solution

Update the db.env in the ENV_FILES to have the following line included:
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH:
(where $ORACLE_HOME is the Oracle 10gR2 home)

Starting up BI Scheduler should now give the following message in the NQScheduler.log:
[16020] Metadata Database Type: Oracle 10g R2
Data Source Name: OBIEE
Data Source Type: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Pro
2009-04-02 10:36:08
[68013] Service started.
2009-04-02 10:36:08
Service started.

DBCA (or other GUI's) do not launch when ssh'ing to another server in vnc
When ssh'ing to another server through vnc and requiring the gui interface to open, you need to ssh using the following command to enable X11 forwarding.
$ ssh -X