When crateing index.

Hi,
I get the below error while creating an index on a table. Plz, suggest a solution why this happens and how can I resolve this problem.
ORA-00054: resource busy and acquire with NOWAIT specified
Here is the code for index creation.
create index IND_ACCOUNT_ID on T_BIL_ACCOUNT_SERVICE_BALANCE (account_id);

Other sessions still have open transactions on the table that you are trying to create an index on.
You can check:
DBA_DML_LOCKS to find sessions that still have a DML-lock on that table.
or,
V$transaction to find open transactions (use ADDR field to join to v$session.TADDR to find the session).
Edited by: Toon Koppelaars on Jun 29, 2009 12:44 PM
Added TADDR...

Similar Messages

Can't select "include book documents" when creating index in InDesign CC

I'm trying to make an index for several dokuments in a book. I've made the index but when I try to generate the index the checkbox is greyed out so I can't check it. Do You know what's wrong?

Thank You. That worked well.
One more question: It looks as if the index does not include the words of all the documents in the book. Is it something I do wrong?
Thanks
Henning
Fra: Peter Spier <[email protected]<mailto:[email protected]>>
Svar til: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Dato: onsdag 10. juli 2013 13:04
Til: Henning Kristoffersen <[email protected]<mailto:[email protected]>>
Emne: Can't select "include book documents" when creating index in InDesign CC
Re: Can't select "include book documents" when creating index in InDesign CC
created by Peter Spier<http://forums.adobe.com/people/P+Spier> in InDesign - View the full discussion<http://forums.adobe.com/message/5491834#5491834

Error Indexing not allowed when marking indexing for document HR_DOC

Hello all,
We are able to solve the first problem. Now we have the following error
"Error Indexing not allowed when marking indexing for document HR_DOC"
Has anyone idea on how to solve it?
Thanks a lot.
Best regards,

....and thanks a lot for your feedback in resolving this issue!

What happens inside ...... when fired Index Reorganize

Hi all,
what happens inside ...... when fired Index Reorganize
Thanks
vijay

Logical scan fragmentation is removed (where possible). This can improve performance of certain queries, because it reduces the amount of big disk head movements need to go through all the pages.
In addition to that, it brings the amount of unused space in line with the original fill factor of the index. If you haven't specified any fill factor when the index was first created, then all unused space will be removed (where possible). It does this
by joining the rows of multiple pages onto fewer pages and releasing the empty pages. This can improve performance of many queries, since fewer I/O and less memory is now needed to access the same amount of row data.
When the command runs, it will lock just one or a few pages at a time. This way, most blocking is avoided, and any blocking that does occur will be short lived.
This also means that the reorganization occurs inline, within the pages and extents that are already allocated for the specific index. This is one of the big differences with Reindexing, where new pages (and extents) are allocated.
Gert-Jan

When do indexes become invalid?

When do indexes become invalide?

Indexes can become invalid or unusable whenever a DBA tasks shifts the ROWID values, thereby requiring an index rebuild. These DBA tasks that shift table ROWID's include:
Table partition maintenance - Alter commands (move, split or truncate partition) will shift ROWID's, making the index invalid and unusable.
CTAS maintenance - Table reorganization with "alter table move" or an online table reorganization (using the dbms_redefinition package) will shift ROWIDs, creating unusable indexes.
Oracle imports - An Oracle import (imp utility) with the skip_unusable_indexes=y parameter
SQL*Loader (sqlldr utility) - Using direct path loads (e.g. skip_index_maintenance) will cause invalid and unusable indexes.
Cheers

When rebuild indexes

Hi there are indexes in the system.
But When I query
select lf_rows,del_lf_rows
from index_stats;
no row is returned.
How can I know whether the ındexes need to rebuıld?

