IN_WRONG_TABLESPACE, object: table/index

Hi all,
Apologies for the repost of this topic. I have seen it a few times but without resolutions. My problem is as follows.
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPSR3.D010INC~1, value: PSAPSR346C
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPSR3.D010L, value: PSAPSR346C
This is IAORA.
TABART
TABSPACE
PCTINC
OFREELIST
OPCTFREE
APPL0
PSAPSR3
0000
1
10
APPL1
PSAPSR3
0000
1
10
APPL2
PSAPSR3
0000
1
10
CLUST
PSAPSR3
0000
1
10
POOL
PSAPSR3
0000
1
10
SDIC
PSAPSR3
0
1
10
SDOCU
PSAPSR3
0000
1
10
SLDEF
PSAPSR346D
0000
1
10
SLEXC
PSAPSR346D
0000
1
10
SLOAD
PSAPSR3
0000
1
10
SPROT
PSAPSR3
0000
1
10
SSDEF
PSAPSR346D
0000
1
10
SSEXC
PSAPSR346D
0000
1
10
SSRC
PSAPSR3
0000
1
10
TEMP
PSAPSR3
0000
1
10
USER
PSAPSR3USR
0000
1
10
USER1
PSAPSR3USR
0000
1
10
This is TAORA.
TABART
TABSPACE
PCTINC
OFREELIST
OFREEGROUP
OPCTFREE
OPCTUSED
APPL0
PSAPSR3
0000
001
01
10
40
APPL1
PSAPSR3
0000
1
1
10
40
APPL2
PSAPSR3
0000
1
1
10
40
CLUST
PSAPSR3
0000
1
1
10
40
POOL
PSAPSR3
0000
1
1
10
40
SDIC
PSAPSR3
0
1
1
10
40
SDOCU
PSAPSR3
0000
1
1
10
40
SLDEF
PSAPSR346D
0000
1
1
10
40
SLEXC
PSAPSR346D
0000
1
1
10
40
SLOAD
PSAPSR3
0000
1
1
10
40
SPROT
PSAPSR3
0000
1
1
10
40
SSDEF
PSAPSR346D
0000
1
1
10
40
SSEXC
PSAPSR346D
0000
1
1
10
40
SSRC
PSAPSR3
0000
1
1
10
40
TEMP
PSAPSR3
0000
1
1
10
40
USER
PSAPSR3USR
0000
1
1
10
40
USER1
PSAPSR3USR
0000
1
1
10
40
select tablespace_name from dba_tablespaces;
SYSTEM,PSAPUNDO,SYSAUX,PSAPTEMP,PSAPSR3,PSAPSR346C,PSAPSR3USR
Tablespace does exist as you can see above now to determine type of tablespace, and as per below query you can see it contains
both data and indexes.
select distinct(segment_type), tablespace_name from dba_segments order by tablespace_name;
SEGMENT_TYPE       TABLESPACE_NAME
INDEX              PSAPSR3
TABLE              PSAPSR3
INDEX              PSAPSR346C
TABLE              PSAPSR346C
TABLE              PSAPSR3USR
TYPE2 UNDO         PSAPUNDO
INDEX              SYSAUX
INDEX PARTITION    SYSAUX
LOB PARTITION      SYSAUX
LOBINDEX           SYSAUX
LOBSEGMENT         SYSAUX
As per note 655162 option 1 and 2 are applicable to me. But as this tablespace seems to be both a data and index tablespace I am thinking I need to create the tablespace entry in IAORA and TAORA.
How would I correctly edit these table entries and which of the following tables might also have to be edited?
DDART and DARTT are used to maintain the classes ( tabarts)
DD09L maps the tables to each class ( tabart)
TAORA/IAORA maps the classes to the tablespaces
TSORA lists the tablespaces.
As a non dba I find the sap note a bit confusing please advise.
Kind Regards,
Johan

