Issue with index creation of an infocube.

Hi,
I have an issue with creation of index's for a info cube in SAP BI. when i create index's using
a process chain for the cube it is getting failed in the process chain. when i try to check the index's for this
cube manual the following below massage is shown.
*The recalculation can take some time (depending on data volume)*
*The traffic light status is not up to date during this time*
Even i tried to repair the index's using the standard program "SAP_INFOCUBE_INDEXES_REPAIR" in SE38
to repair the index so it is leading to dump in this case.
Dear experts with the above issue please suggest.
Regards,
Prasad.

Hi,
Please check the Performance tab in the Cube manage and try doing a repair index from there.
This generates a job so check the job in SM37 and see if it finishes. If it fails, check the job log which will give you the exact error.
These indices are F fact table indices so if nothing works, try activating the cube by the pgm 'RSDG_CUBE_ACTIVATE' and see if that resolves the issue.
Let us know the results.

Similar Messages

Adobe Bridge issue with index.html files

Hi, I have a perplexing problem.... Three weeks ago, I created a web photo gallery in Bridge. I transferred it to my website via FTP and it worked like a charm. Three days later I created another web gallery transferred it to my website using my ftp and the address of what I uploaded takes me to a blank page. I contacted my web hosting support and was told it looks like an issue with my index.html file. Here is a link to the gallery that is working: www.janieblanchard/com/galleries/prettylights/index.html
Here is the link to the site that is not working:
www.janieblanchard.com/galleries/macrogallery/index.html
Any advice would be so helpful, I've spend too many hours trying different galleries and uploading multiple times.
Thanks!

What exact camera make and model?
What specific, exact version of Adobe Camera Raw (ACR) plug-in?
What specific, exact versions of Bridge and of Yosemite?
BOILERPLATE TEXT:
Note that this is boilerplate text.
If you give complete and detailed information about your setup and the issue at hand,
such as your platform (Mac or Win),
exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
your settings in Photoshop > Preference > Performance
the type of file you were working on,
machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
what troubleshooting steps you have taken so far,
what error message(s) you receive,
if having issues opening raw files also the exact camera make and model that generated them,
if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
etc.,
someone may be able to help you (not necessarily this poster).
a screen shot of your settings or of the image could be very helpful too.
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks!

Issue with PDF creation

Hi,
We have an issue with the PDF file generated using standard SAP program 'RFFOEDI1'. The issue is that special characters for the country 'CZ' are printed as '#' in the PDF.
However, the spool for 'CZ' prints the special characters correctly.
Can any one please let us know why is the program 'RFFOEDI1' not printing special characters for 'CZ' correctly????
Cheers,
Raghav.

Please update to latest Acrobat 9 release which is 9.4.2.
Also do let us know
a) office 2003 flavour: Standard or professional?
b) OS flavour? Also whether it is 32bit or 64bit?
Also as you mentioned that "Not all documents are affected", so we would require any of your affected file to analyze the issue. Can you please share the file? You can use acrobat.com to share the file.
Thanks,
Vishal

Issues with user creation in Oracle 10g

ear All,
After logon to database with sysdba user i created one user by following query:
CREATE USER BI_USER
IDENTIFIED BY VALUES '0CE8A6E883EE4E19'
DEFAULT TABLESPACE BI_USER
TEMPORARY TABLESPACE TEMP1
PROFILE DEFAULT
ACCOUNT UNLOCK;
After creating this i have given following privledges to it:
GRANT RESOURCE TO BI_USER;
GRANT CONNECT TO BI_USER;
GRANT SCHEDULER_ADMIN TO BI_USER;
GRANT DBA TO BI_USER;
GRANT SELECT_CATALOG_ROLE TO BI_USER;
GRANT GLOBAL QUERY REWRITE TO BI_USER;
GRANT ANALYZE ANY TO BI_USER;
GRANT EXECUTE ANY PROCEDURE TO BI_USER;
GRANT CREATE SEQUENCE TO BI_USER;
GRANT CREATE SYNONYM TO BI_USER;
GRANT EXECUTE ANY PROGRAM TO BI_USER;
GRANT SELECT ANY DICTIONARY TO BI_USER;
GRANT DROP ANY VIEW TO BI_USER;
GRANT CREATE DIMENSION TO BI_USER;
GRANT DROP ANY TYPE TO BI_USER;
GRANT CREATE ANY DIRECTORY TO BI_USER;
GRANT ALTER ANY MATERIALIZED VIEW TO BI_USER;
GRANT CREATE MATERIALIZED VIEW TO BI_USER;
GRANT UNLIMITED TABLESPACE TO BI_USER;
BEGIN
SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(
PRIVILEGE => SYS.DBMS_RULE_ADM.EXECUTE_ANY_RULE,
GRANTEE => 'BI_USER',
GRANT_OPTION => FALSE);
END;
GRANT EXECUTE ANY TYPE TO BI_USER;
GRANT CREATE ANY MATERIALIZED VIEW TO BI_USER;
GRANT CREATE TRIGGER TO BI_USER;
GRANT CREATE ANY TABLE TO BI_USER;
GRANT CREATE TABLE TO BI_USER;
BEGIN
SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(
PRIVILEGE => SYS.DBMS_RULE_ADM.EXECUTE_ANY_RULE_SET,
GRANTEE => 'BI_USER',
GRANT_OPTION => FALSE);
END;
GRANT CREATE TYPE TO BI_USER;
GRANT DROP ANY INDEX TO BI_USER;
GRANT SELECT ANY TABLE TO BI_USER;
GRANT CREATE JOB TO BI_USER;
GRANT QUERY REWRITE TO BI_USER;
GRANT CREATE VIEW TO BI_USER;
GRANT CREATE SESSION TO BI_USER;
GRANT EXECUTE ANY CLASS TO BI_USER;
BEGIN
SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(
PRIVILEGE => SYS.DBMS_RULE_ADM.EXECUTE_ANY_EVALUATION_CONTEXT,
GRANTEE => 'BI_USER',
GRANT_OPTION => FALSE);
END;
GRANT CREATE INDEXTYPE TO BI_USER;
GRANT CREATE DATABASE LINK TO BI_USER;
GRANT ALTER SESSION TO BI_USER;
GRANT DROP ANY DIRECTORY TO BI_USER;
GRANT CREATE PROCEDURE TO BI_USER;
GRANT DROP ANY SYNONYM TO BI_USER;
GRANT DROP ANY TABLE TO BI_USER;
Now following are the issues i am facing:
1). After all this when i logon to this user through toad it is successful but through SQL it says invalid username and password
2). Whenever i create a table it is created in SYS schema not in the user schema for creating it in user schema i have to right username.tablename also in select statement.
Can any body help me in this.