> Having said that, there is almost never a need to
re-build indexes, and of all the factors claimed to
be an indicator for when an index needs to be
re-built, the ratio of deleted leaf rows is the least
useful.
Actually, I am going to disagree with you. That particular ratio (leaf rows versus deleted leaf rows) is extremely useful as at least one indicator of when an index might truly benefit from a rebuild -but only if measured over a period of time (weeks) and stays at or over about 40% persistently throughout that period. The nonsense factor arises from the fact that people use it as an instantaneous measure and panic when it reaches quite low levels (I seem to recall the Oracle University Performance Tuning course material for 9i mentioning 15% at one point -though it also mentioned 20% elsewhere in the same chapter, so the source of the panic is not hard to pin down!)
Of course, constantly validating the structure of an index merely to prove it's a rare nutcase of an index that genuinely would benefit from a rebuild is not a trivial exercise in the first place, so one might well pause for thought before even attempting it: is this particular index even likely to get close to the 40% threshold? If not, don't bother validating it in the first place.
And yes, there are other measures you should be looking at to determine if your index really needs rebuilding (average space in the blocks of the index, for example, dropping very low and, again, over a period of time, staying that way).
But it's not right to completely dismiss a particular measure just because it has been abused to high heaven in the past!

Error when creating index with parallel option on very large table

I am getting a
"7:15:52 AM ORA-00600: internal error code, arguments: [kxfqupp_bad_cvl], [7940], [6], [0], [], [], [], []"
error when creating an index with parallel option. Which is strange because this has not been a problem until now. We just hit 60 million rows in a 45 column table, and I wonder if we've hit a bug.
Version 10.2.0.4
O/S Linux
As a test I removed the parallel option and several of the indexes were created with no problem, but many still threw the same error... Strange. Do I need a patch update of some kind?

This is most certainly a bug.
From metalink it looks like bug 4695511 - fixed in 10.2.0.4.1

Multiple objects with same name when rebuilding index online

I am looking for advice on how to handle a race-condition in sql server, related to reading metadata while an online index rebuild is being performed.
The problem is as follows:
At some point we execute the following statement:
SELECT
obj.object_id AS id,
scm.name AS scm,
obj.name AS name,
obj.type AS type,
ds.name AS dataspace_name,
prop.value AS description,
part.data_compression_desc as compression_desc
FROM sys.objects AS obj
INNER JOIN sys.schemas AS scm ON obj.schema_id = scm.schema_id
INNER JOIN sys.indexes AS idx ON obj.object_id = idx.object_id AND idx.type IN (0,1)
INNER JOIN sys.data_spaces AS ds ON idx.data_space_id = ds.data_space_id
INNER JOIN (SELECT object_id, data_compression_desc FROM sys.partitions WHERE index_id IN (0,1) /*Heap, Clustered*/) AS part ON part.object_id = obj.object_id
LEFT OUTER JOIN sys.extended_properties AS prop ON obj.object_id = prop.major_id AND prop.minor_id = 0 AND prop.class = 1 AND prop.name = 'Description'
WHERE obj.type = 'U' OR obj.type = 'S'";
The statement returns some metadata for indexes (indices?), the purpose of wich is not the subject.
When executed while an online index rebuild is running, a race condition occurs: When the rebuilding enters the final phase, the new index, which have the same name, becomes visible and thus results in two rows with the same name (from sys.object). I am unaware
if this only occurs for clustered index (which is what we have observed).
We became aware of this behaviour, as we added the metadata to a .Net Dictionary using name as key, and received a duplicate key exception. We have, hoewever, not been able to reproduce the situation, due to the nature of the race condition, and we found very
little documentation on the subject.
What we would like to do now, is to differentiate between the two. We see two options:
1) We could just use the first of the rows and ignore the second. This solution would require that the metadata for both rows are identical.
2) We could discern the "real" index from the "rebuilding" index. This requires some kind of extension of the Where-part.
We have not been able to determine if the requirements for either option is present, as we havent found any documentation, nor have we been able to test for differences, as we cannot reproduce the situation.
We would also like some way of reproducing the situation, so ideas as to how to do that is welcome.
Can anyone direct me to relevant documentation, or alternate solutions.
HRP

1. Use the index with the lower fragmentation to identify the newly rebuilt index (as it almost always will have lower fragmentation)
2. To reproduce, block the online index rebuild process by trying to alter the table's definition in a transaction (and don't commit, which will place schema lock on the table)
Satish Kartan http://www.sqlfood.com/

InDesign CS5.5 crashes when generating index