Hi guys,
For clarification:
disp+work information
kernel release                46D
kernel make variant           46D_EXT
DBMS client library           OCI_920__OCI_7_API
DBSL shared library version   46D.00
compiled on                   Linux 2.6.5-7.202.5-smp #1_SMP_Thu_Aug_25_06:20:45_UTC_2005 x86_64
compiled for                  64 BIT
compile time                  Aug 10 2008 21:39:12
update level                  0
patch number                  2415
source id                     0.2415
supported environment
database (SAP, table SVERS)   46A
                              46B
                              46C
                              46D
DBMS server                   ORACLE 8.0.5..
                              ORACLE 8.0.6..
                              ORACLE 8.1.6..
                              ORACLE 8.1.7..
                              ORACLE 9.2.0..
                              ORACLE 10.2.0..
operating system              Linux 2.6
                              System build information:
                              LCHN :
System components:
ST-PI     2008_1_46C
ST-A/PI     01J_R3_46C
SAP_NOTES     46C
SAP_HR     46C
SAP_BASIS     46C
SAP_APPL     46C
SAP_ABA     46C
Regards,
J

Similar Messages

Objects (table, index, partition) fragmented

Hi all,
I run the script bellow to find fragmented objects:
select segment_name, segment_type, count(*) from dba_extents
where owner = ownname
group by segment_name, segment_type
having count(*) > 1
order by 3
And i get some liste like this:
object_names object_types 249
My question is the objects that i have are fragmented and what can i do to solve that fragmentation i mean to avoid object fragmentation.
regards
raistarevo

Hi,
You can go to the 8i documentation for more information:
http://download-west.oracle.com/docs/cd/A87860_01/doc/appdev.817/a76936/dbms_s2a.htm#1004668
But I advice you to read this thread below first.
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:8381899310385
Cheers

Function based indexes on object tables

Hi,
I am trying to create a function based index on an object table. I am getting the following error:
SQL> create index cell1_indx on cell1(create_cell1(id)) indextype is mdsys.spatial_index;
create index cell1_indx on cell1(create_cell1(id)) indextype is mdsys.spatial_index
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-13249: Stmt-Execute Failure: SELECT num_rows from all_tables where owner='ASHE' and table_name=
'CELL1'
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: at line 1
Here cell1 is an object table.
Is the procedure for creating function based indexes on object tables different from relational tables?
Chinni

