ORA-01555 while creating indexes

Similar Questions

• ORA-02327: cannot create indexes on the LOB data type expression

  DB 10.2.0.4
  DB 5.2
  
  I am not able to move lobindex and lobsegment. While try occurs below error
  
  SQL > ALTER INDEX dev. "" SYS_IL0000718396C00002$ $"REBUILD THE TABLESPACE DATA_TEMP;
  ALTER INDEX dev. "" SYS_IL0000718396C00002$ $"REBUILD TABLESPACE DATA_TEMP
  *
  ERROR on line 1:
  ORA-02327: cannot create indexes on the LOB data type expression
  
  Thank you
  
  Published by: user13382934 on October 16, 2012 14:05

  correct syntax is
  ALTER TABLE.

  MOVE the LOB ()
  STORE AS (tablespace );

  Where is a name of the / columns LOB, not the name of the segment. Moving type LOB data will move its indexes as well.

• ORA-22913 while creating a TABLE QUEUE type "typed".

  Hi guys:
  
  I'm trying to recreate a [AskTom post | http://asktom.oracle.com/pls/apex/f?p=100:11:0:P11_QUESTION_ID:8760267539329], but with one difference. My Type of Oracle contains a field that is an another Type of Oracle, and when I try to create a QUEUE_TABLE, I got the ORA-22913.
  
  Here are my steps:
  
  create or replace TYPE PODTL_TYPE AS OBJECT
  (
  VARCHAR2 (25), point
  ref_item varchar2 (25).
  physical_location_type varchar2 (1).
  physical_location number (10),
  physical_qty_ordered number (12.4).
  unit_cost number (20.4).
  origin_country_id VARCHAR2 (3),
  supp_pack_size number (12.4).
  date of earliest_ship_date,
  date of latest_ship_date,
  pickup_loc varchar2 (250).
  pickup_no varchar2 (25).
  packing_method varchar2 (6).
  round_lvl varchar2 (6).
  door_ind varchar2 (1).
  PRIORITY_LEVEL number (1).
  new_item varchar2 (1).
  VARCHAR2 (1) quarantine,.
  rcvd_unit_qty number (12.4).
  tsf_po_link_id number (10),
  cost_source varchar2 (4).
  date of est_in_stock_date
  );
  
  /
  
  create or replace TYPE PODtl_coll in the PODTL_TYPE table;
  
  /
  
  create or replace TYPE PODesc AS OBJECT
  (
  doc_type varchar2 (1).
  order_no varchar2 (10),
  order_type varchar2 (9).
  order_type_desc varchar2 (250).
  Dept. number 4,
  dept_name varchar2 (120),
  buyer number 4
  Buyer_Name varchar2 (120),
  provider varchar2 (10),
  promotion number (10),
  prom_desc varchar2 (160).
  qc_ind varchar2 (1).
  date of not_before_date,
  date of not_after_date,
  date of otb_eow_date,
  date of earliest_ship_date,
  date of latest_ship_date,
  date of close_date,
  conditions varchar2 (15).
  terms_code varchar2 (50).
  freight_terms varchar2 (30),
  cust_order varchar2 (1).
  payment_method varchar2 (6).
  payment_method_desc varchar2 (40),
  backhaul_type varchar2 (6).
  backhaul_type_desc varchar2 (40),
  backhaul_allowance number (20.4).
  ship_method varchar2 (6).
  ship_method_desc varchar2 (40),
  purchase_type varchar2 (6).
  purchase_type_desc varchar2 (40),
  status varchar2 (1).
  ship_pay_method varchar2 (2),
  ship_pay_method_desc varchar2 (40),
  fob_trans_res varchar2 (2),
  fob_trans_res_code_desc varchar2 (40),
  fob_trans_res_desc varchar2 (250).
  fob_title_pass varchar2 (2),
  fob_title_pass_code_desc varchar2 (40),
  fob_title_pass_desc varchar2 (250).
  vendor_order_no varchar2 (15).
  exchange_rate number (20,10).
  factory varchar2 (10),
  factory_desc varchar2 (240).
  Agent varchar2 (10),
  agent_desc varchar2 (240).
  discharge_port varchar2 (5).
  discharge_port_desc varchar2 (150).
  lading_port varchar2 (5).
  lading_port_desc varchar2 (150).
  bill_to_id varchar2 (5).
  freight_contract_no varchar2 (10),
  po_Type varchar2 (4).
  po_type_desc varchar2 (120),
  pre_mark_ind varchar2 (1).
  currency_code VARCHAR2 (3),
  contract_no number (6).
  pickup_loc varchar2 (250).
  pickup_no varchar2 (25).
  date of pickup_date,
  date of app_datetime,
  comment_desc varchar2 (2000).
  PODtl PODtl_coll
  );
  
  /
  
  Here are my 3 types of Oracle. When I try to create the QUEUE TABLE:
  
  
  DBMS_AQADM. () CREATE_QUEUE_TABLE
  Queue_table = > "PODESC_QUEUE_TABLE"
  Queue_payload_type = > 'PODesc ',.
  Multiple_consumers = > TRUE);
  
  END;
  
  I got the following error:
  
  22913 00000 - "must specify the name of the table for the nested table column or attribute.
  * Cause: The storage clause is not specified for a column in a nested table
  or an attribute.
  * Action: Specify the clause table nested for the nested table storage
  column or attribute.
  
  
  How can I solve this?

  Welcome to the forum!

  Every time you post please provide the Oracle version 4-digit (result of SELECT * FROM V$ VERSION).
  >
  I'm trying to recreate a [AskTom post | http://asktom.oracle.com/pls/apex/f?p=100:11:0:P11_QUESTION_ID:8760267539329], but with one difference. My Type of Oracle contains a field that is an another Type of Oracle, and when I try to create a QUEUE_TABLE, I got the ORA-22913.
  >
  You cannot use a NESTED in the charge of the message table.

  Chapter 4 Managing Oracle Streams AQ queues User Guide Advanced
  http://docs.Oracle.com/CD/B28359_01/server.111/b28420/manage.htm
  >
  4.6.4 collection Types of Message payloads

  You cannot create a message payload using a VARRAY that is not itself contained within an object. You also cannot currently use an even NESTED table as an object embedded in a message payload. However, you can create an object type that contains one or more VARRAYs and create a queue table that is based on this type of object, as shown in example 4-1.

  Example 4-1 creation of objects containing VARRAYs

  CREATE TYPE number_varray AS VARRAY (32) OF NUMBER;
  CREATE TYPE embedded_varray AS OBJECT (col1 number_varray);
  RUN DBMS_AQADM. () CREATE_QUEUE_TABLE
  queue_table-online "QT."
  queue_payload_type-online 'embedded_varray');
  >
  You need to change your payload to a supported type.