Hello everyone. I have been working on a 232 page catalog and have been indexing as I've went along. The catalog itself (232 pages) is a book file. When I generated the index before it seemed to take a long time, but it always got through it and had no problems. One day, randomly, it decided it wasn't going to work anymore and crashes when I re-generate the index.
I have tried to add documents at sections at a time to see if it might be a particular file, but my tests have all been inconclusive. I have the catalog separated into 8 sections (32 pages each) I added 1, 2, 3, 4, and 5 generating the index after each addition. I got to section five and it was still okay. When I added section 6 it crashed. I tried generating section 6 by itself and it was fine. Then I generated sections 1-5, and 7 together and it still crashed! I've done every possible combination of index generating and I'm getting desparate. I really do not want to have all my indexing work on the entire back section of the catalog to be wasted.
Is anyone having a similar problem? If I could get it narrowed down to one section, it would help greatly. I do have x refs in my documents but they are all contained within section 4 (which had no problems generating).
I'm assuming the problem lies within section 6 or 7, but I generated them together by themselves and the index generated without a problem.

My InDesign crashed a couple of months for no apparent reason and, whenever I tried to resume the same activity as I was doing when it crashed, it crashed again! I wasn't creating an index but adding photos. Bascially, what I had to do was copy and paste all of my data into a new document. That worked. It was a pain, because I had to copy the master pages, style sheets, blah, blah but it worked. I think what happens is that files get corrupted if they keep crashing. You're better off just grabbing the data and creating a new doc. A pain, I know but....
Good luck! I am just now getting into Indexes, btw.

SOAP Error When Referencing Indexed Picklist Fields

You may receive the following error, or something similar, when trying to access the "Indexed Picklist" fields via webservices.
<siebelf:errormsg>Method 'SetFieldValue' of business component 'Opportunity Copy No Sales Process' (integration component 'Opportunity') for record with search specification '[Name] = "Hay man"' returned the following error:"The value entered in field Indexed Pick 1 of buscomp Opportunity Copy No Sales Process does not match any value in the bounded pick list Occam Indexed Custom Opty 1.(SBL-DAT-00225)"(SBL-EAI-04375)</siebelf:errormsg>
This error can be caused by searching for a picklist value that doesn't exist. In many cases, the picklist values are valid, but the developer is accessing the wrong picklist. This is a common mistake because the user interface, and WSDL files are a little different. Indexed Picklist 1 in the user interface is really IndexedPick0 in the WSDL definition file, not IndexedPick1 like many people would think.
Indexed Picklist 1 = IndexedPick0
Indexed Picklist 2 = IndexedPick1
Indexed Picklist 3 = IndexedPick2
Indexed Picklist 4 = IndexedPick3
Indexed Picklist 5 = IndexedPick4
Indexed Picklist 6 = IndexedPick5
Below are the tests I ran when testing this issue, both SOAP requests and responses.
==========================================================================================================================================
The value "Will" is a valid value for the indexed picklist 1 in the admin screen.... I receive the error because I should be looking in IndexedPick0, not IndexedPick1.
<?xml version="1.0" encoding="UTF-8" standalone="no"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body>
<OpportunityWS_OpportunityUpdate_Input xmlns="urn:crmondemand/ws/opportunity/10/2004">
<ListOfOpportunity>
<Opportunity>
<OpportunityName>Hay man</OpportunityName>
<IndexedPick1>Will</IndexedPick1>
</Opportunity>
</ListOfOpportunity>
</OpportunityWS_OpportunityUpdate_Input>
</soap:Body>
</soap:Envelope>
<?xml version="1.0" encoding="UTF-8" ?>
- <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <SOAP-ENV:Body>
- <SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>Method 'SetFieldValue' of business component 'Opportunity Copy No Sales Process' (integration component 'Opportunity') for record with search specification '[Name] = "Hay man"' returned the following error:"The value entered in field Indexed Pick 1 of buscomp Opportunity Copy No Sales Process does not match any value in the bounded pick list Occam Indexed Custom Opty 1.(SBL-DAT-00225)"(SBL-EAI-04375)</faultstring>
- <detail>
- <siebelf:errorstack xmlns:siebelf="http://www.siebel.com/ws/fault">
- <siebelf:error>
<siebelf:errorsymbol />
<siebelf:errormsg>Method 'SetFieldValue' of business component 'Opportunity Copy No Sales Process' (integration component 'Opportunity') for record with search specification '[Name] = "Hay man"' returned the following error:"The value entered in field Indexed Pick 1 of buscomp Opportunity Copy No Sales Process does not match any value in the bounded pick list Occam Indexed Custom Opty 1.(SBL-DAT-00225)"(SBL-EAI-04375)</siebelf:errormsg>
</siebelf:error>
</siebelf:errorstack>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
==========================================================================================================================================
Correct example and good response.
<?xml version="1.0" encoding="UTF-8" standalone="no"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body>
<OpportunityWS_OpportunityUpdate_Input xmlns="urn:crmondemand/ws/opportunity/10/2004">
<ListOfOpportunity>
<Opportunity>
<OpportunityName>Hay man</OpportunityName>
<IndexedPick0>Will</IndexedPick0>
</Opportunity>
</ListOfOpportunity>
</OpportunityWS_OpportunityUpdate_Input>
</soap:Body>
</soap:Envelope>
<?xml version="1.0" encoding="UTF-8" ?>
- <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <SOAP-ENV:Body>
- <ns:OpportunityWS_OpportunityUpdate_Output xmlns:ns="urn:crmondemand/ws/opportunity/10/2004">
- <ListOfOpportunity xmlns="urn:/crmondemand/xml/opportunity">
- <Opportunity>
<OpportunityId>1-UVW382</OpportunityId>
<AccountId>1-SILNWP</AccountId>
<CreatedDate>12/07/2006 08:58:52</CreatedDate>
<CreatedBy>Will Braithwaite, 12/07/2006 08:58:52</CreatedBy>
<ExternalSystemId />
<IntegrationId>1-UVW382</IntegrationId>
<ModifiedDate>07/13/2007 09:45:56</ModifiedDate>
<ModifiedById>1-S79WT5</ModifiedById>
<ModifiedBy>Will Braithwaite, 07/13/2007 09:45:56</ModifiedBy>
<CreatedById>1-S79WT5</CreatedById>
</Opportunity>
</ListOfOpportunity>
</ns:OpportunityWS_OpportunityUpdate_Output>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Post Author: ayla1209
CA Forum: Data Connectivity and SQL
I'm having the same error - did you ever get a solution?

