I am running below command to create an index on the table of oracle ebs.
create index mtl_index_N1 on MTL_MATERIAL_TRANSACTIONS(last_update_date);
But I am getting error which does not seems correct with index. what is this issue? is error related with Database indexes or sqldeveloper issue?
Related
I just tried setting up Azure SQL data sync's sync group using sample Azure SQL database. I am syncing dbo.BuildVersion table of the sample database.
I get the following error on member database.
Database provisioning failed with the exception "Incorrect syntax near the keyword 'NOT'.Inner exception: SqlException ID: 39f49622-6a56-4a44-8e55-2a646f99a584, Error Code: -2146232060 - SqlError Number:156, Message: SQL error with code 156 For more information, provide tracing ID ‘679953bc-7dac-4490-89e9-ea6d145d0442’ to customer support."
How should I resolve this issue?
Thanks
I am able to resolve this issue by creating empty table in the member database first and then running the sync.
Does Sync service not create table when table does not exist in the member database?
It does create it, however, under certain circumstances it fails to create it do to some issue with the schema itself. Therefore, the workaround, as you figured out, is to create the table manually.
I have upgraded Postgres to 12.1, PostGIS to 3.0 and PGAdmin to 4.15. Running queries and using PGAdmin GUI results in some error messages:
ERROR: column rel.relhasoids does not exist
LINE 1: SELECT rel.relhasoids AS has_oids
Error retrieving data from the server: INTERNAL SERVER ERROR
String indices must be integers
What am I missing that will solve these errors?
I needed to remove the server from PGAdmin and re-add it.
When trying to setup a target to VoltDB, SymmetricDS fails on schema creation (specifically the table - SYM_INCOMING_ERROR).
Is there a setting to change the schema without having to recompile?
[voltdb] - AbstractSymmetricEngine - An error occurred while starting
SymmetricDS
org.jumpmind.db.sql.SqlException: General Provider Error
(GRACEFUL_FAILURE): 'Error: Table SYM_INCOMING_ERROR has a maximum row size
of 2403801 but the maximum supported row size is 2097152'
I would export the DDL SQL, fix the issue and apply it using flyway or liquibase
I am trying to convert and migrate an Oracle schema to MSSQL server. At the last step, migrating data, I get the error message:
The table [MYDATABASE].[MYSCHEMA].MYTABLE] doesnot exist in target. You must first convert the table then load it into the database.
This error message appears for each table in my schema.
Can someone explain what is happening and what I need to do to get past this?
Are you tries to migrate the data before doing the ‘synchronize with the database’ operation?
If Yes,
This error message generally occurs when the target table doesn’t
exist on SQL server database. After converting schema, you need to
synchronize the table with the database before migrating the data.
To do this you right click on the SQL Server database in Metadata
explorer and click “Synchronize with database” menu.
Note: Table structure will not be created in the SQL server database until you synchronize.
CREATE INDEX test_index ON cola_markets(shape)
INDEXTYPE IS MDSYS.SPATIAL_INDEX;
I am creating an index on Oracle Spatial column, following the guidelines here at http://docs.oracle.com/cd/B19306_01/appdev.102/b14255/sdo_objindex.htm#i78196
However, SQL developer keeps complaining about the following error.
That is definitely the right syntax. I confirm that there is no typing mistake by running it on my database.
On the possibility that this is some oddity due to SQL Developer, can you also try and run the command with plain sqlplus ? What do you get ?