2). Whenever i create a table it is created in SYS schema not in the user schema for creating it in user schema i have to right username.tablename also in select statement.
<code>
sqlplus scott/tiger
Connected.
SQL> desc t
Name Null? Type
TESTCOL VARCHAR2(10)
SQL> select * from t;
TESTCOL
1
2
3 new
SQL> conn / as sysdba
Connected.
SQL> sho user
USER is "SYS"
SQL> select * from scott.t
2 ;
TESTCOL
1
2
3 new
SQL> create table scott.t_copy as select * from scott.t;
Table created.
SQL> conn scott/tiger
Connected.
SQL> select * from t_copy;
TESTCOL
1
2
3 new
<code>
1). After all this when i logon to this user through toad it is successful
but through SQL it says invalid username and password
<code>
$ echo $ORACLE_SID
orcl
$ tnsping orcl
TNS Ping Utility for Linux: Version 10.2.0.2.0 - Production on 27-AUG-2009 14:38:34
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
/home/oracle/oracle/product/10.2.0/db_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl)))
OK
$ sqlplus scott/tiger
SQL*Plus: Release 10.2.0.2.0 - Production on Thu Aug 27 14:38:42 2009
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> sho user
USER is "SCOTT"
SQL> select * from t_copy;
TESTCOL
1
2
3 new
<code>
please tell the syntax how you connect through sqlplus

Issue with index on table

Hi,
We have created an index(assume z2) on table CATSDB with 2 fields. There is an other index(Z1 assume) with the same fields and the order is also same. When a report accesing the table it is taking more time to run when index Z2 is on table. But when deleted then the report ran quickly. Is it with the duplicate index created???
Please let me know
Regards
Shiva