Query takes 5 min when using Indexes and 1 Second without Indexes !!

Hi,
We have been using indexes on all tables until recently when we faced problems with queries like the one below:
SELECT a.std_id FROM students a, student_degree b, student_course c, course d
WHERE b.std_id = a.std_id
AND c.std_id = a.std_id
AND d.crn = c.crn
AND b.in_progress = 'Y'
AND b.major_code = 'ABTC'
AND a.program_code = 'DP'
AND a.level_code = 'S2'
AND a.campus_code = '05'
AND a.termcode = '200702';
This query takes more than 5 minutes to return a result, but as soon as we remove indexes on the columns termcode and campus_code,it shows result in 1 second.
What could be the problem ?, Is there an attribute that need to be set when creating these indexes ?
Thanks in advance
Madani

Thank you Karthik for your reply.Here are the explain plan report (as shown on Oracle 9i Enterprise Manager)
*1-Explain plan without Indexes:*
Execution Steps:
Step # Step Name
11 SELECT STATEMENT
10 MERGE JOIN
7 SORT [JOIN]
6 NESTED LOOPS
4 NESTED LOOPS
1 ERMS.STUDENT_DEGREE TABLE ACCESS [FULL]
3 ERMS.STUDENTS TABLE ACCESS [BY INDEX ROWID]
2 ERMS.SYS_C006642 INDEX [UNIQUE SCAN]
5 ERMS.SYS_C007065 INDEX [RANGE SCAN]
9 SORT [JOIN]
8 ERMS.COURSE TABLE ACCESS [FULL]
Step # Description
1 This plan step retrieves all rows from table STUDENT_DEGREE.
2 This plan step retrieves a single ROWID from the B*-tree index SYS_C006642.
3 This plan step retrieves rows from table STUDENTS through ROWID(s) returned by an index.
4 This plan step joins two sets of rows by iterating over the driving, or outer, row set (the first child of the join) and, for each row, carrying out the steps of the inner row set (the second child). Corresponding pairs of rows are tested against the join condition specified in the query's WHERE clause.
5 This plan step retrieves one or more ROWIDs in ascending order by scanning the B*-tree index SYS_C007065.
6 This plan step joins two sets of rows by iterating over the driving, or outer, row set (the first child of the join) and, for each row, carrying out the steps of the inner row set (the second child). Corresponding pairs of rows are tested against the join condition specified in the query's WHERE clause.
7 This plan step accepts a row set (its only child) and sorts it in preparation for a merge-join operation.
8 This plan step retrieves all rows from table COURSE.
9 This plan step accepts a row set (its only child) and sorts it in preparation for a merge-join operation.
10 This plan step accepts two sets of rows sorted on the join key. By walking both sets of rows in the order of the join key, every distinct pair of rows satisfying the join condition in the WHERE clause is found through a single pass of the row sets.
11 This plan step designates this statement as a SELECT statement.
*2-Explain plan with Indexes:* (I added index on column campus_code which is a varchar2 column)
Execution Steps:
Step # Step Name
11 SELECT STATEMENT
10 MERGE JOIN
7 SORT [JOIN]
6 NESTED LOOPS
4 NESTED LOOPS
1 ERMS.COURSE TABLE ACCESS [FULL]
3 ERMS.STUDENTS TABLE ACCESS [BY INDEX ROWID]
2 ERMS.INDEX_STUDENTS_CAMPUS_CODE INDEX [RANGE SCAN]
5 ERMS.SYS_C007065 INDEX [RANGE SCAN]
9 SORT [JOIN]
8 ERMS.STUDENT_DEGREE TABLE ACCESS [FULL]
Step # Description
1 This plan step retrieves all rows from table COURSE.
2 This plan step retrieves one or more ROWIDs in ascending order by scanning the B*-tree index INDEX_STUDENTS_CAMPUS_CODE.
3 This plan step retrieves rows from table STUDENTS through ROWID(s) returned by an index.
4 This plan step joins two sets of rows by iterating over the driving, or outer, row set (the first child of the join) and, for each row, carrying out the steps of the inner row set (the second child). Corresponding pairs of rows are tested against the join condition specified in the query's WHERE clause.
5 This plan step retrieves one or more ROWIDs in ascending order by scanning the B*-tree index SYS_C007065.
6 This plan step joins two sets of rows by iterating over the driving, or outer, row set (the first child of the join) and, for each row, carrying out the steps of the inner row set (the second child). Corresponding pairs of rows are tested against the join condition specified in the query's WHERE clause.
7 This plan step accepts a row set (its only child) and sorts it in preparation for a merge-join operation.
8 This plan step retrieves all rows from table STUDENT_DEGREE.
9 This plan step accepts a row set (its only child) and sorts it in preparation for a merge-join operation.
10 This plan step accepts two sets of rows sorted on the join key. By walking both sets of rows in the order of the join key, every distinct pair of rows satisfying the join condition in the WHERE clause is found through a single pass of the row sets.
11 This plan step designates this statement as a SELECT statement.

