Error while rebuilding a text index

I am on Oracle 10.2.0.3 and HP UNIX 11i. I am rebuilding a text index (textidx1) online
using:
Alter index rebuild textidx1;
If I do a query so index is used, I get:
ORA-29861: domain index is marked LOADING/FAILED/UNUSABLE
Error goes away after index is completely rebuilt.
Since I am rebuilding index online, this error should not occur, otherwise what
Is the purpose of on line index rebuild? Can someone explain how to get rid
Of the error. I cannot stop my application while rebuilding text indexes.

With text indexes if one adds the workd online:
alter index X_TEXT_OBJECT_VALUE rebuild online
ERROR at line 1:
ORA-29874: warning in the execution of ODCIINDEXALTER routine
ORA-29960: line 1,
DRG-10595: ALTER INDEX X_TEXT_OBJECT_VALUE failed
DRG-10562: missing alter index parameter
with normal indexes adding online does not give syntax error.

Similar Messages

ERROR while syncing the Text Index

Hi All,
We are facing an issue while syncing the text index on the table, and the error is below,
System error: Plsql job execution is failed with error code -20000 and error message ORA-20000: Oracle Text error: DRG-10017: you must be CTXSYS to do this: SYNC
We have granted the USER with CTXAPP and CTXSYS roles.
We are scheduling the SYNC from the QUARTZ Scheduler and it happens for every 5 Minutes. We are getting this error in ADHOC Basis.
Could anyone help us in solving the issue.
Thanks.

Hi
to be able to run ctx_ddl.sync_index as a database job it is necessary to have explicit grants for ctx_ddl, the inheritance via the role ctxapp does not suffice.
SQL> grant execute on ctxsys.ctx_ddl to <user_submitting_the_job>;
-Edwin

Error while deleting from BIA index

HI EXPERTS GETTING BELOW ERROR PLZ GIVE CLARITY ON THIS:
1.A communication error occured, with the TREX TcpIp
2.Error while deleting from BIA index; reconstruction required
THANKS &REGARDS,
rAMESH,

Dear Ramesh,
Please check the connection with BIA. Please ask the Basis team to check the BW to BIA connection if they maintain it.
YOu can go to rsddbiamon2 and check BIA connection availibility for more details.
If that is right please try redoing the step at which you faced error and it should help.
Please close the question if you have got the answer or solved it.
Regards,
Den

Error while saving Long Texts

Hello
We are using SRM7 Extended classic scenario.
We don't use shopping carts, rather create POs directly in SRM which will be transferred to ECC as per the standard.
Error:
I am getting an error "Error while saving Long Texts" during my PO creation. I get this message in a small pop-up screen. As soon as i click ok or close the pop up screen it kicks me out of the PO creation screen back into the main SRM screen.
When:
During the PO Creation
Any specific situation:
Yes, only for Material POs
This is happening when I am creating the PO with a Material code. I can create free text PO without any issues.
This is a standard message and the message number is 022.
Thaks for the help guys.

Hi,
To confirm can you check commeting "getOADBTransaction().commit();" gives any error message?
If yes then you can try the following option:
Have you checked whether the "/" is changed to "\" in the dbc file?
In the following two entries the slash has to be made as shown below:
APPS_JDBC_URL=jdbc\:oracle\:thin\:@(DESCRIPTION\=(ADDRESS_LIST\=(LOAD_BALANCE\=YES)(FAILOVER\=YES)(ADDRESS\=(PROTOCOL\=tcp)(HOST\=10.100.503.6)(PORT\=1521)))(CONNECT_DATA\=(SERVICE_NAME\=VIS)))
JDBC\:processEscapes=true
Thanks and Regards,
Lacman

Error while synchronizing oracle text.

Hi,
I am getting below error when synchronize oracle text index. I checked in database mentoined index is present in user schema. My database version is oracle 9.2.0.7.
BEGIN ctx_ddl.sync_index ( 'IDX_DEPDOCUMENTOBJECT') END;
ERROR at line 1:
ORA-20000: Oracle Text error:
DRG-50857: oracle error in drekmap (lob write)
ORA-01403: No data found
ORA-06512: at "CTXSYS.DRUE", line 157
ORA-06512: at "CTXSYS.CTX_DDL", line 1328
ORA-06512: at line 1
Pls suggest how i troubleshoot this error message.
Thanks in advance.
Edited by: user8943509 on Mar 16, 2010 5:15 AM