• ORA-00600 while creating the queue table

  Hello
  I'm getting
  ERROR on line 1:
  ORA-00600: internal error code, arguments: [kcbz_check_objd_typ], [0], [0,]
  [1], [], [], [], []
  ORA-06512: at "SYS." DBMS_AQADM_SYS', line 2830
  ORA-06512: at "SYS." DBMS_AQADM', line 58
  ORA-06512: at line 2
  When creating table queue.
  The problem seems to be the name of the created object. Here's the script:
  
  CREATE OR REPLACE TYPE BNA_CHG_EVENT AS OBJECT
  (
  NUMBER (2),
  INTEGER ID
  );
  /
  
  (it works fine)
  
  BEGIN
  SYS. DBMS_AQADM. CREATE_QUEUE_TABLE
  (
  QUEUE_TABLE = > 'BNA_CHG_EVENT_QT '.
  , QUEUE_PAYLOAD_TYPE = > 'BNA_CHG_EVENT '.
  "Compatible = > ' 10.0.0 '.
  , SORT_LIST = > 'ENQ_TIME, PRIORITY '.
  , MULTIPLE_CONSUMERS = > TRUE
  , MESSAGE_GROUPING = 0 >
  , SECURE = > FALSE
  );
  End;
  /
  
  (it crashes with ora-600).
  When I change the name of BNA_CHG_EVENT_QT to the BNA_CHG_EVENT_OT object is created without errors.
  Database is Oracle Database 10 g Enterprise Edition Release 10.2.0.4.0.
  
  Any suggestions on the cause of the error?
  Thanks in advance
  
  ARO
  Kuba Gasiorowski

  ERROR on line 1:
  ORA-00600: internal error code, arguments: [kcbz_check_objd_typ], [0], [0,]
  [1], [], [], [], []
  ORA-06512: at "SYS." DBMS_AQADM_SYS', line 2830
  ORA-06512: at "SYS." DBMS_AQADM', line 58
  ORA-06512: at line 2

  Check on the support of Oracle
  If you have upgraded DB to 10g, check 8247215 Bug

  Workaround
  A temporary workaround is to set dbblock_check_objtyp = false

• Active Data Guard and Undo and ora-01555

  Hello
  
  We have a 11.1.0.7 two nodes primary CARS with a physical standby single instance Active Data Guard. When you run an export datapump since the day before, we get an ORA-01555 while the undo_retention is well beyond the duration of watering for export.
  
  I'm looking to better understand the cancellation as part of Active Data Guard. Is there any dependency for cancellation between the primary (s) and the day before? Are the settings Cancel (undo_retention, tablespace... undo size) on the primary and independent intelligence on the other?
  
  Thank you.

  The wait is a physical expectation. An exact copy of the primary. The cancellation to sleep is controlled by it again come from the primary. When the cancellation is replaced in the primary, he gets crushed to the standby regardless of what it executes. You cannot cancel maintained around more on the eve, it is a replica of the primary.

  Increasing the undo tablespace and the primary undo_retention allows more Cancel to keep both primary and standby, but Eve is always controlled by the direction of the primary to cancel it. Of course, you must change the setting to sleep too so that everything is the same when you made the day before to a primary database.

  I hope this helps.

  Larry

