Cause'PER_ADDRESSES_SPT' Index status is failed.
It should be valid.
unpublished bug 4440568 GET TRIGGER ERRORS ENTERING PEOPLE AND LOCATIONS IN HRMS
Reported issue points to a root cause of oracle spatial not being correctly installed on this environment.
Please fix your environment, re-run the index script noted above and recommence your testing.
Solution
To implement the solution, please execute the following steps in your test instance first:
1) ) Run $ORACLE_HOME/md/admin/mdinst.sql from 9iR2 Oracle_home.
connect as system/manager.
2) Forcefully drop the indexes.
connect apps/apps
drop index hr.HR_LOCATIONS_SPT force;
drop index HR.PER_ADDRESSES_SPT force;
3) Delete the entries from sdo_index_metadata_table
connect mdsys/mdsys
delete from sdo_index_metadata_table where sdo_index_name='HR_LOCATIONS_SPT';
delete from sdo_index_metadata_table wheresdo_index_name='PER_ADDRESSES_SPT';
commit;
4) rebuild the indexes.
sqlplus apps/apps @@$PER_TOP/patch/115/sql/irctxloc.sql HR applsys apps CTXSYS
sqlplus apps/apps @@$PER_TOP/patch/115/sql/irctxadr.sql HR applsys apps CTXSYS(
note : HR applsys apps CTXSYS are 4 parameters to the sql)
5) Verify that the index is valid by running
SQL > select DOMIDX_STATUS, DOMIDX_OPSTATUS from dba_indexes whereINDEX_NAME = 'PER_ADDRESSES_SPT';
BUT NONE OF THESE WORKED FOR ME. I DELETED THE INDEXES AND RETESTED THE ISSUE.. THE ISSUE GOT RESOLVED... :)
Share the content if you found it is useful (You can share using 300 community websites) click "share" at the end of the post.
You are encouraged to leave a comment.
You are encouraged to leave a comment.
Thursday, March 05, 2009
HRMS - New Employee creation Errors out ORA-29861
Subscribe to:
Post Comments (Atom)
Let us be Friends...
Popular Posts
-
Primary Node: Host name: genius.chainsys.com IP : 192.168.2.236 File locations: apps - /oracle/D1/apps (SHARED) db - /oracle/PROD/db inst - ...
-
1. Installation of the Demantra Base Application or Patches Create a C:/Tmp folder on the machine where the setup.exe will be executed pri...
-
This blog describes the process of re-creating an existing Applications Release 12 database instance using the export and import utilities....
-
Secure Sockets Layer (SSL) SSL is a technology that defines the essential functions of mutual authentication, data encryption, and data inte...
-
For Installation of the OBIEE please follow my previous post http://balajiabhi.blogspot.com/2009/07/installation-and-configuration-of-obiee....
-
In a default configuration of Oracle Applications the user validating and sign on is done at the database level. For this purpose the FND_US...
-
Hi, everybody should come across, while during a clone, you might have experienced very poor performance while running txkWfClone.sh profil...
-
Today, I need to blog out my experience with Apex integration with R12 E Business Suite!!! How I did: as follows. As you know how to install...
-
This was a biggest issue we were facing at the point of implementation. We were getting the reports designed in Developer and all are displa...
-
Symptoms: #### <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> < > <...
2 comments:
Dropping and index is not a solution, that is just avoiding the problem. You do not even know what all problem you created by solving this one.
Better check with Oracle before dropping a sedded object be it an index.
It is the same solution, what we have already discussed on OTN too. Please follow the OTN Forum, before commenting on my blog. Dont you know the meaning of recreating the index after dropping? that too with oracle provided script. The script i have mentioned here is being used by all PER patches to recreate or alter indexes. The issue was resolved and our implementation went very well. The issue itself is not pertaining to PER, it is the Oracle Spatial is not installed in your database. Kindly check it and proceed further.
Post a Comment