I'm trying to create a simple full-text index like this:
exec ctx_ddl.create_preference('my_own_lexer', 'AUTO_LEXER');
create index myidx ON tbl(name)
INDEXTYPE IS ctxsys.context PARAMETERS ('LEXER my_own_lexer')
Got error:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: Oracle Text error:
DRG-10502: index IDX does not exist
DRG-00100: internal error, arguments : [50611],[drli.c],[2743],[License Error:
could not find the given license file:
/u01/app/oracle/product/11.2.0/xe/ctx/data/inxight/lang/license.dat],[]
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 366
Using BASIC_LEXER instead of AUTO_LEXER - works without errors
centOS, Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Beta
thanx!
Oracle XE 11gR2 is a beta product. But Express Edition is a restricted product, lacking some of the functionality included in the bigger product. So this may be a bug or a feature by design. The licensing documentation doesn't explicitly mention AUTO_LEXER, which we might expect if Oracle had deliberately excluded it, so "bug" is quite likely.
The best thing to do is raise this question on the OTN forum for the product. Members of the XE team read and respond to user feedback there.
Related
I know so little about Sybase that I don't even know whether database link is the correct term in Sybase. What I'm looking for is a way to communicate with Sybase over Oracle's heterogeneous services, commonly called a database link in Oracle (linked server if you speak SQL Server).
We are a primarily Oracle shop with a healthy dose of SQL Server, but zero Sybase experience. As you might guess, we have a piece of software that happens to run on Sybase, and we need to get information out of its database.
Professional services from the software vendor have not been helpful at all; frankly, we don't even know if they gave us the correct driver.
Our Oracle DBA is as sure as he can be (without knowing anything about Sybase) that he has everything set up correctly on the Oracle side.
When we try to run a query from Oracle to get data from Sybase, we get:
select * from call_request#sybase
*
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[SAP][ASE ODBC Driver][Adaptive Server Enterprise]Incorrect syntax near the
keyword 'where'.
{ZZZZZ,NativeErr = 156}
ORA-02063: preceding 3 lines from SYBASE
Complaining about syntax near "where" doesn't make much sense, since there is no predicate at all. And it doesn't help to add a dummy
where 1=1
We're completely unsure where to turn. What can we even check next? Where is the documentation for setting this sort of thing up? Any ideas what is wrong?
After upgrading from Oracle 11/12 to 18/19 I get this error: ORA-01036: illegal variable name/number.
The error occurred in a query like this:
SELECT * FROM (SELECT * FROM TABLE) MY_TABLE WHERE ROWNUM <= :P_ROWNUM
(Subquery + binding parameters)
The identical query works properly with the Oracle 11.2.0.4 or 12.1.0.2 client. It fails with the Oracle Client 18c or 19c.
PS: The Oracle Server is version 18c 64x for Windows.
I use Delphi 10.1.2 with ADO components (dbGO). I also tried with Delphi 13.3.3 but the behavior is the same.
It seems to be a problem in the Oracle OLE DB provider (ORAOLEDB).
If I don't use ADO but DevArt Unidac all worked as expected.
Someone can help me?
Max
Your query is fine. We ran into a similar issue when migrating from 12.1 to 19. In our case, we have a custom OLE DB provider that interfaces with OraOLEDB (and others) using the Microsoft OLE DB Provider Templates (ATL). When attempting to upgrade from 12.1.x to 19c we started seeing the strange and confusing "ORA-01036: illegal variable name/number" error for parameterized SELECT queries. The queries would succeed the first time they were executed but subsequent executions would fail when all we did was change the parameter value (the queries were executed sequentially). I went on a wild goose chase trying to diagnose the issue and finally decided it had to be an Oracle caching bug of some kind. Yesterday, I experimented with the cache-related connection string attributes and found that adding the MetaDataCacheSize attribute and setting its value to 0 (zero) resolved the issue for us. None of the current Oracle patches appear to address this issue, at least none of those that mention the ORA-01036 error.
SQL> #apex_epg_config D:\X19
I am getting an error during installation of oracle apex 19 on window server 2008 with oracle 11gr2
Loading images directory: D:\X19/apex/images
declare
ERROR at line 1:
ORA-00600: internal error code, arguments: [kzxcInitLoadLocal-7], [64131],
[ORA-64131: XMLIndex Metadata: failure during the looking up of the dictionary
ORA-30966: error detected in the XML Index layer
ORA-30966: error detected in the XML Index layer
], [], [], [], [], [], [], [], [], []
ORA-06512: at "XDB.DBMS_XDB", line 437
ORA-06512: at line 65
timing for: Load Images
Elapsed: 00:05:40.40
Oracle apex status is VALID in dba_registory.
When I open the URL then the following message is displayed.
apex url
How to solve this issue?
It is your version 11.2.0.4 ? This is what the documentation states:
Oracle APEX 19.2 is fully supported through Oracle Support Services on all Editions (EE, SE2, SE, and SE1) of the Oracle database, 11.2.0.4 or higher with a valid Oracle Database Technical Support agreement.
If you have no option to use a different database version ( like 12c or 18c ) my suggestion is that you install a prior version of Apex, like 5.1.4
Without more details regarding your db configuration, I could only find a possible explanation:
ORA-00600 [kzxcInitLoadLocal-7], [64131], [ORA-64131: XMLIndex Metadata: failure during the looking up of the dictionary (Doc ID 1383658.1)
The note states that the error is produced by a wrongly database character set change. If this is the case, restore the database backup from prior to the database character set change via the ALTER DATABASE CHARACTER SET method, then use CSSCAN/CSALTER to change the database character set.
I created an SSIS package to copy data from one Oracle table to another Oracle table. Each table is in a different database.
I'm getting this error for every single column of the source table:
ERROR [HY010] [Oracle][ODBC]Function sequence error
This is the screenshot.
I have no idea what this means. I've also researched but I haven't seen anything that has helped me.
How can I fix this? I did read that an alternative is to create a linked server.
I wanted to add that the ODBC driver was created with a relatively recent Oracle 12 driver, so I'm not sure why VARCHAR2 columns would not be supported.
Also wanted to point out that the Windows server where the Oracle DB is 64-bit (Windows Server 2008) and Visual Studio 2008 (where the SSIS package is created) is 32-bit. That's why the driver has "_32" at the end.
Based on the following documentation:
The error occurs when ODBC functions are called out of the order required by the ODBC Specification.
The error can also occur if an ODBC function call returns an error and the application continues making ODBC calls that require the previous ODBC call to succeed.
I think you should check that all columns data types are supported by the ODBC driver.
Similar questions
MS-Oracle ODBC Driver Function Sequence Error
Update 1
You can refer to the following link to learn more about supported data types:
Oracle® Database Gateway for ODBC User's Guide - Data Type Conversion
Note that in the link above they mentioned that:
If a table contains a column whose data type is not supported by Oracle Database Gateway for ODBC, the column information is not returned to the Oracle database.
When i am trying to import i'm getting the error.can anyone help me?
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORA-31626: job does not exist
ORA-31637: cannot create job SYS_IMPORT_FULL_01 for user TBAADM
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT_INT", line 600
ORA-39080: failed to create queues "KUPC$C_1_20110614115239" and "KUPC$S_1_20110614115239" for data Pump job
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPC$QUE_INT", line 1555
ORA-00832: no streams pool created and cannot automatically create one
yes you can. It does help to tell which expport/import tool you use, exp/imp or expdp/impdp. A simple google search reveals: How to export from oracle 11.2 and import into 10.2 version This example is using both expdp/impdp and exp/imp.
The main difference is that when using expdp you need to specify the version of the database that is going to import the dump file. This is done on the commandline.
With exp, you need to use the exp utility from the lower version database.