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
-
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...
-
The Following Error was detected while doing Cloning of DB Tier. The actual Fact was: The server was heavily loaded, so the control file cre...
-
In this Blog, I am going to explain you the way you can get the Translation Synchronization Patch for the Language you license thro OAM. T...
-
Hi, everybody should come across, while during a clone, you might have experienced very poor performance while running txkWfClone.sh profil...
-
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...
-
Symptom: A MultiException has 6 exceptions. They are: 1. java.lang.AssertionError: Cannot export non clusterable object with jndiName:weblo...
-
Happy and Prosperous New Year 2010!!! Today I need to discuss an issue while planning to upgrade my 12.1.1 instance to 12.1.2 using the patc...
-
Primary Node: Host name: genius.chainsys.com IP : 192.168.2.236 File locations: apps - /oracle/D1/apps (SHARED) db - /oracle/PROD/db inst - ...
-
This blog speaks about the Login Page Issue on R12.1.1 instance. Suddenly the login page was throwing an error - 404 /OA_HTML/AppsLogin was ...
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