Error when create index

Hi,
Platform Tru64 BD 8.1.7.
When i create some index for intermedia search, i get some errors:
CREATE TABLE DOCUMENTO (
ID NUMBER (15) NOT NULL,
NOME VARCHAR2 (100) NOT NULL,
DESCRICAO VARCHAR2 (255),
FORMATO VARCHAR2 (128),
AUTOR VARCHAR2 (100),
RESPONSAVEL VARCHAR2 (100) NOT NULL,
DATA_DOCUMENTO DATE,
DATA_CATALOGACAO DATE DEFAULT SYSDATE NOT NULL,
ESTADO VARCHAR2 (2) DEFAULT 'AC' NOT NULL,
DOCUMENTO BLOB,
INTERMEDIA VARCHAR2 (4000),
NAME VARCHAR2 (90),
CRIADO_POR VARCHAR2 (90),
CRIADO_EM DATE,
ALTERADO_POR VARCHAR2 (90),
ALTERADO_EM DATE,
CONSTRAINT ESTADO_CK
CHECK (ESTADO IN ('AC','AN')) ,
CONSTRAINT ID_CONSTRAINTS
UNIQUE (ID),
PRIMARY KEY ( ID ));
CREATE INDEX DOCUMENTO_INDEX ON
DOCUMENTO(DOCUMENTO);
ERROR at line 2:
ORA-02327: cannot create index on expression with datatype LOB
CREATE INDEX INTERMEDIA_INDEX ON
DOCUMENTO(INTERMEDIA);
ERROR at line 2:
ORA-01450: maximum key length (1578) exceeded
Could you give me some help?

