Error in exporting DR$ tables
Hi,
I have user(Say User1) with Roles CONNECT,RESOURCE,CTXAPP roles granted to it.
The entire schema except tables LIKE DR$ATTRIBUTE_VALUES_INDEX$I and DR$ATTRIBUTE_VALUES_INDEX$K and ATTRIBUTES view are not exported appropriately.
C:\>exp user1/user1@instance_name file=E:\code\Backup\temp\user1.dmp
log=E:\code\Backup\temp\user1.log rows=yes constraints=yes indexes=yes
grants=yes consistent=y;
On exporting the same i was encountered with
==========================================================
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the OLAP, Data Mining and Real Application Testing options
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)
About to export specified tables via Conventional Path ...
EXP-00011: user1. ATTRIBUTES does not exist
EXP-00011: user1.DR$ATTRIBUTE_VALUES_INDEX$I does not exist
EXP-00011: user1.DR$ATTRIBUTE_VALUES_INDEX$K does not exist
Export terminated successfully with warnings.
===========================================================
NOTE: the tables and view are existing in the schema(user1).
Please help...
According to Metalink Note:139388.1:
This is intended behavior.
Secondary objects are not exported because the CREATE INDEX at import time
will recreate them.
The column 'SECONDARY' of DBA_TABLES indicates if the table is a secondary object
created by the ODCIIndexCreate method of the Oracle Data Cartridge (Y or N).
Similar Messages
-
Error while exporting a table - EXP-00091
I am doing an export of a table. The table has 1000838 rows. After the export is completed,
when I checked the log - it said
Connected to: Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
With the Partitioning option
JServer Release 9.2.0.4.0 - Production
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
About to export specified tables via Conventional Path ...
. . exporting table FIDA_LABEL 1000838 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
Export terminated successfully with warnings.
I looked in the Oracle error messages document and found this out ---
EXP-00091 Exporting questionable statistics
Cause: Export was able to export statistics, but the statistics may not be useable. The statistics are questionable because one or more of the following happened during export: a row error occurred, client character set or NCHARSET does not match with the server, a query clause was specified on export, only certain partitions or subpartitions were exported, or a fatal error occurred while processing a table.
Action: To export non-questionable statistics, change the client character set or NCHARSET to match the server, export with no query clause, or export complete tables. If desired, import parameters can be supplied so that only non-questionable statistics will be imported, and all questionable statistics will be recalculated.
And this how my export command looks like -
exp vincent/passphr query=\"where state in \(\'MD\',\'CA\',\'WI\'\)\" file=$EXPDIR/fida_label_9i.dmp tables=vincent.fida_label
log=$LOGDIR/fida_label_exp.log
Ofcourse, I am using the query clause because I really need to and it has always worked when we were in the Oracle 8i environment. We recently moved to the 9i. And this happens in this 9i version...
And I certainly do not want to specify the import parameters to ignore the questionable statistics as no changes are desired in that area...(my hands are tied..).
What could " a fatal error occurred while processing a table " mean? And how can this be traced and troubleshooted ? Or how can I find out if any row errors occurred ? And if required, how do I check the character sets and other likes ?? (I have no idea in this area)
Thanks. All I needed was to get around this error. Your suggesions/responses would be highly appreciatedWhat version of Oracle 9i are you using? Do you have a standard 'NLS_LANG' environment variable set on client's machines? Or do you set it to different values on different machines?
Here is one of way you could get around it.
Could you specify the export parameter 'STATISTICS=NONE' while exporting the table data?
Try this and see.
If this is successful, you could use the import utility as usual. You could always compute or estimate statistics on the table after import. -
Facing error while exporting a table from command prompt.
Hi Everyone,
Please see the below error and suggest me what to do? My database is 11g.
SQL> connect system/manager;
Connected.
SQL> expdp scott directory=test_dir dumpfile=scott.dmp tables=emp;
SP2-0734: unknown command beginning "expdp scot..." - rest of line ignored.Regards,
BS2012.
Edited by: BS2012 on Apr 29, 2013 1:57 PMBS2012 wrote:
Hi Jeneesh,
Thanks for correcting me. I've never done import and export before. if I'll have to do that from sqlplus then what should I write?
Regards,
BS2012.Could you explain your business requirements?
You cannot do export/import as it is from sqlplus...
You may be able to write pl/sql code using DBMS_DATAPUMP package..
Explain your requirements, people will be able to help.. -
EXP-00015: error while exporting a table !!!
Hi
I was trying to take table backup by exp and import method.
Got the following error
Please adivse.
EXP-00015: error on row 7548444 of table LOADER_POS, column VERSIONDATE, datatype 12
From
PJaffar
Appreciate your response.
There is enough space.
When u say analyze table structure ..
Are you talking about the Updating the statistics. ?
Please explain.
Thanks again.
From
PBy "analyze table structure", you can see if you have any corruptions of block :
analyze table table_name validate structure;[pre]
or
[pre]analyze index index_name validate structure;[pre]
Nicolas. -
Error rollback segment while exporting a table
I am getting error while exporting a table, can someone advise me how i can handle this issue.
EXP-00056: ORACLE error 1555 encountered
ORA-01555: snapshot too old: rollback segment number with name "" too small
ORA-22924: snapshot too old
ThanksHi, I have the same problem...
I have a table with a blob type (14740 records)
I have increase the PCTVERSION to 100 (= maximum)
undo_retention = 604800 (7 days)
undo tablespace = 2 Gb
exporting with parameter CONSISTENT=n
Still I got the message
EXP-00056: ORACLE error 1555 encountered
ORA-01555: snapshot too old: rollback segment number with name "" too small
ORA-22924: snapshot too old
When exporting the table
What do I have to do more ????? -
Error in exporting from oracle8i (8.1.6)
hi,
i tried to make export in oracle8i (8.1.6) using the utility exp but it gives me this error after exporting only tables of the user:
EXP-00008:ORACLE ERROR 6553 ENCOUNTERED
ORA-06553:PLS-561:CHARACTER SET MISMATCH ON VALUE FOR PARAMETER 'SHORTNAME'
the dmp file generated does not contain any relations or procedures or db triggers,only tables.
knowing that i use AR8MSWIN1256 AS NLS_CHARACTERSET AND AS NLS_NCHAR_CHARACTERSET
and i already run the following sql files :
catalog.sql , catproc.sql ,catexp.sql
any one help me? thank you in advance.This forum focuses on heterogeneous connectivity rather than
homogeneous connectivity.
Vira -
ORA-00904 error while export table with CLOB
All,
I'm trying to export from Oracle Client 8.0.4 an specific Oracle 9i R2 schema, but this error appears. This error is related with tables that have CLOB field types, because schemas with tables without this field type can be exported with no error. I've already run the catexp.sql script, but it haven't solved this problem.
Does anyone can help me?
Thanks,
DaviYou can try performing the import of the dump to see if it would work with 8i client or the 8.0.4 client.
if not, you may not be able to use this method to move data into 8.0.4 database that is no longer spported by current tools.
you may then want to try use other techniques like dumping tables into flat files and then using SQL*Loader to load into 8.0.4.
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:88212348059#14506966201668 -
R3load export of table REPOSRC with lob col - error ora-1555 and ora-22924
Hello,
i have tried to export data from our production system for system copy and then upgrade test. while i export the R3load job has reported error in table REPOSRC, which has lob column DATA. i have apsted below the conversation in which i have requested SAP to help and they said it comes under consulting support. this problem is in 2 rows of the table.
but i would like to know if i delete these 2 rows and then copy from our development system to production system at oracle level, will there be any problem with upgrade or operation of these prorgams and will it have any license complications if i do it.
Regards
Ramakrishna Reddy
__________________________ SAP SUPPORT COnveration_____________________________________________________
Hello,
we have are performing Data Export for System copy of our Production
system, during the export, R3load Job gave error as
R3LOAD Log----
Compiled Aug 16 2008 04:47:59
/sapmnt/DB1/exe/R3load -datacodepage 1100 -
e /dataexport/syscopy/SAPSSEXC.cmd -l /dataexport/syscopy/SAPSSEXC.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) INFO: Export without hintfile
(NT) Error: TPRI_PAR: normal NameTab from 20090828184449 younger than
alternate NameTab from 20030211191957!
(SYSLOG) INFO: k CQF :
TPRI_PAR&20030211191957&20090828184449& rscpgdio 47
(CNV) WARNING: conversion from 8600 to 1100 not possible
(GSI) INFO: dbname = "DB120050205010209
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname
= "dbttsap "
(GSI) INFO: sysname = "AIX"
(GSI) INFO: nodename = "dbttsap"
(GSI) INFO: release = "2"
(GSI) INFO: version = "5"
(GSI) INFO: machine = "00C8793E4C00"
(GSI) INFO: instno = "0020111547"
(DBC) Info: No commits during lob export
DbSl Trace: OCI-call 'OCILobRead' failed: rc = 1555
DbSl Trace: ORA-1555 occurred when reading from a LOB
(EXP) ERROR: DbSlLobGetPiece failed
rc = 99, table "REPOSRC"
(SQL error 1555)
error message returned by DbSl:
ORA-01555: snapshot too old: rollback segment number with name "" too
small
ORA-22924: snapshot too old
(DB) INFO: disconnected from DB
/sapmnt/DB1/exe/R3load: job finished with 1 error(s)
/sapmnt/DB1/exe/R3load: END OF LOG: 20100816104734
END of R3LOAD Log----
then as per the note 500340, i have chnaged the pctversion of table
REPOSRC of lob column DATA to 30, but i get the error still,
i have added more space to PSAPUNDO and PSAPTEMP also, still the same
error.
the i have run the export as
exp SAPDB1/sap file=REPOSRC.dmp log=REPOSRC.log tables=REPOSRC
exp log----
dbttsap:oradb1 5> exp SAPDB1/sap file=REPOSRC.dmp log=REPOSRC.log
tables=REPOSRC
Export: Release 9.2.0.8.0 - Production on Mon Aug 16 13:40:27 2010
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit
Production
With the Partitioning option
JServer Release 9.2.0.8.0 - Production
Export done in WE8DEC character set and UTF8 NCHAR character set
About to export specified tables via Conventional Path ...
. . exporting table REPOSRC
EXP-00056: ORACLE error 1555 encountered
ORA-01555: snapshot too old: rollback segment number with name "" too
small
ORA-22924: snapshot too old
Export terminated successfully with warnings.
SQL> select table_name, segment_name, cache, nvl(to_char
(pctversion),'NULL') pctversion, nvl(to_char(retention),'NULL')
retention from dba_lobs where
table_name = 'REPOSRC';
TABLE_NAME | SEGMENT_NAME |CACHE | PCTVERSION | RETENTION
REPOSRC SYS_LOB0000014507C00034$$ NO 30 21600
please help to solve this problem.
Regards
Ramakrishna Reddy
Dear customer,
Thank you very much for contacting us at SAP global support.
Regarding your issue would you please attach your ORACLE alert log and
trace file to this message?
Thanks and regards.
Hello,
Thanks for helping,
i attached the alert log file. i have gone through is, but i could
not find the corresponding Ora-01555 for table REPOSRC.
Regards
Ramakrishna Reddy
+66 85835-4272
Dear customer,
I have found some previous issues with the similar symptom as your
system. I think this symptom is described in note 983230.
As you can see this symptom is mainly caused by ORACLE bug 5212539 and
it should be fixed at 9.2.0.8 which is just your version. But although
5212539 is implemented, only the occurrence of new corruptions will be
avoided, the already existing ones will stay in the system regardless of the patch.
The reason why metalink 452341.1 was created is bug 5212539, since this
is the most common software caused lob corruption in recent times.
Basically any system that was running without a patch for bug 5212539 at some time in the past could be potentially affected by the problem.
In order to be sure about bug 5212539 can you please verify whether the
affected lob really is a NOCACHE lob? You can do this as described in
mentioned note #983230. If yes, then there are basically only two
options left:
-> You apply a backup to the system that does not contain these
corruptions.
-> In case a good backup is not available, it would be possible to
rebuild the table including the lob segment with possible data loss . Since this is beyond the scope of support, this would have to be
done via remote consulting.
Any further question, please contact us freely.
Thanks and regards.
Hello,
Thanks for the Help and support,
i have gone through the note 983230 and metalink 452341.1.
and i have ran the script and found that there are 2 rows corrupted in
the table REPOSRC. these rows belong to Standard SAP programs
MABADRFENTRIES & SAPFGARC.
and to reconfirm i have tried to display them in our development system
and production system. the development systems shows the src code in
Se38 but in production system it goes to short dump DBIF_REPO_SQL_ERROR.
so is it possible to delete these 2 rows and update ourselves from our
development system at oracle level. will it have any impact on SAP
operation or upgrade in future.
Regards
Ramakrishna ReddyHello, we have solved the problem.
To help someone with the same error, what we have done is:
1.- wait until all the processes has finished and the export is stopped.
2.- startup SAP
3.- SE14 and look up the tables. Crete the tables in the database.
4.- stop SAP
5.- Retry the export (if you did all the steps with sapinst running but the dialogue window in the screen) or begin the sapinst again with the option: "continue with the old options".
Regards to all. -
Export with Table Splitting : ORA-01115: IO error reading block from file
Hello,
We are in perfroming the last dryrun of our CU&UC conversion.
The are now in the process of exporting the ECC6 system (Oracle 10.2.0.4.0, HPUX ia64) using sapinst features, "table splitting preparation"
When doing so, we are facing critical errors :
Creating file /export_uni/sapinst_splitting/ora_query3_tmp3_1.sql.
ERROR 2010-08-11 10:27:28.881
CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-12801: error signaled in parallel query server P002
ORA-01115: IO error reading block from file 90 (block # 16640)
ORA-27072: File I/O error
HPUX-ia64 Error: 22: Invalid argument
Additional information: 4
Additional information: 16640
Additional information: -1
ORA-01115: IO error reading block from file 90 (block # 16640)
ORA-27072: File I/O error
HPUX-ia64 Error: 22: Invalid argument
ORA-06512: at "SAPR3.TABLE_SPLITTER", line 775
ORA-06512: at line 1
I have therefore perfmed a dbverify ; no corruption has been recorded.
When trying to perfrom the EXPORT, without table splitting ; it works fine ...but the processing time is extremely long, as you can imagine. Any help would be highly appreciated.Regards.
RaoulThank you Stefan,
Our HPUX Release seems to be indeed 11v3,
[root@:/root]# uname -a
HP-UX B.11.31 U ia64 2566039091 unlimited-user license
I'll check the installation of the patch and keep you informed
Thank you
Raoul
Edited by: Raoul Shiro on Aug 11, 2010 11:57 AM -
Export Access table into SP - error on hyperlink fields?
I'm trying to Export an Access DB into Sharepoint. There are two hyperlink fields in the master table that seem to be blocking the transfer. The fields are named XLS and PDF. The data content of the links look like: "XLS#m:\aaaa\bbbb\cccc\dddd.xlsx"
In the Access master table, you'd see XLS which would be a link to
'm:\aaaa\bbbb\cccc\dddd.xlsxm:\aaaa\bbbb\cccc\dddd.xlsx'
The actual message in the error log is:
There was an error copying data to a SharePoint list. URL data 'M:\aaaa\bbbbb\ccccc\ddddd.xlsx XLS' in field 'XLS' could not be sent to the server. The URL may be invalid or longer than 255 characters.
Is it trying to access the xlsx file itself? If i remove the hyperlink fields, everything works. However, what do i need to do to be able to include these two fields?Hi,
According to your description, my understanding is that the Access table cannot be exported to SharePoint with the hyperlink fields.
The format of the hyperlinks in the hyperlink fields XLS and PDF are invalid in SharePoint, so the error occurred when exporting the table to SharePoint.
I recommend to share the files linked in the hyperlink field with the users you need and use the following link format in the hyperlink field:
file://aaaa/bbbb/cccc/dddd.xlsx.
Best regards.
Thanks
Victoria Xia
TechNet Community Support -
Error in updating condition table 372
Hello,
While saving Excise Invoice I am facing error 'Error in updating condition table 372'.Could you please solve this probelm?
Thanks in AdvanceDear All,
I done this--by doing some configuration changes.
Normally while doing Exports we are tempted to use the same sales area and accordingly we may give the combination of excise grp+series grp+export type in IMG>>>Logistics General>>>India>>>Business transactions>>>Outgoing excise invoices>>>Maintain default excise groups and series groups.
Once after removing the export type to your sales area combination--system will show this error--and we cannot even post the Excise invoices.(J1IIN)
I tried in my IDES--that with export type(Ex.Export under Bond)--with this assignment--i am able to post my excise invoices.
Once after removing this assignment of export type--again i am getting this error.
Actually i am not even aware why it is happening--almost after two months of struggle--i find this.
(i feel it is in the same way that we cannot even open/See a sales order by deleting sales group which was created&used previously)
i am sharing this because somebody may get a little help with my thread.
Mark this if helpful--there by others can easily find this thread.
Phanikumar -
Access 2013 crashed when I export a table from the access
Hi!
Access 2013 always crashed when I export a table from the access to the Database Symfoware.
1、The conditions of the Access 2013 crashed are the follows.
1)Create a table in the Access 2013.
2)Using the ODBC driver of the Database Symfoware to export the table from the access to the Database Symfoware.
2、The Environments are the follows.
1)Access 2013 X64(Version:15.0.4420.1017)
2)Win2008R2 X64
3)Symfoware V11.1 X64
3、The Application log from the Win2008R2 are follows.
ログの名前: Application
ソース: Application Error
日付: 2014/04/18 16:21:06
イベント ID: 1000
タスクのカテゴリ: (100)
レベル: エラー
キーワード: クラシック
ユーザー: N/A
コンピューター: WIN-29UTU2AIK6J
説明:
障害が発生しているアプリケーション名: MSACCESS.EXE、バージョン: 15.0.4420.1017、タイム スタンプ: 0x50674523
障害が発生しているモジュール名: ACECORE.DLL、バージョン: 15.0.4420.1017、タイム スタンプ: 0x506742b7
例外コード: 0xc0000005
障害オフセット: 0x0000000000171f36
障害が発生しているプロセス ID: 0xb6c
障害が発生しているアプリケーションの開始時刻: 0x01cf5ad638668c5b
障害が発生しているアプリケーション パス: C:\Program Files\Microsoft Office\Office15\MSACCESS.EXE
障害が発生しているモジュール パス: C:\Program Files\Common Files\Microsoft Shared\OFFICE15\ACECORE.DLL
レポート ID: 00e87957-c6ca-11e3-ad2c-0050568d2ced
イベント XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-18T07:21:06.000000000Z" />
<EventRecordID>3442</EventRecordID>
<Channel>Application</Channel>
<Computer>WIN-29UTU2AIK6J</Computer>
<Security />
</System>
<EventData>
<Data>MSACCESS.EXE</Data>
<Data>15.0.4420.1017</Data>
<Data>50674523</Data>
<Data>ACECORE.DLL</Data>
<Data>15.0.4420.1017</Data>
<Data>506742b7</Data>
<Data>c0000005</Data>
<Data>0000000000171f36</Data>
<Data>b6c</Data>
<Data>01cf5ad638668c5b</Data>
<Data>C:\Program Files\Microsoft Office\Office15\MSACCESS.EXE</Data>
<Data>C:\Program Files\Common Files\Microsoft Shared\OFFICE15\ACECORE.DLL</Data>
<Data>00e87957-c6ca-11e3-ad2c-0050568d2ced</Data>
</EventData>
</Event>
4、When the access crashed,I got the dump file .Then I use the Windbg got some information from the dump files.
The detailes are follows.
FAULTING_IP:
+58872faf03d6dd84
00000000`00000000 ?? ???
EXCEPTION_RECORD: 00000000001723c0 -- (.exr 0x1723c0)
ExceptionAddress: 000007fee3951f36 (ACECORE+0x0000000000171f36)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
FAULTING_THREAD: 00000000000010b8
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
PROCESS_NAME: MSACCESS.EXE
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: ACECORE
FAULTING_MODULE: 0000000076eb0000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP: 506742b7
ERROR_CODE: (NTSTATUS) 0x80000003 - {
EXCEPTION_CODE: (NTSTATUS) 0x80000003 (2147483651) - {
MOD_LIST: <ANALYSIS/>
CONTEXT: 0000000000171ed0 -- (.cxr 0x171ed0)
rax=0000000001be3598 rbx=0000000000000000 rcx=01cf5d1b0f402a5c
rdx=0000000009cfad30 rsi=0000000006688ef0 rdi=0000000001be35d0
rip=000007fee3951f36 rsp=0000000000172490 rbp=00000000001727a0
r8=0000000009b409d0 r9=0000000006688ef0 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000001be19f0
r14=0000000009cfad30 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
ACECORE+0x171f36:
000007fe`e3951f36 4d3927 cmp qword ptr [r15],r12 ds:00000000`00000000=????????????????
Resetting default scope
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 000007fee395c095 to 000007fee3951f36
STACK_TEXT:
00000000`00172490 000007fe`e395c095 : ffffffff`ffffffff 00000000`00000000 00000000`01bddaa2 ffffffff`ffffffff : ACECORE+0x171f36
00000000`001727b0 000007fe`e388f8eb : 000007fe`e399dc10 000007fe`e399dc30 000007fe`e399dc50 00000000`000000f9 : ACECORE+0x17c095
00000000`00172b50 000007fe`e388f590 : 00000000`06688ef0 00000000`00000004 00000000`000000f9 00000000`00000000 : ACECORE+0xaf8eb
00000000`00172ba0 000007fe`e388f406 : 00000000`00000004 00000000`000000f9 00000000`11cb1130 00000000`000000f9 : ACECORE+0xaf590
00000000`00172c30 000007fe`e391aee7 : 00000000`00000000 00000000`00173198 00000000`06688ef0 00000000`11cb0998 : ACECORE+0xaf406
00000000`00172c70 000007fe`e3933a72 : 00000000`00400100 00000000`00000002 00000000`00000001 00000000`06688ef0 : ACECORE+0x13aee7
00000000`00172e50 000007fe`e384e5b1 : 00000000`00000000 00000000`11cb0020 00000000`06688ef0 00000000`00000001 : ACECORE+0x153a72
00000000`00172e90 000007fe`e38358d1 : 00000000`000007ff 00000000`06688ef0 00000000`01bd99f0 00000000`00000000 : ACECORE+0x6e5b1
00000000`00173280 000007fe`e38718eb : 00000000`000007ff 00000000`06688ef0 00000000`11cb0000 00000000`00000000 : ACECORE+0x558d1
00000000`00173340 00000001`3f3b0cd2 : 00000000`0a0945c0 00000000`000000fe 00000000`000007ff 00000000`00000000 : ACECORE+0x918eb
00000000`00173430 00000001`3f3b0b9b : 00000000`00173730 00000000`001741e0 00000000`065e5b00 00000000`00000100 : MSACCESS!CreateIExprSrvObj+0x16af32
00000000`00173630 00000001`3f3afcea : 00000000`00173730 00000000`00000000 00000000`00000000 00000000`065e5b00 : MSACCESS!CreateIExprSrvObj+0x16adfb
00000000`001736a0 00000001`3f983140 : 00000000`00174401 00000000`0a3235e0 00000000`0a319aa0 00000000`00179fc8 : MSACCESS!CreateIExprSrvObj+0x169f4a
00000000`00174290 00000001`3f3aabeb : 00000000`00000000 00000000`00000000 00000000`00179f38 00000000`00000000 : MSACCESS!FUniqueIndexTableFieldEx+0x26ab4
00000000`00174530 00000001`3f3a9670 : 00000000`001778e0 00000000`00179f38 00000000`00000031 00000000`00000000 : MSACCESS!CreateIExprSrvObj+0x164e4b
00000000`00177870 00000001`3f3a8c1b : 00000000`00000010 00000000`108c5990 003d0044`00570050 00000000`74ac3f69 : MSACCESS!CreateIExprSrvObj+0x1638d0
00000000`001779d0 00000001`3f5450df : 00000000`0a0945c0 00000000`0000009c 00000000`0a0945c0 00000000`00000000 : MSACCESS!CreateIExprSrvObj+0x162e7b
00000000`00179e30 00000001`3f64e915 : 00000000`43ed8000 00000000`00000000 00000000`3f800000 00000000`00000000 : MSACCESS!FillADT+0x5830b
00000000`0017c450 00000001`3f33b172 : 00000000`00000000 00000000`0006075e 00000000`0017e370 00000000`00000000 : MSACCESS!IdsComboFillOfActidIarg+0xaddf1
00000000`0017d730 00000001`3f33a9ef : 00000000`0017e0a0 00000000`00000b86 00000000`00000000 00000000`0fea0000 : MSACCESS!CreateIExprSrvObj+0xf53d2
00000000`0017d790 00000001`3f33a20c : 00000000`06620400 00000000`00000000 00000000`00000001 00000000`0017e420 : MSACCESS!CreateIExprSrvObj+0xf4c4f
00000000`0017e400 00000001`3f6019cd : 0071023b`007a000a 00000000`00374a30 00000000`00000005 00000000`0000000c : MSACCESS!CreateIExprSrvObj+0xf446c
00000000`0017e850 00000000`06706fd5 : e2504700`aa00ee81 00005d1b`0f2363ea 00000000`0017e9e0 00000001`3f200000 : MSACCESS!IdsComboFillOfActidIarg+0x60ea9
00000000`0017e8f0 00000000`0a30c378 : 00000000`00000000 00000000`00000008 00000000`067069ac 00000000`00000000 : 0x6706fd5
00000000`0017e960 00000000`00000000 : 00000000`00000008 00000000`067069ac 00000000`00000000 00000000`00000008 : 0xa30c378
FOLLOWUP_IP:
ACECORE+171f36
000007fe`e3951f36 4d3927 cmp qword ptr [r15],r12
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ACECORE+171f36
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ACECORE.DLL
STACK_COMMAND: .cxr 0x171ed0 ; kb
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS_80000003_ACECORE.DLL!Unknown
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/MSACCESS_EXE/15_0_4420_1017/50674523/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1
Followup: MachineOwner
5、Where the access crashed I used the ODBC trace to get the trace log of the ODBC API.
The ODBC API called by Access before it crashed are the follows.
I also ansysised the log,and I did not find any Abnormal.
Test 1174-10f0
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
6
SWORD
-8 <SQL_C_WCHAR>
PTR 0x00000000002C1F20 [
12] "LENGTH"
SQLLEN 62
SQLLEN * 0x00000000002C1E38 (12)
Test 1174-10f0
ENTER SQLGetData
HSTMT 0x0000000009F7C490
UWORD
10
SWORD
99 <SQL_C_DEFAULT>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x00000000002C1E38
Test 1174-10f0
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
10
SWORD
99 <SQL_C_DEFAULT>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x00000000002C1E38 (-1)
Test 1174-10f0
ENTER SQLFetch
HSTMT 0x0000000009F7C490
Test 1174-10f0
EXIT SQLFetch with return code 100 (SQL_NO_DATA_FOUND)
HSTMT 0x0000000009F7C490
Test 1174-10f0
ENTER SQLFreeStmt
HSTMT 0x0000000009F7C490
UWORD
0 <SQL_CLOSE>
Test 1174-10f0
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
0 <SQL_CLOSE>
6、I also did the test with the Access 2010,and with the Sql Srever/Oracle.
The results are the follows.
1) With the Access 2010(X86 or X64) and Access 2013 X86,it successes when I export the table to the DB Symfoware.But only with the Access 2013 X64,the Access crashed.
2)With the Access 2010(X86 or X64) and Access 2013(X86 or X64),using the Sql Srever/Oracle,it always successes .
According to all the descrived above, I wonder if it a bug of the Access2013 .
Could anyone can help me ?
Thanks for any help.George Zhao
Thank you for your help.
I have already install
the latest patches of the Office 2013.But it doesn't work.It is down also too. And ODBC
drive of Database Symfoware is the newest driver of the Database Symfoware. Now I wonder that
if it si a bug of the ODBC
drive of Database Symfoware,I should fix the bug,but I have analysised the odbc trace log and I do not find any wrongs ,so I think maybe it is a bug of the Access .
I have see many situations about the Access down on the internet . -
R3trans not exporting all tables
Hi
I am creating a control file to export SXNODES table
export
file = '/tmp/SXNODES_dmp'
delete * from 'SXNODES'
select * from 'SXNODES'
When I export, using R3trans, I get 0 entries exported. I used to be able to export this table until we upgraded to ENHP4
3 ETW678Xstart export of "R3TRCNTDSXNODES" ...
4 ETW000 0 entries from TADIR exported (R3TRCNTDSXNODES ).
4 ETW679 end export of "R3TRCNTDSXNODES".
3 ETW678Xstart export of "R3TRCNTDSXNODES" ...
4 ETW000 0 entries from SXNODES exported (000*).
4 ETW000 The corresponding TADIR entry was already selected before (R3TRCNTDSXNODES).
4 ETW679 end export of "R3TRCNTDSXNODES".
Any idea?Hi Prashant,
The error clearly says 'FAGLFLEXA-MANDT - is not a key field'
RCLNT is the key field for client for FAGLFLEXA table.
Also, as you already mentioned client=200 in the control file, there's no need to give a where clause for client.
select * from FALGLFLEXA will do.
Regards,
Sajith -
Database version :11.1.0.7.0
Problem : While trying to export a table using the following command
command : exp scott/tiger FILE=c:\owb_target.dmp LOG=c:\owb_target.log tables= (scott.emp,scott.dept)
Error encounteres is as follows :
About to export specified tables via Conventional Path ..
EXP-00008: ORACLE error 1455 encountered
ORA-01455: converting column overflows integer datatype
EXP-00000: Export terminated unsuccessfull
Any idea how to get around this ?
CheersThere are various Metalink Docs that point to this being a bug - have you opened an SR ?
HTH
Srini -
Error while exporting database
Hi guys!!!
i get the following error while i export the objects of a database.The error occurs during the table's exportation:
EXP-00003: no definition of memory found for the segment (5, 5713).
I noticed that the error occurs only in the tables that have a sdo_geometry column.
What can cause this error?
Thank you,
AngeloHI
Yes I have experienced this. To get around this I export my tables locally, so that I use the same version of the export utilitiy as the database.
This is a known issue see METALINK NOTE:274076.1
(Bug 3784697)
"This problem during export has been introduced with the 9.2.0.5 patchset, an export from the 9.2.0.5.0 or any higher release database (e.g. 9.2.0.6.0 or 10.1.0.4.0) with a lower release export utility, e.g. 9.2.0.4.0 or 8.1.7.4.0 will now produce the EXP-3 error."
Dawn
Maybe you are looking for
-
Windows 7 very slow logon, Waiting for the User Profile Service, winlogon event 6006
Hello, Every so often one of our Windows 7 clients which is not normally having any delay at logon will take a very long time to login. This may be 10 or 20 minutes or up to an hour in some cases. Typically the event log will contain entries like The
-
Why is the "microphone" missing on my iPhone in Mail?
Just today I noticed that the little microphone is missing from the Mail keyboard when sending Mail. Why?
-
Screen saver slide show keeps reverting to National Geographic photos?
Hi all - quick question about a minor annoyance. I have the screen saver set to display photos from one of my iPhoto photo sets using the built in screen saver options. For no apparent reason, it occasionally decides to stop displaying my photos an
-
"group by" slow for using "count(distinct some_column)" - a better way?
Hi all, i have an select count(distinct some_column), from [...] group by [...]; Which is slowed down for the "*count(distinct some_column)*". The "group by" aggregates base records. But the base records have 1:n for some #1 event #n records each. So
-
How the transaction executing in Oracle bpm 10g
Hi, i want to know "how the database transaction executing in Oracle bpm 10g", My Scenario is 'i have two data tables, i need to update the same information in two different data tables with OBPM 10g. let's imagine, info is updated in 1st data table,