• Spatial index error while creating an index for a column GeoRaster

  Hi all
  
  Several months ago, I inserted 12 map PNG Raster files in Oracle as GeoRaster data. I then looked into MapBuilder to verify that they have been charged, and as they appear, it seems to suggest that they were.
  
  Today, however, I realized that I had not created an entry for USER_SDO_GEOM_METADATA or a spatial index. That's why I tried to do it by using the code below. When I made an entry in USER_SDO_GEOM_METADATA, I didn't add .spatialextent after the column name, web_raster_map. But while reading the manual MapViewer I decided that it was necessary to create a new entry. However, the error message displayed at the end, was the same in each case. If anyone has any ideas on what I can hurt, I would be grateful.
  
  Is the entries abscissa-x and the ordered is wrong? Should this be X and Y, and if that resolves the errors? I've been using a script I created previously to vector data and adapting.
  

  INSERT INTO USER_SDO_GEOM_METADATA
  (TABLE_NAME,
  COLUMN_NAME,
  DIMINFO,
  SRID)
  VALUES (
  'WEB_RASTER_MAP_FILE',
  'web_raster_map.spatialextent',
  SDO_DIM_ARRAY( -- full grid size goes here
  SDO_DIM_ELEMENT('eastings-x', -3273.58473839662, -8471.66, 0.005),
  SDO_DIM_ELEMENT('northings-y', -9694.76, -1632.88473839662, 0.005)),
  96163497); -- this is a user created srid
  commit;
  
  CREATE INDEX WEB_RASTER_MAP_FILE_IDX ON WEB_RASTER_MAP_FILE (web_raster_map)
     INDEXTYPE IS MDSYS.SPATIAL_INDEX;
  commit;

  Error message was:

  Error starting at line 14 in command:
  CREATE INDEX WEB_RASTER_MAP_FILE_IDX ON WEB_RASTER_MAP_FILE (web_raster_map)
     INDEXTYPE IS MDSYS.SPATIAL_INDEX
  Error at Command Line:14 Column:13
  Error report:
  SQL Error: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
  ORA-13200: internal error [Unsupported Type] in spatial indexing.
  ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
  29855. 00000 -  "error occurred in the execution of ODCIINDEXCREATE routine"
  *Cause:    Failed to successfully execute the ODCIIndexCreate routine.
  *Action:   Check to see if the routine has been coded correctly.
  commit succeeded.

  Kind regards
  
  Tim
  
  Published by: user467357 on March 23, 2009 17:45
  To add an additional comment.

  Tim,
  You must create the index on web_raster_map.spatialextent.
  The create index must therefore:

  CREATE the INDEX WEB_RASTER_MAP_FILE_IDX ON WEB_RASTER_MAP_FILE (web_raster_map.spatial_extent)
  INDEXTYPE IS MDSYS. SPATIAL_INDEX;

• ORA-00934: function of group not allowed error when creating index

  ORA-00934: Group feature is not allowed here
  

  create index idx_emp on emp(max(install_time))

  Hello

  Daniel wrote:
  ORA-00934: Group feature is not allowed here

  create index idx_emp on emp(max(install_time))
  

  It's true. It is documented in the Manual of the SQL language

  Restrictions on Function-based Indexes 
  
  Function-based indexes are subject to the following restrictions:
  ...
  The column_expression cannot contain any aggregate functions.
  

  MAX is an aggregate function.

  What problem are you trying to solve? If you could create an index like this, how would you use it?
  Explain what you need to do, and someone will help you find a good way to do it.

• Table exists but still error: ORA-00942, isn't able to create indexes: Help

  It's my script... the table FLASH_SALES_BY_STORE_AND_HOUR exist in my database, so why I get the error message.
  ERROR on line 1:
  ORA-00942: table or view does not exist
  
  
  
  Here is my script.
  
  ASK for IDX_SALES_STORE_DEL
  
  CREATE INDEX IDX_SALES_STORE_DEL ON FLASH_SALES_BY_STORE_AND_HOUR (STORE_ID, TRUNC (LOCAL_DATE))
  TABLESPACE 'FLASH '.
  STORAGE
  (
  DEFAULT USER_TABLES
  )
  /
  
  QUICK creation IDX_SALES_STORE_VIEWexit
  
  
  CREATE INDEX IDX_SALES_STORE_VIEW ON FLASH_SALES_BY_STORE_AND_HOUR (STORE_ID, TRUNC (LOCAL_DATE), DEPARTMENT)
  TABLESPACE 'FLASH '.
  STORAGE
  (
  DEFAULT USER_TABLES
  )
  /

  Please, re - run the script as the user who owns the table...

  Otherwise, add the schema name before the name of the index (if not index will be created under SYS) and table name (since you missed the creation of synonym).

  HTH,
  Thierry

• Error while creating or rebuilding Oracle text Lexer keyword index

  Hi all
  I am getting following error when I create oracle text indexes using lexer & keyword in the list of stopwords.
  Please help me if any body know.
  Thanks in advance.
  
  
  Error from the 1 in the command line:
  CREATE INDEX TXT_INX_TEXT_SEARCH ON TEXT_SEARCH (BFILE_DOC)
  
  Post INDEXTYPE IS "CTXSYS. "" (LOCAL) CONTEXT.
  PARTITION SETTINGS "BEFORE_2007" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q1_2007" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q2_2007" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q3_2007" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q4_2007" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q1_2008" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q2_2008" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q3_2008" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q4_2008" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q1_2009" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q2_2009" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q3_2009" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q4_2009" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "THE_REST' ('LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)')
  )
  Error in the command line: 1 column: 13
  Error report:
  SQL error: ORA-29855: error when executing routine ODCIINDEXCREATE
  ORA-20000: Oracle text error:
  DRG-11000: invalid keyword LEXER
  ORA-06512: at "CTXSYS. DRUE", line 160
  ORA-06512: at "CTXSYS. TEXTINDEXMETHODS', line 365
  29855 00000 - "an error occurred in the execution of routine ODCIINDEXCREATE.
  * Cause: Cannot run the ODCIIndexCreate routine.
  * Action: Check if the routine was coded correctly.
  
  
  Kind regards
  Jack R.

  Hello

  It works if you put a clause of additional PARAMETERS to the end, so the creation looks like:
  CREATE INDEX TXT_INX_TEXT_SEARCH ON TEXT_SEARCH (BFILE_DOC)
  INDEXTYPE IS "CTXSYS. "" (LOCAL) CONTEXT.
  PARTITION SETTINGS "BEFORE_2007" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q1_2007" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q2_2007" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q3_2007" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q4_2007" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q1_2008" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q2_2008" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q3_2008" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q4_2008" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q1_2009" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q2_2009" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q3_2009" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "Q4_2009" ("LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)"),
  PARTITION SETTINGS "THE_REST' ('LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)')
  )
  PARAMETERS ('LEXER dd_lexer list of words EMPTY dd_stoplist SYNC (ON COMMIT)')<==>

  Hope this helps

  Herald tiomela