Forget last message, i forget to specify index type
Pedro Ribeiro

Oracle Error when creating indexes

Help!! I'm getting an error on a spatial create. I read the documents here on this error and I've tried every suggestion.
1. Plenty of free space in the tablespace indx
2. Plenty of free space in the temp tablespace
Does anyone have any ideas??
Thanx in Advance..
Frank
SQL> CREATE INDEX iseechart_geometry_idx ON iseechart (isee_geometry)
2 INDEXTYPE IS MDSYS.SPATIAL_INDEX
3 PARAMETERS('TABLESPACE=INDX SDO_INDX_DIM=2');
CREATE INDEX iseechart_geometry_idx ON iseechart (isee_geometry)
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13236: internal error in R-tree processing: [failed to cluster in memory]
ORA-13249: Internal error in Spatial index: [mdrcrclmem]
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: at line 1

Hi Frank,
When you specified "sdo_indx_dim" instead of "sdo_indx_dims",
the parser is ignoring the parameter. Since the default
is 2, it still works fine.
Regarding sdo_rtr_override:
Glad that the workaround helped. This is a non-documented parameter
for R-tree that gives a workaround for any possible bugs that
are introduced as part of new features in new releases. Given
the nature of spatial, there could be some data-specific bugs. In 9.2,
there are some new clustering improvements (internal) and guessing
from the error stack the new one is running out of some stack space
internally due to data outliers (does not occur in all datasets though).
The sdo_rtr_override=0 defaults the behavior of the current operation
(create-index or query) to prior releases (like 9.1). This parameter
allows the users to work uninterrupted while things improve in new
releases. The behavior of this parameter should not be used to compare
performance etc. in different versions though and should be used only
as a workaround. (It is not documented due to these implications
and only recommended when needed by spatial).
Spatial will definitely try to improve on the error messages.
Please file a bug with some sample data or send Oracle
the data at the earliest so that this can be fixed properly.
- Ravi.

Mail are make my Mac freeze when Re-indexing

Hi Guys,
After upgrade to Mavericks, I realize that my Mail is not indexing well.
Sometimes I search email, and cannot found.
After browsing, I see in the Apple Websites here :
http://support.apple.com/kb/PH14876
That the Mail should be re-indexing.
I follow the instruction, I have delete file Envelope* in Maildata directory.
After that I open my Mail, and it started to re-indexing.
My email was so huge, it's about 350k email to reindex.
It tooks 4 hours, and when the Mail reindexing mail 320k something, it makes my computer HANGS......
I have leave it for some hours, but still no respond, and the screen still on the last page.....
mouse and everything is not work in this stage.
I have try twice times ,and seems the same situation happen
Need help, how to solve this problem ?????

When you have the problem, note the exact time: hour, minute, second.
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above. Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first. Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. In most cases, a few dozen lines are more than enough. It is never necessary or helpful to post more than about 100 lines. "The more, the better" is not the rule here.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

Error when saving index schedule

Dear Gurus,
this occurs when I try to save a schedule time for an index ID.
system admin > system config > index admin > my index ID > Properties > define schedule
I've created a new cycle(daily), click ok then tried to save but it gives me this error:
Operation failed: AbstractIndex.getSystemList: more than one system id set in index management task queue reader task
what should I do? I need to define a schedule for index time at noon and after office hour(daily).

problem solved, deselect some system ID in the index management task queue reader. after that, able to create schedule for index

When crateing index.

Similar Messages

Maybe you are looking for