One of the many new features in Oracle 8i is the Function-Based Index (we will refrain from using FBI, but only just). This allows the DBA to create indexes on functions or expressions; these functions can be user generated pl/sql functions, standard SQL functions (non-aggregate only) or even a C callout.
A classic problem the DBA faces in SQL Tuning is how to tune those queries that use function calls in the where clause, and result in indexes created on these columns not to be used.
Example
Standard B-Tree index on SURNAME with cost based optimizer
create index non_fbi on sale_contacts (surname);
analyze index non_fbi compute statistics;
analyze table sale_contacts compute statistics;
SELECT count(*) FROM sale_contacts
WHERE UPPER(surname) = 'ELLISON';
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=3 Card=1 Bytes=17)
1 0 SORT (AGGREGATE)
2 1 TABLE ACCESS (FULL) OF 'SALES_CONTACTS' (Cost=3 Card=16 Bytes=272)
Now we use a function based index
create index fbi on sale_contacts (UPPER(surname));
analyze index fbi compute statistics;
analyze table sale_contacts compute statistics;
SELECT count(*) FROM sale_contacts WHERE UPPER(surname) = 'ELLISON';
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=2 Card=1 Bytes=17)
1 0 SORT (AGGREGATE)
2 1 INDEX (RANGE SCAN) OF 'FBI' (NON-UNIQUE) (Cost=2 Card=381 Bytes=6477)
The function-based index has forced the optimizer to use index range scans (retuning zero or more rowids) on the surname column rather than doing a full table scan (non-index lookup). Optimal performance does vary depending on table size, uniqueness and selectivity of columns, use of fast full table scans etc. Therefore try both methods to gain optimal performance in your database.
It is important to remember that the function-based B*Tree index does not store the expression results in the index but uses an "expression tree". The optimizer performs expression matching by parsing the expression used in the SQL statement and comparing the results against the expression-tree values in the function-based index. This comparison IS case sensitive (ignores spaces) and therefore your function-based index expressions should match expressions used in the SQL statement where clauses.
Init.ora Parameters
The following parameter must be set in your parameter file: QUERY_REWRITE_INTEGRITY = TRUSTED
QUERY_REWRITE_ENABLED = TRUE
COMPATIBLE = 8.1.0.0.0 (or higher)
Grants
Grants To create function-based indexes the user must be granted CREATE INDEX and QUERY REWRITE, or alternatively be granted CREATE ANY INDEX and GLOBAL QUERY REWRITE. The index owner must have EXECUTE access on the function used for the index. If execute access is revoked then the function-based index will be "disabled" (see dba_indexes).
Disabled Indexes
If your function-based index has a status of "disabled" the DBA can do one of the following:
a) drop and create the index (take note of its current settings)
b) alter index enable, function-based indexes only, also use disable keyword as required
c) alter index unusable.
Queries on a DISABLED index fail if the optimizer chooses to use the index.Here is an example ORA error:
ERROR at line 1: ORA-30554: function-based index MYUSER.FBI is disabled.
All DML operations on a DISABLED index also fail unless the index is also marked UNUSABLE and the initialization parameter SKIP_UNUSABLE_INDEXES is set to true.
Some more Examples
CREATE INDEX expression_ndx
ON mytable ((mycola + mycolc) * mycolb);
SELECT mycolc FROM mytable
WHERE (mycola + mycolc) * mycolb <= 256;
..or a composite index..
CREATE INDEX example_ndx
ON myexample (mycola, UPPER(mycolb), mycolc);
SELECT mycolc FROM myexample
WHERE mycola = 55 AND UPPER(mycolb) = 'JONES';
Restriction & Rule Summary
The following restrictions apply to function based indexes. You may not index:
a) LOB columns
b) REF
c) Nested table column
d) Objects types with any of the above data types.
Function-based indexes must always follow these rules:
a) Cost Based optimizer only, must generate statistics after the index is created
b) Can not store NULL values (function can not return NULL under any circumstance)
c) If a user defined pl/sql routine is used for the function-based index, and is invalidated, the index will become "disabled"
d) Functions must be deterministic (always return the same value for a known input)
e) The index owner must have "execute" access on function used in the function-based index. Revocation of the privilege will render the index "disabled"
f) May have a B-Tree and Bitmap index type only
g) Can not use expressions that are based on aggregate functions, ie. SUM, AVG etc.
h) To alter a function-based index as enabled, the function used must be valid, deterministic and the signature of the function matches the signature of the function when it was created.
Joel P�rez

Database objects Tables, Views, Indexes not expand in Connections navigator

In SQL Developer tool when I clicked on any database object: Tables, Views, Indexes, Packages, Procedures, Functions, and Triggers none of them expands in Connections navigator so I am not able to see all tables, Views, Indexes in this schema objects.
Please advise
Thanks a lot
Vincent

If the user you're connecting with is not the owner of the objects, you can access them through the Other Users node.
Hope that helps,
K.

Impossible to create an index with an object table