• ORA-02354: Error exporting/importing data, ORA-01555: snapshot too old: rollback segment number with the name "" too small

  Hello

  I am getting below error while taking expdp backup table of BLOB.

  ORA-31693: Data Table object 'HCLM_ADMIN '. "' SCAN_UPLOADEDFILES_TEMP ' failed to load/unload and being ignored because of the error:

  ORA-02354: Error exporting/importing data

  ORA-01555: snapshot too old: rollback segment number with the name "" too small

  ORA-22924: snapshot too old

  ORA-31693: Data Table object 'HCLM_ADMIN '. "' TPA_FAXWATCHER ' failed to load/unload and being ignored because of the error:

  ORA-02354: Error exporting/importing data

  ORA-01555: snapshot too old: rollback segment number with the name "" too small

  ORA-22924: snapshot too old

  We have already set aside retention to 50000 .table structure are:

  SQL > show Cancel parameter

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  UNDO_MANAGEMENT string AUTO

  UNDO_RETENTION integer 50000

  undo_tablespace string UNDOTBS1

  SQL > alter table hclm_admin. SCAN_UPLOADEDFILES_TEMP modify lob (FILE_BLOB) (RETENTION);

  Modified table.

  SQL > select nom_de_colonne, pctversion and retention

  from dba_lobs where owner = 'HCLM_ADMIN' and table_name = "SCAN_UPLOADEDFILES_TEMP";

  COLUMN_NAME

  --------------------------------------------------------------------------------

  PCTVERSION RETENTION

  ---------- ----------

  FILE_BLOB

  50000

  SQL > alter table hclm_admin. TPA_FAXWATCHER modify lob (FILEDATA_BLOB) (RETENTION);

  Modified table.

  SQL > select column_name, pctversion and retention of dba_lobs where owner = 'HCLM_ADMIN' and table_name = "SCAN_UPLOADEDFILES_TEMP";

  Column_name PCTVERSION RETENTION

  ---------- ----------

  FILE_BLOB

  50000

  CREATE TABLE HCLM_ADMIN. TPA_FAXWATCHER

  (

  FILENAME_VAR VARCHAR2 (50 BYTE),

  DATE OF CREATED_DATE_DTE,

  FILEPATH_VAR VARCHAR2 (100 BYTE),

  DATE OF TIMESTAMP_DTE,

  FAXNO_VAR VARCHAR2 (15 BYTE),

  DEPARTMENT_VAR VARCHAR2 (50 BYTE),

  REQUESTTYPE_VAR VARCHAR2 (50 BYTE),

  TAGTO_VAR VARCHAR2 (50 BYTE),

  REMARK_VAR VARCHAR2 (1000 BYTE),

  DOCTYPE_VAR VARCHAR2 (50 BYTE),

  TAGTOVALUE_VAR VARCHAR2 (50 BYTE),

  DOCTYPE_OTHER_VAR VARCHAR2 (50 BYTE),

  HEGIC_NO_VAR VARCHAR2 (50 BYTE),

  RECORDNO_NUM NUMBER OF NON-NULL,

  FILEDATA_BLOB BLOB,

  DATE OF FAXLOCKDATE_DTE,

  NUMBER OF FAXLOCKSTATUS_VAR

  FAXLOCKBYUSER_VAR VARCHAR2 (50 BYTE)

  )

  (STORE AS) LOB (FILEDATA_BLOB)

  TABLESPACE HCLM_ALERTSVC

  ALLOW ONLINE STORAGE

  8192 CHUNK

  RETENTION

  NOCACHE

  LOGGING

  INDEX)

  TABLESPACE HCLM_ALERTSVC

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  ))

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  ))

  TABLESPACE HCLM_ALERTSVC

  PCTUSED 0

  PCTFREE 10

  INITRANS 1

  MAXTRANS 255

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  )

  LOGGING

  NOCOMPRESS

  NOCACHE

  NOPARALLEL

  MONITORING;

  ALTER TABLE HCLM_ADMIN. (ADD) TPA_FAXWATCHER

  KEY ELEMENTARY SCHOOL

  (RECORDNO_NUM)

  USING INDEX

  TABLESPACE HCLM_ALERTSVC

  PCTFREE 10

  INITRANS 2

  MAXTRANS 255

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  ));

  CREATE TABLE HCLM_ADMIN. SCAN_UPLOADEDFILES_TEMP

  (

  NUMBER OF TEMPID_NUM

  SESSION_ID VARCHAR2 (200 BYTE),

  NUMBER OF UPLOADFILE_NUM

  NUMBER OF DOCNO_NUM

  NUMBER OF SCANJOB_NUM

  FILENAME_VAR VARCHAR2 (200 BYTE),

  FILETYPE_VAR VARCHAR2 (200 BYTE),

  FILE_BLOB BLOB,

  VARCHAR2 (200 BYTE) FLAG,

  NUMBER OF USERID_NUM

  CREATED_DATE DATE

  )

  (STORE AS) LOB (FILE_BLOB)

  TABLESPACE PHCLMDBTBS

  ALLOW ONLINE STORAGE

  8192 CHUNK

  RETENTION

  NOCACHE

  LOGGING

  INDEX)

  TABLESPACE PHCLMDBTBS

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  ))

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  ))

  TABLESPACE PHCLMDBTBS

  PCTUSED 0

  PCTFREE 10

  INITRANS 1

  MAXTRANS 255

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  )

  LOGGING

  NOCOMPRESS

  NOCACHE

  NOPARALLEL

  MONITORING;

  Kind regards

  Hello

  First check the lob corrupt as:

  SQL > create table corrupted_lob_data (corrupted_rowid rowid);

  Table created.

  SQL > set off concat

  SQL >

  declare

  SQL > error_1555 exception;

  pragma exception_init (error_1555,-1555);

  number num.

  Start

  for cursor_lob in (select rowid r, & lob_column of table_owner. & table_with_lob) loop

  Start

  NUM: = dbms_lob.instr (. cursor_lob & lob_column, hextoraw ('889911'));

  exception

  When error_1555 then

  insert into corrupted_lob_data values (cursor_lob.r);

  commit;

  end;

  end loop;

  end;

  2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

  17.

  Enter the value of lob_column: FILE_BLOB

  Enter the table_owner value: hclm_admin

  Enter the value of table_with_lob: SCAN_UPLOADEDFILES_TEMP

  former 6: for cursor_lob in (select rowid r, & lob_column of table_owner. & table_with_lob) loop

  6 news: for cursor_lob (select rowid r, FILE_BLOB of hclm_admin loop SCAN_UPLOADEDFILES_TEMP.)

  old 8: num: = dbms_lob.instr (. cursor_lob & lob_column, hextoraw ('889911'));

  8 new: num: = dbms_lob.instr (cursor_lob. FILE_BLOB, hextoraw ('889911'));

  PL/SQL procedure successfully completed.

  SQL > select * from corrupted_lob_data;

  CORRUPTED_ROWID

  ------------------

  AAASF/AAKAABacyAAA

  To resolve this problem, we have 3 options

  (1) to restore and recover the LOB segment using physical backup.

  (2) empty LOBs affected using the UPDATE, as mentioned in the Note 787004.1statement:

  SQL > update SCAN_UPLOADEDFILES_TEMP

  Set FILE_BLOB = empty_blob()

  where rowid in (select corrupted_rowid

  of corrupted_lob_data);

  SQL > commit;

  (3) perform the export, excluding the corrupt ROWID. by adding the following to export command parameter

  Query =------"where rowid not in (\'AAASF/AAKAABacyAAA\'\) \ \" "

  Kind regards

  Alok Dwivedi