Hi
i am giving total index and buffering concept details by seeing this you can understand how we can achive performance through these
reward if usefull
Performance during table access
Indexes
Primary and secondary indexes
Structure of an index
Accessing tables using indexes
Table buffering
Advantages of buffering
Concept of buffering
Buffering types
Buffer synchronization
Primary and secondary indexes
Index: Technical key of a database table.
Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
Structure of an Index
An index can be used to speed up the selection of data records from a table.
An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
When creating indexes, please note that:
An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
Only those fields whose values significantly restrict the amount of data are meaningful in an index.
When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
Make sure that the indexes on a table are as disjunctive as possible.
(That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
Accessing tables using Indexes
The database optimizer decides which index on the table should be used by the database to access data records.
You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated
Database access using Buffer concept
Buffering allows you to access data quicker by letting you
access it from the application server instead of the database.
Advantages of buffering
Table buffering increases the performance when the records of the table are read.
As records of a buffered table are read directly from the local buffer of the application server on which the accessing transaction is running, time required to access data is greatly reduced. The access improves by a factor of 10 to 100 depending on the structure of the table and on the exact system configuration.
If the storage requirements in the buffer increase due to further data, the data that has not been accessed for the longest time is displaced. This displacement takes place asynchronously at certain times which are defined dynamically based on the buffer accesses. Data is only displaced if the free space in the buffer is less than a predefined value or the quality of the access is not satisfactory at this time.
Entering $TAB in the command field resets the table buffers on the corresponding application server. Only use this command if there are inconsistencies in the buffer. In large systems, it can take several hours to fill the buffers. The performance is considerably reduced during this time.
Concept of buffering
The R/3 System manages and synchronizes the buffers on the individual application servers. If an application program accesses data of a table, the database interfaces determines whether this data lies in the buffer of the application server. If this is the case, the data is read directly from the buffer. If the data is not in the buffer of the application server, it is read from the database and loaded into the buffer. The buffer can therefore satisfy the next access to this data.
The buffering type determines which records of the table are loaded into the buffer of the application server when a record of the table is accessed. There are three different buffering types.
With full buffering, all the table records are loaded into the buffer when one record of the table is accessed.
With generic buffering, all the records whose left-justified part of the key is the same are loaded into the buffer when a table record is accessed.
With single-record buffering, only the record that was accessed is loaded into the buffer.
Buffering types
With full buffering, the table is either completely or not at all in the buffer. When a record of the table is accessed, all the records of the table are loaded into the buffer.
When you decide whether a table should be fully buffered, you must take the table size, the number of read accesses and the number of write accesses into consideration. The smaller the table is, the more frequently it is read and the less frequently it is written, the better it is to fully buffer the table.
Full buffering is also advisable for tables having frequent accesses to records that do not exist. Since all the records of the table reside in the buffer, it is already clear in the buffer whether or not a record exists.
The data records are stored in the buffer sorted by table key. When you access the data with SELECT, only fields up to the last specified key field can be used for the access. The left-justified part of the key should therefore be as large as possible for such accesses. For example, if the first key field is not defined, the entire table is scanned in the buffer. Under these circumstances, a direct access to the database could be more efficient if there is a suitable secondary index there.
With generic buffering, all the records whose generic key fields agree with this record are loaded into the buffer when one record of the table is accessed. The generic key is a left-justified part of the primary key of the table that must be defined when the buffering type is selected. The generic key should be selected so that the generic areas are not too small, which would result in too many generic areas. If there are only a few records for each generic area, full buffering is usually preferable for the table. If you choose too large a generic key, too much data will be invalidated if there are changes to table entries, which would have a negative effect on the performance.
A table should be generically buffered if only certain generic areas of the table are usually needed for processing.
Client-dependent, fully buffered tables are automatically generically buffered. The client field is the generic key. It is assumed that not all of the clients are being processed at the same time on one application server. Language-dependent tables are a further example of generic buffering. The generic key includes all the key fields up to and including the language field.
The generic areas are managed in the buffer as independent objects. The generic areas are managed analogously to fully buffered tables. You should therefore also read the information about full buffering.
Single-record buffering is recommended particularly for large tables in which only a few records are accessed repeatedly with SELECT SINGLE. All the accesses to the table that do not use SELECT SINGLE bypass the buffer and directly access the database.
If you access a record that was not yet buffered using SELECT SINGLE, there is a database access to load the record. If the table does not contain a record with the specified key, this record is recorded in the buffer as non-existent. This prevents a further database access if you make another access with the same key
You only need one database access to load a table with full buffering, but you need several database accesses with single-record buffering. Full buffering is therefore generally preferable for small tables that are frequently accessed.
Synchronizing local buffers
The table buffers reside locally on each application server in the system. However, this makes it necessary for the buffer administration to transfer all changes made to buffered objects to all the application servers of the system.
If a buffered table is modified, it is updated synchronously in the buffer of the application server from which the change was made. The buffers of the whole network, that is, the buffers of all the other application servers, are synchronized with an asynchronous procedure.
Entries are written in a central database table (DDLOG) after each table modification that could be buffered. Each application server reads these entries at fixed time intervals.
If entries are found that show a change to the data buffered by this server, this data is invalidated. If this data is accessed again, it is read directly from the database. In such an access, the table can then be loaded to the buffer again.

Issue with User Creation in AS ABAP

Hi Experts,
We are implementing IDM 7.2 SP8. We have successfully performed initial load from CRM systems and also created Business Roles in CRM containing privelleges from CRM system. We can successfully assign roles from IDM to users in CRM for users loaded in IDM after initial load.
However, we are not able to create users in CRM backend system. Please find below details on the same:
Creating user from IDM UI and also assigning role:
1) We try to create user using the standard SAP Provisioning Task - "Display Identity". We maintain the user details like - first name, last name, validity etc and also the
2) We select the Business Role to be assigned to user and click on save. Workflow is triggered for the same and after approval from role owner, the correspodning tasks get executed.
3) The user gets created in IDM UI and also the desired role is assigned to user. However, no changes occur in backend CRM system.
4) Job logs and found that the job "SETABAPROLES&PROFILESFORUSER"(from standard sap framework) fails with error -
putNextEntry failed storing
Exception from Modify operation:com.sap.idm.ic.ToPassException: User 1 does not exist
Creating User from IDM UI without assigning any role:
1) We create a user using "Create Identity Task", maintain the attribute "ACCOUNT<repository name>" for the user, maintain the validity dates and click on save.
2) User is created in IDM UI but nothing happens in backend CRM system.
I followed thread 3331868 and understand that "Account Privilege PRIV:<Repository>:ONLY" should be assigned to user for creation in backend system. However, i am not able to find the privellege in IDM UI for assignment while user creation.
Kindly help me with steps on how to assign this privelege while creation of new user in IDM UI so that user can be created in backend system.
Thanks and regards,
Nitin

The repository:ONLY privilege should be created when you do the initial load if you use one of the SAP templates. If not, you can manually create it.
On the repository, set the master privilege to be SAP:repository:ONLY (note, it can be anything but changing it would make life hard for anyone following you).
Create a task called 'Assign Master Privilege' which has:
MSKEYVALUE %mskeyvalue%
MXREF_MX_PRIVILEGE PRIV:$rep.$Name:ONLY
Ensure that the repository is set to 'inherited'
Assign your new task as the 'No Master Task' on all repositories.
When a user gets a privilege in a back end system, it will check to see if they have an 'ONLY' priv for that repository. If not, it triggers the 'No Master Task' which assigns it and then it will assign the backend privilege.
Peter