Is it possible to use object tables with Oracle Spatial ?
With Oracle 8.1.7.0.0, here is the example where I encounter a problem (this example works of course with an equivalent relational table) :
create or replace type zonegeo as object (
id integer, definitionGeo MDSYS.SDO_GEOMETRY
create table essaigeo of zonegeo (id PRIMARY KEY)
OBJECT ID PRIMARY KEY;
INSERT INTO USER_SDO_GEOM_METADATA
VALUES ('ESSAIGEO','DEFINITIONGEO',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X', 47680.000, 1197822.000, 0.005),
MDSYS.SDO_DIM_ELEMENT('Y', 1620431.000, 2677441.000, 0.005)
NULL -- SRID
CREATE INDEX ESSAIGEO_SPATIAL_IDX
ON ESSAIGEO(DEFINITIONGEO)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS ('SDO_LEVEL = 6);
ERREUR ` la ligne 1 :
ORA-29855: erreur d'exicution de la routine ODCIINDEXCREATE
ORA-13203: ichec de lecture de la table USER_SDO_GEOM_METADATA
ORA-13203: ichec de lecture de la table USER_SDO_GEOM_METADATA
ORA-06512: ` "MDSYS.SDO_INDEX_METHOD", ligne 8
ORA-06512: ` ligne 1

In Oracle 8.1.7 you cannot embed a geometry type in another type and index it.
In 9i, you can , but not in the way you've defined it, i.e. you have to create a regular
table, and have a column of type zonegeo, and make a few other changes, i.e.:
create or replace type zonegeo as object (
id integer, definitionGeo MDSYS.SDO_GEOMETRY
create table essaigeo (zone zonegeo);
INSERT INTO USER_SDO_GEOM_METADATA
VALUES ('ESSAIGEO','ZONE.DEFINITIONGEO',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X', 47680.000, 1197822.000, 0.005),
MDSYS.SDO_DIM_ELEMENT('Y', 1620431.000, 2677441.000, 0.005)
NULL -- SRID
CREATE INDEX ESSAIGEO_SPATIAL_IDX
ON ESSAIGEO(ZONE.DEFINITIONGEO)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS ('SDO_LEVEL = 6);

New tables & indexes created do not show up in dba_segments view

Dear all,
I have created 3 tables and some indexes, but these objects do not show up in dba_segments view. Is this a normal behaviour? Previously, with dictionary managed tablespace, I can specify the minimum extent to create, when the table/index is created. But I'm not sure how the locally managed tablespace work. Please do advice. Thank you very much in advance.
I'm using Oracle 11g R2 (11.2.0.1.0) for Microsoft Windows (x64), running on Windows 7.
For the purpose of reproducing this issue, I have created the tablespaces as follow:
CREATE TABLESPACE CUST_DATA
DATAFILE 'd:\app\asus\oradata\orcl11gr2\CUST_DATA01.DBF' SIZE 512K
AUTOEXTEND ON NEXT 256K MAXSIZE 2000K
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K
SEGMENT SPACE MANAGEMENT AUTO;
CREATE TABLESPACE CUST_INDX
DATAFILE 'd:\app\asus\oradata\orcl11gr2\CUST_INDX.DBF' SIZE 256K
AUTOEXTEND ON NEXT 128K MAXSIZE 2000K
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K
SEGMENT SPACE MANAGEMENT AUTO;
CREATE TABLE CUSTOMER_MASTER (CUST_ID VARCHAR2 (10),
CUST_NAME VARCHAR2 (30),
EMAIL VARCHAR2 (30),
DOB DATE,
ADD_TYPE CHAR (2) CONSTRAINT CK_ADD_TYPE CHECK (ADD_TYPE IN ('B1','B2','H1','H2')),
CRE_USER VARCHAR2 (5) DEFAULT USER,
CRE_TIME TIMESTAMP (3) DEFAULT SYSTIMESTAMP,
MOD_USER VARCHAR2 (5),
MOD_TIME TIMESTAMP (3),
CONSTRAINT PK_CUSTOMER_MASTER PRIMARY KEY (CUST_ID) USING INDEX TABLESPACE CUST_INDX)
TABLESPACE CUST_DATA;
SQL> SELECT TABLE_NAME, TABLESPACE_NAME
2 FROM USER_TABLES
3 WHERE TABLE_NAME LIKE 'CUST%';
TABLE_NAME TABLESPACE_NAME
CUSTOMER_MASTER CUST_DATA
SQL> SELECT INDEX_NAME, TABLESPACE_NAME
2 FROM USER_INDEXES
3 WHERE TABLE_NAME LIKE '%CUST%';
INDEX_NAME TABLESPACE_NAME
PK_CUSTOMER_MASTER CUST_INDX
SQL> SELECT SEGMENT_NAME, SEGMENT_TYPE, TABLESPACE_NAME, BYTES
2 FROM USER_SEGMENTS;
no rows selected

Prior to 11g, when you created a table or whatever, you automatically allocated one extent.
This is now no longer true and depends on a parameter I don't remember.
dba_segments is a summary of dba_extents.
Obviously, if there is no extent allocated, the table (view is defined with inner join) will not show up.
You could qualify this is as a bug and submit a SR to Oracle. But then the performance impact may be huge.
Sybrand Bakker
Senior Oracle DBA

How do I reference the instance in a constraint on an object table?

I want to create a unique constraint that involves the result of a deterministic member function.
I can do it just fine if I create table with a column of the object type:
drop table test_table1;
drop table test_table2;
drop type test_type;
create type test_type as object (
     alpha varchar2(30),
     member function get_beta return varchar2 deterministic
show errors;
create type body test_type as
     member function get_beta return varchar2 deterministic is
     begin
          return 'Beta';
     end;
end;
show errors;
create table test_table1 (
     test_instance mattk.test_type,
     beta varchar2(4000) as (test_type.get_beta(test_instance)),
     constraint test_table1_pk primary key (beta)
insert into test_table1 (test_instance) values (test_type('Alpha'));
commit;
insert into test_table1 (test_instance) values (test_type('Gamma'));
commit;As I said, this works just fine, and the second insert statement produces the following error:
insert into test_table1 (test_instance) values (test_type('Gamma'))
ORA-00001: unique constraint (MATTK.TEST_TABLE1_PK) violatedHowever, I'd really like my table to be an object table.
If I do that:
create table test_table2 of test_type;How do I then reference the object instance that the row represents?

I've got it all worked out now. Thanks everyone for the helpful advice.
I changed the type definition slightly. I added an Attribute for Beta, in addition to keeping the deterministic member function.
drop table test_table2;
drop type test_type;
create type test_type as object (
     alpha varchar2(30),
     beta varchar2(30),
     member function get_beta return varchar2 deterministic
show errors;
create type body test_type as
     member function get_beta return varchar2 deterministic is
     begin
          if (self.beta <> 'Beta') then
               raise_application_error(-20000, 'Beta is not properly set.');
          end if;
          return 'Beta';
     end;
end;
show errors;
create table test_table2 of test_type;
alter table test_table2 add (
     constraint test_table2_pk primary key (alpha, beta)
create unique index test_table2_idx1 on test_table2(test_type.get_beta(object_value));
insert into test_table2 values (test_type('Alpha', 'Beta'));
commit;
insert into test_table2 values (test_type('Gamma', 'Beta'));
update test_table2 t set t.beta = 'BETA';
insert into test_table2 values (test_type('Delta', 'Delta'));Correctly produces the following errors:
insert into test_table2 values (test_type('Gamma', 'Beta'))
ORA-00001: unique constraint (MATTK.TEST_TABLE2_IDX1) violated
update test_table2 t set t.beta = 'BETA'
ORA-20000: Beta is not properly set.
ORA-06512: at "MATTK.TEST_TYPE", line 5
insert into test_table2 values (test_type('Delta', 'Delta'))
ORA-20000: Beta is not properly set.
ORA-06512: at "MATTK.TEST_TYPE", line 5The presence of the unique index over the deterministic member function guarantees that function will be called on any insert or update, which gives it the opportunity to error out if the attribute is not properly set.
The reason I was interested in doing this is because Oracle does not support constant attribute values.
Again, thanks everyone for the helpful replies.

Is it permissable to extend an SAP-provided table index?

(Please note I realize this might not be the best forum for this post; I did look at ABAP development, SAP on Oracle, and a few others, but given some other threads, it seemed like this might be the best place for it. Apologies if not).
We have a very large table (GMIA), and I noticed that two customer-created indexes can essentially be combined into one because the first index is RGRANT_NBR plus fields A and B, and the second index is RGRANT_NBR plus fields A, B, C, D, and E. So I might as well get rid of the first index and just keep the second one having RGRANT_NBR plus fields A through E.
However, I noticed that SAP-provided index 4 contains simply one field - RGRANT_NBR. So ideally, I could just add fields A, B, C, D, and E to index 4, then I could get rid of my second customer-created index.
Question: Is it permissable to extend an SAP-provided index like this? As a developer, I'm not in the modifying SAP objects business, but this is the first time I've been presented this situation with a table index. Given that our GMIA table has MILLIONS of records in it, getting rid of another customer-created index completely might be a great opportunity.
Thoughts?
Dave

I really don't have a requirement for this. I'm a developer, and I've noticed some of our biggest timeout issues concern programs that hit table GMIA. So I thought I'd take a look at GMIA and our indexes to learn more about it via SE11 and DB02.
In our Production environment, we have over 88 million records in this table for a table size of 38.23 GB. Aside from the 6 SAP-provided indexes, 8 customer indexes have been created by others over time. It was in looking at these indexes that I noticed our 8th customer index, ZS8, is essentially the same 3 fields as ZS3, plus a few more fields. Ideally, ZS8 should NOT have been created, and ZS3 should have simply been extended with the additional fields.
It was suggested to me in another thread a long while back that I could potentially get rid of ZS3 as well and just make SAP index 4 look like ZS8 because SAP index 4 is just indexed by Grant Number (RGRANT_NBR). ZS8's first index field is Grant Number followed by 5 or 6 additional fields. That's why I was wondering if it was even a "thing" or a possibility to extend an SAP index, but customizing an SAP component makes Dave a very, VERY nervous boy.
Basically, I'm alarmed at the number of records in the table and the number of indexes we have. There's no archiving strategy here, so I probably can't do anything about the number of records in GMIA, which go back to 2006 when we first went live with SAP. But I can clearly get rid of one customer-created index (ZS3). And if I can deactivate SAP index 4, I would assume the system would then automatically use ZS8 since the first field is Grant Number for situations where it would have used SAP index 4.
So that's the background here. Honestly, I don't know how much improvement these things will make, but getting rid of ZS3 will save 5 GB of space, and presumably "deactivating" SAP index 4 would save almost 5 GB as well. I'm assuming we might see some negligible performance gains on our table operations involving GMIA, but it's still a beast with a large number of indexes, so I don't know.
I'm really, really interested in hearing from others' thoughts and recommendations -- your input is MOST welcome here!
Dave

Processing SCHEMA_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX

I tried to import my 20GB data into my database but it is pending/hanging almost 1 day at this line, which is
Processing SCHEMA_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX .
My db version is :Version 11.1.0.7.0
What could be the reason? Why it is waiting so long on this line? It is locking indexes?

Windows Server 2008 R2 Enterprise
impdp user/pass@DB exclude=statistics schemas=user dumpfile=a.dmp log=a.log
Import: Release 11.1.0.7.0 - 64bit Production on Friday, 10 August, 2012 17:04:03
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "ODB"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "ODB"."SYS_IMPORT_FULL_01": odb/********@TEST parallel=4 dumpfile=UAT_08082012.DMP
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"ODB" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
Processing object type SCHEMA_EXPORT/DB_LINK
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "ODB"."PN_INVENTORY_HISTORY" 218.6 MB 1302517 rows
SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
and waiting here since 1 day..
alert log file has some warnings like:
<txt>Warning: drop_queue_table: No evaluation for the queue table: ODB.ROS_IN_QUEUE_TABLE
</txt>
</msg>
<msg time='2012-08-11T00:29:21.710+03:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
Thread 1 advanced to log sequence 91 (LGWR switch)
Current log# 1 seq# 91 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO01.LOG
Sat Aug 11 10:16:16 2012
Thread 1 advanced to log sequence 92 (LGWR switch)
Current log# 2 seq# 92 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO02.LOG
Sat Aug 11 10:16:40 2012
Thread 1 cannot allocate new log, sequence 93
Checkpoint not complete_
Current log# 2 seq# 92 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO02.LOG_
Thread 1 advanced to log sequence 93 (LGWR switch)_
Current log# 3 seq# 93 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO03.LOG_
Thread 1 cannot allocate new log, sequence 94_
Checkpoint not complete_
Current log# 3 seq# 93 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO03.LOG_
Thread 1 advanced to log sequence 94 (LGWR switch)_
Current log# 1 seq# 94 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO01.LOG_
Sat Aug 11 10:16:56 2012_
Thread 1 cannot allocate new log, sequence 95_
Checkpoint not complete_
Current log# 1 seq# 94 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO01.LOG
Thread 1 advanced to log sequence 95 (LGWR switch)
Current log# 2 seq# 95 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO02.LOG
<txt>Errors in file d:\app\traxadmin\diag\rdbms\test\test\trace\test_j003_6036.trc:
ORA-12012: error on auto execute of job 74639
ORA-20111: ORA-24010: QUEUE ODB.IFACE_AEX_IN_Q does not exist
ORA-06512: at "ODB.PKG_IFACE_QUEUE", line 80
ORA-24010: QUEUE ODB.IFACE_AEX_IN_Q does not exist
ORA-06512: at "ODB.PKG_IFACE_QUEUE", line 48
ORA-06512: at "ODB.PKG_AEX_INBOUND"
Edited by: user638937 on 11.Ağu.2012 00:27

DB02old showing Missing in R/3 DDIC Tables & Indexes in BI 7.0 system

Hi,
Db02old showing missing in R/3 DDIC Tables & Indexes ,Details given below.
                                    Tables          Indexes
Total number                        63,413          88,532
Total size/kb                1,208,272,704     227,436,608
More than 1 extent                 16,499           6,629
Missing in database                 0               0
Missing in R/3 DDIC                 5               1
Space-critical objects              0               0
Unknown indexes in ABAP Dictionary
     DB indexes                       1
         /BIC/E101128~900
Unknown objects in ABAP Dictionary
    DB tables                        5
        /BI0/1ASSET
        /BI0/1ASSET_CLAS
        /BIC/E100219
        /BIC/F101145
        /BIC/F101153
Why it is showing ? Please advise.
Thnks&Rgds,
Ganga.

Hi Bhaskar,
I have done the below process
In T-code DB02 Menu "Go TO" -> Table and Indices -> DB <-> ABAP Dic<->Display
It is showing the below details
Other checks
Tables 1
SCI_TEMPT Should not be created in DB
I have select the SCI_TEMPT table and clicked on create in DB.
After that again I have checked the db02 t-code again it is showing the same.
Please let me know how can fix this issue.
Regards,
Reddy V.

Object tables/associative arrays are using lots of memory what is alternate

I'm using mostly object tables/associative arrays in my package and it is using lots of server memorey so i want to use a different technicque to save momorey .
like using create global temporary table or nested Table Store as or creating table run time at the start and droping it in the end .
do have any suggestion for this ?
for this package i'm retriving data from different table into object tables and do calculation in memorey before i send data to front end for reporting using reference cursor .
give me your suggetion or if you know any example code for this type of process using different technique please let us know .
thank you very much
regards
shailen Patel

You can create a global temporary table like this:
CREATE GLOBAL TEMPORARY TABLE AR_TRIAL_RCPT(
LOC_ACCT_ID NUMBER(12),
ACCT_ID NUMBER(12),
CURRENCY_ID NUMBER(12),
AMT NUMBER(13,   4),
AMT_PRIMARY NUMBER(13,   4)
[ON COMMIT PRESERVE ROWS]
;If you want the table truncated on COMMITs leave out the part in brackets other wise leave off the brackets and the table won't be truncated until your session terminates or you explicitly truncate the table.
You can also define indexes, primary keys, foreign keys, check constraints, etc. on your temporary table if need be to improve processing.
Now when it comes to inserting into your newly minted global temporary table, you should be able to use one of insert statements from the following anonymous PL/SQL block:
CREATE GLOBAL TEMPORARY TABLE AR_TRIAL_RCPT(
LOC_ACCT_ID NUMBER(12),
ACCT_ID NUMBER(12),
CURRENCY_ID NUMBER(12),
AMT NUMBER(13,   4),
AMT_PRIMARY NUMBER(13,   4)
--[ON COMMIT PRESERVE ROWS]
CREATE GLOBAL succeeded.
declare
l_open_receipt_select_1 varchar2(4000) :=
    'select 1, 1, 1, 12.05, 12.05 from dual';
l_open_receipt_select_2 varchar2(4000) :=
    'select 2, 2, 1, 17.05, 17.05 from dual';
l_open_receipt_select_3 varchar2(4000) :=
    'select 3 loc_acct_id,
1 currency_id,
27.05 amt,
3 acct_id,
27.05 amt_primary
from dual';
l_open_receipt_select_4 varchar2(4000) :=
    'select 4 loc_acct_id,
1 currency_id,
24.35 amt,
4 acct_id,
24.35 amt_primary
from dual';
l_ins_stmt varchar2(4000);
begin
-- If the column order is known ahead of time and is consistent
-- You can use this form:
l_ins_stmt :=
    'insert into ar_trial_rcpt (
loc_acct_id, acct_id, currency_id, amt, amt_primary
) '||l_open_receipt_select_1||
' union all '||
l_open_receipt_select_2;
execute immediate l_ins_stmt;
-- If the column order is NOT known ahead of time or is INconsistent
-- You can use this form:
l_ins_stmt :=
    'insert into ar_trial_rcpt (
loc_acct_id, acct_id, currency_id, amt, amt_primary
select loc_acct_id
, acct_id
, currency_id
, amt
, amt_primary
from ('||l_open_receipt_select_3||')
union all
select loc_acct_id
, acct_id
, currency_id
, amt
, amt_primary
from ('||l_open_receipt_select_4||')';
execute immediate l_ins_stmt;
end;
anonymous block completed
select * from ar_trial_rcpt
LOC_ACCT_ID ACCT_ID CURRENCY_ID AMT    AMT_PRIMARY
1           1        1           12.05 12.05
2           2        1           17.05 17.05
3           3        1           27.05 27.05
4           4        1           24.35 24.35
4 rows selected

How to transport table Index

Hi All,
Any ideas how to transport a table index on an IO, we can create the index but its not allowing us to change the package name, its still in $tmp.
Thanks in advance,
BW Dev.

Hi,
You will have to collect it. Choose the table on which your index you have created.
From the menu option select GOTO --> Object directory entry.
You will be displayed with $tmp as package. Make change in the pacakage to the relevant one.
On Executing the change you will be prompted with a request no. select the one. and transport to your required system.
Hope this helps!!!

How to obtain the table index in word use LabVIEW Report Generation Toolkit for Microsoft Office

I created a word templete and it had several tables. When I use the "Word Edit Cell" function in LabVIEW Report Generation Toolkit for Microsoft Office, the function need "table index", and I didn't find any function to get or set the table index in word document. How can I achieve my attention to write value to specified table cell using the "Word Edit Cell" function?
Thanks for reply!
YangAfreet

Hi yangafreet
You do not need to get the table index for the word edit cell.vi from anywhere. LabVIEW will automatically index all the tables in the document. See the attatched vi for an example.
Rich
Attachments:
Table Edit.vi ‏23 KB

To Use Cursor or TYPE table Index by PLS_integer

Hi All,
Let's see if I have table with no. of records 19,26,20,000.
If I want to loop through all the records which will be a optimized way To Use Cursor or TYPE table Index by PLS_integer.
Please guide.
Thanks.

What is it you want to do to/with the rows you're looping through?
Ideally you want to avoid looping, as that's row by row (aka slow by slow) processing and it's expensive time-wise.
If you're doing DML (insert/update/delete) then you're best off doing it in one sql statement, rather than looping.

Fact Table index vs BIA Index

BIA gurus..
Prior to our BIA implementation we had the drop and rebuild index process variants in our process chains.
Now after the BIA implementation we have the BIA index roll-up process variant included in the process chain.
Is it still required to have the drop and rebuilt index process variants during data load ?
Do the infocube fact table indexes ever get hit after the BIA implementation ?
Thanks,
Ajay Pathak.

I think you still need the delete/create Index variants as it not only helps in query performance but also speeds up the load to your cubes.
Documentation in Perfomance tab:
"Indices can be deleted before the load process and after the loading is finished be recreated. This accelerates the data loading. However, simultaneous read processes to a cube are negatively influenced: they slow down dramatically. Therefore, this method should only be used if no read processes take place during the data loading."
More details at:
[http://help.sap.com/saphelp_nw70/helpdata/EN/80/1a6473e07211d2acb80000e829fbfe/frameset.htm]

IN_WRONG_TABLESPACE, object: table/index

Similar Messages

Maybe you are looking for