SCOTT@orcl_11g> CREATE USER u1 IDENTIFIED BY u1
2 /
User created.
SCOTT@orcl_11g> GRANT CONNECT, RESOURCE, CTXAPP TO u1
2 /
Grant succeeded.
SCOTT@orcl_11g> GRANT EXECUTE ON CTXSYS.CTX_DDL TO u1
2 /
Grant succeeded.
SCOTT@orcl_11g> CREATE USER u2 IDENTIFIED BY u2
2 /
User created.
SCOTT@orcl_11g> GRANT CONNECT, RESOURCE TO u2
2 /
Grant succeeded.
SCOTT@orcl_11g> CONNECT u1/u1
Connected.
U1@orcl_11g>
U1@orcl_11g> CREATE TABLE u1_tab (u1_col CLOB)
2 /
Table created.
U1@orcl_11g> CREATE INDEX u1_idx
2 ON u1_tab (u1_col)
3 INDEXTYPE IS CTXSYS.CONTEXT
4 /
Index created.
U1@orcl_11g> INSERT INTO u1_tab VALUES ('whatever')
2 /
1 row created.
U1@orcl_11g> COMMIT
2 /
Commit complete.
U1@orcl_11g> CREATE OR REPLACE PROCEDURE u1_proc
2 AS
3 BEGIN
4 ctx_ddl.sync_index ( 'U1.U1_IDX');
5 END u1_proc;
6 /
Procedure created.
U1@orcl_11g> SHOW ERRORS
No errors.
U1@orcl_11g> GRANT EXECUTE ON u1_proc TO u2
2 /
Grant succeeded.
U1@orcl_11g> SELECT * FROM u1_tab
2 WHERE CONTAINS (u1_col, 'whatever') > 0
3 /
no rows selected
U1@orcl_11g> CONNECT u2/u2
Connected.
U2@orcl_11g>
U2@orcl_11g> EXEC u1.u1_proc
PL/SQL procedure successfully completed.
U2@orcl_11g> CONNECT u1/u1
Connected.
U1@orcl_11g>
U1@orcl_11g> SELECT * FROM u1_tab
2 WHERE CONTAINS (u1_col, 'whatever') > 0
3 /
U1_COL
whatever
U1@orcl_11g>

Error while rebuilding InterMedia index

While executing "alter index ABC.SAMPLE_INTERMEDIA_INDEX rebuild online parameters( 'sync memory 45M' );", we encounter the following error:
java.sql.SQLException: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: interMedia Text error:
DRG-50857: oracle error in drekmap (execute insert)
ORA-01562: failed to extend rollback segment number 6
ORA-01650: unable to extend rollback segment RBS06 by 130 in tablespace RBS
My configuration is as follows:
Oracle 8i (8.1.7.3)
SEGMENT TBLSPC INITIAL_EX NEXT_EX MIN_EX MAX_EX STATUS
SYSTEM SYSTEM 57344 57344 2 505 ONLINE
RBS01 RBS 1048576 1048576 40 32765 ONLINE
RBS02 RBS 1048576 1048576 40 32765 ONLINE
RBS03 RBS 1048576 1048576 40 32765 ONLINE
RBS04 RBS 1048576 1048576 40 32765 ONLINE
RBS05 RBS 1048576 1048576 40 32765 ONLINE
RBS06 RBS 1048576 1048576 40 32765 ONLINE
RBS07 RBS 1048576 1048576 40 32765 ONLINE
TBLSPC INITIAL_EX NEXT_EX MIN_EX MAX_EX
RBS 1048576 1048576 40 505
Questions:
1. What is the relationship between the RBS parameters and the operation to rebuild the intermedia index?
2. How do we optimally set up our RBS parameters OR organize the "alter index rebuild" command to not run into such issues?
Thanks in advance.

I would set up a large rollback segment (eg "BIGROLL") and offline all but BIGROLL before doing the rebuild.
Tom Best

Errors while rebuilding InterMedia index

While executing "alter index ABC.SAMPLE_INTERMEDIA_INDEX rebuild online parameters( 'sync memory 45M' );", we encounter the following error:
java.sql.SQLException: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: interMedia Text error:
DRG-50857: oracle error in drekmap (execute insert)
ORA-01562: failed to extend rollback segment number 6
ORA-01650: unable to extend rollback segment RBS06 by 130 in tablespace RBS
My configuration is as follows:
Oracle 8i (8.1.7.3)
SEGMENT TBLSPC INITIAL_EX NEXT_EX MIN_EX MAX_EX STATUS
SYSTEM SYSTEM 57344 57344     2      505 ONLINE
RBS01     RBS 1048576 1048576 40 32765 ONLINE
RBS02     RBS 1048576 1048576 40 32765 ONLINE
RBS03     RBS 1048576 1048576 40 32765 ONLINE
RBS04     RBS 1048576 1048576 40 32765 ONLINE
RBS05 RBS 1048576 1048576 40 32765 ONLINE
RBS06     RBS 1048576 1048576 40 32765 ONLINE
RBS07     RBS 1048576 1048576 40 32765 ONLINE
TBLSPC INITIAL_EX NEXT_EX MIN_EX MAX_EX
RBS 1048576 1048576 40 505
Questions:
1. What is the relationship between the RBS parameters and the operation to rebuild the intermedia index?
2. How do we optimally set up our RBS parameters OR organize the "alter index rebuild" command to not run into such issues?
Thanks in advance.