Performance issue with Indexing

Our users are experiencing the performance problem using Oracle 8.1.7 database. We are using Business object to display the data as required.
This is the below script using BO.
Can you please suggest me technically how to get resolved this issue?
Please let me know if you need any more information.
Thanks
 This is an example of the typical type of query I use, it works o.k. but I think some indexing could make it run much quicker.
I think the TEST.SH_TYS____COMPL.CLOSED_TIME & TEST.SH_TYS____COMPL.CANCELLED_TIME are key fields that could be indexed to speed up the report.
Also I tend to do a lot of reports using the TEST.TYS__COMPL_CONFIGURATION.OWNING_CENTRE as a filter, this isn't that large a table but
uses a table join on TEST.TYS____COMPL.CID = TEST.TYS__COMPL_CONFIGURATION.CID so indexing the TEST.TYS____COMPL.CID field could
provide an improvement.
The TEST.TYS____COMPL.CREATE_DATE is another key field when we want to identify tickets raised during a period.
The TEST.TYS____COMPL.SUBCASE_OF is another key field we filter by.
The TEST.TYS____COMPL.CLEAR_CODE_OBJECT_FAMILY,TEST.TYS____COMPL.CLEAR_CODE_OBJECT & TEST.TYS____COMPL.CLEAR_CODE_ACTION fields may also be useful.
 SELECT TEST.TYS____COMPL.COMPL_ID, TEST.TYS____COMPL.STATUS, TEST.TYS____COMPL.MODIFIED_DATE,
