10 Oracle Application Server Wireless

10.1.1 Unable to Test Locally Deployed JSPs

Users reported being unable to test local JSPs using the 10.1.2.1 version of the WDK. In order to test locally deployed JSPs, follow these steps:

1. Modify the ORACLE_HOME/j2ee/OC4J_Wireless/applications/wdk/wdk-web/WEB-INF/web.xml file by removing the xml comments (in lines 6 and 31 in this example):

   1.    <!-- For Transcoder -->
   2.   <filter-mapping>
   3.        <filter-name>SdkTranscoder</filter-name>
   4.        <servlet-name>SdkContentRetriever</servlet-name>
   5.    </filter-mapping>
   6. <!--
   7.    <filter-mapping>
   8.        <filter-name>SdkTranscoder</filter-name>
   9.        <url-pattern>*.jsp</url-pattern>
   10.    </filter-mapping>
   11.    <filter-mapping>
   12.        <filter-name>SdkTranscoder</filter-name>
   13.        <url-pattern>*.mxml</url-pattern>
   14.    </filter-mapping>
   15.    <filter-mapping>
   16.        <filter-name>SdkTranscoder</filter-name>
   17.        <url-pattern>*.xhtml</url-pattern>
   18.    </filter-mapping>
   19.    <filter-mapping>
   20.        <filter-name>SdkTranscoder</filter-name>
   21.        <url-pattern>*.html</url-pattern>
   22.    </filter-mapping>
   23.    <filter-mapping>
   24.        <filter-name>SdkTranscoder</filter-name>
   25.        <url-pattern>*.htm</url-pattern>
   26.    </filter-mapping>
   27.    <filter-mapping>
   28.        <filter-name>SdkTranscoder</filter-name>
   29.        <url-pattern>*.xml</url-pattern>
   30.    </filter-mapping>
   31. -->
   
   

2. Restart the OC4J_Wireless process.

10.1.2 EDGE_CREATE Script Errors

Some users have reported receiving an error when trying to create the edge schema on an Oracle Application Server 10g installation. This is because the dbms_aq package is often locked by other sessions when one tries to create the edge user (using the create_edge_user.sql script). When trying to create the edge schema (after connecting as edge/<password>@<db name> and running edg_create_streams.sql), table and queue creation fails.

To fix this problem:

1. Unlock the package. This is a database administrator function. The session locking the package must relinquish the lock. This may require restarting the entire database instance. It ensures that no session is holding a lock on the dbms_aq package.

2. Explicitly give execute privilege to the edge user on the dbma_aq package:

   1. Log in as system.

   2. Execute SQL> grant execute on dbms_aq to edge;

3. Connect as edge/<password>@<db name> and run edg_create_streams.sql, again.

10.1.3 Database Lock Hangs STREAMS Dispatcher

The STREAMS dispatcher runs as a database job. If your PL/SQL development activities require you to constantly recompile packages, a database lock can hang the STREAMS dispatcher. Generally, you can restart the dispatcher by executing:

exec edg_utl.deschedule_job;

To check whether or not the job exits gracefully, check the edg_jobs table. Run the following query:

select component_name, status from edg_jobs;

If the job has exited gracefully, this query will return no rows. If this job is in the process of exiting, the status will be Stopping. It may take up to 30-40 seconds for the job to finish completely. If this query continues to return a status of Stopping, the dispatch job has frozen. To correct this, first clear this row from the table. Execute:

delete from edg_jobs where component_name = 'EdgeDispatchJob';

Next, restart the database. Once the database is restarted, restart (or reschedule) the job. Do this by executing:

exec edg_utl.schedule_job;

The job will restart. To verify, use this query:

select component_name, status from edg_jobs;

This should return a status of Started.

10.1.4 OracleAS Wireless Patch Required after XDK Patch is Applied

If you are using Apache Axis and the wireless feature in Oracle Application Server 10.1.2, and you have already applied a Release 10.1.2 XDK patch, you must download an OracleAS Wireless one-off patch from Metalink.

The OracleAS Wireless one-off patch fixes a problem introduced by the XDK fix. If you do not apply the OracleAS Wireless patch, logging in from the voice channel will fail.