• ORA-01555: snapshot too old: rollback segment number 7 with the name ' _SYSSMU7_1291102260$ ' too small

  
  Hello

  I get ORA-01555 error when performing the following procedure.

  CREATE OR REPLACE PROCEDURE proc1 (text in varchar2, varchar2 data type)
  AS

  L_STMT varchar2 (6000);
  number of l_exists;
  v_code NUMBER;
  v_errm VARCHAR2 (400);
  tabnam VARCHAR2 (100);
  colnam VARCHAR2 (100);
  
  cursor tab_cur is
  Select utc.table_name, utc.column_name, utc.data_type
  from user_tables utb, user_tab_columns utc
  where utc.table_name = utb. Table-name
  and NOT EXISTS (SELECT ' X'
  OF tl table_list
  WHERE the tl.table_name = utc.table_name)
  AND utc.data_type = 'VARCHAR2'
  ORDER OF THE UTC. TABLE_NAME;

  TYPE table_info_tt IS TABLE OF tab_cur % ROWTYPE;
  l_tab table_info_tt;

  BEGIN

  insert into m_log values (SYSTIMESTAMP, 'Start time');
  commit;

  OPEN tab_cur.
  LOOP
  
  Get the tab_cur COLLECT in BULK WITHIN the limits of the 1000 l_tab;
  
  FOR indx in 1.l_tab.count
  LOOP
  
  BEGIN
  
  L_STMT: = ' SELECT COUNT (1)
  OF ' | l_tab (indx). TABLE_NAME | ' WHERE ' | l_tab (indx). Column_name |' =: intext';
  run immediately L_STMT in l_exists using text;
  
  tabnam: = l_tab (indx). TABLE_NAME;
  colnam: = l_tab (indx). COLUMN_NAME;
  
  EXCEPTION
  
  WHILE OTHERS THEN
  
  L_STMT: = ' SELECT COUNT (1)
  OF ' | l_tab (indx). TABLE_NAME | » OÙ ' ||' » ' || l_tab (indx). COLUMN_NAME |' "' |' =: intext';
  run immediately L_STMT in l_exists using intext;
  
  tabnam: = l_tab (indx). TABLE_NAME;
  colnam: = l_tab (indx). COLUMN_NAME;
  END;
  
  IF (l_exists = 0) then
  
  null;
  
  on the other
  
  insert into ADM_TEXT_INFO
  values (l_tab (indx). Table_name, l_tab (indx). Column_name, text, data type);
  
  commit;
  
  END IF;
  
  END LOOP;
  
  EXIT WHEN l_tab.count = 0;
  
  END LOOP;
  
  CLOSE Tab_cur;
  
  insert into m_log values ("SYSTIMESTAMP," over time ");
  commit;
  exception
  while others then
  v_code: = SQLCODE;
  v_errm: = SUBSTR (SQLERRM, 1, 200);
  INSERT INTO VALUES error_log (v_code, v_errm, SYSTIMESTAMP);
  commit;
  DBMS_OUTPUT. Put_line (' error code:' | v_code |) ': ' || v_errm);
  
  END;
  /

  Details of database version are the following:

  Oracle Database 11 g Enterprise Edition Release 11.1.0.7.0 - 64 bit Production

  PL/SQL Release 11.1.0.7.0 - Production

  CORE Production 11.1.0.7.0

  AMT for Linux: Version 11.1.0.7.0 - Production

  NLSRTL Version 11.1.0.7.0 - Production

  
  SQL > show Cancel parameter

  VALUE OF TYPE NAME
  ------------------------------------ ----------- --------
  UNDO_MANAGEMENT string AUTO
  UNDO_RETENTION around 2000
  undo_tablespace string UNDOTBS1

  I changed the undo_retention and checked, it still gives the same error. The undo tablespace size is 23.7 GB (GB 23 is free, only 27 MB are used).

  Can anyone please suggest me, what could be the problem.

  Thank you

  SB2011

  Have a look here:

  Ask Tom & quot; SQL to retrieve a columns & quot;