TEST.TYS____COMPL.CREATE_DATE, TEST.TYS____COMPL.SUBMITTER, TEST.TYS____COMPL.LAST_MODIFIED_BY,
TEST.TYS____COMPL.COMPL_ENQUIRY_DESCRIPTION, TEST.TYS____COMPL.COMPL_CLEAR_TARGET_TIME,
TEST.TYS____COMPL.CURRENT_ACTION, TEST.TYS____COMPL.RESTORE_UNITS, TEST.TYS____COMPL.CID,
TEST.TYS____COMPL.ELEMENT_ID, TEST.TYS____COMPL.SITE_LOCATION_ID, TEST.TYS____COMPL.SITE,
TEST.TYS____COMPL.PROACTIVITY, TEST.TYS____COMPL.INCIDENT_START_TIME,
TEST.TYS____COMPL.TOTAL_OUTAGE_TIME__SECS_, TEST.TYS____COMPL.TOTAL_TICKET_TIME__SECS_,
TEST.TYS____COMPL.TOTAL_COMPL_TIME__SECS_, TEST.TYS____COMPL.SEVERITY, TEST.TYS____COMPL.BACKUP_METHOD,
TEST.TYS____COMPL.ELEMENT, TEST.TYS____COMPL.SERVICE_TYPE, TEST.TYS____COMPL.ELEMENT_DESCRIPTION,
TEST.TYS____COMPL.ELEMENT_CATEGORY, TEST.TYS____COMPL.BACK_UP_END_DATE, TEST.TYS____COMPL.BACK_UP_START_DATE,
TEST.TYS____COMPL.INCIDENT_END_TIME, TEST.TYS____COMPL.CUST_ACCEPTED_CLOSURE_TIME,
TEST.TYS____COMPL.CLOSING_COMMENTS, TEST.TYS____COMPL.CLEAR_CODE, TEST.TYS____COMPL.ASSIGNED_TO,
TEST.TYS____COMPL.ASSIGNEE_LOGIN, TEST.TYS____COMPL.RESTORE_AMOUNT, TEST.TYS____COMPL.COMPL_REPORTABLE,
TEST.TYS____COMPL.SLA_ATTRIBUTABLE, TEST.TYS____COMPL.CDSP_OUTAGE__SECS_, TEST.TYS____COMPL.FORMAT,
TEST.TYS____COMPL.CONTRACT_SERVICE_LEVEL, TEST.TYS____COMPL.ASSIGNED_TEAM,
TEST.TYS____COMPL.REASON_FOR_CANCELLATION, TEST.TYS____COMPL.CLEAR_CODE_OBJECT,
TEST.TYS____COMPL.CLEAR_CODE_ACTION, TEST.TYS____COMPL.CLOSE_CODE_OPTION,
TEST.TYS____COMPL.CLEAR_CODE_OBJECT_FAMILY, TEST.TYS____COMPL.SERVICE_IMPACT, TEST.SH_TYS____COMPL.CLOSED_TIME,
TEST.SH_TYS____COMPL.CLOSED_USER, TEST.SH_TYS____COMPL.CANCELLED_TIME, TEST.SH_TYS____COMPL.CANCELLED_USER,
TEST.TYS__COMPL_CONFIGURATION.OWNING_CENTRE, TEST.TYS__COMPL_CONFIGURATION.CONTRACT,
TEST.TYS____COMPL.SOURCE, TEST.TYS____COMPL.SUBCASE_OF, TEST.SH_TYS____COMPL.OLD_COMPL_ID,
TEST.TYS____COMPL.SUPPLIER_1, TEST.TYS____COMPL.SUPPLIER_4, TEST.TYS____COMPL.SUPPLIER_3,
TEST.TYS____COMPL.SUPPLIER_2, TEST.TYS____COMPL.TIME_SUPPLIER_ADVISED_BTSS_1,
TEST.TYS____COMPL.TIME_SUPPLIER_ADVISED_BTSS_2, TEST.TYS____COMPL.TIME_SUPPLIER_ADVISED_BTSS_3,
TEST.TYS____COMPL.TIME_SUPPLIER_ADVISED_BTSS_4, TEST.TYS____COMPL.SUPPLIER_1_REF,
TEST.TYS____COMPL.SUPPLIER_2_REF, TEST.TYS____COMPL.SUPPLIER_3_REF, TEST.TYS____COMPL.SUPPLIER_4_REF,
TEST.TYS____COMPL.PASSED_TO_SUPPLIER_AT_1, TEST.TYS____COMPL.PASSED_TO_SUPPLIER_AT_2,
TEST.TYS____COMPL.PASSED_TO_SUPPLIER_AT_3, TEST.TYS____COMPL.PASSED_TO_SUPPLIER_AT_4,
TEST.TYS____COMPL.SUPPLIER_RESOLVED_TIME_1, TEST.TYS____COMPL.SUPPLIER_RESOLVED_TIME_2,
TEST.TYS____COMPL.SUPPLIER_RESOLVED_TIME_3, TEST.TYS____COMPL.SUPPLIER_RESOLVED_TIME_4,
TEST.TYS____COMPL.FAILURE, TEST.TYS____COMPL.COUNTRY, TEST.TYS____COMPL.CUSTOMERS_NAME,
TEST.TYS____COMPL.CUSTOMERS_TEL_NO, TEST.TYS____COMPL.CUSTOMER_E_MAIL_ADDRESS
FROM TEST.TYS____COMPL, TEST.SH_TYS____COMPL, TEST.TYS__COMPL_CONFIGURATION
WHERE TEST.TYS____COMPL.OLD_COMPL_ID = TEST.SH_TYS____COMPL.OLD_COMPL_ID AND
TEST.TYS____COMPL.CID = TEST.TYS__COMPL_CONFIGURATION.CID AND
((TEST.SH_TYS____COMPL.CLOSED_TIME < (TO_DATE(TRUNC(next_day(SYSDATE - 7, 'MONDAY')), 'DD/MM/YY HH24:MI:SS')
- TO_DATE('01/01/1970 01:00:00', 'DD/MM/YY HH24:MI:SS')) * 24 * 3600 + 1) AND
(TEST.SH_TYS____COMPL.CLOSED_TIME > (TO_DATE(TRUNC(next_day(SYSDATE - 14, 'MONDAY')), 'DD/MM/YY HH24:MI:SS')
- TO_DATE('01/01/1970 01:00:00', 'DD/MM/YY HH24:MI:SS')) * 24 * 3600) OR
(TEST.SH_TYS____COMPL.CANCELLED_TIME < (TO_DATE(TRUNC(next_day(SYSDATE - 7, 'MONDAY')), 'DD/MM/YY HH24:MI:SS')
- TO_DATE('01/01/1970 01:00:00', 'DD/MM/YY HH24:MI:SS')) * 24 * 3600 + 1) AND
(TEST.SH_TYS____COMPL.CANCELLED_TIME > (TO_DATE(TRUNC(next_day(SYSDATE - 14, 'MONDAY')), 'DD/MM/YY HH24:MI:SS')
- TO_DATE('01/01/1970 01:00:00', 'DD/MM/YY HH24:MI:SS')) * 24 * 3600))

I'm sending herewith the explain plan from toad as below for further invetigation
Operation Object Name Rows Bytes Cost Object Node In/Out PStart PStop
SELECT STATEMENT Optimizer Mode=CHOOSE 7 K 19360
CONCATENATION
HASH JOIN 3 K 2 M 11048
TABLE ACCESS FULL ARADMIN.T60 11 K 473 K 200
NESTED LOOPS 3 K 1 M 10837
TABLE ACCESS BY INDEX ROWID ARADMIN.H35 3 K 111 K 3255
INDEX RANGE SCAN ARADMIN.STF_CANT 3 K 48
TABLE ACCESS BY INDEX ROWID ARADMIN.T35 1 M 698 M 2
INDEX UNIQUE SCAN ARADMIN.IT35 1 M 1
HASH JOIN 3 K 2 M 11048
TABLE ACCESS FULL ARADMIN.T60 11 K 473 K 200
NESTED LOOPS 3 K 1 M 10837
TABLE ACCESS BY INDEX ROWID ARADMIN.H35 3 K 111 K 3255
INDEX RANGE SCAN ARADMIN.STF_CLOT 3 K 48
TABLE ACCESS BY INDEX ROWID ARADMIN.T35 1 M 698 M 2
INDEX UNIQUE SCAN ARADMIN.IT35 1 M 1

Issue with Webservice Creation using Session Beans.

