Following the last post on Troubleshooting during Upgrade Oracle Applications 11i to 10g, in this post I'm going to write about troubleshooting AFTER upgrade Oracle Applications 11i to 10g.
Case 1: ORA-29877: FAILED IN THE EXECUTION OF THE ODCIINDEXPDATE ROUTINE
Symptom:
When trying to save in "Find Service Request" Form, an error message shows up:
ORA-29877: failed in the execution of the ODCIINDEXUPDATE routine ORA-20000: Oracle Text error: DBG-50857: oracle error in textindexmethods. ODCIIndexUpdate ORA-20000: Oracle Text error: DBG-10602: failed to queue DML change to column for in Package CS_ServiceRequest_PVT Procedure Update_ServiceRequest
Cause:
KOREAN_LEXER was deprecated in release 9.0.1 and desupported in release 10.2.0.1. It is replaced by KOREAN_MORPH_LEXER and Oracle Text indexes need to be migrated from the obsolete KOREAN_LEXER to the new KOREAN_MORPH_LEXER. This was not done during the database upgrade.
Solution:
Run the following script as sysdba: sqlplus "/ as sysdba" @$ORACLE_HOME/ctx/sample/script/drkorean.sql
If you get this error (or similar):
$ sqlplus "/as sysdba" @drkorean.sql SQL*Plus: Release 10.2.0.3.0 - Production on … Copyright (c) 1982, 2006, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production With the Partitioning, OLAP and Data Mining options
List of indexes that use KOREAN_LEXER as top level lexer: List of indexes that use KOREAN_LEXER as a sub lexer: "CS"."CS_FORUM_MESSAGES_TL_N4" "CS"."CS_INCIDENTS_ALL_TL_N1" "CS"."CS_KB_SOLN_CAT_TL_N1" "CS"."SUMMARY_CTX_INDEX" "ICX"."ICX_QUES_CTX" Migrate KOREAN_LEXER to KOREAN_MORPH_LEXER Rebuild all indexes that use korean lexer as top level lexer: Reindex all documents that use KOREAN_LEXER as sub lexer reindexing : "CS"."CS_FORUM_MESSAGES_TL" finished. reindexing : "CS"."CS_INCIDENTS_ALL_TL" finished. declare * ERROR at line 1: ORA-29861: domain index is marked LOADING/FAILED/UNUSABLE ORA-06512: at line 316
It is mean that one or more Text indexes are invalid so we have to check which indexes are affected.
Run this query to check which indexes are invalid:
select owner, index_name, index_type, status, domidx_status, domidx_opstatus from dba_indexes where ityp_owner='CTXSYS' order by 1;
select idx_owner, idx_name, idx_type, idx_status from ctxsys.ctx_indexes order by 1;
Drop the affected indexes (e.g. drop index cs.CS_KB_SOLN_CAT_TL_N1 force;)
Recreate dropped indexes as described in Metalink Note 312640.1 - Oracle Text: Re-installation of Applications 11i (11.5.10) Oracle Text Indexes Section 2: Create the CS Text index preferences and indexes (7, 8, 9, 10 & 11)
Rerun script $ORACLE_HOME/ctx/sample/script/drkorean.sql to complete the lexer conversion.
Case 2: FRM-40735: ON-ERROR TRIGGER ORA-01001 FRM-42100 WHEN SEARCHING PARTIALLY PEOPLE
Symptom:
In Users form, when trying to query by person field like ‘%name%’ an error message shows up:
FRM-40735: ON-ERROR TRIGGER RAISED UNHANDLED EXCEPTION ORA-01001
At alert_SID.log: ORA-07445: exception encountered: core dump [qerixGetKey()+562] [SIGSEGV] [Address not mapped to object] [0x10] [] []
Cause:
Initialization parameters didn’t set properly for 10g.
Solution:
Add the follwing to initSID.ora file: _b_tree_bitmap_plans = FALSE
For additional information see note 216205.1 - Database Initialization Parameters for Oracle Applications 11i
Case 3: Error in iAS Cache: java.io.NotSerializableException: oracle.apps.qot.util.LookupValuesKey
Symptom:
When trying to access the Quote tab from sales online, an error message is returned:
Error in iAS Cache: java.io.NotSerializableException: oracle.apps.qot.util.LookupValuesKey
Restart Apache resolve the issue for a short time but after some clicks it’s happens again.
Solution:
Should apply patch 6024690. Note 422499.1 - LookupValuesKey Error Accessing Quote Tab
Case 4: Oracle Forms Web CGI: Error detected
Symptom:
After login to applications and choose a responsibility, just before java applet startup, an error message shows up:
Oracle Forms Web CGI: Error detected Your request cannot be serviced at this time due to the following error: ERROR: URL Contains One or More Restricted Characters
Solution:
1) Comment out the value FORMS60_BLOCK_URL_CHARACTERS in apps.conf. 2) Bounce Apache.
Follow Note:395628.1 - 11.5.10 Error: URL Contains One Or More Restricted Characters
You are welcom to leave a comment...
Aviad |
1 comments:
Hi Aviad,
Thanks for ur info. we fixed some of our issues using ur blog. ITs really very helpful for us.
Thanks
Bhaskar Ivaturi.
Post a Comment