Please ask this question in the Oracle text (formerly interMedia text) forum.
You will get a quicker, more expert answer there.

Error When Creating OR Rebuilding Oracle Text index using Lexer Keyword

Hi All,
I am getting following error when i creating oracle text index using lexer & stoplist keyword.
Pls Help me if any body know.
Thanks in Advance.
Error starting at line 1 in command:
CREATE INDEX TXT_INX_TEXT_SEARCH ON TEXT_SEARCH (BFILE_DOC)
Post INDEXTYPE IS "CTXSYS"."CONTEXT" LOCAL (
PARTITION "BEFORE_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)') ,
PARTITION "Q1_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q1_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q1_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "THE_REST" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)')
Error at Command Line:1 Column:13
Error report:
SQL Error: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: Oracle Text error:
DRG-11000: invalid keyword LEXER
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 365
29855. 00000 - "error occurred in the execution of ODCIINDEXCREATE routine"
*Cause: Failed to successfully execute the ODCIIndexCreate routine.
*Action: Check to see if the routine has been coded correctly.
Regards,
Jack R.

Hi,
it works if you put an extra PARAMETERS clause at the end so the creation looks like:
CREATE INDEX TXT_INX_TEXT_SEARCH ON TEXT_SEARCH (BFILE_DOC)
INDEXTYPE IS "CTXSYS"."CONTEXT" LOCAL (
PARTITION "BEFORE_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)') ,
PARTITION "Q1_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q1_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q1_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "THE_REST" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)')
PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)') <== Added
Hope this helps
Herald ten Dam

Error while importing a table index.

Hi,
We are facing a problem while importing an index to the production region. Below are the details.
1. A secondary index was created on standard SAP table ILOA in DEV region.
2. The Index was successfully moved to the Quality system, without any glitches.
3. Due to some issue (releated to testing, for which we had to revert back the changes), we had to delete the index on ILOA in the DEV region. The transports were moved to the PPD region and hence, the index on ILOA was deleted in PPD also.
4. Once the issue related to testing was resolved, we again created an index on the table ILOA and moved it to PPD.
All these 4 mentioned steps happened successfully and in PPD there was no error while importing the transports.
But, while moving the above transports to the Production region, there was an error :
"Index ILOA~Y could not be activated
(E - No index ILOA~Y found with status M)"
Please note that Y is the name of the index that was created on the table ILOA.
The error code that we have got is "8".
Can anyone please shed any light on what the issue is?? WE cannot re-import the transports in to Production without analysing this issue,because our client doesnt permit that.
Thanks and eagerly awaiting a kind reply.
Regards,
Raghavendra.

You've three transports - one to create the index, one to delete, and one to recreate. It could be that the the third one tried to run before the database had finished with the second?
Have you looked on SE14 for the actual status on production of the index?
matt

Error in creation of text indexes and synching with user datastore

Hi
has any body encountered error in creating text indexes on 9.2.0.1 with user datastore. you can create them only with no-populate option. however once created after checking-in documents the indexes cannot be synched using ctx_ddl command manually.

The only thing that I have seen similar to this was worked around by updating the column to itself, then sync...not sure if this is the same thing you are running into, but it may be worth a try. See the Oracle Text FAQ - take special note of step c:
===============================
Creates the index without populating it.
SQL > CREATE INDEX GLOBALINDEXEDBLOB_I
ON ODMM_CONTENTSTORE ("GLOBALINDEXEDBLOB" ) INDEXTYPE IS CTXSYS.CONTEXT PARAMETERS (' stoplist CTXSYS.DEFAULT_STOPLIST storage IFS_DEF_STORAGE section group IFS_SECTION_GROUP wordlist IFS_DEF_WORDLIST memory 32000000 filter IFS_DEF_FILTER format column FORMAT charset column CHARACTERSET lexer IFS_GLOBAL_LEXER language column LANGUAGE nopopulate');
b. Mark globalindexedblob column in every row as updated.
SQL > update odmm_contentstore set globalindexedblob = globalindexedblob;
c. Sync the index. If you skipped the previous step, then this step does not index content that existed prior to index creation in step a.
SQL > exec ctx_ddl.sync_index('GLOBA[i]Long postings are being truncated to ~1 kB at this time.

Error while importing a text file for a list of values

Hi Experts,
While importing a text file for a list of values in designer, I am getting error message as below:
"Invalid setting in Excel key of the Engines section of the Windows Registry. (3433)".
I am using BO XI R3. Universe Designer version : 12.1.0.882
Any suggestion ?
Regards

plzzzzzzzzzzzzzzzzz.............sme1 help me out

I am getting ORA-20001: Seed insert error while seed translatable text step

Hi,
I am getting this error while English to Arabic translation in the Seed translatable text step
ORA-20001: Seed insert error: WWV_FLOW_ICON_BAR.ICON_IMAGE_ALT ORA-00001: unique constraint (APEX_030200.WWV_FLOW_TRANSLATABLE_TEXT_PK) violated
Can i get any suggetion from your side.
Thanks,
nar

Did you ever figure this out. Because I also have this error.

Error When Creating Oracle Text index using Lexer Keyword

Hi All,
I am getting following error when i creating oracle text index using lexer & stoplist keyword.
Pls Help me if any body know.
Thanks in Advance.
Error starting at line 1 in command:
CREATE INDEX TXT_INX_TEXT_SEARCH ON TEXT_SEARCH (BFILE_DOC)
Post INDEXTYPE IS "CTXSYS"."CONTEXT" LOCAL (
PARTITION "BEFORE_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)') ,
PARTITION "Q1_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q1_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q1_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "THE_REST" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)')
Error at Command Line:1 Column:13
Error report:
SQL Error: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: Oracle Text error:
DRG-11000: invalid keyword LEXER
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 365
29855. 00000 - "error occurred in the execution of ODCIINDEXCREATE routine"
*Cause: Failed to successfully execute the ODCIIndexCreate routine.
*Action: Check to see if the routine has been coded correctly.
Regards,
Jack R.

Hi,
it works if you put an extra PARAMETERS clause at the end so the creation looks like:
CREATE INDEX TXT_INX_TEXT_SEARCH ON TEXT_SEARCH (BFILE_DOC)
INDEXTYPE IS "CTXSYS"."CONTEXT" LOCAL (
PARTITION "BEFORE_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)') ,
PARTITION "Q1_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2007" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q1_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2008" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q1_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q2_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q3_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "Q4_2009" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)'),
PARTITION "THE_REST" PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)')
PARAMETERS ('LEXER dd_lexer STOPLIST dd_stoplist SYNC (ON COMMIT)') <== Added
Hope this helps
Herald ten Dam

Error while uploading standard text files for the Global rule set

Hi all,
As part of Post Installation Activities we have uploaded standard text files for business process, functions, risks and rule set obtained with the installable Software.
While uploading the text files we have uploaded the Basis Functions Authorizations first and then R/3 text files.
When we checked no actions are appearing in the rule architect under respective functions except for the BASIS Module.
Is this because we have uploaded the Basis functions before the R/3 text files?If yes, how to replace the Basis with the R/3 ones.
We tried to replace the Basis function authorizations by re-uploading the R/3 text files again but we got the below error message u201CORA-00001:unique constraint (SAPSR3DB.SYS_C004479) violatedu201D
Can somebody please help in this regard how to get the standard rule set in our system?
Thanks and Best Regards,
Srihari.K

Hi Sri,
you should upload first the static text files and the authorization objects first and then the GRC standard rule set files following the instructions of the SAP Configuration Guide available in Service Market Place under http://service.sap.com/instguides .
The GRC standard rule set contains files named Basis_functions_action.txt and R3_function_action.txt. The first one contains ONLY function definitions in terms of transcation codes for basis only, whereas the second one contains functions definition for basis AND ERP modules. The same holds for the *_function_permission.txt files. There are also function definition files for other SAP solutions such as APO, CRM, HR etc.
You can open a customer message and request a deletion script for the rule sets files you have uploaded already. After their application of this script all rule set data will be deleted from your database. If you have uploaded static text and authorization files correctly, you can then upload the GRC standard rule set files as needed again.
best regards,
Frank

Error while rebuilding the index

HI
can any one help me with this.
while i am trying to drop and rebuild an index i got the error like...
ORA-01652: unable to extend temp segment by 8091 in tablespace SYSTEM
what have to be done....
Thanks in advance...

user8884944 wrote:
HI
can any one help me with this.
while i am trying to drop and rebuild an index i got the error like...
ORA-01652: unable to extend temp segment by 8091 in tablespace SYSTEM
what have to be done....
Thanks in advance...It wasn't the direct cause of your error, but what were you doing trying to build an index in the SYSTEM tablespace?
As for the error itself
http://lmgtfy.com/?q=ORA-01652

Error while rebuilding a text index

Similar Messages

Maybe you are looking for