Hi All,
I want to expose my Session beans as webservice.
I'm using Weblogic Application Server.
When I do the modeling using JDeveloper, I'm unable to convert the Session bean to webservice.
Any information on this is highly appreciable.
Thanks & Regards,
Kumar Madhavan.

I can't give you much of a walk through, as I have just started it myself, but I'm using a universal unique identifier to represent each client. Whenever a client posts data from a jsp or applet the uuid is also sent. I use POST to pass all my parameters. If the server hasen't received data in say 5 minutes from the client then it is assumed the client went offline. Its working for me so far.
COn

Issue with Data Load to InfoCube with Nav Attrivutes Turned on in it

Hi,
I am having a issue with loading data to a InfoCube. When i turn
on the navgational attributes in the cube the data load is failing
and it just says "PROCESSED WITH ERRORS". when i turn them off
the data load is going fine. I have done a RSRV test both on
the infoobject as well as the cube and it shows no errors. What
could be the issue and how do I solve it.
Thanks
Rashmi.

Hi,
To activate a navigation attribute in the cube the data need not be dropped from the cube.
You can always activate the navigation attribute in the cube with data in the cube.
I think you have tried to activate it in the master data as well and then in the cube or something like that??
follow the correct the procedure and try again.
Thanks
Ajeet

Long running index creation

Hi,
We have an InfoCube that has more than 8,5 milion records. When we execute a delta load from its underlying ODS we delete and recreate index. But index creation is taking a very long time (more than 8 hours!) which is unacceptable.
How can we improve index creation on this InfoCube? It's a very simple one (no aggregates, no partitioning, just compression). I have been trying to find similar issues on the forums, and some SAP notes, but I didn't get anything good.
Thanks and best regards,
David.

Hi Pizzaman,
Thanks for your reply. Our DB and BW is Oracle 9.2.0.2 and BW 3.1 SP14.
Indeed, our Cube only has 3 requests: Init of about 8,5 milion records and 2 more requests with 0 entries.
Our first approach has been not to remove the indices daily but rebuild them on a weekly basis, cause, as you say, Cube won't be updated with lots of information. We would like to improve that scenario, though.
Right now we're trying to balance InfoCube dimensions (there were two huge dimensions that have been decreased in size). Do you believe that huge dimensions can impact on Cube index creation? Or is index creation only related to the fact table (that won't change)?
Thanks,
David.

Issue in PO creation for Direct Material Procurement.

Hi Experts,
I am working with SRM 7.0 Classic Scenario.
I have no issues with SC creation for indirect materials with Account Assignment.
But when I select Order as Direct material in SC for any material with out account assignment on Approval of SC PO is created in SRM system as Extendended Classic Scenario even though I have not activated Extended classic scenario.
Kindly help me out in this issue how can I order as DIRECT MATERIAL WITH Classic scenario.
Regards,
B.N.Karthikeyan.

karthi
it is standard behavior,
but you can do one thing .
BBP_CREATE_BE_PO_NEW BADI - TRY . CLEAR THE ACCOUNT ASSIGNMENT .Thats all . check it up with technical resoucre.
but you have to decide by developemnt what are the materials are PO with account / without account assignment
br
muthu

XML DB Index creation problem

We are facing issues in creating index on XMLTYPE elements. In the below example, when we try to create index on "/PurchaseOrder/LineItems/LineItem/Description" element, its throwing "ORA-29036: This feature is not supported" error. It is allowing us to create index on Description element if we remove "maxOccurs="unbounded" attribute either in "LineItem" element or "Part" element. Please provide pointers on this issue. Below are the sample code for schema, table and index creation.
DECLARE
XMLSCHEMADOC VARCHAR2(32767);
BEGIN
XMLSCHEMADOC := '
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb"
version="1.0" xdb:storeVarrayAsTable="true">
<xs:element name="PurchaseOrder" type="PurchaseOrderType"/>
<xs:complexType name="PurchaseOrderType">
<xs:sequence>
<xs:element name="Reference" type="ReferenceType"/>
<xs:element name="Actions" type="ActionsType"/>
<xs:element name="Reject" type="RejectionType" minOccurs="0"/>
<xs:element name="Requestor" type="RequestorType"/>
<xs:element name="User" type="UserType"/>
<xs:element name="CostCenter" type="CostCenterType"/>
<xs:element name="ShippingInstructions" type="ShippingInstructionsType"/>
<xs:element name="SpecialInstructions" type="SpecialInstructionsType"/>
<xs:element name="LineItems" type="LineItemsType"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="LineItemsType">
<xs:sequence>
<xs:element name="LineItem" type="LineItemType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="LineItemType">
<xs:sequence>
<xs:element name="Description" type="DescriptionType"/>
<xs:element name="Part" type="PartType" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="ItemNumber" type="xs:integer"/>
</xs:complexType>
<xs:complexType name="PartType">
<xs:attribute name="Id">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="10"/>
<xs:maxLength value="14"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="Quantity" type="moneyType"/>
<xs:attribute name="UnitPrice" type="quantityType"/>
</xs:complexType>
<xs:simpleType name="ReferenceType">
<xs:restriction base="xs:string">
<xs:minLength value="18"/>
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="ActionsType">
<xs:sequence>
<xs:element name="Action" maxOccurs="4">
<xs:complexType>
<xs:sequence>
<xs:element name="User" type="UserType"/>
<xs:element name="Date" type="DateType" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="RejectionType">
<xs:all>
<xs:element name="User" type="UserType" minOccurs="0"/>
<xs:element name="Date" type="DateType" minOccurs="0"/>
<xs:element name="Comments" type="CommentsType" minOccurs="0"/>
</xs:all>
</xs:complexType>
<xs:complexType name="ShippingInstructionsType">
<xs:sequence>
<xs:element name="name" type="NameType" minOccurs="0"/>
<xs:element name="address" type="AddressType" minOccurs="0"/>
<xs:element name="telephone" type="TelephoneType" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:simpleType name="moneyType">
<xs:restriction base="xs:decimal">
<xs:fractionDigits value="2"/>
<xs:totalDigits value="12"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="quantityType">
<xs:restriction base="xs:decimal">
<xs:fractionDigits value="4"/>
<xs:totalDigits value="8"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="UserType">
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="10"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="RequestorType">
<xs:restriction base="xs:string">
<xs:minLength value="0"/>
<xs:maxLength value="128"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CostCenterType">
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="4"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="VendorType">
<xs:restriction base="xs:string">
<xs:minLength value="0"/>
<xs:maxLength value="20"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="PurchaseOrderNumberType">
<xs:restriction base="xs:integer"/>
</xs:simpleType>
<xs:simpleType name="SpecialInstructionsType">
<xs:restriction base="xs:string">
<xs:minLength value="0"/>
<xs:maxLength value="2048"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="NameType">
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="20"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="AddressType">
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="256"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="TelephoneType">
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="24"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="DateType">
<xs:restriction base="xs:date"/>
</xs:simpleType>
<xs:simpleType name="CommentsType">
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="2048"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="DescriptionType">
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="256"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
DBMS_XMLSCHEMA.registerSchema(
 SCHEMAURL => 'purchaseorder1.xsd',
 SCHEMADOC => XMLSCHEMADOC,
 LOCAL => TRUE,
 GENTYPES => TRUE,
 GENTABLES => TRUE,
 genbean => FALSE,
 enablehierarchy => 1,
 force => FALSE);