• ORA-01555 - Tuning for the UNDO tablespace.

  Dear DBA Kings/Queens,
  
  I often "ORA-01555 snapshot too old error" due to the special delete statement. Which removes the lines about 50 000 all day as a batch. Eventhough, I reduced to 50 000 to 10 000 and 1000. No luck.
  Can someone tell me how to set UNDO tablespace.
  -----------------------------------------------------------------------------
  Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64 bit Production
  PL/SQL Release 9.2.0.7.0 - Production
  CORE 9.2.0.7.0; Production
  AMT for Solaris: release 9.2.0.7.0 - Production
  NLSRTL Version 9.2.0.7.0 - Production
  -----------------------------------------------------------------------------
  SQL > show Cancel parameter
  
  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  UNDO_MANAGEMENT string AUTO
  UNDO_RETENTION integer 10800
  undo_suppress_errors Boolean TRUE
  undo_tablespace string UNDOTBS1
  -----------------------------------------------------------------------------
  
  Size in GB:
  
  TOTAL USED FREE USED_PCNT NOM_TABLESPACE
  ------------------------------ ---------- ---------- ---------- ----------
  UNDOTBS1 13.5; 1.34; 12.17; 9.89

  Which removes the lines about 50 000 all day as a batch

  Has often committed?
  -do not commit frequently.

  -Increase the setting "undo_retention.

  -reduce the duration of operation (plan use of execution to check your query)... perhaps may create index. Or to commit all the 5000 rows

  -For collecting statistics on the table

  Edited by: Surachart Opun (HunterX) July 23, 2009 12:04 AM

• CREATE INDEXES online is waiting for the TX = 4 mode

  Hello

  I have a strange blocking problem where an INDEX CREATE LINE is waiting for a transaction that did only inserted a line in the parent table.

  Wait is mode TX = 4 (not TM locks) and I currently have it reproduced only on 11.2.0.3 and 11.2.0.4

  Easy to replicate the schema SCOTT:

  Session 1:

  SQL > set time on

  14:54:58 SQL > insert into SCOTT. Dept (DEPTNO, dname) values (50, 'test');

  1 line of creation.

  Session 2;

  14:55:24 SQL > create index test on SCOTT. EMP (ename) online;

  It's waiting ' enq: TX - line lock conflict ":"

  SQL > select sid, chain_signature from v$ wait_chains where blocker_is_valid = 'TRUE '.

  SID CHAIN_SIGNATURE

  ---------- ----------------------------------------------------------------------

  603 ' SQL * Net client message' < ='enq: TX - line lock conflict '

  While waiting to acquire the lock of transaction in mode 4:

  SQL > select * lock gv$ where sid = 603

  INST_ID SELECT ADDR KADDR SID TYPE ID1 ID2 LMODE CTIME BLOCK REQUEST

  ---------- ---------------- ---------------- ---------- ---- ---------- ---------- ---------- ---------- ---------- ----------

  1 00000006CDA05EB8 00000006CDA05F10 603 352577 0 4 0 348 2 AE

  1 00000006CDA06078 00000006CDA060D0 603 DL 779505 0 3 0 308 2

  1 00000006CD9FABE0 00000006CD9FAC38 603 DL 779505 0 3 0 308 2

  1 00007F28001F5028 00007F28001F5088 603 779505 0 2 0 308 2 TM

  1 00007F28001F5028 00007F28001F5088 603 779510 0 4 0 308 2 TM

  1 00000006CD9FA240 00000006CD9FA298 603 779505 0 4 0 308 2 OD

  1 00000006B4F26790 00000006B4F26808 589847 711499 6 0 308 2 TX 603

  1 00000006CDA0ED68 00000006CDA0EDC0 655377 996169 0 4 308 TX 603 0

  I've traced 10046 and 10704:

  broadcast message = obj 29231196672 #= 779514 tim = 1447251053634045

  ksqgtl * mode TX-000f001e-000ad97c = 4 flags = 0 x 10001 timeout = 21474836 *.

  ksqgtl: xcb = 0x6bb322528, ktcdix = 2147483647, topxcb = 0x6bb322528

  ktcipt (topxcb) = 0 x 0

  ksucti: init logon has of txn DID:

  ksqgtl:

  ksqlkdid: 0001-003F-0000AFC4

  ksudidTrace: ksqgtl

  ktcmydid(): 0001-003F-0000AFC4

  ksusesdi: 0001-003F-0000AFC3

  ksusetxn: 0001-003F-0000AFC4

  ksqcmi: TX, f001e, ad97c mode = 4 timeout = 21474836

  2015-11-11 15:11:36.566

  WAITING #140700792578680: nam ='enq: TX - line lock conflict ' ela 42932082 name = | mode = 1415053316 usn < < 16 | location = sequence 983070 = obj 711036 #= 779514 tim = 1447251096566283

  And there is nothing in V$ SESSION leader/block/line current. class obj # is EMP. current sql_id is the CREATE INDEX.

  If anyone has an idea on:

  -Why creating an index in line must wait for transactions that modified only parent table

  -How to continue the investigation

  -can or cannot reproduce in other versions

  Thanks in advance,

  Franck.

  I guess you have a constraint foreign key between emp and Dept.

  It's expected behaviours: since 11.1 any DML at one end of a referential integrity constraint translates into a mode lock 3 taken at the other end, and your phenomenon resembles a side effect of this.

  When you try to create the index online that your session must assume that the other session (holding mode 3 on the emp and dept) may have changed the emp and dept, so it must wait for the session to the commit or rollback.

  (I guess that in principle, he could walk the cancellation of the transaction see if EMP had in fact been changed - but maybe who was considered too complicated to be worth the risk to implement)

  Concerning

  Jonathan Lewis

  Updated - I just did a quick check to reproduce the effect on 11.1.0.7

  For reference - here are a few notes on modes of locking and how the application has changed over time: https://jonathanlewis.wordpress.com/2010/06/21/locks/