10.1.5 Broken Icons in Wireless Device Portal Homepage

Icons on the OracleAS Wireless Device Portal Home page for an upgraded instance in SSL mode are broken. This is because Mod_rewrite of the icons in an SSL configuration does not work.

To fix the problem, you must enable rewrite in SSL mode by adding the following entries to the SSL Virtual Host configuration:

RewriteEngine on
RewriteOptions inherit

Here is a sample entry:

<VirtualHost _default_:4444>
# General setup for the virtual host
DocumentRoot "/Portal1012/Apache/Apache\htdocs"
@ ServerName iwinrea05.us.oracle.com
ServerAdmin you@your.address
ErrorLog "|/Portal1012/Apache/Apache/bin/rotatelogs logs/error_log 43200"
TransferLog "|/Portal1012/Apache/Apache/bin/rotatelogs logs/access_log 43200"
Port 443

10.1.6 HDML Error When Using Expense Demo Application

A problem has been reported by users running the Expense Demo application on HDML-enabled devices. An error may appear when one attempts to click the Approve or Reject button using an HDML-enabled device to access the built-in Expense Demo application in Device Portal. Users should avoid using the Approve/Reject functionality for this demo when using HDML-enabled devices.

10.2.1 Migrate Account Numbers and PINs after Upgrade

If you upgrade Oracle Application Server Wireless from a previous release (9.0.2.x or 9.0.4.x), you must migrate your user account numbers and PINs to OID. Failure to do so breaks the voice login.

10.2.2 SDO_INDEX_METADATA NULL FETCH Error

If you upgrade Oracle Application Server Wireless from a previous release (9.0.2.x or 9.0.4.x), you must complete the following workaround to avoid the SDO_INDEX_METADATA NULL FETCH error:

1. Connect as SYS.

2. Run the following SQL statement:

   alter session set current_schema=MDSYS;
   update sdo_index_metadata_table set SDO_INDEX_STATUS =
   'VALID' where SDO_INDEX_STATUS is NULL;
   
   update sdo_index_metadata_table set SDO_INDEX_DIMS = 2
   where SDO_INDEX_GEODETIC ='TRUE' and SDO_RTREE_DIMENSIONALITY=3;
   

10.2.3 Updated Transformer Stylesheets Patch Required after Upgrade

If you are upgrading from Release 9.0.2 to Release 10g (9.0.4), and then to Release 10.1.2, you must download the updated transformer stylesheets from the Oracle Mobile Tech Center (http://www.oracle.com/technology/products/iaswe/devices/index.html) and apply the stylesheets to the instance. Detailed instructions are included as part of the transformer stylesheets bundle. If you do not apply this update, service names rendered on the devices will be prefixed with a colon and an underscore (:_).

10.2.4 OracleAS Metadata Repository Creation Assistant 9.2.0.6 Error with Wireless 10.1.2

The OracleAS Metadata Repository Creation Assistant tool may fail to load OracleAS Wireless schemas into 9.0.2.6 databases. To avoid this problem, ensure that you increase the max_enabled_roles parameter to 100 before attempting a RepCA installation with a 9.2.0.6 RAC database.

First, check the current max_enabled_roles parameter value:

1. Connect to the database as sysdba.

2. Issue the command:

   SQL> select name,value from $parameter where name='max_enabled_roles';
   
   

3. If the value is lower than 100, connect to the RAC database as sysdba and issue the following command:

   SQL> alter system set max_enabled_roles=100 scope=spfile;
   
   

4. Restart the database to use the new value.

10.2.5 Configuration Assistant Error Message

You may see Configuration Assistant error messages in ORACLE_HOME/wireless/logs/upgrade_CA.out similar to this:

SQL Exception: java.sql.BatchUpdateException: error occurred during batching: ORA-01430: column being added already exists in table

This message can be safely ignored if your 10.1.2 instance is a fresh instance, that is, it has not been upgraded from 9.0.2, 9.0.4, or any other previous release of Oracle Application Server.

10.2.6 IBM WebSphere Required Patch Version 6.0.2

If you are using IBM WebSphere Application Server, install the following patch: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24009813

Doing so will help you avoid problems when using Oracle Industrial Telnet Server and (potentially) other products.