END;
CREATE TABLE PURCHASEORDER (
PURCHASE_ORDER_ID NUMBER PRIMARY KEY,
PURCHASE_ORDER_CONTENTS XMLType
XMLTYPE COLUMN PURCHASE_ORDER_CONTENTS
XMLSCHEMA "purchaseorder1.xsd"
ELEMENT "PurchaseOrder"
VARRAY PURCHASE_ORDER_CONTENTS."XMLDATA"."LineItems"."LineItem"
STORE AS table ACTION_TABLE
((primary key (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$))
organization index overflow);
create index po_lineitem_org_idx on PURCHASEORDER(extractValue(PURCHASE_ORDER_CONTENTS,'/PurchaseOrder/LineItems/LineItem/Description'));

Hi,
Thanks for your reply. Please find below my issues
issue 1 : (index creation using extractvalue)
I am able to create index on Description element if I remove maxoccurs="unbounded" from Part element. I am not able to understand, how i am able to create index if I remove maxoccurs="unbounded" from its sibiling.
issue 2 : (Creating an Index for Direct Access to an Ordered Collection Table)
When i tried to create table i am getting the following error.
SQL> CREATE TABLE PURCHASEORDER (
2 PURCHASE_ORDER_ID NUMBER PRIMARY KEY,
3 PURCHASE_ORDER_CONTENTS XMLType
4 )
5 XMLTYPE COLUMN PURCHASE_ORDER_CONTENTS
6 XMLSCHEMA "purchaseorder1.xsd"
7 ELEMENT "PurchaseOrder"
8 VARRAY PURCHASE_ORDER_CONTENTS."XMLDATA"."LineItems"."LineItem"
9 STORE AS table LINEITEM_TABLE
10 ((primary key (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$)))
11 VARRAY PURCHASE_ORDER_CONTENTS."XMLDATA"."LineItems"."LineItem"."Part"
12 STORE AS table PART_TABLE
13 ((primary key (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$)));
VARRAY PURCHASE_ORDER_CONTENTS."XMLDATA"."LineItems"."LineItem"."Part"
ERROR at line 11:
ORA-22809: nonexistent attribute
Please provide pointers.

Performance issues with the Vouchers index build in SES

Hi All,
We are currently performing an upgrade for: PS FSCM 9.1 to PS FSCM 9.2.
As a part of the upgrade, Client wants Oracle SES to be deployed for some modules including, Purchasing, Payables (Vouchers)
We are facing severe performance issues with the Vouchers index build. (Volume of data = approx. 8.5 million rows of data)
The index creation process runs for over 5 days.
Can you please share any information or issues that you may have faced on your project and how they were addressed?

Check the following logs for errors:
1. The message log from the process scheduler
2. search_server1-diagnostic.log in /search_server1/logs directory
If the build is getting stuck while crawling then we typically have to increase the Java Heap size for the Weblogic instance for SES>

Spatial query index creation fails with ORA-13282: failure on initializatio

Hi,
I have an Oracle 10g 10.2.0.5.0 database newly installed. Spatial index creation fails:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13282: failure on initialization of coordinate transformation
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
The script I am trying to run is:
Insert into USER_SDO_GEOM_METADATA
(TABLE_NAME, COLUMN_NAME, DIMINFO, SRID)
Values
('SOME_TABLE', 'geo',
"SDO_DIM_ARRAY"(
"SDO_DIM_ELEMENT"('X',600000,900000,0.001),
"SDO_DIM_ELEMENT"('Y',150000,400000,0.001)), 23700);
CREATE INDEX IX_GEO_SOME_TABLE ON SOME_TABLE (GEO) INDEXTYPE IS MDSYS.SPATIAL_INDEX ;
Earlier I had some issues with NLS settings in relation to Spatial, but in this particular case setting the NLS_LANG for AMERICAN_AMERICA does not help. I found this comment http://www.orafaq.com/forum/t/127312/2/ but would not like to hack around with MDSYS table content. Any help is highly appreciated.
Regards, Tamas

Tamas,
1 . . .Are you indexing a table that already has geometries or an empty table?
. . . .If the former, do all the geometries in that table have the same (not NULL) SRID (23700)?
2 . .The link you posted suggests a parsing problem since in Hungarian (23700), the decimal seperator is a comma (not a period). Accordingly, I believe the edit to mdsys.sdo_cs_srs.WKTEXT would be:
PROJCS["HD72 / EOV", GEOGCS [ "HD72", DATUM ["Hungarian Datum 1972 (EPSG ID 6237)", SPHEROID ["GRS 1967 (EPSG ID 7036)", 6378160, 298,247167427]], PRIMEM [ "Greenwich", 0,000000 ], UNIT ["Decimal Degree", 0,01745329251994328]], PROJECTION ["Egyseges Orszagos Vetuleti (EPSG OP 19931)"], UNIT ["Meter", 1]]
^ ^ ^ Regards,
Noel

Issues with ODATA service creation

Hi Gurus,
I am facing some issues with ODATA service creation. I have an analytic view which I want to consume via SAP UI5.
As per guides and blogs, I need to create 3 files, namely .xsaccess, .xsapp and .xsodata. I created these three files but at the same time .xsodata and .xsaccess got created at one more place. That place is my package which I checked out while creating the repository. Now when I try to activate my .xsaccess or .xsapp file, I get an error message - "The file name .xsaccess or .xsapp already exists and only 1 file is allowed per package"
for more info please revert.
Kindly help.
Best regards,
Chandan

Chandan Sinha wrote:
Can we add multiple analytic views in one ODATA service?
Certainly. You just have multiple entities then. You can even create associations between them. Here is an example that uses a combination of CDS Views, Attribute Views, and Analytic Views:
service namespace "Wile.services" {
"Wile.data.models::AN_EPISODES" as "Episodes"
keys ("EPISODE_ID")
navigates ("ToACMEItems" as "ACMEItems",
            "ToCoyoteNames" as "CoyoteNames",
            "ToRoadRunnerNames" as "RoadRunnerNames",
            "ToDirectors" as "Directors",
            "ToWriters" as "Writers");
"Wile.data.models::AT_ACME_ITEMS" as "ACMEItems"
keys ("EPISODE_ID","ITEM_ID");
"Wile.data.models::AT_ACME_CATALOG" as "ACMECatalog"
keys ("ITEM_ID")
create using "Wile.services:ACMECatalogExits.xsjslib::itemsCreate"
update using "Wile.services:ACMECatalogExits.xsjslib::itemsUpdate"
delete using "Wile.services:ACMECatalogExits.xsjslib::itemsDelete";
"Wile.data::WileECoyote.Episode.CoyoteNamesView" as "CoyoteNames"
with ("EPISODE_ID","NAME_ID","NAME")
keys ("EPISODE_ID","NAME_ID");
"Wile.data::WileECoyote.Episode.RoadRunnerNamesView" as "RoadRunnerNames"
with ("EPISODE_ID","NAME_ID","NAME")
keys ("EPISODE_ID","NAME_ID");
"Wile.data::WileECoyote.Episode.DirectorsView" as "Directors"
with ("EPISODE_ID","NAME_ID","NAME","URL")
keys ("EPISODE_ID","NAME_ID");
"Wile.data::WileECoyote.Episode.WritersView" as "Writers"
with ("EPISODE_ID","NAME_ID","NAME","URL")
keys ("EPISODE_ID","NAME_ID");
association "ToACMEItems" principal "Episodes"("EPISODE_ID")
   multiplicity "1"
   dependent "ACMEItems"("EPISODE_ID") multiplicity "*";
association "ToCoyoteNames" principal "Episodes"("EPISODE_ID")
   multiplicity "1"
   dependent "CoyoteNames"("EPISODE_ID") multiplicity "*";
association "ToRoadRunnerNames" principal "Episodes"("EPISODE_ID")
   multiplicity "1"
   dependent "RoadRunnerNames"("EPISODE_ID") multiplicity "*";
association "ToDirectors" principal "Episodes"("EPISODE_ID")
   multiplicity "1"
   dependent "Directors"("EPISODE_ID") multiplicity "*";
association "ToWriters" principal "Episodes"("EPISODE_ID")
   multiplicity "1"
   dependent "Writers"("EPISODE_ID") multiplicity "*";

Issue with index creation of an infocube.

Similar Messages

Maybe you are looking for