• Why I can't create indexes on the table of RDF data

  When I tried to create indexes on the table of RDF data, it always say the table or view does not exist. I created the RDF model using java codes:

  Oracle Oracle = new Oracle ("jdbc:oracle:thin:@localhost:1521:orcl", "system", "123");

  Chart GraphOracleSem = new GraphOracleSem (oracle, "test2");

  
  

  And used the following commands in sqlplus to create indexes:

  SQL >

  SELECT THE SEPARATE OWNER, OBJECT_NAME

  FROM DBA_OBJECTS

  WHERE TYPE_OBJET = 'TABLE '.

  4. AND OBJECT_NAME like ' % TEST2;

  OWNER

  --------------------------------------------------------------------------------

  OBJECT_NAME

  --------------------------------------------------------------------------------

  SYSTEM

  TEST2_NS

  SYSTEM

  RDFB_TEST2

  SYSTEM

  TEST2_TPL

  OWNER

  --------------------------------------------------------------------------------

  OBJECT_NAME

  --------------------------------------------------------------------------------

  SYSTEM

  RDFC_TEST2

  
  

  SQL > connect as sysdba

  Enter the password:

  Connected.

  SQL >

  SQL >

  SQL > select * from TEST2_TPL;

  Select * from TEST2_TPL

  *

  ERROR on line 1:

  ORA-00942: table or view does not exist

  SQL > CREATE INDEX test2_sub_idx ON TEST2_TPL (triple. GET_SUBJECT());

  CREATE INDEX test2_sub_idx ON TEST2_TPL (triple. GET_SUBJECT())

  *

  ERROR on line 1:

  ORA-00942: table or view does not exist

  Hi Shifu,

  It is not recommended to use the SYS or SYSTEM to store/manage schema graph RDF data.

  Can you please try the following in a SQL * more terminal?

  SQL > conn system/eu1

  Connected.

  SQL >

  SQL >

  SQL > create user graphuser identified by graphuser;

  Created by the user.

  SQL > grant connect, resources, unlimited tablespace to graphuser;

  Grant succeeded.

  SQL > conn graphuser/graphuser

  Connected.

  SQL > create table graph_tpl (triple sdo_rdf_triple_s) compress;

  Table created.

  SQL > sem_apis.create_sem_model exec ('graphic', 'graph_tpl', 'three');

  PL/SQL procedure successfully completed.

  SQL > insert into graph_tpl values (sdo_rdf_triple_s ('graph', '', '', ''));

  1 line of creation.

  SQL > select count (1) in the mdsys.rdfm_graph;

  1

  You see the same result?

  Thank you

  Zhe Wu

