Trex Index Creation Error
Hi everybody,
Trying to create a nex index (the first one) using the index Administration iview I get the following error:
Index could not be created; creating index failed: general configuration error (Errorcode 2030)
I also obtain the same errorcode running the python script runInstallationTest.py
Everything looks fine in the portal trex monitor (all green lights)
Any help would be very apprecieated.
Hi again Detlev and thanks for your reply,
I'm a bit confused here, take a look of this note:
Note 798575:
Symptom
TREX 6.1 SP9/SR1 index creation failed
Other terms
cannot create allConfig, Windows 2000 2003, create index
Reason and Prerequisites
You have installed TREX 6.1 SP9/SR1 and cannot create an index. The returned message in trace files is like the following: Cannot create allConfig.
Solution
Add the TREX-User to administrotors group:
Choose from Control Panel/Administrative Tools the Computer Management Tool.
Navigate to System Tools/Local Users and Groups
Under users select the TREX-user with right click and choose properties.
In the Member Of tab add the administrators group.
But the installation guide recommends on page 24: "We recommend not giving the user administrative
permissions for security reasons.
If the group sapsys is available, we recommend that you
assign this group to the user."
Sapsys is not available, I think I will try with David's approach.
Similar Messages
-
Index Creation Error, while creating Information space
Hi,
I'm trying to create an Information Space in explorer based
off of a Universe created on a Bex Query from SAP BW.
This
Universe is created in Universe design tool based on BW 7.4, gives below error, while creating report in Web Intelligence based on Universe.
Database error: Failed to execute MDX Query.
Reason occured when starting the parser timeout during
allocate/CPC-CALL.
2) In Explorer everything seems to be working fine with the
Information Space creation up until the point where I need to index it. When I click 'Index' it takes about 5-10
seconds and then fails with the following error
Latest indexing failed
Start Date: 2015/02/11 08:51
End Date: 2015/02/11 08:53
Server, BOHDSIA.ExplorerIndexingServer, generated the
following messages:
Index Creation Failed (
The execution of the specified analysis query
failed.-Database error: A database error has occured. (IES 10901)
Database error: A database error has occured. (IES 10901))
The Bex Query executes successfully in BEx Analyzer and webi
report created with BEX as datasourcePlease see reply at:
http://technet.oracle.com:89/ubb/Forum36/HTML/000661.html -
I'm getting the following error when trying to create an r-tree index:
create index new_gps_idx on gis.new_gps (geometry) indextype is mdsys.spatial_index PARAMETERS('TABLESPACE=INDX')
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-06512: at line 1
I get the error regardless of which tablespace I specify.
I can however create fixed quad-tree indexes with the following command, in the same tablespace:
create index new_gps_idx on gis.new_gps (geometry) indextype is mdsys.spatial_index PARAMETERS('SDO_LEVEL=4');
The error is defined as:
ORA-29855 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.
I have created one r-tree index on a large spatial table, 5633 geometries, in the INDX tablespace. I am not able to create another one.
The INDX tablespace is only 2% used and its size is 200MB.
Any help would be greatly appreciated.
Dave
nullHi David,
Can you try applying the patch (if you haven't already)? Unfortunately I can't rememeber the details of what the symptoms were, and although the patch kit describes a fix there is no corresponding bug in Oracle's bug database. If I remember correctly there was a bug in the values the r-tree code was using for intermediate (temporary) tables created during r-tree index creation.
Sorry I can't pin this down for you.
dan -
Intermedia text index creation error
My intermedia text was working fine, but now when create one index, it failed and it gave me the following error message:
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: ConText error:
ORA-06520: PL/SQL: Error loading external library
ORA-06522: ld.so.1: extprocPLSExtProc: fatal: libskgxp8.so: open failed: No such file or directory
ORA-06512: at "CTXSYS.DRUE", line 122
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 34
ORA-06512: at line 1
The listener itself is fine, is it because some library need to be re-created?
null<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Alexander Bogomolov ([email protected]):
I've installed Intermedia text. During sample index creation i've get following error messages:
ORA-06520: PL/SQL: Error loading external library
ORA-06522: Unable to load DLL
ORA-06512: at "CTXSYS.DRUE", line 126
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 54
ORA-06512: at line 1...
seems to be incorrect NET8 settings. How can I solve this problem?
thanks.
Sorry for bad English. regards!<HR></BLOCKQUOTE>
*** check your listener.ora file
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = oracle_home)
(PROGRAM = extproc)
(SID_DESC =
(GLOBAL_DBNAME = global dbname)
(ORACLE_HOME = oracle_home)
(SID_NAME = sidname)
for the correct location of extproc
null -
ORA-1652: Index creation error
At the time of table re-organisation, Index creation got aborted for the secondary index creation. then we have continued our activity leaving the index creation due to short of System downtime.
Again we have run the sql statment when the sap system is up, then it has thrown an error:
ORA-1652 unable to extend temp segment by 128 in tablespace PSAPTEMP.
In the current system, we are not ready to increase the size of datafile or resizing.where it leads to the increase the size of database.
Here we have option to create a new temp tablespace, will delete after index creation, but while doing this how do we point the new tablespace which is created for this activity.
SAP 4.6c oracle 9 sun solaris.
Kindly advise what can be done. reply ASAPMartin,
We have discussed with the team like,
1. Create new temporary tablespace with desired Size which should be minimum 25GB
CREATE temporary tablespace PSAPTEMP1......
2. If the original tablespace is a default temporary tablespace, set the new tablespace as default temporary tablespace in the database.
SQL> alter database default temporary tablespace PSAPTEMP1;
3. Perform the index creation
4. Make the old tablespace PSAPTEMP as the default temporary tablespace.
SQL> alter database default temporary tablespace PSAPTEMP
5. Drop the new tablespace.
SQL> drop tablespace temp including contents.
Here I have a question, while switching the default temporary tablespace from PSAPTEMP to the much bigger new PSAPTEMP1Tablespace whether this will affect the running transaction.
Any impact on switching the tablespace online..?
We are performing this activity in the online system(running sap system)
Thanks, -
Hello i took an export of iFS schema "ifssys" and tried to import into another database with same set of tablespaces. the tables got created but index creation failed with following error msg.
Oracle error 6510 encountered.
Pl/Sql: unhandled user-defined exception
at CTXSYS.DRIUTL
no data found
at CTXSYS.DRIIMP
problem importing metadata for index
INDEXBLOB_I. index creation will be skipped.
Please note i had given connect, resource,dba and ctxapp role to ifssys user.
Kindly suggest.
Manish Jain.
nullPlease see response at: http://technet.oracle.com:89/ubb/Forum36/HTML/000661.html
-
Index creation error while importing
Hello i took an export of iFS schema "ifssys" and tried to import into another database with sample set of tablespaces. the tables got created but index creation failed with following error msg.
Oracle error 6510 encountered.
Pl/Sql: unhandled user-defined exception
at CTXSYS.DRIUTL
no data found
at CTXSYS.DRIIMP
problem importing metadata for index
INDEXBLOB_I. index creation will be skipped.
Please note i had give connect, resource,dba and ctxapp role to ifssys user.
Kindly suggest.
Manish Jain.Please see reply at:
http://technet.oracle.com:89/ubb/Forum36/HTML/000661.html -
BIA Index creation error due to invalid characters
Hi All,
While creating BIA index on an Infocube the index creation process fails with the following message.
Index for table '/BIC/SSPSEGTXT' is being processed
A character set conversion is not possible.
Parallel indexing process terminated (Task: '4')
Turns out this field is a text field and has characters such as * and + in the description,which is causing this problem.
How do I proceed with the index creation.
Options I have are:
a) Get rid of this field.. Impossible since there are a few queries that require this information.
b) Run the Database scan tool RSI18N_Search to eliminate foreign characters ....but this does not work for me.
Can anyone suggest some other option or a resolution to this problem. Or If anyone has prior experience of working with the program RSI18N_Search please let me know.
Regards
VKVenkat, Andres,
You can try several things here;
1) This is pretty ugly but in case you need a quick way around. Create another cube w/o that char, load all the data to that cube from the first cube, and start sending daily deltas to both cubes. Of course put the second cube to BWA
2) Delete the master data! When you try deleting the master data (a particular record or records that you identified), mostly you will find out that it's used in a transactional data(in ODS or Cube) therefore it will not allow you to delete those records, unless you delete the records from the cubes first, then try it again. OR you might be lucky that it's not stored in anycube and it will delete it right away!
The right way is the second option, however when you delete data from cubes, ods, it will lock the cube + invalidate aggregates if you have + BWA indexes etc. You need to recreate them again. So try doing it in non-business hours or in your maintenance window.
Cheers
Tansu -
Index creation error. Can't lock configuration object.
Hi,
My Trex it is giving me a lot of trouble. I am not able to create index with the Trex Search and Classification service (the message I get is==> Index could not be created: null)
The defaulttrace says:
#1.5 #0017A4F64A4801160000003200001F7000043C109F857E90#1191942000781#com.sap.workflow#sap.com/irj#com.sap.workflow#Guest#0####9fd2cf80767011dc9b4f0017a4f64a48#Thread[ThreadPool.Worker4,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/Applications/Workflow/General#Plain###TaskSchedulerDeadline.run()#
#1.5 #0017A4F64A4801160000003300001F7000043C109F859265#1191942000797#com.sap.workflow#sap.com/irj#com.sap.workflow.#Guest#0####9fd2cf80767011dc9b4f0017a4f64a48#Thread[ThreadPool.Worker4,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###LockConfigException: Cannot lock configuration object "config://local/com.sap.workflow/scheduler/task" without a valid user ID.
at com.sapportals.config.fwk.data.ConfigLockManager.lock(ConfigLockManager.java:516)
at com.sapportals.config.fwk.data.ConfigLockManager.lock(ConfigLockManager.java:265)
at com.sapportals.config.fwk.data.Configurable.lock(Configurable.java:184)
at com.sapportals.config.fwk.data.ConfigPlugin.getAndLockConfigurable(ConfigPlugin.java:452)
at com.sap.workflow.cfg.AbstractConfiguration.setValue(AbstractConfiguration.java:313)
at com.sap.workflow.es.scheduler.TaskSchedulerDeadline.run(TaskSchedulerDeadline.java:86)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:174)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:108)
at java.lang.Thread.run(Thread.java:534)
What means the message "Cannot lock configuration object "config://local/com.sap.workflow/scheduler/task" without a valid user ID."?
Have I to do something abut configuration, users, permissions??
The version is 7.00 patch 57
Operation system is WServer 2003SR2 Enterprise Edition (En)
I have installed the TREX HTTP server
In Monitoring I see a green light for http server, index server, name server, queue server
I am so confused, don't know wich way to turn.
Any help will be appreciated.
Thanks in advance.
Guillermo.Hi,
It was an error caused by permissions.
By mistake the repository /taxonomies was manipulated by an user and the permissions were changed.
After it the portal wasn't able to create new folders under that repository.
Regards. -
Intermedia index creation error
Hi,
I am getting the following error while importing a table with intermedia index on it.
error occured in execution of ODCIINDEXCREATE routine.
intermedia text error : Lost RPC connection to external procedure agent.
at CTXSYS.DRUE
at CTXSYS.TEXTINDEXMETHODS
Any help is appreciated.
thanks,
Manish.We are encountering this error, too. On my local server, running 8.1.6 on Win2k on a laptop, I can create indexes successfully. We have a range of content, including Office 200 file types, html , text, etc.
The column being indexed is LONG RAW. I believe we are using patch 8.1.6.3 already. We are eager to resolve this problem. -
Spatial index creation error -ORA-13011: value is out of range
I am trying to create a spatial index and this is what I get.
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13200: internal error [ROWID:AAAFXYAADAAABxyAAD] in spatial indexing.
ORA-13206: internal error [] while creating the spatial index
ORA-13011: value is out of range
ORA-00600: internal error code, arguments: [kope2upic014], [], [], [], [],
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 7
ORA-06512: at line 1
I can't find any documentation as to how to fix this. How do you determine which row of data is out of range? Any help would be greatly appreciated!Hi Jeff,
The data at rowid AAAFXYAADAAABxyAAD has a problem.
Can see what the issue is by doing:
select sdo_geom.validate_geometry(geom_col_name,diminfo)
from your_table_name a, user_sdo_geom_metadata b
where b.table_name='YOUR_TABLE_NAME'
and a.rowid='AAAFXYAADAAABxyAAD';
If you are using Oracle9iR2 then this would be even better:
select sdo_geom.validate_geometry_with_context(geom_col_name,diminfo)
from your_table_name a, user_sdo_geom_metadata b
where b.table_name='YOUR_TABLE_NAME'
and a.rowid='AAAFXYAADAAABxyAAD'; -
Refresh Schema Index Creation Errors
This may be an old question, but I didn't see it listed.
When I run the schematool on an empty DB I get exceptions
similar to the following. Schematool appears to be attempting
to create the same index more than once.
If I rerun it, it notices the existing index (or perhaps
just the existing table the index is on) and continues
updating the schema. With my current data model I get
three of these before schematool finishes successfully.
If I set ignoreErrors="true" then it runs without complaint.
The completed schema seems to be fine when it's all done
but I can't run a complete database create cycle without
manual intervention or ignoring errors. I don't want to
do that in case some other error occurs.
Should I worry about this?
Environment: Kodo 2.4.0 (same ocurred with all previous versions),
Postgresql 7.3.1 (also PG 7.1.2), Redhat Linux 8.0 (also RH 7.1).
java.sql.SQLException: ERROR: relation named "booking_alternateflightsegmeni" already exists
at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:126)
at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:451)
at org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java:281)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:48)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:179)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:165)
at com.solarmetric.datasource.PoolConnection$PoolStatement.executeUpdate(PoolConnection.java:112)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:899)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.createTable(SchemaTool.java:830)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTable(SchemaTool.java:461)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTables(SchemaTool.java:472)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:355)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:321)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1132)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1069)
at com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolTask.java:54)
at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:118)
at org.apache.tools.ant.Task.perform(Task.java:319)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at com.intellij.rt.ant.execution.AntMain.runBuild(AntMain.java:493)
at com.intellij.rt.ant.execution.AntMain.start(AntMain.java:166)
at com.intellij.rt.ant.execution.AntMain.main(AntMain.java:191)
/live/home/ron/Work.hostess/ronsoft/projects/europe.asap/build.xml:494: java.sql.SQLException:
ERROR: relation named "booking_alternateflightsegmeni" already exists
at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:125)
at org.apache.tools.ant.Task.perform(Task.java:319)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at com.intellij.rt.ant.execution.AntMain.runBuild(AntMain.java:493)
at com.intellij.rt.ant.execution.AntMain.start(AntMain.java:166)
at com.intellij.rt.ant.execution.AntMain.main(AntMain.java:191)
Caused by: java.sql.SQLException: ERROR: relation named "booking_alternateflightsegmeni" already exists
at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:126)
at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:451)
at org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java:281)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:48)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:179)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:165)
at com.solarmetric.datasource.PoolConnection$PoolStatement.executeUpdate(PoolConnection.java:112)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:899)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.createTable(SchemaTool.java:830)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTable(SchemaTool.java:461)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTables(SchemaTool.java:472)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:355)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:321)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1132)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1069)
at com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolTask.java:54)
at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:118)
... 8 more
--- Nested Exception ---
java.sql.SQLException: ERROR: relation named "booking_alternateflightsegmeni" already exists
at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:126)
at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:451)
at org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java:281)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:48)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:179)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:165)
at com.solarmetric.datasource.PoolConnection$PoolStatement.executeUpdate(PoolConnection.java:112)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:899)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.createTable(SchemaTool.java:830)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTable(SchemaTool.java:461)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTables(SchemaTool.java:472)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:355)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:321)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1132)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1069)
at com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolTask.java:54)
at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:118)
at org.apache.tools.ant.Task.perform(Task.java:319)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at com.intellij.rt.ant.execution.AntMain.runBuild(AntMain.java:493)
at com.intellij.rt.ant.execution.AntMain.start(AntMain.java:166)
at com.intellij.rt.ant.execution.AntMain.main(AntMain.java:191)
/live/home/ron/Work.hostess/ronsoft/projects/europe.asap/build.xml:494: java.sql.SQLException:
ERROR: relation named "booking_alternateflightsegmeni" already exists
at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:125)
at org.apache.tools.ant.Task.perform(Task.java:319)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at com.intellij.rt.ant.execution.AntMain.runBuild(AntMain.java:493)
at com.intellij.rt.ant.execution.AntMain.start(AntMain.java:166)
at com.intellij.rt.ant.execution.AntMain.main(AntMain.java:191)
Caused by: java.sql.SQLException: ERROR: relation named "booking_alternateflightsegmeni" already exists
at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:126)
at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:451)
at org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java:281)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:48)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:179)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:165)
at com.solarmetric.datasource.PoolConnection$PoolStatement.executeUpdate(PoolConnection.java:112)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:899)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.createTable(SchemaTool.java:830)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTable(SchemaTool.java:461)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTables(SchemaTool.java:472)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:355)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:321)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1132)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1069)
at com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolTask.java:54)
at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:118)
... 8 more
--- Nested Exception ---
java.sql.SQLException: ERROR: relation named "booking_alternateflightsegmeni" already exists
at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:126)
at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:451)
at org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java:281)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:48)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:179)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:165)
at com.solarmetric.datasource.PoolConnection$PoolStatement.executeUpdate(PoolConnection.java:112)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:899)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.createTable(SchemaTool.java:830)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTable(SchemaTool.java:461)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTables(SchemaTool.java:472)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:355)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:321)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1132)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1069)
at com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolTask.java:54)
at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:118)
at org.apache.tools.ant.Task.perform(Task.java:319)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at com.intellij.rt.ant.execution.AntMain.runBuild(AntMain.java:493)
at com.intellij.rt.ant.execution.AntMain.start(AntMain.java:166)
at com.intellij.rt.ant.execution.AntMain.main(AntMain.java:191)
/live/home/ron/Work.hostess/ronsoft/projects/europe.asap/build.xml:494: java.sql.SQLException:
ERROR: relation named "booking_alternateflightsegmeni" already exists
at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:125)
at org.apache.tools.ant.Task.perform(Task.java:319)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at com.intellij.rt.ant.execution.AntMain.runBuild(AntMain.java:493)
at com.intellij.rt.ant.execution.AntMain.start(AntMain.java:166)
at com.intellij.rt.ant.execution.AntMain.main(AntMain.java:191)
Caused by: java.sql.SQLException: ERROR: relation named "booking_alternateflightsegmeni" already exists
at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:126)
at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:451)
at org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java:281)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:48)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:179)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:165)
at com.solarmetric.datasource.PoolConnection$PoolStatement.executeUpdate(PoolConnection.java:112)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:899)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.createTable(SchemaTool.java:830)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTable(SchemaTool.java:461)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTables(SchemaTool.java:472)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:355)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:321)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1132)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1069)
at com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolTask.java:54)
at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:118)
... 8 more
--- Nested Exception ---
java.sql.SQLException: ERROR: relation named "booking_alternateflightsegmeni" already exists
at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:126)
at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:451)
at org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java:281)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:48)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:179)
at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:165)
at com.solarmetric.datasource.PoolConnection$PoolStatement.executeUpdate(PoolConnection.java:112)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:899)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.createTable(SchemaTool.java:830)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTable(SchemaTool.java:461)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refreshTables(SchemaTool.java:472)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:355)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:321)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1132)
at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1069)
at com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolTask.java:54)
at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:118)
at org.apache.tools.ant.Task.perform(Task.java:319)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at com.intellij.rt.ant.execution.AntMain.runBuild(AntMain.java:493)
at com.intellij.rt.ant.execution.AntMain.start(AntMain.java:166)
at com.intellij.rt.ant.execution.AntMain.main(AntMain.java:191)
Build completed with 30 errors. Time: 13 s
Ron Hitchens {mailto:[email protected]} RonSoft Technologies
(949) 830-8233 (Home Office) http://www.ronsoft.com
(707) 924-3878 (fax) Bit Twiddling At Its Finest
"Don't fear the Reaper" -Blue Oyster CultWhen I run the schematool on an empty DB I get exceptions
similar to the following. Schematool appears to be attempting to create
the same index more than once.This is just due to Kodo running into max index name length restrictions.
It's actually trying to create 2 different indexes with different names,
but because the names have to be truncated to meet the DB's requirements,
they come out the same.
In the coming month's we're going to roll out a more advanced schema
manipulation system that automatically avoids these kinds of errors. In
the meantime, you have several options:
* Just use the -ignoreErrors flag. The schema will be created fine;
it'll just be missing a few indexes.
* Have the schematool output a .sql script, change it manually, and then
run it against your DB.
* Use the documented metadata extensions to set the table and column
names for the problematic indexes to something shorter. The index name
generation algorithm currently uses the table and column names to form
the index name, so shortening these up will prevent truncation of the
index names, and therefore prevent collisions.
* Use the documented NameTruncationVersion setting (see the docs for the
DictionaryProperties configuration property) to switch to another naming
algorithm. -
friends,
i m unable to create an index on table named counties having SDO_GEOMETRY column named geom.
when i execute the create index command it gives me this error
SQL> create index county_ind on counties(geom)
2 INDEXTYPE IS MDSYS.SPATIAL_INDEX
3 PARAMETERS('SDO_LEVEL = 16, SDO_NUMTILES=32');
create index county_ind on counties(geom)
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13200: internal error [ROWID:AAAG13AABAAAkfXAAD] in spatial indexing.
ORA-13197: element MDSYS.COUNTIES.. is out of range
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 7
ORA-06512: at line 1
please help me to solve this problem
Harpreet
nulltry this
create index idx_cities on cities(location)
indextype is mdsys.spatial_index
parameters('sdo_level=9');
the same procedure for counties,interstates
and states.first drop the index and then
recreate it.still if it doesnt work check
somepackageboby,package ie like triggers are
anyone of these invalid make this to be valid
and try again
srikanth.v
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Shalu:
I tried it all I still keep getting this error
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCI
ORA-13203: failed to read SDO_GEOM_METADATA table
ORA-29400: data cartridge error
ORA-00904: invalid column name
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 7
ORA-06512: at line 1
Shalu<HR></BLOCKQUOTE>
null -
Spatial Index Creation Error on 9.2.0.1
Hi,
I can´t create a spatial index on an Oracle 9.2.0.1, Windows 2000 Server. I create the table, register metadata and when I try to create the index the folowing error is returned (some messages in Portuguese):
ORA-29855: ocorreu um erro na execução da rotina ODCIINDEXCREATE
ORA-13249: Error executing stmt: begin mdsys.prvt_idx.execute_insert(NULL, NULL, ' VALUES (''TESTUSER'',''MDIDX_INIT'', 0, 0, 64, -1, NLS_UPPER(''MDRT_7844$''), ''I_SDOTEST'', 1, ''TESTUSER'', ''"GEOM"'', 0, 0, 2, 0, ''DEFAULT'', ''DEFAULT'', NULL,NULL, NULL, NULL, NULL, NULL, NULL, 2, ''DEFAULT'', 10, NULL, NULL, NULL, NULL, ''FALSE'', ''VALID'', NULL)', NULL); end;
ORA-13249: Error in Spatial index: insert to metadata failed
ORA-29400: erro no cartucho de dados
ORA-00913: valores demais
ORA-06512: em "MDSYS.PRVT_IDX", line 5
ORA-06512: em line 1
ORA-06512: em "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: em line 1
The same error occurs with other database users.
On my notebook (Windows XP) with the same Oracle version installed the index is created succesfully.
What can be wrong on the server ?
Thanks.When I connect through sqlplus it shows:
SQL*Plus: Release 9.2.0.1.0 - Production on Mon Jun 14 17:14:33 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL>
The select on dba_registry returns:
COMP_ID COMP_NAME VERSION STATUS MODIFIED CONTROL SCHEMA PROCEDURE STARTUP PARENT_ID
CATALOG Oracle9i Catalog Views 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS SYS DBMS_REGISTRY_SYS.VALIDATE_CATALOG
CATPROC Oracle9i Packages and Types 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS SYS DBMS_REGISTRY_SYS.VALIDATE_CATPROC
OWM Oracle Workspace Manager 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS WMSYS OWM_VALIDATE
JAVAVM JServer JAVA Virtual Machine 9.2.0.1.0 VALID 12-MAI-2002 16:55:28 SYS SYS
XML Oracle XDK for Java 9.2.0.2.0 VALID 14-JUN-2004 15:59:45 SYS SYS XMLVALIDATE
CATJAVA Oracle9i Java Packages 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS SYS DBMS_REGISTRY_SYS.VALIDATE_CATJAVA
ORDIM Oracle interMedia 9.2.0.1.0 LOADED 12-MAI-2002 17:27:10 SYS ORDSYS
SDO Spatial 9.2.0.1.0 LOADED 12-MAI-2002 17:40:16 SYS MDSYS
CONTEXT Oracle Text 9.2.0.1.0 VALID 12-MAI-2002 17:32:11 CTXSYS CTXSYS
XDB Oracle XML Database 9.2.0.1.0 VALID 14-JUN-2004 15:59:55 SYS XDB DBMS_REGXDB.VALIDATEXDB
WK Oracle Ultra Search 9.2.0.1.0 VALID 12-MAI-2002 17:44:01 WKSYS WKSYS WK_UTIL.VALID
ODM Oracle Data Mining 9.2.0.1.0 LOADED 12-MAI-2002 17:49:36 SYS ODM
APS OLAP Analytic Workspace 9.2.0.1.0 LOADED 12-MAI-2002 17:58:32 SYS SYS
XOQ Oracle OLAP API 9.2.0.1.0 LOADED 12-MAI-2002 17:59:07 SYS SYS
AMD OLAP Catalog 9.2.0.1.0 INVALID 14-JUN-2004 15:59:57 SYS OLAPSYS CWM2_OLAP_INSTALLER.VALIDATE_CWM2_INSTALL
Any ideas ? -
Intermedia index creation error while taking import
Hi,
I tried taking an export dump from a intermedia text indexed schema , and re-importing into a new schema. All objects got created except intermedia indexes.
Please suggest.
IMP-00017: following statement failed with ORACLE error 6510:
"BEGIN "
"ctxsys.driimp.create_index('RESOURCE_SUMMARY_NDX','RESOURCES',USER,"
"'RESOURCEID','2','RESOURCESUMMARYXML','1',"
"'2000','48','8130','49',"
"NULL, NULL, NULL );"
regards,
Manish Jain.Please see reply at:
http://technet.oracle.com:89/ubb/Forum36/HTML/000661.html
Maybe you are looking for
-
I just got my new MacBook 2 days ago, I have a 2WIRE router and haven't been able to connect wirelessly. I have tried absolutely everything (putting $ before te password, making it a public net, installing the AirPort updates...) Nothing seems to wor
-
Do anyone know we're to buy a 3 meter long cable for power to my iPad
Do anyone know we're to buy a 3 meter long cable for power to my iPad?
-
Inbound Interface for Accepting Bank Statement Through EDI
Hi All , Pls Help me out to complete this Scenerio with u r Ideas and Inputs . Inbound Interface for Accepting Bank Statement Through EDI. Rgds Rafi .
-
Storing DW snippets in the cloud
Hi, was sent here by the Adobe Dreamweaver management on Facebook. I lately wrote nearly the same posting here in October 2012 regarding the DW CS6 version. I still want to change to DW (CC this time) but can't because Adobe seems not to be able to m
-
Unusual message appearing on my screen
Hey, today i wtinessed a very strange message on my phone, my phone was locked and i got my phone out of my pocket and it had a message saying "i now have control of your phone. i can hear everything you say". once i unlocked the key pad it disappear