• ORA-19504: cannot create the file '+ DATA '.

  Hello everyone.

  This is the scenario:

  We have a test server that is used to restore daily backups of the Production database. Restore us the database with the same SID as the production one.

  For specific reasons, we need create a second database (with a different SID) on this server with an older backup from the production one. To realize that I'm trying to use a part of the "DUPLICATE without connection to the target" tutorials on the web.

  I tried the simple guide that I found which is:

  (1) copy the backup files cold /somedirectory

  (2) start OLD database with nomount

  (3) connect RMAN with OLDER as an auxiliary

  (4) run the following: DUPLICATE DATABASE FOR OLD BACKUP LOCATION ' / somedirectory' NOFILENAMECHECK.

  Here's the result (I deleted some lines because of the size of it):

  ----------------------

  RMAN > ProdDB to OlderDB DUPLICATE DATABASE

  2 > LOCATION of BACKUP "/ home/oracle/OlderBackupFiles.

  3 > NOFILENAMECHECK.

  4 >

  From October 1, 14 Db double

  content of Script memory:

  {

  clone of SQL 'alter system set control_files =

  "+DATA/OlderDB/controlfile/current.829.859839217" comment =

  ' Set by RMAN "scope = spfile;

  clone of SQL 'alter system set = db_name

  "ProdDB" comment =

  ' Modified by RMAN duplicate "scope = spfile;

  clone of SQL 'alter system set db_unique_name =

  "OlderDB" comment =

  ' Modified by RMAN duplicate "scope = spfile;

  clone to stop immediately;

  Start clone force nomount

  Restore controlfile primary clone of ' / home/oracle/OlderDB/controlfile_ProdDB_20141001_4159.bkp';

  change the clone database mount;

  }

  execution of Script memory

  SQL statement: alter system set control_files = comment "+DATA/OlderDB/controlfile/current.829.859839217" = "defined by RMAN" scope = spfile

  SQL statement: change the system db_name set = comment "ProdDB" = "modified by RMAN duplicate" scope = spfile

  SQL statement: alter system set db_unique_name = comment "OlderDB" = "modified by RMAN duplicate" scope = spfile

  (...)

  From restoration to 1 October 14

  allocated channel: ORA_AUX_DISK_1

  channel ORA_AUX_DISK_1: SID = 191 type device = DISK

  channel ORA_AUX_DISK_1: restore the control file

  channel ORA_AUX_DISK_1: restoration complete, duration: 00:00:03

  output file name=+DATA/OlderDB/controlfile/current.829.859839217

  Restoration finished in October 1, 14

  mounted database

  output channel: ORA_AUX_DISK_1

  allocated channel: ORA_AUX_DISK_1

  channel ORA_AUX_DISK_1: SID = 191 type device = DISK

  content of Script memory:

  {

  until the SNA 274262921.

  the value of newname for datafile clone 1 again;

  the value of newname for datafile clone 2 again.

  the value of newname for datafile clone 3 again.

  the value of newname for datafile clone 4 new ones;

  the value of newname for datafile clone 5 again.

  the value of newname for datafile clone 6 again.

  the value of newname for datafile clone 7 again.

  restoration

  database clone;

  }

  (...)

  From restoration to 1 October 14

  using the ORA_AUX_DISK_1 channel

  channel ORA_AUX_DISK_1: from the restore backup set data file

  channel ORA_AUX_DISK_1: specifying datafile (s) to restore from backup set

  channel ORA_AUX_DISK_1: restore datafile 00001 to + DATA

  channel ORA_AUX_DISK_1: restore datafile 00002 to + DATA

  channel ORA_AUX_DISK_1: restore datafile 00003 to + DATA

  channel ORA_AUX_DISK_1: restore datafile 00004 in + DATA

  channel ORA_AUX_DISK_1: restore datafile 00005 to + DATA

  channel ORA_AUX_DISK_1: restore datafile 00006 to + DATA

  channel ORA_AUX_DISK_1: restore datafile 00007 to + DATA

  channel ORA_AUX_DISK_1: reading from the backup /home/oracle/OlderDB/database_ProdDB_20141001_4157.bkp piece

  channel ORA_AUX_DISK_1: ORA-19870: error when restoring the backup /home/oracle/OlderDB/database_ProdDB_20141001_4157.bkp piece

  ORA-19504: cannot create the file '+ DATA '.

  ORA-17502: ksfdcre:4 cannot create the file + DATA

  ORA-15041: diskgroup space 'DATA' exhausted

  switch to the previous backup

  Oracle instance started

  (...)

  content of Script memory:

  {

  clone of SQL 'alter system set = db_name

  "OlderDB" comment =

  ' Restore the original value by RMAN "scope = spfile;

  clone of SQL 'alter system reset db_unique_name scope = spfile;

  clone to stop immediately;

  }

  execution of Script memory

  Errors in the script of the memory

  RMAN-03015: an error has occurred in the script stored memory Script

  RMAN-06136: the auxiliary database ORACLE error: ORA-01507: database not mounted

  ORA-06512: at "SYS." "X$ DBMS_RCVMAN ', line 13466

  ORA-06512: at line 1

  RMAN-05556: not all data files have backups can be recovered on SNA 274262921

  RMAN-03015: an error has occurred in the script stored memory Script

  RMAN-06026: some targets not found - abandonment of restoration

  RMAN-06023: no backup or copy of the file 4 found to restore

  RMAN-06023: no backup or copy of datafile 3 found to restore

  RMAN-06023: no backup or copy of datafile 2 found to restore

  RMAN-06023: no backup or copy of datafile 1 found to restore

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of the command duplicate Db at 15:39:11 01/10/2014

  RMAN-05501: abandonment of duplicate target database

  Complete recovery manager.

  ------------------------------------------------------------------

  The first mistake of the stack was ORA-19504 while trying to restore the backup of the database.

  First thing I took a glance was ASM occupation but it enough available space.

  The second was a permission problem, but it doesn't seem to be the case because RMAN can correctly write the controlfile to ASM.

  One have some advice on what I should look for?

  Thanks in advance sorry for my English.

  Select this option.

  Hello.

  Thanks, but is not the case. As I have said, that the DATA diskgroup has space enough he uses only a single disk in a RAID.

  But I solved my problem... To the auxiliary database, I added the following to the spfile:

  DB_FILE_NAME_CONVERT = '+ DATA/ProdDB', '+ DATA/OlderDB ".

  LOG_FILE_NAME_CONVERT = '+ DATA/ProdDB', '+ DATA/OlderDB ".

  I don't know why, but with these two clauses, it worked well. Perhaps RMAN was trying to restore it to the wrong place?